Record ledger entry for PR #2009 direct-push conflict fix

[BigSimmo]

Summary

• Records an immutable review-ledger entry for the follow-up fix to PR Add outstanding-issues row-staleness fingerprint checks #2009: after the first fix (PR Resolve merge conflicts + review fixes for PR #2009 #2018, squash-merged) drifted again because squash-merge doesn't preserve an ancestor link to main, I pushed a real (non-squashed) merge commit directly onto PR Add outstanding-issues row-staleness fingerprint checks #2009's own branch (codex/account-setup-polish-20260814). main is now a true git ancestor of that branch, so mergeable_state moved from dirty to behind (a trivial one-commit lag, not a conflict), and PR mergeability/PR policy checks are green with full CI now running on PR Add outstanding-issues row-staleness fingerprint checks #2009 for the first time.
• No product code changes — this PR only adds docs/branch-review-records/75a51e7413c063ecd1a7ac074cba09c119cb4ef8c5318bfdde5f7836b4143d9e.record.md.

Verification

• npx prettier --check on the new record file — passed

• Not applicable: this is a documentation-only ledger record with no executable behavior change.

• npm run verify:pr-local — not run; this is a single append-only immutable ledger record file (the format this repo's own tooling generates via npm run ledger:append), not source/config/test code, so the smallest correct gate is the format check above.

Risk and rollout

• Risk: None — documentation/ledger metadata only.
• Rollback: revert this commit; it doesn't affect any runtime behavior.
• Provider or production effects: None.

Notes

• Related: PR Resolve merge conflicts + review fixes for PR #2009 #2018 (merged) and PR Add outstanding-issues row-staleness fingerprint checks #2009 (open, now unblocked).

---

Generated by Claude Code

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

[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: 14 minutes

Limit details: You’ve used all 1 included review currently available under your plan. You completed 94 included PR reviews in the past 7 days; at that activity level, included reviews refill at 1 review per hour.

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: 70ac1bcb-229e-48a9-bce5-ead8e9b07879

📥 Commits

Reviewing files that changed from the base of the PR and between 4ffc59f and 708de38.

📒 Files selected for processing (1)

• docs/branch-review-records/75a51e7413c063ecd1a7ac074cba09c119cb4ef8c5318bfdde5f7836b4143d9e.record.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 ↗︎.