docs: make outstanding issues the universal task ledger

[BigSimmo]

Summary

• Make docs/outstanding-issues.md the single universal repository task ledger.
• Add one 35-item recommended execution queue with order, acuity, capability, timing, effort, approvals, verification, and stop rules.
• Preserve detailed open/resolved evidence in the same file; remove the competing-ledger contract.
• Reconcile current main: keep Fix Next.js binding to allow Railway healthchecks #25 active and archive the completed/live-verified Create codeql.yml #26 trigger work.

Verification

• npx prettier --check AGENTS.md docs/README.md docs/branch-review-ledger.md docs/codebase-index.md docs/outstanding-issues.md
• npm run docs:check-links — 1,122 references resolved
• npm run docs:check-index — all 42 top-level modules/routes and schema tables indexed
• git diff --check for the ledger-specific change
• Merged current origin/main and resolved the ledger conflict using newer live evidence
• npm run verify:pr-local

Verification not run: the isolated worktree has no project node_modules; the risk-scoped dry run selected runtime, format, lint, typecheck, unit, and offline RAG fixture checks. Hosted required CI must provide the complete gate.

Risk and rollback

• Risk: Low. Documentation and repository-memory contract only; no runtime, API, migration, retrieval, clinical-output, or provider behavior change.
• Rollback: Revert this PR commit to restore the prior ledger format.
• Provider or production effects: GitHub PR/CI only. No Supabase, OpenAI, Railway, deployment, or production mutation performed.

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

Clinical Governance Preflight

Not applicable: no ingestion, answer generation, search/ranking, source rendering, document access, privacy, production environment, or clinical output behavior changed.

[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: 19 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: 044de4d4-04d0-432b-88b5-2769f2a05bc8

📥 Commits

Reviewing files that changed from the base of the PR and between bb70161 and ee94dbe.

📒 Files selected for processing (5)

• 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-e61499

---

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

[chatgpt-codex-connector]

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 011e7646e8

ℹ️ 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]

Wire the execution queue into /issues

When the advertised /issues workflow is used, this new queue is currently invisible: .claude/skills/issues/SKILL.md:22-25 still tells agents to state only the Open items grouped by priority, and .claude/hooks/issues-surface.sh:28-35 explicitly parses only rows under ## Open items. That means users will still see items like #51/#1 before queue item #52 and will never see queue-only work such as the Privacy/legal package through the normal entry point, so the new recommended execution order is not actually actionable unless the skill/hook are updated or all executable queue work is represented in the Open items table.

AGENTS.md reference: AGENTS.md:L453-L458

Useful? React with 👍 / 👎.

[BigSimmo]

Superseded by #1109, which reconciles the ledger against current main, includes the repository-wide activation wiring, and adds the missing provider-gated credential-containment task.