4 Commits

Include renames

Author	SHA1	Message	Date
jochen	95ce92c62f	ADR 0221: a push sends no build a policy or a plan holds back, except to the machine it names ... A named push's cascade sent every machine a build held back by `record` or by a plan waiting on its first machine, so a change meant to be walked through the mesh one machine at a time reached all of them at once (issue 259). Records the decision, narrows ADR 0083's flush with a dated pointer, amends to-be 30, and locates issue 259 in the controller.	2026-10-05 22:23:29 +02:00
jschoubben	05857f71f0	Accept ADR 0083 — one push leaves the mesh consistent	2026-09-20 12:52:55 +02:00
jschoubben	0d5693cc2c	ADR 0083: the cascade compares against what was last sent, not a snapshot	2026-09-18 02:38:00 +02:00
jschoubben	9fd7e6c458	ADR 0083 proposed; 057/058 diagnosed and located ... One push leaves the mesh consistent (the 057 decision, proposed for acceptance); the shared runtime waits for its broker (058). Fixes on mesh-control fix/one-push-is-enough and mesh-tools fix/the-runtime-waits-for-its-broker; the built-store-cross-node bed enforces both.	2026-09-18 02:10:01 +02:00