Repository navigation
Refresh Codex 0.162.1 probe and replay evidence - #56
Merged
Merged
Conversation
minglong51
marked this pull request as ready for review
October 11, 2026 18:02
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.
Refresh the Phase 0 Codex probes from 0.157.1 to the installed 0.162.1 native executable and its code-mode-host companion, with exact SHA-256 pins. Accept the newly generated schema's
promaxaccount-plan value while continuing to validate and discard account metadata.Regenerate all four sanitized replay rows from fresh private input, permission, command, and file-request captures. Each live probe passed observer restart, correlation, stale/duplicate rejection, and freshness checks; authentication copies were removed and denied action targets remained absent. Claude and Kimi pins are unchanged.
Validation: all 280 tests pass; all 45 live scenario checks pass; re-export from the four private sources matches the fixture byte for byte. Evidence checks keep all 24 capability cells unknown and the four replay rows unqualified. Independent Gemini 3.1 Pro review found no blockers; macOS/Linux CI is required before merge.