fix(release): repair beta6 validation regressions#105034
Merged
Merged
Conversation
Contributor
|
Codex review: stale review; fresh review needed. Summary Next step |
(cherry picked from commit db39fe8)
Contributor
Author
|
Land-ready proof for exact head
Known proof gap: the three original release-validation child failures and full beta validation intentionally rerun after merge against the new canonical |
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.
What Problem This Solves
The beta6 candidate had three deterministic release-validation regressions:
codex/*provider route.Why This Change Was Made
db39fe807202b259cf1269eae560c213e0c2afef, centralizing provider/runtime compatibility while preserving rejection for unsupported pairs.User Impact
Beta6 retains native Codex runtime switching for both
codex/*andopenai/*routes. Existing pre-hash Codex thread bindings resume without unnecessary context reprojection. Control UI behavior is unchanged; its suite is deterministic under shared-worker ordering.Evidence
tbx_01kxadxjrn0dayyqn5assy8ck8: focused chat-send 99/99 and full Control UI 143 files / 2,331 tests passed.tbx_01kxaee72ew2mdqgrcxccpy6fk: runtime/directive 328/328 and Codex context-engine 29/29 passed.tbx_01kxagj2q2aygpzw0hxhhegx07: full TUI PTY real-backend file 8/8 passed after registering terminalizing validation-abort cases last.tbx_01kxah6wq8h2v9q22c6qnp6dme: full TUI PTY real-backend file 8/8 passed after recognizing the Gateway's transient active-parent response in the existing bounded/newretry loop.git diff --checkpassed.Risk
The runtime change is an exact canonical backport already landed and validated on main. The fingerprint change uses the existing compatibility API and only admits the prior representation for the same next tool set. The TUI changes preserve all cases, follow main's canonical terminalizing-test ordering, and keep success mandatory after bounded busy-state retries. The package helper is the exact test contract required by the existing matrix assertions. No config, secret, or migration surface changes.
Current review state
Awaiting exact-head hosted PR CI. After merge, rerun the three failed lanes and full beta release validation on the new
release/2026.7.1head.