e2e-environment-preflight

1# e2e-environment-preflight — the gate that runs before the first row
2 
3**Never auto-triggered.** Named callers only:
4 
5| Caller | Moment |
6|---|---|
7| A requirements document or test plan | once end-to-end proof is required and the document names an external system |
8| A task brief | before staffing any end-to-end journey |
9| `e2e-red-triage` | when a red turns out to be environmental and owes a new check |
10 
11This skill is self-contained: the trigger and the three artifacts.
12 
13Terms: the **owner** is whoever owns the work, usually the user; a **row** is one acceptance check in the test plan; a **journey** is one end-to-end scenario made of rows; a **red** is a row that failed or gave no answer; the **suite** is all the rows of a journey.
14 
15**Each repository binds this locally.** A repo-level `e2e-environment-preflight` names its own systems, its
16own primer directory, its own evidence paths, and its own configuration decisions. This file is
17the contract; the local one is the address book. If the repository has no local binding, the
18first journey that needs one writes it.
19 
20## The trigger, as an operational test
21 
22> The preflight is required when **any acceptance row's evidence comes from a system outside the
23> repository under test** — a running service, a host, a browser session, a live model endpoint,
24> an installed agent. Rows whose evidence is produced entirely by code in the repository do not
25> trigger it.
26…