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. Read [Quality concepts](../../CONCEPTS.md) before discovery or interpretation. It defines ownership, subject identity, execution facts, evaluation, comparison, and result states shared by the skills. The project owns E2E Cases, fixtures, adapters, acceptance criteria, canonical commands, and operating notes. Preserve its test grouping and call evidence: a CaseRun may contain several OperationRuns. Framework code without runnable project-owned tests cannot establish live coverage. ## 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 registry or listing mechanism, configuration, fixtures, and recent result artifacts; - the test-process revision and the identity of the system under test, including the requested target or environment, where the runner executes, and how it