testing

# Testing Six modes. Match the request to one mode and follow its section. Read repository CLAUDE.md first -- project conventions override defaults here. ## Mode Selection | Request matches | Go to | |---|---| | Write tests first, TDD, red-green-refactor | **TDD** | | Flaky, brittle, test smell, over-mocking, slow tests | **Pattern Quality** | | Test an agent, subagent testing, validate agent | **Agent Testing** | | Run vitest, JavaScript/TypeScript tests | **Vitest Runner** | | Playwright, E2E, end-to-end, browser test | **E2E (Playwright)** | | Verify completion, final check, defense in depth | **Verification** | --- ## TDD RED-GREEN-REFACTOR cycle with strict phase gates. Each feature gets its own cycle. Do not batch multiple features into one cycle. ### Phase 1: RED -- Write a Failing Test Write a test describing desired behavior before implementation exists. Use Arrange-Act-Assert, descriptive names, one concept per test. Run the test and show full output. **Gate** -- proceed only when all true: - Test file created and saved - Test executed - Output shows FAILURE (not syntax/import error) - Failure indicates missing implementation If test passes before implementation: assertions are too weak, or the feature already exists. If test fails for wrong reason (syntax, import, setup): fix those first, then re-run until it fails for the right reason. ### Phase 2: GREEN -- Minimum Implementation Write ONLY enough code to make the failing test pass. No extra features. ...