3 Commits

Include renames

Author	SHA1	Message	Date
mesh-adminandClaude Opus 5.5	02b542a059	Keep a layer's placement beside it, and say the layer whole (issue 651) ... The settings verb's path splits a layer it is given into its config values and its placement, so what a person types still works; a layer reads back and goes into the history whole. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>	2026-10-14 00:42:37 +00:00
jochen	cc11de2513	A trusted setting is proposed through the settings verb and set only on the operator's warrant (hq ADR 0277) ... Issue 339 made every trusted setting the controller's terminal's alone, so an agent could only hand the operator a line to type at the control node. Now anyone the bus admits may PROPOSE a layer: settings propose keeps the proposal in the controller's own asks (the asked bucket, which the controller alone writes), judged as settings set judges, and asks the operator on the operator channel at the level approve with every key, its exact new value (in its shape where a path or an address may not leave the mesh), the was of a changed key, the removed keys and the layer's fingerprint. The serving controller sets the layer on the warrant alone: once, for the ask it holds, only when the record's values still digest to what the option bound and the layer is still the one shown, with the terminal's judgement and history, and keeps who approved it beside the layer, which settings says back (migration 0090). Decline, expiry, a cancel, a replacement or the router's refusal discard it; nothing is asked when no router, no grant or no channel can carry it. settings proposals lists them. The push afterwards is a separate act.	2026-10-10 14:42:40 +02:00
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