6 Commits

Include renames

Author	SHA1	Message	Date
jochen	404efb764b	mesh-delivery: keep each delivery's time from its merge and answer times per class (hq ADR 0282, issue 382) ... The operator's budget (a leaf module running everywhere within five minutes of its merge, a core module within ten) cannot be held to without measuring it. Each delivery now keeps its delivery time, class and phases from the walk the controller says; 'times' answers the week's median and worst per class, the deliveries over budget and their longest phase, and one delivery's breakdown; 'deliveries' is headed by the same line. A phase the walk could not measure stays unknown, never a zero. Measurement only.	2026-10-10 20:14:19 +02:00
jochen	32d55beb47	Say a pull request nobody checks as a delivery held, owned by mesh-delivery (hq issue 347) ... The confirmation review asked for the delivery domain's own vocabulary instead of a provider standing. A gitea health check would need a `tools` list (turning gitea's tools into seat verbs), a check of another kind beside it, and would hold the forge's own deliveries at the first-node gate; so the delivery's owner says it, with the word it already has. - gitea_open_pulls (gitea): every open pull request from the forge itself, with what its base requires and the statuses its head has. - mesh-delivery asks it every five minutes and keeps its own first-seen time per head (the forge's update time moves on every comment). A head on a base requiring mesh/merge-gate OR mesh/repo-check (hq requires only the second) with neither for ten minutes is a `stalled` line in state `unannounced`, which the controller raises as delivery.<id>.stalled (D14); H2 has nothing to close. Once announced it is a delivery of its own. - The gitea-side watcher and its provider standing are gone.	2026-10-09 13:14:36 +02:00
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	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	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	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