docs(ledger): record PR #1381 CI triage closeout

[BigSimmo]

Summary

• Append one docs/branch-review-ledger.md row for the completed PR Refine document top bar and actions sheet #1381 CI triage after squash-merge.
• No product, test, or config changes.

Verification

• npm run ledger:append wrote a single append-only row
• git diff --check
• Hosted CI on this docs-only PR (pending)

Risk and rollout

• Risk: None (append-only ledger documentation).
• Rollback: Revert this commit.
• Provider or production effects: None.

Clinical Governance Preflight

• Source-backed claims still require linked source verification before clinical use
• No patient-identifiable document workflow was introduced or expanded
• Supabase target and environment configuration are unchanged
• Service-role keys and private document access remain server-only and unchanged
• Demo/synthetic content separation is unchanged
• Source metadata, review status, and outdated/unknown-source behavior are unchanged
• No clinical decision-support or TGA SaMD behavior changed

Notes

RAG impact: no retrieval behaviour change — ledger documentation only.

[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

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:16 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: b2062db1-e76c-4a0f-94b8-a031cc6a92fd

📥 Commits

Reviewing files that changed from the base of the PR and between 7422900 and d73a142.

📒 Files selected for processing (1)

• docs/branch-review-ledger.md

---

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