4 Commits

Include renames

Author	SHA1	Message	Date
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
jochen	f0fd7fe886	Leave a kept core move out of what a gate judges (issue 201, review 91) ... gatedSend took its judged moves from the record, so on a machine kept at a newer controller the gate judged the controller moving back to the record, read its own send's kept controller as a later build there, and was superseded with nothing judged. The kept moves are now left out there as in ungatedIn (withoutKept). The doc says the bus step keeps too, and the three store tests are listed.	2026-10-12 19:16:26 +02:00
jochen	d170491256	Keep the core over an older record instead of refusing the send (issue 201, review 90) ... Refusing the whole send wedged a machine whose gate put back the controller and whose put-back send was refused: every later automatic send there was refused, retried each tick, and held up every other walk. A send now composes the controller and the node-engine at the build the machine was last sent when the mesh's record is older, and carries the rest; nothing is refused or retried, and a plan whose own build is the older one ends with its gate superseded. A sent build that failed its gate is never kept, so the next send completes a put-back. The condition names the two ways out and clears on any send that carries the record, a person's push included.	2026-10-12 18:51:17 +02:00
jochen	9038d4b0d3	Refuse a send that puts the controller or node-engine behind its machine's build (issue 201) ... On 2026-10-02 a plan sent the control node a controller older than the one running there, whose seat row the newer build had widened; the older binary refused the row and the mesh went quiet for ten minutes. ADR 0185 took the outage out of it, and the race stayed open. Every send but a person's push now refuses a move of mesh-controller or mesh-host to a build asked before the one its machine was last sent (the builds' registration order, issue 219), whatever composed it — gated or not. A gate's own put-back is the one exception, for the modules it puts back, and says so in its send's scope. The refusal is the send's error, which the plan keeps as its note, and a warning condition on the machine, cleared by the next send there that carries no such move.	2026-10-12 18:21:17 +02:00