e2e-pipeline

Verifies documentation accuracy by executing live probes against plugin skills. Receives behavioral claims extracted from docs, runs each probe command, compares output against expected signals, returns structured pass/fail report. Dispatched by e2e-doc-sync skill during Phase 4 (Live Probe).

Opens a browser, executes reproduction steps, and collects debug observations (console logs, JS errors, network requests, screenshots). Produces a structured report.md. Runs in isolated subagent context to keep verbose browser data out of main conversation. Never modifies code — observation only.

Adaptive flow validator. Runs E2E flows in browser, auto-repairs selector/URL/flow issues, enriches assertions, and produces PR-ready reports. Two rounds — Round 1 fixes, Round 2 captures clean evidence (screenshots + trace). Operates in subagent context or as a persistent teammate with multi-turn round control.

Autonomous flow YAML generator. Analyzes codebase context and mapping files to produce E2E test flows without browser interaction. Supports browser flows, CLI-only flows (Execute external), cross-boundary flows (browser + API + Verify external), and smoke tests. Never opens a browser.

Autonomous UI element mapper. Explores web pages using agent-browser CLI and generates/updates YAML mapping files for E2E testing. Supports full exploration, incremental single-page update, and browser-only discovery mode. Returns page inventory with elements, selectors, and unexplored areas.

Use when compiling E2E flow YAML files to standalone bash test scripts — invoke with "/e2e-compile <flow-name>" or "/e2e-compile --all". Triggers on "/e2e-compile", "compile flow", "e2e compile", "compile the flow", "generate test script", "compile e2e", "recompile flow".

Use when debugging frontend runtime bugs by injecting console.log, observing in browser, and auto-cleaning up. Triggers on "e2e debug", "e2e-debug", "debug in browser", "inject logs", "runtime debug", "why is this empty", "data shape bug". Also triggered by /e2e-dispatch menu or systematic-debugging experiment dispatch.

Use when the user explicitly invokes /e2e-dispatch or asks for the E2E operations menu without specifying a particular operation. This is a unified router — for specific operations, prefer e2e-test, e2e-map, e2e-walkthrough, or e2e-skill-ops directly.

Use when plugin documentation needs updating after feature changes, when verifying existing docs accurately reflect actual skill/agent behavior, or for periodic documentation maintenance. Scans source code with diff-aware detection, enriches with usage history from journal and memory, writes or updates docs, then verifies accuracy via live behavioral probes. Triggers on "sync e2e docs", "update e2e documentation", "doc sync", "e2e-doc-sync", "check doc coverage".

Use when generating E2E test flows from plans, specs, or PRs, verifying flows in browser or CLI, running smoke tests across all mapped pages, or recording backend/API verification with asciinema. Supports browser UI flows, CLI-only flows (Execute external), and mixed flows. Triggers on "e2e flow", "generate flow", "create flow", "verify flow", "draft flow", "smoke test", "e2e smoke", "write a flow", "produce flow", "validate flow", "flow from plan", "cli flow", "backend e2e", "api test flow", "cli recording".

4 hooks across 2 events