BIRTH Stage 2.6A-FIX5 — QT-001 Remove Legacy Planner + False-Proof Rebuild

Date 2026-06-07. Mode: EXECUTION. Live mutation: YES (additive/reversible/birth-neutral). Status: PARTIAL — STAGE2_6A_FIX5_LEGACY_PLANNER_REMOVED_FALSE_PROOF_REBUILT_READY_FOR_CODEX_REAUDIT.

Fifth corrective macro for Stage 2.6A. Answers Codex STAGE2_6A_FIX4_FAIL_HARDCODE_OR_BYPASS_STILL_DANGEROUS.

Core lesson, finally acted on: Codex kept finding defects because prior fixes graded newly-created guards in isolation while the real writer/driver/builder/current-plan path still called legacy objects, and the "no-legacy" guard was a hand-maintained NAME deny-list that never traced the actual dependency closure. FIX5 builds the REAL recursive callgraph first, proves no authoritative root reaches the legacy planner v2 (or any legacy object), then rebuilds every false proof as a behavioral/structural control.

Outcome: 12/12 Codex FIX4 blockers reproduced LIVE then 11 FIXED + 1 ROUTED_2_6B_BLOCKING. Apply remains BLOCKED for real structural reasons. Production no-worse: QT-001 births 0, permits 0, done ledgers 0, Tier1/signoff 0, readiness BLOCKED, gateway md5 unchanged.

Do NOT proceed to apply / permit / 2.6B until a fresh independent Codex re-audit of FIX5 PASSES. Docs 01–13 + checkpoint give the full evidence.