docs(issues): queue 7 ledger requests — DP6M3G resolution, #231 re-grade, 3 new recs, 2 duplicate closures - #2130
Conversation
…ade, 3 new recs, 2 duplicate closures - done #DP6M3G: packet S1b (PR #2035, merge 92f7618) landed the pre-deadline strong-route fix for medication_dose_risk; canary pair 32025082010 -> 32039841070 green. - update #231: S1/S1b/S1d landed with green canaries, closing the generation-quality false-rejection and finalizer-gap holes. Residual R4 (chronic strong-route provider_timeout on metformin-renal-dosing / valproate-pregnancy) safely degrades to extractive fallback; re-graded P1 -> P2. Remediation-plan Phase 5.2 satisfied and live-drift #316 Phase 1.2 classified all RPC divergence as attribute-only. - add: neuroleptic-side-effect-escalation canary latency advisory (20.2 s, non-blocking). - add: probe-generation-quality.ts has no answer-text capture mode, blocking a blinded Gate E read from probe output alone. - add: pointer to the RAG improvement programme board (README/HANDOVER/COORDINATION) and the open-PR check before starting RAG-surface work. - done #BTVMVK: duplicate of #342 (already closed — crawler-probe triage). - done #ND10QT: duplicate of #343 (open — carries the structural source_metadata fix; PR #2121 restored the strict pin). No canonical ledger edit here — each request is an immutable file under docs/outstanding-issues-inbox/; reconciliation applies them in a separate transaction.
You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard. |
Warning Review limit reachedYou’ve reached a temporary PR review limit under our Fair Usage Limits Policy. Next review available in:5 minutes Limit details: You’ve used all 1 included review currently available under your plan. You completed 101 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 (8)
Comment |
This pull request has been ignored for the connected project Preview Branches by Supabase. |
Uh oh!
There was an error while loading. Please reload this page.
Summary
docs/outstanding-issues-inbox/— no edit to the canonicaldocs/outstanding-issues.mdin this PR.done #DP6M3G: packet S1b (PR fix(rag): route the medication_dose_risk class to the strong route before the deadline (A1 R1, #231) #2035, merge92f7618c0) landed the pre-deadline strong-route fix formedication_dose_risk; canary pair32025082010 -> 32039841070green.update #231: S1 (fix(rag): stop verification rejecting verbatim-faithful answers (#231 S1) #2022), S1b (fix(rag): route the medication_dose_risk class to the strong route before the deadline (A1 R1, #231) #2035), S1d (fix(rag): recover fast-route final-gate source gaps extractively (packet S1d) #2054) landed with green canary pairs, closing the generation-quality false-rejection and finalizer-gap holes. Residual R4 (chronic strong-routeprovider_timeouton metformin-renal-dosing / valproate-pregnancy) safely degrades to source-backed extractive fallback, never model synthesis; re-graded P1 -> P2. Remediation-plan Phase 5.2 is satisfied and live-drift Fix answer search URL chat loading #316 Phase 1.2 classified all ten RPC divergences as attribute-only.neuroleptic-side-effect-escalationcanary latency advisory, theprobe-generation-quality.tsanswer-text capture gap, and a pointer to the RAG improvement programme board (README/HANDOVER/COORDINATION).done #BTVMVK: duplicate of DB reliability: full-inventory drift detection (check:drift), DR rehearsal, expand/contract migration policy #342 (already closed — crawler-probe triage).done #ND10QT: duplicate of Retrieval correctness: repair #325 golden regression, corpus-grounded finding #11 fix, RC9 confidence hardening #343 (open — carries the structuralsource_metadatafix; PR fix(rag): restore the strict source_metadata presence pin on retrieval rows #2121 restored the strict pin).Reconciliation is intentionally NOT included in this PR.
check:ledger-write-disciplinecompares HEAD against the merge-base withorigin/mainand requires everyapplied/entry to match an identical pending file that already existed at that base — so a brand-new request can never be reconciled in the same PR that creates it; only a request already merged intomainis eligible. That's confirmed by every prior reconcile-only commit in this repo's history (e.g.86cc82f44), which never introduces new pending files, only moves already-landed ones toapplied/. Once this PR merges, a separate fresh-base reconciliation PR applies these 7 requests (plus any other pending requests already onmain) to the canonical ledger.RAG impact: no retrieval behaviour change — ledger only.
Verification
npm run check:outstanding-issues— passed:Ledger inbox check passed: 16 pending request(s), 339 applied./Outstanding-issues guard passed: 365 rows (48 open, 317 archived), unique display and durable ids, collision-free allocation enabled, deprecated next-id marker ignored, no merge driver, no ids deleted from base 53438ae4392a.npm run check:ledger-write-discipline— passed:Ledger write discipline passed for 53438ae4392a..HEAD.npx prettier --checkon the touched files —All matched files use Prettier code style!npm run verify:pr-local/verify:ui/verify:release— this PR touches only JSON request files underdocs/outstanding-issues-inbox/, no source, test, or build-relevant paths; the two ledger-specific gates above are the smallest checks that actually cover this change.Risk and rollout
Notes
ISSUES-LIST.html) is unaffected — no canonical ledger edit occurred in this PR, so there is nothing to refresh yet. It will need a refresh after the follow-up reconciliation PR lands.