e2e-verification

# E2E Verification (Playwright + local login) ## Overview Drive the **running** Chorus dev server in a real browser via the Playwright MCP to verify UI changes end-to-end. Core loop: **log in with local credentials → navigate → snapshot to read state / act → screenshot for the human**. This is manual acceptance, not the automated Vitest suite (`pnpm test`). Use it when an AC says "the user sees X" and only a real browser can confirm it. ## Prerequisites - **Dev server healthy** on port **8637**. Always check first: ```bash curl -s -o /dev/null -w "%{http_code}" http://localhost:8637/login # expect 200 ``` If it's not `200` (connection refused, 500, or anything else), the server isn't running or is broken — start it with `pnpm dev:local` and re-check until it returns `200` before driving the browser. (Plain `pnpm dev` works too, but `pnpm dev:local` brings up the full local stack.) - **Playwright MCP tools available.** They are deferred — load them first: `ToolSearch("select:mcp__playwright__browser_navigate,mcp__playwright__browser_snapshot,mcp__playwright__browser_take_screenshot,mcp__playwright__browser_click,mcp__playwright__browser_fill_form")` ## Step 1 — Find credentials Local dev uses the **default-auth** path (plain email + password on `/login`). Read it from the `.env` file at the repo root: ```bash grep -E "DEFAULT_USER|DEFAULT_PASSWORD" .env # DEFAULT_USER="admin@chorus.local" # DEFAULT_PASSWORD="chorus" ``` `DEFAULT_USER` logs in as a regular ...