7 Commits

Include renames

Author	SHA1	Message	Date
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	74f912e1fb	Put the merge check back to pending before a recheck asks it (hq issue 305) ... A recheck asks of the head the forge already judged, and the forge keeps the newest status of each context on it. Nobody reset mesh/merge-gate or mesh/repo-check, so the old green stood and branch protection would merge on it while the fresh check ran; rechecked heads did turn red. mesh-delivery's recheck now asks the forge's holder to set the gate, and the repository check when the head holds one, to pending ("checking again: <why>") before it asks the controller; a forge that cannot be told refuses the recheck whole. The gitea holder takes pending, and only pending, on the merge check's statuses by hand: no verdict, so issue 293 still holds.	2026-10-08 10:11:26 +02:00
jochen	13894744a7	Answer what the mesh's checks said of a pull request, as mesh-delivery's checks verb (hq ADR 0239) ... Reading a pull request's mesh/merge-gate and mesh/repo-check meant scraping the controller's journal: the forge clips each status to 140 characters and nothing returned the verdict whole. mesh-delivery already keeps the verdict; it now keeps the machine that ran it, the layers' modules and the report, and its checks verb joins that to the forge's statuses, read through a new gitea_commit_statuses tool that also says whether the base's protection lets the commit merge. after: novox/mesh-controller	2026-10-07 19:36:41 +02:00
jochen	d1de0edd4a	Ask the check of a delivery that waits for one nobody asked (hq issue 290) ... A pull request's head announced again from the bus's history at mesh-delivery's first start was proposed with no verdict and nothing ever asked its check: the controller had taken that announcement long before, and stalled raised it after an hour for the operator. A proposed delivery with no verdict and no check asked is now asked through delivery-check once it has waited past a grace longer than a check takes; an announcement carrying its head's decided gate status takes it. The proposed bound runs from the ask, and H2's close may re-ask once (a table row) before the delivery is the operator's.	2026-10-07 11:44: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