I read this as an advisory-only contract decision - I’ll inspect the approved plan, start-work quality rules, checkpoint, and cited evidence, then return a strict blocking verdict without edits or live actions.


1. **Yes.** The runner is part of Todo 2’s QA/evidence flow, owns generated temporary state, and is interrupted mid-operation while managing a child process. The contract explicitly maps **“mid-operation interrupts → repeated interruptions”** and states: **“A class applies when its trigger fact holds. Probe each applicable class.”** This is not limited to product code.

2. **`REPAIR_REQUIRED`.** Product behavior is sound, but checkbox completion is governed by the whole start-work quality contract. The independent audit returned `needs-fix`, and the contract says: **“`confirmed` is the only pass verdict. `false-positive`, `needs-fix`, and `needs-human-review` all block checkbox completion.”** Reviewer removal restored workspace hygiene but did not turn the failed interruption behavior into a confirmed pass.

3. **Minimum evidence-only repair and acceptance:**
   - **Recommended design:** Change the runner to own its pytest child through `Popen`, convert SIGTERM into orderly cancellation, and use an idempotent `finally` path that terminates, bounded-waits, escalates if necessary, reaps the child, removes only its owned temporary parent, and exits with an interruption status rather than success.
   - **Alternative:** Introduce an evidence-only supervisor/helper that owns signal forwarding, child reaping, and temporary-root cleanup. This is more reusable but adds coupling and another failure surface; one runner does not justify it.
   - **Acceptance:** Reproduce the FIFO-synchronized SIGTERM case after the child-entered signal; require bounded runner exit, no surviving runner or child, and zero `.task-2-red-r3-*` directories. Then rerun normal RED twice, modified-manifest rejection, focused tests, diagnostics/static gates, and cleanup. A fresh independent verifier must return `confirmed`.
   - **Non-negotiable safeguards:** Evidence files only; no product module or product-test behavior changes; terminate only the runner-owned child/resources; bounded escalation with child reaping; cancellation must never emit success; no live, network, provider, service, customer, or Git actions.