chore: safe branch cleanup — delete empty remotes, close #108, review audit batch

[BigSimmo]

Summary

• Deleted five superseded remote branches after content proof:
  • #108 empty-diff trio: codex/document-reader-condensed-view, cursor/page-anchored-search-composer-30ee, cursor/pr-1379-babysit-ledger-9365
  • Obsolete: circleci-project-setup (CircleCI removed in chore: remove CircleCI from repo #1412)
  • Superseded: execute-audit-code-remediation (PR feat: implement document subsystem audit recommendations #1162 merged; unique ledger row already on main)
• Archived #108 in docs/outstanding-issues.md
• Reviewed a bounded batch of 10 audit/remediation remotes: 2 rejected+deleted, 8 retained with unique content still differing from main; recorded branch-cleanup ledger rows for each

Verification

• npm run check:outstanding-issues — passed (120 rows, 57 open / 63 archived)
• npm run check:branch-review-ledger — passed (1306 records)
• npm run format before push
• node scripts/reconciliation-preflight.mjs — 1 worktree, 0 dirty
• npm run sweep:branch-ledger -- --no-fetch — 5 deleted refs gone; 0 automatic deletion candidates among remaining
• npm run branch:cleanup — no merged local branches
• Verification not run: npm run verify:pr-local — docs-only ledger/issues change; domain checks above cover the touched surfaces
• UI verification not run: no UI/routing/styling changes

Risk and rollout

• Risk: Low — documentation/ledger only; remote ref deletions already applied on GitHub for five empty/obsolete branches
• Rollback: Restore deleted refs from recorded SHAs in #108 / ledger rows if needed; revert this PR for doc/ledger text
• Provider or production effects: None (GitHub ref deletes only; no app/runtime change)

Notes

• This cloud checkout had no dirty worktrees to clean (#079 multi-worktree farm is operator-local)
• Open PR heads preserved (cursor/ledger-merge-dedupe-ad64, cursor/ci-hygiene-gates-1bf5, and others)
• Stopped after one batch of 10 per the cleanup guide; remaining remotes with unique content were not mass-deleted

  

[coderabbitai]

Warning

Review limit reached

You’ve reached a temporary PR review limit under our Fair Usage Limits Policy.

Your recent review volume is higher than typical usage, so adaptive limits are currently applied.

Next review available in: 5 minutes

Your organization has reached its usage spending cap. Adjust your spending cap in the billing tab.

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

Run ID: d81c52e7-e26a-4b11-9d6f-7d554f498a45

📥 Commits

Reviewing files that changed from the base of the PR and between 0173afa and 92a78af.

📒 Files selected for processing (2)

• docs/branch-review-ledger.md
• docs/outstanding-issues.md

---

_{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 ↗︎.

[chatgpt-codex-connector]

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: adca2ab55b

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".