A batch that shares nothing with a running rollout starts beside it (issue 973, step 1)

+500 -83

4 Commits

Author	SHA1	Message	Date
jschoubben	6355176fda	The ssh-client test offers the forge from another node, as the catalogue's ssh-client now requires forge-account (issue 985) mesh/merge-gate head 6355176fdab0 merged into trunk 6a62a7e552ea — pass: builds build-agent, mesh-controller → ace, g14, novox, shanks; no bus step; every … Details mesh/repo-check head 6355176fdab0 merged into trunk 6a62a7e552ea — pass: its merge-check.sh passed Details mesh/delivery delivered Details	2026-10-17 01:00:40 +02:00
jschoubben	300d3c1bf4	Cut a closed batch beside the open walks it shares nothing with, queue a related one with the reason, fold only related waiting walks (issue 973) mesh/merge-gate head 300d3c1bf466 merged into trunk 6a62a7e552ea — pass: builds build-agent, mesh-controller → ace, g14, novox, shanks; no bus step; every … Details mesh/repo-check head 300d3c1bf466 merged into trunk 6a62a7e552ea — fail: its merge-check.sh failed: --- FAIL: TestSSHClientOwnsTheOperatorsSSHConfig (0.01s) Details mesh/delivery superseded: a newer head of the same pull request Details	2026-10-17 00:49:53 +02:00
jschoubben	baf1501d81	A walk, a retry and a let-go wait only for a started walk they are related to (issue 973)	2026-10-17 00:46:27 +02:00
jschoubben	a5ba47e23c	Name the open walk a change is related to, own path related to all (issue 973)	2026-10-17 00:45:00 +02:00

A batch that shares nothing with a running rollout starts beside it (issue 973, step 1) #366