6 Commits

Include renames

Author	SHA1	Message	Date
jschoubben	9f7e082688	List a repository's modules from the merged message's manifests and the indexer's own bucket, not the controller's build records, so a new module gets a value and a key with no build asked (issue 1851, I1 I2 I4, ADR 0501 §6, ADR 0453 §6) ... I1: a merge writes each module its manifests name, at its directory. I2: a pull request's changed directory, a preview's touched module and a source revision's modules come from the modules bucket (a module a pull request adds is found in the preview by its manifest). I4: the value of today's form (fp, none) is no longer written, since it was computed from the build records; mesh-sdk keeps it readable until R4g. One commit: the three share applyMerged and its tests. Pins mesh-sdk feat/r4e-sdk 9cb4d59.	2026-10-22 18:08:48 +02:00
jschoubben	3bd2a065f9	The indexer writes '.' for a root module's path and the toolchains each fingerprint was computed with (issue 1615)	2026-10-21 11:33:49 +02:00
jschoubben	07a28b03c4	The indexer writes each module's directory into modules.<m> and keeps it (issue 1606, ADR 0478 clause 8)	2026-10-21 11:16:16 +02:00
mesh-tools	3c655c5ab4	Write a failed build as the controller does, an outcome with failed set (issue 1281)	2026-10-19 22:47:41 +00:00
mesh-tools	8ffcf02a9c	Take the SDK that counts a stateless build record as an outcome; fixtures in the controller's layout (issue 1281)	2026-10-19 22:44:21 +00:00
jschoubben	c084a311a1	Write each module's source fingerprint at a trunk merge in the indexer (issues 1239, 1209)	2026-10-19 15:03:57 +02:00