e2elisted

# E2E Quality Operate the project's existing E2E capability and help it grow toward comprehensive coverage over time. Start from project-owned tests, fixtures, conventions, and entrypoints. Assessment is read-only; when the user explicitly asks to add or fix coverage, change the project's E2E assets under its development rules and validate them through the canonical entrypoint. Comprehensive coverage is the long-term direction, not a requirement to close every gap in one task. ## Keep the owners separate 1. Treat case-harness or another framework as infrastructure that may provide runners, lifecycle, assertions, evidence, and verdict primitives. 2. Treat the project as owner of its E2E cases, fixtures, adapters, acceptance criteria, canonical commands, and operating notes for environments, retries, cleanup, and evidence. 3. Treat this skill as the operator that discovers and runs those assets, interprets their evidence, exposes remaining coverage, and helps add bounded project-owned cases when requested. Do not call a lower-level framework directly when the project exposes a wrapper. Framework code without runnable project-owned tests is `no_capability`, not an executable E2E suite. ## Discover and select Read the project's AGENTS.md and README first, then locate: - the business or system boundary the project intends E2E to verify; - E2E, acceptance, integration, or system-test directories and their nearest operating notes; - the canonical command, exact case