docs(issues): reconcile 28 queued ledger requests after PRs #2023–#2037 (closes #212 row; supersedes #2032)

[BigSimmo]

Summary

• One fresh-base npm run issues:reconcile over the complete pending inbox: 28 requests applied, 3 cancellation decisions, 0 pending / 217 applied afterwards. Immutable audit records moved to docs/outstanding-issues-inbox/applied/.
• Closes fix(supabase): make GUC-set migration hosted-safe; neutralize obsolete N+1 migration #212 (four-tranche row-contract sweep complete at T4 PR harden(worker): validate claimed job rows and enrichment read-backs against Zod row contracts (#212 T4) #2037) and adds the RAG-programme rows queued by PRs harden(api): validate inbound DB and RPC payloads against Zod row contracts #2023/docs: coordination-chat handover for the RAG improvement programme #2024/fix(rag): route the medication_dose_risk class to the strong route before the deadline (A1 R1, #231) #2035/feat(rag): adversarial fixture contract, validator, baseline record and data-flow register (packet S4 / B0) #2036/harden(worker): validate claimed job rows and enrichment read-backs against Zod row contracts (#212 T4) #2037: R1 pre-deadline strong routing (P1), R2+R3 claim-support strictness (P2), Sentry search-route unhandled error (P2), the document-summary governance question (P1) with its Option B implementation task (P3), the eval-canary post-merge-only protocol note (P3), and the source_metadata data-backed pin (P3).
• Marks HANDOVER §2 rows S4 (feat(rag): adversarial fixture contract, validator, baseline record and data-flow register (packet S4 / B0) #2036, squash f5b093291) and fix(supabase): make GUC-set migration hosted-safe; neutralize obsolete N+1 migration #212 T4 (harden(worker): validate claimed job rows and enrichment read-backs against Zod row contracts (#212 T4) #2037, squash 1726537b7) as merged — the workers wrote them pre-merge.
• Visual register refreshed: ISSUES_LIST_UPDATED path=C:\Users\joshs\OneDrive\ISSUES-LIST.html (90 issues).
• Supersedes PR docs(issues): reconcile inbox requests from PR #2023/#2024 #2032, which reconciled against an older base and failed check:ledger-write-discipline with reconciliation moved only part of the base inbox and left 6 request(s) pending. Reconcile must be a single fresh-base transaction, so this is a new branch off f5b093291, not a merge-and-rerun.

RAG impact: no retrieval behaviour change — ledger reconcile and status-row documentation only.

Verification

• npm run check:outstanding-issues — Ledger inbox check passed: 0 pending request(s), 217 applied. · Outstanding-issues guard passed: 348 rows (97 open, 251 archived) … no ids deleted from base f5b0932914eb.
• npm run check:ledger-write-discipline — Ledger write discipline passed for f5b0932914eb..HEAD.
• npm run verify:pr-local -- --files <all changed> docs scope — completed: check:runtime, check:installed-lock-parity, format:changed, sitemap:check, docs:check-index, docs:check-inventory, docs:check-scripts, docs:check-links, check:branch-review-ledger, check:outstanding-issues, check:ledger-write-discipline — failed: (none).
• UI verification not run: no UI change. Provider-backed evaluation not run: no runtime change.

Risk and rollout

• Risk: minimal — canonical ledger transaction plus docs. Do not use GitHub's "Update branch" on this PR; if main gains new inbox requests before merge, close this and re-run one fresh reconcile.
• Rollback: revert the squash commit.
• Provider or production effects: None

Notes

• Ledger record: docs/branch-review-records/…record.md for head b849065dd.

---

Opened by the RAG programme coordinator chat (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.

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

[coderabbitai]

Caution

Review failed

An error occurred during the review process. Please try again later.

---

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

[BigSimmo]

Superseded by #2045 (reconcile landed there; inbox is now 0 pending on main). Its HANDOVER row fixes move to the D2 docs PR.

[BigSimmo]

Superseded by #2045 (reconcile landed there; inbox is now 0 pending on main). Its HANDOVER row fixes move to the D2 docs PR.

[BigSimmo]

Flagging before this merges: main already contains an identical reconciliation via #2045 ("docs(issues): reconcile 28 inbox requests into the outstanding-issues ledger"), merged as 14421fba. docs/outstanding-issues-inbox/ on main is now empty (only README.md and applied/), so this PR's own 28-request reconcile transaction is now redundant against the same base content #2045 already applied.

This PR's own body says: "Do not use GitHub's 'Update branch' on this PR; if main gains new inbox requests before merge, close this and re-run one fresh reconcile." That's effectively what happened here, just via a different PR doing the same reconcile rather than new pending requests landing — so per that same instruction, recommend closing this PR as superseded by #2045 rather than merging or syncing it (merging now risks double-applying or conflicting with the already-landed ledger transaction). Leaving it to a human to close since this session doesn't close PRs.

---

Generated by Claude Code

[BigSimmo]

Superseded by #2045 (reconcile landed there; inbox 0 pending on main). HANDOVER row fixes moved to #2048/#2061.

[BigSimmo]

Superseded by #2045 (reconcile landed there; inbox 0 pending on main). HANDOVER row fixes moved to #2048/#2061.