3 Commits

Include renames

Author	SHA1	Message	Date
jochen	db0cb1e15e	Refuse a declaring module's mergeable file that names no keys (hq issue 574, ADR 0326 §3) ... A module that declares a setting and owns a mergeable file naming no keys still let every key reach that file. The refusal was held back in #272 because betterbird was one; mesh-catalog #252 named its keys, and every module in mesh-catalog and mesh-media-catalog main now passes, so the module check and registration refuse it again. A stored definition is still composed as it is, never left out of a machine.	2026-10-13 00:40:24 +02:00
jochen	dd10889209	Hold back refusing a declaring module's silent mergeable file (hq issue 168) ... betterbird declares a preference and owns a mergeable file that names no keys, and the catalogue can only name them once this controller runs: the refusal made the catalogue check fail against catalogue main. It follows once mesh-catalog names the keys.	2026-10-12 18:00:33 +02:00
jochen	286257d802	Let a mergeable file name the setting keys it takes (hq issue 168, ADR 0326) ... Every key of a module's layers merged into every mergeable file it owns: the mesh's own words, a key meant for a ${setting:} in another file, a key for a second configuration file. A module could not own two configurable files. A file now names its keys in takes-settings and takes only those; a key no file names is stray where it is set; a module that declares a setting names the keys of every mergeable file, and one that declares none keeps today's form (ADR 0164 §15).	2026-10-12 17:47:05 +02:00