This implements hq ADR 0269, which the operator accepted on 2026-10-09 (hq #238). It narrows ADR 0118's rule "never started on the way out".
Why. The zfs module (mesh-catalog #147) holds the distribution's zfs-scrub-weekly@<pool>.timer stopped and disabled while its own schedule scrubs the pool. On the home server the mesh found that timer running and enabled. Under ADR 0118 alone, unassigning the module would have left the pool with no scrub schedule, and nothing would have said so.
What changes.
store.Applied gains Declared: what the mesh held a service's unit to.
On removal, a unit found running or enabled that the declaration held stopped or disabled is started or enabled again. This happens only while it is still exactly as the mesh held it.
A masked unit is left as it is, and so is one somebody started or enabled since. In both cases the report says why.
If the restore fails (the start is refused, or the unit is not running after it), the engine undoes that attempt. The report says waiting, the record is kept, and the next apply tries again. No apply is made fatal.
The plan says "restore if still as the mesh held it … unless it is masked or was changed since".
A record from before Declared existed starts nothing.
Every call in internal/system that names a service's unit passes -- before it.
Tests.
internal/apply/giveback_test.go:
a unit given back running and enabled;
only what the mesh stopped is restored;
an old record starts nothing;
the plan's wording;
a masked unit, or one changed since, left alone;
a failed restore that waits and is never fatal, over two applies.
internal/system/dashdash_test.go: the -- before the unit.
All were written first and failed against the previous code. The tests' fake service managers read the new argument order through oldShape. The full suite passes.
This implements hq ADR 0269, which the operator accepted on 2026-10-09 (hq #238). It narrows ADR 0118's rule "never started on the way out".
**Why.** The zfs module (mesh-catalog #147) holds the distribution's `zfs-scrub-weekly@<pool>.timer` stopped and disabled while its own schedule scrubs the pool. On the home server the mesh found that timer running and enabled. Under ADR 0118 alone, unassigning the module would have left the pool with no scrub schedule, and nothing would have said so.
**What changes.**
- `store.Applied` gains `Declared`: what the mesh held a service's unit to.
- On removal, a unit found running or enabled that the declaration held stopped or disabled is started or enabled again. This happens **only while it is still exactly as the mesh held it**.
- A masked unit is left as it is, and so is one somebody started or enabled since. In both cases the report says why.
- If the restore fails (the start is refused, or the unit is not running after it), the engine undoes that attempt. The report says `waiting`, the record is kept, and the next apply tries again. No apply is made fatal.
- The plan says "restore if still as the mesh held it … unless it is masked or was changed since".
- A record from before `Declared` existed starts nothing.
- Every call in `internal/system` that names a service's unit passes `--` before it.
**Tests.**
- `internal/apply/giveback_test.go`:
- a unit given back running and enabled;
- only what the mesh stopped is restored;
- an old record starts nothing;
- the plan's wording;
- a masked unit, or one changed since, left alone;
- a failed restore that waits and is never fatal, over two applies.
- `internal/system/dashdash_test.go`: the `--` before the unit.
All were written first and failed against the previous code. The tests' fake service managers read the new argument order through `oldShape`. The full suite passes.
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)
A unit found running and enabled that a declaration held stopped and disabled stayed stopped and
disabled when the declaration went: ADR 0118 never starts a unit on the way out. Unassigning the zfs
module would so have left the home server's pool with no scrub schedule at all, said nowhere.
The host now records what it declared for a service (Declared, beside Found). On removal, a unit found
running and declared stopped is started again, and one found enabled and declared disabled is enabled
again, each read back; the report says restored, and the plan says it first. A record from before the
field starts nothing.
Deliverynovox/mesh-host@dfb14151bd20 — failed since 2026-10-09T00:54:49Z
Covered: covered after its failure: a later walk that contains it was delivered: plan-1791657606681868190 (novox/mesh-host at 9d8aa9d6 into main, done, contains its merge 690966d8)
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
Transitions
2026-10-09 00:04 (new) → proposed (announced): novox/mesh-host#66's head announced
2026-10-09 00:05 proposed → checked (checked): the verdict names this commit
2026-10-09 00:05 checked → ready (accepted): the gate passed or warned, and the repository's own check did not fail
2026-10-09 00:48 ready → proposed (recheck): checked at 00:05Z before mesh-host #64/#65 merged (same apply code); check against today's main before merging
2026-10-09 00:49 proposed → checked (checked): the verdict names this commit
2026-10-09 00:49 checked → ready (accepted): the gate passed or warned, and the repository's own check did not fail
2026-10-09 00:54 ready → published (merged): on the trunk its modules follow: merged there, and its walk opened — or nothing for a walk to move
2026-10-09 00:54 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
2026-10-09 00:54 delivering → failed (failed): its walk failed: a gate on a first machine (what it carried put back), a build, a machine
The commit's note under refs/notes/mesh-plan keeps every transition: git log --notes=mesh-plan.
<!-- mesh-delivery:view -->
**Delivery** `novox/mesh-host@dfb14151bd20` — **failed** since 2026-10-09T00:54:49Z
**Covered**: covered after its failure: a later walk that contains it was delivered: plan-1791657606681868190 (novox/mesh-host at 9d8aa9d6 into main, done, contains its merge 690966d8)
**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
**Transitions**
- 2026-10-09 00:04 (new) → proposed (announced): novox/mesh-host#66's head announced
- 2026-10-09 00:05 proposed → checked (checked): the verdict names this commit
- 2026-10-09 00:05 checked → ready (accepted): the gate passed or warned, and the repository's own check did not fail
- 2026-10-09 00:48 ready → proposed (recheck): checked at 00:05Z before mesh-host #64/#65 merged (same apply code); check against today's main before merging
- 2026-10-09 00:49 proposed → checked (checked): the verdict names this commit
- 2026-10-09 00:49 checked → ready (accepted): the gate passed or warned, and the repository's own check did not fail
- 2026-10-09 00:54 ready → published (merged): on the trunk its modules follow: merged there, and its walk opened — or nothing for a walk to move
- 2026-10-09 00:54 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
- 2026-10-09 00:54 delivering → failed (failed): its walk failed: a gate on a first machine (what it carried put back), a build, a machine
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
Run by the build seat on g14 as build-1791502546865216465 (builds --log build-1791502546865216465).
--- the gate: mesh-host
mesh-host: ok
long-running resources without health: 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-08T23:23:48Z 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-08T23:23:48Z
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
--- its merge-check.sh (go toolchain)
ok github.com/novox/mesh-host/cmd/mesh-bootstrap 1.014s
ok github.com/novox/mesh-host/cmd/mesh-host 5.281s
ok github.com/novox/mesh-host/examples 1.018s
ok github.com/novox/mesh-host/internal/accounts 1.021s
ok github.com/novox/mesh-host/internal/apply 2.200s
ok github.com/novox/mesh-host/internal/bootstrap 1.360s
ok github.com/novox/mesh-host/internal/bundle 1.020s
ok github.com/novox/mesh-host/internal/declaration 1.044s
ok github.com/novox/mesh-host/internal/firewall 1.787s
ok github.com/novox/mesh-host/internal/identity 1.044s
ok github.com/novox/mesh-host/internal/image 1.017s
ok github.com/novox/mesh-host/internal/inventory 1.025s
ok github.com/novox/mesh-host/internal/link 10.332s
ok github.com/novox/mesh-host/internal/liveness 2.044s
ok github.com/novox/mesh-host/internal/network 1.038s
ok github.com/novox/mesh-host/internal/outward 1.021s
ok github.com/novox/mesh-host/internal/profile 1.521s
ok github.com/novox/mesh-host/internal/reachable 1.021s
ok github.com/novox/mesh-host/internal/store 1.092s
ok github.com/novox/mesh-host/internal/system 1.028s
ok github.com/novox/mesh-host/internal/tunnel 1.018s
ok github.com/novox/mesh-host/internal/units 1.010s
ok github.com/novox/mesh-host/internal/upgrade 1.044s
ok github.com/novox/mesh-host/internal/witness 1.499s
ok github.com/novox/mesh-host/packaging 1.011s
ok github.com/novox/mesh-host/validate 1.010s
**Merge check** at `9d48b8ba`
- `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
Run by the build seat on g14 as `build-1791502546865216465` (`builds --log build-1791502546865216465`).
```
--- the gate: mesh-host
mesh-host: ok
long-running resources without health: 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-08T23:23:48Z 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-08T23:23:48Z
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
--- its merge-check.sh (go toolchain)
ok github.com/novox/mesh-host/cmd/mesh-bootstrap 1.014s
ok github.com/novox/mesh-host/cmd/mesh-host 5.281s
ok github.com/novox/mesh-host/examples 1.018s
ok github.com/novox/mesh-host/internal/accounts 1.021s
ok github.com/novox/mesh-host/internal/apply 2.200s
ok github.com/novox/mesh-host/internal/bootstrap 1.360s
ok github.com/novox/mesh-host/internal/bundle 1.020s
ok github.com/novox/mesh-host/internal/declaration 1.044s
ok github.com/novox/mesh-host/internal/firewall 1.787s
ok github.com/novox/mesh-host/internal/identity 1.044s
ok github.com/novox/mesh-host/internal/image 1.017s
ok github.com/novox/mesh-host/internal/inventory 1.025s
ok github.com/novox/mesh-host/internal/link 10.332s
ok github.com/novox/mesh-host/internal/liveness 2.044s
ok github.com/novox/mesh-host/internal/network 1.038s
ok github.com/novox/mesh-host/internal/outward 1.021s
ok github.com/novox/mesh-host/internal/profile 1.521s
ok github.com/novox/mesh-host/internal/reachable 1.021s
ok github.com/novox/mesh-host/internal/store 1.092s
ok github.com/novox/mesh-host/internal/system 1.028s
ok github.com/novox/mesh-host/internal/tunnel 1.018s
ok github.com/novox/mesh-host/internal/units 1.010s
ok github.com/novox/mesh-host/internal/upgrade 1.044s
ok github.com/novox/mesh-host/internal/witness 1.499s
ok github.com/novox/mesh-host/packaging 1.011s
ok github.com/novox/mesh-host/validate 1.010s
```
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)
Third review of mesh-catalog #147.
A unit's name can now come from a setting (a template's instance), so every systemctl call that names a
unit passes `--` before it, and a name can never be read as an option.
On removal, a unit is started or enabled again only when it is exactly the stopped and disabled the mesh
held it to. A masked unit, or one somebody started or enabled since, is left as it is, and the report
says why. A restore that fails (the start refused, or the unit not running after it) puts back what this
attempt changed and is reported as waiting, so no apply is made fatal by it and the next one tries again.
The tests' fake service managers read systemctl's arguments in the shape they were written for
(oldShape); internal/system's own test holds the `--`.
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
Run by the build seat on ace as build-1791503698460311801 (builds --log build-1791503698460311801).
--- the gate: mesh-host
mesh-host: ok
long-running resources without health: 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-08T23:47:08Z 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-08T23:47:08Z
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
--- its merge-check.sh (go toolchain)
ok github.com/novox/mesh-host/cmd/mesh-bootstrap 1.013s
ok github.com/novox/mesh-host/cmd/mesh-host 5.352s
ok github.com/novox/mesh-host/examples 1.017s
ok github.com/novox/mesh-host/internal/accounts 1.013s
ok github.com/novox/mesh-host/internal/apply 4.430s
ok github.com/novox/mesh-host/internal/bootstrap 1.529s
ok github.com/novox/mesh-host/internal/bundle 1.012s
ok github.com/novox/mesh-host/internal/declaration 1.053s
ok github.com/novox/mesh-host/internal/firewall 1.628s
ok github.com/novox/mesh-host/internal/identity 1.093s
ok github.com/novox/mesh-host/internal/image 1.061s
ok github.com/novox/mesh-host/internal/inventory 1.065s
ok github.com/novox/mesh-host/internal/link 10.372s
ok github.com/novox/mesh-host/internal/liveness 2.097s
ok github.com/novox/mesh-host/internal/network 1.080s
ok github.com/novox/mesh-host/internal/outward 1.065s
ok github.com/novox/mesh-host/internal/profile 1.531s
ok github.com/novox/mesh-host/internal/reachable 1.030s
ok github.com/novox/mesh-host/internal/store 1.263s
ok github.com/novox/mesh-host/internal/system 1.031s
ok github.com/novox/mesh-host/internal/tunnel 1.036s
ok github.com/novox/mesh-host/internal/units 1.028s
ok github.com/novox/mesh-host/internal/upgrade 1.126s
ok github.com/novox/mesh-host/internal/witness 4.574s
ok github.com/novox/mesh-host/packaging 1.030s
ok github.com/novox/mesh-host/validate 1.028s
**Merge check** at `a018ebd1`
- `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
Run by the build seat on ace as `build-1791503698460311801` (`builds --log build-1791503698460311801`).
```
--- the gate: mesh-host
mesh-host: ok
long-running resources without health: 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-08T23:47:08Z 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-08T23:47:08Z
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
--- its merge-check.sh (go toolchain)
ok github.com/novox/mesh-host/cmd/mesh-bootstrap 1.013s
ok github.com/novox/mesh-host/cmd/mesh-host 5.352s
ok github.com/novox/mesh-host/examples 1.017s
ok github.com/novox/mesh-host/internal/accounts 1.013s
ok github.com/novox/mesh-host/internal/apply 4.430s
ok github.com/novox/mesh-host/internal/bootstrap 1.529s
ok github.com/novox/mesh-host/internal/bundle 1.012s
ok github.com/novox/mesh-host/internal/declaration 1.053s
ok github.com/novox/mesh-host/internal/firewall 1.628s
ok github.com/novox/mesh-host/internal/identity 1.093s
ok github.com/novox/mesh-host/internal/image 1.061s
ok github.com/novox/mesh-host/internal/inventory 1.065s
ok github.com/novox/mesh-host/internal/link 10.372s
ok github.com/novox/mesh-host/internal/liveness 2.097s
ok github.com/novox/mesh-host/internal/network 1.080s
ok github.com/novox/mesh-host/internal/outward 1.065s
ok github.com/novox/mesh-host/internal/profile 1.531s
ok github.com/novox/mesh-host/internal/reachable 1.030s
ok github.com/novox/mesh-host/internal/store 1.263s
ok github.com/novox/mesh-host/internal/system 1.031s
ok github.com/novox/mesh-host/internal/tunnel 1.036s
ok github.com/novox/mesh-host/internal/units 1.028s
ok github.com/novox/mesh-host/internal/upgrade 1.126s
ok github.com/novox/mesh-host/internal/witness 4.574s
ok github.com/novox/mesh-host/packaging 1.030s
ok github.com/novox/mesh-host/validate 1.028s
```
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)
mesh/delivery covered after its failure: a later walk that contains it was delivered: plan-1791657606681868190 (novox/mesh-host at 9d8aa9d6 into main, do…
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
Run by the build seat on ace as build-1791504243580078458 (builds --log build-1791504243580078458).
--- 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-08T23:57:57Z 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-08T23:57:57Z
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
--- its merge-check.sh (go toolchain)
ok github.com/novox/mesh-host/cmd/mesh-bootstrap 1.012s
ok github.com/novox/mesh-host/cmd/mesh-host 5.351s
ok github.com/novox/mesh-host/examples 1.015s
ok github.com/novox/mesh-host/internal/accounts 1.013s
ok github.com/novox/mesh-host/internal/apply 4.526s
ok github.com/novox/mesh-host/internal/bootstrap 1.508s
ok github.com/novox/mesh-host/internal/bundle 1.027s
ok github.com/novox/mesh-host/internal/declaration 1.066s
ok github.com/novox/mesh-host/internal/firewall 1.658s
ok github.com/novox/mesh-host/internal/identity 1.115s
ok github.com/novox/mesh-host/internal/image 1.037s
ok github.com/novox/mesh-host/internal/inventory 1.036s
ok github.com/novox/mesh-host/internal/link 10.330s
ok github.com/novox/mesh-host/internal/liveness 2.076s
ok github.com/novox/mesh-host/internal/network 1.053s
ok github.com/novox/mesh-host/internal/outward 1.042s
ok github.com/novox/mesh-host/internal/profile 1.509s
ok github.com/novox/mesh-host/internal/reachable 1.040s
ok github.com/novox/mesh-host/internal/store 1.206s
ok github.com/novox/mesh-host/internal/system 1.041s
ok github.com/novox/mesh-host/internal/tunnel 1.044s
ok github.com/novox/mesh-host/internal/units 1.033s
ok github.com/novox/mesh-host/internal/upgrade 1.138s
ok github.com/novox/mesh-host/internal/witness 4.661s
ok github.com/novox/mesh-host/packaging 1.034s
ok github.com/novox/mesh-host/validate 1.032s
**Merge check** at `dfb14151`
- `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
Run by the build seat on ace as `build-1791504243580078458` (`builds --log build-1791504243580078458`).
```
--- 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-08T23:57:57Z 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-08T23:57:57Z
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
--- its merge-check.sh (go toolchain)
ok github.com/novox/mesh-host/cmd/mesh-bootstrap 1.012s
ok github.com/novox/mesh-host/cmd/mesh-host 5.351s
ok github.com/novox/mesh-host/examples 1.015s
ok github.com/novox/mesh-host/internal/accounts 1.013s
ok github.com/novox/mesh-host/internal/apply 4.526s
ok github.com/novox/mesh-host/internal/bootstrap 1.508s
ok github.com/novox/mesh-host/internal/bundle 1.027s
ok github.com/novox/mesh-host/internal/declaration 1.066s
ok github.com/novox/mesh-host/internal/firewall 1.658s
ok github.com/novox/mesh-host/internal/identity 1.115s
ok github.com/novox/mesh-host/internal/image 1.037s
ok github.com/novox/mesh-host/internal/inventory 1.036s
ok github.com/novox/mesh-host/internal/link 10.330s
ok github.com/novox/mesh-host/internal/liveness 2.076s
ok github.com/novox/mesh-host/internal/network 1.053s
ok github.com/novox/mesh-host/internal/outward 1.042s
ok github.com/novox/mesh-host/internal/profile 1.509s
ok github.com/novox/mesh-host/internal/reachable 1.040s
ok github.com/novox/mesh-host/internal/store 1.206s
ok github.com/novox/mesh-host/internal/system 1.041s
ok github.com/novox/mesh-host/internal/tunnel 1.044s
ok github.com/novox/mesh-host/internal/units 1.033s
ok github.com/novox/mesh-host/internal/upgrade 1.138s
ok github.com/novox/mesh-host/internal/witness 4.661s
ok github.com/novox/mesh-host/packaging 1.034s
ok github.com/novox/mesh-host/validate 1.032s
```
mesh-admin
changed title from Start again on removal what the mesh's own declaration stopped (hq ADR 0269, proposed) to Start again on removal what the mesh's own declaration stopped (hq ADR 0269)2026-10-09 00:17:45 +00:00
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
Run by the build seat on ace as build-1791506884912535378 (builds --log build-1791506884912535378).
--- 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-09T00:43:55Z 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-09T00:43:55Z
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
--- its merge-check.sh (go toolchain)
ok github.com/novox/mesh-host/cmd/mesh-bootstrap 1.016s
ok github.com/novox/mesh-host/cmd/mesh-host 5.316s
ok github.com/novox/mesh-host/examples 1.019s
ok github.com/novox/mesh-host/internal/accounts 1.014s
ok github.com/novox/mesh-host/internal/apply 4.339s
ok github.com/novox/mesh-host/internal/bootstrap 1.480s
ok github.com/novox/mesh-host/internal/bundle 1.020s
ok github.com/novox/mesh-host/internal/declaration 1.051s
ok github.com/novox/mesh-host/internal/firewall 1.659s
ok github.com/novox/mesh-host/internal/identity 1.091s
ok github.com/novox/mesh-host/internal/image 1.023s
ok github.com/novox/mesh-host/internal/inventory 1.023s
ok github.com/novox/mesh-host/internal/link 10.327s
ok github.com/novox/mesh-host/internal/liveness 2.051s
ok github.com/novox/mesh-host/internal/network 1.040s
ok github.com/novox/mesh-host/internal/outward 1.030s
ok github.com/novox/mesh-host/internal/profile 1.491s
ok github.com/novox/mesh-host/internal/reachable 1.017s
ok github.com/novox/mesh-host/internal/store 1.185s
ok github.com/novox/mesh-host/internal/system 1.017s
ok github.com/novox/mesh-host/internal/tunnel 1.019s
ok github.com/novox/mesh-host/internal/units 1.014s
ok github.com/novox/mesh-host/internal/upgrade 1.104s
ok github.com/novox/mesh-host/internal/witness 4.417s
ok github.com/novox/mesh-host/packaging 1.012s
ok github.com/novox/mesh-host/validate 1.011s
**Merge check** at `dfb14151`
- `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
Run by the build seat on ace as `build-1791506884912535378` (`builds --log build-1791506884912535378`).
```
--- 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-09T00:43:55Z 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-09T00:43:55Z
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
--- its merge-check.sh (go toolchain)
ok github.com/novox/mesh-host/cmd/mesh-bootstrap 1.016s
ok github.com/novox/mesh-host/cmd/mesh-host 5.316s
ok github.com/novox/mesh-host/examples 1.019s
ok github.com/novox/mesh-host/internal/accounts 1.014s
ok github.com/novox/mesh-host/internal/apply 4.339s
ok github.com/novox/mesh-host/internal/bootstrap 1.480s
ok github.com/novox/mesh-host/internal/bundle 1.020s
ok github.com/novox/mesh-host/internal/declaration 1.051s
ok github.com/novox/mesh-host/internal/firewall 1.659s
ok github.com/novox/mesh-host/internal/identity 1.091s
ok github.com/novox/mesh-host/internal/image 1.023s
ok github.com/novox/mesh-host/internal/inventory 1.023s
ok github.com/novox/mesh-host/internal/link 10.327s
ok github.com/novox/mesh-host/internal/liveness 2.051s
ok github.com/novox/mesh-host/internal/network 1.040s
ok github.com/novox/mesh-host/internal/outward 1.030s
ok github.com/novox/mesh-host/internal/profile 1.491s
ok github.com/novox/mesh-host/internal/reachable 1.017s
ok github.com/novox/mesh-host/internal/store 1.185s
ok github.com/novox/mesh-host/internal/system 1.017s
ok github.com/novox/mesh-host/internal/tunnel 1.019s
ok github.com/novox/mesh-host/internal/units 1.014s
ok github.com/novox/mesh-host/internal/upgrade 1.104s
ok github.com/novox/mesh-host/internal/witness 4.417s
ok github.com/novox/mesh-host/packaging 1.012s
ok github.com/novox/mesh-host/validate 1.011s
```
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.
This implements hq ADR 0269, which the operator accepted on 2026-10-09 (hq #238). It narrows ADR 0118's rule "never started on the way out".
Why. The zfs module (mesh-catalog #147) holds the distribution's
zfs-scrub-weekly@<pool>.timerstopped and disabled while its own schedule scrubs the pool. On the home server the mesh found that timer running and enabled. Under ADR 0118 alone, unassigning the module would have left the pool with no scrub schedule, and nothing would have said so.What changes.
store.AppliedgainsDeclared: what the mesh held a service's unit to.waiting, the record is kept, and the next apply tries again. No apply is made fatal.Declaredexisted starts nothing.internal/systemthat names a service's unit passes--before it.Tests.
internal/apply/giveback_test.go:internal/system/dashdash_test.go: the--before the unit.All were written first and failed against the previous code. The tests' fake service managers read the new argument order through
oldShape. The full suite passes.Delivery
novox/mesh-host@dfb14151bd20— failed since 2026-10-09T00:54:49ZCovered: covered after its failure: a later walk that contains it was delivered: plan-1791657606681868190 (novox/mesh-host at
9d8aa9d6into main, done, contains its merge690966d8)Delivery plan — builds mesh-host → ace, g14, novox, shanks; no bus step
Transitions
The commit's note under
refs/notes/mesh-plankeeps every transition:git log --notes=mesh-plan.Merge check at
9d48b8bamesh/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 g14 as
build-1791502546865216465(builds --log build-1791502546865216465).Merge check at
a018ebd1mesh/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-1791503698460311801(builds --log build-1791503698460311801).Merge check at
dfb14151mesh/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-1791504243580078458(builds --log build-1791504243580078458).Start again on removal what the mesh's own declaration stopped (hq ADR 0269, proposed)to Start again on removal what the mesh's own declaration stopped (hq ADR 0269)Merge check at
dfb14151mesh/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-1791506884912535378(builds --log build-1791506884912535378).