Issue 920 (met again 2026-10-21: mesh-sdk #64's plan said 'building for 1h8m — LATE' for about 70 minutes while every send to novox was refused, which held every delivery behind it). release_plan.go:930 wrote the refusal into the plan's note and kept it building; planLineSaid printed 'building for' whatever the note said, so plans, status and the stalled condition hid why. Now a building plan whose current tier is all built and whose note is a refusal (written by refusalNote, matched by refused() on its fixed form, the same text as before) says 'tier N of M, held: , for '. A tier's summary left in the note is never said as a hold.
Tests: 920/AC1-3 in plan_clock_test.go, each failing before its change. Review: two rounds (round 1: a tier summary would have read as a hold). Try build-1792602137710728728 passed (7m45s). The two plans blocking each other is issue 1750.
Issue 920 (met again 2026-10-21: mesh-sdk #64's plan said 'building for 1h8m — LATE' for about 70 minutes while every send to novox was refused, which held every delivery behind it). release_plan.go:930 wrote the refusal into the plan's note and kept it building; planLineSaid printed 'building for' whatever the note said, so plans, status and the stalled condition hid why. Now a building plan whose current tier is all built and whose note is a refusal (written by refusalNote, matched by refused() on its fixed form, the same text as before) says 'tier N of M, held: <refusal>, for <since>'. A tier's summary left in the note is never said as a hold.
Tests: 920/AC1-3 in plan_clock_test.go, each failing before its change. Review: two rounds (round 1: a tier summary would have read as a hold). Try build-1792602137710728728 passed (7m45s). The two plans blocking each other is issue 1750.
Reviewed-by: review-fts@shanks at 612f493c4926cffc50f171eebf716f61abc7ae36
mesh/merge-gate head 612f493c4926 merged into trunk 5ba2ffe8e608 — pass: builds mesh-controller → novox; no bus step; every machine composes with the chang…
Deliverynovox/mesh-controller@612f493c4926 — delivered since 2026-10-21T17:25:52Z
Delivery plan — builds mesh-controller → novox; no bus step
tier 0: mesh-controller
novox: receives mesh-controller
Machines
mesh-controller on every machine running it: sent
Transitions
2026-10-21 17:11 (new) → proposed (announced): novox/mesh-controller#426's head announced
2026-10-21 17:21 proposed → checked (checked): a verdict names this commit and the trunk's head as its trunk commit
2026-10-21 17:21 checked → ready (accepted): the gate passed or warned, and the repository's own check did not fail
2026-10-21 17:23 ready → published (merged): on the trunk its modules follow: merged there, and its walk opened — or nothing for a walk to move
2026-10-21 17:23 published → delivering (go): its walk started: let go by this owner in its group's order, by a person, or on the controller's own path — not a failed walk that carried a later commit for it, after which it waits for a walk of its own commit
2026-10-21 17:25 delivering → delivered (done): its walk is done, carrying its own commit: every machine of its deploy plan passed, or was left as its policy says
The commit's note under refs/notes/mesh-plan keeps every transition: git log --notes=mesh-plan.
<!-- mesh-delivery:view -->
**Delivery** `novox/mesh-controller@612f493c4926` — **delivered** since 2026-10-21T17:25:52Z
**Delivery plan** — builds mesh-controller → novox; no bus step
- tier 0: mesh-controller
- novox: receives mesh-controller
**Machines**
- mesh-controller on every machine running it: sent
**Transitions**
- 2026-10-21 17:11 (new) → proposed (announced): novox/mesh-controller#426's head announced
- 2026-10-21 17:21 proposed → checked (checked): a verdict names this commit and the trunk's head as its trunk commit
- 2026-10-21 17:21 checked → ready (accepted): the gate passed or warned, and the repository's own check did not fail
- 2026-10-21 17:23 ready → published (merged): on the trunk its modules follow: merged there, and its walk opened — or nothing for a walk to move
- 2026-10-21 17:23 published → delivering (go): its walk started: let go by this owner in its group's order, by a person, or on the controller's own path — not a failed walk that carried a later commit for it, after which it waits for a walk of its own commit
- 2026-10-21 17:25 delivering → delivered (done): its walk is done, carrying its own commit: every machine of its deploy plan passed, or was left as its policy says
The commit's note under `refs/notes/mesh-plan` keeps every transition: `git log --notes=mesh-plan`.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Issue 920 (met again 2026-10-21: mesh-sdk #64's plan said 'building for 1h8m — LATE' for about 70 minutes while every send to novox was refused, which held every delivery behind it). release_plan.go:930 wrote the refusal into the plan's note and kept it building; planLineSaid printed 'building for' whatever the note said, so plans, status and the stalled condition hid why. Now a building plan whose current tier is all built and whose note is a refusal (written by refusalNote, matched by refused() on its fixed form, the same text as before) says 'tier N of M, held: , for '. A tier's summary left in the note is never said as a hold.
Tests: 920/AC1-3 in plan_clock_test.go, each failing before its change. Review: two rounds (round 1: a tier summary would have read as a hold). Try build-1792602137710728728 passed (7m45s). The two plans blocking each other is issue 1750.
Reviewed-by: review-fts@shanks at
612f493c49Delivery
novox/mesh-controller@612f493c4926— delivered since 2026-10-21T17:25:52ZDelivery plan — builds mesh-controller → novox; no bus step
Machines
Transitions
The commit's note under
refs/notes/mesh-plankeeps every transition:git log --notes=mesh-plan.Merge check at
612f493cJudged: head
612f493c4926merged into trunk5ba2ffe8e608; read beside it: mesh-catalog7a7a4034852a, mesh-controller-main5ba2ffe8e608, mesh-hostc231d1031fc7, mesh-toolse0fadc43d9ddmesh/merge-gate: PASS — every machine composes with the change as it did without (4 of 4 compose) (modules: mesh-controller)mesh/repo-check: PASS — its merge-check.sh passedDelivery plan — builds mesh-controller → novox; no bus step
Run by the build seat on ace as
build-1792602668918001065(builds --log build-1792602668918001065).