5 Commits

Include renames

Author	SHA1	Message	Date
mesh-tools	3208aa0461	Take the catalogue, overlay and validator from mesh-sdk in cmd/mesh-controller, p to s (issue 1381, 3 of 6 import swaps)	2026-10-20 08:24:43 +00:00
jschoubben	66dc501fc4	Split the unit level from the integration level in cmd, builder, link, catalogue, inventory; cheap fixtures for the archive-entry bound, the registry waits and the catalogue copy (issue 895)	2026-10-17 21:32:23 +02:00
jschoubben	5b455b8a24	Keep the first-machine gate behind a switch for walks begun before hq ADR 0360, and test both paths	2026-10-14 19:35:07 +02:00
jochen	9a7ae131cb	TestReplay336 reads the bus call in its mesh form ... The previous commit named the upgrade as a mesh call, and the replay still looked for the command-line words; it now asserts the seat and the upgrade, as any wording of the call says them.	2026-10-09 03:08:21 +02:00
jochen	1fdc68a8aa	Tell the operator at once when sends wait for the bus's planned step, and say it before the merge (hq issue 336) ... For 28 minutes on 2026-10-08 every send to the control-node was refused for a new bus build that only a person's bus upgrade moves, and no condition said so: the refusal lived only in each walk's note, and S3 would have called it lateness after half an hour, in words that named neither the bus nor the verb. - Row S17, bus.<module>.step-waiting: raised on the first watchdog tick after a walk's send is refused for the bus, for the operator, naming the machines, what waits, the bus build from and to, since when and mesh-controller.bus upgrade. It clears once the bus's machine runs the build the mesh holds. - S3 leaves out a walk held only by the bus's step. - A change that builds the bus says in its delivery plan and summary (which mesh/merge-gate carries) that merging it needs a person's bus upgrade, and that nothing else reaches its machine until then. - TestReplay336 fails on the commit before and passes on this one.	2026-10-09 02:33:57 +02:00