Driver

PR #357 Rex review flagged advertised-but-not-parsed allowed_tools_override field in the agent-routing v1 schema. Adopters who set it get a silent no-op — confusing UX. The field is documented at:

• .claude/hooks/apply-agent-routing.sh:115 (parser comment block)
• docs/multi-project.md:549 (adopter-facing schema table)

…but parse_routing() inside apply-agent-routing.sh never emits an allowed_tools_override: line in the per-agent override map, so the SessionStart frontmatter rewrite ignores any value an adopter sets.

Scope

Pick one of two fix paths (recorded as the AC decision):

1. Add the parser branch so the field works as documented. Lower migration risk for adopters who've already added the field — preferred.
2. Drop the field from both the parser comment + docs/multi-project.md:549. Acceptable if the field is deemed too risky / advanced for v1 (the docs already mark it as "advanced — use sparingly").

Same shape applies for the future timeout_seconds: field if it shows the same drift — sanity-check during this fix.

Acceptance Criteria

• Decision recorded: parser-branch-or-drop (in the PR description or a short AgDR)
• Either allowed_tools_override: is parsed + applied to the agent frontmatter, OR every doc/comment reference is dropped
• Smoke test extended: case for an allowed_tools_override: entry asserting the documented behaviour holds
• TBD — refine before starting work

Source: PR #357 Rex review (#357 (review))