novox/mesh-controller

Hold a first merge whose new module the running build-agent refuses for an unknown manifest word, name it, and ask it again when build-agent is delivered (issue 1173) #438

Merged

mesh-tools merged 4 commits from fix/1173-held-first-build into main

2026-10-22 15:28:11 +00:00

Author	SHA1	Message	Date
jschoubben	1e9b87e03a	Hold every refused module of a first merge and ask each again by its own path (issue 1173) mesh/merge-gate head 1e9b87e03acd merged into trunk b8f77577fed2 — pass: builds build-agent, mesh-controller → ace, g14, novox, shanks; no bus step; every … Details mesh/repo-check head 1e9b87e03acd merged into trunk b8f77577fed2 — pass: its merge-check.sh passed Details mesh/delivery delivered Details mesh/check failed: integration: github.com/novox/mesh-controller/internal/identity.TestACertificateChainsToTheMeshsOwnAuthority: authority_test.go:45:… A held merge was asked again by the rule of a first merge, which finds nothing once a sibling module of the same merge registered, so it stayed held forever; and a second refusal in a merge already held fell through to a failed build. The hold now keeps a list of module, path and word, a refusal in a held waiting merge joins it, and the delivery of build-agent asks each held path again on the merge's Approve warrant.	2026-10-22 16:50:06 +02:00
jschoubben	45a09f90e3	Carry a held merge's new announcement into its record (issue 1173) HoldMerge replaced the event on the flag only; the record kept the old one.	2026-10-22 16:33:28 +02:00
jschoubben	4538d05732	Ask a held first build again when a delivery of build-agent ends (issue 1173) ADR 0482 section 5: the build waiting for a build-agent that reads its manifest is asked once the plan delivering it ends.	2026-10-22 16:19:45 +02:00
jschoubben	980d396d40	Keep a first merge whose manifest word the running build-agent does not read, and name it (issue 1173) ADR 0482 section 5: a merged manifest the running reader refuses waits for the newer reader, never failed.	2026-10-22 16:18:39 +02:00