3 Commits

Include renames

Author	SHA1	Message	Date
mesh-adminandClaude Opus 5.5	d43fbc202c	Let a file resource name a template file in its module's repository ... A file's text may live in files/<name> beside the manifest instead of inline, so modules can move their files out of module.json (ADR 0349 clause 2, issue 654). The build packs files/ into the module's declared archive and reads each template back from the packed bytes, proven by the digest, into content: the manifest the mesh holds, composition and the node-engine stay as they are. module check, the merge gate and module add read templates from the tree beside the manifest, so a change to a template alone is judged. A file naming both template and content, a template outside files/, a missing one, and a held manifest that still names one are refused by name. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>	2026-10-13 23:56:43 +00:00
jschoubben	5c606fd1d4	Take only a check build its verdict names, and keep a build another check still names ... The artifact store takes writes from anything on its network, so a record planted under another merge's key could have been registered: the walk now takes a scratch build only when the build seat's own verdict for one of its pull requests names its key and digests. Deleting by digest also took builds another check shared (review of #311; novox/hq ADR 0350).	2026-10-13 23:16:55 +02:00
jschoubben	cd49b50c40	Build a change once: the check builds what its merge moves, the walk takes it by key ... A merge built every moved module a second time although its check had judged the same tree (issue 649). The check now builds into the scratch namespace under a reuse key (source fingerprint plus the builder's own digest), and the walk of the trunk commit copies a build of the same key by digest instead of building, saying per module why when it cannot (novox/hq ADR 0350).	2026-10-13 23:04:40 +02:00