docs(ci-reds): bound R7 window without misnaming its endpoint

The four-run observation window contains two green in-gate runs, so it
cannot be described as ending at the first green. Name it directly as
the first four in-gate runs; the timestamps continue to define the
boundary exactly and later verification gates remain excluded.
This commit is contained in:
Levi Neuwirth 2026-08-29 19:15:41 +02:00
parent 054a427e74
commit 756c2b87df
No known key found for this signature in database
1 changed files with 2 additions and 2 deletions

View File

@ -561,8 +561,8 @@ isolate an in-gate cause. All these runs establish is that none of the
four conditions **by itself** reproduces the failure. They do not show four conditions **by itself** reproduces the failure. They do not show
that any of them is uninvolved when the gate supplies the rest. that any of them is uninvolved when the gate supplies the rest.
**THE OBSERVATION WINDOW IS BOUNDED, deliberately.** It is the four **THE OBSERVATION WINDOW IS BOUNDED, deliberately.** It is the first
in-gate runs of 2026-08-29 up to and including the first green — four in-gate runs of 2026-08-29 —
`20260829T144541Z`, `T150011Z`, `T152024Z`, `T152824Z` — plus the 17 `20260829T144541Z`, `T150011Z`, `T152024Z`, `T152824Z` — plus the 17
out-of-gate runs taken between them. **Later head-exact verification out-of-gate runs taken between them. **Later head-exact verification
gates on this lane are NOT part of it and do not move these numbers.** gates on this lane are NOT part of it and do not move these numbers.**