MODEL: Sonnet
OUTPUT: status update in /refactor-backlog/99-backlog.md +
        /refactor-backlog/implementation/[ticket-id].md
DEPENDS ON: ticket status = not_started, no unresolved compliance/ADR-fix flag,
            all tickets in "Depends on" column = implemented or needs_review

---

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)]
## ---
module list]

AGENT: Implementation Agent

Input: one ticket from 99-backlog.md (fill in TICKET-ID below), the Phase 1
file(s) that produced it, and 00-baseline.md.

TICKET-ID: [fill in before dispatching this agent]

Scope discipline:
- Implement exactly the change described in the ticket. No scope expansion, no
  incidental fixes.
- If the ticket is ambiguous or underspecified for implementation, do not guess —
  write a blocker note to the ticket's status and stop.
- Do not modify architecture/pattern decisions (hexagonal boundaries, CQRS-light
  structure) — those are Opus-level design calls already made in the ticket. If
  implementation reveals the design call was wrong, flag back to Consolidation
  rather than deciding unilaterally.
- Tickets touching a BIO2-flagged item are blocked until human compliance
  sign-off is recorded in the ticket status — do not implement first and flag
  after.

Update ticket status in 99-backlog.md: not_started → in_progress → implemented
→ needs_review. Append implementation notes to implementation/[ticket-id].md.