Fixes novox/hq issue 495 (the node-engine refused a directory as not placed, said nothing was touched, then wrote a file into it).
On ace on 2026-10-11 at 12:42:08 the engine refused docker.state (/var/lib/docker), then created docker.log-rotation (/var/lib/docker/log-rotation.conf) and ran the module's step.
What changes
A refused directory gates the rest of its module (internal/apply/apply.go), as a run-once step that did not complete already does (ADR 0136's gated). Only the placement guard's refusals gate; a directory that failed to be made for another reason stays an ordinary failure. Each skipped resource says its directory <path> was refused (novox/hq issue 495), so nothing more of this module was attempted, and the journal says gated <module>.*: its directory <path> was refused.
A file is judged by the same guard as a directory (refusedPlaces in internal/apply/placement_guard.go, rule 6 in its header): it is refused in a forbidden tree (rule 2, the runtimes' data roots included) or in the engine's own trees (except the engine's own module), and below any refused directory or access, whatever its module and declared order. An archive is refused below a refused path. Rules 3 and 4 (a directory's owner below /etc or a home) do not apply to files.
The failure says truthfully what was not attempted: Error.Modules names the gated modules, and the message reads the rest of <module> was not attempted and is listed as skipped; everything else was attempted, so what is not listed as failed or skipped was done. It no longer says everything was attempted. This also corrects the step gate's message, which said this is an action for a module's step.
Tests (written first, both failed on main, commit 1acfed4)
TestARefusedDirectoryGatesItsModule: the shape from ace (a directory at the runtime's data root, a file below it, a run-once step after it, another module's file). On main the file was written, the step ran, and the report said everything was attempted. Now nothing is written below the directory, the step does not run, both are reported as skipped naming the directory, the other module's file is applied, and the message names the module.
TestAFileIsJudgedByTheSameGuardAsADirectory: a file in the runtime's data root is refused; a file declared before a refused directory below a home is refused and not written.
sh merge-check.sh passes locally (gofmt, vet, every test under the race detector).
Live impact checked
I read the controller's current plan for ace, g14, novox and shanks: no file, archive or directory of any module but mesh-host is in a forbidden tree or the engine's own trees (mesh-host.launcher and mesh-host.next are the engine's own, allowed). The journals of novox, shanks and g14 since 2026-10-10 18:00 show no is not placed refusal, so no module there becomes gated by this change. ace's tools did not answer at the time, so ace's journal was not read.
Fixes novox/hq issue 495 (the node-engine refused a directory as not placed, said nothing was touched, then wrote a file into it).
On ace on 2026-10-11 at 12:42:08 the engine refused `docker.state` (/var/lib/docker), then created `docker.log-rotation` (/var/lib/docker/log-rotation.conf) and ran the module's step.
## What changes
- **A refused directory gates the rest of its module** (`internal/apply/apply.go`), as a run-once step that did not complete already does (ADR 0136's `gated`). Only the placement guard's refusals gate; a directory that failed to be made for another reason stays an ordinary failure. Each skipped resource says `its directory <path> was refused (novox/hq issue 495), so nothing more of this module was attempted`, and the journal says `gated <module>.*: its directory <path> was refused`.
- **A file is judged by the same guard as a directory** (`refusedPlaces` in `internal/apply/placement_guard.go`, rule 6 in its header): it is refused in a forbidden tree (rule 2, the runtimes' data roots included) or in the engine's own trees (except the engine's own module), and below any refused directory or access, whatever its module and declared order. An archive is refused below a refused path. Rules 3 and 4 (a directory's owner below /etc or a home) do not apply to files.
- **The failure says truthfully what was not attempted**: `Error.Modules` names the gated modules, and the message reads `the rest of <module> was not attempted and is listed as skipped; everything else was attempted, so what is not listed as failed or skipped was done.` It no longer says `everything was attempted`. This also corrects the step gate's message, which said `this is an action` for a module's step.
## Tests (written first, both failed on main, commit 1acfed4)
- `TestARefusedDirectoryGatesItsModule`: the shape from ace (a directory at the runtime's data root, a file below it, a run-once step after it, another module's file). On main the file was written, the step ran, and the report said everything was attempted. Now nothing is written below the directory, the step does not run, both are reported as skipped naming the directory, the other module's file is applied, and the message names the module.
- `TestAFileIsJudgedByTheSameGuardAsADirectory`: a file in the runtime's data root is refused; a file declared *before* a refused directory below a home is refused and not written.
`sh merge-check.sh` passes locally (gofmt, vet, every test under the race detector).
## Live impact checked
I read the controller's current plan for ace, g14, novox and shanks: no file, archive or directory of any module but `mesh-host` is in a forbidden tree or the engine's own trees (`mesh-host.launcher` and `mesh-host.next` are the engine's own, allowed). The journals of novox, shanks and g14 since 2026-10-10 18:00 show no `is not placed` refusal, so no module there becomes gated by this change. ace's tools did not answer at the time, so ace's journal was not read.
Both fail on main: the shape seen on ace, a refused directory, a file below it and a
step after it, writes the file, runs the step and reports that everything was attempted.
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)
On ace the engine refused Docker's data root as not placed, said nothing was touched, then
wrote a file into it and ran the module's step. A refused directory now gates the rest of
its module as a failed step does, a file is refused in a forbidden tree or below a refused
path, and the failure names the modules whose rest was not attempted.
Deliverynovox/mesh-host@4695dfc0a27b — delivered since 2026-10-11T17:06:02Z
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
Machines
mesh-host on ace: passed — healthy 3 times over 2m32s
mesh-host on the rest running it: sent
Transitions
2026-10-11 16:51 (new) → proposed (announced): novox/mesh-host#83's head announced
2026-10-11 16:54 proposed → checked (checked): the verdict names this commit
2026-10-11 16:54 checked → ready (accepted): the gate passed or warned, and the repository's own check did not fail
2026-10-11 17:02 ready → published (merged): on the trunk its modules follow: merged there, and its walk opened — or nothing for a walk to move
2026-10-11 17:02 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-11 17:06 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@4695dfc0a27b` — **delivered** since 2026-10-11T17:06:02Z
**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
**Machines**
- mesh-host on ace: passed — healthy 3 times over 2m32s
- mesh-host on the rest running it: sent
**Transitions**
- 2026-10-11 16:51 (new) → proposed (announced): novox/mesh-host#83's head announced
- 2026-10-11 16:54 proposed → checked (checked): the verdict names this commit
- 2026-10-11 16:54 checked → ready (accepted): the gate passed or warned, and the repository's own check did not fail
- 2026-10-11 17:02 ready → published (merged): on the trunk its modules follow: merged there, and its walk opened — or nothing for a walk to move
- 2026-10-11 17:02 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-11 17:06 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
read by no module's build: internal/apply/refused_directory_test.go
Run by the build seat on ace as build-1791735586340642099 (builds --log build-1791735586340642099).
--- 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-11T16:12:35Z 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-11T16:12:35Z
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:
- internal/apply/refused_directory_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.014s
ok github.com/novox/mesh-host/cmd/mesh-host 5.513s
ok github.com/novox/mesh-host/examples 1.021s
ok github.com/novox/mesh-host/internal/accounts 1.483s
ok github.com/novox/mesh-host/internal/apply 4.674s
ok github.com/novox/mesh-host/internal/bootstrap 1.515s
ok github.com/novox/mesh-host/internal/bundle 1.018s
ok github.com/novox/mesh-host/internal/declaration 1.058s
ok github.com/novox/mesh-host/internal/firewall 1.667s
ok github.com/novox/mesh-host/internal/identity 1.084s
ok github.com/novox/mesh-host/internal/image 1.017s
ok github.com/novox/mesh-host/internal/inventory 1.018s
ok github.com/novox/mesh-host/internal/link 10.493s
ok github.com/novox/mesh-host/internal/liveness 2.131s
ok github.com/novox/mesh-host/internal/meshcli 1.592s
ok github.com/novox/mesh-host/internal/network 1.072s
ok github.com/novox/mesh-host/internal/outward 1.065s
ok github.com/novox/mesh-host/internal/profile 1.534s
ok github.com/novox/mesh-host/internal/reachable 1.064s
ok github.com/novox/mesh-host/internal/store 1.235s
ok github.com/novox/mesh-host/internal/system 1.064s
ok github.com/novox/mesh-host/internal/tunnel 1.066s
ok github.com/novox/mesh-host/internal/units 1.061s
ok github.com/novox/mesh-host/internal/upgrade 1.184s
ok github.com/novox/mesh-host/internal/witness 4.645s
ok github.com/novox/mesh-host/packaging 1.062s
? github.com/novox/mesh-host/rootsearch [no test files]
ok github.com/novox/mesh-host/validate 1.016s
**Merge check** at `7233ddbe`
- `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
- read by no module's build: internal/apply/refused_directory_test.go
Run by the build seat on ace as `build-1791735586340642099` (`builds --log build-1791735586340642099`).
```
--- 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-11T16:12:35Z 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-11T16:12:35Z
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:
- internal/apply/refused_directory_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.014s
ok github.com/novox/mesh-host/cmd/mesh-host 5.513s
ok github.com/novox/mesh-host/examples 1.021s
ok github.com/novox/mesh-host/internal/accounts 1.483s
ok github.com/novox/mesh-host/internal/apply 4.674s
ok github.com/novox/mesh-host/internal/bootstrap 1.515s
ok github.com/novox/mesh-host/internal/bundle 1.018s
ok github.com/novox/mesh-host/internal/declaration 1.058s
ok github.com/novox/mesh-host/internal/firewall 1.667s
ok github.com/novox/mesh-host/internal/identity 1.084s
ok github.com/novox/mesh-host/internal/image 1.017s
ok github.com/novox/mesh-host/internal/inventory 1.018s
ok github.com/novox/mesh-host/internal/link 10.493s
ok github.com/novox/mesh-host/internal/liveness 2.131s
ok github.com/novox/mesh-host/internal/meshcli 1.592s
ok github.com/novox/mesh-host/internal/network 1.072s
ok github.com/novox/mesh-host/internal/outward 1.065s
ok github.com/novox/mesh-host/internal/profile 1.534s
ok github.com/novox/mesh-host/internal/reachable 1.064s
ok github.com/novox/mesh-host/internal/store 1.235s
ok github.com/novox/mesh-host/internal/system 1.064s
ok github.com/novox/mesh-host/internal/tunnel 1.066s
ok github.com/novox/mesh-host/internal/units 1.061s
ok github.com/novox/mesh-host/internal/upgrade 1.184s
ok github.com/novox/mesh-host/internal/witness 4.645s
ok github.com/novox/mesh-host/packaging 1.062s
? github.com/novox/mesh-host/rootsearch [no test files]
ok github.com/novox/mesh-host/validate 1.016s
```
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 module-less action that stopped the apply after a module was gated was reported as
everything else attempted. The failure now names the gated modules and the stop, counts
skipped resources apart from applied ones, and the tests cover an archive below a refused
path, a gated module tried again by the next apply, and a refused file among the failures.
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
read by no module's build: internal/apply/refused_directory_test.go
Run by the build seat on novox as build-1791737484518583770 (builds --log build-1791737484518583770).
--- 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-11T16:22:35Z 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-11T16:22:35Z
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:
- internal/apply/refused_directory_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.011s
ok github.com/novox/mesh-host/cmd/mesh-host 11.224s
ok github.com/novox/mesh-host/examples 1.015s
ok github.com/novox/mesh-host/internal/accounts 7.319s
ok github.com/novox/mesh-host/internal/apply 28.083s
ok github.com/novox/mesh-host/internal/bootstrap 5.339s
ok github.com/novox/mesh-host/internal/bundle 1.024s
ok github.com/novox/mesh-host/internal/declaration 1.062s
ok github.com/novox/mesh-host/internal/firewall 2.589s
ok github.com/novox/mesh-host/internal/identity 2.958s
ok github.com/novox/mesh-host/internal/image 1.021s
ok github.com/novox/mesh-host/internal/inventory 1.122s
ok github.com/novox/mesh-host/internal/link 10.939s
ok github.com/novox/mesh-host/internal/liveness 4.494s
ok github.com/novox/mesh-host/internal/meshcli 1.617s
ok github.com/novox/mesh-host/internal/network 1.081s
ok github.com/novox/mesh-host/internal/outward 1.015s
ok github.com/novox/mesh-host/internal/profile 1.487s
ok github.com/novox/mesh-host/internal/reachable 1.080s
ok github.com/novox/mesh-host/internal/store 2.941s
ok github.com/novox/mesh-host/internal/system 1.012s
ok github.com/novox/mesh-host/internal/tunnel 1.016s
ok github.com/novox/mesh-host/internal/units 1.008s
ok github.com/novox/mesh-host/internal/upgrade 2.092s
ok github.com/novox/mesh-host/internal/witness 29.993s
ok github.com/novox/mesh-host/packaging 1.030s
? github.com/novox/mesh-host/rootsearch [no test files]
ok github.com/novox/mesh-host/validate 1.008s
**Merge check** at `4695dfc0`
- `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
- read by no module's build: internal/apply/refused_directory_test.go
Run by the build seat on novox as `build-1791737484518583770` (`builds --log build-1791737484518583770`).
```
--- 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-11T16:22:35Z 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-11T16:22:35Z
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:
- internal/apply/refused_directory_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.011s
ok github.com/novox/mesh-host/cmd/mesh-host 11.224s
ok github.com/novox/mesh-host/examples 1.015s
ok github.com/novox/mesh-host/internal/accounts 7.319s
ok github.com/novox/mesh-host/internal/apply 28.083s
ok github.com/novox/mesh-host/internal/bootstrap 5.339s
ok github.com/novox/mesh-host/internal/bundle 1.024s
ok github.com/novox/mesh-host/internal/declaration 1.062s
ok github.com/novox/mesh-host/internal/firewall 2.589s
ok github.com/novox/mesh-host/internal/identity 2.958s
ok github.com/novox/mesh-host/internal/image 1.021s
ok github.com/novox/mesh-host/internal/inventory 1.122s
ok github.com/novox/mesh-host/internal/link 10.939s
ok github.com/novox/mesh-host/internal/liveness 4.494s
ok github.com/novox/mesh-host/internal/meshcli 1.617s
ok github.com/novox/mesh-host/internal/network 1.081s
ok github.com/novox/mesh-host/internal/outward 1.015s
ok github.com/novox/mesh-host/internal/profile 1.487s
ok github.com/novox/mesh-host/internal/reachable 1.080s
ok github.com/novox/mesh-host/internal/store 2.941s
ok github.com/novox/mesh-host/internal/system 1.012s
ok github.com/novox/mesh-host/internal/tunnel 1.016s
ok github.com/novox/mesh-host/internal/units 1.008s
ok github.com/novox/mesh-host/internal/upgrade 2.092s
ok github.com/novox/mesh-host/internal/witness 29.993s
ok github.com/novox/mesh-host/packaging 1.030s
? github.com/novox/mesh-host/rootsearch [no test files]
ok github.com/novox/mesh-host/validate 1.008s
```
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 novox/hq issue 495 (the node-engine refused a directory as not placed, said nothing was touched, then wrote a file into it).
On ace on 2026-10-11 at 12:42:08 the engine refused
docker.state(/var/lib/docker), then createddocker.log-rotation(/var/lib/docker/log-rotation.conf) and ran the module's step.What changes
internal/apply/apply.go), as a run-once step that did not complete already does (ADR 0136'sgated). Only the placement guard's refusals gate; a directory that failed to be made for another reason stays an ordinary failure. Each skipped resource saysits directory <path> was refused (novox/hq issue 495), so nothing more of this module was attempted, and the journal saysgated <module>.*: its directory <path> was refused.refusedPlacesininternal/apply/placement_guard.go, rule 6 in its header): it is refused in a forbidden tree (rule 2, the runtimes' data roots included) or in the engine's own trees (except the engine's own module), and below any refused directory or access, whatever its module and declared order. An archive is refused below a refused path. Rules 3 and 4 (a directory's owner below /etc or a home) do not apply to files.Error.Modulesnames the gated modules, and the message readsthe rest of <module> was not attempted and is listed as skipped; everything else was attempted, so what is not listed as failed or skipped was done.It no longer sayseverything was attempted. This also corrects the step gate's message, which saidthis is an actionfor a module's step.Tests (written first, both failed on main, commit
1acfed4)TestARefusedDirectoryGatesItsModule: the shape from ace (a directory at the runtime's data root, a file below it, a run-once step after it, another module's file). On main the file was written, the step ran, and the report said everything was attempted. Now nothing is written below the directory, the step does not run, both are reported as skipped naming the directory, the other module's file is applied, and the message names the module.TestAFileIsJudgedByTheSameGuardAsADirectory: a file in the runtime's data root is refused; a file declared before a refused directory below a home is refused and not written.sh merge-check.shpasses locally (gofmt, vet, every test under the race detector).Live impact checked
I read the controller's current plan for ace, g14, novox and shanks: no file, archive or directory of any module but
mesh-hostis in a forbidden tree or the engine's own trees (mesh-host.launcherandmesh-host.nextare the engine's own, allowed). The journals of novox, shanks and g14 since 2026-10-10 18:00 show nois not placedrefusal, so no module there becomes gated by this change. ace's tools did not answer at the time, so ace's journal was not read.Delivery
novox/mesh-host@4695dfc0a27b— delivered since 2026-10-11T17:06:02ZDelivery plan — builds mesh-host → ace, g14, novox, shanks; no bus step
Machines
Transitions
The commit's note under
refs/notes/mesh-plankeeps every transition:git log --notes=mesh-plan.Merge check at
7233ddbemesh/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-1791735586340642099(builds --log build-1791735586340642099).Merge check at
4695dfc0mesh/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 novox as
build-1791737484518583770(builds --log build-1791737484518583770).