The build seat now runs the gate itself (mesh-controller #101), judging a node-engine change with this tree's validator in the running controller because the module graph builds mesh-host from here. merge-check.sh becomes the repository's layer (mesh/repo-check): gofmt, vet, and the suite under -race when the toolchain has a C compiler.
Tested: the script passes locally. Do not merge before mesh-controller #101.
The build seat now runs the gate itself (mesh-controller #101), judging a node-engine change with this tree's validator in the running controller because the module graph builds mesh-host from here. `merge-check.sh` becomes the repository's layer (`mesh/repo-check`): gofmt, vet, and the suite under -race when the toolchain has a C compiler.
Tested: the script passes locally. Do not merge before mesh-controller #101.
The build seat now runs the gate itself, judging a node-engine change with the change's
validator in the running controller because the module graph builds mesh-host from here.
This script is the repository's own layer (mesh/repo-check): format, vet, and the suite
under the race detector when the toolchain can.
Deliverynovox/mesh-host@ad812a5888c3 — delivered since 2026-10-06T23:05:28Z
Machines
mesh-host on ace: passed — healthy 3 times over 2m37s
mesh-host on the rest running it: sent
Transitions
2026-10-06 23:05 (new) → proposed (announced): novox/mesh-host#43 merged; its head was not heard by this owner, so it is made from the forge's word
2026-10-06 23:05 proposed → held (merged-unchecked): merged without a passing check — a verdict known with it is taken first: only a person decides that it goes on
2026-10-06 23:05 held → delivering (go): its walk started on a word that was not this owner's: the controller's own path, which waits for nobody, or a person's plans go
2026-10-06 23:05 delivering → delivered (done): its walk is done: 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-host@ad812a5888c3` — **delivered** since 2026-10-06T23:05:28Z
**Machines**
- mesh-host on ace: passed — healthy 3 times over 2m37s
- mesh-host on the rest running it: sent
**Transitions**
- 2026-10-06 23:05 (new) → proposed (announced): novox/mesh-host#43 merged; its head was not heard by this owner, so it is made from the forge's word
- 2026-10-06 23:05 proposed → held (merged-unchecked): merged without a passing check — a verdict known with it is taken first: only a person decides that it goes on
- 2026-10-06 23:05 held → delivering (go): its walk started on a word that was not this owner's: the controller's own path, which waits for nobody, or a person's `plans go`
- 2026-10-06 23:05 delivering → delivered (done): its walk is done: 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.
The build seat now runs the gate itself (mesh-controller #101), judging a node-engine change with this tree's validator in the running controller because the module graph builds mesh-host from here.
merge-check.shbecomes the repository's layer (mesh/repo-check): gofmt, vet, and the suite under -race when the toolchain has a C compiler.Tested: the script passes locally. Do not merge before mesh-controller #101.
Delivery
novox/mesh-host@ad812a5888c3— delivered since 2026-10-06T23:05:28ZMachines
Transitions
plans goThe commit's note under
refs/notes/mesh-plankeeps every transition:git log --notes=mesh-plan.