Repository navigation
[codex] Phase 4.10 context routing hardening - #283
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
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.
Summary
Implements the current Phase 4.10 context/routing hardening stack: provider-facing context pressure accounting, lane-aware model routing, strict shared runtime tool protocol cleanup, model profile catalog support, modality admission, bounded repair traces, and memory-quality guardrails. It also adds catalog-backed OpenRouter Gemma aliases (gemma31b, gemma26b) while keeping the default route unchanged.
Validation
Notes
The branch contains the five local commits currently ahead of origin/main and has been verified against the local working tree. GitHub reported existing default-branch Dependabot alerts during push; those are unrelated to this PR.