Repository navigation
Reuse Codex route validation for same-session business STATE updates - #277
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.
A Codex tool continuation can return a new business STATE while its route, native session, model, tier and exit are unchanged. Including that discarded probe input in the qualification key started another two-shot probe and could block an otherwise qualified session on a transient validation timeout. Reuse the live proof across business STATE updates, while sending each turn's own STATE unchanged.
The independent two-shot STATE check, original candidate expiry, account/model/tier/exit/TLS isolation and native session/window boundaries remain enforced. The regression reproduces four probes for two business turns before the fix and requires only the initial pair afterward.
Validation: targeted unit-tag regressions passed for cache identity/model isolation, all five HTTP tool-session tier cases, final-tier separation, prepared dispatch and existing WS continuation/expiry/model/identity/capacity protection. This follows the isolated source self-check in #276; both changes are intended for the same fixed production release.