e2e-test-workflowlisted

# E2E Test Workflow Coordinate the existing E2E skills without copying or weakening their rules. Keep one primary owner for environment creation, execution, cleanup, verdict aggregation, and terminal reporting. ## Exact dependencies Use exactly these component skills: - `e2e-scenario-author` - `e2e-runner` - `playwright-e2e` - `e2e-report-renderer` Treat `e2e-test-workflow` as the orchestrator; never invoke it recursively. Do not replace a missing component with generic reasoning or a different test framework. Load each selected component's `SKILL.md` before applying that phase, and let the component's normative rule IDs govern its own artifacts and behavior. ## Input contract Freeze and report: - repository root and immutable source revision - requested scenario IDs, areas, test symbols, or `all` - requested lanes: `catalog`, `api-integration`, `browser`, `html-report` - whether catalog generation or refresh was explicitly authorized - whether persistent JSON, Markdown, or HTML output was explicitly requested - supplied QA browser handoff and its case IDs Apply these defaults: - Select `api-integration` for a general E2E workflow request. - Select `browser` only when explicitly requested, or for an `all`/`full` request when a bounded Playwright profile proves that Playwright is configured. Record `NOT_APPLICABLE` when an `all`/`full` request has no Playwright setup. - Select `catalog` generation only for an explicit generate, refresh, or full-workflow request. A