novox/mesh-controller

Resolve a config value from four sources: default, mesh config, node config, the module on the node (hq issue 630) #303

Closed

mesh-admin wants to merge 8 commits from fix/630-config-values-from-four-sources into main

Author	SHA1	Message	Date
mesh-admin	660649eeed	Test config end to end into a composed file, and hold the settings tests to no whole-mesh module layer (hq issue 630) mesh/delivery stopped: the pull request closed unmerged Details mesh/merge-gate out of date: judged against trunk 6f1a05366c1d, the trunk is now 8ddf8b700558; judged again on a recheck or when it is merged Details mesh/repo-check out of date: judged against trunk 6f1a05366c1d, the trunk is now 8ddf8b700558; judged again on a recheck or when it is merged Details	2026-10-13 13:19:30 +00:00
mesh-admin	c9b63f61bd	Serve config as a seat verb, and say each value's source as one of the four (hq issue 630) The listings named a node's own value "the node", which now could be node config; they say "<module> on <node>" for the module's own value instead.	2026-10-13 13:18:33 +00:00
mesh-admin	3f9b935c25	Keep the list from a catalogue build, and carry it and mesh and node config through the facts and the gate (hq issue 630) The merge gate must compose with the same config the mesh holds, and judge a catalogue change against the list it brings.	2026-10-13 13:17:48 +00:00
mesh-admin	0c31ca0eaf	Add the config command: mesh, node and module values in one call, with why and history (hq issue 630) One place to set each of the three sources over a default, refusing what is not a predefined key and a module value without a node, recorded in the hand-act log like any act by hand.	2026-10-13 13:16:54 +00:00
mesh-admin	ea4c318404	Test the four sources, the refusals and the move of whole-mesh module layers (hq issue 630)	2026-10-13 13:15:46 +00:00
mesh-admin	df5254f308	Keep mesh and node config with their history, and move whole-mesh module layers onto each assigned node (hq issue 630) An assignment is one module on one node, so a new whole-mesh layer is refused and the ones held are laid under each assigned node's layer, every replaced layer kept, so no machine composes differently.	2026-10-13 13:14:42 +00:00
mesh-admin	fba6a7c454	Carry the catalogue's predefined.json with a build, and declare the config verb (hq issue 630) The controller only learns manifests through builds, so the list of predefined keys travels the same way: the builder reads it at the catalogue's root, judges the manifest against it and hands it on.	2026-10-13 13:13:24 +00:00
mesh-admin	3d16515771	Declare preferences with a type and a predefined key, and lay mesh and node config between default and node (hq issue 630) A preference may fall back to one reviewed mesh-wide or node-wide value instead of a module layer for the whole mesh; like a default, config fills ${setting:} only.	2026-10-13 13:08:37 +00:00