chore(ledger): record PR #1992 CI-blocker fix review

[BigSimmo]

Summary

• Records the review that diagnosed and fixed PR Converge Therapy with shared site infrastructure #1992's four failing required checks (Static PR checks, Unit coverage, Production UI, Lighthouse budget) via npm run ledger:append. The actual code fix was pushed directly to PR Converge Therapy with shared site infrastructure #1992's own branch (codex/therapy-global-convergence-20260814 @ a3d81a6), not to this branch — see PR Converge Therapy with shared site infrastructure #1992 for that diff.
• Adds one immutable review record file under docs/branch-review-records/.

Verification

• npm run verify:pr-local

Verification not run: this is a single generated ledger-record file with no behavioural code change; npm run check:branch-review-ledger / check:ledger-write-discipline validate the ledger format and are part of verify:pr-local/CI's static checks, which will run automatically in this PR's CI.

Risk and rollout

• Risk: none — append-only documentation record, no code path touched.
• Rollback: revert this commit.
• Provider or production effects: None

Notes

• The actual CI-blocker fixes for PR Converge Therapy with shared site infrastructure #1992 (a Prettier formatting fix and a JS-regex end-anchor bug in a source-contract test) are on PR Converge Therapy with shared site infrastructure #1992's own branch, not here.

---

Generated by Claude Code

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

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: 33 minutes

Limit details: You’ve used all 1 included review currently available under your plan. You completed 93 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: 71880b3b-1f40-4345-8751-73f6f6185d33

📥 Commits

Reviewing files that changed from the base of the PR and between 4fcc6ad and 6eb7b26.

📒 Files selected for processing (1)

• docs/branch-review-records/b9fd36f90154b07043f9ea0dd6456f7bc0f6337655ee0d5e54143fab8128966b.record.md

---

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