jschoubben
4e14ef9835
mesh/merge-gate pass: builds mesh-delivery → novox; no bus step; every machine composes with the change as it did without (4 of 4 compose)
mesh/repo-check pass: its merge-check.sh passed, each part in its toolchain: merge-check.sh (go), merge-check-typescript.sh (typescript)
mesh/delivery delivered
A build the controller held back for a person reaches its machines by a backlog walk on the operator's word, which credits the delivery that published the build one step per machine and never the walk's own "every machine running it". Its last record keeps no gate, only the machines it is done on, so the credited steps stayed judging for ever, and `covered` read only the aggregate steps, so the held merge had no end but a person's wrong act (the catalogue's #125, held 28 hours after hq ADR 0270 went live). A finished backlog walk now passes the steps it carried on the machines it is done on; `carries` counts a module as sent everywhere when a passed step stands on every machine the held delivery's plan sends it to; and a walk that carried a step still judging is asked for by its id, since one that ended before the holder's restart may be older than the ended walks the controller lists back. Three tests fail before and pass after.