Fixes issue 397 (a call's kept record holds the controller's whole command line, which may carry a setting's value).
Why
kept() in internal/link/calls.go withholds the arguments line, values, secret and stdin, and kept the command argument of the generic command verb verbatim, to 120 bytes. A line such as settings set <module> '<value>' --node <node> through that verb therefore put the value itself into the calls record, which answers anyone who may call the seat.
What it does now
command is kept the way a mesh-cli line is: its first word, with the rest said to have been given. Two bounds the issue did not ask for and I decided here, both narrow:
A command of one word is kept whole (builds, plans, conditions), because there is nothing after it to withhold and the record stays readable for the reading commands that make up most of its use.
A command argument that is not a string is kept as (given, not kept), since its first word cannot be taken.
Whether a real secret was kept
The report left this open; it is now checked. I read the whole answer of mesh-controller.calls at 2026-10-10 22:52 UTC — 14850 lines — and looked in it for the kept command argument and for which verbs were called. The word "command" does not appear in it, and no call of the command verb is among them. So no setting's value is readable there as it stands. This says nothing about calls older than the record's window, which keeps only the newest.
Checked here
The new test fails against the unfixed code, where it reads back s3cret verbatim from a --values line and laptop and show from a node show laptop line; it passes with the fix. I ran it both ways (git stash on calls.go alone).
go test ./internal/link/ -count=1: ok.
go vet ./... clean, and gofmt -l names nothing outside vendor/.
make check cannot run on this machine: its fmt step fails on three vendored third-party files that are not gofmt'd (antithesis-sdk-go, nats-server), which this change does not touch. I ran the rest of what it does instead — make postgres and go test -race -timeout 15m ./... — and will say what that gave before asking for the merge.
Fixes issue 397 (a call's kept record holds the controller's whole command line, which may carry a setting's value).
## Why
`kept()` in internal/link/calls.go withholds the arguments `line`, `values`, `secret` and `stdin`, and kept the `command` argument of the generic `command` verb verbatim, to 120 bytes. A line such as `settings set <module> '<value>' --node <node>` through that verb therefore put the value itself into the `calls` record, which answers anyone who may call the seat.
## What it does now
`command` is kept the way a mesh-cli `line` is: its first word, with the rest said to have been given. Two bounds the issue did not ask for and I decided here, both narrow:
- A command of **one word** is kept whole (`builds`, `plans`, `conditions`), because there is nothing after it to withhold and the record stays readable for the reading commands that make up most of its use.
- A `command` argument that is **not a string** is kept as `(given, not kept)`, since its first word cannot be taken.
## Whether a real secret was kept
The report left this open; it is now checked. I read the whole answer of `mesh-controller.calls` at 2026-10-10 22:52 UTC — 14850 lines — and looked in it for the kept `command` argument and for which verbs were called. The word "command" does not appear in it, and no call of the `command` verb is among them. So no setting's value is readable there as it stands. This says nothing about calls older than the record's window, which keeps only the newest.
## Checked here
- The new test fails against the unfixed code, where it reads back `s3cret` verbatim from a `--values` line and `laptop` and `show` from a `node show laptop` line; it passes with the fix. I ran it both ways (`git stash` on calls.go alone).
- `go test ./internal/link/ -count=1`: ok.
- `go vet ./...` clean, and `gofmt -l` names nothing outside `vendor/`.
- `make check` cannot run on this machine: its `fmt` step fails on three vendored third-party files that are not gofmt'd (antithesis-sdk-go, nats-server), which this change does not touch. I ran the rest of what it does instead — `make postgres` and `go test -race -timeout 15m ./...` — and will say what that gave before asking for the merge.
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 …
kept() withheld the arguments line, values, secret and stdin, and kept
the command argument of the generic command verb verbatim. A line such
as `settings set <module> '<value>' --node <node>` therefore put the
value into the calls record, which answers anyone who may call the seat.
It is now kept as a mesh-cli line is: its first word, with the rest said
to have been given. A command of one word is kept whole, since there is
nothing after it to withhold, and one that is not a string is kept as
"(given, not kept)".
The record as it stands holds no such line: its whole answer, read at
2026-10-10 22:52 UTC, carries no call of the command verb. That says
nothing of calls older than its window.
Deliverynovox/mesh-controller@15a9919df53e — delivered since 2026-10-10T23:36:17Z
Delivery plan — builds build-agent, mesh-controller → ace, g14, novox, shanks; no bus step
tier 0: mesh-controller
tier 1: build-agent
ace: receives build-agent
g14: receives build-agent
novox: receives mesh-controller, build-agent
shanks: receives build-agent
build-agent keeps data (ADR 0233): what it holds is backed up before it moves
Machines
mesh-controller on novox: passed — healthy 3 times over 3m37s
mesh-controller on the rest running it: sent
build-agent on ace: passed — healthy 3 times over 4m35s
build-agent on the rest running it: sent
Transitions
2026-10-10 23:05 (new) → proposed (announced): novox/mesh-controller#210's head announced
2026-10-10 23:11 proposed → checked (checked): the verdict names this commit
2026-10-10 23:11 checked → ready (accepted): the gate passed or warned, and the repository's own check did not fail
2026-10-10 23:25 ready → published (merged): on the trunk its modules follow: merged there, and its walk opened — or nothing for a walk to move
2026-10-10 23:25 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-10 23:36 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@15a9919df53e` — **delivered** since 2026-10-10T23:36:17Z
**Delivery plan** — builds build-agent, mesh-controller → ace, g14, novox, shanks; no bus step
- tier 0: mesh-controller
- tier 1: build-agent
- ace: receives build-agent
- g14: receives build-agent
- novox: receives mesh-controller, build-agent
- shanks: receives build-agent
- build-agent keeps data (ADR 0233): what it holds is backed up before it moves
**Machines**
- mesh-controller on novox: passed — healthy 3 times over 3m37s
- mesh-controller on the rest running it: sent
- build-agent on ace: passed — healthy 3 times over 4m35s
- build-agent on the rest running it: sent
**Transitions**
- 2026-10-10 23:05 (new) → proposed (announced): novox/mesh-controller#210's head announced
- 2026-10-10 23:11 proposed → checked (checked): the verdict names this commit
- 2026-10-10 23:11 checked → ready (accepted): the gate passed or warned, and the repository's own check did not fail
- 2026-10-10 23:25 ready → published (merged): on the trunk its modules follow: merged there, and its walk opened — or nothing for a walk to move
- 2026-10-10 23:25 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-10 23:36 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
read by no module's build: internal/link/calls_test.go
Run by the build seat on novox as build-1791672837439356752 (builds --log build-1791672837439356752).
--- the gate: build-agent, mesh-controller
mesh-controller: ok, 56 tool(s); WARNING: merge-window ask(s) for a setting and do(es) not say whether it is trusted, so it counts as trusted: set at the terminal alone; say "trusted" false where nothing trusts it (novox/hq issue 339); WARNING: controller stay(s) up and say(s) not how it is ready — judged by liveness alone, refused from 2026-11-18 (ADR 0240 rule 8)
long-running resources without health: 1
files asking for a setting without saying whether it is trusted: 1
1 manifest(s) checked. Judged against the seats this binary carries; a claim on one of the mesh's own seats is judged fully at registration, and a seat declared by a module not given here reads as unknown. Identities judged on a 6-character machine name, against the bounds of the providers given here
judging 1 module(s) changed against 4 machine(s), as the snapshot of 2026-10-10T22:12:40Z 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-10T22:12:40Z
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/link/calls_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.045s
ok github.com/novox/mesh-controller/cmd/mesh-controller 274.914s
ok github.com/novox/mesh-controller/examples/objectstore-provisioner 1.024s
ok github.com/novox/mesh-controller/examples/postgres-provisioner 1.042s
ok github.com/novox/mesh-controller/examples/redis-provisioner 1.022s
ok github.com/novox/mesh-controller/examples/route-proxy 1.136s
ok github.com/novox/mesh-controller/internal/artifacts 1.058s
ok github.com/novox/mesh-controller/internal/broker 10.390s
ok github.com/novox/mesh-controller/internal/builder 15.427s
ok github.com/novox/mesh-controller/internal/catalogue 5.111s
ok github.com/novox/mesh-controller/internal/conditions 2.519s
ok github.com/novox/mesh-controller/internal/envfile 1.029s
ok github.com/novox/mesh-controller/internal/facts 1.033s
ok github.com/novox/mesh-controller/internal/identity 16.289s
ok github.com/novox/mesh-controller/internal/inventory 113.569s
ok github.com/novox/mesh-controller/internal/lease 17.674s
ok github.com/novox/mesh-controller/internal/licences 15.557s
ok github.com/novox/mesh-controller/internal/licences/adapters 1.011s
ok github.com/novox/mesh-controller/internal/link 59.538s
ok github.com/novox/mesh-controller/internal/lint 2.130s
ok github.com/novox/mesh-controller/internal/outward 1.043s
ok github.com/novox/mesh-controller/internal/overlay 1.026s
ok github.com/novox/mesh-controller/internal/secrets 1.428s
ok github.com/novox/mesh-controller/internal/store 11.857s
ok github.com/novox/mesh-controller/internal/testbus 1.178s
ok github.com/novox/mesh-controller/internal/token 1.015s
**Merge check** at `1390836b`
- `mesh/merge-gate`: **PASS** — every machine composes with the change as it did without (4 of 4 compose) (modules: build-agent, mesh-controller)
- `mesh/repo-check`: **PASS** — its merge-check.sh passed
**Delivery plan** — builds build-agent, mesh-controller → ace, g14, novox, shanks; no bus step
- tier 0: mesh-controller
- tier 1: build-agent
- ace: receives build-agent
- g14: receives build-agent
- novox: receives mesh-controller, build-agent
- shanks: receives build-agent
- build-agent keeps data (ADR 0233): what it holds is backed up before it moves
- read by no module's build: internal/link/calls_test.go
Run by the build seat on novox as `build-1791672837439356752` (`builds --log build-1791672837439356752`).
```
--- the gate: build-agent, mesh-controller
mesh-controller: ok, 56 tool(s); WARNING: merge-window ask(s) for a setting and do(es) not say whether it is trusted, so it counts as trusted: set at the terminal alone; say "trusted" false where nothing trusts it (novox/hq issue 339); WARNING: controller stay(s) up and say(s) not how it is ready — judged by liveness alone, refused from 2026-11-18 (ADR 0240 rule 8)
long-running resources without health: 1
files asking for a setting without saying whether it is trusted: 1
1 manifest(s) checked. Judged against the seats this binary carries; a claim on one of the mesh's own seats is judged fully at registration, and a seat declared by a module not given here reads as unknown. Identities judged on a 6-character machine name, against the bounds of the providers given here
judging 1 module(s) changed against 4 machine(s), as the snapshot of 2026-10-10T22:12:40Z 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-10T22:12:40Z
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/link/calls_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.045s
ok github.com/novox/mesh-controller/cmd/mesh-controller 274.914s
ok github.com/novox/mesh-controller/examples/objectstore-provisioner 1.024s
ok github.com/novox/mesh-controller/examples/postgres-provisioner 1.042s
ok github.com/novox/mesh-controller/examples/redis-provisioner 1.022s
ok github.com/novox/mesh-controller/examples/route-proxy 1.136s
ok github.com/novox/mesh-controller/internal/artifacts 1.058s
ok github.com/novox/mesh-controller/internal/broker 10.390s
ok github.com/novox/mesh-controller/internal/builder 15.427s
ok github.com/novox/mesh-controller/internal/catalogue 5.111s
ok github.com/novox/mesh-controller/internal/conditions 2.519s
ok github.com/novox/mesh-controller/internal/envfile 1.029s
ok github.com/novox/mesh-controller/internal/facts 1.033s
ok github.com/novox/mesh-controller/internal/identity 16.289s
ok github.com/novox/mesh-controller/internal/inventory 113.569s
ok github.com/novox/mesh-controller/internal/lease 17.674s
ok github.com/novox/mesh-controller/internal/licences 15.557s
ok github.com/novox/mesh-controller/internal/licences/adapters 1.011s
ok github.com/novox/mesh-controller/internal/link 59.538s
ok github.com/novox/mesh-controller/internal/lint 2.130s
ok github.com/novox/mesh-controller/internal/outward 1.043s
ok github.com/novox/mesh-controller/internal/overlay 1.026s
ok github.com/novox/mesh-controller/internal/secrets 1.428s
ok github.com/novox/mesh-controller/internal/store 11.857s
ok github.com/novox/mesh-controller/internal/testbus 1.178s
ok github.com/novox/mesh-controller/internal/token 1.015s
```
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 …
The review of #210 found that the fix left the hole open and widened
another.
A command's words were cut on a space alone, while the verb's own
splitter parts them on a space, a tab or a newline. The same line
written with tabs found no space, so all of it was kept — the very hole
this closes. Its words are now parted as the splitter parts them.
And because the command arm sits above the arm that caps a string at
120 bytes, a command kept whole was no longer capped: for a 300-byte
single token the change kept more than the code it replaced. The first
word now carries the same cap.
A one-word command is still kept whole, but the comment no longer
claims it carries nothing to withhold: the record is written before the
verb judges the line, so one word may be a token or compact JSON. The
cap is what bounds that.
The test now says the whole of what is kept for each line, which is
also what proves the rest is gone, and looks for forbidden words as
whole words rather than as substrings — so "set" is back in the list,
and "show" cannot hide in a word such as "shown". All eight cases fail
against the unfixed code.
mesh/merge-gate: PASS — every machine composes with the change as it did without (4 of 4 compose) (modules: build-agent, mesh-controller)
mesh/repo-check: PASS — its merge-check.sh passed
Delivery plan — builds build-agent, mesh-controller → ace, g14, novox, shanks; no bus step
tier 0: mesh-controller
tier 1: build-agent
ace: receives build-agent
g14: receives build-agent
novox: receives mesh-controller, build-agent
shanks: receives build-agent
build-agent keeps data (ADR 0233): what it holds is backed up before it moves
read by no module's build: internal/link/calls_test.go
Run by the build seat on g14 as build-1791673505305625892 (builds --log build-1791673505305625892).
--- the gate: build-agent, mesh-controller
mesh-controller: ok, 56 tool(s); WARNING: merge-window ask(s) for a setting and do(es) not say whether it is trusted, so it counts as trusted: set at the terminal alone; say "trusted" false where nothing trusts it (novox/hq issue 339); WARNING: controller stay(s) up and say(s) not how it is ready — judged by liveness alone, refused from 2026-11-18 (ADR 0240 rule 8)
long-running resources without health: 1
files asking for a setting without saying whether it is trusted: 1
1 manifest(s) checked. Judged against the seats this binary carries; a claim on one of the mesh's own seats is judged fully at registration, and a seat declared by a module not given here reads as unknown. Identities judged on a 6-character machine name, against the bounds of the providers given here
judging 1 module(s) changed against 4 machine(s), as the snapshot of 2026-10-10T23:02:40Z 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-10T23:02:40Z
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/link/calls_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.034s
ok github.com/novox/mesh-controller/cmd/mesh-controller 219.972s
ok github.com/novox/mesh-controller/examples/objectstore-provisioner 1.010s
ok github.com/novox/mesh-controller/examples/postgres-provisioner 1.017s
ok github.com/novox/mesh-controller/examples/redis-provisioner 1.009s
ok github.com/novox/mesh-controller/examples/route-proxy 1.150s
ok github.com/novox/mesh-controller/internal/artifacts 1.042s
ok github.com/novox/mesh-controller/internal/broker 2.618s
ok github.com/novox/mesh-controller/internal/builder 2.389s
ok github.com/novox/mesh-controller/internal/catalogue 4.402s
ok github.com/novox/mesh-controller/internal/conditions 2.351s
ok github.com/novox/mesh-controller/internal/envfile 1.025s
ok github.com/novox/mesh-controller/internal/facts 1.027s
ok github.com/novox/mesh-controller/internal/identity 3.922s
ok github.com/novox/mesh-controller/internal/inventory 73.775s
ok github.com/novox/mesh-controller/internal/lease 17.589s
ok github.com/novox/mesh-controller/internal/licences 3.577s
ok github.com/novox/mesh-controller/internal/licences/adapters 1.007s
ok github.com/novox/mesh-controller/internal/link 51.131s
ok github.com/novox/mesh-controller/internal/lint 2.013s
ok github.com/novox/mesh-controller/internal/outward 1.039s
ok github.com/novox/mesh-controller/internal/overlay 1.021s
ok github.com/novox/mesh-controller/internal/secrets 1.428s
ok github.com/novox/mesh-controller/internal/store 3.210s
ok github.com/novox/mesh-controller/internal/testbus 1.160s
ok github.com/novox/mesh-controller/internal/token 1.017s
**Merge check** at `15a9919d`
- `mesh/merge-gate`: **PASS** — every machine composes with the change as it did without (4 of 4 compose) (modules: build-agent, mesh-controller)
- `mesh/repo-check`: **PASS** — its merge-check.sh passed
**Delivery plan** — builds build-agent, mesh-controller → ace, g14, novox, shanks; no bus step
- tier 0: mesh-controller
- tier 1: build-agent
- ace: receives build-agent
- g14: receives build-agent
- novox: receives mesh-controller, build-agent
- shanks: receives build-agent
- build-agent keeps data (ADR 0233): what it holds is backed up before it moves
- read by no module's build: internal/link/calls_test.go
Run by the build seat on g14 as `build-1791673505305625892` (`builds --log build-1791673505305625892`).
```
--- the gate: build-agent, mesh-controller
mesh-controller: ok, 56 tool(s); WARNING: merge-window ask(s) for a setting and do(es) not say whether it is trusted, so it counts as trusted: set at the terminal alone; say "trusted" false where nothing trusts it (novox/hq issue 339); WARNING: controller stay(s) up and say(s) not how it is ready — judged by liveness alone, refused from 2026-11-18 (ADR 0240 rule 8)
long-running resources without health: 1
files asking for a setting without saying whether it is trusted: 1
1 manifest(s) checked. Judged against the seats this binary carries; a claim on one of the mesh's own seats is judged fully at registration, and a seat declared by a module not given here reads as unknown. Identities judged on a 6-character machine name, against the bounds of the providers given here
judging 1 module(s) changed against 4 machine(s), as the snapshot of 2026-10-10T23:02:40Z 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-10T23:02:40Z
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/link/calls_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.034s
ok github.com/novox/mesh-controller/cmd/mesh-controller 219.972s
ok github.com/novox/mesh-controller/examples/objectstore-provisioner 1.010s
ok github.com/novox/mesh-controller/examples/postgres-provisioner 1.017s
ok github.com/novox/mesh-controller/examples/redis-provisioner 1.009s
ok github.com/novox/mesh-controller/examples/route-proxy 1.150s
ok github.com/novox/mesh-controller/internal/artifacts 1.042s
ok github.com/novox/mesh-controller/internal/broker 2.618s
ok github.com/novox/mesh-controller/internal/builder 2.389s
ok github.com/novox/mesh-controller/internal/catalogue 4.402s
ok github.com/novox/mesh-controller/internal/conditions 2.351s
ok github.com/novox/mesh-controller/internal/envfile 1.025s
ok github.com/novox/mesh-controller/internal/facts 1.027s
ok github.com/novox/mesh-controller/internal/identity 3.922s
ok github.com/novox/mesh-controller/internal/inventory 73.775s
ok github.com/novox/mesh-controller/internal/lease 17.589s
ok github.com/novox/mesh-controller/internal/licences 3.577s
ok github.com/novox/mesh-controller/internal/licences/adapters 1.007s
ok github.com/novox/mesh-controller/internal/link 51.131s
ok github.com/novox/mesh-controller/internal/lint 2.013s
ok github.com/novox/mesh-controller/internal/outward 1.039s
ok github.com/novox/mesh-controller/internal/overlay 1.021s
ok github.com/novox/mesh-controller/internal/secrets 1.428s
ok github.com/novox/mesh-controller/internal/store 3.210s
ok github.com/novox/mesh-controller/internal/testbus 1.160s
ok github.com/novox/mesh-controller/internal/token 1.017s
```
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Fixes issue 397 (a call's kept record holds the controller's whole command line, which may carry a setting's value).
Why
kept()in internal/link/calls.go withholds the argumentsline,values,secretandstdin, and kept thecommandargument of the genericcommandverb verbatim, to 120 bytes. A line such assettings set <module> '<value>' --node <node>through that verb therefore put the value itself into thecallsrecord, which answers anyone who may call the seat.What it does now
commandis kept the way a mesh-clilineis: its first word, with the rest said to have been given. Two bounds the issue did not ask for and I decided here, both narrow:builds,plans,conditions), because there is nothing after it to withhold and the record stays readable for the reading commands that make up most of its use.commandargument that is not a string is kept as(given, not kept), since its first word cannot be taken.Whether a real secret was kept
The report left this open; it is now checked. I read the whole answer of
mesh-controller.callsat 2026-10-10 22:52 UTC — 14850 lines — and looked in it for the keptcommandargument and for which verbs were called. The word "command" does not appear in it, and no call of thecommandverb is among them. So no setting's value is readable there as it stands. This says nothing about calls older than the record's window, which keeps only the newest.Checked here
s3cretverbatim from a--valuesline andlaptopandshowfrom anode show laptopline; it passes with the fix. I ran it both ways (git stashon calls.go alone).go test ./internal/link/ -count=1: ok.go vet ./...clean, andgofmt -lnames nothing outsidevendor/.make checkcannot run on this machine: itsfmtstep fails on three vendored third-party files that are not gofmt'd (antithesis-sdk-go, nats-server), which this change does not touch. I ran the rest of what it does instead —make postgresandgo test -race -timeout 15m ./...— and will say what that gave before asking for the merge.Delivery
novox/mesh-controller@15a9919df53e— delivered since 2026-10-10T23:36:17ZDelivery 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
1390836bmesh/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-1791672837439356752(builds --log build-1791672837439356752).Merge check at
15a9919dmesh/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 g14 as
build-1791673505305625892(builds --log build-1791673505305625892).