docs(ledger): batch the review appends from #1206, #1207, #1210, #1211, #1224 and the #1192 landing

[BigSimmo]

Summary

Five open PRs change docs/branch-review-ledger.md and nothing else, contributing fifteen review records between them. This lands all fifteen in one commit so the five originals can be closed rather than each carrying its own main sync and CI cycle. A sixteenth record covers the #1192 landing, added here rather than as a seventh ledger PR.

PR	Records	Subject
#1206	2	PR #1162 CI-green and prlanded closeout
#1207	10	Bugbot/thorough review pass across #1162, #1185, #1186, #1187, #1188, #1190, #1192, #1195
#1210	1	PR #1090 prlanded outcome
#1211	1	PR #1197 Bugbot do-not-merge review
#1224	1	PR #1197 prlanded merge
—	1	PR #1192 prlanded (squash c4d5f47a39), recorded here to avoid another single-row PR

The queue cost of these five is out of proportion to sixteen lines of documentation. Each needs a main sync to become mergeable, and each sync risks the union merge driver re-appending records both sides already carry — which is exactly what blocked #1192's check:branch-review-ledger twice in one hour today, and what outstanding item #82 tracks. Batching removes five sync-and-rerun loops.

Rows from the five source PRs are copied verbatim from each PR head, then asserted byte-identical against their source after appending, so nothing is paraphrased, reordered within a PR, or lost. No existing record is edited or removed; this is a pure 16-line append.

The five source PRs are left open. Closing them is the author's call, and they can be closed as landed here once this merges.

Verification

Documentation-only change to a single file, so the source-code gates in the template do not apply. What was run:

• npm run check:branch-review-ledger — 957 records, union merge active, no conflict markers, no exact duplicates
• npm run docs:check-links — 1192 repo path references resolve
• prettier --check docs/branch-review-ledger.md — clean
• git diff origin/main...HEAD --numstat reports 16 insertions and 0 deletions, so no existing record or line ending was disturbed
• Byte-identity assertion: all 15 carried-over rows match their source PR head exactly
• Verification not run: npm run verify:pr-local and npm run verify:ui. This change cannot affect application behavior — it adds table rows to one markdown file and touches no source, test, config, or build input.

Risk and rollout

• Risk: low — additive documentation only, with no code, schema, or configuration effect
• Rollback: revert the single squash commit; the source PRs remain open and can still be merged individually
• Provider or production effects: None

Clinical Governance Preflight

Not applicable. This change touches no ingestion, answer generation, search/ranking, source rendering, document access, privacy, production environment, or clinical output surface. The Supabase target is unchanged at Clinical KB Database (sjrfecxgysukkwxsowpy).

Notes

• Every row was checked against current main first; none had already landed by another route.
• Ordering appends by source PR (docs: ledger closeout for merged PR #1162 #1206, docs(ledger): record Cursor Bugbot review of PR #1186 #1207, docs: record PR #1090 prlanded outcome in branch review ledger #1210, docs: ledger PR #1197 Bugbot do-not-merge review #1211, docs: ledger prlanded merge for PR #1197 #1224) and preserving each PR's internal order keeps the records readable against the originals.

  

[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, you can upgrade your account or add credits to your account and enable them for code reviews in your settings.

[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: 11 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: a71aa544-8268-4d24-a365-bc00e121d142

📥 Commits

Reviewing files that changed from the base of the PR and between c4d5f47 and 33624fa.

📒 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/batch-ledger-appends-4fd7

---

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.}