Fill a preference's ${setting:} from its manifest default (hq ADR 0262) #153

Merged

mesh-admin merged 4 commits from feat/setting-defaults into main 2026-10-08 15:54:34 +00:00

Conversation 6 Commits 4 Files Changed 21

+1179 -31

4 Commits

Author	SHA1	Message	Date
jochen	af63b233db	Leave out a module whose stored manifest has an unknown field, and raise it (hq ADR 0262 review) ... A key dropped silently ran a module without what its manifest says, and a key inside a block still failed the whole catalogue. Judge a key by what it is about, and narrow the listing to one machine.	2026-10-08 17:34:53 +02:00
jochen	f5680ba8da	List every module's preferences in the settings verb (hq ADR 0262) ... One verb is the interface to every preference, so no module builds a settings tool of its own: each key, its default and why, and every assigned machine's value with its source.	2026-10-08 17:24:32 +02:00
jochen	76babaea52	Read stored manifests leniently and mark the defaults layer (hq ADR 0262 review) ... A strict read of the stored catalogue fails every plan and send once a manifest uses a field an older controller lacks; registration stays strict. A node named default lost its layer to the name check. Judge the operator's keys by whole words, and scan a default under any key.	2026-10-08 17:24:32 +02:00
jochen	e41b78cd77	Fill a preference's ${setting:} from its manifest default (hq ADR 0262) ... Without a default, a running module could never gain a setting: the file asking for it failed to compose until set, and the key was refused as stray until a file asked for it. Defaults sit under the mesh's and the node's settings, never merge into a JSON file, are refused for the operator's own values, and settings shows each value's source.	2026-10-08 17:24:32 +02:00