A no-move tier waits for no new report, so its walk asks the next tier (issue 648) #309

Merged

mesh-admin merged 2 commits from fix/648-a-no-move-tier-waits-for-nothing into main

2026-10-14 00:32:47 +00:00

Author	SHA1	Message	Date
jochen	70885ab3c4	Share one prefix between the no-move Why's writer and its reader (review of #309 , issue 648) mesh/delivery delivered Details mesh/merge-gate head 70885ab3c4a3 merged into trunk ca3f43c400ba — pass: builds mesh-controller → novox; no bus step; every machine composes with the chang… Details mesh/repo-check head 70885ab3c4a3 merged into trunk ca3f43c400ba — pass: its merge-check.sh passed Details	2026-10-14 02:22:25 +02:00
jochen	d9b86376d3	A no-move tier waits for no new report, so its walk asks the next tier (issue 648) A build made from the source every machine running it runs is marked sent and sent nothing, yet the tier's wait asked each machine for a report after that marking. None follows, and the walk waited for ever. Each machine is now judged by whether it answered its last send, the one whose builds made the build no move.	2026-10-14 02:18:53 +02:00