4 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
jochen	4354d9d7c7	Name the bus upgrade as the mesh call a person makes, and say a same-source rebuild needs no step (review of #173) ... The condition and the plan named the verb in command-line form; the operator reaches it through the mesh MCP server, so it is written as that call. A rebuild of the same source moves nothing (issue 280), which the plan cannot know before the build, so its line says so.	2026-10-09 02:54:23 +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
jochen	3d05d74400	Publish only a commit on its module's trunk; post a pull request's change plan (hq ADR 0238) ... One commit, one plan: a commit off the trunk — a pull request's head, a branch built by hand, a rebuild or replay of one — is for checking. The build seat reads from its clone which branches hold the commit, and the controller records and never registers a build whose commit is not on the branch the module follows (the repository's default for a new one), so nothing off the trunk can be sent. A pull request's check now carries its change plan, computed by the planner: what a merge would build in which order, what each machine would receive, and what is not an ordinary send — the bus step, a module waiting for a person, a provider's consumers.	2026-10-06 22:49:55 +02:00