16 Commits

Include renames

Author	SHA1	Message	Date
jschoubben	0997b071a3	Pin every R4e member module to mesh-sdk's final R4e head 104533e8, which holds review fixes S1 and S2, so the group pins one SDK	2026-10-22 21:29:20 +02:00
jschoubben	08bc672488	Pin every R4e member module to mesh-sdk's final R4e head 875c680d, which holds main's #68 and #69, so the group pins one SDK	2026-10-22 20:45:16 +02:00
jschoubben	91e68ac13b	Merge feat/r4e-builder into feat/r4e (R4e integration) ... The checker's go.mod and go.sum conflicted on the mesh-sdk pin (checker lane 9cb4d59, builder lane e76a5a3): every module touched is pinned to the sdk lane's newest head d1af87a until the final SDK head.	2026-10-22 20:29:53 +02:00
jschoubben	b39090aab9	Read manifests with mesh-sdk's ParseManifestForInputs in the indexer and the builder, so claude-code, dunst and xterm are built too (issue 1751) ... The indexer's own copy goes. Pins mesh-sdk feat/r4e-sdk e76a5a3 in every module of the group.	2026-10-22 18:20:37 +02:00
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	a2a5167d72	Write a preview of the conflicts for a head that does not merge, and give the candidate's modules the reason; pin mesh-sdk to the R4c-5a head (issue 1445)	2026-10-21 21:25:45 +02:00
jschoubben	4242fb5b0b	The indexer gives a candidate's touched module the fingerprint its merge preview gives it, and wakes on the checker's preview.written without a restart; pin mesh-sdk to the R4c-5a head (issues 1445, 1681)	2026-10-21 21:17:09 +02:00
jschoubben	ebac167cd6	Move the indexer and builder to mesh-sdk main with the toolchains and root path (issue 1615)	2026-10-21 12:45:10 +02:00
mesh-tools	ba7ce55887	Give the indexer a manifests bucket and the SDK that knows the new keys (issue 1449, design 47 R4c-2)	2026-10-20 18:53:40 +00:00
mesh-tools	c93954e53c	Pin mesh-sdk to main's merge of #47 (88581d0a), the same tree as ba684e54 the review read	2026-10-20 06:33:01 +00:00
mesh-tools	14e9d56a22	Ask under each asking's own router id, spell the heads in lower case as the gate does, show a removed have plainly; pin mesh-sdk ba684e5 (review round 1: G2, T1, issue 1370)	2026-10-20 01:30:54 +00:00
mesh-tools	409c41d4ae	Stamp the modules with the gate's source revision, read from source.main (issue 1344)	2026-10-20 00:30:52 +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	4b8e71370c	Recognise a trunk build by repository identity and an empty ref in the indexer and the view (issue 1281) ... Build records name their repository by clone URL and a plan-asked build has no ref, so no module fingerprint was ever written or compared; both now use the SDK's tests.	2026-10-19 22:39:51 +02:00
jschoubben	677f94e901	Say which pull requests are open and drop every other candidate, so the candidates hold only open pull requests (issue 1279, ADR 0443)	2026-10-19 21:56:42 +02:00
jschoubben	4e87c4e485	Keep the candidate groups from the forge bridge's pull messages in a new indexer module (issue 1238)	2026-10-19 15:00:25 +02:00