test-setuplisted

Scaffold the project's test infrastructure from the approved QA plan before any feature tests are written. Non-autonomous: present the full plan, get approval, then execute. Never install packages or write config files without sign-off. ## Phases 1. **Load context** — read `docs/specs/qa-plan.md` to understand the chosen pyramid and tooling decisions. If the file is missing, stop and direct to `/qa-plan`. Also read `package.json` and any existing test config files to avoid duplicating setup. 2. **Present the plan** — show the user the EXACT commands and files that will be created, including: install commands for Vitest, `@testing-library/react`, `@testing-library/jest-dom`, `@playwright/test`, and any supporting packages (`jsdom`, `@vitejs/plugin-react` — or `@vitejs/plugin-react-swc` for Next.js projects that use the SWC compiler; both require `jsdom` as the Vitest test environment, etc.); a Playwright browser-binary install step (`npx playwright install --with-deps`) that runs after `@playwright/test` is installed, so that `npm run test:e2e` does not fail with a missing-browser error; config files to be written (`vitest.config.ts`, `vitest.setup.ts`, `playwright.config.ts`); `package.json` scripts to be added (`test`, `test:watch`, `test:e2e`); and the CI test step (e.g. a GitHub Actions job snippet). Under `full`, confirm each category; under `lean`, one confirmation for the whole plan; under `solo`, proceed directly. Get explicit approval before running anything. 3. **Ap