docs: finalize universal repository task ledger

[BigSimmo]

Summary

• reconcile the universal ledger onto current main after PR docs: make outstanding issues the universal task ledger #1106 superseded the older PR docs: activate universal repository task ledger #1109 structure
• preserve PR docs: make outstanding issues the universal task ledger #1106 and PR issues: align scheduled diagnostics priority #1110 task IDs/priorities while carrying forward only non-duplicate recommended work
• make credential containment the first A1 item without storing the exposed value
• add the Safety Plan privacy contract, absent-relevance fail-closed rule, stranded-upload recovery, threshold-conflict design, catalogue-toolbar convergence, and Current Clinical Work brief
• keep all 33 recommended rows backed by durable open IDs and archive the stale Clean stale frontend identity and CSS #14/chore(deps): bump pdfkit from 0.19.0 to 0.19.1 #34 claims
• keep the SessionStart recommended queue visible even when the wider open table is empty

Validation

• Bash syntax and live SessionStart execution — passed
• empty-open regression fixture — passed (one recommended row remained visible with zero open rows)
• ledger invariant — passed (33 contiguous recommendations; 43 open items; all queue IDs tracked and unique)
• npm run docs:check-links — passed (1,140 references)
• npm run docs:check-index — passed (42 modules/routes and all schema tables)
• npm run docs:check-scripts — passed (334 npm script references)
• npm run check:skills — passed (32 canonical skills, 8 aliases)
• Prettier, git diff --check, and changed-file credential-pattern scan — passed
• verify:cheap — not run: this isolated worktree has no dependency installation; hosted clean-install checks are required before merge

Risk and rollback

Low risk: repository documentation and the read-only SessionStart hook only. No runtime application code, migrations, provider configuration, credential values, production data, or deployments are changed. Roll back by reverting the merge commit.

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

Clinical governance preflight: not applicable; this records future work but changes no ingestion, answer generation, search/ranking, source rendering, access, privacy implementation, production environment, or clinical output behavior.

---

Note

Low Risk
Documentation and a read-only SessionStart hook only; no application runtime, migrations, or provider changes.

Overview
Reconciles docs/outstanding-issues.md onto current main after PR #1106 superseded the older ledger structure: 33 ordered recommendations, each tied to a durable open ID, with #59 (exposed GitHub token containment) first in the A1 queue alongside privacy/legal and Safety Plan work.

The recommended execution queue is reordered and expanded with new tracked items (#59–#63)—token containment, Safety Plan privacy alignment, absent-relevance fail-closed behavior, stranded-upload recovery, threshold-conflict design (#35), catalogue-toolbar convergence (#39), and a “Current Clinical Work” brief (#63). Stale #14 / #34 claims move to Resolved; #14 drops from the open table.

issues-surface.sh no longer treats “zero open rows” as an empty ledger: SessionStart surfaces the queue when recommendations exist, with updated copy in AGENTS.md. docs/branch-review-ledger.md records this reconciliation pass.

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

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

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: 93edfb89-f7b9-402a-821e-c884d0b386f2

📥 Commits

Reviewing files that changed from the base of the PR and between 527988c and 52532fa.

📒 Files selected for processing (4)

• .claude/hooks/issues-surface.sh
• AGENTS.md
• docs/branch-review-ledger.md
• docs/outstanding-issues.md

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch codex/universal-ledger-main-final

---

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