chore(worktree): raise Codex setup maxBuffer and reconcile ledger snapshot

[BigSimmo]

Summary

• Merge origin/main to clear DIRTY mergeability on PR chore(worktree): raise Codex setup maxBuffer and reconcile ledger snapshot #2400.
• Drop false caring-contacts inbox cancel/done records that claimed validateGovernedMessage / resolveClosingContactMessageBody wiring and recovery-screen integration without production callers (Codex P2 review).
• Regenerate data/outstanding-issues-snapshot.json from the post-merge inbox set.
• Raise default spawnSyncmaxBuffer to 64 MB in scripts/setup-codex-worktree.mjs to avoid ENOBUFS during large captured command output.

The earlier Medication sidebar href fix (/medications workspace, not /?mode=prescribing) landed on this branch in d29d561d0 and is retained in history; it is no longer a net diff vs current main.

Verification

• node ./node_modules/vitest/vitest.mjs run tests/caring-contacts-message-policy.test.ts tests/caring-contacts-message-copy.test.ts tests/caring-contacts-service-state.test.ts tests/sidebar-production.dom.test.tsx — 4 files, 80 passed
• npm run snapshot:issues after removing false inbox requests
• npm run format
• npm run verify:pr-local — deferred to CI for this docs/workflow-only delta

UI verification not run: no UI/routing/styling behaviour change in the remaining two-file diff vs main.

Risk and rollout

• Risk: Low — dev worktree setup buffer and generated ledger snapshot metadata only; no clinical output or dispatch behaviour changes.
• Rollback: Revert this PR; no production runtime or schema effect.
• Provider or production effects: None

Clinical Governance Preflight

• 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

Notes

Codex review threads on false ledger cancellations addressed by deleting the cancel requests instead of claiming integration that does not exist. Bugbot Medication shortcut thread addressed by d29d561d0 (href: "/medications").

[coderabbitai]

Warning

Review limit reached

Next included review available in 37 minutes.

View limit details

Limit details: You’ve used the included review currently available. Your 93 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: dbee4746-241c-4dae-acf5-e71d81a845e7

📥 Commits

Reviewing files that changed from the base of the PR and between bfa34ff and 68f212e.

📒 Files selected for processing (2)

• data/outstanding-issues-snapshot.json
• scripts/setup-codex-worktree.mjs

---

_{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]

Cursor Bugbot has reviewed your changes using default effort and found 1 potential issue.

^{Bugbot Autofix is ON. A cloud agent has been kicked off to fix the reported issue. You can view the agent here.}

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

[cursor]

Not approved: Cursor Bugbot completed as skipped and reported 1 unresolved high-severity finding that needs human review. No reviewers were assigned because the only CODEOWNER is the PR author. Human review is needed before merge.

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

[chatgpt-codex-connector]

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit:a3adb23654

ℹ️ 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".