A declared directory's owner now takes ${setting:<key>} — ${setting:puid} for the user alone, ${setting:puid}:${setting:pgid} for user and group — filled at composition from the module's settings layers, the same layers a file's content takes.
Whole numbers only. A value that is not a uid/gid (a name, text, a sign, a fraction, 2^32-1 or above) is refused at composition naming the key, and the directory is left as it was. The owner is written as the parsed number (strconv.FormatUint), so "0001" reaches the node-engine as 1. JudgeSettings runs the same pass, so settings set refuses such a value before it is stored. A key nothing sets is refused by name (UnsetSettingError).
Terminal only (review 60). Every key a directory's owner asks for is in TerminalKeys, whatever else asks for it (a trusted: false file, a default): root chowns the folder to it, so through the settings verb a caller could have set puid to 0. Uid/gid 0 stays allowed at the terminal.
Module check (OwnerSettingProblems, in ParseManifest). An owner holding a setting must be, on each side of the colon, a whole ${setting:key} or a whole number. Every key must be one the module asks for elsewhere (a file, a unit, a contribution, a served fact) or declares a default for.
The placeholder sweep (issue 231) accepts ${setting:…} in a directory's owner only; a file's owner still refuses it.
A key a directory's owner asks for is not called stray.
An assignment's placement owner (issue 153) still wins over the manifest's, as before.
Why
Issue 279: the TV, film and music managers refused their recycle-bin folders on the home server because they run as the node's puid/pgid and the folder's owner was a literal. Decided on the issue 2026-10-11: the run-as account stays an assignment property (ADR 0112), and a directory's owner may name it, whole numbers only.
Design limit I chose
"A key the module declares" is read as: a key the module asks for elsewhere or gives a default for. puid/pgid are the operator's own and never get a default (ADR 0262), so the media modules declare them through their identity file's ${setting:puid}.
Tested
internal/catalogue/setting_in_owner_test.go: filling, a composed machine's directory owned 1001:2000, refusals, JudgeSettings, the module check's shapes, not stray, written as the number (0001:00 → 1:0), owner keys in TerminalKeys.
cmd/mesh-controller/terminal_settings_test.goTestADirectoryOwnersKeyIsRefusedThroughAVerb (listed in testdata/store-tests): through the real verb dispatch, puid 0 per node, pgid mesh-wide, clear, and the command verb are refused and the layer is unchanged; another key with the owner kept still passes. Fails without the TerminalKeys change.
sh merge-check.sh with the throwaway store (make postgres): pass, store tests included.
mesh-media-catalog #33 (the recycle bins) depends on this and merges after it is delivered.
Fixes issue 279
## What
A declared directory's `owner` now takes `${setting:<key>}` — `${setting:puid}` for the user alone, `${setting:puid}:${setting:pgid}` for user and group — filled at composition from the module's settings layers, the same layers a file's content takes.
- **Whole numbers only.** A value that is not a uid/gid (a name, text, a sign, a fraction, 2^32-1 or above) is refused at composition naming the key, and the directory is left as it was. The owner is written as the parsed number (`strconv.FormatUint`), so "0001" reaches the node-engine as 1. `JudgeSettings` runs the same pass, so `settings set` refuses such a value before it is stored. A key nothing sets is refused by name (`UnsetSettingError`).
- **Terminal only (review 60).** Every key a directory's owner asks for is in `TerminalKeys`, whatever else asks for it (a `trusted: false` file, a default): root chowns the folder to it, so through the `settings` verb a caller could have set puid to 0. Uid/gid 0 stays allowed at the terminal.
- **Module check (`OwnerSettingProblems`, in `ParseManifest`).** An owner holding a setting must be, on each side of the colon, a whole `${setting:key}` or a whole number. Every key must be one the module asks for elsewhere (a file, a unit, a contribution, a served fact) or declares a default for.
- The placeholder sweep (issue 231) accepts `${setting:…}` in a directory's owner only; a file's owner still refuses it.
- A key a directory's owner asks for is not called stray.
- An assignment's placement owner (issue 153) still wins over the manifest's, as before.
## Why
Issue 279: the TV, film and music managers refused their recycle-bin folders on the home server because they run as the node's puid/pgid and the folder's owner was a literal. Decided on the issue 2026-10-11: the run-as account stays an assignment property (ADR 0112), and a directory's owner may name it, whole numbers only.
## Design limit I chose
"A key the module declares" is read as: a key the module asks for elsewhere or gives a default for. puid/pgid are the operator's own and never get a default (ADR 0262), so the media modules declare them through their identity file's `${setting:puid}`.
## Tested
- `internal/catalogue/setting_in_owner_test.go`: filling, a composed machine's directory owned `1001:2000`, refusals, JudgeSettings, the module check's shapes, not stray, written as the number (`0001:00` → `1:0`), owner keys in TerminalKeys.
- `cmd/mesh-controller/terminal_settings_test.go` `TestADirectoryOwnersKeyIsRefusedThroughAVerb` (listed in testdata/store-tests): through the real verb dispatch, puid 0 per node, pgid mesh-wide, clear, and the command verb are refused and the layer is unchanged; another key with the owner kept still passes. Fails without the TerminalKeys change.
- `sh merge-check.sh` with the throwaway store (`make postgres`): pass, store tests included.
mesh-media-catalog #33 (the recycle bins) depends on this and merges after it is delivered.
Fixes issue 279
Deliverynovox/mesh-controller@a371de37fef6 — delivered since 2026-10-12T14:08:49Z
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
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 is judged on its first machine
Machines
mesh-controller on novox: passed — healthy 3 times over 4m8s
mesh-controller on the rest running it: sent
build-agent on ace: passed — healthy 1 times over 1m44s
build-agent on the rest running it: sent
Transitions
2026-10-12 13:51 (new) → proposed (announced): novox/mesh-controller#260's head announced
2026-10-12 13:57 proposed → checked (checked): the verdict names this commit
2026-10-12 13:57 checked → ready (accepted): the gate passed or warned, and the repository's own check did not fail
2026-10-12 14:00 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:00 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:08 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@a371de37fef6` — **delivered** since 2026-10-12T14:08:49Z
**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
- 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 is judged on its first machine
**Machines**
- mesh-controller on novox: passed — healthy 3 times over 4m8s
- mesh-controller on the rest running it: sent
- build-agent on ace: passed — healthy 1 times over 1m44s
- build-agent on the rest running it: sent
**Transitions**
- 2026-10-12 13:51 (new) → proposed (announced): novox/mesh-controller#260's head announced
- 2026-10-12 13:57 proposed → checked (checked): the verdict names this commit
- 2026-10-12 13:57 checked → ready (accepted): the gate passed or warned, and the repository's own check did not fail
- 2026-10-12 14:00 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:00 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:08 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: 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
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 is judged on its first machine
read by no module's build: internal/catalogue/setting_in_owner_test.go
Run by the build seat on novox as build-1791808137896790199 (builds --log build-1791808137896790199).
--- the gate: build-agent, mesh-controller
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:20:08Z says they run
composing every machine as the mesh is
the bus's user list leaves out 5 user(s) the mesh has minted no credential for: controller, node.f35, node.idt, node.ygcyr, node.yvbpsm. Each is a user that cannot connect until one is issued
the bus's user list leaves out 5 user(s) the mesh has minted no credential for: controller, node.f35, node.idt, node.ygcyr, node.yvbpsm. Each is a user that cannot connect until one is issued
composing every machine with the change
the bus's user list leaves out 5 user(s) the mesh has minted no credential for: controller, node.f35, node.idt, node.ygcyr, node.yvbpsm. Each is a user that cannot connect until one is issued
the bus's user list leaves out 5 user(s) the mesh has minted no credential for: controller, node.f35, node.idt, node.ygcyr, node.yvbpsm. Each is a user that cannot connect until one is issued
merge gate: PASS — every machine composes with the change as it did without (4 of 4 compose)
judged by controller development build against the facts of 2026-10-12T12:20:08Z
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/setting_in_owner_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.065s
ok github.com/novox/mesh-controller/cmd/mesh-controller 322.384s
ok github.com/novox/mesh-controller/examples/objectstore-provisioner 1.021s
ok github.com/novox/mesh-controller/examples/postgres-provisioner 1.030s
ok github.com/novox/mesh-controller/examples/redis-provisioner 1.021s
ok github.com/novox/mesh-controller/examples/route-proxy 1.125s
ok github.com/novox/mesh-controller/internal/artifacts 1.061s
? github.com/novox/mesh-controller/internal/beside [no test files]
ok github.com/novox/mesh-controller/internal/broker 7.808s
ok github.com/novox/mesh-controller/internal/builder 20.560s
ok github.com/novox/mesh-controller/internal/catalogue 8.423s
ok github.com/novox/mesh-controller/internal/conditions 2.596s
ok github.com/novox/mesh-controller/internal/envfile 1.028s
ok github.com/novox/mesh-controller/internal/facts 1.036s
ok github.com/novox/mesh-controller/internal/identity 15.477s
ok github.com/novox/mesh-controller/internal/inventory 132.875s
ok github.com/novox/mesh-controller/internal/lease 17.696s
ok github.com/novox/mesh-controller/internal/licences 14.178s
ok github.com/novox/mesh-controller/internal/licences/adapters 1.014s
ok github.com/novox/mesh-controller/internal/link 70.068s
ok github.com/novox/mesh-controller/internal/lint 2.563s
ok github.com/novox/mesh-controller/internal/outward 1.048s
ok github.com/novox/mesh-controller/internal/overlay 1.025s
ok github.com/novox/mesh-controller/internal/secrets 1.529s
ok github.com/novox/mesh-controller/internal/store 8.500s
ok github.com/novox/mesh-controller/internal/testbus 1.182s
ok github.com/novox/mesh-controller/internal/token 1.014s
store tests, each run against the store:
./cmd/mesh-controller --- PASS: TestAStopWithoutAMergeWalksTheOthersAgain (0.45s)
./cmd/mesh-controller --- PASS: TestAStopWithoutAMergeEndsTheMergesThatContainIt (0.50s)
./cmd/mesh-controller --- PASS: TestAStopWalksTheOthersAgainInTheOpenBatch (0.55s)
./cmd/mesh-controller --- PASS: TestAStopNamesWhatStaysOnTheMachinesAndWhatStillCarriesIt (0.45s)
./cmd/mesh-controller --- PASS: TestAStopWithoutAMergeLeavesItOutOfABatch (0.47s)
./cmd/mesh-controller --- PASS: TestSavingPlansAndMovingMergesIsOneAct (0.46s)
./cmd/mesh-controller --- PASS: TestNodeShowAndStatusReadTheLastSendFromTheStore (0.48s)
./cmd/mesh-controller --- PASS: TestTheConditionsVerbReadsTheLooksTheBucketNoLongerHolds (0.34s)
./cmd/mesh-controller --- PASS: TestAWalkLetGoAndStoppedByVerbsIsSaidStartedAndEnded (0.53s)
./cmd/mesh-controller --- PASS: TestAWalkStoppedOrClosedByAPersonIsSaidEndedStopped (0.55s)
./cmd/mesh-controller --- PASS: TestAWalkRetriedByAPersonIsSaidStartedAgain (0.44s)
./cmd/mesh-controller --- PASS: TestABacklogReleasedByAPersonIsSaidStarted (0.44s)
./cmd/mesh-controller --- PASS: TestAWalkEndedByCancelOrClearIsSaidEnded (0.49s)
./cmd/mesh-controller --- PASS: TestAWalkRestartedByARebuildIsSaidStarted (0.51s)
./cmd/mesh-controller --- PASS: TestAWalkStoppedByHandAndRetriedEndsFailedWhenItFailsAgain (0.61s)
./internal/inventory --- PASS: TestTheLastSendSaysWhatTheMachineAnswered (0.28s)
./internal/inventory --- PASS: TestAReportIsTheLastSendsAnswerOnlyWhenItIsAboutThatSend (0.27s)
./internal/inventory --- PASS: TestAnIssuedValueIsSealedToEveryHolderOnceAndNotAgain (0.30s)
./internal/inventory --- PASS: TestAnIssuedValueIsSealedAgainAfterAKeyChangeOrAnAcceptance (0.30s)
./internal/inventory --- PASS: TestAConditionsLooksAreKeptBesideTheBucket (0.27s)
./internal/inventory --- PASS: TestAWalksStartIsKeptAndARefusedSaveLeavesItUnsaid (0.26s)
**Merge check** at `ea756680`
- `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
- 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 is judged on its first machine
- read by no module's build: internal/catalogue/setting_in_owner_test.go
Run by the build seat on novox as `build-1791808137896790199` (`builds --log build-1791808137896790199`).
```
--- the gate: build-agent, mesh-controller
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:20:08Z says they run
composing every machine as the mesh is
the bus's user list leaves out 5 user(s) the mesh has minted no credential for: controller, node.f35, node.idt, node.ygcyr, node.yvbpsm. Each is a user that cannot connect until one is issued
the bus's user list leaves out 5 user(s) the mesh has minted no credential for: controller, node.f35, node.idt, node.ygcyr, node.yvbpsm. Each is a user that cannot connect until one is issued
composing every machine with the change
the bus's user list leaves out 5 user(s) the mesh has minted no credential for: controller, node.f35, node.idt, node.ygcyr, node.yvbpsm. Each is a user that cannot connect until one is issued
the bus's user list leaves out 5 user(s) the mesh has minted no credential for: controller, node.f35, node.idt, node.ygcyr, node.yvbpsm. Each is a user that cannot connect until one is issued
merge gate: PASS — every machine composes with the change as it did without (4 of 4 compose)
judged by controller development build against the facts of 2026-10-12T12:20:08Z
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/setting_in_owner_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.065s
ok github.com/novox/mesh-controller/cmd/mesh-controller 322.384s
ok github.com/novox/mesh-controller/examples/objectstore-provisioner 1.021s
ok github.com/novox/mesh-controller/examples/postgres-provisioner 1.030s
ok github.com/novox/mesh-controller/examples/redis-provisioner 1.021s
ok github.com/novox/mesh-controller/examples/route-proxy 1.125s
ok github.com/novox/mesh-controller/internal/artifacts 1.061s
? github.com/novox/mesh-controller/internal/beside [no test files]
ok github.com/novox/mesh-controller/internal/broker 7.808s
ok github.com/novox/mesh-controller/internal/builder 20.560s
ok github.com/novox/mesh-controller/internal/catalogue 8.423s
ok github.com/novox/mesh-controller/internal/conditions 2.596s
ok github.com/novox/mesh-controller/internal/envfile 1.028s
ok github.com/novox/mesh-controller/internal/facts 1.036s
ok github.com/novox/mesh-controller/internal/identity 15.477s
ok github.com/novox/mesh-controller/internal/inventory 132.875s
ok github.com/novox/mesh-controller/internal/lease 17.696s
ok github.com/novox/mesh-controller/internal/licences 14.178s
ok github.com/novox/mesh-controller/internal/licences/adapters 1.014s
ok github.com/novox/mesh-controller/internal/link 70.068s
ok github.com/novox/mesh-controller/internal/lint 2.563s
ok github.com/novox/mesh-controller/internal/outward 1.048s
ok github.com/novox/mesh-controller/internal/overlay 1.025s
ok github.com/novox/mesh-controller/internal/secrets 1.529s
ok github.com/novox/mesh-controller/internal/store 8.500s
ok github.com/novox/mesh-controller/internal/testbus 1.182s
ok github.com/novox/mesh-controller/internal/token 1.014s
store tests, each run against the store:
./cmd/mesh-controller --- PASS: TestAStopWithoutAMergeWalksTheOthersAgain (0.45s)
./cmd/mesh-controller --- PASS: TestAStopWithoutAMergeEndsTheMergesThatContainIt (0.50s)
./cmd/mesh-controller --- PASS: TestAStopWalksTheOthersAgainInTheOpenBatch (0.55s)
./cmd/mesh-controller --- PASS: TestAStopNamesWhatStaysOnTheMachinesAndWhatStillCarriesIt (0.45s)
./cmd/mesh-controller --- PASS: TestAStopWithoutAMergeLeavesItOutOfABatch (0.47s)
./cmd/mesh-controller --- PASS: TestSavingPlansAndMovingMergesIsOneAct (0.46s)
./cmd/mesh-controller --- PASS: TestNodeShowAndStatusReadTheLastSendFromTheStore (0.48s)
./cmd/mesh-controller --- PASS: TestTheConditionsVerbReadsTheLooksTheBucketNoLongerHolds (0.34s)
./cmd/mesh-controller --- PASS: TestAWalkLetGoAndStoppedByVerbsIsSaidStartedAndEnded (0.53s)
./cmd/mesh-controller --- PASS: TestAWalkStoppedOrClosedByAPersonIsSaidEndedStopped (0.55s)
./cmd/mesh-controller --- PASS: TestAWalkRetriedByAPersonIsSaidStartedAgain (0.44s)
./cmd/mesh-controller --- PASS: TestABacklogReleasedByAPersonIsSaidStarted (0.44s)
./cmd/mesh-controller --- PASS: TestAWalkEndedByCancelOrClearIsSaidEnded (0.49s)
./cmd/mesh-controller --- PASS: TestAWalkRestartedByARebuildIsSaidStarted (0.51s)
./cmd/mesh-controller --- PASS: TestAWalkStoppedByHandAndRetriedEndsFailedWhenItFailsAgain (0.61s)
./internal/inventory --- PASS: TestTheLastSendSaysWhatTheMachineAnswered (0.28s)
./internal/inventory --- PASS: TestAReportIsTheLastSendsAnswerOnlyWhenItIsAboutThatSend (0.27s)
./internal/inventory --- PASS: TestAnIssuedValueIsSealedToEveryHolderOnceAndNotAgain (0.30s)
./internal/inventory --- PASS: TestAnIssuedValueIsSealedAgainAfterAKeyChangeOrAnAcceptance (0.30s)
./internal/inventory --- PASS: TestAConditionsLooksAreKeptBesideTheBucket (0.27s)
./internal/inventory --- PASS: TestAWalksStartIsKeptAndARefusedSaveLeavesItUnsaid (0.26s)
```
Independent review for issue 279 (a directory's owner following the account a module runs as). The filling, the number check and the module check are right, and the tests prove them. One trust gap blocks the merge.
Blocking: a key a directory's owner names is not a terminal key
TerminalKeys (internal/catalogue/terminal_keys.go) makes a key terminal-only when a served value or a trusted file asks for it. It does not look at a directory's owner. OwnerSettingProblems accepts an owner key that the module asks for anywhere else (a unit name, a contribution, a served fact, a file marked "trusted": false) or that has a declared default. In every one of those cases the key stays settable through the settings verb. Any caller of the mesh MCP server could then set it to 0, or to the agent account's uid, push, and have the node-engine chown that module's directory as root to the uid it chose. Rule 1 of issue 339 says what root owns is the terminal's or the operator's warrant (ADR 0277), never a verb's. ADR 0266's agent boundary depends on that rule.
I checked this with a throwaway test (not committed):
the PR's own accepted shape, owner: ${setting:workers} with a preference default: TerminalKeys = [places accesses], so workers is verb-settable;
recycler() with the identity file marked "trusted": false: it parses, and puid is not terminal;
JudgeSettings accepts puid: "0", pgid: "0", so a verb-set value of 0 composes to owner 0:0.
The paired media change is safe as it stands: the identity env file states no trust, so it counts as trusted and puid and pgid are terminal through it. The mechanism is not safe, though, because the next manifest that uses it can open the hole.
The fix: in TerminalKeys, add every ${setting:…} key found in a directory's owner. Add a test through the real verb dispatch (as issue 339's tests do) that a settings verb changing such a key is refused and the layer stays as it was. The test should fail on main+this-PR without the fix.
The decision note does not require refusing uid 0 or gid 0. Once the key is terminal-only, owner 0 is the operator's own choice, the same as a places owner (issue 153), and I would leave it allowed.
Non-blocking
Leading zeros pass unchanged.wholeID("00") and wholeID("0001") are true, and the value is substituted verbatim (00:0). The node-engine's idsOf reads 00 as uid 0, but its guard rootOwner compares the string to "0" and so calls 00 non-root. That error is on the strict side today, but the two disagree. Write the number in canonical form when filling: strconv.FormatUint(n, 10) from the parsed value.
Unset key on a node: the module is left out with an UnsetSettingError (needs-operator) and nothing of it is sent, which matches how a file's unset key is handled. Fine.
Negative, +1, 1, hex, fractions, true, 2^32-1 and above are all refused, and the refusal names the key. Names are refused, so nothing but a number reaches idsOf. Good.
A file's owner still refuses a placeholder, and a placement owner (issue 153) still wins over the manifest's owner. Good.
Checks run
sh merge-check.sh with MESH_TEST_POSTGRES against a throwaway Postgres: pass, including vet, gofmt, go test -race and every store test.
The five new tests all fail against main's catalogue code.
mesh/merge-gate: success (every machine composes). mesh/repo-check: success. mesh/delivery-group: failure, because the paired mesh-media-catalog#32 was rejected (its own check failed). The group cannot merge until that is fixed.
Verdict: request changes at ea75668
Independent review for issue 279 (a directory's owner following the account a module runs as). The filling, the number check and the module check are right, and the tests prove them. One trust gap blocks the merge.
## Blocking: a key a directory's owner names is not a terminal key
`TerminalKeys` (internal/catalogue/terminal_keys.go) makes a key terminal-only when a served value or a trusted file asks for it. It does not look at a directory's owner. `OwnerSettingProblems` accepts an owner key that the module asks for anywhere else (a unit name, a contribution, a served fact, a file marked `"trusted": false`) or that has a declared default. In every one of those cases the key stays settable through the `settings` verb. Any caller of the mesh MCP server could then set it to `0`, or to the agent account's uid, push, and have the node-engine chown that module's directory as root to the uid it chose. Rule 1 of issue 339 says what root owns is the terminal's or the operator's warrant (ADR 0277), never a verb's. ADR 0266's agent boundary depends on that rule.
I checked this with a throwaway test (not committed):
- the PR's own accepted shape, `owner: ${setting:workers}` with a preference default: `TerminalKeys` = [places accesses], so `workers` is verb-settable;
- `recycler()` with the identity file marked `"trusted": false`: it parses, and `puid` is not terminal;
- `JudgeSettings` accepts `puid: "0", pgid: "0"`, so a verb-set value of 0 composes to owner `0:0`.
The paired media change is safe as it stands: the identity env file states no trust, so it counts as trusted and `puid` and `pgid` are terminal through it. The mechanism is not safe, though, because the next manifest that uses it can open the hole.
The fix: in `TerminalKeys`, add every `${setting:…}` key found in a directory's owner. Add a test through the real verb dispatch (as issue 339's tests do) that a `settings` verb changing such a key is refused and the layer stays as it was. The test should fail on main+this-PR without the fix.
The decision note does not require refusing uid 0 or gid 0. Once the key is terminal-only, owner 0 is the operator's own choice, the same as a `places` owner (issue 153), and I would leave it allowed.
## Non-blocking
1. **Leading zeros pass unchanged.** `wholeID("00")` and `wholeID("0001")` are true, and the value is substituted verbatim (`00:0`). The node-engine's `idsOf` reads `00` as uid 0, but its guard `rootOwner` compares the string to `"0"` and so calls `00` non-root. That error is on the strict side today, but the two disagree. Write the number in canonical form when filling: `strconv.FormatUint(n, 10)` from the parsed value.
2. **Unset key on a node:** the module is left out with an `UnsetSettingError` (needs-operator) and nothing of it is sent, which matches how a file's unset key is handled. Fine.
3. Negative, `+1`, ` 1`, hex, fractions, `true`, 2^32-1 and above are all refused, and the refusal names the key. Names are refused, so nothing but a number reaches `idsOf`. Good.
4. A file's owner still refuses a placeholder, and a placement owner (issue 153) still wins over the manifest's owner. Good.
## Checks run
- `sh merge-check.sh` with `MESH_TEST_POSTGRES` against a throwaway Postgres: pass, including vet, gofmt, `go test -race` and every store test.
- The five new tests all fail against main's catalogue code.
- mesh/merge-gate: success (every machine composes). mesh/repo-check: success. mesh/delivery-group: **failure**, because the paired mesh-media-catalog#32 was rejected (its own check failed). The group cannot merge until that is fixed.
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
Run by the build seat on g14 as build-1791809353108857162 (builds --log build-1791809353108857162).
--- 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:48:28Z 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:48:28Z
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:
- cmd/mesh-controller/terminal_settings_test.go, internal/catalogue/setting_in_owner_test.go and testdata/store-tests 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.054s
ok github.com/novox/mesh-controller/cmd/mesh-controller 252.996s
ok github.com/novox/mesh-controller/examples/objectstore-provisioner 1.017s
ok github.com/novox/mesh-controller/examples/postgres-provisioner 1.035s
ok github.com/novox/mesh-controller/examples/redis-provisioner 1.020s
ok github.com/novox/mesh-controller/examples/route-proxy 1.174s
ok github.com/novox/mesh-controller/internal/artifacts 1.071s
? github.com/novox/mesh-controller/internal/beside [no test files]
ok github.com/novox/mesh-controller/internal/broker 4.474s
ok github.com/novox/mesh-controller/internal/builder 15.402s
ok github.com/novox/mesh-controller/internal/catalogue 7.892s
ok github.com/novox/mesh-controller/internal/conditions 2.531s
ok github.com/novox/mesh-controller/internal/envfile 1.035s
ok github.com/novox/mesh-controller/internal/facts 1.037s
ok github.com/novox/mesh-controller/internal/identity 4.952s
ok github.com/novox/mesh-controller/internal/inventory 87.911s
ok github.com/novox/mesh-controller/internal/lease 17.610s
ok github.com/novox/mesh-controller/internal/licences 4.524s
ok github.com/novox/mesh-controller/internal/licences/adapters 1.025s
ok github.com/novox/mesh-controller/internal/link 59.465s
ok github.com/novox/mesh-controller/internal/lint 2.566s
ok github.com/novox/mesh-controller/internal/outward 1.109s
ok github.com/novox/mesh-controller/internal/overlay 1.038s
ok github.com/novox/mesh-controller/internal/secrets 1.568s
ok github.com/novox/mesh-controller/internal/store 3.456s
ok github.com/novox/mesh-controller/internal/testbus 1.191s
ok github.com/novox/mesh-controller/internal/token 1.022s
store tests, each run against the store:
./cmd/mesh-controller --- PASS: TestAStopWithoutAMergeWalksTheOthersAgain (0.35s)
./cmd/mesh-controller --- PASS: TestAStopWithoutAMergeEndsTheMergesThatContainIt (0.35s)
./cmd/mesh-controller --- PASS: TestAStopWalksTheOthersAgainInTheOpenBatch (0.34s)
./cmd/mesh-controller --- PASS: TestAStopNamesWhatStaysOnTheMachinesAndWhatStillCarriesIt (0.34s)
./cmd/mesh-controller --- PASS: TestAStopWithoutAMergeLeavesItOutOfABatch (0.32s)
./cmd/mesh-controller --- PASS: TestSavingPlansAndMovingMergesIsOneAct (0.32s)
./cmd/mesh-controller --- PASS: TestNodeShowAndStatusReadTheLastSendFromTheStore (0.37s)
./cmd/mesh-controller --- PASS: TestTheConditionsVerbReadsTheLooksTheBucketNoLongerHolds (0.28s)
./cmd/mesh-controller --- PASS: TestAWalkLetGoAndStoppedByVerbsIsSaidStartedAndEnded (0.37s)
./cmd/mesh-controller --- PASS: TestAWalkStoppedOrClosedByAPersonIsSaidEndedStopped (0.39s)
./cmd/mesh-controller --- PASS: TestAWalkRetriedByAPersonIsSaidStartedAgain (0.34s)
./cmd/mesh-controller --- PASS: TestABacklogReleasedByAPersonIsSaidStarted (0.34s)
./cmd/mesh-controller --- PASS: TestAWalkEndedByCancelOrClearIsSaidEnded (0.40s)
./cmd/mesh-controller --- PASS: TestAWalkRestartedByARebuildIsSaidStarted (0.35s)
./cmd/mesh-controller --- PASS: TestAWalkStoppedByHandAndRetriedEndsFailedWhenItFailsAgain (0.38s)
./cmd/mesh-controller --- PASS: TestADirectoryOwnersKeyIsRefusedThroughAVerb (0.37s)
./internal/inventory --- PASS: TestTheLastSendSaysWhatTheMachineAnswered (0.20s)
./internal/inventory --- PASS: TestAReportIsTheLastSendsAnswerOnlyWhenItIsAboutThatSend (0.20s)
./internal/inventory --- PASS: TestAnIssuedValueIsSealedToEveryHolderOnceAndNotAgain (0.21s)
./internal/inventory --- PASS: TestAnIssuedValueIsSealedAgainAfterAKeyChangeOrAnAcceptance (0.20s)
./internal/inventory --- PASS: TestAConditionsLooksAreKeptBesideTheBucket (0.20s)
./internal/inventory --- PASS: TestAWalksStartIsKeptAndARefusedSaveLeavesItUnsaid (0.20s)
**Merge check** at `2823238d`
- `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
Run by the build seat on g14 as `build-1791809353108857162` (`builds --log build-1791809353108857162`).
```
--- 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:48:28Z 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:48:28Z
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:
- cmd/mesh-controller/terminal_settings_test.go, internal/catalogue/setting_in_owner_test.go and testdata/store-tests 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.054s
ok github.com/novox/mesh-controller/cmd/mesh-controller 252.996s
ok github.com/novox/mesh-controller/examples/objectstore-provisioner 1.017s
ok github.com/novox/mesh-controller/examples/postgres-provisioner 1.035s
ok github.com/novox/mesh-controller/examples/redis-provisioner 1.020s
ok github.com/novox/mesh-controller/examples/route-proxy 1.174s
ok github.com/novox/mesh-controller/internal/artifacts 1.071s
? github.com/novox/mesh-controller/internal/beside [no test files]
ok github.com/novox/mesh-controller/internal/broker 4.474s
ok github.com/novox/mesh-controller/internal/builder 15.402s
ok github.com/novox/mesh-controller/internal/catalogue 7.892s
ok github.com/novox/mesh-controller/internal/conditions 2.531s
ok github.com/novox/mesh-controller/internal/envfile 1.035s
ok github.com/novox/mesh-controller/internal/facts 1.037s
ok github.com/novox/mesh-controller/internal/identity 4.952s
ok github.com/novox/mesh-controller/internal/inventory 87.911s
ok github.com/novox/mesh-controller/internal/lease 17.610s
ok github.com/novox/mesh-controller/internal/licences 4.524s
ok github.com/novox/mesh-controller/internal/licences/adapters 1.025s
ok github.com/novox/mesh-controller/internal/link 59.465s
ok github.com/novox/mesh-controller/internal/lint 2.566s
ok github.com/novox/mesh-controller/internal/outward 1.109s
ok github.com/novox/mesh-controller/internal/overlay 1.038s
ok github.com/novox/mesh-controller/internal/secrets 1.568s
ok github.com/novox/mesh-controller/internal/store 3.456s
ok github.com/novox/mesh-controller/internal/testbus 1.191s
ok github.com/novox/mesh-controller/internal/token 1.022s
store tests, each run against the store:
./cmd/mesh-controller --- PASS: TestAStopWithoutAMergeWalksTheOthersAgain (0.35s)
./cmd/mesh-controller --- PASS: TestAStopWithoutAMergeEndsTheMergesThatContainIt (0.35s)
./cmd/mesh-controller --- PASS: TestAStopWalksTheOthersAgainInTheOpenBatch (0.34s)
./cmd/mesh-controller --- PASS: TestAStopNamesWhatStaysOnTheMachinesAndWhatStillCarriesIt (0.34s)
./cmd/mesh-controller --- PASS: TestAStopWithoutAMergeLeavesItOutOfABatch (0.32s)
./cmd/mesh-controller --- PASS: TestSavingPlansAndMovingMergesIsOneAct (0.32s)
./cmd/mesh-controller --- PASS: TestNodeShowAndStatusReadTheLastSendFromTheStore (0.37s)
./cmd/mesh-controller --- PASS: TestTheConditionsVerbReadsTheLooksTheBucketNoLongerHolds (0.28s)
./cmd/mesh-controller --- PASS: TestAWalkLetGoAndStoppedByVerbsIsSaidStartedAndEnded (0.37s)
./cmd/mesh-controller --- PASS: TestAWalkStoppedOrClosedByAPersonIsSaidEndedStopped (0.39s)
./cmd/mesh-controller --- PASS: TestAWalkRetriedByAPersonIsSaidStartedAgain (0.34s)
./cmd/mesh-controller --- PASS: TestABacklogReleasedByAPersonIsSaidStarted (0.34s)
./cmd/mesh-controller --- PASS: TestAWalkEndedByCancelOrClearIsSaidEnded (0.40s)
./cmd/mesh-controller --- PASS: TestAWalkRestartedByARebuildIsSaidStarted (0.35s)
./cmd/mesh-controller --- PASS: TestAWalkStoppedByHandAndRetriedEndsFailedWhenItFailsAgain (0.38s)
./cmd/mesh-controller --- PASS: TestADirectoryOwnersKeyIsRefusedThroughAVerb (0.37s)
./internal/inventory --- PASS: TestTheLastSendSaysWhatTheMachineAnswered (0.20s)
./internal/inventory --- PASS: TestAReportIsTheLastSendsAnswerOnlyWhenItIsAboutThatSend (0.20s)
./internal/inventory --- PASS: TestAnIssuedValueIsSealedToEveryHolderOnceAndNotAgain (0.21s)
./internal/inventory --- PASS: TestAnIssuedValueIsSealedAgainAfterAKeyChangeOrAnAcceptance (0.20s)
./internal/inventory --- PASS: TestAConditionsLooksAreKeptBesideTheBucket (0.20s)
./internal/inventory --- PASS: TestAWalksStartIsKeptAndARefusedSaveLeavesItUnsaid (0.20s)
```
This is a re-review against review 60. The blocking finding is fixed, and so is the non-blocking one.
The owner's keys are now terminal keys (rule 5)
TerminalKeys now adds every ${setting:…} found in a directory's owner, whatever else asks for that key. I reran my throwaway probe (not committed):
owner: ${setting:workers} with a preference default: TerminalKeys = [places accesses workers].
recycler() with the identity file marked "trusted": false: TerminalKeys = [places accesses pgid puid].
TestADirectoryOwnersKeyIsRefusedThroughAVerb runs through the real verb dispatch. These are all refused, and the layer is byte-for-byte unchanged afterwards:
puid 0 for one node;
pgid mesh-wide;
a clear;
command running settings set.
Another key still goes through the verb while the owner keys stay as they were, so the refusal is no wider than it needs to be.
I put back ea75668's terminal_keys.go and ran the new test with the store. It fails at the first step (puid 0 through the verb: <nil>), so the test proves the fix. The test is listed in testdata/store-tests, so repo-check counts it.
Owner written as the parsed number
The probe now gives 00 → 0, 0001 → 1 and 007 → 7. The node-engine's rootOwner and idsOf therefore read the same number.
Uid 0 stays allowed, now that only the terminal or the operator's warrant can set it. That matches the decision note and how a places owner works.
Checks
sh merge-check.sh with MESH_TEST_POSTGRES against a throwaway Postgres: pass, including gofmt, vet, go test -race and every store test, the new one included.
The paired mesh-media-catalog change has to pass its own group check before the group merges.
Verdict: approve at 2823238
This is a re-review against review 60. The blocking finding is fixed, and so is the non-blocking one.
## The owner's keys are now terminal keys (rule 5)
`TerminalKeys` now adds every `${setting:…}` found in a directory's owner, whatever else asks for that key. I reran my throwaway probe (not committed):
- `owner: ${setting:workers}` with a preference default: `TerminalKeys` = [places accesses workers].
- `recycler()` with the identity file marked `"trusted": false`: `TerminalKeys` = [places accesses pgid puid].
`TestADirectoryOwnersKeyIsRefusedThroughAVerb` runs through the real verb dispatch. These are all refused, and the layer is byte-for-byte unchanged afterwards:
- puid 0 for one node;
- pgid mesh-wide;
- a clear;
- `command` running `settings set`.
Another key still goes through the verb while the owner keys stay as they were, so the refusal is no wider than it needs to be.
I put back ea75668's `terminal_keys.go` and ran the new test with the store. It fails at the first step (`puid 0 through the verb: <nil>`), so the test proves the fix. The test is listed in `testdata/store-tests`, so repo-check counts it.
## Owner written as the parsed number
The probe now gives `00` → `0`, `0001` → `1` and `007` → `7`. The node-engine's `rootOwner` and `idsOf` therefore read the same number.
Uid 0 stays allowed, now that only the terminal or the operator's warrant can set it. That matches the decision note and how a `places` owner works.
## Checks
- `sh merge-check.sh` with `MESH_TEST_POSTGRES` against a throwaway Postgres: pass, including gofmt, vet, `go test -race` and every store test, the new one included.
- mesh/merge-gate: success (every machine composes).
- mesh/repo-check: success.
- mesh/delivery: ready.
The paired mesh-media-catalog change has to pass its own group check before the group merges.
A media manager runs as the puid/pgid its assignment sets per node, but a
declared directory's owner was literal, so a folder the app must write was
refused on a machine whose identity was not the image's default. A
directory's owner now takes ${setting:<key>} (user, or user:group), filled
at composition and refused unless the value is a whole number, and the
module check refuses any other shape or a key the module asks for nowhere
else.
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 …
Root chowns a directory to the number its owner's setting names, so a key
an owner asks for must not change through the settings verb: any caller
could have set puid to 0 or to its own uid. TerminalKeys now takes every
${setting:…} in a directory's owner, whatever else asks for it, and the
owner is written as the parsed number so "0001" never reaches the
node-engine as text (review 60).
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
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 is judged on its first machine
read by no module's build: cmd/mesh-controller/terminal_settings_test.go, internal/catalogue/setting_in_owner_test.go, testdata/store-tests
Run by the build seat on ace as build-1791813067211604193 (builds --log build-1791813067211604193).
--- the gate: build-agent, mesh-controller
mesh-controller: ok, 58 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-12T13:33:41Z 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-12T13:33:41Z
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:
- cmd/mesh-controller/terminal_settings_test.go, internal/catalogue/setting_in_owner_test.go and testdata/store-tests 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.034s
ok github.com/novox/mesh-controller/cmd/mesh-controller 260.627s
ok github.com/novox/mesh-controller/examples/objectstore-provisioner 1.045s
ok github.com/novox/mesh-controller/examples/postgres-provisioner 1.077s
ok github.com/novox/mesh-controller/examples/redis-provisioner 1.040s
ok github.com/novox/mesh-controller/examples/route-proxy 1.202s
ok github.com/novox/mesh-controller/internal/artifacts 1.110s
? github.com/novox/mesh-controller/internal/beside [no test files]
ok github.com/novox/mesh-controller/internal/broker 4.428s
ok github.com/novox/mesh-controller/internal/builder 34.852s
ok github.com/novox/mesh-controller/internal/catalogue 8.563s
ok github.com/novox/mesh-controller/internal/conditions 2.888s
ok github.com/novox/mesh-controller/internal/envfile 1.111s
ok github.com/novox/mesh-controller/internal/facts 1.062s
ok github.com/novox/mesh-controller/internal/identity 5.104s
ok github.com/novox/mesh-controller/internal/inventory 98.270s
ok github.com/novox/mesh-controller/internal/lease 17.797s
ok github.com/novox/mesh-controller/internal/licences 4.802s
ok github.com/novox/mesh-controller/internal/licences/adapters 1.046s
ok github.com/novox/mesh-controller/internal/link 60.344s
ok github.com/novox/mesh-controller/internal/lint 2.565s
ok github.com/novox/mesh-controller/internal/outward 1.123s
ok github.com/novox/mesh-controller/internal/overlay 1.080s
ok github.com/novox/mesh-controller/internal/secrets 1.496s
ok github.com/novox/mesh-controller/internal/store 3.650s
ok github.com/novox/mesh-controller/internal/testbus 1.274s
ok github.com/novox/mesh-controller/internal/token 1.028s
store tests, each run against the store:
./cmd/mesh-controller --- PASS: TestAStopWithoutAMergeWalksTheOthersAgain (0.43s)
./cmd/mesh-controller --- PASS: TestAStopWithoutAMergeEndsTheMergesThatContainIt (0.44s)
./cmd/mesh-controller --- PASS: TestAStopWalksTheOthersAgainInTheOpenBatch (0.43s)
./cmd/mesh-controller --- PASS: TestAStopNamesWhatStaysOnTheMachinesAndWhatStillCarriesIt (0.41s)
./cmd/mesh-controller --- PASS: TestAStopWithoutAMergeLeavesItOutOfABatch (0.40s)
./cmd/mesh-controller --- PASS: TestSavingPlansAndMovingMergesIsOneAct (0.38s)
./cmd/mesh-controller --- PASS: TestNodeShowAndStatusReadTheLastSendFromTheStore (0.44s)
./cmd/mesh-controller --- PASS: TestTheConditionsVerbReadsTheLooksTheBucketNoLongerHolds (0.30s)
./cmd/mesh-controller --- PASS: TestAWalkLetGoAndStoppedByVerbsIsSaidStartedAndEnded (0.49s)
./cmd/mesh-controller --- PASS: TestAWalkStoppedOrClosedByAPersonIsSaidEndedStopped (0.49s)
./cmd/mesh-controller --- PASS: TestAWalkRetriedByAPersonIsSaidStartedAgain (0.43s)
./cmd/mesh-controller --- PASS: TestABacklogReleasedByAPersonIsSaidStarted (0.41s)
./cmd/mesh-controller --- PASS: TestAWalkEndedByCancelOrClearIsSaidEnded (0.49s)
./cmd/mesh-controller --- PASS: TestAWalkRestartedByARebuildIsSaidStarted (0.43s)
./cmd/mesh-controller --- PASS: TestAWalkStoppedByHandAndRetriedEndsFailedWhenItFailsAgain (0.47s)
./cmd/mesh-controller --- PASS: TestReplay237 (0.43s)
./cmd/mesh-controller --- PASS: TestAnUnassignThatLeavesItsNodeUnresolvedSaysSoOnceInItsAnswer (0.39s)
./cmd/mesh-controller --- PASS: TestAnUnassignThatLeavesItsNodeResolvedSaysNothingOfIt (0.38s)
./cmd/mesh-controller --- PASS: TestAnAssignThatLeavesItsNodeUnresolvedSaysOnlyThePlansRefusal (0.41s)
./cmd/mesh-controller --- PASS: TestADirectoryOwnersKeyIsRefusedThroughAVerb (0.46s)
./internal/inventory --- PASS: TestTheLastSendSaysWhatTheMachineAnswered (0.26s)
./internal/inventory --- PASS: TestAReportIsTheLastSendsAnswerOnlyWhenItIsAboutThatSend (0.26s)
./internal/inventory --- PASS: TestAnIssuedValueIsSealedToEveryHolderOnceAndNotAgain (0.29s)
./internal/inventory --- PASS: TestAnIssuedValueIsSealedAgainAfterAKeyChangeOrAnAcceptance (0.29s)
./internal/inventory --- PASS: TestAConditionsLooksAreKeptBesideTheBucket (0.26s)
./internal/inventory --- PASS: TestAWalksStartIsKeptAndARefusedSaveLeavesItUnsaid (0.28s)
**Merge check** at `a371de37`
- `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
- 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 is judged on its first machine
- read by no module's build: cmd/mesh-controller/terminal_settings_test.go, internal/catalogue/setting_in_owner_test.go, testdata/store-tests
Run by the build seat on ace as `build-1791813067211604193` (`builds --log build-1791813067211604193`).
```
--- the gate: build-agent, mesh-controller
mesh-controller: ok, 58 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-12T13:33:41Z 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-12T13:33:41Z
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:
- cmd/mesh-controller/terminal_settings_test.go, internal/catalogue/setting_in_owner_test.go and testdata/store-tests 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.034s
ok github.com/novox/mesh-controller/cmd/mesh-controller 260.627s
ok github.com/novox/mesh-controller/examples/objectstore-provisioner 1.045s
ok github.com/novox/mesh-controller/examples/postgres-provisioner 1.077s
ok github.com/novox/mesh-controller/examples/redis-provisioner 1.040s
ok github.com/novox/mesh-controller/examples/route-proxy 1.202s
ok github.com/novox/mesh-controller/internal/artifacts 1.110s
? github.com/novox/mesh-controller/internal/beside [no test files]
ok github.com/novox/mesh-controller/internal/broker 4.428s
ok github.com/novox/mesh-controller/internal/builder 34.852s
ok github.com/novox/mesh-controller/internal/catalogue 8.563s
ok github.com/novox/mesh-controller/internal/conditions 2.888s
ok github.com/novox/mesh-controller/internal/envfile 1.111s
ok github.com/novox/mesh-controller/internal/facts 1.062s
ok github.com/novox/mesh-controller/internal/identity 5.104s
ok github.com/novox/mesh-controller/internal/inventory 98.270s
ok github.com/novox/mesh-controller/internal/lease 17.797s
ok github.com/novox/mesh-controller/internal/licences 4.802s
ok github.com/novox/mesh-controller/internal/licences/adapters 1.046s
ok github.com/novox/mesh-controller/internal/link 60.344s
ok github.com/novox/mesh-controller/internal/lint 2.565s
ok github.com/novox/mesh-controller/internal/outward 1.123s
ok github.com/novox/mesh-controller/internal/overlay 1.080s
ok github.com/novox/mesh-controller/internal/secrets 1.496s
ok github.com/novox/mesh-controller/internal/store 3.650s
ok github.com/novox/mesh-controller/internal/testbus 1.274s
ok github.com/novox/mesh-controller/internal/token 1.028s
store tests, each run against the store:
./cmd/mesh-controller --- PASS: TestAStopWithoutAMergeWalksTheOthersAgain (0.43s)
./cmd/mesh-controller --- PASS: TestAStopWithoutAMergeEndsTheMergesThatContainIt (0.44s)
./cmd/mesh-controller --- PASS: TestAStopWalksTheOthersAgainInTheOpenBatch (0.43s)
./cmd/mesh-controller --- PASS: TestAStopNamesWhatStaysOnTheMachinesAndWhatStillCarriesIt (0.41s)
./cmd/mesh-controller --- PASS: TestAStopWithoutAMergeLeavesItOutOfABatch (0.40s)
./cmd/mesh-controller --- PASS: TestSavingPlansAndMovingMergesIsOneAct (0.38s)
./cmd/mesh-controller --- PASS: TestNodeShowAndStatusReadTheLastSendFromTheStore (0.44s)
./cmd/mesh-controller --- PASS: TestTheConditionsVerbReadsTheLooksTheBucketNoLongerHolds (0.30s)
./cmd/mesh-controller --- PASS: TestAWalkLetGoAndStoppedByVerbsIsSaidStartedAndEnded (0.49s)
./cmd/mesh-controller --- PASS: TestAWalkStoppedOrClosedByAPersonIsSaidEndedStopped (0.49s)
./cmd/mesh-controller --- PASS: TestAWalkRetriedByAPersonIsSaidStartedAgain (0.43s)
./cmd/mesh-controller --- PASS: TestABacklogReleasedByAPersonIsSaidStarted (0.41s)
./cmd/mesh-controller --- PASS: TestAWalkEndedByCancelOrClearIsSaidEnded (0.49s)
./cmd/mesh-controller --- PASS: TestAWalkRestartedByARebuildIsSaidStarted (0.43s)
./cmd/mesh-controller --- PASS: TestAWalkStoppedByHandAndRetriedEndsFailedWhenItFailsAgain (0.47s)
./cmd/mesh-controller --- PASS: TestReplay237 (0.43s)
./cmd/mesh-controller --- PASS: TestAnUnassignThatLeavesItsNodeUnresolvedSaysSoOnceInItsAnswer (0.39s)
./cmd/mesh-controller --- PASS: TestAnUnassignThatLeavesItsNodeResolvedSaysNothingOfIt (0.38s)
./cmd/mesh-controller --- PASS: TestAnAssignThatLeavesItsNodeUnresolvedSaysOnlyThePlansRefusal (0.41s)
./cmd/mesh-controller --- PASS: TestADirectoryOwnersKeyIsRefusedThroughAVerb (0.46s)
./internal/inventory --- PASS: TestTheLastSendSaysWhatTheMachineAnswered (0.26s)
./internal/inventory --- PASS: TestAReportIsTheLastSendsAnswerOnlyWhenItIsAboutThatSend (0.26s)
./internal/inventory --- PASS: TestAnIssuedValueIsSealedToEveryHolderOnceAndNotAgain (0.29s)
./internal/inventory --- PASS: TestAnIssuedValueIsSealedAgainAfterAKeyChangeOrAnAcceptance (0.29s)
./internal/inventory --- PASS: TestAConditionsLooksAreKeptBesideTheBucket (0.26s)
./internal/inventory --- PASS: TestAWalksStartIsKeptAndARefusedSaveLeavesItUnsaid (0.28s)
```
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.
What
A declared directory's
ownernow takes${setting:<key>}—${setting:puid}for the user alone,${setting:puid}:${setting:pgid}for user and group — filled at composition from the module's settings layers, the same layers a file's content takes.strconv.FormatUint), so "0001" reaches the node-engine as 1.JudgeSettingsruns the same pass, sosettings setrefuses such a value before it is stored. A key nothing sets is refused by name (UnsetSettingError).TerminalKeys, whatever else asks for it (atrusted: falsefile, a default): root chowns the folder to it, so through thesettingsverb a caller could have set puid to 0. Uid/gid 0 stays allowed at the terminal.OwnerSettingProblems, inParseManifest). An owner holding a setting must be, on each side of the colon, a whole${setting:key}or a whole number. Every key must be one the module asks for elsewhere (a file, a unit, a contribution, a served fact) or declares a default for.${setting:…}in a directory's owner only; a file's owner still refuses it.Why
Issue 279: the TV, film and music managers refused their recycle-bin folders on the home server because they run as the node's puid/pgid and the folder's owner was a literal. Decided on the issue 2026-10-11: the run-as account stays an assignment property (ADR 0112), and a directory's owner may name it, whole numbers only.
Design limit I chose
"A key the module declares" is read as: a key the module asks for elsewhere or gives a default for. puid/pgid are the operator's own and never get a default (ADR 0262), so the media modules declare them through their identity file's
${setting:puid}.Tested
internal/catalogue/setting_in_owner_test.go: filling, a composed machine's directory owned1001:2000, refusals, JudgeSettings, the module check's shapes, not stray, written as the number (0001:00→1:0), owner keys in TerminalKeys.cmd/mesh-controller/terminal_settings_test.goTestADirectoryOwnersKeyIsRefusedThroughAVerb(listed in testdata/store-tests): through the real verb dispatch, puid 0 per node, pgid mesh-wide, clear, and the command verb are refused and the layer is unchanged; another key with the owner kept still passes. Fails without the TerminalKeys change.sh merge-check.shwith the throwaway store (make postgres): pass, store tests included.mesh-media-catalog #33 (the recycle bins) depends on this and merges after it is delivered.
Fixes issue 279
Delivery
novox/mesh-controller@a371de37fef6— delivered since 2026-10-12T14:08:49ZDelivery 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
ea756680mesh/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-1791808137896790199(builds --log build-1791808137896790199).Verdict: request changes at
ea75668Independent review for issue 279 (a directory's owner following the account a module runs as). The filling, the number check and the module check are right, and the tests prove them. One trust gap blocks the merge.
Blocking: a key a directory's owner names is not a terminal key
TerminalKeys(internal/catalogue/terminal_keys.go) makes a key terminal-only when a served value or a trusted file asks for it. It does not look at a directory's owner.OwnerSettingProblemsaccepts an owner key that the module asks for anywhere else (a unit name, a contribution, a served fact, a file marked"trusted": false) or that has a declared default. In every one of those cases the key stays settable through thesettingsverb. Any caller of the mesh MCP server could then set it to0, or to the agent account's uid, push, and have the node-engine chown that module's directory as root to the uid it chose. Rule 1 of issue 339 says what root owns is the terminal's or the operator's warrant (ADR 0277), never a verb's. ADR 0266's agent boundary depends on that rule.I checked this with a throwaway test (not committed):
owner: ${setting:workers}with a preference default:TerminalKeys= [places accesses], soworkersis verb-settable;recycler()with the identity file marked"trusted": false: it parses, andpuidis not terminal;JudgeSettingsacceptspuid: "0", pgid: "0", so a verb-set value of 0 composes to owner0:0.The paired media change is safe as it stands: the identity env file states no trust, so it counts as trusted and
puidandpgidare terminal through it. The mechanism is not safe, though, because the next manifest that uses it can open the hole.The fix: in
TerminalKeys, add every${setting:…}key found in a directory's owner. Add a test through the real verb dispatch (as issue 339's tests do) that asettingsverb changing such a key is refused and the layer stays as it was. The test should fail on main+this-PR without the fix.The decision note does not require refusing uid 0 or gid 0. Once the key is terminal-only, owner 0 is the operator's own choice, the same as a
placesowner (issue 153), and I would leave it allowed.Non-blocking
wholeID("00")andwholeID("0001")are true, and the value is substituted verbatim (00:0). The node-engine'sidsOfreads00as uid 0, but its guardrootOwnercompares the string to"0"and so calls00non-root. That error is on the strict side today, but the two disagree. Write the number in canonical form when filling:strconv.FormatUint(n, 10)from the parsed value.UnsetSettingError(needs-operator) and nothing of it is sent, which matches how a file's unset key is handled. Fine.+1,1, hex, fractions,true, 2^32-1 and above are all refused, and the refusal names the key. Names are refused, so nothing but a number reachesidsOf. Good.Checks run
sh merge-check.shwithMESH_TEST_POSTGRESagainst a throwaway Postgres: pass, including vet, gofmt,go test -raceand every store test.Merge check at
2823238dmesh/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 g14 as
build-1791809353108857162(builds --log build-1791809353108857162).Verdict: approve at
2823238This is a re-review against review 60. The blocking finding is fixed, and so is the non-blocking one.
The owner's keys are now terminal keys (rule 5)
TerminalKeysnow adds every${setting:…}found in a directory's owner, whatever else asks for that key. I reran my throwaway probe (not committed):owner: ${setting:workers}with a preference default:TerminalKeys= [places accesses workers].recycler()with the identity file marked"trusted": false:TerminalKeys= [places accesses pgid puid].TestADirectoryOwnersKeyIsRefusedThroughAVerbruns through the real verb dispatch. These are all refused, and the layer is byte-for-byte unchanged afterwards:commandrunningsettings set.Another key still goes through the verb while the owner keys stay as they were, so the refusal is no wider than it needs to be.
I put back ea75668's
terminal_keys.goand ran the new test with the store. It fails at the first step (puid 0 through the verb: <nil>), so the test proves the fix. The test is listed intestdata/store-tests, so repo-check counts it.Owner written as the parsed number
The probe now gives
00→0,0001→1and007→7. The node-engine'srootOwnerandidsOftherefore read the same number.Uid 0 stays allowed, now that only the terminal or the operator's warrant can set it. That matches the decision note and how a
placesowner works.Checks
sh merge-check.shwithMESH_TEST_POSTGRESagainst a throwaway Postgres: pass, including gofmt, vet,go test -raceand every store test, the new one included.The paired mesh-media-catalog change has to pass its own group check before the group merges.
A media manager runs as the puid/pgid its assignment sets per node, but a declared directory's owner was literal, so a folder the app must write was refused on a machine whose identity was not the image's default. A directory's owner now takes ${setting:<key>} (user, or user:group), filled at composition and refused unless the value is a whole number, and the module check refuses any other shape or a key the module asks for nowhere else.Root chowns a directory to the number its owner's setting names, so a key an owner asks for must not change through the settings verb: any caller could have set puid to 0 or to its own uid. TerminalKeys now takes every ${setting:…} in a directory's owner, whatever else asks for it, and the owner is written as the parsed number so "0001" never reaches the node-engine as text (review 60).2823238de5toa371de37feMerge check at
a371de37mesh/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 ace as
build-1791813067211604193(builds --log build-1791813067211604193).