6 Commits

Include renames

Author	SHA1	Message	Date
jochen	6327f297ea	Cover a held merge only when the forge says a later delivered merge contains it (review of #150) ... Merge order on a protected trunk was the whole proof; the review asked for ancestry. The gitea module gains gitea_contains, a read-only compare of two commits (total_commits 0 is contained), and mesh-delivery asks it once per pair, off the lock like its plan ask, keeping the answer on the delivery. A forge that cannot say leaves the merge held, not covered. Merge order stays the cheap first filter. A later delivery now carries a module only when its own check passed (so a merge held without a passing check is closed only by one that passed), its walk is of its own merge commit on the same trunk, and its steps say the module reached every machine running it, not one. The words say what is known: a later merge that contains it was delivered.	2026-10-09 02:57:18 +02:00
jochen	2d1d4bf988	End a merge that moves nothing or that a later merge delivered, and lift a group hold its check answered (hq issues 319, 316) ... A held delivery asked a person a question with no right answer: four hq merges that build nothing, merges adding a module the controller sends nowhere, controller merges whose change a later walk of the same trunk already delivered, and a group member held because its composed check had not yet answered. Only stop could end them, which marks a delivered change as an error on its pull request. - A merge whose plan moves no module (nothing, or only a new module sent nowhere) is delivered at once. - A new final state, covered: every module a merge moves was sent by a finished walk of a later merge into the same trunk, which contains it. Shown as success on the pull request; a group counts it as delivered. - A group member waits published while its composed check is asked and unanswered, and a member held for it is lifted back to published once it passes for the heads that merged. Read again each tick, so the deliveries already held end by themselves after the rollout.	2026-10-09 02:24:26 +02:00
mesh-admin	f7b1853b8b	Merge pull request 'mesh-delivery: retire history instead of holding it; end owed work the forge cannot do (hq issue 313)' (#121) from fix/313-retire-adopted-history into main	2026-10-08 09:36:52 +00:00
jochen	0ce567a736	Retire history instead of holding it, and end owed work the forge cannot do (hq issue 313)	2026-10-08 11:20:46 +02:00
jochen	6ae112d299	Say which order rule won, and how to end a contradiction (hq issue 309) ... A group whose order rules disagreed was refused as "its order contradicts itself" with only the member ids: nobody could see which rules clashed or what to write to resolve it. The controller now resolves rules by precedence (hq ADR 0249) and answers, per pair, the rules it won over, and per contradiction no precedence resolves, both rules and how to declare the order. mesh-delivery keeps both, lists them in groups and the plan note, and refuses a group by those words; a cycle through more members names the pairs in it. An older controller's answer reads as before.	2026-10-08 10:43:21 +02:00
jochen	b6f0bc309b	Add mesh-delivery, the owner of deliveries and delivery groups (hq ADR 0239) ... One module answers 'did my change go out' for a commit and orders a cross-repository change: one compiled state table, its state on the bus, every transition said, noted on the commit and shown on the pull request. The forge's holder gains the note, view and status tools it asks with, and says closed pull requests and a merge's head and statuses.	2026-10-06 23:59:54 +02:00