docs(issues): add #085 — repository maturity backlog to the universal ledger - #1302
Conversation
…ledger Capture the deferred repository-maturity backlog as one consolidated Open-items row (#85, P3, task) in docs/outstanding-issues.md, pointing at the canonical runbook docs/maturity-backlog-workorders.md so it's discoverable via /issues. Covers X3 (rag.ts), X7 (src/lib reorg), X6 (coverage floors), X5 (ACL consolidation), L1 (one-shot archiving), L4 (ledger rotation), and M1 (repo-host hardening), with the go-ahead/provider gates noted. Bumps the next-id marker to 086. Docs-only; no code or behaviour change. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_019Jc1ZYHFjXjn6mE6U6riVU
This pull request has been ignored for the connected project Preview Branches by Supabase. |
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Path: .coderabbit.yaml Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (1)
📝 WalkthroughWalkthroughThe issues ledger advances its allocator from 086 to 087 and adds open item ChangesLedger update
Estimated code review effort: 1 (Trivial) | ~5 minutes Possibly related PRs
Suggested reviewers: 🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
Comment |
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit:84715966c6
ℹ️ 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".
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
BigSimmo
commented
Jul 28, 2026
@cursoragent please resolve all CI failing tests after understanding the issue. Please also fix any comments and resolve them and also ensure that you fix with smallest required fix with best coding practice and u derstabding the fix rather than simple patch. Please fix any merge conflicts and ensure any issues are found. Please resolve any issues you find. Please also run bugbot. Please mark comments resolved also once you resolve them. |
PR #1302 is cleaned up on tip Root cause: real conflict with Fixes
CI on tip: |
Resolve the outstanding-issues conflict with main's #85 upload-limit row by allocating #86 for the repository maturity backlog, bump the allocator to 087, and add #86 to the recommended execution queue with go-ahead and provider gates. X7/M1 definitions arrive via main's maturity workorders tracker. Co-authored-by: BigSimmo <BigSimmo@users.noreply.github.com>
Co-authored-by: BigSimmo <BigSimmo@users.noreply.github.com>
Uh oh!
There was an error while loading. Please reload this page.


Summary
Add the deferred repository-maturity backlog to
docs/outstanding-issues.md(the Universal TaskLedger that
/issuesreads), so it's discoverable alongside the rest of the team's outstanding work— not siloed in the maturity tracker.
Per the ledger's conventions (detailed runbooks live elsewhere; status is canonical here), this is
one consolidated Open-items row rather than six duplicated entries:
#085(P3, task) — "Repository maturity backlog — remaining structural work", pointing at thecanonical runbook
docs/maturity-backlog-workorders.md.It enumerates the remaining items (X3
rag.ts, X7src/libreorg, X6 coverage floors, X5 ACLconsolidation, L1 one-shot archiving, L4 ledger rotation, M1 host hardening) with their go-ahead /
provider gates.
issues:next-idmarker085 → 086.Kept the Detail cell under the column's existing max width so prettier pads only the new row (no
table-wide re-pad) — the diff is
+2/−1.Verification
npm run format:check— clean (row aligns to the existing table; no re-pad)npm run docs:check-links— repo path references resolvenpm run docs:check-scripts— npm-run references resolveRisk and rollout
Clinical Governance Preflight
Not applicable — documentation only. No ingestion, answer generation, retrieval/ranking, source
governance, document access, privacy, schema, or production behaviour changed.
🤖 Generated with Claude Code
Generated by Claude Code
Summary by CodeRabbit