docs(ledger): reconcile 15 inbox requests and archive resolved issues

[BigSimmo]

Summary

Reconciles 15 pending inbox requests into \docs/outstanding-issues.md\ and regenerates \data/outstanding-issues-snapshot.json:

• Archives 13 resolved tasks from Bundle 1 (PR clinical(governance): resolve forms permissions, test guards, and alert tiers (Bundle 1) #2763):
  • #97W4FD: Clinical test guard patterns in pr-policy.mjs
  • #H0HKFD: ACMA fictional phone numbers in care-plan mockup fixtures
  • #8KFQ3X, #YJGWDZ, #W1B9RP: Forms PDF /P permissions decoding & UI distinction
  • #GNNMAF: Patient alert info tier unread gates routing to unassessedAdvisory
  • #H3PXP0: Outdated status reset upon clinical re-verification
  • #0JGJTK: Calculator mockups directive copy removal
  • #Y2E4DX: Hepatic none recognition in isProfileEmpty
  • #WM4DNW: Differential records validation_status derivation
  • #ZV7H8Q: Negative veto regex on substring matches
  • #E8ARD5: Authored source deny rationales in medication lexicon
  • #7ZA9S9: Formulation strength parsing on multi-strength products
• Applies 2 new tasks queued from PR Specifiers builder: correct the one-of mapping, and show each option's review status #2726 (specifiers).
• Moves 15 applied inbox requests to \docs/outstanding-issues-inbox/applied/.
• Regenerates \data/outstanding-issues-snapshot.json\ (91 open, 0 pending).

Verification Evidence

• 
  pm run check:outstanding-issues: Passed (0 pending, 91 open, 538 archived)
• 
  ode scripts/check-ledger-write-discipline.mjs: Passed for base 0c3e217

---

Note

Low Risk
Documentation and ledger metadata only; no runtime, auth, or data-path changes in the diff shown.

Overview
Refreshes data/outstanding-issues-snapshot.json after ledger reconciliation: ledger_revision moves to a new SHA, open drops 102 → 91, pending → 0, and resolved rises 525 → 538 (P2/P3 open counts tick down accordingly).

The snapshot drops thirteen previously open rows that Bundle 1 / PR #2763 closed (clinical governance preflight gaps, forms PDF handling, medication/differential governance, calculator mockup copy, care-plan phone fixtures, lexicon deny rationales, and similar follow-ups from earlier PRs). It adds two new open tasks from PR #2726: specifier one-of group labels needing psychiatrist review (#FYSQGK, P3) and DSM-5-TR specifier catalogue sign-off across 585 items (#Z3GZ5P, P2).

No application or test code changes appear in this diff—only the generated ledger snapshot content and counts.

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

[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]

Important

• 🔍 Trigger review

This repository does not receive automatic reviews because it has fewer than 10 stars.

⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Advanced

Run ID: 248fd788-78cc-4ffb-b5f6-c6b408611bf6

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

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

[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_4bdd75e8-ec1f-4f23-b39c-1cd9be63e6f5)

[BigSimmo]

PR Helper unblock + adversarial review

Actions (isolated /workspace/pr-2770):

• Static PR checks had failed check:ledger-write-discipline (partial base-inbox reconcile left 14 pending).
• Finished the batch: applied remaining inbox requests, then rebuilt docs/outstanding-issues.md as one audited applyRequestBatch from merge-base so sibling cancel requests correctly suppress two done targets.
• Regenerated snapshot; verified LEDGER_WRITE_BASE_SHA=<merge-base> npm run check:ledger-write-discipline pass.
• Pushed to PR head only (no force). Did not merge. Left existing user-owned auto-merge untouched (not enabled/disabled by this helper).

Adversarial verdict — GO_WITH_CAVEATS

• Ledger reconcile + archive only; write-discipline now matches full base batch.
• Caveats: (1) sequencing vs Make the outstanding-issues snapshot merge-safe (v2), and record the measured assessment of two other rows #2735 snapshot v2 — update/regenerate the loser after the winner lands; (2) wait for required CI green on the new head before Chief merge.

The PR was not merged. Final merge is left to the user.

[BigSimmo]

Adversarial review (ledger reconcile)

Head: 7516a68d2aef2ff0efd82169a09d5aa6b93c4578
Mergeable: MERGEABLE (0 behind main).
Required-focus CI: PR policy / Static PR checks / Safety and config / Build SUCCESS. Unit coverage still in progress at comment time. Batch reconcile cancel ignored.

Evidence

• Ledger + snapshot + inbox applied/archive only. Snapshot is still v1 shape (sha + ISO timestamp; open=81 / pending=0 / resolved=548).
• No runtime, authz, or RAG surface.

Verdict: GO_WITH_CAVEATS

Same sequencing caveat vs #2735 snapshot v2: land one first, then update-branch + regenerate the other. Do not land both blind. Chief ping after Unit coverage and PR required are green on this exact head.

The PR was not merged. Final merge is left to the user.