cc-tdd-cyclelisted

# TDD Cycle — Red → Green → Refactor Scope: $ARGUMENTS Describe what behavior you want to implement. Include: - The function, method, or feature to implement - The expected behavior (inputs and outputs, or acceptance criteria) - Any known constraints or edge cases - Relevant files or modules (if known) --- ## Before you begin — mandatory pre-check This command enforces strict TDD discipline. The three phases are sequential and non-negotiable: 1. **RED** — a failing test exists before any implementation code is written 2. **GREEN** — the minimum implementation to make the test pass (no more) 3. **REFACTOR** — clean up the code while keeping all tests green Do not write implementation code during RED. Do not refactor during GREEN. Mixing phases invalidates the cycle. ## Verifiable phase gates RED → GREEN and GREEN → REFACTOR are enforced by `tddCycleStateMachine` in `domain/loop`. Evidence must be captured with `captureTddSuiteEvidence` (verification runner) — do not hand-edit JSON under `.codeconductor/evidence/`. - RED→GREEN requires runner evidence that the suite **failed**. - GREEN→REFACTOR requires runner evidence that the suite **passed**. Do not advance phases until that evidence exists. --- ## Phase 1 — RED (Tester role) Adopt the **Tester** role as defined in `CLAUDE.md`. ### 1a — Scope clarification Before writing any test, confirm: - What is the unit of behavior being tested? (function, method, endpoint, domain rule) - What are the inputs and expe