Fixes novox/hq issue 496 (the merge gate does not judge the paths the controller resolves for a module's directories, so a directory inside Docker's data passes).
What happened
mesh-catalog #205 gave docker's state directory "place": ".". dirsFor resolved it to /var/lib/docker. The controller's systemPath judged only the places and accesses settings, so the merge gate passed it; only the node-engine refused it, at apply, and failed the walk.
Where it is judged (changed after review)
resolvedPathProblems runs in ParseManifest, beside unknownDirRefs. Every route a definition takes into the mesh runs ParseManifest: module check, registration of a build (the builder's and the registry verbs'), and the merge gate's reading of the changed repository (shelfWithChange). A refusal there stops one definition before any machine sees it.
Live composition judges nothing of this. It reads registered manifests without ParseManifest, and the first version of this PR refused in dirInto, which failed the whole machine's declaration: a module registered from outside the catalogue (which never passes the gate) would have frozen every module on its machine. The node-engine fails only the one resource, so composition leaves it to the engine. A test (TestComposingAMachineIsNeverStoppedByOneModulesPath) holds that.
This is the narrowest place that still refuses #205's shape at the gate. The trade-off: a path is resolved with the default data root (/var/lib) and an access's default path from the definition. A node's own data root or a places/accesses setting is judged by Places/AccessPlaces (issue 339) and by the engine, not here. A path still holding a placeholder only a machine fills (${setting:…}, an access with no default) is the engine's to judge.
The rules: the node-engine's, no more
A directory or file is refused when its path is one of protectedRoots or holds one, is at or below a tree in forbiddenBelow, or is at or below one of engineTrees and its module is not mesh-host. These are mesh-host's own lists from internal/apply/placement_guard.go, with files judged as directories are, as mesh-host #83 (issue 495, rule 6) makes the engine do. The rules that need the machine stay the engine's: where the runtimes really keep their data, links, the accounts' homes, and a directory's owner below /etc.
Compared with the first version, the controller no longer refuses anything below /bin, /sbin, /lib, /lib32 or /lib64; exactly /storage, /data, /services or /var/lock; or /var/lib/mesh-host for the mesh-host module.
systemPath stays the stricter rule for a setting, unchanged.
Keeping the two lists in step
TestTheResolvedPathRulesAreTheNodeEnginesOwn reads mesh-host's placement_guard.go through internal/beside and parses it with go/parser. It fails when protectedRoots, forbiddenBelow, engineTrees or engineModule differ. In a merge check it reads the mesh-host clone beside the check; elsewhere it reads the copy captured at bd5cc69 in testdata/beside/mesh-host/internal/apply/placement_guard.go.captured. CAPTURED gains a paragraph at its end saying how that copy is taken. That file is also in #227; the addition is at the end and merges cleanly with #227 (checked with git merge-tree). The test also passes against mesh-host #83's head 4695dfc (MESH_CHECK_BESIDE), whose lists are unchanged. A shared mesh-sdk package for the lists is possible, but I do not think it is worth it while the engine's rules are mostly machine-dependent; the test catches drift.
Proof
Tests first (internal/catalogue/resolved_path_test.go), run against main's code, fail there: the #205 shape is accepted; seven refused shapes are accepted; a file reaching Docker's data through an access's default path is accepted.
With the change: the #205 shape is refused, naming docker, "state", /var/lib/docker and issue 496. place: "mesh" is accepted (/var/lib/mesh/docker). /etc, /var/run, /usr/local/bin, the engine's own trees for mesh-host, an account's .ssh, a module's own root, a file below /lib, and /storage, /data, /services and /var/lock are accepted.
${access:…}: a file at ${access:images}/marker with the access's default at /var/lib/docker/volumes is refused; an access with no default path is left to its setting's judgement and the engine (TestAPathThroughAnAccessIsJudgedWithTheAccessFilledIn).
Today's mesh: all 1179 directory and file paths in the live plans of novox, ace, shanks and g14 (mesh-controller.plan, 2026-10-11) pass the new rule. All 138 manifests of mesh-catalog (fccad8c) and mesh-media-catalog (54527e8) parse. Nothing is newly refused.
go vet ./..., go test for internal/catalogue, internal/inventory, internal/builder and cmd/mesh-controller pass; main merged in (#229). No database used.
Touches no file of #223. Of #227's files it touches only testdata/beside/CAPTURED, at its end, and the two merge cleanly.
Fixes novox/hq issue 496 (the merge gate does not judge the paths the controller resolves for a module's directories, so a directory inside Docker's data passes).
## What happened
mesh-catalog #205 gave docker's `state` directory `"place": "."`. `dirsFor` resolved it to `/var/lib/docker`. The controller's `systemPath` judged only the `places` and `accesses` settings, so the merge gate passed it; only the node-engine refused it, at apply, and failed the walk.
## Where it is judged (changed after review)
`resolvedPathProblems` runs in `ParseManifest`, beside `unknownDirRefs`. Every route a definition takes into the mesh runs `ParseManifest`: `module check`, registration of a build (the builder's and the registry verbs'), and the merge gate's reading of the changed repository (`shelfWithChange`). A refusal there stops one definition before any machine sees it.
Live composition judges nothing of this. It reads registered manifests without `ParseManifest`, and the first version of this PR refused in `dirInto`, which failed the whole machine's declaration: a module registered from outside the catalogue (which never passes the gate) would have frozen every module on its machine. The node-engine fails only the one resource, so composition leaves it to the engine. A test (`TestComposingAMachineIsNeverStoppedByOneModulesPath`) holds that.
This is the narrowest place that still refuses #205's shape at the gate. The trade-off: a path is resolved with the default data root (/var/lib) and an access's default path from the definition. A node's own data root or a `places`/`accesses` setting is judged by `Places`/`AccessPlaces` (issue 339) and by the engine, not here. A path still holding a placeholder only a machine fills (`${setting:…}`, an access with no default) is the engine's to judge.
## The rules: the node-engine's, no more
A directory or file is refused when its path is one of `protectedRoots` or holds one, is at or below a tree in `forbiddenBelow`, or is at or below one of `engineTrees` and its module is not `mesh-host`. These are mesh-host's own lists from internal/apply/placement_guard.go, with files judged as directories are, as mesh-host #83 (issue 495, rule 6) makes the engine do. The rules that need the machine stay the engine's: where the runtimes really keep their data, links, the accounts' homes, and a directory's owner below /etc.
Compared with the first version, the controller no longer refuses anything below /bin, /sbin, /lib, /lib32 or /lib64; exactly /storage, /data, /services or /var/lock; or /var/lib/mesh-host for the mesh-host module.
`systemPath` stays the stricter rule for a setting, unchanged.
## Keeping the two lists in step
`TestTheResolvedPathRulesAreTheNodeEnginesOwn` reads mesh-host's placement_guard.go through `internal/beside` and parses it with go/parser. It fails when `protectedRoots`, `forbiddenBelow`, `engineTrees` or `engineModule` differ. In a merge check it reads the mesh-host clone beside the check; elsewhere it reads the copy captured at bd5cc69 in testdata/beside/mesh-host/internal/apply/placement_guard.go.captured. CAPTURED gains a paragraph at its end saying how that copy is taken. That file is also in #227; the addition is at the end and merges cleanly with #227 (checked with `git merge-tree`). The test also passes against mesh-host #83's head 4695dfc (`MESH_CHECK_BESIDE`), whose lists are unchanged. A shared mesh-sdk package for the lists is possible, but I do not think it is worth it while the engine's rules are mostly machine-dependent; the test catches drift.
## Proof
- Tests first (`internal/catalogue/resolved_path_test.go`), run against main's code, fail there: the #205 shape is accepted; seven refused shapes are accepted; a file reaching Docker's data through an access's default path is accepted.
- With the change: the #205 shape is refused, naming docker, "state", /var/lib/docker and issue 496. `place: "mesh"` is accepted (/var/lib/mesh/docker). /etc, /var/run, /usr/local/bin, the engine's own trees for mesh-host, an account's .ssh, a module's own root, a file below /lib, and /storage, /data, /services and /var/lock are accepted.
- `${access:…}`: a file at `${access:images}/marker` with the access's default at /var/lib/docker/volumes is refused; an access with no default path is left to its setting's judgement and the engine (`TestAPathThroughAnAccessIsJudgedWithTheAccessFilledIn`).
- Today's mesh: all 1179 directory and file paths in the live plans of novox, ace, shanks and g14 (`mesh-controller.plan`, 2026-10-11) pass the new rule. All 138 manifests of mesh-catalog (fccad8c) and mesh-media-catalog (54527e8) parse. Nothing is newly refused.
- `go vet ./...`, `go test` for internal/catalogue, internal/inventory, internal/builder and cmd/mesh-controller pass; main merged in (#229). No database used.
Touches no file of #223. Of #227's files it touches only testdata/beside/CAPTURED, at its end, and the two merge cleanly.
mesh/merge-gate pass: builds build-agent, mesh-controller → ace, g14, novox, shanks; no bus step; every machine composes with the change as it did without …
Deliverynovox/mesh-controller@8115f1ac42bf — delivered since 2026-10-11T18:05:08Z
Delivery plan — builds build-agent, mesh-controller → ace, g14, novox, shanks; no bus step
tier 0: mesh-controller
tier 1: build-agent
ace: receives build-agent
g14: receives build-agent
novox: receives mesh-controller, build-agent
shanks: receives build-agent
build-agent keeps data (ADR 0233): what it holds is backed up before it moves
Machines
mesh-controller on novox: passed — healthy 3 times over 3m37s
mesh-controller on the rest running it: sent
build-agent on ace: passed — healthy 3 times over 7m42s
build-agent on the rest running it: sent
Transitions
2026-10-11 16:59 (new) → proposed (announced): novox/mesh-controller#228's head announced
2026-10-11 17:06 proposed → checked (checked): the verdict names this commit
2026-10-11 17:06 checked → rejected (refused): the gate failed or could not run, or the repository's own check failed
2026-10-11 17:37 rejected → proposed (recheck): Its repo-check failed only in internal/link's TestNatsABuildIsTakenAndItsOutcomeReachesEverybody (a log stream read once after 0.12 s held one message, wanted two), a package #228 does not touch; the same test passed in #227, #229 and #223 today. Opened as its own issue; checked again.
2026-10-11 17:44 proposed → checked (checked): the verdict names this commit
2026-10-11 17:44 checked → ready (accepted): the gate passed or warned, and the repository's own check did not fail
2026-10-11 17:51 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:51 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 18:05 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-controller@8115f1ac42bf` — **delivered** since 2026-10-11T18:05:08Z
**Delivery plan** — builds build-agent, mesh-controller → ace, g14, novox, shanks; no bus step
- tier 0: mesh-controller
- tier 1: build-agent
- ace: receives build-agent
- g14: receives build-agent
- novox: receives mesh-controller, build-agent
- shanks: receives build-agent
- build-agent keeps data (ADR 0233): what it holds is backed up before it moves
**Machines**
- mesh-controller on novox: passed — healthy 3 times over 3m37s
- mesh-controller on the rest running it: sent
- build-agent on ace: passed — healthy 3 times over 7m42s
- build-agent on the rest running it: sent
**Transitions**
- 2026-10-11 16:59 (new) → proposed (announced): novox/mesh-controller#228's head announced
- 2026-10-11 17:06 proposed → checked (checked): the verdict names this commit
- 2026-10-11 17:06 checked → rejected (refused): the gate failed or could not run, or the repository's own check failed
- 2026-10-11 17:37 rejected → proposed (recheck): Its repo-check failed only in internal/link's TestNatsABuildIsTakenAndItsOutcomeReachesEverybody (a log stream read once after 0.12 s held one message, wanted two), a package #228 does not touch; the same test passed in #227, #229 and #223 today. Opened as its own issue; checked again.
- 2026-10-11 17:44 proposed → checked (checked): the verdict names this commit
- 2026-10-11 17:44 checked → ready (accepted): the gate passed or warned, and the repository's own check did not fail
- 2026-10-11 17:51 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:51 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 18:05 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: build-agent, mesh-controller)
mesh/repo-check: FAIL — its merge-check.sh failed: --- FAIL: TestTheResolverAndWhatAsksItComposeOnOneMachine (0.02s)
Delivery plan — builds build-agent, mesh-controller → ace, g14, novox, shanks; no bus step
tier 0: mesh-controller
tier 1: build-agent
ace: receives build-agent
g14: receives build-agent
novox: receives mesh-controller, build-agent
shanks: receives build-agent
build-agent keeps data (ADR 0233): what it holds is backed up before it moves
read by no module's build: internal/catalogue/resolved_path_test.go
Run by the build seat on g14 as build-1791735585724490754 (builds --log build-1791735585724490754).
--- the gate: build-agent, mesh-controller
mesh-controller: ok, 56 tool(s); WARNING: merge-window ask(s) for a setting and do(es) not say whether it is trusted, so it counts as trusted: set at the terminal alone; say "trusted" false where nothing trusts it (novox/hq issue 339); WARNING: controller stay(s) up and say(s) not how it is ready — judged by liveness alone, refused from 2026-11-18 (ADR 0240 rule 8)
long-running resources without health: 1
files asking for a setting without saying whether it is trusted: 1
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 1 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
modules the change moves:
- mesh-controller (changed)
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 2 module(s) in 2 tier(s): build-agent, mesh-controller
notes:
- internal/catalogue/resolved_path_test.go read by no module's build, and rebuild nothing (issue 280)
--- its merge-check.sh (go toolchain)
ok github.com/novox/mesh-controller/cmd/mesh-builder 1.028s
ok github.com/novox/mesh-controller/cmd/mesh-controller 225.123s
ok github.com/novox/mesh-controller/examples/objectstore-provisioner 1.009s
ok github.com/novox/mesh-controller/examples/postgres-provisioner 1.023s
ok github.com/novox/mesh-controller/examples/redis-provisioner 1.009s
ok github.com/novox/mesh-controller/examples/route-proxy 1.154s
ok github.com/novox/mesh-controller/internal/artifacts 1.046s
? github.com/novox/mesh-controller/internal/beside [no test files]
ok github.com/novox/mesh-controller/internal/broker 2.873s
ok github.com/novox/mesh-controller/internal/builder 13.986s
--- FAIL: TestTheResolverAndWhatAsksItComposeOnOneMachine (0.02s)
resolver_manifests_test.go:124: judged against /var/lib/build-agent/workspace/check/mesh-catalog as cloned beside this check
resolver_manifests_test.go:124: judged against /var/lib/build-agent/workspace/check/mesh-catalog as cloned beside this check
resolver_manifests_test.go:124: judged against /var/lib/build-agent/workspace/check/mesh-catalog as cloned beside this check
resolver_manifests_test.go:198: the runtime is given map[live-restore:true log-driver:json-file log-opts:map[max-file:10 max-size:100m]]; live-restore and nothing else
FAIL
FAIL github.com/novox/mesh-controller/internal/catalogue 5.281s
ok github.com/novox/mesh-controller/internal/conditions 2.345s
ok github.com/novox/mesh-controller/internal/envfile 1.026s
ok github.com/novox/mesh-controller/internal/facts 1.029s
ok github.com/novox/mesh-controller/internal/identity 4.147s
ok github.com/novox/mesh-controller/internal/inventory 76.172s
ok github.com/novox/mesh-controller/internal/lease 17.679s
ok github.com/novox/mesh-controller/internal/licences 3.713s
ok github.com/novox/mesh-controller/internal/licences/adapters 1.009s
ok github.com/novox/mesh-controller/internal/link 58.189s
ok github.com/novox/mesh-controller/internal/lint 2.049s
ok github.com/novox/mesh-controller/internal/outward 1.030s
ok github.com/novox/mesh-controller/internal/overlay 1.018s
ok github.com/novox/mesh-controller/internal/secrets 1.411s
ok github.com/novox/mesh-controller/internal/store 3.186s
ok github.com/novox/mesh-controller/internal/testbus 1.165s
ok github.com/novox/mesh-controller/internal/token 1.015s
FAIL
--- what failed, picked from the whole of its output (the whole is in the build's log)
--- FAIL: TestTheResolverAndWhatAsksItComposeOnOneMachine (0.02s)
resolver_manifests_test.go:124: judged against /var/lib/build-agent/workspace/check/mesh-catalog as cloned beside this check
resolver_manifests_test.go:124: judged against /var/lib/build-agent/workspace/check/mesh-catalog as cloned beside this check
resolver_manifests_test.go:124: judged against /var/lib/build-agent/workspace/check/mesh-catalog as cloned beside this check
resolver_manifests_test.go:198: the runtime is given map[live-restore:true log-driver:json-file log-opts:map[max-file:10 max-size:100m]]; live-restore and nothing else
FAIL github.com/novox/mesh-controller/internal/catalogue 5.281s
**Merge check** at `174c8b5d`
- `mesh/merge-gate`: **PASS** — every machine composes with the change as it did without (4 of 4 compose) (modules: build-agent, mesh-controller)
- `mesh/repo-check`: **FAIL** — its merge-check.sh failed: --- FAIL: TestTheResolverAndWhatAsksItComposeOnOneMachine (0.02s)
**Delivery plan** — builds build-agent, mesh-controller → ace, g14, novox, shanks; no bus step
- tier 0: mesh-controller
- tier 1: build-agent
- ace: receives build-agent
- g14: receives build-agent
- novox: receives mesh-controller, build-agent
- shanks: receives build-agent
- build-agent keeps data (ADR 0233): what it holds is backed up before it moves
- read by no module's build: internal/catalogue/resolved_path_test.go
Run by the build seat on g14 as `build-1791735585724490754` (`builds --log build-1791735585724490754`).
```
--- the gate: build-agent, mesh-controller
mesh-controller: ok, 56 tool(s); WARNING: merge-window ask(s) for a setting and do(es) not say whether it is trusted, so it counts as trusted: set at the terminal alone; say "trusted" false where nothing trusts it (novox/hq issue 339); WARNING: controller stay(s) up and say(s) not how it is ready — judged by liveness alone, refused from 2026-11-18 (ADR 0240 rule 8)
long-running resources without health: 1
files asking for a setting without saying whether it is trusted: 1
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 1 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
modules the change moves:
- mesh-controller (changed)
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 2 module(s) in 2 tier(s): build-agent, mesh-controller
notes:
- internal/catalogue/resolved_path_test.go read by no module's build, and rebuild nothing (issue 280)
--- its merge-check.sh (go toolchain)
ok github.com/novox/mesh-controller/cmd/mesh-builder 1.028s
ok github.com/novox/mesh-controller/cmd/mesh-controller 225.123s
ok github.com/novox/mesh-controller/examples/objectstore-provisioner 1.009s
ok github.com/novox/mesh-controller/examples/postgres-provisioner 1.023s
ok github.com/novox/mesh-controller/examples/redis-provisioner 1.009s
ok github.com/novox/mesh-controller/examples/route-proxy 1.154s
ok github.com/novox/mesh-controller/internal/artifacts 1.046s
? github.com/novox/mesh-controller/internal/beside [no test files]
ok github.com/novox/mesh-controller/internal/broker 2.873s
ok github.com/novox/mesh-controller/internal/builder 13.986s
--- FAIL: TestTheResolverAndWhatAsksItComposeOnOneMachine (0.02s)
resolver_manifests_test.go:124: judged against /var/lib/build-agent/workspace/check/mesh-catalog as cloned beside this check
resolver_manifests_test.go:124: judged against /var/lib/build-agent/workspace/check/mesh-catalog as cloned beside this check
resolver_manifests_test.go:124: judged against /var/lib/build-agent/workspace/check/mesh-catalog as cloned beside this check
resolver_manifests_test.go:198: the runtime is given map[live-restore:true log-driver:json-file log-opts:map[max-file:10 max-size:100m]]; live-restore and nothing else
FAIL
FAIL github.com/novox/mesh-controller/internal/catalogue 5.281s
ok github.com/novox/mesh-controller/internal/conditions 2.345s
ok github.com/novox/mesh-controller/internal/envfile 1.026s
ok github.com/novox/mesh-controller/internal/facts 1.029s
ok github.com/novox/mesh-controller/internal/identity 4.147s
ok github.com/novox/mesh-controller/internal/inventory 76.172s
ok github.com/novox/mesh-controller/internal/lease 17.679s
ok github.com/novox/mesh-controller/internal/licences 3.713s
ok github.com/novox/mesh-controller/internal/licences/adapters 1.009s
ok github.com/novox/mesh-controller/internal/link 58.189s
ok github.com/novox/mesh-controller/internal/lint 2.049s
ok github.com/novox/mesh-controller/internal/outward 1.030s
ok github.com/novox/mesh-controller/internal/overlay 1.018s
ok github.com/novox/mesh-controller/internal/secrets 1.411s
ok github.com/novox/mesh-controller/internal/store 3.186s
ok github.com/novox/mesh-controller/internal/testbus 1.165s
ok github.com/novox/mesh-controller/internal/token 1.015s
FAIL
--- what failed, picked from the whole of its output (the whole is in the build's log)
--- FAIL: TestTheResolverAndWhatAsksItComposeOnOneMachine (0.02s)
resolver_manifests_test.go:124: judged against /var/lib/build-agent/workspace/check/mesh-catalog as cloned beside this check
resolver_manifests_test.go:124: judged against /var/lib/build-agent/workspace/check/mesh-catalog as cloned beside this check
resolver_manifests_test.go:124: judged against /var/lib/build-agent/workspace/check/mesh-catalog as cloned beside this check
resolver_manifests_test.go:198: the runtime is given map[live-restore:true log-driver:json-file log-opts:map[max-file:10 max-size:100m]]; live-restore and nothing else
FAIL github.com/novox/mesh-controller/internal/catalogue 5.281s
```
mesh/merge-gate pass: builds build-agent, mesh-controller → ace, g14, novox, shanks; no bus step; every machine composes with the change as it did without …
mesh-admin
changed title from Issue 496: every path the controller resolves for a directory or file is judged where the plan is composed to Issue 496: a definition's resolved directory and file paths are judged by the node-engine's rules where the definition is judged2026-10-11 16:59:34 +00:00
mesh/merge-gate: PASS — every machine composes with the change as it did without (4 of 4 compose) (modules: build-agent, mesh-controller)
mesh/repo-check: FAIL — its merge-check.sh failed: --- FAIL: TestNatsABuildIsTakenAndItsOutcomeReachesEverybody (0.12s)
Delivery plan — builds build-agent, mesh-controller → ace, g14, novox, shanks; no bus step
tier 0: mesh-controller
tier 1: build-agent
ace: receives build-agent
g14: receives build-agent
novox: receives mesh-controller, build-agent
shanks: receives build-agent
build-agent keeps data (ADR 0233): what it holds is backed up before it moves
read by no module's build: internal/catalogue/engine_guard_test.go, internal/catalogue/resolved_path_test.go, testdata/beside/CAPTURED, testdata/beside/mesh-host/internal/apply/placement_guard.go.captured
Run by the build seat on novox as build-1791737959759578837 (builds --log build-1791737959759578837).
--- the gate: build-agent, mesh-controller
mesh-controller: ok, 56 tool(s); WARNING: merge-window ask(s) for a setting and do(es) not say whether it is trusted, so it counts as trusted: set at the terminal alone; say "trusted" false where nothing trusts it (novox/hq issue 339); WARNING: controller stay(s) up and say(s) not how it is ready — judged by liveness alone, refused from 2026-11-18 (ADR 0240 rule 8)
long-running resources without health: 1
files asking for a setting without saying whether it is trusted: 1
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 1 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
modules the change moves:
- mesh-controller (changed)
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 2 module(s) in 2 tier(s): build-agent, mesh-controller
notes:
- internal/catalogue/engine_guard_test.go, internal/catalogue/resolved_path_test.go, testdata/beside/CAPTURED and testdata/beside/mesh-host/internal/apply/placement_guard.go.captured read by no module's build, and rebuild nothing (issue 280)
--- its merge-check.sh (go toolchain)
ok github.com/novox/mesh-controller/cmd/mesh-builder 1.049s
ok github.com/novox/mesh-controller/cmd/mesh-controller 270.502s
ok github.com/novox/mesh-controller/examples/objectstore-provisioner 1.020s
ok github.com/novox/mesh-controller/examples/postgres-provisioner 1.032s
ok github.com/novox/mesh-controller/examples/redis-provisioner 1.018s
ok github.com/novox/mesh-controller/examples/route-proxy 1.132s
ok github.com/novox/mesh-controller/internal/artifacts 1.058s
? github.com/novox/mesh-controller/internal/beside [no test files]
ok github.com/novox/mesh-controller/internal/broker 7.179s
ok github.com/novox/mesh-controller/internal/builder 27.572s
ok github.com/novox/mesh-controller/internal/catalogue 8.539s
ok github.com/novox/mesh-controller/internal/conditions 2.707s
ok github.com/novox/mesh-controller/internal/envfile 1.036s
ok github.com/novox/mesh-controller/internal/facts 1.034s
ok github.com/novox/mesh-controller/internal/identity 9.763s
ok github.com/novox/mesh-controller/internal/inventory 107.925s
ok github.com/novox/mesh-controller/internal/lease 17.721s
ok github.com/novox/mesh-controller/internal/licences 8.750s
ok github.com/novox/mesh-controller/internal/licences/adapters 1.011s
nats: permissions violation: Permissions Violation for Publish to "mesh.seat.s.tool.v.anchor" on connection [5]
could not read whether b-1 was cancelled, so it is built: nats: no responders available for request
--- FAIL: TestNatsABuildIsTakenAndItsOutcomeReachesEverybody (0.12s)
builds_nats_test.go:132: the stream holds map[mesh.seat.node-build-agent.event.log.b-1:1] under the build's subject, want 2
could not read whether b-2 was cancelled, so it is built: nats: no responders available for request
could not read whether b-3 was cancelled, so it is built: nats: no responders available for request
could not read whether b-3 was cancelled, so it is built: nats: no responders available for request
could not read whether w-1 was cancelled, so it is built: nats: no responders available for request
could not read whether w-2 was cancelled, so it is built: nats: no responders available for request
could not read whether w-3 was cancelled, so it is built: nats: no responders available for request
could not read whether build-old-seat was cancelled, so it is built: nats: no responders available for request
internal/link conformance: NOT JUDGED AGAINST THE CLONE: the seat placed no mesh-sdk beside this check in MESH_CHECK_BESIDE=/var/lib/build-agent/workspace/check (it does once mesh-controller #220 has rolled out); read the captured copy at f047d0a4a9702f5d7f3d7eadd3e62496311acc00
2026/10/11 17:02:33 the notices of messages consumers gave up on cannot be taken, so none is kept until they can: asking about consumer controller on DEAD_LETTER_NOTICES: nats: stream not found
build-cancelled was cancelled by hand as this machine took it; not built
build-waited-cancelled was cancelled by hand as this machine took it; not built
2026/10/11 17:02:46 the notices of messages consumers gave up on cannot be taken, so none is kept until they can: nats: consumer not found
2026/10/11 17:03:01 how sonarr on media hears what it consumes gave up on message 1 of EVENTS (mesh.mod.gitea.event.pull.merged) after 5 deliveries; kept as dead letter 1
2026/10/11 17:03:02 another controller holds the controller's consumer on CONTROL; standing by until it lets go
2026/10/11 17:03:03 took the controller's consumer on CONTROL: the controller that held it let go
2026/10/11 17:03:11 kept what home-server says about the machine, and refused its account of declaration d11 (epoch 57, sequence 11, report 40): the account kept is newer
2026/10/11 17:03:11 kept what home-server says about the machine, and refused its account of declaration d12 (epoch 57, sequence 12, report 40): the account kept is newer
2026/10/11 17:03:14 kept what home-server says about the machine, and not its account of declaration d1: the mesh has sent it d2 since
2026/10/11 17:03:16 anchor took over the tunnel on wg0: its overlay key is the tunnel's now
FAIL
FAIL github.com/novox/mesh-controller/internal/link 64.466s
ok github.com/novox/mesh-controller/internal/lint 2.481s
ok github.com/novox/mesh-controller/internal/outward 1.038s
ok github.com/novox/mesh-controller/internal/overlay 1.024s
ok github.com/novox/mesh-controller/internal/secrets 1.447s
ok github.com/novox/mesh-controller/internal/store 5.874s
ok github.com/novox/mesh-controller/internal/testbus 1.195s
ok github.com/novox/mesh-controller/internal/token 1.026s
FAIL
--- what failed, picked from the whole of its output (the whole is in the build's log)
--- FAIL: TestNatsABuildIsTakenAndItsOutcomeReachesEverybody (0.12s)
builds_nats_test.go:132: the stream holds map[mesh.seat.node-build-agent.event.log.b-1:1] under the build's subject, want 2
FAIL github.com/novox/mesh-controller/internal/link 64.466s
**Merge check** at `8115f1ac`
- `mesh/merge-gate`: **PASS** — every machine composes with the change as it did without (4 of 4 compose) (modules: build-agent, mesh-controller)
- `mesh/repo-check`: **FAIL** — its merge-check.sh failed: --- FAIL: TestNatsABuildIsTakenAndItsOutcomeReachesEverybody (0.12s)
**Delivery plan** — builds build-agent, mesh-controller → ace, g14, novox, shanks; no bus step
- tier 0: mesh-controller
- tier 1: build-agent
- ace: receives build-agent
- g14: receives build-agent
- novox: receives mesh-controller, build-agent
- shanks: receives build-agent
- build-agent keeps data (ADR 0233): what it holds is backed up before it moves
- read by no module's build: internal/catalogue/engine_guard_test.go, internal/catalogue/resolved_path_test.go, testdata/beside/CAPTURED, testdata/beside/mesh-host/internal/apply/placement_guard.go.captured
Run by the build seat on novox as `build-1791737959759578837` (`builds --log build-1791737959759578837`).
```
--- the gate: build-agent, mesh-controller
mesh-controller: ok, 56 tool(s); WARNING: merge-window ask(s) for a setting and do(es) not say whether it is trusted, so it counts as trusted: set at the terminal alone; say "trusted" false where nothing trusts it (novox/hq issue 339); WARNING: controller stay(s) up and say(s) not how it is ready — judged by liveness alone, refused from 2026-11-18 (ADR 0240 rule 8)
long-running resources without health: 1
files asking for a setting without saying whether it is trusted: 1
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 1 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
modules the change moves:
- mesh-controller (changed)
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 2 module(s) in 2 tier(s): build-agent, mesh-controller
notes:
- internal/catalogue/engine_guard_test.go, internal/catalogue/resolved_path_test.go, testdata/beside/CAPTURED and testdata/beside/mesh-host/internal/apply/placement_guard.go.captured read by no module's build, and rebuild nothing (issue 280)
--- its merge-check.sh (go toolchain)
ok github.com/novox/mesh-controller/cmd/mesh-builder 1.049s
ok github.com/novox/mesh-controller/cmd/mesh-controller 270.502s
ok github.com/novox/mesh-controller/examples/objectstore-provisioner 1.020s
ok github.com/novox/mesh-controller/examples/postgres-provisioner 1.032s
ok github.com/novox/mesh-controller/examples/redis-provisioner 1.018s
ok github.com/novox/mesh-controller/examples/route-proxy 1.132s
ok github.com/novox/mesh-controller/internal/artifacts 1.058s
? github.com/novox/mesh-controller/internal/beside [no test files]
ok github.com/novox/mesh-controller/internal/broker 7.179s
ok github.com/novox/mesh-controller/internal/builder 27.572s
ok github.com/novox/mesh-controller/internal/catalogue 8.539s
ok github.com/novox/mesh-controller/internal/conditions 2.707s
ok github.com/novox/mesh-controller/internal/envfile 1.036s
ok github.com/novox/mesh-controller/internal/facts 1.034s
ok github.com/novox/mesh-controller/internal/identity 9.763s
ok github.com/novox/mesh-controller/internal/inventory 107.925s
ok github.com/novox/mesh-controller/internal/lease 17.721s
ok github.com/novox/mesh-controller/internal/licences 8.750s
ok github.com/novox/mesh-controller/internal/licences/adapters 1.011s
nats: permissions violation: Permissions Violation for Publish to "mesh.seat.s.tool.v.anchor" on connection [5]
could not read whether b-1 was cancelled, so it is built: nats: no responders available for request
--- FAIL: TestNatsABuildIsTakenAndItsOutcomeReachesEverybody (0.12s)
builds_nats_test.go:132: the stream holds map[mesh.seat.node-build-agent.event.log.b-1:1] under the build's subject, want 2
could not read whether b-2 was cancelled, so it is built: nats: no responders available for request
could not read whether b-3 was cancelled, so it is built: nats: no responders available for request
could not read whether b-3 was cancelled, so it is built: nats: no responders available for request
could not read whether w-1 was cancelled, so it is built: nats: no responders available for request
could not read whether w-2 was cancelled, so it is built: nats: no responders available for request
could not read whether w-3 was cancelled, so it is built: nats: no responders available for request
could not read whether build-old-seat was cancelled, so it is built: nats: no responders available for request
internal/link conformance: NOT JUDGED AGAINST THE CLONE: the seat placed no mesh-sdk beside this check in MESH_CHECK_BESIDE=/var/lib/build-agent/workspace/check (it does once mesh-controller #220 has rolled out); read the captured copy at f047d0a4a9702f5d7f3d7eadd3e62496311acc00
2026/10/11 17:02:33 the notices of messages consumers gave up on cannot be taken, so none is kept until they can: asking about consumer controller on DEAD_LETTER_NOTICES: nats: stream not found
build-cancelled was cancelled by hand as this machine took it; not built
build-waited-cancelled was cancelled by hand as this machine took it; not built
2026/10/11 17:02:46 the notices of messages consumers gave up on cannot be taken, so none is kept until they can: nats: consumer not found
2026/10/11 17:03:01 how sonarr on media hears what it consumes gave up on message 1 of EVENTS (mesh.mod.gitea.event.pull.merged) after 5 deliveries; kept as dead letter 1
2026/10/11 17:03:02 another controller holds the controller's consumer on CONTROL; standing by until it lets go
2026/10/11 17:03:03 took the controller's consumer on CONTROL: the controller that held it let go
2026/10/11 17:03:11 kept what home-server says about the machine, and refused its account of declaration d11 (epoch 57, sequence 11, report 40): the account kept is newer
2026/10/11 17:03:11 kept what home-server says about the machine, and refused its account of declaration d12 (epoch 57, sequence 12, report 40): the account kept is newer
2026/10/11 17:03:14 kept what home-server says about the machine, and not its account of declaration d1: the mesh has sent it d2 since
2026/10/11 17:03:16 anchor took over the tunnel on wg0: its overlay key is the tunnel's now
FAIL
FAIL github.com/novox/mesh-controller/internal/link 64.466s
ok github.com/novox/mesh-controller/internal/lint 2.481s
ok github.com/novox/mesh-controller/internal/outward 1.038s
ok github.com/novox/mesh-controller/internal/overlay 1.024s
ok github.com/novox/mesh-controller/internal/secrets 1.447s
ok github.com/novox/mesh-controller/internal/store 5.874s
ok github.com/novox/mesh-controller/internal/testbus 1.195s
ok github.com/novox/mesh-controller/internal/token 1.026s
FAIL
--- what failed, picked from the whole of its output (the whole is in the build's log)
--- FAIL: TestNatsABuildIsTakenAndItsOutcomeReachesEverybody (0.12s)
builds_nats_test.go:132: the stream holds map[mesh.seat.node-build-agent.event.log.b-1:1] under the build's subject, want 2
FAIL github.com/novox/mesh-controller/internal/link 64.466s
```
mesh/merge-gate: PASS — every machine composes with the change as it did without (4 of 4 compose) (modules: build-agent, mesh-controller)
mesh/repo-check: PASS — its merge-check.sh passed
Delivery plan — builds build-agent, mesh-controller → ace, g14, novox, shanks; no bus step
tier 0: mesh-controller
tier 1: build-agent
ace: receives build-agent
g14: receives build-agent
novox: receives mesh-controller, build-agent
shanks: receives build-agent
build-agent keeps data (ADR 0233): what it holds is backed up before it moves
read by no module's build: internal/catalogue/engine_guard_test.go, internal/catalogue/resolved_path_test.go, testdata/beside/CAPTURED, testdata/beside/mesh-host/internal/apply/placement_guard.go.captured
Run by the build seat on novox as build-1791740235393498242 (builds --log build-1791740235393498242).
--- the gate: build-agent, mesh-controller
mesh-controller: ok, 56 tool(s); WARNING: merge-window ask(s) for a setting and do(es) not say whether it is trusted, so it counts as trusted: set at the terminal alone; say "trusted" false where nothing trusts it (novox/hq issue 339); WARNING: controller stay(s) up and say(s) not how it is ready — judged by liveness alone, refused from 2026-11-18 (ADR 0240 rule 8)
long-running resources without health: 1
files asking for a setting without saying whether it is trusted: 1
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 1 module(s) changed against 4 machine(s), as the snapshot of 2026-10-11T17:31:39Z 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-11T17:31:39Z
modules the change moves:
- mesh-controller (changed)
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 2 module(s) in 2 tier(s): build-agent, mesh-controller
notes:
- internal/catalogue/engine_guard_test.go, internal/catalogue/resolved_path_test.go, testdata/beside/CAPTURED and testdata/beside/mesh-host/internal/apply/placement_guard.go.captured read by no module's build, and rebuild nothing (issue 280)
--- its merge-check.sh (go toolchain)
ok github.com/novox/mesh-controller/cmd/mesh-builder 1.052s
ok github.com/novox/mesh-controller/cmd/mesh-controller 267.317s
ok github.com/novox/mesh-controller/examples/objectstore-provisioner 1.020s
ok github.com/novox/mesh-controller/examples/postgres-provisioner 1.025s
ok github.com/novox/mesh-controller/examples/redis-provisioner 1.010s
ok github.com/novox/mesh-controller/examples/route-proxy 1.121s
ok github.com/novox/mesh-controller/internal/artifacts 1.038s
? github.com/novox/mesh-controller/internal/beside [no test files]
ok github.com/novox/mesh-controller/internal/broker 4.787s
ok github.com/novox/mesh-controller/internal/builder 24.713s
ok github.com/novox/mesh-controller/internal/catalogue 9.281s
ok github.com/novox/mesh-controller/internal/conditions 2.722s
ok github.com/novox/mesh-controller/internal/envfile 1.010s
ok github.com/novox/mesh-controller/internal/facts 1.015s
ok github.com/novox/mesh-controller/internal/identity 7.847s
ok github.com/novox/mesh-controller/internal/inventory 107.514s
ok github.com/novox/mesh-controller/internal/lease 17.623s
ok github.com/novox/mesh-controller/internal/licences 6.892s
ok github.com/novox/mesh-controller/internal/licences/adapters 1.010s
ok github.com/novox/mesh-controller/internal/link 64.037s
ok github.com/novox/mesh-controller/internal/lint 2.338s
ok github.com/novox/mesh-controller/internal/outward 1.033s
ok github.com/novox/mesh-controller/internal/overlay 1.028s
ok github.com/novox/mesh-controller/internal/secrets 1.546s
ok github.com/novox/mesh-controller/internal/store 4.066s
ok github.com/novox/mesh-controller/internal/testbus 1.238s
ok github.com/novox/mesh-controller/internal/token 1.024s
**Merge check** at `8115f1ac`
- `mesh/merge-gate`: **PASS** — every machine composes with the change as it did without (4 of 4 compose) (modules: build-agent, mesh-controller)
- `mesh/repo-check`: **PASS** — its merge-check.sh passed
**Delivery plan** — builds build-agent, mesh-controller → ace, g14, novox, shanks; no bus step
- tier 0: mesh-controller
- tier 1: build-agent
- ace: receives build-agent
- g14: receives build-agent
- novox: receives mesh-controller, build-agent
- shanks: receives build-agent
- build-agent keeps data (ADR 0233): what it holds is backed up before it moves
- read by no module's build: internal/catalogue/engine_guard_test.go, internal/catalogue/resolved_path_test.go, testdata/beside/CAPTURED, testdata/beside/mesh-host/internal/apply/placement_guard.go.captured
Run by the build seat on novox as `build-1791740235393498242` (`builds --log build-1791740235393498242`).
```
--- the gate: build-agent, mesh-controller
mesh-controller: ok, 56 tool(s); WARNING: merge-window ask(s) for a setting and do(es) not say whether it is trusted, so it counts as trusted: set at the terminal alone; say "trusted" false where nothing trusts it (novox/hq issue 339); WARNING: controller stay(s) up and say(s) not how it is ready — judged by liveness alone, refused from 2026-11-18 (ADR 0240 rule 8)
long-running resources without health: 1
files asking for a setting without saying whether it is trusted: 1
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 1 module(s) changed against 4 machine(s), as the snapshot of 2026-10-11T17:31:39Z 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-11T17:31:39Z
modules the change moves:
- mesh-controller (changed)
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 2 module(s) in 2 tier(s): build-agent, mesh-controller
notes:
- internal/catalogue/engine_guard_test.go, internal/catalogue/resolved_path_test.go, testdata/beside/CAPTURED and testdata/beside/mesh-host/internal/apply/placement_guard.go.captured read by no module's build, and rebuild nothing (issue 280)
--- its merge-check.sh (go toolchain)
ok github.com/novox/mesh-controller/cmd/mesh-builder 1.052s
ok github.com/novox/mesh-controller/cmd/mesh-controller 267.317s
ok github.com/novox/mesh-controller/examples/objectstore-provisioner 1.020s
ok github.com/novox/mesh-controller/examples/postgres-provisioner 1.025s
ok github.com/novox/mesh-controller/examples/redis-provisioner 1.010s
ok github.com/novox/mesh-controller/examples/route-proxy 1.121s
ok github.com/novox/mesh-controller/internal/artifacts 1.038s
? github.com/novox/mesh-controller/internal/beside [no test files]
ok github.com/novox/mesh-controller/internal/broker 4.787s
ok github.com/novox/mesh-controller/internal/builder 24.713s
ok github.com/novox/mesh-controller/internal/catalogue 9.281s
ok github.com/novox/mesh-controller/internal/conditions 2.722s
ok github.com/novox/mesh-controller/internal/envfile 1.010s
ok github.com/novox/mesh-controller/internal/facts 1.015s
ok github.com/novox/mesh-controller/internal/identity 7.847s
ok github.com/novox/mesh-controller/internal/inventory 107.514s
ok github.com/novox/mesh-controller/internal/lease 17.623s
ok github.com/novox/mesh-controller/internal/licences 6.892s
ok github.com/novox/mesh-controller/internal/licences/adapters 1.010s
ok github.com/novox/mesh-controller/internal/link 64.037s
ok github.com/novox/mesh-controller/internal/lint 2.338s
ok github.com/novox/mesh-controller/internal/outward 1.033s
ok github.com/novox/mesh-controller/internal/overlay 1.028s
ok github.com/novox/mesh-controller/internal/secrets 1.546s
ok github.com/novox/mesh-controller/internal/store 4.066s
ok github.com/novox/mesh-controller/internal/testbus 1.238s
ok github.com/novox/mesh-controller/internal/token 1.024s
```
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 496 (the merge gate does not judge the paths the controller resolves for a module's directories, so a directory inside Docker's data passes).
What happened
mesh-catalog #205 gave docker's
statedirectory"place": ".".dirsForresolved it to/var/lib/docker. The controller'ssystemPathjudged only theplacesandaccessessettings, so the merge gate passed it; only the node-engine refused it, at apply, and failed the walk.Where it is judged (changed after review)
resolvedPathProblemsruns inParseManifest, besideunknownDirRefs. Every route a definition takes into the mesh runsParseManifest:module check, registration of a build (the builder's and the registry verbs'), and the merge gate's reading of the changed repository (shelfWithChange). A refusal there stops one definition before any machine sees it.Live composition judges nothing of this. It reads registered manifests without
ParseManifest, and the first version of this PR refused indirInto, which failed the whole machine's declaration: a module registered from outside the catalogue (which never passes the gate) would have frozen every module on its machine. The node-engine fails only the one resource, so composition leaves it to the engine. A test (TestComposingAMachineIsNeverStoppedByOneModulesPath) holds that.This is the narrowest place that still refuses #205's shape at the gate. The trade-off: a path is resolved with the default data root (/var/lib) and an access's default path from the definition. A node's own data root or a
places/accessessetting is judged byPlaces/AccessPlaces(issue 339) and by the engine, not here. A path still holding a placeholder only a machine fills (${setting:…}, an access with no default) is the engine's to judge.The rules: the node-engine's, no more
A directory or file is refused when its path is one of
protectedRootsor holds one, is at or below a tree inforbiddenBelow, or is at or below one ofengineTreesand its module is notmesh-host. These are mesh-host's own lists from internal/apply/placement_guard.go, with files judged as directories are, as mesh-host #83 (issue 495, rule 6) makes the engine do. The rules that need the machine stay the engine's: where the runtimes really keep their data, links, the accounts' homes, and a directory's owner below /etc.Compared with the first version, the controller no longer refuses anything below /bin, /sbin, /lib, /lib32 or /lib64; exactly /storage, /data, /services or /var/lock; or /var/lib/mesh-host for the mesh-host module.
systemPathstays the stricter rule for a setting, unchanged.Keeping the two lists in step
TestTheResolvedPathRulesAreTheNodeEnginesOwnreads mesh-host's placement_guard.go throughinternal/besideand parses it with go/parser. It fails whenprotectedRoots,forbiddenBelow,engineTreesorengineModulediffer. In a merge check it reads the mesh-host clone beside the check; elsewhere it reads the copy captured at bd5cc69 in testdata/beside/mesh-host/internal/apply/placement_guard.go.captured. CAPTURED gains a paragraph at its end saying how that copy is taken. That file is also in #227; the addition is at the end and merges cleanly with #227 (checked withgit merge-tree). The test also passes against mesh-host #83's head 4695dfc (MESH_CHECK_BESIDE), whose lists are unchanged. A shared mesh-sdk package for the lists is possible, but I do not think it is worth it while the engine's rules are mostly machine-dependent; the test catches drift.Proof
internal/catalogue/resolved_path_test.go), run against main's code, fail there: the #205 shape is accepted; seven refused shapes are accepted; a file reaching Docker's data through an access's default path is accepted.place: "mesh"is accepted (/var/lib/mesh/docker). /etc, /var/run, /usr/local/bin, the engine's own trees for mesh-host, an account's .ssh, a module's own root, a file below /lib, and /storage, /data, /services and /var/lock are accepted.${access:…}: a file at${access:images}/markerwith the access's default at /var/lib/docker/volumes is refused; an access with no default path is left to its setting's judgement and the engine (TestAPathThroughAnAccessIsJudgedWithTheAccessFilledIn).mesh-controller.plan, 2026-10-11) pass the new rule. All 138 manifests of mesh-catalog (fccad8c) and mesh-media-catalog (54527e8) parse. Nothing is newly refused.go vet ./...,go testfor internal/catalogue, internal/inventory, internal/builder and cmd/mesh-controller pass; main merged in (#229). No database used.Touches no file of #223. Of #227's files it touches only testdata/beside/CAPTURED, at its end, and the two merge cleanly.
Delivery
novox/mesh-controller@8115f1ac42bf— delivered since 2026-10-11T18:05:08ZDelivery plan — builds build-agent, mesh-controller → 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
174c8b5dmesh/merge-gate: PASS — every machine composes with the change as it did without (4 of 4 compose) (modules: build-agent, mesh-controller)mesh/repo-check: FAIL — its merge-check.sh failed: --- FAIL: TestTheResolverAndWhatAsksItComposeOnOneMachine (0.02s)Delivery plan — builds build-agent, mesh-controller → ace, g14, novox, shanks; no bus step
Run by the build seat on g14 as
build-1791735585724490754(builds --log build-1791735585724490754).Issue 496: every path the controller resolves for a directory or file is judged where the plan is composedto Issue 496: a definition's resolved directory and file paths are judged by the node-engine's rules where the definition is judgedMerge check at
8115f1acmesh/merge-gate: PASS — every machine composes with the change as it did without (4 of 4 compose) (modules: build-agent, mesh-controller)mesh/repo-check: FAIL — its merge-check.sh failed: --- FAIL: TestNatsABuildIsTakenAndItsOutcomeReachesEverybody (0.12s)Delivery plan — builds build-agent, mesh-controller → ace, g14, novox, shanks; no bus step
Run by the build seat on novox as
build-1791737959759578837(builds --log build-1791737959759578837).Merge check at
8115f1acmesh/merge-gate: PASS — every machine composes with the change as it did without (4 of 4 compose) (modules: build-agent, mesh-controller)mesh/repo-check: PASS — its merge-check.sh passedDelivery plan — builds build-agent, mesh-controller → ace, g14, novox, shanks; no bus step
Run by the build seat on novox as
build-1791740235393498242(builds --log build-1791740235393498242).