Merge pull request 'Design 47 H: lead answer H-A-72 (the runner's and mesh-wants' seat forms)' (#745) from design/47-H1-answers-7 into main

This commit was merged in pull request #745.
This commit is contained in:
2026-11-20 01:52:59 +00:00
@@ -284,3 +284,12 @@ Where two preparers disagreed, the chosen one is named.
asker judgement in `mesh-delivery-sdk/steprun` (H-A-41) is the contracts-indexer-bridge developer's subtask, since
that package is mesh-delivery's shared code and it already writes there; the three build modules' wiring stays
mesh-catalog's BUILD-1. The lead's order of work.
- **H-A-72 (contracts-indexer-bridge developer, 02:53; the runner's and mesh-wants' seats)** (1) The pipeline value:
`group` goes; `module`, `commit`, `fingerprint`, `repository`, `version`, `widens`, `tests` and `over-budget` move into
each mover; `run`, `published`, `unlogged` and `end-count` stay on the pipeline (P7). (2) The runner's state `queue`:
`queue.next` and one key `waiting.<sequence, 20 digits>` with value `{pipeline}`, so the lowest sequence is read by key
order (P1). (3) `wait-held` and `wait-ended` move to the one subject form `<branch>.<source>`, the body naming the
module for a step's wait (P8). (4) The step events and `run-started` keep `<module>.<branch>.<commit>`, the
commit-or-group token becoming `<commit>` (P8). (5) `pipeline-ended` carries per mover its step results as a list of
step results, each naming its module (H-A-35, P10). (6) The tier end is a second event of the seat mesh-wants,
`pipeline-wanted.<branch>.<source>` with `outcome`; `wanted` stays per node and module (P8); H-A-56 reads so.