Refuse a declaring module's mergeable file that names no keys (hq issue 574, ADR 0326 §3) #282

Merged

mesh-admin merged 2 commits from fix/574-a-declaring-module-names-its-files-keys into main 2026-10-12 23:28:22 +00:00

Conversation 7 Commits 2 Files Changed 8

+216 -3

2 Commits

Author	SHA1	Message	Date
jochen	18221c4079	Judge ADR 0326 §3 only where a definition is written (hq issue 574) ... ParseManifest also reads stored builds again: a build's manifest at a commit, the gate, a release, a module put back. betterbird's builds from before its accounts file named its keys would have become uncomposable there, so a send to g14 or shanks could fail and a rollback be refused. The refusal now runs in module check, module add, a build taken in, the builder and the merge gate's registration, and a file is no longer reported by both §2 and §3.	2026-10-13 00:54:26 +02:00
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