docs(issues): reopen #343 and #318, correct stale RAG coordination state

docs/branch-review-records/a5af2f79967d97669b10f94d0894c54e4295d92811796eae62580b3a173d4e3d.record.md

@@ -0,0 +1 @@
+| 2026-08-20 | claude/ledger-reconciliation-docs-truth-b0a2e9 | 4e9e31279d16de7fcf1465b31274c47fe4d9c15a | docs/outstanding-issues.md, docs/outstanding-issues-inbox/**, docs/rag-improvement/COORDINATION.md | PR #2206 opened: reopens #343 (re-filed as #S19JRT) and #318 (reopened as #1YPV51), reconciles 4 pending ledger requests, corrects stale RAG coordination section 7 state. verify:pr-local, check:branch-review-ledger, check:ledger-write-discipline all green. | verify:pr-local,check:branch-review-ledger,check:ledger-write-discipline,format |

docs/outstanding-issues-inbox/39b3c784-e840-4308-91c2-a146f4ff5c45.json

@@ -0,0 +1,14 @@
+{
+  "version": 2,
+  "id": "39b3c784-e840-4308-91c2-a146f4ff5c45",
+  "createdOn": "2026-08-20",
+  "action": "add",
+  "payload": {
+    "pri": "P1",
+    "type": "task",
+    "summary": "Reopen #318: the medication interaction lexicon clinical review and sign-off has not actually happened; the lexicon remains clinically unreviewed",
+    "detail": "#318 was closed 2026-08-18 with outcome 'Completed Clinical Lead medication interaction lexicon review and sign-off'. The repo owner confirmed in chat on 2026-08-21 that this review and sign-off was not performed by the Clinical Lead. The medication interaction lexicon therefore remains clinically unreviewed and its sign-off block is empty, exactly as the original #318 described before its (inaccurate) closure. This must be reopened and tracked through to a genuine Clinical Lead review and sign-off; do not close again without explicit owner confirmation that the review was actually carried out. Related: #SBKXZ7 flags the same missing-attribution gap (no reviewedBy/reviewedAt) for therapy sign-off.",
+    "source": "session 2026-08-21 ledger reconciliation and docs-truth pass; owner confirmed in chat the 2026-08-18 closure was inaccurate",
+    "issueUlid": "01M0FZW46J1YPV51XHYNP4W5QS"
+  }
+}

docs/outstanding-issues-inbox/43f5e351-6a7b-4217-b4a4-897d8be9b905.json

@@ -0,0 +1,11 @@
+{
+  "version": 2,
+  "id": "43f5e351-6a7b-4217-b4a4-897d8be9b905",
+  "createdOn": "2026-08-20",
+  "action": "done",
+  "payload": {
+    "id": "#Q5JHBJ",
+    "outcome": "Closed 2026-08-20: every deliverable named in this row's own summary is complete and evidenced in its detail. The 20260818090000 schema_drift_snapshot v2 history probe was deployed in the owner-authorised production window, the first unguarded no-statements report was triaged (all fifteen versions classified), and the fail-fast guard migrations were authored and landed (six migrations, allowlist now 20 entries). Proof recorded in the row: full chain replay Applied 210/210 with CHAIN == MANIFEST, seven mutants raise and name their object, production and staging both green, and live-drift run 32251326536 reported No unexpected schema drift with all 20 history rows allowed. The row's detail already states the one residual is NOT this row's scope and is tracked separately as #M54C4N (the PGRST106 migration-history alignment step). Leaving the row in Open items made completed deployment and guard work re-dispatchable. Raised by the Codex review of PR #2206 (comment 3825543312).",
+    "baseRowFingerprint": "8ee621e4b25222d846295f592c9a875058e82d9ac994390e4841b80a9764e1be"
+  }
+}

docs/outstanding-issues-inbox/74e3183a-6e6a-49ef-9e8d-6bb329396ca6.json

@@ -0,0 +1,11 @@
+{
+  "version": 2,
+  "id": "74e3183a-6e6a-49ef-9e8d-6bb329396ca6",
+  "createdOn": "2026-08-20",
+  "action": "done",
+  "payload": {
+    "id": "#VZN8G3",
+    "outcome": "Closed as a duplicate 2026-08-20. #VZN8G3 and the earlier, still-open #BSBE9B are the same task: both require a docling-lab-fixtures.v2 corpus with unruled tables, merged/spanning cells and rotated headers, and both gate any docling table-quality promotion argument on that corpus existing. #BSBE9B is the canonical row and stays open; keeping both invites parallel implementations and conflicting closure state. The duplicate arose because inbox request a20fc4ce was queued without first checking the ledger for an existing row, and it was only visible once reconciliation allocated the id. Raised by the Codex review of PR #2206 (comment 3825543316).",
+    "baseRowFingerprint": "4d882e491bda78435ceae533c0fb5af75bd1477894dfed4e4b7f4a3176f89426"
+  }
+}

docs/outstanding-issues-inbox/b9a9492c-5cb5-4e13-8428-fbb3f70d979e.json

@@ -0,0 +1,14 @@
+{
+  "version": 2,
+  "id": "b9a9492c-5cb5-4e13-8428-fbb3f70d979e",
+  "createdOn": "2026-08-20",
+  "action": "add",
+  "payload": {
+    "pri": "P2",
+    "type": "task",
+    "summary": "Add the DB-side structural constraint backing the source_metadata pin, or document why the data-backed pin is sufficient",
+    "detail": "Re-files #343, closed 2026-08-18 with outcome 'Made retrieval row contract source_metadata schema structural and nullish' -- that outcome is false. Verified 2026-08-21: PR #2107 loosened the source_metadata pin in src/lib/rag/rag-row-contracts.ts to .nullish(); PR #2121 restored the strict .nullable()-required-key pin (git log: ce702ba68 then 4575cf57a). The comment at rag-row-contracts.ts:44-49 explicitly reads 'PR #2107 loosened it to .nullish() and this PR restores it. See docs/outstanding-issues.md #343 for the constraint-backing follow-up.' The DB-side structural constraint (check (jsonb_typeof(metadata) = 'object')) was never added: grep of supabase/schema.sql and supabase/migrations/ finds only 'metadata jsonb not null default {}::jsonb' with no jsonb_typeof check anywhere. The cancelled duplicate #ND10QT record itself states '#343, which is still open', confirming the two closures landed inconsistently. Actionable follow-up: add the check (jsonb_typeof(metadata) = 'object') constraint on documents.metadata with a fail-fast validation guard migration per AGENTS.md's guard-migration contract, or record in this row why the Zod-level pin in rag-row-contracts.ts is sufficient without a DB constraint.",
+    "source": "session 2026-08-21 ledger reconciliation and docs-truth pass",
+    "issueUlid": "01M0FZF4AJS19JRTFT15QVWGZ5"
+  }
+}