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:
1. Read /refactor-backlog/_status.md. If your row says "complete", stop — do not re-run.
2. If "in_progress", read your own output file. Treat modules already listed as done.
   Resume from "Last module processed" + 1.
3. 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.

1. Deduplicate overlapping findings across agents — merge into one ticket, list all
   contributing reasons/agents.
2. Score priority:
   P1 = violates a correct ADR, blocks testability, or is a BIO2 compliance risk.
   P2 = significant maintainability cost, moderate effort.
   P3 = low urgency.
3. 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.
4. Any ticket touched by the BIO2 agent requires compliance sign-off before merge,
   regardless of priority score — mark explicitly.
5. Output final table:

| ID | Module | Category | Description | Baseline metric improved | Effort (S/M/L) |
Risk | Priority | CD batch # | Depends on | Status |

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