chore(planning): close phase 8 — verification decision recorded (CH as 08.1), direction-split research handoff written

.planning/STATE.md

@@ -2,16 +2,16 @@
 gsd_state_version: 1.0
 milestone: v1.x
 milestone_name: routing-engine-upgrades-and-extras
-status: executing
-stopped_at: "08-05 executed (D-03 optimality gate GREEN after the gate caught the four-family ALT steering returning suboptimal routes — fromTable families removed from the potential, Rule 1; the CPU campaign measured HONEST FAILs: 25-route p95 152.788 ms / extended 185.692 ms vs the 8 ms budget; the pre-committed L=32 ladder rung measured worse and stopped; c3 NOT retired — every record carries the quoted post-ALT truth; NEXT: maintainer decisions — R2 upload (deploy-time) + the SC-1 escalation track: direction-split potentials / CH / Workers Paid reversal / keep c3)"
-last_updated: "2026-10-25T12:09:32.000Z"
+status: ready_to_plan
+stopped_at: "F1 remediation applied (debug alt-potential-4x-slowdown RC-1): clean-columns-only ALT containment in routing/src/astar.ts — per-node sentinel skip removed; suite re-spec'd RED-first (A11) + new A13 mixed-column case; new committed oracle sweep measure-astar-oracle-sweep.mjs 0/200 suboptimal; CPU back in the pre-ALT band (p95 136.6 ms this host vs 1037.6 pre-fix — honest c3 FAIL vs 8 ms stands); D-03 gate green. Commits c071e20 / 2a5a0b5 / 97d6e35. NEXT: maintainer R2 upload + the SC-1 escalation decision (unchanged)"
+last_updated: "2026-10-25T14:15:06.953Z"
 last_activity: 2026-10-25
 progress:
   total_phases: 4
-  completed_phases: 1
+  completed_phases: 2
   total_plans: 5
   completed_plans: 5
-  percent: 100
+  percent: 50
 ---
 
 # Project State
@@ -25,9 +25,9 @@ See: .planning/PROJECT.md (updated 2026-10-22)
 
 ## Current Position
 
-Phase: 8
-Plan: 08-05 complete (all five plans executed; commits `149636c` / `79a302c` / `720ad43` + the measurement session)
-Status: Phase 8 executed — maintainer decisions open (R2 upload; the SC-1 escalation track)
+Phase: 08.1
+Plan: Not started
+Status: Ready to plan
 Last activity: 2026-10-25
 
 Progress: [██████████] 100%
@@ -36,7 +36,7 @@ Progress: [██████████] 100%
 
 **Velocity:**
 
-- Total plans completed: 34
+- Total plans completed: 39
 - Average duration: —
 - Total execution time: —
 
@@ -52,6 +52,7 @@ Progress: [██████████] 100%
 | 5 | 5 | - | - |
 | 6 | 8 | - | - |
 | 7 | 6 | - | - |
+| 8 | 5 | - | - |
 
 ## Accumulated Context
 
@@ -69,7 +70,7 @@ None yet.
 
 ### Blockers/Concerns
 
-- **PHASE 8 ESCALATION (open, 2026-10-25):** the CPU verdict measured FAIL post-ALT (25-route p95 152.788 ms / extended 185.692 ms vs the 8 ms budget; the L=32 probe worse) — the c3 class remains. The theoretical wall: no two-sided-Lipschitz landmark extension exists on a graph with sentinel fringes; sound+fast needs direction-split potentials with a re-proven meet rule (search-skeleton work). Options: direction-split potentials (new phase) / CH (Phase-6 deferral) / Workers Paid reversal ($0 law) / keep c3 (current shipped posture). Records: docs/BUDGETS.md §c3, docs/KNOWN-LIMITATIONS.md, 08-05-SUMMARY.md.
+- **PHASE 8 ESCALATION (open, 2026-10-25):** the CPU verdict measured FAIL post-ALT (25-route p95 152.788 ms / extended 185.692 ms vs the 8 ms budget; the L=32 probe worse) — the c3 class remains. The theoretical wall: no two-sided-Lipschitz landmark extension exists on a graph with sentinel fringes; sound+fast needs direction-split potentials with a re-proven meet rule (search-skeleton work). Options: direction-split potentials (new phase) / CH (Phase-6 deferral) / Workers Paid reversal ($0 law) / keep c3 (current shipped posture). Records: docs/BUDGETS.md §c3, docs/KNOWN-LIMITATIONS.md, 08-05-SUMMARY.md. **F1 addendum (2026-10-25, post-plan):** the debug session also exposed RC-1 — a LIVE correctness bug in the ALT potential (per-node sentinel skip broke cross-edge consistency; 1/194 fresh pairs suboptimal vs Dijkstra) — fixed the same day (clean-columns-only containment; commits c071e20/2a5a0b5/97d6e35; new committed oracle-sweep gate 0/200). On the current 0/24-clean binary ALT is inert (exact haversine), so the CPU band is pre-ALT again (p95 136.6 ms this host) and this escalation is UNCHANGED — a future clean-column binary re-arms ALT with no code change; F2 (transposed tables) is the then-relevant performance follow-up.
 - ~~PHASE 4 device-gate legs UNVERIFIED~~ RESOLVED 2026-10-24: legs 1–4+6 PASS on real hardware; leg 5 user-accepted (BotFather Main Mini App configured; unknown-id surface covered by automated gates). Known-open cosmetic: /cari absent from the client command menu (Telegram non-default setMyCommands defect; command works when typed; register script re-arms all scopes for retry).
 - Design-source conflict (root `DESIGN.md` typography vs `telemetry_rams/DESIGN.md` + mockups) — Phase 1 resolves; mockup markup is layout reference only, design doc tokens are binding (scrub rounded/blur utilities)
 - ~~VPS provisioning starts in Phase 4 (Photon bake-off)~~ SUPERSEDED by Phase 4 D-03: search is an in-Worker curated gazetteer ($0); VPS provisioning (Valhalla + Photon) defers to Phase 5; Photon is a documented SearchSource backend #3 (free-first mandate: one VPS, Oracle Cloud Always Free candidate)
@@ -91,6 +92,6 @@ None yet.
 
 ## Session Continuity
 
-Last session: 2026-10-25T12:09:32.000Z
-Stopped at: "08-05 executed (D-03 gate green after the fromTable fix; CPU verdict honest FAIL 152.788/185.692 ms; ladder stop at L=32; c3 remains — escalation open); NEXT: maintainer R2 upload + the SC-1 escalation decision"
-Resume file: .planning/phases/08-alt-landmark-preprocessing-routing-backend-v2/08-05-SUMMARY.md
+Last session: 2026-10-25T14:15:06.939Z
+Stopped at: "F1 remediation applied (debug alt-potential-4x-slowdown RC-1): clean-columns-only ALT containment; oracle sweep 0/200; CPU in the pre-ALT band (c3 stands); D-03 green — gates re-run 2026-10-25"
+Resume file: None