e2e

# E2E Tests ## Execution Context Write and run E2E coverage directly in the primary conversation. For a cost-controlled feature workflow, the user switches that conversation to the lower-cost implementation/test model before this phase. Write E2E tests using TDD (Red-Green-Refactor). Always run the tests you create and watch them fail before implementing. ## Related skills - **`/tdd`** — Follow the Red-Green-Refactor cycle when writing tests. - **`/pr-fixup`** — Use after the PR opens only for CI or reviewer findings. - **`/playwright-cli`** — Interactive browser automation. Use to validate features against the dev server before writing tests, and to debug failing tests with `--debug=cli`. ## References Load `references/fixture-state.md` for capability-readiness and remembered workflow fixture rules. Load `references/ui-state-and-cleanup.md` for lifecycle, WebSocket, terminal, Dockview, and sidebar/context-menu rules. ## Location `apps/web/e2e/` ``` apps/web/e2e/ ├── fixtures/ │ ├── backend.ts # Worker-scoped backend + frontend process │ ├── test-base.ts # Extended fixture (apiClient, seedData, testPage) │ └── office-fixture.ts # Office fixtures (officeApi, officeSeed with workspace+agent) ├── helpers/ │ ├── api-client.ts # HTTP client for seeding data (read for available methods) │ └── office-api-client.ts # Office-specific API client (onboarding, issues, agents) ├── pages/ # Page objects (read for available p...