2 Commits

Include renames

Author	SHA1	Message	Date
jschoubben	e1367d185a	Send the bus's user list alone before a walk's gate, so a new grant is on the bus when the first machine is judged (issue 490) ... A walk left the machine holding the bus out of a gated send whenever a build waited there for that same gate, so a module's new health tool was refused by the bus on its first machine and the gate could not pass. The grants step sends that machine its declaration with every build kept, before the first machine's send; plans and the change plan say it.	2026-10-11 19:01:41 +02:00
jschoubben	e6e1e3bc89	A gate judges its own send and the build it sent, and never puts the controller back behind its store (hq issue 352) ... On 2026-10-09 a release's gate on the control node read the machine's report against a newer send another plan had just made there, failed three builds the machine had reported healthy, and put them back on every machine to a controller older than the store's schema; that controller then passed the newer plan's gate from its own health. - A gate keeps what its send carried (digest, sequence) and reads the report against it; a report on the last send is on it too. - A gate judges only the build the machine was last sent: another build there supersedes the judging — no verdict, nothing put back. - A controller is told its build (MESH_CONTROLLER_VERSION, ${version} in a process's env) and records how far it reads the store's schema; a put-back to a build that reaches less, or never said, is refused and the current build kept, said as urgent. - A release's open gate holds other sends of its modules there, and a plan's own first send waits on it.	2026-10-09 17:15:40 +02:00