Repository navigation
fix: expose stable Codex executable to A2A user service - #216
Merged
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Adds the stable user executable directory to the shipped A2A service PATH and prepares v0.7.1. Under the actual user's systemd manager, v0.7.0 admitted a request/arm but exited runtime_unavailable before transport because bare codex could not be found. The corrected read-only service lookup resolves the existing stock daemon successfully.
Validation: 10 shared-reader tests pass; compileall, systemd unit verification and diff check pass; native owned systemd-run preflight uses /usr/bin/env codex with the corrected PATH and reports existing daemon 0.160.0, then exits0. Required hosted release CI must pass before merge/tag publication and ordinary install. Live service M1, multiroot and soak remain separate acceptance gates.
No mailbox schema, transport logic, daemon bootstrap/restart or OpenClaw changes. v0.7.0 and its failed zero-attempt qualification are preserved; bounded service and Restart=no remain.
Refs #181. Plan0119, service failure evidence in the docs/p63-v070-installed packet. The branches share the lane catalog and must preserve both projections when integrating.
Need help on this PR? Tag
@codesmith-botwith what you need. Autofix is disabled.