docs: reconcile v0.8.65 release ledger to live state

[Hmbown]

Refreshes docs/V0865_RELEASE_LEDGER.md to reflect the live state after Phase 2 triage + a 25-issue milestone reconciliation against main.

Headline: v0.8.65 is not release-ready — 0 of 25 open milestone issues are closeable (18 partial, 7 not started); major architecture (Fleet substrate, provider descriptors/pricing/catalog/telemetry/context-budget, config split, README end-cap) is still outstanding.

Records:

• Phase 2 PR outcomes: Add provider readiness dashboard rows #3485 + fix: prevent ordinary prompt text from being interpreted as a mode switch (#3387) #3491 merged; Harden local state storage boundaries #3433/fix: prevent ordinary prompt text from being interpreted as a mode switch #3455/feat(tui): resolve provider switches through an atomic RouteCandidate (#3384) #3492 closed with evidence; feat(tui): enhance approval modal button prominence with visual grouping #3437/docs: add official-site and mirror provenance copy to codewhale.net #3440 reviewed (needs rework — both carry a SECURITY.md .net→.com regression); docs(prompt): add Orchestration disposition + Fleet design note (Track B / EPIC #3154) #3470/Refresh repo agent guidance around live state #3452/Extract shared bridge core helpers #3432 held for Hunter; Feat/memory tags #3381/feat(hippocampal): v2 memory system — glossary, namespaces, rollback, auto-inject, daemon #2933/Feat/whaleflow cost tracking #2486/feat: i18n Phase 1-4b wiring + rebase compile fixes #2239 out of scope.
• Per-issue reconciliation table with merged evidence and next steps.
• A decisions-for-Hunter list (incl. the v0.8.65: Resolve every provider/model switch through a ReadyRouteCandidate #3384 finding: wire on the canonical codewhale_config::route::RouteResolver from feat(config): EPIC #2608 route foundation — canonical types + ReadyRouteCandidate/RouteResolver (#3084, #3384) #3458, not a parallel resolver).

Supersedes the orphan codex/v0.8.65-ledger-update branch. Docs-only.

[claude]

Claude finished @Hmbown's task in 1m 5s —— View job

---

Review: docs/V0865_RELEASE_LEDGER.md

• Read diff and full file
• Verify internal consistency (counts, cross-references, SHA formatting)
• Check factual claims within the document's scope
• Post review

---

Docs-only change. No code correctness, security, or provider-routing issues to flag. The reconciliation is thorough and the verdict ("0 closeable") is substantiated by the table. A few notes:

Correctness checks

• Issue math checks out. 18 partial + 7 not-started = 25 total. All rows in the table tally against those counts. ✓
• Cross-references are consistent. v0.8.65: Resolve every provider/model switch through a ReadyRouteCandidate #3384 appears in both the reconciliation table and decision item Simplify UI and improve footer display (v0.3.14) #2 with the same instruction ("build on feat(config): EPIC #2608 route foundation — canonical types + ReadyRouteCandidate/RouteResolver (#3084, #3384) #3458, not a parallel module"). feat(tui): resolve provider switches through an atomic RouteCandidate (#3384) #3492's closure rationale in the Closed-with-evidence section matches that decision. ✓
• fix: prevent ordinary prompt text from being interpreted as a mode switch #3455 appears twice correctly — once in Phase 2 Closed-with-evidence (closed in favor of fix: prevent ordinary prompt text from being interpreted as a mode switch (#3387) #3491) and is implicitly the "community PR" credited in the fix: prevent ordinary prompt text from being interpreted as a mode switch (#3387) #3491 row. No contradiction. ✓

One gap worth noting

PR #3484 (model-picker search) is mentioned in the verdict intro (line 19) as a recently landed foundation PR, but it doesn't appear in either the Phase 1 or Phase 2 merged tables. A reader tracing the merge history can't tell which session landed it or find the associated evidence. Suggest adding it to whichever phase table is correct (Phase 2 if it landed this session, Phase 1 if prior).

Minor

• Inconsistent SHA lengths: 5b8a5ac0b and 662a459ee are 9 chars; the other evidence SHAs are 10 chars. 9-char SHAs can theoretically collide on large repos. Not blocking, but worth normalising.
• The CodeWhale-trackd-routes worktree entry (line 114) correctly names this PR's branch — good self-consistency.
• The SECURITY.md .net→.com regression finding for feat(tui): enhance approval modal button prominence with visual grouping #3437 and docs: add official-site and mirror provenance copy to codewhale.net #3440 is clearly documented and correctly gates both PRs. Good call calling that out explicitly.

Overall

This is a high-quality state snapshot. The release-readiness verdict is evidence-backed and the decisions-for-Hunter list is specific and actionable. The #3384 gap (build on #3458 resolver, not the parallel WIP one) is the most architecturally load-bearing item and it's documented well. Ready to merge once Hunter reviews the decisions section — the docs themselves are sound.

---