Send an approved settings layer by a walk at once, so the operator's Approve takes effect (issue 641, ADR 0344) #305

Merged

mesh-admin merged 4 commits from fix/641-an-approved-setting-is-sent into main 2026-10-13 17:22:20 +00:00

Conversation 8 Commits 4 Files Changed 6

+946 -17

4 Commits

Author	SHA1	Message	Date
jochen	8bbb1b19ae	A settings gate keeps the module's build, and a walk that cannot keep a build fails (issue 641 review) ... Without a build on the gate, a merge walk sending the machine a new build of the module was read as the settings send's own report. A refusal for a last send not known, or a kept build gone, never clears, so retrying it every tick held the walk of waiting builds; it now fails the walk with why. Every failure names the machines passed over as away (ADR 0344 §6).	2026-10-13 17:33:07 +02:00
jochen	e32ca00aed	Test that a settings send moves no ungated build waiting on its machine (issue 641, ADR 0344 §3)	2026-10-13 16:55:49 +02:00
jochen	1219ec8229	A settings walk sends the layer alone, every build kept, and stops before a data move (issue 641, ADR 0344) ... A judged send carries what waits on its machine, which would have released builds held after a failed walk without a person's word. The settings walk now keeps every build of its machine, refuses a send that would move a running module's data, and never says delivered when it reached no machine.	2026-10-13 16:50:10 +02:00
jochen	e324f5d821	Send an approved settings layer by a walk at once, so the operator's Approve is the act that takes effect (issue 641, ADR 0344) ... The warrant set the layer and left the push as a second act nobody took: the operator approved a betterbird change on Telegram and nothing reached g14. Now the warrant opens a settings walk: the machines the layer reaches, one at a time, the module judged on each at its gate, its end told once through plan-moved. The ask and the proposer's answer say so instead of naming push.	2026-10-13 16:39:47 +02:00