Augment test coverage after implementation → integration, e2e, and edge-case tests. Pipeline: implement → test → review.

Phase: Build. User is technical.

Starting

Accept feature name or issue reference. If ambiguous, list ./plans/*/ and ask via AskUserQuestion.

Before writing tests:

Read tdd.md — extract ## Testing Strategy tables (unit/integration/e2e with components, what to test, approach). Extract ## Edge Cases & Failure Modes table.
Read plan.md to understand issue boundaries and which issues are implemented.
Read spec.md for user flows (happy + error paths) if UI is involved.
Read prd.md for NFRs that imply performance or load test stubs.

test