7 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	2d2aa7ba9b	Carry the catalogue's predefined list on the bridge's merged message, so the indexer keeps it without the controller's mirror (issue 1953 L5-D1, ADR 0565 §2)	2026-10-29 22:21:12 +01:00
jschoubben	902e3c9e96	Refuse placement files on a forge message and delete placement-seed: no repository holds placement (ADR 0567 §11, issue 1126)	2026-10-28 18:09:38 +01:00
jschoubben	7e99c354ac	Give a catalogue pull request's placement a candidate state and each node an answer in its own have, so a placement change is checked by the nodes it places before it merges (issue 1126)	2026-10-27 02:07:47 +01:00
jschoubben	9f7f50de8d	A merged message of the catalogue carries its placement files, so the indexer reads placement at the merge without asking the forge again (issue 1126, ADR 0549 §2)	2026-10-26 18:08:59 +01:00
mesh-tools	6f9a83646a	Pin the json names of manifests, locks and inputs2 by the encoded bytes (issue 1442, review round 1) ... Go decodes keys case-insensitively, so a round trip could not see a dropped tag; the encoded bytes now name each field and an older message re-encodes to its own bytes.	2026-10-20 18:22:58 +00:00
mesh-tools	31c3b6cedc	Carry manifests and lock hashes in the forge messages, keep a module's new-form inputs, and lay out the build modules' toolchain keys (design 47 R4c-1, issues 1442, 1443) ... The indexer needs a module's manifest, lock hashes and toolchain to compute its new-form fingerprint, and has none of them (ADR 0465 clauses 1, 2, 5): the forge messages now carry the first two, a module keeps its inputs so it can be computed again when a toolchain is reported, and the build modules' toolchain keys have a layout and an agreement rule.	2026-10-20 18:20:15 +00:00