docs(ledger): open-PR review and Bugbot sweep

[BigSimmo]

Summary

• Appends docs/branch-review-ledger.md rows for a fresh review of every open PR after docs(ledger): record PR #1050 review disposition + live cost-readout validation #1277 merged.
• Records merge-tree classification, CI blockers, and repo pr-bugbot triage outcomes (no hosted cursor[bot] comments were present on these PRs).
• Docs-only; no product, retrieval, or provider behavior change.

Verification

• npm run check:branch-review-ledger (self-test + guard passed: 1072 records)
• Verification not run: npm run verify:pr-local — docs-only ledger append; ledger guard is the scoped check
• UI verification not run: no UI/routing/styling changes

Risk and rollout

• Risk: Low — append-only ledger bookkeeping
• Rollback: Revert this commit / close PR
• Provider or production effects: None

Notes

• Review findings live in the ledger rows and the chat summary; this PR does not mutate other PR branches.

  

[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 ↗︎.

[coderabbitai]

Warning

Review limit reached

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

Next review available in: 53 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: fc344d01-d46f-4fcb-b1f0-d1cbb489766b

📥 Commits

Reviewing files that changed from the base of the PR and between df29f31 and c92bbe8.

📒 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 cursor/open-pr-review-ledger-0687

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

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

[chatgpt-codex-connector]

You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard.
To continue using code reviews, add credits to your account and enable them for code reviews in your settings.