4 Commits

Include renames

Author	SHA1	Message	Date
jschoubben	a20bdf7952	Carry mesh package versions in build asks and fingerprints ... ADR 0573 §2 has every module build against the latest published version of each mesh package it uses, chosen by the planner and written by the build, never pinned by hand (issue 1585, S4). The ask, the fetch request and the merge preview now carry the packages and their versions, and the new-form fingerprint takes each version, so a package's trunk merge changes every dependent's fingerprint. A module using no package keeps its fingerprint. Folded onto feat/judge-once by builder-1585a: Module keeps both Packages and the verdict fields. Claude-Session: https://claude.ai/code/session_01NcbgfJ9Gum47zkFKWRaovL	2026-11-01 02:40:12 +01:00
jschoubben	8d65cb3016	Carry each named path's git object beside a module's other inputs (issue 1758, S3, ADR 0499 §2-§3) ... Forge.Paths, PreviewModule.Paths, KeptInputs2.Paths and buildstep.ModuleTree.Paths, each optional and read as absent by older readers; a kept or previewed tree that its named paths do not compute to is refused, so a recompute gives the merge's value.	2026-10-22 17:27:58 +02:00
jschoubben	78364e318b	Put the module trees of a merge into go/buildstep for both fetch steps, and let a preview name the conflicts of a head that does not merge (issues 1675, 1676, 1445)	2026-10-21 21:21:48 +02:00
jschoubben	b944d07158	Add the checker's owed bucket, the mesh/check status context and the previews layout, and correct the checker header: the checker decides the status, the bridge sets it (issue 1673)	2026-10-21 19:21:22 +02:00