Fixes the engine's half of novox/hq issue 458 (a restart count read as "since then"); the controller's half is mesh-controller#243.
The journal line said ..., N restart(s) counted. The number is the liveness judge's own kept.Counted: every rise of systemd's NRestarts or the runtime's RestartCount after a start's grace, kept across recreates, starts by hand and the engine's own restarts, forgotten only when the resource is no longer declared. It now reads N automatic restart(s) since this engine began watching it, from a small unhealthyWords function.
Test: TestAnUnhealthyResourceSaysWhatItsRestartCountCounts. On main it does not compile, because main has no such function. go vet and go test -race ./cmd/mesh-host are green.
Fixes the engine's half of novox/hq issue 458 (a restart count read as "since then"); the controller's half is mesh-controller#243.
The journal line said `..., N restart(s) counted`. The number is the liveness judge's own `kept.Counted`: every rise of systemd's NRestarts or the runtime's RestartCount after a start's grace, kept across recreates, starts by hand and the engine's own restarts, forgotten only when the resource is no longer declared. It now reads `N automatic restart(s) since this engine began watching it`, from a small `unhealthyWords` function.
Test: `TestAnUnhealthyResourceSaysWhatItsRestartCountCounts`. On main it does not compile, because main has no such function. `go vet` and `go test -race ./cmd/mesh-host` are green.
mesh/merge-gate pass: builds mesh-host → ace, g14, novox, shanks; no bus step; every machine composes with the change as it did without (4 of 4 compose)
Deliverynovox/mesh-host@a18d09db753e — delivered since 2026-10-12T09:12:37Z
Delivery plan — builds mesh-host → ace, g14, novox, shanks; no bus step
tier 0: mesh-host
ace: receives mesh-host
g14: receives mesh-host
novox: receives mesh-host
shanks: receives mesh-host
grants step: if this changes what the bus's user list says (a new tool, subject or user), novox is sent that list alone, every build there kept, before mesh-host is judged on its first machine
composed together: pass — every machine composes with the change as it did without (4 of 4 compose)
Machines
mesh-host on ace: passed — healthy 3 times over 2m40s
mesh-tools on every machine running it: sent
node-tools on ace: passed — judged with mesh-host: healthy 3 times over 2m40s
mesh-host on the rest running it: sent
node-tools on the rest running it: sent
Transitions
2026-10-12 08:47 (new) → proposed (announced): novox/mesh-host#84's head announced
2026-10-12 08:51 proposed → checked (checked): the verdict names this commit
2026-10-12 08:51 checked → ready (accepted): the gate passed or warned, and the repository's own check did not fail
2026-10-12 09:08 ready → published (merged): on the trunk its modules follow: merged there, and its walk opened — or nothing for a walk to move
2026-10-12 09:08 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-12 09:12 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-host@a18d09db753e` — **delivered** since 2026-10-12T09:12:37Z
**Delivery plan** — builds mesh-host → ace, g14, novox, shanks; no bus step
- tier 0: mesh-host
- ace: receives mesh-host
- g14: receives mesh-host
- novox: receives mesh-host
- shanks: receives mesh-host
- grants step: if this changes what the bus's user list says (a new tool, subject or user), novox is sent that list alone, every build there kept, before mesh-host is judged on its first machine
**Group** `fix/458-restarts-say-what-they-count`, in order: novox/mesh-host@a18d09db753e → novox/mesh-controller@cde0dc287bf5
- novox/mesh-host@a18d09db753e before novox/mesh-controller@cde0dc287bf5: engine before controller
- composed together: pass — every machine composes with the change as it did without (4 of 4 compose)
**Machines**
- mesh-host on ace: passed — healthy 3 times over 2m40s
- mesh-tools on every machine running it: sent
- node-tools on ace: passed — judged with mesh-host: healthy 3 times over 2m40s
- mesh-host on the rest running it: sent
- node-tools on the rest running it: sent
**Transitions**
- 2026-10-12 08:47 (new) → proposed (announced): novox/mesh-host#84's head announced
- 2026-10-12 08:51 proposed → checked (checked): the verdict names this commit
- 2026-10-12 08:51 checked → ready (accepted): the gate passed or warned, and the repository's own check did not fail
- 2026-10-12 09:08 ready → published (merged): on the trunk its modules follow: merged there, and its walk opened — or nothing for a walk to move
- 2026-10-12 09:08 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-12 09:12 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/merge-gate: PASS — every machine composes with the change as it did without (4 of 4 compose) (modules: mesh-host)
mesh/repo-check: PASS — its merge-check.sh passed
Delivery plan — builds mesh-host → ace, g14, novox, shanks; no bus step
tier 0: mesh-host
ace: receives mesh-host
g14: receives mesh-host
novox: receives mesh-host
shanks: receives mesh-host
grants step: if this changes what the bus's user list says (a new tool, subject or user), novox is sent that list alone, every build there kept, before mesh-host is judged on its first machine
read by no module's build: cmd/mesh-host/restarts_words_test.go
Run by the build seat on ace as build-1791794862568341274 (builds --log build-1791794862568341274).
--- the gate: mesh-host
mesh-host: ok
long-running resources without health: 0
files asking for a setting without saying whether it is trusted: 0
1 manifest(s) checked. Judged against the seats this binary carries; a claim on one of the mesh's own seats is judged fully at registration, and a seat declared by a module not given here reads as unknown. Identities judged on a 6-character machine name, against the bounds of the providers given here
judging 0 module(s) changed against 4 machine(s), as the snapshot of 2026-10-12T08:35:24Z says they run
composing every machine as the mesh is
the bus's user list leaves out 5 user(s) the mesh has minted no credential for: controller, node.f35, node.idt, node.ygcyr, node.yvbpsm. Each is a user that cannot connect until one is issued
the bus's user list leaves out 5 user(s) the mesh has minted no credential for: controller, node.f35, node.idt, node.ygcyr, node.yvbpsm. Each is a user that cannot connect until one is issued
composing every machine with the change
the bus's user list leaves out 5 user(s) the mesh has minted no credential for: controller, node.f35, node.idt, node.ygcyr, node.yvbpsm. Each is a user that cannot connect until one is issued
the bus's user list leaves out 5 user(s) the mesh has minted no credential for: controller, node.f35, node.idt, node.ygcyr, node.yvbpsm. Each is a user that cannot connect until one is issued
merge gate: PASS — every machine composes with the change as it did without (4 of 4 compose)
judged by controller development build against the facts of 2026-10-12T08:35:24Z
machines:
- a machine (f35): composes
- holds mesh-dns-resolver (idt): composes
- holds git, holds mesh-artifact-store, holds mesh-broker, holds mesh-catalog, holds mesh-delivery, holds mesh-dns-resolver, holds mesh-store, holds mesh-vault, holds npm-package-registry, the control node, the hub (ygcyr): composes
- a machine (yvbpsm): composes
a merge would rebuild 1 module(s) in 1 tier(s): mesh-host
notes:
- cmd/mesh-host/restarts_words_test.go read by no module's build, and rebuild nothing (issue 280)
--- its merge-check.sh (go toolchain)
ok github.com/novox/mesh-host/cmd/mesh-bootstrap 1.021s
ok github.com/novox/mesh-host/cmd/mesh-host 5.575s
ok github.com/novox/mesh-host/examples 1.026s
ok github.com/novox/mesh-host/internal/accounts 1.503s
ok github.com/novox/mesh-host/internal/apply 5.125s
ok github.com/novox/mesh-host/internal/bootstrap 1.586s
ok github.com/novox/mesh-host/internal/bundle 1.045s
ok github.com/novox/mesh-host/internal/declaration 1.078s
ok github.com/novox/mesh-host/internal/firewall 1.771s
ok github.com/novox/mesh-host/internal/identity 1.119s
ok github.com/novox/mesh-host/internal/image 1.050s
ok github.com/novox/mesh-host/internal/inventory 1.034s
ok github.com/novox/mesh-host/internal/link 10.507s
ok github.com/novox/mesh-host/internal/liveness 2.151s
ok github.com/novox/mesh-host/internal/meshcli 1.588s
ok github.com/novox/mesh-host/internal/network 1.068s
ok github.com/novox/mesh-host/internal/outward 1.052s
ok github.com/novox/mesh-host/internal/profile 1.523s
ok github.com/novox/mesh-host/internal/reachable 1.047s
ok github.com/novox/mesh-host/internal/store 1.237s
ok github.com/novox/mesh-host/internal/system 1.055s
ok github.com/novox/mesh-host/internal/tunnel 1.049s
ok github.com/novox/mesh-host/internal/units 1.045s
ok github.com/novox/mesh-host/internal/upgrade 1.173s
ok github.com/novox/mesh-host/internal/witness 4.939s
ok github.com/novox/mesh-host/packaging 1.049s
? github.com/novox/mesh-host/rootsearch [no test files]
ok github.com/novox/mesh-host/validate 1.041s
**Merge check** at `a18d09db`
- `mesh/merge-gate`: **PASS** — every machine composes with the change as it did without (4 of 4 compose) (modules: mesh-host)
- `mesh/repo-check`: **PASS** — its merge-check.sh passed
**Delivery plan** — builds mesh-host → ace, g14, novox, shanks; no bus step
- tier 0: mesh-host
- ace: receives mesh-host
- g14: receives mesh-host
- novox: receives mesh-host
- shanks: receives mesh-host
- grants step: if this changes what the bus's user list says (a new tool, subject or user), novox is sent that list alone, every build there kept, before mesh-host is judged on its first machine
- read by no module's build: cmd/mesh-host/restarts_words_test.go
Run by the build seat on ace as `build-1791794862568341274` (`builds --log build-1791794862568341274`).
```
--- the gate: mesh-host
mesh-host: ok
long-running resources without health: 0
files asking for a setting without saying whether it is trusted: 0
1 manifest(s) checked. Judged against the seats this binary carries; a claim on one of the mesh's own seats is judged fully at registration, and a seat declared by a module not given here reads as unknown. Identities judged on a 6-character machine name, against the bounds of the providers given here
judging 0 module(s) changed against 4 machine(s), as the snapshot of 2026-10-12T08:35:24Z says they run
composing every machine as the mesh is
the bus's user list leaves out 5 user(s) the mesh has minted no credential for: controller, node.f35, node.idt, node.ygcyr, node.yvbpsm. Each is a user that cannot connect until one is issued
the bus's user list leaves out 5 user(s) the mesh has minted no credential for: controller, node.f35, node.idt, node.ygcyr, node.yvbpsm. Each is a user that cannot connect until one is issued
composing every machine with the change
the bus's user list leaves out 5 user(s) the mesh has minted no credential for: controller, node.f35, node.idt, node.ygcyr, node.yvbpsm. Each is a user that cannot connect until one is issued
the bus's user list leaves out 5 user(s) the mesh has minted no credential for: controller, node.f35, node.idt, node.ygcyr, node.yvbpsm. Each is a user that cannot connect until one is issued
merge gate: PASS — every machine composes with the change as it did without (4 of 4 compose)
judged by controller development build against the facts of 2026-10-12T08:35:24Z
machines:
- a machine (f35): composes
- holds mesh-dns-resolver (idt): composes
- holds git, holds mesh-artifact-store, holds mesh-broker, holds mesh-catalog, holds mesh-delivery, holds mesh-dns-resolver, holds mesh-store, holds mesh-vault, holds npm-package-registry, the control node, the hub (ygcyr): composes
- a machine (yvbpsm): composes
a merge would rebuild 1 module(s) in 1 tier(s): mesh-host
notes:
- cmd/mesh-host/restarts_words_test.go read by no module's build, and rebuild nothing (issue 280)
--- its merge-check.sh (go toolchain)
ok github.com/novox/mesh-host/cmd/mesh-bootstrap 1.021s
ok github.com/novox/mesh-host/cmd/mesh-host 5.575s
ok github.com/novox/mesh-host/examples 1.026s
ok github.com/novox/mesh-host/internal/accounts 1.503s
ok github.com/novox/mesh-host/internal/apply 5.125s
ok github.com/novox/mesh-host/internal/bootstrap 1.586s
ok github.com/novox/mesh-host/internal/bundle 1.045s
ok github.com/novox/mesh-host/internal/declaration 1.078s
ok github.com/novox/mesh-host/internal/firewall 1.771s
ok github.com/novox/mesh-host/internal/identity 1.119s
ok github.com/novox/mesh-host/internal/image 1.050s
ok github.com/novox/mesh-host/internal/inventory 1.034s
ok github.com/novox/mesh-host/internal/link 10.507s
ok github.com/novox/mesh-host/internal/liveness 2.151s
ok github.com/novox/mesh-host/internal/meshcli 1.588s
ok github.com/novox/mesh-host/internal/network 1.068s
ok github.com/novox/mesh-host/internal/outward 1.052s
ok github.com/novox/mesh-host/internal/profile 1.523s
ok github.com/novox/mesh-host/internal/reachable 1.047s
ok github.com/novox/mesh-host/internal/store 1.237s
ok github.com/novox/mesh-host/internal/system 1.055s
ok github.com/novox/mesh-host/internal/tunnel 1.049s
ok github.com/novox/mesh-host/internal/units 1.045s
ok github.com/novox/mesh-host/internal/upgrade 1.173s
ok github.com/novox/mesh-host/internal/witness 4.939s
ok github.com/novox/mesh-host/packaging 1.049s
? github.com/novox/mesh-host/rootsearch [no test files]
ok github.com/novox/mesh-host/validate 1.041s
```
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 the engine's half of novox/hq issue 458 (a restart count read as "since then"); the controller's half is mesh-controller#243.
The journal line said
..., N restart(s) counted. The number is the liveness judge's ownkept.Counted: every rise of systemd's NRestarts or the runtime's RestartCount after a start's grace, kept across recreates, starts by hand and the engine's own restarts, forgotten only when the resource is no longer declared. It now readsN automatic restart(s) since this engine began watching it, from a smallunhealthyWordsfunction.Test:
TestAnUnhealthyResourceSaysWhatItsRestartCountCounts. On main it does not compile, because main has no such function.go vetandgo test -race ./cmd/mesh-hostare green.Delivery
novox/mesh-host@a18d09db753e— delivered since 2026-10-12T09:12:37ZDelivery plan — builds mesh-host → ace, g14, novox, shanks; no bus step
Group
fix/458-restarts-say-what-they-count, in order: novox/mesh-host@a18d09db75 → novox/mesh-controller@cde0dc287bMachines
Transitions
The commit's note under
refs/notes/mesh-plankeeps every transition:git log --notes=mesh-plan.Merge check at
a18d09dbmesh/merge-gate: PASS — every machine composes with the change as it did without (4 of 4 compose) (modules: mesh-host)mesh/repo-check: PASS — its merge-check.sh passedDelivery plan — builds mesh-host → ace, g14, novox, shanks; no bus step
Run by the build seat on ace as
build-1791794862568341274(builds --log build-1791794862568341274).