Fixes issue 1160 (the fourth fix item of issue 230, never built). Seen tonight: plan-1792348575846657518 has waited since 20:46 at 'tier 0 built; waiting for mesh-host on g14 to be applied' for g14, a laptop asleep, and every later delivery waits behind it.
release_plan.go: the gate between tiers (settleTierGate) takes the same silent set the last tier takes (silentNodes, from walkReports): a machine whose send has had no report past the bound (15 min) is named silent and not waited for, a note on the plan says it was left as it was, later tiers are not sent to it (withoutSilent), and it keeps its want of the plan's builds for the declaration it gets when heard again, as the last tier's silent machine is kept today. A middle tier whose every machine is silent ends the plan failed with each named, since its later tiers depend on it; the last tier is unchanged. silentWaitsOf keeps arming middle-tier keys, so the send key's expiry now moves the plan.
Tests: 1160/AC1-AC4 (unit), AC5 (integration: a plan of two tiers whose first-tier machine never reports passes after the bound on the key's expiry and sends its second tier to the other machine). Try build-1792351534915001547 passed in 3 m 29 s (unit level 2299 tests, 2.54 s of 5 s).
A core issue: resolved with a replay or replay-none once delivered. This merge cannot unstick tonight's plan, which runs the controller of before it.
Fixes issue 1160 (the fourth fix item of issue 230, never built). Seen tonight: plan-1792348575846657518 has waited since 20:46 at 'tier 0 built; waiting for mesh-host on g14 to be applied' for g14, a laptop asleep, and every later delivery waits behind it.
`release_plan.go`: the gate between tiers (`settleTierGate`) takes the same silent set the last tier takes (`silentNodes`, from `walkReports`): a machine whose send has had no report past the bound (15 min) is named silent and not waited for, a note on the plan says it was left as it was, later tiers are not sent to it (`withoutSilent`), and it keeps its want of the plan's builds for the declaration it gets when heard again, as the last tier's silent machine is kept today. A middle tier whose every machine is silent ends the plan failed with each named, since its later tiers depend on it; the last tier is unchanged. `silentWaitsOf` keeps arming middle-tier keys, so the send key's expiry now moves the plan.
Tests: 1160/AC1-AC4 (unit), AC5 (integration: a plan of two tiers whose first-tier machine never reports passes after the bound on the key's expiry and sends its second tier to the other machine). Try build-1792351534915001547 passed in 3 m 29 s (unit level 2299 tests, 2.54 s of 5 s).
A core issue: resolved with a replay or replay-none once delivered. This merge cannot unstick tonight's plan, which runs the controller of before it.
Reviewed-by: reviewer-r12@shanks at 1ec27e6ba18f1e3e1b59bbf907237b2ca45a9602
mesh/merge-gate head 1ec27e6ba18f merged into trunk 461fa9c7b4ed — pass: builds mesh-controller → novox; no bus step; every machine composes with the chang…
mesh/delivery covered after its stop: a later merge that contains it was delivered: novox/mesh-controller@75a27ec1a4bc (merged as b1cfb85f into main, wal…
Deliverynovox/mesh-controller@1ec27e6ba18f — stopped since 2026-10-18T22:05:48Z
Covered: covered after its stop: a later merge that contains it was delivered: novox/mesh-controller@75a27ec1a4 (merged as b1cfb85f into main, walk plan-1792361327794761328): mesh-controller
Delivery plan — builds mesh-controller → novox; no bus step
tier 0: mesh-controller
novox: receives mesh-controller
Transitions
2026-10-18 19:29 (new) → proposed (announced): novox/mesh-controller#384's head announced
2026-10-18 19:36 proposed → checked (checked): a verdict names this commit and the trunk's head as its trunk commit
2026-10-18 19:36 checked → ready (accepted): the gate passed or warned, and the repository's own check did not fail
2026-10-18 21:45 ready → published (merged): on the trunk its modules follow: merged there, and its walk opened — or nothing for a walk to move
2026-10-18 22:05 published → stopped (stop): a merged change never reached the machines: its walk plan-1792354535451678994 ended done before its word without building mesh-controller (moved nothing the mesh holds: nothing to walk), and no later merge into main that contains it delivered them (novox/hq issue 474)
The commit's note under refs/notes/mesh-plan keeps every transition: git log --notes=mesh-plan.
<!-- mesh-delivery:view -->
**Delivery** `novox/mesh-controller@1ec27e6ba18f` — **stopped** since 2026-10-18T22:05:48Z
**Covered**: covered after its stop: a later merge that contains it was delivered: novox/mesh-controller@75a27ec1a4bc (merged as b1cfb85f into main, walk plan-1792361327794761328): mesh-controller
**Delivery plan** — builds mesh-controller → novox; no bus step
- tier 0: mesh-controller
- novox: receives mesh-controller
**Transitions**
- 2026-10-18 19:29 (new) → proposed (announced): novox/mesh-controller#384's head announced
- 2026-10-18 19:36 proposed → checked (checked): a verdict names this commit and the trunk's head as its trunk commit
- 2026-10-18 19:36 checked → ready (accepted): the gate passed or warned, and the repository's own check did not fail
- 2026-10-18 21:45 ready → published (merged): on the trunk its modules follow: merged there, and its walk opened — or nothing for a walk to move
- 2026-10-18 22:05 published → stopped (stop): a merged change never reached the machines: its walk plan-1792354535451678994 ended done before its word without building mesh-controller (moved nothing the mesh holds: nothing to walk), and no later merge into main that contains it delivered them (novox/hq issue 474)
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.
Fixes issue 1160 (the fourth fix item of issue 230, never built). Seen tonight: plan-1792348575846657518 has waited since 20:46 at 'tier 0 built; waiting for mesh-host on g14 to be applied' for g14, a laptop asleep, and every later delivery waits behind it.
release_plan.go: the gate between tiers (settleTierGate) takes the same silent set the last tier takes (silentNodes, fromwalkReports): a machine whose send has had no report past the bound (15 min) is named silent and not waited for, a note on the plan says it was left as it was, later tiers are not sent to it (withoutSilent), and it keeps its want of the plan's builds for the declaration it gets when heard again, as the last tier's silent machine is kept today. A middle tier whose every machine is silent ends the plan failed with each named, since its later tiers depend on it; the last tier is unchanged.silentWaitsOfkeeps arming middle-tier keys, so the send key's expiry now moves the plan.Tests: 1160/AC1-AC4 (unit), AC5 (integration: a plan of two tiers whose first-tier machine never reports passes after the bound on the key's expiry and sends its second tier to the other machine). Try build-1792351534915001547 passed in 3 m 29 s (unit level 2299 tests, 2.54 s of 5 s).
A core issue: resolved with a replay or replay-none once delivered. This merge cannot unstick tonight's plan, which runs the controller of before it.
Reviewed-by: reviewer-r12@shanks at
1ec27e6ba1Delivery
novox/mesh-controller@1ec27e6ba18f— stopped since 2026-10-18T22:05:48ZCovered: covered after its stop: a later merge that contains it was delivered: novox/mesh-controller@75a27ec1a4 (merged as
b1cfb85finto main, walk plan-1792361327794761328): mesh-controllerDelivery plan — builds mesh-controller → novox; no bus step
Transitions
The commit's note under
refs/notes/mesh-plankeeps every transition:git log --notes=mesh-plan.Merge check at
1ec27e6bJudged: head
1ec27e6ba18fmerged into trunk461fa9c7b4ed; read beside it: mesh-cataloga6295d6b98d5, mesh-controller-main461fa9c7b4ed, mesh-host8119c470d393, mesh-tools7412c5b6c9c5mesh/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 shanks as
build-1792351765963600901(builds --log build-1792351765963600901).