The seat list answers definitions alone (§527); the holders are the seat mesh-module-assigner's
view seat-holders, which the runner now consumes (A-466z).
A test run queued behind the build capacity with its holder present was ended failed for no
holder after five minutes, which is not true; the queue is §86's finding's and the untaken
bound's to time (A-466y).
A run's bound times owed progress from the ask's taking, a run never taken ends at a bound of
its own, blame-tries travels in the request, the hand order goes, a test run's output lives
with its key, stands names what a reader waits on, and G-24 reads in number order
(A-466p to A-466x).
A bound counted from the asking would end a run that only waited in the queue as could not
run, which is not true; the queue is the build-capacity finding's to time (A-466n).
The lead's answers A-466m to A-466o: the assigner names the composition runs' asks in its
step-progress, each run's bound is a setting, and since the watchman on main times only a
build seat's running ask, it now times every pipeline step that reads a run, so a reader no
part ends is said as pipeline-stands.
The four reviewers by architectural domain found results crossing candidates, a read of a
build seat's state, fixed durations and caps, unstated seat contract fields and a rerun rule
that differed between the two kinds; the lead's answers A-466 to A-466l settle each. The
lines move to a file of their own, G-24, so G-2 stays under its bound. The split of the main
file and G-22 waits until after G, as the operator decided at 10:31 CET.
The coordinator's answers of 2026-11-17: a step left reading a failed result would say what
is no longer true, so a rerun of a test run moves all its readers; the node-engine's
differing input bytes and the split of design 47's main file wait until after G.
G's live delivery of 2026-11-17 composed each machine once per pipeline (96 runs for one
revision, 80 more on rerun, the assigner's inputs state at its cap twice) and ran the same
tests once per artifact. Pipelines of one candidate now read one composition run per
machine, kept by the assigner, whose verdict names the modules it blames so one module's
fault fails only its own pipelines; test steps naming the same packages read one test run,
kept by the runner. The operator, 2026-11-17 about 10:20 CET: "In G, now".