Skip to content

[codex] Phase 4.10 context routing hardening - #283

Merged
panviktor merged 5 commits into
mainfrom
codex/phase4-10-context-routing
Apr 11, 2026
Merged

panviktor merged 5 commits into
mainfrom
codex/phase4-10-context-routing

Conversation

@panviktor

Copy link
Copy Markdown
Owner

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

  • cargo fmt --all -- --check
  • python3 -m json.tool crates/domain/data/model_catalog.json >/dev/null
  • cargo test -q -p synapse_domain model_catalog --lib
  • cargo test -q -p synapse_domain inbound_message_service::tests::effect_switch_model --lib
  • cargo test -q -p synapse_adapters models_help_includes_configured_routes --lib
  • cargo check -q -p synapse_domain -p synapse_adapters -p synapseclaw --features channel-matrix
  • cargo build --release --features channel-matrix
  • local user-service deploy plus health checks on ports 42617..42622
  • gateway smoke for /model gemma31b resolving to google/gemma-4-31b-it via OpenRouter

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.

@panviktor
panviktor marked this pull request as ready for review April 11, 2026 08:29
@panviktor
panviktor merged commit 582c92b into main Apr 11, 2026
0 of 8 checks passed
@panviktor
panviktor deleted the codex/phase4-10-context-routing branch April 11, 2026 08:30
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