5 Commits

Include renames

Author	SHA1	Message	Date
jschoubben	73a31eb205	Judge each move against what the node runs, again when its have or the module's policy changes; carry the operator's keys in the node-engine's composition (issue 1945, B11, B12) ... The assigner holds a move of a module of policy record from the judgement beside its digest, so it is judged by ADR 0377 §3's tests against the composition the node's have names, a held one never taking its place, and written again when the have changes or a person sets the policy (ADR 0539 clauses 2 and 14). The node-engine's own file operator-keys, from its setting operator-signers, carries the operator's public keys (clause 3).	2026-10-24 17:14:41 +02:00
jschoubben	aee0a2718f	Write each module's composition per node, signed, with its digest and the move's judgement beside it (issue 1945, B1) ... Every act that sent a declaration now writes compositions instead, by compare-and-set under the lease, and a module's compositions are kept for its five newest fingerprints and whatever its want or have names (ADR 0539 clauses 1 to 5 and 14). A module the mesh provides itself, which no want can name, rides in the node's own.	2026-10-24 16:54:11 +02:00
mesh-tools	d984816844	Feature 57 (config and provisioning): release mesh-controller, the reviewed release branch merged with main, on top of main	2026-10-16 08:28:38 +00:00
jschoubben	a330c564ba	Say a module assigned and left out of its machine's composition as a condition (issue 380) ... A push leaves out a module whose settings do not compose and sends the rest, which is right, but only plan said so: nfs-server ran nowhere for days while the operator believed it ran. The self-check now raises needs-operator for a setting nobody gave, naming the setting and the command, and left-out for any other cause; both warnings, cleared once the module composes or is unassigned. status and node show list the same modules as assigned, not applied.	2026-10-11 04:43:58 +02:00
jochen	8bcf787258	Raise a machine's network from what its engine says, once (hq ADR 0241) ... A VPN client rewrote the laptop's resolver file and nothing said so. The engine now states its machine's networking; the controller keeps it with the machine's health (migration 0077) and raises the rewrite as its own finding naming the writer, the machine's own faults as machine.<m>.network, and what several machines cannot reach once, there. The gate waits on a rewrite it did not make rather than putting back a good build.	2026-10-07 18:52:16 +02:00