docs: make outstanding issues the universal task ledger#1107
Conversation
…horitative-1c2750 # Conflicts: # docs/outstanding-issues.md
…horitative-1c2750
|
This pull request has been ignored for the connected project Preview Branches by Supabase. |
|
Warning Review limit reached
Next review available in: 9 minutes Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available. How can I continue?After more reviews become available, a review can be triggered using the 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 configurationConfiguration used: Path: .coderabbit.yaml Review profile: CHILL Plan: Pro Plus Run ID: 📒 Files selected for processing (8)
✨ Finishing Touches🧪 Generate unit tests (beta)
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. Comment |
There was a problem hiding this comment.
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 061e278. Configure here.
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 061e278386
ℹ️ 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".
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 60b1e2ffb5
ℹ️ 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".
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: ed5ccfcd2e
ℹ️ 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".
| The deduplicated execution order is in [`outstanding-issues.md`](outstanding-issues.md). Supabase work | ||
| in its active queue targets only `Clinical KB Database` (`sjrfecxgysukkwxsowpy`); this register must | ||
| not reintroduce work for another Supabase project. |
There was a problem hiding this comment.
Keep staging soak in the active task queue
When an operator relies on /issues or the SessionStart summary after this change, the Railway staging soak/rollback rehearsal is no longer surfaced anywhere: it was removed from this backlog, but the launch runbook still lists it as step 4 and spells out the scripts/soak-test.ts --confirm-staging verification with the answer-p95 target. Since the new contract says the deduplicated execution order lives in docs/outstanding-issues.md, either add that still-recommended provider action to the active queue or explicitly retire/update the runbook; otherwise release readiness can skip the staging load/rollback proof.
AGENTS.md reference: AGENTS.md:L457-L461
Useful? React with 👍 / 👎.

Summary
docs/outstanding-issues.mdthe single universal repository task ledger/issues, the session-start memory hook, repository instructions and supporting docs to use the universal queuesjrfecxgysukkwxsowpy) Supabase workRAG impact: no retrieval behaviour change — documentation and repository-memory workflow only.
Verification
npm run verify:pr-local(365 files; 3,241 passed, 1 skipped; offline RAG fixtures 36 cases / 21 suites)npm run docs:check-links(1,125 references)npm run docs:check-indexgit diff --checkNo live Supabase, OpenAI, deployment, or production-data workflow was run.
Note
Low Risk
Documentation and agent-workflow changes only; no application, database, or RAG runtime behavior is modified.
Overview
docs/outstanding-issues.mdbecomes the single universal task ledger. The old Open items table (P1–P3 + type) is replaced by a Prioritised queue of ~30 active rows with execution order, acuity (A1 / A2 / A3 / Optional), capability, timing, effort, approvals, and stop rules. A separate evidence register keeps historical detail; only queue rows are executable. New sections cover Supabase scope (Clinical KB Database only), recommended sequence, and merged operator/RAG work (e.g.#052reindex vs agent-enrichment overlap).Agent and repo memory wiring is aligned to the queue. The SessionStart hook
.claude/hooks/issues-surface.shparses## Prioritised queueinstead of open items. Theissuesskill andAGENTS.mddescribe read/filter/mutate against the queue and require recommended provider work to appear there even when runbooks live inoperator-backlog.md.Supporting docs:
operator-backlog.mdis reframed as a detailed register (execution order points at the ledger; staging provision/soak rows removed).docs/README.md,codebase-index.md, andbranch-review-ledger.mdare updated accordingly.#014(next/imagesigned previews) is archived as superseded by the privacy-safeSignedImageapproach.Reviewed by Cursor Bugbot for commit 061e278. Configure here.