The router had zero production callers — architecturally implemented but
cognitively dead. This makes it operational (handoff 2026-09-10 §1/§20.A–C):
- ISSUE stage (production dispatch entry) now classifies route before the
fixed-depth chain; LOCAL_FIX terminally routes out to the local
implementation/verification lane (ROUTED_LOCAL_FIX, tree records route)
- Sufficiency inputs replace substring inference as primary evidence:
5 questions with traceable provenance; non-establishable facts recorded
as UNKNOWN and forced upward (never manufactured certainty)
- Mechanism-uncertainty language (performance/timing/concurrency) makes
local_authority honest — measurement questions are not source-readable
- Escalation/downgrade/FINAL_ROUTE are persisted events in the same
append-only authority (route.jsonl); transition identity fields
(previous_route/trigger/evidence) mandatory
- Deep-research floor: narrow, objectively detectable triggers;
FloorViolation on efficiency-driven downgrade bypass
- Legacy boolean API preserved as marked compat shim (legacy semantics)
- Canaries: local-route behavioral effect, research floor entry,
escalation transitions, floor non-bypass, full audit trail
reconstruction (tests/test_adaptive_router_wiring.py)
- Suite: 1178 passed (3 pre-existing env failures excluded, reproduced
on clean master)
Refs #291, #324 (checkpoint defect, unrelated)