sdd-workflowlisted

# SDD Workflow Use this owner for change work. SDD is the spine; TDD is embedded inside the accepted spec. ## Canonical Lifecycle Do not start implementation until the user-visible gates are aligned. 1. **Align user need**: outcome, actor, pain, constraints, non-goals, and success target. 2. **Gather required material**: repo docs, code paths, existing source decisions, and referenced repos/blogs needed for the change. 3. **Write spec and acceptance**: target behavior, boundaries, acceptance criteria, verification strategy, and open questions. 4. **Write executable plan and align**: file targets, task order, tests, cleanup list, subagent use, hook checks, and validation commands. 5. **Clean unneeded files**: delete, demote, archive, or retain only after ownership and safety are clear. 6. **Implement**: make the smallest scoped change that satisfies the accepted spec. 7. **Test and accept**: run agreed unit, integration, E2E, or deterministic checks. 8. **Deliver report**: use `effective-interact` for material work, with changes, evidence, validation, risks, and next actions. During implementation, update the active task's `Spec updates` only for decision-level changes that alter assumptions, acceptance criteria, allowed paths, validation commands, user-visible behavior, or risk. Do not turn it into a progress log; progress belongs in the harness progress file when a repo harness is active. ## TDD - Write or identify the failing test before implementation when behavior