docs: restore confirmed universal ledger tasks

[BigSimmo]

Summary

• restore three confirmed, reproducible tasks omitted when the universal ledger landed: Safety Plan privacy alignment, fail-closed answer relevance metadata, and stranded-upload recovery
• make the recommended queue contiguous and bind each restored row to stable IDs [WIP] Optimize search and ingestion performance #59-[WIP] Improve data integrity and reliability of ingestion #61
• keep the SessionStart hook from hiding a non-empty recommended queue if the open table is temporarily empty
• retain the already-merged fix: reconcile redesign and restore lint #23 P2 correction from PR issues: align scheduled diagnostics priority #1110

Verification

• npm run verify:cheap — 365 files passed; 3,242 tests passed, 1 skipped
• npm run docs:check-links — 1,143 references
• npm run docs:check-index — 42 modules/routes plus all schema tables
• npm run docs:check-scripts — 334 npm-run references
• npm run check:skills — 32 canonical skills, 8 aliases
• Bash syntax and live SessionStart execution
• structural assertions — 43 unique open IDs, 29 contiguous queue rows, no missing queue IDs, next ID 062
• Prettier and git diff --check

Risk and rollout

Documentation and read-only hook logic only. No application, database, provider, deployment, or production-data behavior changes. Roll back by reverting this PR.

Clinical Governance Preflight

No clinical output behavior changes in this PR. The ledger records future clinical/privacy work with explicit owner, verification, approval, and stop conditions. No OpenAI, Supabase, Railway, live application, deployment, or production-data workflow ran.

---

Note

Low Risk
Documentation and read-only SessionStart hook output only; no runtime product, data, or deployment behavior changes.

Overview
Re-adds #59 (Safety Plan vs privacy contract), #60 (fail-closed missing answer relevance metadata), and #61 (stranded upload without job) to docs/outstanding-issues.md, with full open rows and slots in the recommended execution queue. The queue is rebuilt to 29 contiguous orders (next ID #62), documents two parallel A1 items (#053 legal, #059 local privacy), and tightens queue rules (contiguous orders, ID sync with open items).

issues-surface.sh now treats “empty” only when both open items and the recommended queue are empty, and computes queue_total before that check so sessions still see queued work if the open table is temporarily empty.

No application, API, or database code changes—ledger and read-only hook behavior only.

^{Reviewed by Cursor Bugbot for commit bfe6179. 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: 53 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: 0f3a583f-a2e6-4fb4-a76c-4995282b6679

📥 Commits

Reviewing files that changed from the base of the PR and between a0404bf and bfe6179.

📒 Files selected for processing (2)

• .claude/hooks/issues-surface.sh
• docs/outstanding-issues.md

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch codex/ledger-post-1106-followup

---

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

[BigSimmo]

Superseded by merged PR #1112, which includes the same three confirmed ledger tasks, stable queue IDs/order, and the SessionStart empty-open guard on current main. Closing this conflicting duplicate; no additional change should be merged from this branch.