docs(issues): reconcile 31 queued ledger requests after PRs #2107 and #2127–#2131 - #2138
Conversation
-#2131 One fresh-base issues:reconcile over the complete pending inbox (31 requests). Closes #DP6M3G (S1b landed), #SDQSFD (#2127), #TYJ0XP (#2128); re-grades #231 to P2 with the R4 residual and Phase 5.2 cross-link; cancels duplicates #BTVMVK (of closed#342) and #ND10QT (of #343); adds the RAG programme pointer, the neuroleptic latency advisory, the probe answer-text gap, and the non-RAG captures queued since #2119. Visual register refreshed. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard. |
This pull request has been ignored for the connected project Preview Branches by Supabase. |
Warning Review limit reachedYou’ve reached a temporary PR review limit under our Fair Usage Limits Policy. Next review available in:47 minutes Limit details: You’ve used all 1 included review currently available under your plan. You completed 102 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 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 configurationConfiguration used: Path: .coderabbit.yaml Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (33)
Comment |
Uh oh!
There was an error while loading. Please reload this page.
Summary
npm run issues:reconcileover the complete pending inbox: 31 requests applied,0 pending / 370 appliedafterwards. Open rows 104 → 44 (many closures were the 15 "delivered resolutions" queued by feat(ledger): record 15 delivered resolutions, harden operator runbooks, and relax source metadata schema #2107 plus the RAG-programme closures below).#DP6M3G(R1 landed as S1b fix(rag): route the medication_dose_risk class to the strong route before the deadline (A1 R1, #231) #2035),#SDQSFD(fix(ci): route src/lib/rag/** to the offline RAG eval gates in change-scope classification #2127),#TYJ0XP(docs(rag): document the eval-canary pair protocol's dispatch-only trigger and two canary-reading lessons #2128); re-grades#231to P2 with the R4 residual and the Phase 5.2 cross-link; cancels duplicates#BTVMVK(of closedDB reliability: full-inventory drift detection (check:drift), DR rehearsal, expand/contract migration policy #342) and#ND10QT(of Retrieval correctness: repair #325 golden regression, corpus-grounded finding #11 fix, RC9 confidence hardening #343); adds the programme pointer (#GKFK9V), the neuroleptic latency advisory (#VKH7N1), and the probe answer-text gap (#E0N0QC). Visual register refreshed (ISSUES_LIST_UPDATED).RAG impact: no retrieval behaviour change — ledger only.
Verification
npm run check:outstanding-issues—Ledger inbox check passed: 0 pending request(s), 370 applied.·Outstanding-issues guard passed: 378 rows (44 open, 334 archived) … no ids deleted from base bc73e73706df.npm run check:ledger-write-discipline—Ledger write discipline passed for bc73e73706df..HEAD.npm run verify:pr-local -- --files <all changed>docs scope —failed: (none).Risk and rollout
Notes
#343was closed by a feat(ledger): record 15 delivered resolutions, harden operator runbooks, and relax source metadata schema #2107 request stating "Made retrieval row contract source_metadata schema structural and nullish". That is not what happened: feat(ledger): record 15 delivered resolutions, harden operator runbooks, and relax source metadata schema #2107 loosened the pin to.nullish()and PR fix(rag): restore the strict source_metadata presence pin on retrieval rows #2121 restored.nullable(); the structural half (acheck (jsonb_typeof(metadata)='object')constraint) is still not done. Recommend re-adding as a new row in the next batch, or reopening if the owner prefers.#318(P1, medication interaction lexicon never clinically reviewed) was closed by a feat(ledger): record 15 delivered resolutions, harden operator runbooks, and relax source metadata schema #2107 request stating "Completed Clinical Lead medication interaction lexicon review and sign-off". That is a clinical governance sign-off; the owner should confirm it was actually performed by them before this closure stands. Applied as queued because feat(ledger): record 15 delivered resolutions, harden operator runbooks, and relax source metadata schema #2107 was owner-merged; flagged rather than overridden.f6a97c212underdocs/branch-review-records/.Opened by the RAG programme coordinator chat (Claude Code).