ehoandClaude Opus 5
12f17d9d73
Two backlog trees are complete: `docs/project/backlog/` (75 files, every WP done) and `docs/project/refactor-backlog-setup/` (the arc before it). Move both under `docs/project/archive/` with `git mv`, so history stays intact through `git log --follow`. `SHOWCASE-ROADMAP.md` moves with them, because it points at the now-archived backlog README. Add `docs/project/archive/README.md`. It states that these trees are historical and names the two directories that are still live. Repoint every inbound reference named in RD-30's Files table: CLAUDE.md, the root README, both backend READMEs, `LetterHtml.cs`, `a11y.mdx`, the `document-feature` and `new-ssp` skills, and the readable-codebase PLAN, README, and RD-19 ticket. Fix two upward-relative links inside the moved WP files (WP-68, WP-69) that gained a directory level and would otherwise break. Repoint `.prettierignore`'s two agent-prompt exclusions to their new path, so prettier keeps leaving those files' exact wording alone. Mark RD-30 done and check off its acceptance criteria; flip its README row to done. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
2.4 KiB
MODEL: Opus OUTPUT FILE: /refactor-backlog/99-backlog.md DEPENDS ON: 01-readability.md through 07-bio2-compliance.md (all complete)
PERSISTENCE & RESUME PROTOCOL
Before starting work:
- Read /refactor-backlog/_status.md. If your row says "complete", stop — do not re-run.
- If "in_progress", read your own output file. Treat modules already listed as done. Resume from "Last module processed" + 1.
- If "not_started", confirm your dependencies show "complete" in _status.md. If not, stop and report a blocking dependency instead of guessing.
While working: 4. Append findings incrementally, one module at a time. After each module, update _status.md: "Last module processed" and "Last updated". 5. Each finding gets a stable ID (e.g. RD-014) that never changes across runs. 6. If interrupted, the file + status row is the full recovery state.
On completion: 7. Mark your _status.md row "complete" only once every module in scope has a corresponding section in your output file.
Every output file starts with:
Scope: [modules covered]
Status: [not_started | in_progress | complete]
Last updated: [timestamp]
Depends on: [file(s)]
---
Phase 1 file changed since last run]
ROLE: Consolidation & CD-Sequencing Agent
Input: all Phase 1 files (01–07) + 00-baseline.md.
- Deduplicate overlapping findings across agents — merge into one ticket, list all contributing reasons/agents.
- Score priority: P1 = violates a correct ADR, blocks testability, or is a BIO2 compliance risk. P2 = significant maintainability cost, moderate effort. P3 = low urgency.
- Sequence for continuous delivery: every ticket must be independently deployable without a big-bang release. Reject/split any ticket that can't ship alone — decompose into a dependency chain of smaller tickets.
- Any ticket touched by the BIO2 agent requires compliance sign-off before merge, regardless of priority score — mark explicitly.
- Output final table:
| ID | Module | Category | Description | Baseline metric improved | Effort (S/M/L) | Risk | Priority | CD batch # | Depends on | Status |
- Separately list "ADR-fix" tickets — require human/architect approval before any dependent code ticket proceeds.
HALT CONDITION: after writing 99-backlog.md, stop and report to the human for approval before any Implementation Agent (Phase 3) starts — even if no tickets carry a compliance or ADR-fix flag.