issues: reconcile the 57-request backlog into the canonical ledger

[BigSimmo]

⚠️ Read this before touching PR #2559

PR #2559 must be CLOSED, not merged. This reconcile was run with --allow-concurrent while #2559's branch was still on origin. Merging both reconciliations is precisely the canonical-ledger conflict and journal corruption that #EH9VA6 exists to prevent.

Closing it loses nothing. All 46 applied records unique to claude/issues-reconcile-2526 came from requests that were still pending on main, and this PR has now applied every one of them. I verified that by set comparison before proceeding — re-appliable: 46, NOT recoverable from main: 0 — rather than assuming it.

Summary

• Apply all 57 queued inbox requests to docs/outstanding-issues.md and regenerate data/outstanding-issues-snapshot.json.
• Close the four Caring Contacts defects whose fixes merged earlier today.
• File three loose ends surfaced by that work.

Diff shape: 57 pure renames (requests move into applied/ byte-identical, so request immutability holds) plus the canonical ledger and the generated snapshot. No request was deleted or modified.

The four closures

Each sits in Resolved / archive citing its merge commit and a fact checkable against main with one grep — not a file name:

Issue	Merged in	Evidence on main
#59JT7W	94a14a829 (#2532)	closing-message-body-not-authored ×8 in message-policy.ts
#RZVMPD	94a14a829 (#2532)	PLAN_LIST_COLUMNS ×3 in db/postgres-repository.ts
#J7PZQP	2631782a3 (#2534)	patientDetailClearedAt in episode.ts
#PAMATF	2631782a3 (#2534)	planSendingHold ×2 in model.ts

#59JT7W's row records that an earlier done request (c862828e) closed it before a fix existed. That is why these closures name commits rather than files, and why I confirmed each row's section rather than trusting the open-item count — a falling count is exactly what that earlier mistake also produced.

Why the override was used

The remote interlock refuses to reconcile while an unmerged reconcile branch exists on origin. Its own remedy is to land or close that PR — but every branch deletion from this cloud container fails (fatal: the remote end hung up unexpectedly, then Everything up-to-date; ten attempts across two branches). With deletion unavailable, the override was the only remaining route, and it was taken with the owner's explicit approval after the risk was stated twice.

Two cancellations that did nothing

1e305210 and fd9de7fe reported no effect: their targets had already been applied by an earlier reconciliation. Both are recorded as-is. Per the tool's own guidance, correcting those rows needs a fresh update request — not a retried cancel.

Verification

• npm run check:outstanding-issues — [snapshot] in step with data/outstanding-issues-snapshot.json (73 open, 0 pending)
• npm run check:ledger-write-discipline — Ledger write discipline passed for a9472efcad32..HEAD.
• npm run check:branch-review-ledger — Branch review ledger guard passed: 880 live table records + 1206 archived + 588 immutable
• npm run docs:check-links — docs link check passed: 5460 repo path references resolve.
• npx prettier --check over every changed file — All matched files use Prettier code style!
• Each of the four rows read back individually and confirmed in Resolved / archive with its SHA

Run with GATE_RECEIPTS=refresh so no cached receipt could stand in for a real run. No provider-backed gate: no eval:*, no verify:release, no check:supabase-project, no live Supabase or OpenAI test:live path.

Risk and rollout

• Risk: Low for the repository, contingent on issues: reconcile the seventeen queued ledger requests #2559 not merging. Ledger and generated snapshot only; no runtime code path is touched.
• Rollback: Revert the single commit. Requests return to pending and a later reconcile re-applies them.
• Provider or production effects: None.
• RAG impact: none

🤖 Generated with Claude Code

https://claude.ai/code/session_014X6aJ6PgN26a8XiDm4FVHF

---

Generated by Claude Code

[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: Team

Run ID: f43d516b-85bd-4cae-936a-d8c20697eb61

---

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

[chatgpt-codex-connector]

Codex Review Summary

This comment shows the latest Codex review activity on this pull request.

Review	Status	Commit	Review trigger
📝 Code Review	✅ Completed 2026-09-02T23:04:02.110422Z	1700556	Draft marked ready

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review" or "@codex security review".

Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings.

[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_c9132934-d162-4769-a1d9-7c436dc965b7)

[chatgpt-codex-connector]

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 1700556e92

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".