Triage E2E Test

Start from a test name (not a CI run), find its recent distinct failure modes, investigate one, falsify a root-cause mechanism, and land on fix-the-test vs. file-a-bug with the action to match. This is an orchestrator: deterministic work lives in scripts/, and detailed procedures live in references/ that you read only when a stage needs them.

When to use

• You picked up a specific e2e test already failing or flaking in CI, and want its history and evidence without hunting for the runs by hand.

Non-negotiable rules