mesh-delivery: say a ready or rejected delivery whose check has not answered on the forge (hq issue 441) #199

Merged

mesh-admin merged 2 commits from fix/441-a-held-delivery-without-its-check-is-said into main

2026-10-11 01:26:37 +00:00

Author	SHA1	Message	Date
jschoubben	9bd8903ed2	mesh-delivery: test that an unanswered line clears when its delivery moves on or its pull request closes (issue 441) mesh/merge-gate pass: builds mesh-delivery → novox; no bus step; every machine composes with the change as it did without (4 of 4 compose) Details mesh/repo-check pass: its merge-check.sh passed, each part in its toolchain: merge-check.sh (go), merge-check-typescript.sh (typescript) Details mesh/delivery covered after its failure: a later walk that contains it was delivered: plan-1791682028101285377 (novox/mesh-catalog at a5b4a757 into main,… Details The review asked for the clearing paths to be pinned: a recheck or a merge clears the line before the forge is read again, and a pull request gone from the open list is no longer said.	2026-10-11 03:03:43 +02:00
jschoubben	5855c41f9d	mesh-delivery: say a ready or rejected delivery whose check has not answered on the forge (issue 441) mesh/merge-gate pass: builds mesh-delivery → novox; no bus step; every machine composes with the change as it did without (4 of 4 compose) Details mesh/repo-check pass: its merge-check.sh passed, each part in its toolchain: merge-check.sh (go), merge-check-typescript.sh (typescript) Details mesh/delivery superseded: a newer head of the same pull request Details Ready and rejected have no bound, and the watch for unchecked heads skipped every head with a delivery, so a lost or lagging status write left a pull request unable to merge with nothing said. Such a head is now said on issue 438's rule: an unanswered line past the table's bound for a check asked and not answered.	2026-10-11 03:00:23 +02:00