Ask build-agent until the builder says it writes references, so a plan never waits on a key nothing can reference (issue 1886, ADR 0522) #442

Merged

jschoubben merged 4 commits from fix/1886-builder-says-references into main 2026-10-23 00:27:01 +00:00

Conversation 2 Commits 4 Files Changed 8

+547 -5

4 Commits

Author	SHA1	Message	Date
jschoubben	bbadbb2af0	Judge the ask and the settle by one say of the builder (issue 1886, merge check hang) ... The settle read the say from the builder's bucket while the ask read it through builderSaysReferences; where they differed (a test's say against a bus with no bucket) a module was handed back and taken from its key again at every turn, and the look's loop never ended.	2026-10-23 01:59:18 +02:00
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