Repository navigation
Add native runtime claim lifecycle outcomes - #988
Merged
Merged
Conversation
|
Warning You have reached your daily quota limit. Please wait up to 24 hours and I will start processing your requests again! |
Codex Review SummaryThis comment shows the latest Codex review activity on this pull request.
ℹ️ About Codex in GitHubYour team has set up Codex to review pull requests in this repo. Reviews are triggered when you
Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings. |
GraciousGazelles
force-pushed
the
fix/w18773-native-lifecycle-outcomes
branch
from
October 23, 2026 19:46
4526356 to
6ca63e2
Compare
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
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.
The native runtime-proof launcher now supports the full protected work-item lifecycle. Its v2 certificate authorizes only exact claim and release calls; current-work and same-actor exact-request receipt reads use ordinary MCP authentication. The launcher projects bounded canonical outcomes from the primary
codex exec --jsonstream to its existing journal path, leaving lost completion or missing receipt unresolved and never forwarding raw tool/model output or child-thread events.The change also enables the four fixed Ops tools and preserves the existing v1 HTTP claim certificate wire contract. Ops-side v2 verifier/tool compatibility is being implemented separately against the frozen contract; end-to-end first use remains pending both accepted artifacts.
Validation: source and regression tests are included, but no local build/tests were run. Hosted checks and independent focused review are pending.