e2e-runnerlisted

# E2E Runner — Execution & Reporting Protocol ## Purpose Run a catalog or existing integration suite only when its framework, run-owned infrastructure, and verification evidence can be proven. Default to terminal-only results and remove transient artifacts; create a report only when explicitly requested. ## Prerequisites Before detailed execution, read the complete [execution contract](reference/kb/operating-contract.md) and run `node scripts/detect-test-profile.js <repository-root>` once for bounded discovery. Select only the needed topic: | Evidence or task | Read next | |---|---| | Testcontainers topology, data ownership, or bootstrap | [Environment and data](reference/kb/test-environment-and-data.md) | | HTTP scenario assertions | [HTTP API E2E](reference/kb/http-api-e2e.md) | | Kafka/outbox or eventual consistency | [Async execution](reference/kb/async-and-eventual-consistency.md) | | Persistent body/log artifacts | [Masking and evidence](reference/kb/pii-masking-and-evidence.md) | | Build-task or CI integration | [CI integration](reference/kb/ci-integration.md) | | Timing/order diagnosis | [Flaky tests](reference/kb/flaky-tests.md) | Read [principles](reference/principles.md) only to resolve a rationale question, and use [the KB index](reference/kb/INDEX.md) only if these routes do not identify the needed topic. Neither is a blanket preflight dependency. The complete RUN contract remains mandatory; one owner still controls the full lifecycle. ## Instructions 1.