9 Commits

Include renames

Author	SHA1	Message	Date
jschoubben	1414ed7f7b	Judge an ask by the builder's say the walk read, never a second read (issue 1886, review round 1) ... A second read that failed, or that turned true in between, refused the ask and failed the whole plan.	2026-10-23 01:03:19 +02:00
jschoubben	f67342f0d8	Ask build-agent for the build modules that write references, whatever the builder says (issue 1886, ADR 0522 §6) ... They push and answer each reference, so a key they write themselves can never carry their own delivery; until R4g build-agent delivers them as it does the builder.	2026-10-23 00:53:25 +02:00
jschoubben	fae7710bed	Ask build-agent for every module until a running builder says it writes references (issue 1886) ... R4e's own delivery plan waited for ever in tier 1: the controller took every module but build-agent's own from a referenced builder key, and only R4e's builder and build modules, delivered by that same plan, write references. The builder now says so in its bucket of instances; until it does, a walk asks build-agent as before R4e, and an open walk waiting on a key the running builder cannot reference is judged again at the next look.	2026-10-23 00:47:15 +02:00
jschoubben	61449249a8	Name build-agent's own as the builder's module, build-agent and mesh-tools (ADR 0520 §1, issue 1851) ... ADR 0520 narrowed after its review: mesh-tools-go builds from its own directory on a pinned base and has its key from mesh-build-image, and mesh-tools-python is no module, so the set is named, not derived from the toolchain bases.	2026-10-22 21:08:47 +02:00
jschoubben	9713ceb84d	Ask build-agent for itself and its toolchain images, never a builder key (ADR 0520, issue 1851) ... The builder writes no key of build-agent or of the toolchain bases its builds stand on, so a walk moving one would hold its tier for ever. Until R4g they are build-agent's own, as the builder's module is; the bases are read from the toolchains, not copied.	2026-10-22 21:06:33 +02:00
jschoubben	bc80683b9e	Count the work the take-ins start in the background, so a test's mesh closes only once that work has ended (issue 1851, A5-A7; issue 1790, D3)	2026-10-22 20:41:30 +02:00
jschoubben	dfc2f2aa98	Take a walk's key in again when it was recorded at an earlier merge, so the module is registered at the commit the walk carries before it is built (issue 1851, A6)	2026-10-22 19:05:05 +02:00
jschoubben	25fdf9920e	Read a commit as the same as itself however short, and fit the pending assignments' tests to a mesh that asks no build (issue 1851, A9, A10)	2026-10-22 19:05:04 +02:00
jschoubben	62268cf43d	Take a walk's modules from the builder's done keys and ask no build but the builder's own: a key building or unreferenced holds the tier and says so, a failed key fails the walk in its words (issue 1851, A6, A7)	2026-10-22 19:05:04 +02:00