Why (ADR 0312, accepted with the operator's Approve; issue 537). The node-engine half is merged and delivered (mesh-host #86, 3f7f7971): an access takes grant {containers, account} and the engine joins those identities to the path's own group, never changing the path. This half composes the grant.
What changes
internal/catalogue/grants.go: for each read-write access of a module, the grant names the module's containers whose volume source is the path or below it (filepath.Clean, path or path/…; ${access:x} already resolved; a :ro mount of a read-write access is granted too — the grant follows what mounts the path, not how), and the account its tools run as: the operator's account for the machine's tool runner, or the module's own account (ADR 0259 §8). The tool runner gets the access's id in its restart-on (sorted), so it restarts once to hold the group (ADR 0312 §6). A read-write access of a module that runs nothing there is sent an empty grant, so the engine still judges its group.
Sent only to an engine stating contract 4 (link.GrantContract); Rendering.GrantsGroups from the engine's newest statement (plan.go); an older engine gets nothing new and no restart.
go.mod/vendor: the engine's validator pinned at mesh-host 3f7f797168d3; testdata/beside recaptured there.
Checked: make check green (all packages). Independent review approved the composition (no over-granting found; /storage/media2 near-miss and :ro tests added at its request).
Rollout effects (the operator was told and said deliver now): on ace, every container mounting a read-write access is recreated once (radarr, sonarr, lidarr, bazarr, bookshelf, nzbget, qbittorrent, n8n; Plex reads only); a shared folder whose group cannot write becomes an unhealthy module condition; a newly granted group shows relogin needed where the operator's own session runs; the tool runner restarts once per machine where it gains a group.
**Why** (ADR 0312, accepted with the operator's Approve; issue 537). The node-engine half is merged and delivered (mesh-host #86, 3f7f7971): an `access` takes `grant {containers, account}` and the engine joins those identities to the path's own group, never changing the path. This half composes the grant.
**What changes**
- `internal/catalogue/grants.go`: for each read-write access of a module, the grant names the module's containers whose volume source is the path or below it (`filepath.Clean`, `path` or `path/`…; `${access:x}` already resolved; a `:ro` mount of a read-write access is granted too — the grant follows what mounts the path, not how), and the account its tools run as: the operator's account for the machine's tool runner, or the module's own account (ADR 0259 §8). The tool runner gets the access's id in its `restart-on` (sorted), so it restarts once to hold the group (ADR 0312 §6). A read-write access of a module that runs nothing there is sent an empty grant, so the engine still judges its group.
- Sent only to an engine stating contract 4 (`link.GrantContract`); `Rendering.GrantsGroups` from the engine's newest statement (`plan.go`); an older engine gets nothing new and no restart.
- `go.mod`/vendor: the engine's validator pinned at mesh-host 3f7f797168d3; `testdata/beside` recaptured there.
**Checked**: `make check` green (all packages). Independent review approved the composition (no over-granting found; `/storage/media2` near-miss and `:ro` tests added at its request).
**Rollout effects** (the operator was told and said deliver now): on ace, every container mounting a read-write access is recreated once (radarr, sonarr, lidarr, bazarr, bookshelf, nzbget, qbittorrent, n8n; Plex reads only); a shared folder whose group cannot write becomes an unhealthy module condition; a newly granted group shows *relogin needed* where the operator's own session runs; the tool runner restarts once per machine where it gains a group.
Each read-write access is composed with a grant: the module's containers that
mount its path and the account its tools run as (the operator's, or the module's
own under ADR 0259 §8); that runtime restarts on the access, so it holds a group
the engine put its account in. A read access grants nothing. Sent only to an
engine whose statement says GrantContract (4), since an older one refuses the
field. Pins the node-engine at the branch that reads it.
A path beginning with the same letters is another path, and a read-only mount
of a read-write access is still granted: the grant follows what mounts it.
mesh/merge-gate pass: builds build-agent, mesh-controller, route-proxy → ace, g14, novox, shanks; no bus step; every machine composes with the change as it…
mesh/delivery covered after its failure: a later walk that contains it was delivered: plan-1791819383983869952 (novox/mesh-controller at c672b3df into ma…
Deliverynovox/mesh-controller@74bd90df7ef4 — failed since 2026-10-12T14:30:59Z
Covered: covered after its failure: a later walk that contains it was delivered: plan-1791819383983869952 (novox/mesh-controller at c672b3df into main, done, contains its merge 3cfc1216)
Delivery plan — builds build-agent, mesh-controller, route-proxy → ace, g14, novox, shanks; no bus step
build-agent keeps data (ADR 0233): what it holds is backed up before it moves
route-proxy provides route: its consumers are sent again after it
route-proxy keeps data (ADR 0233): what it holds is backed up before it moves
grants step: if this changes what the bus's user list says (a new tool, subject or user), novox is sent that list alone, every build there kept, before build-agent, route-proxy is judged on its first machine
Machines
mesh-controller on novox: passed — healthy 3 times over 4m15s
mesh-controller on the rest running it: sent
build-agent on ace: failed — ace failed what it was sent
Transitions
2026-10-12 12:03 (new) → proposed (announced): novox/mesh-controller#256's head announced
2026-10-12 12:11 proposed → checked (checked): the verdict names this commit
2026-10-12 12:11 checked → ready (accepted): the gate passed or warned, and the repository's own check did not fail
2026-10-12 14:20 ready → published (merged): on the trunk its modules follow: merged there, and its walk opened — or nothing for a walk to move
2026-10-12 14:20 published → delivering (go): its walk started: let go by this owner in its group's order, by a person, or on the controller's own path — not a failed walk that carried a later commit for it, after which it waits for a walk of its own commit
2026-10-12 14:30 delivering → failed (failed): its walk failed, carrying its own commit: 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-controller@74bd90df7ef4` — **failed** since 2026-10-12T14:30:59Z
**Covered**: covered after its failure: a later walk that contains it was delivered: plan-1791819383983869952 (novox/mesh-controller at c672b3df into main, done, contains its merge 3cfc1216)
**Delivery plan** — builds build-agent, mesh-controller, route-proxy → ace, g14, novox, shanks; no bus step
- tier 0: mesh-controller
- tier 1: build-agent
- tier 2: route-proxy
- ace: receives build-agent, route-proxy
- g14: receives build-agent
- novox: receives mesh-controller, build-agent, route-proxy
- shanks: receives build-agent
- build-agent keeps data (ADR 0233): what it holds is backed up before it moves
- route-proxy provides route: its consumers are sent again after it
- route-proxy keeps data (ADR 0233): what it holds is backed up before it moves
- grants step: if this changes what the bus's user list says (a new tool, subject or user), novox is sent that list alone, every build there kept, before build-agent, route-proxy is judged on its first machine
**Machines**
- mesh-controller on novox: passed — healthy 3 times over 4m15s
- mesh-controller on the rest running it: sent
- build-agent on ace: failed — ace failed what it was sent
**Transitions**
- 2026-10-12 12:03 (new) → proposed (announced): novox/mesh-controller#256's head announced
- 2026-10-12 12:11 proposed → checked (checked): the verdict names this commit
- 2026-10-12 12:11 checked → ready (accepted): the gate passed or warned, and the repository's own check did not fail
- 2026-10-12 14:20 ready → published (merged): on the trunk its modules follow: merged there, and its walk opened — or nothing for a walk to move
- 2026-10-12 14:20 published → delivering (go): its walk started: let go by this owner in its group's order, by a person, or on the controller's own path — not a failed walk that carried a later commit for it, after which it waits for a walk of its own commit
- 2026-10-12 14:30 delivering → failed (failed): its walk failed, carrying its own commit: 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`.
build-agent keeps data (ADR 0233): what it holds is backed up before it moves
route-proxy provides route: its consumers are sent again after it
route-proxy keeps data (ADR 0233): what it holds is backed up before it moves
grants step: if this changes what the bus's user list says (a new tool, subject or user), novox is sent that list alone, every build there kept, before build-agent, route-proxy is judged on its first machine
read by no module's build: internal/catalogue/grants_test.go, testdata/beside/CAPTURED
Run by the build seat on shanks as build-1791806598559726889 (builds --log build-1791806598559726889).
--- the gate: build-agent, mesh-controller, route-proxy
mesh-controller: ok, 57 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-12T12:01:38Z 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-12T12:01:38Z
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 3 module(s) in 3 tier(s): build-agent, mesh-controller, route-proxy
notes:
- internal/catalogue/grants_test.go and testdata/beside/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.035s
ok github.com/novox/mesh-controller/cmd/mesh-controller 270.949s
ok github.com/novox/mesh-controller/examples/objectstore-provisioner 1.011s
ok github.com/novox/mesh-controller/examples/postgres-provisioner 1.052s
ok github.com/novox/mesh-controller/examples/redis-provisioner 1.022s
ok github.com/novox/mesh-controller/examples/route-proxy 1.228s
ok github.com/novox/mesh-controller/internal/artifacts 1.092s
? github.com/novox/mesh-controller/internal/beside [no test files]
ok github.com/novox/mesh-controller/internal/broker 4.434s
ok github.com/novox/mesh-controller/internal/builder 25.798s
ok github.com/novox/mesh-controller/internal/catalogue 8.053s
ok github.com/novox/mesh-controller/internal/conditions 2.750s
ok github.com/novox/mesh-controller/internal/envfile 1.055s
ok github.com/novox/mesh-controller/internal/facts 1.063s
ok github.com/novox/mesh-controller/internal/identity 5.105s
ok github.com/novox/mesh-controller/internal/inventory 105.627s
ok github.com/novox/mesh-controller/internal/lease 17.736s
ok github.com/novox/mesh-controller/internal/licences 4.575s
ok github.com/novox/mesh-controller/internal/licences/adapters 1.063s
ok github.com/novox/mesh-controller/internal/link 67.757s
ok github.com/novox/mesh-controller/internal/lint 2.536s
ok github.com/novox/mesh-controller/internal/outward 1.097s
ok github.com/novox/mesh-controller/internal/overlay 1.080s
ok github.com/novox/mesh-controller/internal/secrets 1.531s
ok github.com/novox/mesh-controller/internal/store 3.591s
ok github.com/novox/mesh-controller/internal/testbus 1.250s
ok github.com/novox/mesh-controller/internal/token 1.016s
store tests, each run against the store:
./cmd/mesh-controller --- PASS: TestAStopWithoutAMergeWalksTheOthersAgain (0.43s)
./cmd/mesh-controller --- PASS: TestAStopWithoutAMergeEndsTheMergesThatContainIt (0.43s)
./cmd/mesh-controller --- PASS: TestAStopWalksTheOthersAgainInTheOpenBatch (0.43s)
./cmd/mesh-controller --- PASS: TestAStopNamesWhatStaysOnTheMachinesAndWhatStillCarriesIt (0.42s)
./cmd/mesh-controller --- PASS: TestAStopWithoutAMergeLeavesItOutOfABatch (0.41s)
./cmd/mesh-controller --- PASS: TestSavingPlansAndMovingMergesIsOneAct (0.38s)
./cmd/mesh-controller --- PASS: TestNodeShowAndStatusReadTheLastSendFromTheStore (0.46s)
./cmd/mesh-controller --- PASS: TestTheConditionsVerbReadsTheLooksTheBucketNoLongerHolds (0.32s)
./cmd/mesh-controller --- PASS: TestAWalkLetGoAndStoppedByVerbsIsSaidStartedAndEnded (0.48s)
./cmd/mesh-controller --- PASS: TestAWalkStoppedOrClosedByAPersonIsSaidEndedStopped (0.47s)
./cmd/mesh-controller --- PASS: TestAWalkRetriedByAPersonIsSaidStartedAgain (0.44s)
./cmd/mesh-controller --- PASS: TestABacklogReleasedByAPersonIsSaidStarted (0.43s)
./cmd/mesh-controller --- PASS: TestAWalkEndedByCancelOrClearIsSaidEnded (0.48s)
./cmd/mesh-controller --- PASS: TestAWalkRestartedByARebuildIsSaidStarted (0.42s)
./cmd/mesh-controller --- PASS: TestAWalkStoppedByHandAndRetriedEndsFailedWhenItFailsAgain (0.47s)
./internal/inventory --- PASS: TestTheLastSendSaysWhatTheMachineAnswered (0.27s)
./internal/inventory --- PASS: TestAReportIsTheLastSendsAnswerOnlyWhenItIsAboutThatSend (0.28s)
./internal/inventory --- PASS: TestAnIssuedValueIsSealedToEveryHolderOnceAndNotAgain (0.29s)
./internal/inventory --- PASS: TestAnIssuedValueIsSealedAgainAfterAKeyChangeOrAnAcceptance (0.27s)
./internal/inventory --- PASS: TestAConditionsLooksAreKeptBesideTheBucket (0.26s)
./internal/inventory --- PASS: TestAWalksStartIsKeptAndARefusedSaveLeavesItUnsaid (0.26s)
**Merge check** at `74bd90df`
- `mesh/merge-gate`: **PASS** — every machine composes with the change as it did without (4 of 4 compose) (modules: build-agent, mesh-controller, route-proxy)
- `mesh/repo-check`: **PASS** — its merge-check.sh passed
**Delivery plan** — builds build-agent, mesh-controller, route-proxy → ace, g14, novox, shanks; no bus step
- tier 0: mesh-controller
- tier 1: build-agent
- tier 2: route-proxy
- ace: receives build-agent, route-proxy
- g14: receives build-agent
- novox: receives mesh-controller, build-agent, route-proxy
- shanks: receives build-agent
- build-agent keeps data (ADR 0233): what it holds is backed up before it moves
- route-proxy provides route: its consumers are sent again after it
- route-proxy keeps data (ADR 0233): what it holds is backed up before it moves
- grants step: if this changes what the bus's user list says (a new tool, subject or user), novox is sent that list alone, every build there kept, before build-agent, route-proxy is judged on its first machine
- read by no module's build: internal/catalogue/grants_test.go, testdata/beside/CAPTURED
Run by the build seat on shanks as `build-1791806598559726889` (`builds --log build-1791806598559726889`).
```
--- the gate: build-agent, mesh-controller, route-proxy
mesh-controller: ok, 57 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-12T12:01:38Z 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-12T12:01:38Z
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 3 module(s) in 3 tier(s): build-agent, mesh-controller, route-proxy
notes:
- internal/catalogue/grants_test.go and testdata/beside/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.035s
ok github.com/novox/mesh-controller/cmd/mesh-controller 270.949s
ok github.com/novox/mesh-controller/examples/objectstore-provisioner 1.011s
ok github.com/novox/mesh-controller/examples/postgres-provisioner 1.052s
ok github.com/novox/mesh-controller/examples/redis-provisioner 1.022s
ok github.com/novox/mesh-controller/examples/route-proxy 1.228s
ok github.com/novox/mesh-controller/internal/artifacts 1.092s
? github.com/novox/mesh-controller/internal/beside [no test files]
ok github.com/novox/mesh-controller/internal/broker 4.434s
ok github.com/novox/mesh-controller/internal/builder 25.798s
ok github.com/novox/mesh-controller/internal/catalogue 8.053s
ok github.com/novox/mesh-controller/internal/conditions 2.750s
ok github.com/novox/mesh-controller/internal/envfile 1.055s
ok github.com/novox/mesh-controller/internal/facts 1.063s
ok github.com/novox/mesh-controller/internal/identity 5.105s
ok github.com/novox/mesh-controller/internal/inventory 105.627s
ok github.com/novox/mesh-controller/internal/lease 17.736s
ok github.com/novox/mesh-controller/internal/licences 4.575s
ok github.com/novox/mesh-controller/internal/licences/adapters 1.063s
ok github.com/novox/mesh-controller/internal/link 67.757s
ok github.com/novox/mesh-controller/internal/lint 2.536s
ok github.com/novox/mesh-controller/internal/outward 1.097s
ok github.com/novox/mesh-controller/internal/overlay 1.080s
ok github.com/novox/mesh-controller/internal/secrets 1.531s
ok github.com/novox/mesh-controller/internal/store 3.591s
ok github.com/novox/mesh-controller/internal/testbus 1.250s
ok github.com/novox/mesh-controller/internal/token 1.016s
store tests, each run against the store:
./cmd/mesh-controller --- PASS: TestAStopWithoutAMergeWalksTheOthersAgain (0.43s)
./cmd/mesh-controller --- PASS: TestAStopWithoutAMergeEndsTheMergesThatContainIt (0.43s)
./cmd/mesh-controller --- PASS: TestAStopWalksTheOthersAgainInTheOpenBatch (0.43s)
./cmd/mesh-controller --- PASS: TestAStopNamesWhatStaysOnTheMachinesAndWhatStillCarriesIt (0.42s)
./cmd/mesh-controller --- PASS: TestAStopWithoutAMergeLeavesItOutOfABatch (0.41s)
./cmd/mesh-controller --- PASS: TestSavingPlansAndMovingMergesIsOneAct (0.38s)
./cmd/mesh-controller --- PASS: TestNodeShowAndStatusReadTheLastSendFromTheStore (0.46s)
./cmd/mesh-controller --- PASS: TestTheConditionsVerbReadsTheLooksTheBucketNoLongerHolds (0.32s)
./cmd/mesh-controller --- PASS: TestAWalkLetGoAndStoppedByVerbsIsSaidStartedAndEnded (0.48s)
./cmd/mesh-controller --- PASS: TestAWalkStoppedOrClosedByAPersonIsSaidEndedStopped (0.47s)
./cmd/mesh-controller --- PASS: TestAWalkRetriedByAPersonIsSaidStartedAgain (0.44s)
./cmd/mesh-controller --- PASS: TestABacklogReleasedByAPersonIsSaidStarted (0.43s)
./cmd/mesh-controller --- PASS: TestAWalkEndedByCancelOrClearIsSaidEnded (0.48s)
./cmd/mesh-controller --- PASS: TestAWalkRestartedByARebuildIsSaidStarted (0.42s)
./cmd/mesh-controller --- PASS: TestAWalkStoppedByHandAndRetriedEndsFailedWhenItFailsAgain (0.47s)
./internal/inventory --- PASS: TestTheLastSendSaysWhatTheMachineAnswered (0.27s)
./internal/inventory --- PASS: TestAReportIsTheLastSendsAnswerOnlyWhenItIsAboutThatSend (0.28s)
./internal/inventory --- PASS: TestAnIssuedValueIsSealedToEveryHolderOnceAndNotAgain (0.29s)
./internal/inventory --- PASS: TestAnIssuedValueIsSealedAgainAfterAKeyChangeOrAnAcceptance (0.27s)
./internal/inventory --- PASS: TestAConditionsLooksAreKeptBesideTheBucket (0.26s)
./internal/inventory --- PASS: TestAWalksStartIsKeptAndARefusedSaveLeavesItUnsaid (0.26s)
```
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.
Why (ADR 0312, accepted with the operator's Approve; issue 537). The node-engine half is merged and delivered (mesh-host #86, 3f7f7971): an
accesstakesgrant {containers, account}and the engine joins those identities to the path's own group, never changing the path. This half composes the grant.What changes
internal/catalogue/grants.go: for each read-write access of a module, the grant names the module's containers whose volume source is the path or below it (filepath.Clean,pathorpath/…;${access:x}already resolved; a:romount of a read-write access is granted too — the grant follows what mounts the path, not how), and the account its tools run as: the operator's account for the machine's tool runner, or the module's own account (ADR 0259 §8). The tool runner gets the access's id in itsrestart-on(sorted), so it restarts once to hold the group (ADR 0312 §6). A read-write access of a module that runs nothing there is sent an empty grant, so the engine still judges its group.link.GrantContract);Rendering.GrantsGroupsfrom the engine's newest statement (plan.go); an older engine gets nothing new and no restart.go.mod/vendor: the engine's validator pinned at mesh-host 3f7f797168d3;testdata/besiderecaptured there.Checked:
make checkgreen (all packages). Independent review approved the composition (no over-granting found;/storage/media2near-miss and:rotests added at its request).Rollout effects (the operator was told and said deliver now): on ace, every container mounting a read-write access is recreated once (radarr, sonarr, lidarr, bazarr, bookshelf, nzbget, qbittorrent, n8n; Plex reads only); a shared folder whose group cannot write becomes an unhealthy module condition; a newly granted group shows relogin needed where the operator's own session runs; the tool runner restarts once per machine where it gains a group.
Delivery
novox/mesh-controller@74bd90df7ef4— failed since 2026-10-12T14:30:59ZCovered: covered after its failure: a later walk that contains it was delivered: plan-1791819383983869952 (novox/mesh-controller at
c672b3dfinto main, done, contains its merge3cfc1216)Delivery plan — builds build-agent, mesh-controller, route-proxy → 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
74bd90dfmesh/merge-gate: PASS — every machine composes with the change as it did without (4 of 4 compose) (modules: build-agent, mesh-controller, route-proxy)mesh/repo-check: PASS — its merge-check.sh passedDelivery plan — builds build-agent, mesh-controller, route-proxy → ace, g14, novox, shanks; no bus step
Run by the build seat on shanks as
build-1791806598559726889(builds --log build-1791806598559726889).