11 Commits

Include renames

Author	SHA1	Message	Date
jschoubben	1cbfd841de	The indexer writes placement.<node> from the catalogue's placement files at each merge, only where it changed, and says placement-changed (issue 1126, ADR 0549 §2)	2026-10-26 18:14:34 +01:00
jschoubben	07b5f13474	mesh-delivery-indexer reads a registered module again once its repository becomes readable, and takes one in on ask (issue 1945) ... A registered module whose repository the forge answered 404 (car-hunter, snake, before the forge's account could read them) was read again only when the indexer started again or the controller wrote a new build record of it, so the grants part's composed user list stayed short of their subjects and the take-over was refused. A failed read now keeps the module as unread, read again on the next source revision and the next merged message (no timer of its own), and the new tool indexer_take_in (the tools bundle mesh-delivery-indexer-tools, through the indexer's takeins state, as the builder's builder_ask_again) takes one in now and answers what it stored or why not.	2026-10-26 14:01:34 +01:00
jschoubben	82da252cf0	Indexer: index the manifests of modules registered from their own repositories, so the grants part has no gap for them	2026-10-26 11:23:21 +01:00
jschoubben	3553cbaf08	Count only the toolchain reports of nodes a build module is assigned to, so a node it left does not make the builders disagree (issue 1940) ... mesh-build-node was unassigned from ace on 2026-10-23 and its ace.typescript key stayed in mesh-build-node_toolchains at v26.12.0: nothing deletes it, so the indexer, the builder and the checker took it for a builder and every Node fingerprint said 'builders disagree'. The three now read mesh-controller_assignments and pass a toolchain report on only while its build module has an open assignment on its node; builders that run different versions still disagree.	2026-10-24 12:48:41 +02:00
jschoubben	24753bfc2c	Grant gitea_contains in the indexer's invokes and test every called forge tool is granted (issue 1900)	2026-10-23 14:48:41 +02:00
jschoubben	612658e788	Ask the forge for the objects of a merge's named paths in the indexer, the one reader of a manifest's paths, and narrow the module's tree from the answer (issue 1758, I6 reworked; ADR 0499 §2 §3, ADR 0495 §1, L8) ... The manifest invokes gitea.gitea_commit_trees. A forge that cannot say gives the module none with its words.	2026-10-22 18:24:38 +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
mesh-tools	a5da6079de	Write each module once per merge and watch a build module's toolchains bucket on its toolchain.reported event, with no timer (issue 1444, review round 1)	2026-10-20 21:02:44 +00:00
mesh-tools	127ac64cce	Leave an artifact without its lock file out of Locks (issue 1459) and read the build modules' toolchains (issue 1444), part 2 of 2	2026-10-20 20:48:30 +00: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
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