5 Commits

Include renames

Author	SHA1	Message	Date
mesh-adminandClaude Opus 5.5	c0bee5d042	Judge every manifest against the list of predefined keys of its tree, and carry the list from a build ... Mesh and node config may hold values only for keys on a fixed, reviewed list (hq ADR 0348 clause 7, design 57 package K2, issue 661). A build reads predefined.json at the root of the repository at the commit it builds and carries it with the commit's generation; module check and the merge gate read it from the tree. (Part 1 of 2: the changes to existing files.) Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>	2026-10-14 05:45:48 +00: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
jochen	abe5f7dc17	Say a build source only for the trunk's head, and hold what C, assembly and a new go.mod reach (hq ADR 0267, review) ... A hand build of an older trunk commit said a closure lacking what was imported since, and the planner would have mapped the next merge onto it. C and assembly beside Go may include files below their directory, and a go.mod made above a package moves it out of its module: each is now held.	2026-10-10 03:11:06 +02:00
jochen	4d1b81b6cb	Say what a build was made from, and hand an image compiling Go only that (hq ADR 0267, issue 363) ... A merge to the controller's repository moved the route proxy and the build seat's holder whatever it changed, because nothing said which files their builds read. A build of a trunk commit now says its build source per repository: a Go program's import closure, an archive's directory, an image's recipe and the package it names in the new 'compiles' field. That image is built from its build source alone, so a recipe reading past it fails by name, and its fingerprint is over what it was handed.	2026-10-10 02:47:35 +02:00
jschoubben	792352dfad	Read a rebuild of an unchanged source as no move, whatever image digest it made (hq issue 280) ... An image is not byte-reproducible, so ADR 0236's 'same artifacts is no move' never held for one: a catalogue merge that did not touch the bus rebuilt it, and every send to the control node waited for a planned bus upgrade. The builder now records a source fingerprint per build (module tree, context trees, bases and toolchains by digest). A rebuild with the fingerprint of the build it repeats is registered with that build's artifacts, handed to modules standing on it, holds no push, demands no bus step, and a plan sends and gates nothing for it. Identical artifacts remain a second way to be no move.	2026-10-06 22:09:11 +02:00