docs: activate universal task ledger#1104
Conversation
# Conflicts: # docs/outstanding-issues.md
|
Warning Review limit reached
Next review available in: 8 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 (5)
✨ 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 |
![cursor[bot]](https://avatars.githubusercontent.com/in/1210556?s=60&v=4){kind=small}
There was a problem hiding this comment.
Cursor Bugbot has reviewed your changes using default effort and found 2 potential issues.
❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, enable autofix in the Cursor dashboard.
Reviewed by Cursor Bugbot for commit d75811f. Configure here.
![chatgpt-codex-connector[bot]](https://avatars.githubusercontent.com/in/1144995?s=60&v=4){kind=small}
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: d75811f05e
ℹ️ 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: b53f61940d
ℹ️ 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: 8d6c7791f8
ℹ️ 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".
| | #036 | rec | Add an explicit `is_public` visibility flag | No longer recommended: existing owner-scoped retrieval and visible unverified-source warnings sufficiently reduce the present risk; the schema/RLS change is disproportionate without a reproduced access defect. | 2026-07-24 | | ||
| | #041 | rec | Add another Factsheets reading mode | No longer recommended: extend the existing Easy Read/Standard model only when a concrete patient-content need and governance plan exist. | 2026-07-24 | | ||
| | #009 | rec | Confirm `/api/jobs` is intentionally server/ops-only | Archived after current-source verification: repository documentation and reachability tests treat this as an authenticated server/operations surface, and no client calls it. Its lack of an in-app link is intentional rather than abandoned functionality. | 2026-07-24 | | ||
| | #034 | issue | Answer cache can serve stale governance metadata | Archived after current-source verification: all known status-mutating routes call a RAG-cache invalidator, and route tests already assert invalidation on document PATCH, source review, label, bulk, and reindex mutation paths. Equivalent direct coverage exists; changing the protected cache key is not recommended. | 2026-07-24 | |
There was a problem hiding this comment.
This archive entry closes #034 on the assertion that all status-mutating routes already call a RAG-cache invalidator and that route tests assert reindex invalidation, but the single-document full reindex path still updates the documents row (status, error_message, counts) in src/app/api/documents/[id]/reindex/route.ts without any invalidateRagCaches... import or call, and the reindex tests only mock invalidateRagCachesForOwner rather than asserting it. If someone follows this universal ledger literally, the stale-cache regression-test/remedy is dropped while one reindex mutation path remains uncovered; keep #034 open or narrow the archive until that path is fixed/pinned.
AGENTS.md reference: AGENTS.md:L461-L462
Useful? React with 👍 / 👎.
| every worthwhile task and its current state in the universal ledger. Update affected queue and | ||
| evidence records together when work is completed, dropped, superseded, or materially re-scoped. |
There was a problem hiding this comment.
The new invariant requires queue and evidence records to change together, but the existing /issues add|done|update instructions still only append, move, or edit rows under ## Open items / ## Resolved / archive in .claude/skills/issues/SKILL.md. When a user uses the documented shortcut after this lands, new or completed work can be committed to the evidence table while the prioritized queue remains stale, defeating the ledger as the source of dependency order; update the skill/hook or scope this rule accordingly.
AGENTS.md reference: AGENTS.md:L461-L462
Useful? React with 👍 / 👎.
|
Superseded by merged PR #1106, which delivers the same universal-ledger outcome against newer evidence and includes additional retained A1/operator/release work. This branch now conflicts with and would overwrite that newer canonical ledger, so merging it is no longer recommended. All five review threads here were fixed and resolved before closure. |
1 participant
Summary
Verification
No provider configuration, production data, or application runtime behavior is changed.
Note
Low Risk
No application, migration, or runtime changes—only markdown and agent memory contracts; incorrect queue content could mis-prioritise future work but does not change production behavior.
Overview
Promotes
docs/outstanding-issues.mdto the single universal task ledger and reshapes how agents and humans track repo work.The ledger now includes a 23-row prioritised recommended queue (dependency order, classification, acuity, capability, timing, approvals, success criteria, and stop rules), a reconciliation snapshot (2026-07-24 on
main), recommended sequence guidance, an explicit exclusion list for stale or refuted work, and an evidence register that sits alongside the existing open-items table. New tracked work#052(reindex vs agent-enrichment lease),#053(orphaned queued ingestion recovery), and#054(clinical workspace brief); several former open items move to resolved/archive with dated outcomes (e.g.#026document-trigger,#029superseded,#005/#032refuted).AGENTS.mdstates that the ledger owns execution order and must stay in sync with queue/evidence updates, with provider detail remaining indocs/operator-backlog.md.docs/README.mdanddocs/codebase-index.mdlink the ledger in the maintained docs map.docs/branch-review-ledger.mdgets a minor wording tweak only.Reviewed by Cursor Bugbot for commit d75811f. Configure here.