docs(issues): reconcile 28 inbox requests into the outstanding-issues ledger

[BigSimmo]

Summary

Supersedes #2032, which is now stale and should be closed in favor of this PR (see below for why).

• Ran npm run issues:reconcile to apply the currently-pending immutable inbox requests into the canonical docs/outstanding-issues.md ledger. This is the one deliberately serialized fresh-base branch that is allowed to edit that file directly.
• Processed requests are moved to docs/outstanding-issues-inbox/applied/ as an immutable audit trail (standard reconcile behavior).
• Recorded the review with npm run ledger:append as a separate immutable record file.
• No source, test, or script code touched — docs-only.

Why this supersedes #2032

#2032 was opened against main at 78fe906b8, reconciling the 22 requests pending at that time (queued by PR #2023/#2024). While it was open, 6 more requests landed on main from other merged PRs (3 cancellations, 2 updates, 1 done). check:ledger-write-discipline correctly rejected #2032's transaction as partial once main advanced, because it now covered only part of the currently-pending inbox.

Per this repo's own documented process (docs/database-remediation-playbook.md, "Never merge main into a PR that carries a reconciliation — it turns a complete transaction into a partial one and the guard correctly rejects it"), the fix is not to patch #2032 in place — I verified empirically that merging main into #2032's branch and re-reconciling actively fails (refusing to reconcile: #212 is stale, because two of the newly-landed cancellations target rows #2032's first pass had already resolved differently). Instead this PR restarts the reconciliation from a fresh origin/main (f5b0932914eb) and processes the complete current pending batch — 28 requests — as one clean transaction.

New/updated rows from the originally-requested set (unchanged from #2032; deterministic IDs)

• #212 — corrected (unsafe-cast/JSON.parse remediation status)
• #J912J9 — new, P1: governance question on fabricated similarity: 1 on document-summary rows
• #DP6M3G — new, P1: R1, unbudgeted strong escalation / lithium dosing route (packet S1b)
• #6BG9X2 — new, P2: R2 + R3, claim-support strictness on verbatim-faithful restatements (packet S1c)
• #BTVMVK — new, P2: recurring Sentry "Unhandled server request error" on /api/search
• #ND10QT — new, P3: source_metadata pin in rag-row-contracts.ts is data-backed only
• #TYJ0XP — new, P3: eval-canary.yml is post-merge only — record in docs/rag-behaviour
• #0MSNT8 — new, P3: G1 implementation (governance Option B, similarity_origin: document_context)

Plus the 6 additional requests that landed on main mid-session (3 cancel, 2 update, 1 done — see the applied inbox records for full detail).

Verification

• npm run check:outstanding-issues — Outstanding-issues guard passed: 348 rows (97 open, 251 archived), unique display and durable ids, collision-free allocation enabled, deprecated next-id marker ignored, no merge driver, no ids deleted from base f5b0932914eb.
• npm run check:ledger-write-discipline (run locally against LEDGER_WRITE_BASE_SHA=$(git merge-base origin/main HEAD), matching CI's computation) — Ledger write discipline passed for f5b0932914eb..HEAD.
• Verification not run: npm run verify:pr-local / verify:cheap — this diff touches only docs/outstanding-issues.md and JSON inbox request files (a data move, not source/test/config), fully covered by the two ledger-specific gates above.
• npm run format was run; the reconciled docs/outstanding-issues.md was already Prettier-clean (no diff). Unrelated pre-existing drift elsewhere in the tree was reverted to keep this PR docs/ledger-only.
• UI verification not run: no UI/frontend/routing/styling code changed.

Risk and rollout

• Risk: Low. Mechanical ledger-reconcile transaction (ID allocation + markdown table update), not a behavior change. check:ledger-write-discipline verifies the canonical-ledger diff exactly equals the recorded reconciliation transaction.
• Rollback: Revert this commit; the immutable inbox request files remain available under docs/outstanding-issues-inbox/applied/ for re-reconciliation if needed.
• Provider or production effects: None.

Notes

RAG impact: no retrieval behaviour change — ledger reconcile only (docs-only edit to docs/outstanding-issues.md and its inbox; no src/lib/rag/** or retrieval/ranking/eval surface touched).

---

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