Skip to content

fix: bind Codex routing state and workspace identity - #200

Merged
HTExplicit merged 13 commits into
mainfrom
fix/codex-quality-release
Sep 24, 2026
Merged

HTExplicit merged 13 commits into
mainfrom
fix/codex-quality-release

Conversation

@HTExplicit

@HTExplicit HTExplicit commented Sep 23, 2026 •

Copy link
Copy Markdown
Owner

Codex OAuth requests could reuse STATE across logical turns, retain routing qualifications after their local connection disappeared, and derive the selected workspace's plan from a different workspace. This binds routing eligibility to a live scoped connection, shares final outbound identity and routing-hint handling between probes and business requests, and retains only the first committed STATE within the same subject, session and turn.

Team and Business identities use the selected workspace. Historical STATE lengths no longer grant routing eligibility or imply answer quality. The UI distinguishes routing material, response completion, raw model declarations and untested answer quality. Raw diagnostic observation runs before model guards and gateway rewriting, with explicit high checked at the send boundary. Inspection supports non-replayable outgoing bodies without enabling transparent POST replay. All seven bundled plugin versions advance to 0.2.13 for immutable signed packages.

Validation already completed:

  • Protocol: 12 focused service tests and 4 connection-lease repository tests; composition: 2 focused raw-observation/high/limit tests.
  • Identity: 6 focused backend tests, 5 plugin tests and 24 frontend tests (51 unrelated tests intentionally excluded).
  • Five affected contract tests passed after updating connection-bound Cookie fixtures and testing actual Messages forwarding within a proven turn and across new/unknown turns. Production checks were not weakened.
  • The five additional CI failures were corrected and passed targeted checks: retained configuration fields remain environment-reachable, simulated responses match the actual resolved model, and metadata sessions do not imply a shared turn. Unused legacy helpers and unchecked fixture assertions were removed or corrected.
  • The three v0.2.8 gateway conflict resolutions and all 35 identity paths received independent static review.
  • All three new diagnostic wire tests also passed on the complete tree (service 0.237s), with the fixture implementing the same scope and deadline inspection as a real connection lease.

The normal required PR checks remain enabled. Fixed-account Pro20x quality acceptance is pending; correct routing and model labels alone do not establish sustained reasoning quality.

Codex and others added 9 commits September 24, 2026 00:14
Bring 5f88149 (routing probes, turn state, response evidence), 0f2c225
(workspace plan identity, retired length-based tickets) and d1e5bb0
(protocol guards composed with the bounded diagnostics) onto the A
integration with the manual-stop guard.

Conflicts: forward/passthrough keep the v0.2.8 GPT-5.5 Lite mapping step and
return the request with the Codex routing downstream context; the new
model-mismatch stream error uses the v0.2.8 two-argument error event with the
reason as both code and message, as the one-argument form did.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
(cherry picked from commit b771253350b9ec47dd60bf896e9289df42e1cb76)
@HTExplicit
HTExplicit merged commit e44e378 into main Sep 24, 2026
18 checks passed
@HTExplicit
HTExplicit deleted the fix/codex-quality-release branch September 24, 2026 02:50
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant