Design 47 H: lead answers H-A-85 and H-A-86 (bridge_heads, a run's source; the assigner's pins go) #758

Merged
mesh-tools merged 2 commits from design/47-H1-answers-20 into main 2026-11-20 02:22:58 +00:00
@@ -352,3 +352,11 @@ Where two preparers disagreed, the chosen one is named.
artifact references whose `package-published` (and, for a kind-3 edge, whose build step's passed end) was heard at
that pipeline's branch and source, written with the pipeline by compare-and-set, so the wait survives a restart (a
C-R2 field, the contracts developer's). P3, P1.
- **H-A-85 (contracts-indexer-bridge developer, 03:21)** (1) The bridge's read tool of its state `heads` is
`bridge_heads`, in the bridge's tools, answering the state's keys with each head, read-only (H-A-48). P4. (2) A run's
pipeline puts in `source` the newest source revision of its branch at the run's start (what the run is checked
against), its key being `<branch>.run.<run>`. P7.
- **H-A-86 (assigner developer, 03:22)** The assigner's pins of assignment graph revisions go whole (the state `pins`,
the tools `assigner_pins` and `assigner_unpin`, the hearer of the gate's pin events): nothing feeds them once the gate's
pin operations are gone (H-A-28, H-A-48). An assignment graph revision that is not current and that no want or
running build names is removed at the same judging moments as today, pins aside. P7; §764.