Skip to content

fix(dispatch,router): wire grob_hint + doc drift (#5 #6 #14)#245

Merged
Destynova2 merged 2 commits intomainfrom
docs/dispatch-router-drift
Apr 21, 2026
Merged

fix(dispatch,router): wire grob_hint + doc drift (#5 #6 #14)#245
Destynova2 merged 2 commits intomainfrom
docs/dispatch-router-drift

Conversation

@Destynova2
Copy link
Copy Markdown
Contributor

Summary

Two quick wins from the Tier 2 audit, bundled because they share the dispatch/routing scope.

DD-1 — audit #5: let _ = grob_hint in dispatch

The MCP complexity hint (X-Grob-Hint header, metadata.grob_hint, or one-shot MCP slot) was resolved and then silently dropped. It now overrides RouteDecision.complexity_tier right after routing, so a client that declared trivial opts out of [[tiers]] fan-out for that request.

DD-2 — audit #6 + #14: doc drift

  • src/routing/classify/mod.rs: the route() doc-comment listed only 6 priority levels while the actual code has 9 (auto-map, declarative tier match, and algorithmic scoring were missing). Inline numbering also had a // 7. gap and a duplicated // 9. — renumbered.
  • docs/explanation/architecture.md: the request-flow Mermaid still showed the pre-T-VS router subgraph and a single generic "Circuit Breaker" box. Updated to the new routing/ parent (classify + circuit_breaker + health_check), the RE-1a / RE-1b split from ADR-0018, the is_endpoint_healthy AND-gate, and the security-layer global CB that runs after it.

Test plan

  • cargo fmt
  • cargo clippy --all-features -- -D warnings
  • cargo clippy --lib --no-default-features -- -D warnings (cfg mcp off)
  • cargo test --lib — 950 passed, 0 failed
  • CI green

Note: pushed via GitHub Git Data API — local git push was silently reset (see feedback_commis_push_ghosting.md).

Destynova2 and others added 2 commits April 21, 2026 22:45
The MCP complexity hint (`X-Grob-Hint` header, `metadata.grob_hint` body
field, or one-shot MCP tool slot) was resolved and then dropped via
`let _ = grob_hint`. It now overrides `RouteDecision.complexity_tier`
right after routing, so clients that know their task is trivial can opt
out of `[[tiers]]` fan-out for a single request.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
Two drift fixes caught by Tier 2 audit (items #6, #14):

- `src/routing/classify/mod.rs`: the `route()` doc-comment listed only
  6 priority levels while the actual code has 9 (auto-map, declarative
  tier match, and algorithmic scoring were missing). The inline
  numbering also had a gap (skipping #7 and duplicating #9) — renumbered
  to match.
- `docs/explanation/architecture.md`: the request-flow mermaid still
  showed the pre-T-VS `router` subgraph and a single generic "Circuit
  Breaker" box. Updated to reflect the `routing/` parent module
  (classify + circuit_breaker + health_check) and the RE-1a / RE-1b
  split from ADR-0018, including the `is_endpoint_healthy` AND-gate
  and the security-layer global CB that runs after it.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
@Destynova2 Destynova2 enabled auto-merge (squash) April 21, 2026 20:46
@Destynova2 Destynova2 merged commit ae1c81d into main Apr 21, 2026
42 checks passed
@Destynova2 Destynova2 deleted the docs/dispatch-router-drift branch April 21, 2026 20:56
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