hq issue 362; the fix is mesh-catalog #171 (mesh-delivery), still on its branch, so Before is the main it branched from (52f34d3) and Fix its head f8c4bc5.
The replay is TestReplay362 in modules/mesh-delivery/cmd/mesh-delivery/replay362_test.go, written with only what mesh-delivery had before the fix. It covers both orders in which the controller's two records can arrive.
Proved with go run ./cmd/prove --repos <clones> R362: "PROVED — before its fix fails, on its fix passes". Before the fix, the dunst delivery ends superseded and the walk is never let go.
If #171 is rebased or squashed before merge, Fix must be updated to the commit that lands.
hq issue 362; the fix is mesh-catalog #171 (mesh-delivery), still on its branch, so `Before` is the main it branched from (52f34d3) and `Fix` its head f8c4bc5.
The replay is `TestReplay362` in modules/mesh-delivery/cmd/mesh-delivery/replay362_test.go, written with only what mesh-delivery had before the fix. It covers both orders in which the controller's two records can arrive.
Proved with `go run ./cmd/prove --repos <clones> R362`: "PROVED — before its fix fails, on its fix passes". Before the fix, the dunst delivery ends `superseded` and the walk is never let go.
If #171 is rebased or squashed before merge, `Fix` must be updated to the commit that lands.
Deliverynovox/mesh-lab@719ca7ae0bdc — delivered since 2026-10-10T11:14:27Z
Delivery plan — builds nothing: the change touches no module of the mesh's graph
Transitions
2026-10-10 11:06 (new) → proposed (announced): novox/mesh-lab#75's head announced
2026-10-10 11:07 proposed → checked (checked): the verdict names this commit
2026-10-10 11:07 checked → ready (accepted): the gate passed or warned, and the repository's own check did not fail
2026-10-10 11:14 ready → published (merged): on the trunk its modules follow: merged there, and its walk opened — or nothing for a walk to move
2026-10-10 11:14 published → delivered (done): nothing for a walk to move
The commit's note under refs/notes/mesh-plan keeps every transition: git log --notes=mesh-plan.
<!-- mesh-delivery:view -->
**Delivery** `novox/mesh-lab@719ca7ae0bdc` — **delivered** since 2026-10-10T11:14:27Z
**Delivery plan** — builds nothing: the change touches no module of the mesh's graph
**Transitions**
- 2026-10-10 11:06 (new) → proposed (announced): novox/mesh-lab#75's head announced
- 2026-10-10 11:07 proposed → checked (checked): the verdict names this commit
- 2026-10-10 11:07 checked → ready (accepted): the gate passed or warned, and the repository's own check did not fail
- 2026-10-10 11:14 ready → published (merged): on the trunk its modules follow: merged there, and its walk opened — or nothing for a walk to move
- 2026-10-10 11:14 published → delivered (done): nothing for a walk to move
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.
hq issue 362; the fix is mesh-catalog #171 (mesh-delivery), still on its branch, so
Beforeis the main it branched from (52f34d3) andFixits head f8c4bc5.The replay is
TestReplay362in modules/mesh-delivery/cmd/mesh-delivery/replay362_test.go, written with only what mesh-delivery had before the fix. It covers both orders in which the controller's two records can arrive.Proved with
go run ./cmd/prove --repos <clones> R362: "PROVED — before its fix fails, on its fix passes". Before the fix, the dunst delivery endssupersededand the walk is never let go.If #171 is rebased or squashed before merge,
Fixmust be updated to the commit that lands.Delivery
novox/mesh-lab@719ca7ae0bdc— delivered since 2026-10-10T11:14:27ZDelivery plan — builds nothing: the change touches no module of the mesh's graph
Transitions
The commit's note under
refs/notes/mesh-plankeeps every transition:git log --notes=mesh-plan.