Repository navigation
Make Codex input recovery qualification repeatable - #50
Merged
Merged
Conversation
Triad: SHIP 2026-09-26
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.
Phase 0's Codex input/recovery proof depended on temporary scripts that disappeared with the private captures. Add
scripts/codex_qualification.pyto repeat the bounded scenario inside an isolated clilane task: verify host isolation, open one synthetic input request, expire and restart the observer while keeping the provider alive, require a new source read, and cancel the input.The probe uses the existing pinned collector, compares its private journal against the provider capture, and removes its credential copy before child-process cleanup, including on TERM/HUP/INT. Recurring
thread/readresponses maintain freshness while the final turn completes. The analyzer validates the isolatedskills/listexchange, and the transport accepts an explicit sanitized environment.This remains a Phase 0 tool for absolute private sockets. Its report is explicitly unqualified; the 24-cell matrix stays unknown and the shipped runtime is unchanged.
Validation: