docs: record completed branch cleanup

[BigSimmo]

Summary

• records exact branch-cleanup classifications for the completed consolidation pass
• records verified merged/deleted refs and protected/open/patch-unique exceptions
• captures PR feat: recover privacy-minimized clinical feedback #611 Domain 1 recovery and final main synchronization

Cleanup result

• reduced local branches from 171 to 80
• reduced remote-tracking branches from 135 to 60
• left all 36 current worktrees because the remaining candidates are active, protected, open-PR, or process-referenced
• preserved externally validated dirty-worktree backups under C:\Users\joshs.codex\cleanup-backups\Database-20260713-branch-cleanup

Verification

• npm run verify:pr-local -- --dry-run --files docs/branch-review-ledger.md — selected runtime, format, lint, typecheck, and tests; build/RAG skipped
• npm exec --offline -- prettier --check docs/branch-review-ledger.md — passed
• git diff --check — passed
• exact-row audit — 329 branch-cleanup rows, zero duplicate exact records before the final snapshot
• git worktree prune --dry-run — no stale metadata
• npm run verify:cheap — runtime, action pins, sitemap, brand, type/icon scale, and lint passed; typecheck stopped because the controller's shared install lacks newly added @sentry/node and @axe-core/playwright. Clean hosted installs should provide both from the merged lockfile.

Risk / governance

• documentation-only PR; no product API, schema, clinical behavior, provider call, or live data mutation
• patch-unique and ownership-ambiguous branches remain retained and explicitly blocked from deletion
• active/open worktrees and branches remain untouched

[coderabbitai]

Warning

Review limit reached

@BigSimmo, you've reached your PR review limit, so we couldn't start this review.

Next review available in: 5 minutes

Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available.
You're only billed for reviews past your plan's rate limits ($0.25/file).

How can I continue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews.

How do review limits work?

CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability.

For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window.

Please refer docs for additional details.

Review details

⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro Plus

Run ID: b854852c-631e-419c-a4a3-2d1e61568c8e

📥 Commits

Reviewing files that changed from the base of the PR and between 4188d4c and 28232ba.

📒 Files selected for processing (1)

• docs/branch-review-ledger.md

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch codex/branch-cleanup-2026-07-13

---

_{Comment @coderabbitai help to get the list of available commands.}

[supabase]

This pull request has been ignored for the connected project sjrfecxgysukkwxsowpy because there are no changes detected in supabase directory. You can change this behaviour in Project Integrations Settings ↗︎.

---

Preview Branches by Supabase.
Learn more about Supabase Branching ↗︎.