Registers the replay of hq issue 318: TestReplay318 in mesh-controller, laid over the commit before its fix (9b86fa9).
go run ./cmd/prove R318:
R318 (issue 318): PROVED — before its fix fails, on its fix passes
before: replay318_test.go:203: the walk is failed on []: failed its gate on laptop: not healthy within 0s of its apply: its account openrazer.operator on laptop is unhealthy: relogin needed: …
Merge order of the delivery group: mesh-host, mesh-controller, then this, then hq.
Registers the replay of hq issue 318: `TestReplay318` in mesh-controller, laid over the commit before its fix (9b86fa9).
`go run ./cmd/prove R318`:
```
R318 (issue 318): PROVED — before its fix fails, on its fix passes
before: replay318_test.go:203: the walk is failed on []: failed its gate on laptop: not healthy within 0s of its apply: its account openrazer.operator on laptop is unhealthy: relogin needed: …
```
Merge order of the delivery group: mesh-host, mesh-controller, then this, then hq.
composed together: pass — every machine composes with the change as it did without (4 of 4 compose)
Transitions
2026-10-08 12:38 (new) → proposed (announced): novox/mesh-lab#67's head announced
2026-10-08 12:38 proposed → checked (checked): the verdict names this commit
2026-10-08 12:38 checked → ready (accepted): the gate passed or warned, and the repository's own check did not fail
2026-10-08 13:03 ready → published (merged): on the trunk its modules follow: merged there, and its walk opened — or nothing for a walk to move
2026-10-08 13:03 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@1455d9560e1c` — **delivered** since 2026-10-08T13:03:25Z
**Delivery plan** — builds nothing: the change touches no module of the mesh's graph
**Group** `fix/318-a-wait-for-a-person-is-not-a-failure`, in order: novox/hq@01e48196f747 → novox/mesh-controller@51d7bbfdc88c → novox/mesh-host@9d8398206e5b → novox/mesh-lab@1455d9560e1c
- novox/mesh-controller@51d7bbfdc88c before novox/mesh-host@9d8398206e5b: built by, over engine before controller
- composed together: pass — every machine composes with the change as it did without (4 of 4 compose)
**Transitions**
- 2026-10-08 12:38 (new) → proposed (announced): novox/mesh-lab#67's head announced
- 2026-10-08 12:38 proposed → checked (checked): the verdict names this commit
- 2026-10-08 12:38 checked → ready (accepted): the gate passed or warned, and the repository's own check did not fail
- 2026-10-08 13:03 ready → published (merged): on the trunk its modules follow: merged there, and its walk opened — or nothing for a walk to move
- 2026-10-08 13:03 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.
Registers the replay of hq issue 318:
TestReplay318in mesh-controller, laid over the commit before its fix (9b86fa9).go run ./cmd/prove R318:Merge order of the delivery group: mesh-host, mesh-controller, then this, then hq.
Delivery
novox/mesh-lab@1455d9560e1c— delivered since 2026-10-08T13:03:25ZDelivery plan — builds nothing: the change touches no module of the mesh's graph
Group
fix/318-a-wait-for-a-person-is-not-a-failure, in order: novox/hq@01e48196f7 → novox/mesh-controller@51d7bbfdc8 → novox/mesh-host@9d8398206e → novox/mesh-lab@1455d9560eTransitions
The commit's note under
refs/notes/mesh-plankeeps every transition:git log --notes=mesh-plan.