e2e-red-triage

1# e2e-red-triage — for the reds the preflight could not have predicted
2 
3Terms are as in `e2e-environment-preflight`: a **row** is one acceptance check in the test plan, a **red** is a row that failed or gave no answer, a **journey** is one end-to-end scenario made of rows, the **suite** is all the rows of a journey, and **preflight** is the set of environment checks that must be green before the first row runs.
4 
5**Never auto-triggered, and normally never needed.** One caller — the agent running the suite —
6and one moment:
7 
8> The `e2e-environment-preflight` checks were **all green**, and a row went **red anyway** — or produced a
9> null, an empty, a zero, or a silence nobody can yet explain.
10 
11If preflight was not green, the suite should not have started. If a red is an ordinary product
12failure with a clear cause, fix it and move on; this is not the ceremony for an ordinary bug.
13This is the residual after the gate has done its work — a small fraction, and one
14that shrinks every time move 3 is honoured.
15 
16## Why this needs its own protocol
17 
18The preflight handles the failures somebody could enumerate in advance. What is left is the class
19where **the failure produced nothing rather than an error, and the nothing appeared far from its
20cause.** One null can mean five different things across five runs of the same suite; "no results" can mean the query matched nothing or the search never ran.
21…