6 Commits

Include renames

Author	SHA1	Message	Date
jschoubben	4d203b5a5d	Ask mesh-delivery whether a merge's group still assembles (hq issue 525) ... A merge from any head waited for the window because the controller could not see a group's members, so the window skip changed nothing in production and unrelated merges walked one after another. The controller now asks mesh-delivery's groups, within 3 s and before the plans are held: a merge waits only when its head's group has another member whose pull request is open and whose merge it does not keep yet (ADR 0306 §2). No answer means it waits, and its batch says why. A headed merge in no waiting group and related to no batch is cut at once, as one from no head is (ADR 0304 §1, ADR 0306 §3). The controller's grant names mesh-delivery.groups. The installer's first user list in mesh-host must carry it too before the genesis test can pass.	2026-10-12 12:14:46 +02:00
jschoubben	6196a4815e	Let a merge that shares nothing skip the merge window (hq issue 525) ... A merge waited the whole window even when nothing assembling shared anything with it. It now joins only a batch it is related to (ADR 0304 §1, read by ADR 0306 §3: repository, a module the cut would move, a graph edge, a group head), folding the newer into the oldest when it relates to two. A merge related to none starts a batch whose window is closed at once (PlanBatch.CutAtOnce), unless its delivery group may still have a member to merge (ADR 0306 §2). The controller cannot see a group's unmerged members (that is mesh-delivery's record), so a merge from any head still waits, in a batch of its own: the safe error is to wait. Walks stay one at a time; a batch cut at once queues behind an open walk. A stop's merges walked again join a related batch, or their own.	2026-10-12 12:14:46 +02:00
jschoubben	bc4662d656	End the line a walk's ask leaves open as each ADR 0299 store test ends, so its pass is read (issue 459) ... A walk's ask prints " tier N: " and the build ask the rest; the tests' fake ask prints nothing, so go test -v put three tests' --- PASS after it and the store-tests step read them as not run.	2026-10-11 21:06:44 +02:00
jschoubben	201bd28278	Keep a walk's withheld modules on its record, name every machine a stopped send reached, and list the stop's store tests (review of #232)	2026-10-11 20:25:20 +02:00
jschoubben	309475bf6f	Walk a stopped walk's merges again in the open batch, in one act, and say what stays on the machines (review of #232, hq issue 459) ... A new batch beside the open one walked an older commit after a newer one, and a stop that failed partway could leave a merge on two plans. A module shared with the stopped merge, built at its branch, would deliver it; it is left out or withheld. A batch not yet cut can drop a merge, so mesh-delivery can stop a merge walked again. The stopped walk names what it left on which machines.	2026-10-11 20:12:27 +02:00
jschoubben	fbfdded74b	Let delivery-stop leave merges out and walk the others again, so a group stop ends only its own change (hq issue 459, ADR 0299) ... One walk carries every merge of its batch, so ending it for one group member ended every other delivery on it. delivery-stop now takes without: the walk ends, every other merge it answered is batched again, and each later merge of a left-out merge's repository is left out too, since it contains it.	2026-10-11 19:54:12 +02:00