test-plan-formatlisted

# Test Plan Format ## File Conventions - **Location:** `docs/testing/plans/` - **Naming:** `YYYY-MM-DD-<topic>-test-plan.md` where `<topic>` is a slugified summary (lowercase, hyphens, no spaces) - **Create directory if needed:** `mkdir -p docs/testing/plans` --- ## Plan Structure Every test plan MUST follow this exact structure: ~~~markdown # Test Plan: <title> ## Source - Type: <PR #N / branch <name> / last N commits / staged changes> - Base: <main/master> - Date: <YYYY-MM-DD> ## Changes Summary <Brief description of what changed and what needs testing. List affected areas.> ## Detected Tools - Playwright MCP: <available/unavailable> - HTTP client: <curl/httpie/unavailable> - Database access: <psql/sqlite3/mysql/unavailable> ## FE Test Scenarios ### FE-01: <scenario name> - **Area:** <component/page> - **Preconditions:** <what must be true before test> - **Steps:** 1. <action> 2. <action> 3. <verification> - **Expected:** <expected result> - **Edge cases:** - <edge case 1> - <edge case 2> ## BE Test Scenarios ### BE-01: <scenario name> - **Area:** <endpoint/service> - **Method:** <HTTP method> <path> - **Headers:** <required headers, e.g. Authorization: Bearer TOKEN> - **Payload:** `<JSON body>` - **Expected:** <status code>, <response body description> - **DB Check:** `<SQL query>` — <expected state> - **Edge cases:** - <edge case with expected response> ~~~ --- ## Scenario Naming - FE scenarios: `FE-01`, `FE-02`, ... `FE-NN` (zero-padded two d