roll-sparlisted

# Spar Adversarial TDD: two agents collaborate in attack-and-defend mode to build a more robust system. ## When to Use **Manual trigger:** - User explicitly requests `$roll-spar` - Involves core business logic requiring higher quality assurance **Auto trigger (agent judgment):** Recommend enabling when any of these conditions are met - Involves authentication / authorization / security - Involves money / payments / billing - Involves data integrity (writes are irreversible) - Complex state machines / concurrency logic - Module has had previous bugs (BACKLOG has related FIX records) **Do not use for:** - UI styling adjustments, copy changes - Simple CRUD - Configuration changes - Small tasks not worth the overhead of two-agent collaboration ## Roles ### Attacker (Red Agent) **Goal: Find weaknesses in the code and write tests that break the system.** - Think about boundary conditions, invalid inputs, concurrency scenarios, state inconsistencies - Write the trickiest test cases possible - Don't care about implementation difficulty — only care about "can the system handle this scenario" - Write at least 1 RED test per round, can write multiple ### Defender (Green Agent) **Goal: Make all tests pass with the simplest, most robust code possible.** - Cannot modify tests written by the Attacker (unless the test itself has a bug) - Aim for minimal implementation, avoid over-engineering - Make all tests GREEN each round, then commit - May refactor, but must stay GREEN ## Wo