docs: make outstanding issues the universal task ledger

[BigSimmo]

Summary

• make docs/outstanding-issues.md the single universal, ordered repository task ledger
• retain only 18 recommended active rows with acuity, capability, timing, effort, approvals, verification, and stop rules
• update /issues, the session-start hook, repository instructions, and documentation indexes to use that queue
• preserve legacy evidence and resolved history as non-active audit material
• preserve queue order in startup output and make both ingestion safeguards explicit before webhook activation

Verification

• npm run verify:pr-local
  • Verification not run: repeated attempts were blocked by another Database worktree owning the serialized heavyweight-test lock.
• npm run verify:cheap — 365 files passed; 3,241 tests passed, 1 skipped; lint, typecheck, security, schema, ownership, and maintainability gates passed
• npm run docs:check-links — 1,124 references resolved
• Git Bash syntax/runtime check for .claude/hooks/issues-surface.sh; output preserved orders 1–10 and reported 18 active tasks
• UI verification not run: documentation and repository-memory workflow only; no UI, routing, or styling change.
• Release verification not run: no runtime or deployment change.

Risk and rollout

• Risk: low; incorrect queue parsing or stale task surfacing is bounded to repository workflow guidance.
• Rollback: revert this PR to restore the previous priority-grouped issue memory.
• Provider or production effects: GitHub PR/CI only. No production, Supabase, Railway, OpenAI, or paid workflow effects.

Clinical Governance Preflight

Not applicable to runtime behavior: no ingestion implementation, answer generation, retrieval, source rendering, document access, privacy, production environment, or clinical output code changed. Existing provider and clinical approval gates are documented in the ledger and remain fail-closed.

Notes

• This is the canonical replacement for duplicate ledger PRs docs: activate universal task ledger #1104, docs: activate universal repository task ledger #1105, docs: make outstanding issues the universal task ledger #1106, docs: make outstanding issues the universal task ledger #1107, and docs: activate universal repository task ledger #1109.

---

Note

Low Risk
Documentation and agent workflow only; wrong ledger parsing could mis-surface task order but does not affect runtime, production, or clinical code paths.

Overview
docs/outstanding-issues.md becomes the single universal task ledger: the Open items table is the only active queue, with 18 dependency-ordered rows and richer execution metadata (acuity, capability, timing, effort, approvals, verification, stop rules). Ingestion safeguards #52 and #53 are explicitly sequenced before webhook activation (#25). Older claims move into a legacy evidence register that /issues and the session hook do not treat as work.

/issues workflow is aligned end-to-end: the issues skill reads and mutates by Order (not P1→P3 grouping), requires full row fields on add, and dedupes capture against legacy/resolved history. issues-surface.sh parses the wider table and prints the first ten items in ledger order. AGENTS.md and doc indexes describe the ledger as repository memory and point operators at docs/operator-backlog.md for procedures.

^{Reviewed by Cursor Bugbot for commit 05acad6. 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: 2 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: fc54878a-93d1-4fab-8a06-4e36ba21b6bc

📥 Commits

Reviewing files that changed from the base of the PR and between 1391158 and 05acad6.

📒 Files selected for processing (7)

• .claude/hooks/issues-surface.sh
• .claude/skills/issues/SKILL.md
• AGENTS.md
• docs/README.md
• docs/branch-review-ledger.md
• docs/codebase-index.md
• docs/outstanding-issues.md

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch codex/task-ledger-current-3d3b2b

---

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

[cursor]

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

^{❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, enable autofix in the Cursor dashboard.}

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

[cursor]

Priority field parses empty

Medium Severity

The hook reads priority from the Pri / acuity column by splitting on a single space and taking the first token, but pipe-delimited cells include a leading space, so that token is empty and trimming never yields P1/P2/P3. Session-start output then shows zero counts for every priority band and omits priority in the first ten task lines.

 

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

[BigSimmo]

Superseded by merged PR #1106 and follow-up PR #1110. This branch is now conflicting with newer main security and priority records, so it will not be merged.