Skip to content

docs: make outstanding issues the universal task ledger#1107

Closed
BigSimmo wants to merge 7 commits into
mainfrom
codex/task-ledger-authoritative-1c2750
Closed

docs: make outstanding issues the universal task ledger#1107
BigSimmo wants to merge 7 commits into
mainfrom
codex/task-ledger-authoritative-1c2750

Conversation

@BigSimmo

@BigSimmo BigSimmo commented Jul 24, 2026

Copy link
Copy Markdown
Owner

Summary

  • make docs/outstanding-issues.md the single universal repository task ledger
  • move recommended order, acuity, capability, timing, effort, approvals, verification and stop rules into that ledger
  • update /issues, the session-start memory hook, repository instructions and supporting docs to use the universal queue
  • remove the superseded staging-project operator tasks and retain only Clinical KB Database (sjrfecxgysukkwxsowpy) Supabase work

RAG 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)
  • universal-ledger hook syntax and runtime: 30 active (0 A1, 14 A2, 10 A3, 6 optional)
  • npm run docs:check-links (1,125 references)
  • npm run docs:check-index
  • git diff --check

No 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.md becomes 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. #052 reindex vs agent-enrichment overlap).

Agent and repo memory wiring is aligned to the queue. The SessionStart hook .claude/hooks/issues-surface.sh parses ## Prioritised queue instead of open items. The issues skill and AGENTS.md describe read/filter/mutate against the queue and require recommended provider work to appear there even when runbooks live in operator-backlog.md.

Supporting docs: operator-backlog.md is reframed as a detailed register (execution order points at the ledger; staging provision/soak rows removed). docs/README.md, codebase-index.md, and branch-review-ledger.md are updated accordingly. #014 (next/image signed previews) is archived as superseded by the privacy-safe SignedImage approach.

Reviewed by Cursor Bugbot for commit 061e278. Configure here.

@supabase

supabase Bot commented Jul 24, 2026

Copy link
Copy Markdown

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

coderabbitai Bot commented Jul 24, 2026

Copy link
Copy Markdown
Contributor

Warning

Review limit reached

@BigSimmo, you've reached your PR review limit, so we couldn't start this review.

Next review available in: 9 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: bf8c5ff6-4803-45e3-980f-f237ffb2de73

📥 Commits

Reviewing files that changed from the base of the PR and between 705480a and ed5ccfc.

📒 Files selected for processing (8)
  • .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/operator-backlog.md
  • docs/outstanding-issues.md
✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch codex/task-ledger-authoritative-1c2750

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

Comment @coderabbitai help to get the list of available commands.

@cursor cursor Bot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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

Fix All in Cursor

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

Comment thread docs/outstanding-issues.md Outdated

@chatgpt-codex-connector chatgpt-codex-connector Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

💡 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".

Comment thread docs/branch-review-ledger.md Outdated

@chatgpt-codex-connector chatgpt-codex-connector Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

💡 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".

Comment thread docs/outstanding-issues.md

@chatgpt-codex-connector chatgpt-codex-connector Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

💡 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".

Comment thread docs/operator-backlog.md
Comment on lines +7 to +9
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.

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P2 Badge 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 👍 / 👎.

@BigSimmo

Copy link
Copy Markdown
Owner Author

Superseded by the completed universal-ledger reconciliation in #1112 and the preserved UI follow-up merged in #1116. Current origin/main contains the active queue and IDs #59-#65.

@BigSimmo BigSimmo closed this Jul 24, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant