docs(06): A1 decision — c3 now / c2 next milestone; D-12 street-bearing ratified

.planning/phases/06-turn-by-turn-guidance-live-driving/06-04-SUMMARY.md

@@ -184,3 +184,16 @@ Forks: the same three steps are `docs/ROAD-GRAPH.md`.
 - `npm run routing:test`: 65 passed / 0 failed (A1's 625-pair Dijkstra-equivalence sweep green on the bidirectional A*). `npm test -w bot`: 103 passed / 0 failed (RT1–RT11, GE5 one-kv-namespace, re-pinned RP1/RP2). `routing:typecheck` + `bot:typecheck` clean.
 - STATE.md and ROADMAP.md untouched (their working-tree modifications predate this session — orchestrator-owned writes); only this SUMMARY force-added.
 - Honest gaps recorded, not papered over: the A1 CPU gate FAILS (escalated with ladder evidence, above); the R2 bucket awaits account-level activation (user_setup).
+
+## A1 DECISION (maintainer, 2026-10-24)
+
+**c3 now, c2 next milestone.** Short product reroutes (2–8 km) run 2–8 ms — inside the
+free plan's 8 ms budget; cross-metro routes (20–30 km, p95 38–93 ms) degrade honestly
+to the router-pending state (engine's 1102 CPU-exhaust path → fail-honest null → the
+designed pending card). Workers Paid (c1) rejected — $0 mandate. ALT landmark
+preprocessing (c2) is the committed upgrade lever for the NEXT milestone (fixes long
+routes while staying $0). The verifier treats GUID-02's engine side as delivered with
+this documented degradation class.
+
+R2 activation still pending user dashboard click (code 10042) — non-blocking for
+06-07/06-08; /api/route serves honest nulls until the graph uploads.