- **Rationale (2026-04-30):** E134S03 + E134S04 had to be rolled back from `in_progress` (with abandoned worktree containing cycle-0 CRITICAL-error spec) because Discovery registered them as `refined` while still iterating Reviewer cycle-1 corrections. The daemon picked up the un-reviewed drafts and started implementing architecturally wrong code (proposed a redundant CLI surface that already existed, referenced a non-existent artefact name). See commit `4f99ad40` for incident audit trail. The fix is strict adherence to the `draft → refined` lifecycle defined in `base.rules.md` § Backlog State Lifecycle — this clause makes the timing explicit at skill level.
0 commit comments