docs: add v0.8.65 release ledger

[Hmbown]

Summary

• add docs/V0865_RELEASE_LEDGER.md as the v0.8.65 coordination ledger
• capture Phase 1 queue state, worktree layout, merge order, blockers, and next commands
• document concrete outcomes for fix(bridge): clear activeTurnId after approval decision to unblock user #3468, fix(web): remove stale references to retired sub-agent lifecycle tools (#3414) #3472, feat: publish weekly community digest archive route #3420 #3476, fix(tui): allow read-only git tag probes in yolo #3479, feat(web): add fact-drift CI gate for version, providers, and tool inventory (#3415) #3473/feat(web): add fact-drift CI gate #3481, and Add website install/update script at codewhale.net/install.sh #3477/feat(web): publish install script #3482

Verification

• documentation-only ledger update

Notes

• No version bump, tag, release, or artifact publication.
• This ledger intentionally has no defer bucket; each item maps to a concrete completion action.

[claude]

Claude finished @Hmbown's task in 53s —— View job

---

PR Review: docs/V0865_RELEASE_LEDGER.md

• Gather context
• Review ledger content
• Post findings

---

Documentation-only change — no code, no build impact. Review criteria from the custom instructions (correctness bugs, provider-route safety, reuse, tests, security) don't apply here.

Summary

The ledger is well-structured and matches what the PR description claims: Phase 1 queue state, worktree layout, merge order, blockers, and concrete next commands. Each row has a clear completion criterion and a next action. No defer bucket, as stated.

Minor observations

1. Hardcoded local machine path (line 23)

The outer `/Users/hunter/Desktop/Harnesses/CodeWhale` directory is a harness folder...

This path is machine-specific and meaningless to any other contributor who clones the repo. If this ledger is intended only for Hunter's own coordination, that's fine — but worth noting that it leaks a local filesystem layout into committed docs.

2. Worktree table names are local directory names, not repo paths (lines 28–34)
Column 1 (CodeWhale-install-script, CodeWhale-yolo-approval, etc.) refers to local worktree directory names on Hunter's machine. A reader without that context can't act on these. Could substitute branch name + purpose without the local directory column, or add a note that these are local names.

3. PR statuses will go stale immediately
Rows like PR #3481 — Open, mergeable, CI queued will be wrong before this PR is merged. That's an inherent property of a ledger snapshot, not a defect, but it's worth flagging so the intent is clear: this is a point-in-time snapshot, not a live dashboard.

Verdict

No blockers. The structural choices (concrete completion evidence, no defer bucket, explicit commands section) are good practices for a coordination ledger. The local-path content is a minor concern for a committed doc but not a reason to block.