e2e-testlisted

# E2E Test Orchestrator Validate that an application actually works by testing real user journeys — in a browser for frontends, via HTTP for backends. ## Design Principles 1. **Spec-aware:** If OpenSpec artifacts exist, use them as ground truth for what to test. Otherwise, discover from codebase. 2. **Sub-agent per journey:** Each user journey gets its own Task agent to keep context manageable. 3. **Self-healing:** Fix critical blockers (max 3 attempts per journey), document non-critical issues. 4. **Two modes:** Frontend (browser) and Backend (API). Auto-detect or override with `--mode`. --- ## Arguments Parse the user's invocation: | Arg | Description | Default | |-----|-------------|---------| | `--mode` | `frontend`, `backend`, `both`, `auto` | `auto` | | `--spec` | Path to OpenSpec change directory | Auto-detect | | `--base-url` | Application base URL | `http://localhost:3000` (frontend) / `http://localhost:8000` (backend) | | `--skip-start` | Don't attempt to start the dev server | `false` | | `--report` | Export markdown report to path | *(none — console only)* | --- ## Phase 1: Pre-flight ### 1.1 Platform Detection Read project config files to understand the stack: ``` Read: package.json, pyproject.toml, Cargo.toml, go.mod, Makefile, docker-compose.yml ``` Extract: - **Language/framework** (Next.js, FastAPI, Express, Django, etc.) - **Dev server command** (from `scripts.dev`, `[tool.taskipy]`, Makefile, etc.) - **Port** (from config or convention) - **Dat