Repository navigation
Fix Codex borrow probe identity and blocked-request evidence - #269
Merged
Merged
Conversation
HTExplicit
enabled auto-merge (squash)
October 9, 2026 17:54
HTExplicit
disabled auto-merge
October 9, 2026 17:57
HTExplicit
enabled auto-merge (squash)
October 9, 2026 17:58
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.
Codex business requests could be rejected before dispatch while the console still showed only an earlier successful diagnostic. Target probes also replaced the native session headers on every shot and omitted the effective service tier from their body, diverging from the pinned ranxi full-probe request contract.
This restores the probe session contract, includes native identity/routing policy in qualification proofs, preserves the exact failure reason through cooldowns, and records preparation failures separately from actual sends. Ops reports those local rejections as gateway failures with no upstream HTTP status. The admin diagnostic adds an isolated HTTP tool-call/STATE/full-history continuation scenario within the existing eight-request bound. Astra and the downstream Sol extension remain independently validated; no ordinary-path fallback, proxy/mapping/identity changes or database migration is introduced.
Validation: targeted Go request-contract, failure/cooldown/counter, HTTP continuation and Ops attribution regressions passed. Native WS preparation/relay regressions passed. Four focused frontend cases, Vue typecheck, focused ESLint and Vite build passed. Browser checks covered Chinese/English, keyboard disclosure and 390px layout with synthetic data. Production model acceptance is pending deployment; prior short-prompt successes are not evidence for this repair.