4 Commits

Include renames

Author	SHA1	Message	Date
jochen	4499e85476	No change to a machine takes effect unseen (hq ADR 0217, to-be 44) ... Two incidents had one shape: a change took effect that nobody saw first (hq issues 241, 304). Three guards, each silent when nothing is at stake: - settings show [--history], and a set that answers each key it adds, changes and removes, and refuses a removal unless --replace; the replaced or cleared layer is kept in settings_history, in the same transaction as the write (migration 0078). - every send keeps a summary of what it sent (no file content), plan <node> --diff compares with it, and push with no machine is refused unless --all. - a push that would give a running container's mount another host directory holds that machine, naming the module, mount and both directories, until push <node> --move <module>; a named push's cascade is held the same way. Rebased onto main and fitted to it: the hold runs before the push says what it recreates, a whole push still says so first and leaves machines waiting for a gate, the verb's push with no machine is still --behind and a push still needs why. The verbs take plan diff, settings replace and history, and push move beside a machine, each refused where it cannot take effect.	2026-10-08 01:44:43 +02:00
jochen	ed90771382	Send the bus's machine before the grants, and only when its user list moved (hq issue 249) ... Grants first could hold back the very declaration that lets the controller issue them. The holder now goes first, then buckets and memberships, then the rest; a membership that fails holds back only its own machine, and an announcement whose send stopped at its grants is asked again. Whether the holder must go first is read from a digest of the user list it was last sent, not its whole declaration. Migration renumbered to 0058.	2026-10-05 18:17:52 +02:00
jochen	22660dc274	Issue grants before code, and the bus's machine first (hq issue 249) ... A module's new state reached every machine before the permissions to use it, which came only with a later push. Memberships and buckets now go before declarations, the machine holding mesh-broker goes first when its user list must change, and a grant that fails sends nothing and is an error so the rollout is retried.	2026-10-05 18:17:52 +02:00
jschoubben	2e6b9d30bd	Give a cascade round's hold back on every return, a body that cannot be marshalled included (hq ADR 0100)	2026-09-22 18:31:00 +02:00