3 Commits

Include renames

Author	SHA1	Message	Date
jochen	065cfa0d1d	Owe a merge to the record from its branch's first kept merge (hq ADR 0276 review)	2026-10-10 13:54:40 +02:00
jochen	0e0e143055	Keep a merge a cut made history, and build a batch's walk at the branch (hq ADR 0276 review)	2026-10-10 13:48:31 +02:00
jochen	96fc4209d3	Assemble merges in a rolling window and walk each batch once (hq ADR 0276, issue 362) ... Every merge opened a walk and the next merge of the branch superseded it: two catalogue merges 18 s apart left a walk no delivery held, and the operator started it by hand 58 minutes later. A merge now joins the open batch, kept in the store (migration 0089), which is cut into one walk when no merge came for merge-window (90 s) or at merge-window-at-most (10 min): one commit per repository, the latest of its branch, with every file the batch's merges changed. One walk at a time; a started walk is never superseded, a waiting one is folded into the next. The walk names every merge it answers on the wire (delivery.merges, taken_over_by, batch). A failed walk walks its earlier merges alone, newest first, until one is delivered. A delivery group's order becomes tier edges inside the walk. plans shows the batch assembling; S18 and S19 bound its waits; S16 names the merges a waiting walk answers.	2026-10-10 13:20:04 +02:00