docs: refresh maturity tracker + scripts index to merged reality#1010
Conversation
The living backlog tracker had drifted from what shipped: - maturity-backlog-workorders: N2 and X1 → DONE (#986), L3 → DONE (#1002); X3 annotated with its first extraction landing (#997) and refreshed monolith line counts (rag.ts 5,018); corrected the stale "197 flat files" to the 176 top-level .ts files that remain after the rag move; replaced "this PR" placeholders with the PR numbers each item actually landed in; refreshed the progress-summary table to match. - scripts-index: added check-gate-manifest.mjs to the verification-gate building blocks with a one-line description of what it guards. Docs-only accuracy fixes — no source, config, or behaviour change. Verified with docs:check-links, docs:check-scripts, docs:check-index, and Prettier format:check. 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. |
📝 WalkthroughWalkthroughThe PR updates maturity backlog statuses and landed-work details, revises the progress summary, and documents ChangesMaturity and verification documentation
Estimated code review effort: 2 (Simple) | ~10 minutes Possibly related PRs
🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✨ Finishing Touches📝 Generate docstrings
🧪 Generate unit tests (beta)
Comment |
|
You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard. |
Summary
A documentation-accuracy pass — the living maturity backlog tracker had drifted from what
actually shipped across the recent maturity PRs. No source, config, or behaviour changes.
docs/maturity-backlog-workorders.mdN2(dependency-report) andX1(import-boundary lint) → DONE, both landed in ci: enforce mockup import boundary + enable dependency report (maturity X1, N2) #986.L3(single gate manifest) → DONE, landed in ci: enforce the local verify:cheap gate set in CI + gate-manifest self-test (maturity L3) #1002.X3(monolith decomposition) annotated with its first extraction landing (refactor(rag): extract evidence-gate predicates into rag-evidence-gates (maturity X3) #997) andrefreshed line counts (
rag.tsnow 5,018; components untouched)..tsfiles thatremain after the
ragcluster moved intosrc/lib/rag/(refactor(rag): extract the rag cluster into src/lib/rag/ (maturity X2) #994).this PRplaceholders with the PR numbers each item actually landed in(N1 → docs+chore: implement safe maturity-backlog items + work orders for the rest #985, X2 → refactor(rag): extract the rag cluster into src/lib/rag/ (maturity X2) #994, L2 → ci: enforce one SHA per action across workflows + composites (maturity L2) #992, L5 → docs+chore: implement safe maturity-backlog items + work orders for the rest #985), and refreshed the progress-summary table.
docs/scripts-index.mdcheck-gate-manifest.mjsto the verification-gate building blocks with a one-linedescription of what it guards (CI ↔ local gate-list parity).
Performance and broader repo-wide review were considered as part of this "final wins" sweep;
there is no safe, easy performance win here — the remaining perf-relevant surfaces are the
runtime/RAG lane, which is deliberately out of scope for a maintainability pass. That is
recorded honestly rather than padded with a speculative change.
Verification
npm run verify:pr-localVerification not run: docs-only accuracy change with no source/config/behaviour edits. Ran the
documentation gates instead, all green:
npm run docs:check-links— 1032 repo path references resolve.npm run docs:check-scripts— 319npm runreferences resolve to real scripts.npm run docs:check-index— codebase-index coverage OK (41 modules/routes + all schema tables).npx prettier --checkon both edited files — clean.npm run verify:ui— N/A (no UI/routing/styling change)npm run verify:release— N/A (not a release/handoff claim)Risk and rollout
the repo state and the merged PR history before writing.
Clinical Governance Preflight
Not applicable — this change touches no ingestion, answer generation, search/ranking, source
rendering, document access, privacy, production env, or clinical output. Documentation only.
Notes
X4(SAST-blocking on the parser path) remainsPROVIDER-GATED (triage-first)— it needs aSemgrep-capable environment to triage findings before the gate can flip, so it is intentionally
left as an open work order rather than forced here.
🤖 Generated with Claude Code
Generated by Claude Code
Summary by CodeRabbit