issues: complete universal recommended queue

[BigSimmo]

Summary

• repair the landed universal ledger so every queued recommendation points to the correct durable open item
• add seven still-recommended tasks omitted by the competing ledger merge, including credential containment, Safety Plan privacy, fail-closed relevance, stranded-upload recovery, the preserved contrast patch, the explicitly paused document accordion, and the conditional Current Clinical Work brief
• retain PR issues: align scheduled diagnostics priority #1110's #023 P2 correction and keep provider actions approval-gated

Validation

• ledger invariants: 35 contiguous ordered tasks, 47 unique open rows, all queued IDs tracked, next ID 66
• SessionStart hook syntax and live execution: passed
• npm run docs:check-links: passed (1,144 references)
• npm run docs:check-index: passed
• npm run check:skills: passed
• Prettier and git diff --check: passed

Risk

Documentation-only task-memory correction. No application code, migrations, provider configuration, secrets, production data, or deployment behavior changes.

RAG impact: no retrieval behaviour change — task-ledger documentation only.

---

Note

Low Risk
Documentation-only ledger repair in docs/outstanding-issues.md; no runtime, secrets, or application behavior changes.

Overview
Repairs docs/outstanding-issues.md so the recommended execution queue and open-items table stay aligned after a competing ledger merge.

A1 now explicitly covers credential containment, the Safety Plan privacy contract, and the legal/privacy package. The queue grows to 35 ordered rows with new top priorities #059 (exposed-credential containment), #060 (Safety Plan vs privacy notice/PIA), and #061 (fail-closed answer relevance), plus dependency links (e.g. #052 after #061, #062 stranded-upload recovery after #052). Previously omitted work is queued: #063 contrast/browser patch, #064 paused document accordion, #035, #039, and #065 (Current Clinical Work brief).

Adds seven open rows (#059–#065) with outcomes, gates, and stop conditions; expands #054 reconciliation wording; bumps issues:next-id to 066.

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

[coderabbitai]

Warning

Review limit reached

@BigSimmo, you've reached your PR review limit, so we couldn't start this review.

Next review available in: 57 minutes

Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available.
You're only billed for reviews past your plan's rate limits ($0.25/file).

How can I continue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews.

How do review limits work?

CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability.

For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window.

Please refer docs for additional details.

Review details

⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro Plus

Run ID: 3c8f5aae-d0d3-47b3-ab93-8bfa9957c36b

📥 Commits

Reviewing files that changed from the base of the PR and between 527988c and 6401aeb.

📒 Files selected for processing (1)

• docs/outstanding-issues.md

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch codex/ledger-security-containment-5f27

---

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

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

[chatgpt-codex-connector]

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 6401aeb899

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

[chatgpt-codex-connector]

Make paused worktree references recoverable

Rows #63 and #64 add recommended P2 work that depends on agent/formulation-disabled-contrast and codex/chat-document-text-accordion-7cb4, but those identifiers are not present in the local refs, registered worktrees, stash, or any repo file except this ledger row (checked with rg, git for-each-ref, git worktree list, and git stash list). When /issues surfaces this as durable cross-session work, the next operator has no recoverable patch to rebase and can only stall or recreate/lose the preserved work; please commit/export the patch or replace these rows with a concrete durable source.

AGENTS.md reference: AGENTS.md:L453-L460

Useful? React with 👍 / 👎.

[BigSimmo]

Superseded by the completed universal-ledger reconciliation in #1112 and the preserved UI follow-up merged in #1116. Current origin/main contains the active queue and IDs #59-#65.