docs(ledger): Run PR sweep records (2026-08-08)

[BigSimmo]

Summary

• Append superseding Run PR sweep ledger rows for open PRs touched in this maintenance pass (main syncs, CI fixes, and review-thread code fixes).
• No product/runtime behaviour change; ledger-only documentation of the sweep.

Test plan

• npm run check:branch-review-ledger
• npm run ledger:dedupe

RAG impact: no retrieval behaviour change — docs/ledger only.

[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:28 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: 1f4b8c6b-f565-464b-8c74-d6b8d904473f

📥 Commits

Reviewing files that changed from the base of the PR and between 7dd5540 and 6efe25b.

📒 Files selected for processing (1)

• docs/branch-review-ledger.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:e2952044da

ℹ️ 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".

[chatgpt-codex-connector]

Mark later sweep rows as superseding

When these post-merge CI fixes are recorded as later sweeps, both rows repeat the unchanged Run PR sweep: CI fix + threads + drift scope for PRs already recorded at lines 758 and 760. The repository requires one Run PR row per PR per sweep and a superseding record for a later sweep; leaving these unqualified creates stacked records with no authoritative correction chain, undermining review throttling and ledger auditing. Record each later outcome with a distinct superseding scope and verify by looking up both branch refs across this commit.

AGENTS.md reference: AGENTS.md:L147-L147

Useful? React with 👍 / 👎.