Design 47 G: read "no holder" from the seat list, never from five minutes in the queue

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).
This commit is contained in:
2026-11-17 10:38:35 +01:00
parent d7321df3e5
commit 017e20504a
4 changed files with 20 additions and 10 deletions
@@ -1988,7 +1988,8 @@ ADR 0667's checks, of milestone G itself:
ending with that result and naming it in `shared`, a failing test failing once, and `pipeline-ended` counting the
module's tests once. A rerun that passes moves both artifacts' steps and the pipeline ends again; a runner
restarted during a run takes it up again; a replaced reader leaves the ask to the others; at the cap a step ends
`could not run` naming the fill; a second revision with the same digests runs a failed test again (whole, runner
`could not run` naming the fill; a second revision with the same digests runs a failed test again; a test run queued past five minutes with a
holder present is not failed (design 47 G A-466y) (whole, runner
and Go build module, mesh-delivery and mesh-catalog). Live: each module's test steps run once per level, read with
`runner_test_runs`. A reader no part ends raises `pipeline-stands` within five minutes of its last sign of life
(whole, watchman; design 47 G §732).
@@ -384,12 +384,14 @@ that round are written into the lines they name, here. Questions that an earlier
- §535 **A missing build seat and a seat with no holder, each read where it shows.** The runner reads that no build
seat serves an artifact's language from the catalog half of its revision view: no entry whose `acts`, the acting
rules of the seats it claims, hold a rule `build` with `on` naming that language (§323); the pipeline then ends
failed at once, naming the language and the missing build seat. It reads that a seat has no holder from the step
itself: an ask on that seat's work queue whose `step-started` is not heard within five minutes ends the pipeline
failed, naming the seat (§32). It reads neither from the seat list, which answers definitions alone (§527), nor
from any holding. Why: §32 already ends a pipeline whose step nothing starts, and the catalog half is the runner's
one view (develop question Q-RN7). How it is checked: whole (runner), a fixture language with no build seat ends at
once, naming it; a seat whose holder is stopped ends within five minutes, naming the seat.
failed at once, naming the language and the missing build seat. *Amended by A-466y (2026-11-17):* it reads that a
seat has no holder only from the seat list's holders, and a seat with none ends the pipeline failed at once, naming
it; an ask waiting for an existing holder is timed by §86's `build-capacity-waits` and A-466s's
`run-untaken-bound` (G-24 §720, §725), never by five minutes from the ask. Why: §32 already ends a pipeline whose
step nothing starts, and the catalog half is the runner's one view (develop question Q-RN7); a queued step ended
failed for "no holder" while its holder is present would say what is not true (principle 3). How it is checked:
whole (runner), a fixture language with no build seat ends at once, naming it; a seat with no holder in the seat
list ends at once, naming the seat; a step queued past five minutes with a holder present is not failed.
- §539 **The runner's tools are named `runner_`.** The runner's module, `mesh-delivery-pipeline`, names its tools with
the prefix `runner_`, so the design's `runner_catch_up`, `runner_waits`, `runner_release` and `runner_health`
stand, and its first-view tool is `runner_first_views`; `<module>_first_views` (§205) carries the prefix the
@@ -378,9 +378,13 @@ for several build maps is answered once, and the maps' names for it are given in
- §646 **The runner's bodies name `fingerprint`.** (§585) The runner's `step-ended`, pipeline and wait bodies name the
build-input fingerprint `fingerprint`, not `fp`, as §585 reads it. [mesh-delivery DQ-2.] How it is checked: unit
(runner's contract).
- §647 **The runner times an ask from `ask-taken`.** (§535, §602) §535's five minutes run from the ask until the build
seat holder's `ask-taken` (§602), which the runner consumes; `step-started` is the runner's own. [mesh-delivery
DQ-3.] How it is checked: whole (runner), an ask no holder takes ends its pipeline after the setting.
- §647 **The runner times an ask from `ask-taken`.** (§535, §602; A-466y) The runner consumes the build seat holder's
`ask-taken` (§602); `step-started` is the runner's own. *Amended by A-466y (2026-11-17):* §535's five minutes from
the ask until `ask-taken` go. A seat with no holder in the seat list ends the pipeline failed at once, naming it; an
ask waiting for an existing holder is timed by §86's `build-capacity-waits` and by A-466s's `run-untaken-bound`
(G-24 §720, §725), and from its `ask-taken` by its step's bound (A-466p). [mesh-delivery DQ-3.] How it is checked:
whole (runner), a seat with no holder ends the pipeline at once, naming it; an ask a present holder has not taken
past five minutes is not failed (test 109).
- §648 **A `take-in.taken` entry carries the pull request.** (§476, §542) An entry is `{module, commit, fingerprint,
repository, pull}`, the last two from a `merged` message and absent for a `pushed` one. [mesh-delivery DQ-5.] How it
is checked: unit (indexer's contract).
@@ -1603,3 +1603,6 @@ the principle that settles it, cited as "design 47 G A-n".
- **A-466w** (§733; principle 3) Test 108 checks that a reopened pipeline of a composition run says `pipeline-ended`
again, as test 109 does for test runs.
- **A-466x** (G-24; principle 8) G-24's lines read in number order, the watchman's line before the checks.
- **A-466y** (§535, §647, §86, A-466s; principle 3) "No holder" is read only from the seat list's holders: a seat with
none ends the pipeline failed at once, naming it; an ask waiting for an existing holder is timed by §86's finding and
A-466s's `run-untaken-bound`, never by §647's five minutes.