Reconcile 22 queued ledger requests into the canonical issue ledger

[BigSimmo]

Summary

Bookkeeping only. The serialised ledger reconciliation, run from a fresh origin/main base as the ledger contract requires. This is the only operation permitted to edit docs/outstanding-issues.md; every ordinary branch queues immutable inbox requests instead, and 22 had accumulated.

• Applied 22 requests with 4 cancellation decisions. Three of those cancellations were recorded but changed nothing, because their targets had already been applied by an earlier reconciliation. The tool reports each one explicitly, and each affected row needs a fresh update request to correct — that is deliberately not done here, because inventing corrections for other people's rows is outside a reconciliation's job. The fourth cancellation took effect.

• Three of the 22 came from the Ward Flow session that produced Correct the Ward Flow Phase 5 documents that outlived the merge, and record how to go faster #2405:

  • #BR2217 (P2) — data/outstanding-issues-snapshot.json's ledger_revision was rolled backwards by commit ca376969b, from a 2026-08-25 revision to a 2026-08-22 one, by a regenerator running from a stale base. Nothing detected it. The row asks whether the generator should refuse a backwards move, which would make the whole class self-detecting.
  • #TBW7BR (P2) — AGENTS.md still states that scripts/run-playwright.mjs "exits 0 when tests fail and when it refuses to run". It does not: 75 on admission contention, Playwright's own status on test failure, 1 on a wrapper error. The two documents corrected in Correct the Ward Flow Phase 5 documents that outlived the merge, and record how to go faster #2405 no longer say this; AGENTS.md was deliberately left for a policy-scoped change, which is what this row tracks.
  • One cancellation, of a request that would have filed "build Ward Flow Phase 5" as an open P2 task for work merged on 2026-08-26. Confirmed absent from the ledger after reconciliation.

Verification

• Verification run. Results below, each quoted from the gate.

• npm run issues:reconcile — "Applied 22 request(s); their immutable audit records are under docs/outstanding-issues-inbox/applied."

• npm run check:outstanding-issues — "in step with data/outstanding-issues-snapshot.json (98 open, 0 pending)".

• npm run check:ledger-write-discipline — "Ledger write discipline passed for a301c02572c4..HEAD."

• npx prettier --check on docs/outstanding-issues.md and data/outstanding-issues-snapshot.json — "All matched files use Prettier code style!"

• Content-verified by reading the ledger: both new rows present, and the cancelled row absent.

The snapshot was regenerated by the reconciliation tool itself, never hand-edited. Nothing outside the reconciliation transaction is staged — the 24 changed paths are the 22 requests moving into the applied archive, plus the ledger and its snapshot.

No gate was skipped, no assertion deleted, no test loosened, no tolerance lowered. No provider-backed gate was run.

Risk and rollout

Risk: low — bookkeeping records only; no runtime code, configuration, schema or product surface is touched, so no user-facing behaviour can change.

Rollback: revert the single commit. The inbox requests would return to their pending state and could be reconciled again.

One property worth a reviewer's eye: reconciliation is deliberately serialised, so this branch must not be updated from main via GitHub's "Update branch" button, and a second reconciliation must not be opened while this one is unmerged.

Clinical Governance Preflight

Completed because scripts/pr-policy.mjs classifies this change as clinicalRisk: true. The trigger is the single path data/outstanding-issues-snapshot.json, a generated bookkeeping snapshot of the issue ledger that carries no clinical content. The section is completed in full rather than waved away, because the classifier's judgement is what governs the merge.

• Source-backed claims still require linked source verification before clinical use
• No patient-identifiable document workflow was introduced or expanded without explicit governance approval
• Supabase target remains Clinical KB Database (sjrfecxgysukkwxsowpy)
• Service-role keys and private document access remain server-only
• Demo/synthetic content remains clearly separated from real clinical sources
• Source metadata, review status, and outdated/unknown-source behavior remain conservative
• Deployment classification/TGA SaMD impact was checked when clinical decision-support behavior changed

Each holds trivially: this PR moves issue-tracking records and regenerates their snapshot. No ingestion, answer-generation, retrieval, ranking, source-rendering, document-access, privacy or production-environment code is touched; no Supabase configuration changes; no key handling changes; and no clinical decision-support behaviour changes, so the SaMD classification is unaffected.

Notes

• The three no-op cancellations are surfaced rather than silently swallowed, because each leaves a ledger row that someone believed was cancelled and is not. They belong to other sessions' work, so correcting them needs their authors' intent, not a guess from here.

---

Note

Low Risk
Documentation and generated ledger bookkeeping only; no runtime, database, or product-surface changes.

Overview
Bookkeeping-only serial reconciliation: 22 queued inbox requests are applied into docs/outstanding-issues.md, archived under docs/outstanding-issues-inbox/applied, and data/outstanding-issues-snapshot.json is regenerated so counts match (98 open, 0 pending, 414 resolved).

The open ledger gains nine new rows from the batch (including Ward Flow follow-ups, Playwright strict-mode flake #V27DZ1, snapshot ledger_revision rollback #BR2217, and stale AGENTS.md / run-playwright.mjs exit-code guidance #TBW7BR). #321 and #45V4Y7 move to the resolved archive; one cancellation drops a superseded “file Ward Flow Phase 5” task after that work already merged.

No application code, config, or clinical behaviour changes—only issue-tracking records and the generated snapshot.

^{Reviewed by Cursor Bugbot for commit 6f0e6dd. Configure here.}

[coderabbitai]

Warning

Review limit reached

Next included review available in 19 minutes.

View limit details

Limit details: You’ve used the included review currently available. Your 96 included PR review attempts over the past 7 days set your current allowance at 1 review per hour.

Your organization has reached its usage spending cap. Adjust your spending cap in the billing tab.

Learn how review limits work.

Review configuration:

⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro

Run ID: 1e9e05a7-0de1-486b-8f00-d66b79dd1782

📥 Commits

Reviewing files that changed from the base of the PR and between b22639b and c913559.

⛔ Files ignored due to path filters (23)

• docs/outstanding-issues-inbox/applied/0257b988-e4dc-460d-9356-662893a7af6c.json is excluded by !docs/**
• docs/outstanding-issues-inbox/applied/1b2198c4-a52f-4302-be1c-806d91f905ac.json is excluded by !docs/**
• docs/outstanding-issues-inbox/applied/31bbefdc-0125-4b69-9ba5-f85ce916dc1a.json is excluded by !docs/**
• docs/outstanding-issues-inbox/applied/344cfd1b-b9b1-4b5a-a788-6560bfdc956e.json is excluded by !docs/**
• docs/outstanding-issues-inbox/applied/3a4868e6-281a-48c1-895b-82d6aade2bc7.json is excluded by !docs/**
• docs/outstanding-issues-inbox/applied/3eebb95f-3671-41d0-afa8-85460a9b5ff3.json is excluded by !docs/**
• docs/outstanding-issues-inbox/applied/40ff11ca-52f3-4b95-9118-5e0c107e68f0.json is excluded by !docs/**
• docs/outstanding-issues-inbox/applied/454d0cd5-8f4c-4ab9-b9b3-7b5a588283a1.json is excluded by !docs/**
• docs/outstanding-issues-inbox/applied/485bdac6-7f79-4539-9d90-347866604b35.json is excluded by !docs/**
• docs/outstanding-issues-inbox/applied/531e6569-42da-4bb6-9c0f-6a410e207aea.json is excluded by !docs/**
• docs/outstanding-issues-inbox/applied/5fa0b2ee-38ea-4a6a-bada-815b021b5aac.json is excluded by !docs/**
• docs/outstanding-issues-inbox/applied/6e929764-e281-4941-9ef4-062ec5a08497.json is excluded by !docs/**
• docs/outstanding-issues-inbox/applied/76744c9f-6e7f-4390-a202-756e50be0cd1.json is excluded by !docs/**
• docs/outstanding-issues-inbox/applied/8b2a3f89-9bdb-4fb1-8fd0-35165d050263.json is excluded by !docs/**
• docs/outstanding-issues-inbox/applied/970b4089-9e76-4bcf-821e-2e70e16a3617.json is excluded by !docs/**
• docs/outstanding-issues-inbox/applied/970bbb8b-4dbe-4e27-97a4-80142db94d7d.json is excluded by !docs/**
• docs/outstanding-issues-inbox/applied/a5dd669d-8d52-4b67-b249-51b0757a3b9f.json is excluded by !docs/**
• docs/outstanding-issues-inbox/applied/b85ad821-4c9b-4925-b86b-2d5767052b20.json is excluded by !docs/**
• docs/outstanding-issues-inbox/applied/cfa44b9c-3d68-4030-b1e3-3d8f182ca3d4.json is excluded by !docs/**
• docs/outstanding-issues-inbox/applied/d2a6122a-4fcd-4429-92a7-6004fa19eb24.json is excluded by !docs/**
• docs/outstanding-issues-inbox/applied/ecabc51d-034a-4a68-91cd-280214aac6bf.json is excluded by !docs/**
• docs/outstanding-issues-inbox/applied/f7c6371d-b92b-4050-9629-9aac5065f0a8.json is excluded by !docs/**
• docs/outstanding-issues.md is excluded by !docs/**, !**/*.md

📒 Files selected for processing (1)

• data/outstanding-issues-snapshot.json

---

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

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

[cursor]

Bugbot couldn't run - usage limit reached

Bugbot is counted against Cursor usage for this user or team, and this run hit a usage or spend limit.

A user or team admin can review and increase usage limits in the Cursor dashboard.

(requestId: serverGenReqId_71f3dcac-ad18-4511-9488-30f744c327fb)

[cursor]

Left a non-blocking comment and did not approve: Cursor Bugbot did not complete (usage limit / incomplete analysis), so this head is not eligible for automated approval. Human review is needed; no extra reviewers were assigned because the only code owner is the PR author.

_{Sent by Cursor Approval Agent: Pull Request Router and Approver}