Design 47 H: H-A-83, a run on request is one pipeline; kind-3 edges wait on the build step's end

Claude-Session: https://claude.ai/code/session_01JG73KHUnBze48rdua8u2sy
This commit is contained in:
2026-11-20 03:18:48 +01:00
parent 0631f43f25
commit ae7fc40ad4
@@ -341,3 +341,10 @@ Where two preparers disagreed, the chosen one is named.
place: the fill of delivered versions into the graph's edges (versions_edges, versions_fill_edges) served the
assigner's holds, which are gone; the kind-2 edge stays as a declaration (H-A-51's tiers), its "delivered" fact is
nobody's to keep. The indexer's consume of `mesh-wants.version-delivered` goes from its manifest. P7; ADR 0682 §9.
- **H-A-83 (runner developer, 03:19)** (1) A run on request is one pipeline per run with the named commits' modules as
its movers (one take-in, one pipeline, ADR 0682 §6; the run delivers nothing), keyed `<branch>.run.<run id>` in the
runner's state `pipelines`: the seat gains that key form (a small commit C-R2 by the contracts-indexer-bridge
developer); H-A-52's "per member" is corrected to this. P8. (2) Inside a pipeline, a mover's build waits on a kind-1
edge for the From mover's `package-published`, and on a kind-3 edge (a build module, an image base, which publishes no
package) for the From mover's build step ending passed, which the runner hears as its own step end; toolchain edges
first. P3, P7.