docs(ledger): record PR #1050 review disposition + live cost-readout validation

[BigSimmo]

Summary

• Appends the missing docs/branch-review-ledger.md row for PR fix(eval): cost readout counts zero-usage cases as $0 + follow-up ledger capture #1050 (eval cost-readout fix + issues-ledger capture, merged 2026-07-22 as squash 9fb9bc7). The row was omitted at merge time; this is the ride-along mandated by the 2026-07-26 scheduled-runs reader procedure.
• The row records: the converged Codex P2 / CodeRabbit Major finding (provider-attempted cases must stay n/a, not $0) and its fix in eb1046b, the docs(issues): close #008 as false-positive; fix #014 broken doc path #1049 concurrent ID-collision reconciliation (Bump @types/react from 19.2.16 to 19.2.17 #18–fix: reconcile redesign and restore lint #23, next-id 024), and the two subsequent live validations of the cost readout — merged-main canary 30018289898 (2026-07-23) and scheduled run 30216191889 (2026-07-26, Estimated cost USD 0.235936; 9 priced + 35 provably-zero-cost cases, no n/a), which archived issue Bump eslint from 9.39.4 to 10.4.1 #20.

Verification

• npm run check:branch-review-ledger — self-test + guard pass (1049 table records, no conflict markers or duplicates)
• npx prettier --check docs/branch-review-ledger.md — pass

Verification not run: npm run verify:pr-local — single append-only row in one Markdown ledger file; the ledger integrity guard and formatter above are the checks that gate this file in CI, and no source, test, config, or dependency path is touched.

Risk and rollout

• Risk: none beyond documentation — append-only row in the review ledger; no source, dependency, workflow, or clinical surface touched.
• Rollback: plain revert of the single commit.
• Provider or production effects: None (row content cites already-completed hosted runs read from logs; no dispatch or spend).

Clinical Governance Preflight

Not applicable — documentation-only ledger row; no ingestion, answer generation, search/ranking, source rendering, document access, privacy, production env, or clinical output change.

Notes

• The 2026-07-26 scheduled eval-canary (30216191889) was green across all gates; the scheduled CI run (30216361999) failed at the production npm audit step on the brace-expansionGHSA-mh99-v99m-4gvg chain, which skipped the weekly Firefox/WebKit matrix. Per outstanding-issues Improve data integrity and reliability of ingestion #55/fix: reconcile redesign and restore lint #23, the already-open dependabot PR chore(deps): bump the npm-production group with 7 updates #1268 (npm-production group) owns that upgrade — deliberately not duplicated here.

---

Generated by Claude Code

[coderabbitai]

Warning

Review limit reached

@BigSimmo, you've reached your PR review limit, so we couldn't start this review.

Next review available in:58 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: 6b07e204-6b11-4007-b677-f1ebbc91baee

📥 Commits

Reviewing files that changed from the base of the PR and between b3c5e18 and 45ca3e1.

📒 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 claude/clinical-kb-pwa-review-asi3wb

---

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

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