docs(ledger): record PR #1310 as landed at squash 422e43d86

[BigSimmo]

Ledger-only closeout for #1310, which merged as squash 422e43d86.

Verified against origin/main after the merge: npm run check:branch-review-ledger PASS (1107 records before this row) and vitest tests/repo-hygiene.test.ts 25/25 PASS.

The record also captures that main ended up ahead of the authoring branch. Review tightened findReviews to compare scope exactly instead of by substring — worth recording, because the original substring match would have let a branch-cleanup-deletion-pending row satisfy a --scope branch-cleanup lookup and skip a branch that still needed cleanup. refTokens, headMatches, and resolveHead were hardened in the same pass.

One row appended to docs/branch-review-ledger.md; no code, config, or behaviour change.

🤖 Generated with Claude Code

Summary by CodeRabbit

• Documentation
  • Added a ledger entry documenting review-matching and branch verification updates.
  • Recorded successful post-merge repository hygiene checks and verification results.

[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: 3 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: da8701e3-a4a8-468d-b142-7bf89c1078f5

📥 Commits

Reviewing files that changed from the base of the PR and between 03f8730 and 12ae584.

📒 Files selected for processing (1)

• docs/branch-review-ledger.md

📝 Walkthrough

Walkthrough

The branch review ledger gains a row for PR 1310, documenting lookup and validation hardening changes and successful post-merge branch-hygiene checks.

Changes

Branch review ledger

Layer / File(s)	Summary
Add merged PR ledger entry docs/branch-review-ledger.md	Records the squash commit, stricter scope matching, corrected refTokens handling, updated headMatches rules, full-hex resolveHead validation, and verification results.

Estimated code review effort: 1 (Trivial) | ~2 minutes

🚥 Pre-merge checks | ✅ 4 | ❌ 1

❌ Failed checks (1 warning)

Check name	Status	Explanation	Resolution
Description check	⚠️ Warning	The description covers summary and verification, but it omits required template sections like risk/rollback, notes, and the checklist.	Add the template headings and fill the missing sections: Summary, Verification checklist, Risk/Rollback, Clinical Governance Preflight if applicable, and Notes.

✅ Passed checks (4 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title clearly states this PR records PR #1310 as landed in the branch review ledger.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.

---

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

[BigSimmo]

@cursor fix merge conflict

[cursor]

Merge conflict on #1325 is fixed.

GitHub marked it CONFLICTING because main had advanced with #1305 (and #1314) while this branch only appended the #1310 prlanded ledger row. I merged origin/main; the ledger’s merge=union driver kept both sides’ rows with no manual conflict resolution.

• Tip: 12ae5846
• check:branch-review-ledger PASS (1116 records)
• PR is now MERGEABLE (checks still running / BLOCKED until CI finishes)