Say which modules a walk left unchanged, so a merge that moved nothing is not read as stranded (hq issue 611) #295

Merged

mesh-admin merged 1 commits from fix/611-an-unchanged-build-is-delivered into main

2026-10-13 08:25:46 +00:00

Author	SHA1	Message	Date
jochen	05576db018	Say which modules a walk left unchanged, so a merge that moved nothing is not read as stranded (hq issue 611) mesh/merge-gate head 05576db018a4 merged into trunk a688dcff394b — pass: builds build-agent, mesh-controller → ace, g14, novox, shanks; no bus step; every … Details mesh/repo-check head 05576db018a4 merged into trunk a688dcff394b — pass: its merge-check.sh passed Details mesh/delivery delivered Details mesh/delivery-group group fix/611-an-unchanged-build-is-delivered delivered: every member is delivered Details A delivery plan made while another walk built a module reads it whole and names it; the walk, cut later, finds none of the changed files in the build source that build recorded and moves nothing. Its record named no module, so mesh-delivery read 'matched what runs' as 'never built', stopped the delivery and asked the operator about a change already on every machine. The walk now says each such module in delivery.unchanged, with why; its modules keep meaning what it builds.	2026-10-13 08:18:19 +02:00