Part of hq ADR 0272 (proposed, hq PR #243) and issue 343: the controller's terminal has no command.
What.
internal/meshcli: the engine serves /run/nox-mesh-host/cli.sock (dir 0755, socket 0666) while it serves its link. Per connection it reads the peer's user id from the kernel (SO_PEERCRED), names the account from the user database, reads one request (bounded, 30 s), and asks the controller. A connection whose credentials cannot be read, an unknown uid, a bad or oversized request, and an unreachable controller are each answered as a refusal; nothing is ever sent as anyone. At most 8 lines at once.
The socket's directory must be a real directory owned by the engine's account (no link); a non-socket file at the socket path is kept and said, never removed.
link.CLISubject(node) = mesh.control.<node>.cli, inside the grant the engine already has; Queue.AskController asks it on core NATS over the link open now (never the CONTROL stream, which names its subjects).
Wired in runLink beside the other serving goroutines; stops when the engine stands aside (the listener unlinks the socket; the successor makes a fresh one).
ADR 0004. The socket has no network address and nothing sent to it acts on the machine; the engine runs nothing it receives. The comment that explains why rouse is a signal now says so.
ADR 0005. The engine imports one stdlib-only SDK package at build time; it is still one static binary with nothing installed first.
Tests (internal/meshcli): the account sent is the kernel's for the test process and the answer comes back; unreadable credentials are refused and never asked; an unreached controller is said; an oversized request is refused; a non-socket file is kept; the request's and answer's JSON field names (the controller's PR holds the same list). merge-check.sh passes locally (with a throwaway nats-server).
Dependency. Pins git.novox.be/novox/mesh-sdk/go at a pseudo-version of mesh-sdk PR feat/cli-local-protocol (bfe8231); move to go/v0.1.8 once that merges and is tagged.
Merge order. Second: mesh-sdk, this, mesh-controller, mesh-catalog. Either of this and the controller may land first: an engine whose controller does not answer yet says "the controller was not reached, nothing ran"; a controller whose engines do not ask yet answers nothing.
Do not merge before the operator accepts ADR 0272.
Part of hq ADR 0272 (proposed, hq PR #243) and issue 343: the controller's terminal has no command.
**What.**
- `internal/meshcli`: the engine serves `/run/nox-mesh-host/cli.sock` (dir 0755, socket 0666) while it serves its link. Per connection it reads the peer's user id from the kernel (`SO_PEERCRED`), names the account from the user database, reads one request (bounded, 30 s), and asks the controller. A connection whose credentials cannot be read, an unknown uid, a bad or oversized request, and an unreachable controller are each answered as a refusal; nothing is ever sent as anyone. At most 8 lines at once.
- The socket's directory must be a real directory owned by the engine's account (no link); a non-socket file at the socket path is kept and said, never removed.
- `link.CLISubject(node)` = `mesh.control.<node>.cli`, inside the grant the engine already has; `Queue.AskController` asks it on core NATS over the link open now (never the CONTROL stream, which names its subjects).
- Wired in `runLink` beside the other serving goroutines; stops when the engine stands aside (the listener unlinks the socket; the successor makes a fresh one).
**ADR 0004.** The socket has no network address and nothing sent to it acts on the machine; the engine runs nothing it receives. The comment that explains why `rouse` is a signal now says so.
**ADR 0005.** The engine imports one stdlib-only SDK package at build time; it is still one static binary with nothing installed first.
**Tests** (`internal/meshcli`): the account sent is the kernel's for the test process and the answer comes back; unreadable credentials are refused and never asked; an unreached controller is said; an oversized request is refused; a non-socket file is kept; the request's and answer's JSON field names (the controller's PR holds the same list). `merge-check.sh` passes locally (with a throwaway nats-server).
**Dependency.** Pins `git.novox.be/novox/mesh-sdk/go` at a pseudo-version of mesh-sdk PR `feat/cli-local-protocol` (bfe8231); move to `go/v0.1.8` once that merges and is tagged.
**Merge order.** Second: mesh-sdk, this, mesh-controller, mesh-catalog. Either of this and the controller may land first: an engine whose controller does not answer yet says "the controller was not reached, nothing ran"; a controller whose engines do not ask yet answers nothing.
Do not merge before the operator accepts ADR 0272.
mesh/merge-gate pass: builds mesh-host → ace, g14, novox, shanks; no bus step; every machine composes with the change as it did without (4 of 4 compose)
The records send the operator to "the controller's terminal", and nothing
reaches it (hq issue 343). mesh-cli holds no credential: it asks the engine
on its own machine over a socket. The engine reads the asking account from
the kernel (SO_PEERCRED), never from the program, and asks the controller on
mesh.control.<node>.cli, its own node's subject, so the bus server says which
node asked. The controller decides what the line may do; nothing received
on the socket is run or applied here, and the socket has no network address
(ADR 0004 stands).
The local protocol is the SDK's go/cli package, at a pseudo-version of its
branch until that merges and is tagged go/v0.1.8.
Deliverynovox/mesh-host@f684967c3be6 — delivered since 2026-10-09T11:44:51Z
Delivery plan — builds mesh-host → ace, g14, novox, shanks; no bus step
tier 0: mesh-host
ace: receives mesh-host
g14: receives mesh-host
novox: receives mesh-host
shanks: receives mesh-host
Machines
mesh-host on ace: passed — healthy 3 times over 2m26s
mesh-host on novox: judging — carried by release-1791546146134868956
mesh-host on the rest running it: sent
Transitions
2026-10-09 11:10 (new) → proposed (announced): novox/mesh-host#69's head announced
2026-10-09 11:12 proposed → checked (checked): the verdict names this commit
2026-10-09 11:12 checked → ready (accepted): the gate passed or warned, and the repository's own check did not fail
2026-10-09 11:39 ready → published (merged): on the trunk its modules follow: merged there, and its walk opened — or nothing for a walk to move
2026-10-09 11:39 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
2026-10-09 11:44 delivering → delivered (done): its walk is done: every machine of its deploy plan passed, or was left as its policy says
The commit's note under refs/notes/mesh-plan keeps every transition: git log --notes=mesh-plan.
<!-- mesh-delivery:view -->
**Delivery** `novox/mesh-host@f684967c3be6` — **delivered** since 2026-10-09T11:44:51Z
**Delivery plan** — builds mesh-host → ace, g14, novox, shanks; no bus step
- tier 0: mesh-host
- ace: receives mesh-host
- g14: receives mesh-host
- novox: receives mesh-host
- shanks: receives mesh-host
**Machines**
- mesh-host on ace: passed — healthy 3 times over 2m26s
- mesh-host on novox: judging — carried by release-1791546146134868956
- mesh-host on the rest running it: sent
**Transitions**
- 2026-10-09 11:10 (new) → proposed (announced): novox/mesh-host#69's head announced
- 2026-10-09 11:12 proposed → checked (checked): the verdict names this commit
- 2026-10-09 11:12 checked → ready (accepted): the gate passed or warned, and the repository's own check did not fail
- 2026-10-09 11:39 ready → published (merged): on the trunk its modules follow: merged there, and its walk opened — or nothing for a walk to move
- 2026-10-09 11:39 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
- 2026-10-09 11:44 delivering → delivered (done): its walk is done: every machine of its deploy plan passed, or was left as its policy says
The commit's note under `refs/notes/mesh-plan` keeps every transition: `git log --notes=mesh-plan`.
mesh/merge-gate: PASS — every machine composes with the change as it did without (4 of 4 compose) (modules: mesh-host)
mesh/repo-check: PASS — its merge-check.sh passed
Delivery plan — builds mesh-host → ace, g14, novox, shanks; no bus step
tier 0: mesh-host
ace: receives mesh-host
g14: receives mesh-host
novox: receives mesh-host
shanks: receives mesh-host
Run by the build seat on ace as build-1791540739129727907 (builds --log build-1791540739129727907).
--- the gate: mesh-host
mesh-host: ok
long-running resources without health: 0
files asking for a setting without saying whether it is trusted: 0
1 manifest(s) checked. Judged against the seats this binary carries; a claim on one of the mesh's own seats is judged fully at registration, and a seat declared by a module not given here reads as unknown. Identities judged on a 6-character machine name, against the bounds of the providers given here
judging 0 module(s) changed against 4 machine(s), as the snapshot of 2026-10-09T08:07:39Z says they run
composing every machine as the mesh is
the bus's user list leaves out 5 user(s) the mesh has minted no credential for: controller, node.f35, node.idt, node.ygcyr, node.yvbpsm. Each is a user that cannot connect until one is issued
the bus's user list leaves out 5 user(s) the mesh has minted no credential for: controller, node.f35, node.idt, node.ygcyr, node.yvbpsm. Each is a user that cannot connect until one is issued
composing every machine with the change
the bus's user list leaves out 5 user(s) the mesh has minted no credential for: controller, node.f35, node.idt, node.ygcyr, node.yvbpsm. Each is a user that cannot connect until one is issued
the bus's user list leaves out 5 user(s) the mesh has minted no credential for: controller, node.f35, node.idt, node.ygcyr, node.yvbpsm. Each is a user that cannot connect until one is issued
merge gate: PASS — every machine composes with the change as it did without (4 of 4 compose)
judged by controller development build against the facts of 2026-10-09T08:07:39Z
machines:
- a machine (f35): composes
- holds mesh-dns-resolver (idt): composes
- holds git, holds mesh-artifact-store, holds mesh-broker, holds mesh-catalog, holds mesh-delivery, holds mesh-dns-resolver, holds mesh-store, holds mesh-vault, holds npm-package-registry, the control node, the hub (ygcyr): composes
- a machine (yvbpsm): composes
a merge would rebuild 1 module(s) in 1 tier(s): mesh-host
--- its merge-check.sh (go toolchain)
go: downloading git.novox.be/novox/mesh-sdk/go v0.1.8-0.20261009100314-bfe82315f42c
ok github.com/novox/mesh-host/cmd/mesh-bootstrap 1.013s
ok github.com/novox/mesh-host/cmd/mesh-host 5.349s
ok github.com/novox/mesh-host/examples 1.016s
ok github.com/novox/mesh-host/internal/accounts 1.013s
ok github.com/novox/mesh-host/internal/apply 4.453s
ok github.com/novox/mesh-host/internal/bootstrap 1.515s
ok github.com/novox/mesh-host/internal/bundle 1.030s
ok github.com/novox/mesh-host/internal/declaration 1.066s
ok github.com/novox/mesh-host/internal/firewall 1.668s
ok github.com/novox/mesh-host/internal/identity 1.105s
ok github.com/novox/mesh-host/internal/image 1.030s
ok github.com/novox/mesh-host/internal/inventory 1.034s
ok github.com/novox/mesh-host/internal/link 10.335s
ok github.com/novox/mesh-host/internal/liveness 2.184s
ok github.com/novox/mesh-host/internal/meshcli 1.062s
ok github.com/novox/mesh-host/internal/network 1.050s
ok github.com/novox/mesh-host/internal/outward 1.040s
ok github.com/novox/mesh-host/internal/profile 1.513s
ok github.com/novox/mesh-host/internal/reachable 1.038s
ok github.com/novox/mesh-host/internal/store 1.221s
ok github.com/novox/mesh-host/internal/system 1.038s
ok github.com/novox/mesh-host/internal/tunnel 1.044s
ok github.com/novox/mesh-host/internal/units 1.037s
ok github.com/novox/mesh-host/internal/upgrade 1.150s
ok github.com/novox/mesh-host/internal/witness 4.556s
ok github.com/novox/mesh-host/packaging 1.050s
ok github.com/novox/mesh-host/validate 1.049s
**Merge check** at `021d860c`
- `mesh/merge-gate`: **PASS** — every machine composes with the change as it did without (4 of 4 compose) (modules: mesh-host)
- `mesh/repo-check`: **PASS** — its merge-check.sh passed
**Delivery plan** — builds mesh-host → ace, g14, novox, shanks; no bus step
- tier 0: mesh-host
- ace: receives mesh-host
- g14: receives mesh-host
- novox: receives mesh-host
- shanks: receives mesh-host
Run by the build seat on ace as `build-1791540739129727907` (`builds --log build-1791540739129727907`).
```
--- the gate: mesh-host
mesh-host: ok
long-running resources without health: 0
files asking for a setting without saying whether it is trusted: 0
1 manifest(s) checked. Judged against the seats this binary carries; a claim on one of the mesh's own seats is judged fully at registration, and a seat declared by a module not given here reads as unknown. Identities judged on a 6-character machine name, against the bounds of the providers given here
judging 0 module(s) changed against 4 machine(s), as the snapshot of 2026-10-09T08:07:39Z says they run
composing every machine as the mesh is
the bus's user list leaves out 5 user(s) the mesh has minted no credential for: controller, node.f35, node.idt, node.ygcyr, node.yvbpsm. Each is a user that cannot connect until one is issued
the bus's user list leaves out 5 user(s) the mesh has minted no credential for: controller, node.f35, node.idt, node.ygcyr, node.yvbpsm. Each is a user that cannot connect until one is issued
composing every machine with the change
the bus's user list leaves out 5 user(s) the mesh has minted no credential for: controller, node.f35, node.idt, node.ygcyr, node.yvbpsm. Each is a user that cannot connect until one is issued
the bus's user list leaves out 5 user(s) the mesh has minted no credential for: controller, node.f35, node.idt, node.ygcyr, node.yvbpsm. Each is a user that cannot connect until one is issued
merge gate: PASS — every machine composes with the change as it did without (4 of 4 compose)
judged by controller development build against the facts of 2026-10-09T08:07:39Z
machines:
- a machine (f35): composes
- holds mesh-dns-resolver (idt): composes
- holds git, holds mesh-artifact-store, holds mesh-broker, holds mesh-catalog, holds mesh-delivery, holds mesh-dns-resolver, holds mesh-store, holds mesh-vault, holds npm-package-registry, the control node, the hub (ygcyr): composes
- a machine (yvbpsm): composes
a merge would rebuild 1 module(s) in 1 tier(s): mesh-host
--- its merge-check.sh (go toolchain)
go: downloading git.novox.be/novox/mesh-sdk/go v0.1.8-0.20261009100314-bfe82315f42c
ok github.com/novox/mesh-host/cmd/mesh-bootstrap 1.013s
ok github.com/novox/mesh-host/cmd/mesh-host 5.349s
ok github.com/novox/mesh-host/examples 1.016s
ok github.com/novox/mesh-host/internal/accounts 1.013s
ok github.com/novox/mesh-host/internal/apply 4.453s
ok github.com/novox/mesh-host/internal/bootstrap 1.515s
ok github.com/novox/mesh-host/internal/bundle 1.030s
ok github.com/novox/mesh-host/internal/declaration 1.066s
ok github.com/novox/mesh-host/internal/firewall 1.668s
ok github.com/novox/mesh-host/internal/identity 1.105s
ok github.com/novox/mesh-host/internal/image 1.030s
ok github.com/novox/mesh-host/internal/inventory 1.034s
ok github.com/novox/mesh-host/internal/link 10.335s
ok github.com/novox/mesh-host/internal/liveness 2.184s
ok github.com/novox/mesh-host/internal/meshcli 1.062s
ok github.com/novox/mesh-host/internal/network 1.050s
ok github.com/novox/mesh-host/internal/outward 1.040s
ok github.com/novox/mesh-host/internal/profile 1.513s
ok github.com/novox/mesh-host/internal/reachable 1.038s
ok github.com/novox/mesh-host/internal/store 1.221s
ok github.com/novox/mesh-host/internal/system 1.038s
ok github.com/novox/mesh-host/internal/tunnel 1.044s
ok github.com/novox/mesh-host/internal/units 1.037s
ok github.com/novox/mesh-host/internal/upgrade 1.150s
ok github.com/novox/mesh-host/internal/witness 4.556s
ok github.com/novox/mesh-host/packaging 1.050s
ok github.com/novox/mesh-host/validate 1.049s
```
mesh/merge-gate pass: builds mesh-host → ace, g14, novox, shanks; no bus step; every machine composes with the change as it did without (4 of 4 compose)
- A request that timed out was said as "the controller was not reached,
nothing ran", though the line may have run. The engine now follows a line
the controller answers as running, by its call, until it ends; when no
answer comes in time it says the line may have run and names the call.
"Nothing ran" is said only of a request no controller took.
- One account could hold the socket: accepting waited for a free slot, and
a connection could stall before its deadline was set. The deadline is set
at accept, before any lookup; each user id has two lines at once and the
machine eight, and one over is answered busy at once.
- A container running with the operator's user id shares the number, not
the machine: a peer whose mount or user namespace is not the engine's is
refused, and nothing is asked.
SDK pinned at the go/cli branch's newest commit until go/v0.1.9 is tagged.
mesh/merge-gate: PASS — every machine composes with the change as it did without (4 of 4 compose) (modules: mesh-host)
mesh/repo-check: PASS — its merge-check.sh passed
Delivery plan — builds mesh-host → ace, g14, novox, shanks; no bus step
tier 0: mesh-host
ace: receives mesh-host
g14: receives mesh-host
novox: receives mesh-host
shanks: receives mesh-host
Run by the build seat on ace as build-1791542935994283341 (builds --log build-1791542935994283341).
--- the gate: mesh-host
mesh-host: ok
long-running resources without health: 0
files asking for a setting without saying whether it is trusted: 0
1 manifest(s) checked. Judged against the seats this binary carries; a claim on one of the mesh's own seats is judged fully at registration, and a seat declared by a module not given here reads as unknown. Identities judged on a 6-character machine name, against the bounds of the providers given here
judging 0 module(s) changed against 4 machine(s), as the snapshot of 2026-10-09T08:07:39Z says they run
composing every machine as the mesh is
the bus's user list leaves out 5 user(s) the mesh has minted no credential for: controller, node.f35, node.idt, node.ygcyr, node.yvbpsm. Each is a user that cannot connect until one is issued
the bus's user list leaves out 5 user(s) the mesh has minted no credential for: controller, node.f35, node.idt, node.ygcyr, node.yvbpsm. Each is a user that cannot connect until one is issued
composing every machine with the change
the bus's user list leaves out 5 user(s) the mesh has minted no credential for: controller, node.f35, node.idt, node.ygcyr, node.yvbpsm. Each is a user that cannot connect until one is issued
the bus's user list leaves out 5 user(s) the mesh has minted no credential for: controller, node.f35, node.idt, node.ygcyr, node.yvbpsm. Each is a user that cannot connect until one is issued
merge gate: PASS — every machine composes with the change as it did without (4 of 4 compose)
judged by controller development build against the facts of 2026-10-09T08:07:39Z
machines:
- a machine (f35): composes
- holds mesh-dns-resolver (idt): composes
- holds git, holds mesh-artifact-store, holds mesh-broker, holds mesh-catalog, holds mesh-delivery, holds mesh-dns-resolver, holds mesh-store, holds mesh-vault, holds npm-package-registry, the control node, the hub (ygcyr): composes
- a machine (yvbpsm): composes
a merge would rebuild 1 module(s) in 1 tier(s): mesh-host
--- its merge-check.sh (go toolchain)
go: downloading git.novox.be/novox/mesh-sdk/go v0.1.8-0.20261009103748-a5a040c9049b
ok github.com/novox/mesh-host/cmd/mesh-bootstrap 1.013s
ok github.com/novox/mesh-host/cmd/mesh-host 5.371s
ok github.com/novox/mesh-host/examples 1.036s
ok github.com/novox/mesh-host/internal/accounts 1.039s
ok github.com/novox/mesh-host/internal/apply 4.305s
ok github.com/novox/mesh-host/internal/bootstrap 1.484s
ok github.com/novox/mesh-host/internal/bundle 1.034s
ok github.com/novox/mesh-host/internal/declaration 1.058s
ok github.com/novox/mesh-host/internal/firewall 1.660s
ok github.com/novox/mesh-host/internal/identity 1.109s
ok github.com/novox/mesh-host/internal/image 1.032s
ok github.com/novox/mesh-host/internal/inventory 1.033s
ok github.com/novox/mesh-host/internal/link 10.318s
ok github.com/novox/mesh-host/internal/liveness 2.076s
ok github.com/novox/mesh-host/internal/meshcli 1.117s
ok github.com/novox/mesh-host/internal/network 1.047s
ok github.com/novox/mesh-host/internal/outward 1.041s
ok github.com/novox/mesh-host/internal/profile 1.506s
ok github.com/novox/mesh-host/internal/reachable 1.034s
ok github.com/novox/mesh-host/internal/store 1.204s
ok github.com/novox/mesh-host/internal/system 1.035s
ok github.com/novox/mesh-host/internal/tunnel 1.040s
ok github.com/novox/mesh-host/internal/units 1.048s
ok github.com/novox/mesh-host/internal/upgrade 1.138s
ok github.com/novox/mesh-host/internal/witness 4.243s
ok github.com/novox/mesh-host/packaging 1.012s
ok github.com/novox/mesh-host/validate 1.011s
**Merge check** at `564948c2`
- `mesh/merge-gate`: **PASS** — every machine composes with the change as it did without (4 of 4 compose) (modules: mesh-host)
- `mesh/repo-check`: **PASS** — its merge-check.sh passed
**Delivery plan** — builds mesh-host → ace, g14, novox, shanks; no bus step
- tier 0: mesh-host
- ace: receives mesh-host
- g14: receives mesh-host
- novox: receives mesh-host
- shanks: receives mesh-host
Run by the build seat on ace as `build-1791542935994283341` (`builds --log build-1791542935994283341`).
```
--- the gate: mesh-host
mesh-host: ok
long-running resources without health: 0
files asking for a setting without saying whether it is trusted: 0
1 manifest(s) checked. Judged against the seats this binary carries; a claim on one of the mesh's own seats is judged fully at registration, and a seat declared by a module not given here reads as unknown. Identities judged on a 6-character machine name, against the bounds of the providers given here
judging 0 module(s) changed against 4 machine(s), as the snapshot of 2026-10-09T08:07:39Z says they run
composing every machine as the mesh is
the bus's user list leaves out 5 user(s) the mesh has minted no credential for: controller, node.f35, node.idt, node.ygcyr, node.yvbpsm. Each is a user that cannot connect until one is issued
the bus's user list leaves out 5 user(s) the mesh has minted no credential for: controller, node.f35, node.idt, node.ygcyr, node.yvbpsm. Each is a user that cannot connect until one is issued
composing every machine with the change
the bus's user list leaves out 5 user(s) the mesh has minted no credential for: controller, node.f35, node.idt, node.ygcyr, node.yvbpsm. Each is a user that cannot connect until one is issued
the bus's user list leaves out 5 user(s) the mesh has minted no credential for: controller, node.f35, node.idt, node.ygcyr, node.yvbpsm. Each is a user that cannot connect until one is issued
merge gate: PASS — every machine composes with the change as it did without (4 of 4 compose)
judged by controller development build against the facts of 2026-10-09T08:07:39Z
machines:
- a machine (f35): composes
- holds mesh-dns-resolver (idt): composes
- holds git, holds mesh-artifact-store, holds mesh-broker, holds mesh-catalog, holds mesh-delivery, holds mesh-dns-resolver, holds mesh-store, holds mesh-vault, holds npm-package-registry, the control node, the hub (ygcyr): composes
- a machine (yvbpsm): composes
a merge would rebuild 1 module(s) in 1 tier(s): mesh-host
--- its merge-check.sh (go toolchain)
go: downloading git.novox.be/novox/mesh-sdk/go v0.1.8-0.20261009103748-a5a040c9049b
ok github.com/novox/mesh-host/cmd/mesh-bootstrap 1.013s
ok github.com/novox/mesh-host/cmd/mesh-host 5.371s
ok github.com/novox/mesh-host/examples 1.036s
ok github.com/novox/mesh-host/internal/accounts 1.039s
ok github.com/novox/mesh-host/internal/apply 4.305s
ok github.com/novox/mesh-host/internal/bootstrap 1.484s
ok github.com/novox/mesh-host/internal/bundle 1.034s
ok github.com/novox/mesh-host/internal/declaration 1.058s
ok github.com/novox/mesh-host/internal/firewall 1.660s
ok github.com/novox/mesh-host/internal/identity 1.109s
ok github.com/novox/mesh-host/internal/image 1.032s
ok github.com/novox/mesh-host/internal/inventory 1.033s
ok github.com/novox/mesh-host/internal/link 10.318s
ok github.com/novox/mesh-host/internal/liveness 2.076s
ok github.com/novox/mesh-host/internal/meshcli 1.117s
ok github.com/novox/mesh-host/internal/network 1.047s
ok github.com/novox/mesh-host/internal/outward 1.041s
ok github.com/novox/mesh-host/internal/profile 1.506s
ok github.com/novox/mesh-host/internal/reachable 1.034s
ok github.com/novox/mesh-host/internal/store 1.204s
ok github.com/novox/mesh-host/internal/system 1.035s
ok github.com/novox/mesh-host/internal/tunnel 1.040s
ok github.com/novox/mesh-host/internal/units 1.048s
ok github.com/novox/mesh-host/internal/upgrade 1.138s
ok github.com/novox/mesh-host/internal/witness 4.243s
ok github.com/novox/mesh-host/packaging 1.012s
ok github.com/novox/mesh-host/validate 1.011s
```
mesh/merge-gate pass: builds mesh-host → ace, g14, novox, shanks; no bus step; every machine composes with the change as it did without (4 of 4 compose)
- Any failure of a request the link may have delivered now says the line
may have run; "nothing ran" is said only of a request the link knows it
never asked (no link open, nobody listening: link.ErrNotAsked).
- A test holds that a connection saying nothing is answered within its
deadline, set at accept, and gives its slot back.
- The README says the socket refuses a process outside the machine's own
namespaces, so flatpak, toolbox and distrobox shells are refused.
mesh/merge-gate: PASS — every machine composes with the change as it did without (4 of 4 compose) (modules: mesh-host)
mesh/repo-check: PASS — its merge-check.sh passed
Delivery plan — builds mesh-host → ace, g14, novox, shanks; no bus step
tier 0: mesh-host
ace: receives mesh-host
g14: receives mesh-host
novox: receives mesh-host
shanks: receives mesh-host
Run by the build seat on ace as build-1791544244372479958 (builds --log build-1791544244372479958).
--- the gate: mesh-host
mesh-host: ok
long-running resources without health: 0
files asking for a setting without saying whether it is trusted: 0
1 manifest(s) checked. Judged against the seats this binary carries; a claim on one of the mesh's own seats is judged fully at registration, and a seat declared by a module not given here reads as unknown. Identities judged on a 6-character machine name, against the bounds of the providers given here
judging 0 module(s) changed against 4 machine(s), as the snapshot of 2026-10-09T11:09:37Z 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-09T11:09:37Z
machines:
- a machine (f35): composes
- holds mesh-dns-resolver (idt): composes
- holds git, holds mesh-artifact-store, holds mesh-broker, holds mesh-catalog, holds mesh-delivery, holds mesh-dns-resolver, holds mesh-store, holds mesh-vault, holds npm-package-registry, the control node, the hub (ygcyr): composes
- a machine (yvbpsm): composes
a merge would rebuild 1 module(s) in 1 tier(s): mesh-host
--- its merge-check.sh (go toolchain)
ok github.com/novox/mesh-host/cmd/mesh-bootstrap 1.012s
ok github.com/novox/mesh-host/cmd/mesh-host 5.360s
ok github.com/novox/mesh-host/examples 1.017s
ok github.com/novox/mesh-host/internal/accounts 1.020s
ok github.com/novox/mesh-host/internal/apply 4.426s
ok github.com/novox/mesh-host/internal/bootstrap 1.494s
ok github.com/novox/mesh-host/internal/bundle 1.014s
ok github.com/novox/mesh-host/internal/declaration 1.048s
ok github.com/novox/mesh-host/internal/firewall 1.650s
ok github.com/novox/mesh-host/internal/identity 1.159s
ok github.com/novox/mesh-host/internal/image 1.014s
ok github.com/novox/mesh-host/internal/inventory 1.077s
ok github.com/novox/mesh-host/internal/link 10.357s
ok github.com/novox/mesh-host/internal/liveness 2.119s
ok github.com/novox/mesh-host/internal/meshcli 1.371s
ok github.com/novox/mesh-host/internal/network 1.097s
ok github.com/novox/mesh-host/internal/outward 1.088s
ok github.com/novox/mesh-host/internal/profile 1.501s
ok github.com/novox/mesh-host/internal/reachable 1.034s
ok github.com/novox/mesh-host/internal/store 1.207s
ok github.com/novox/mesh-host/internal/system 1.033s
ok github.com/novox/mesh-host/internal/tunnel 1.032s
ok github.com/novox/mesh-host/internal/units 1.023s
ok github.com/novox/mesh-host/internal/upgrade 1.138s
ok github.com/novox/mesh-host/internal/witness 4.482s
ok github.com/novox/mesh-host/packaging 1.027s
? github.com/novox/mesh-host/rootsearch [no test files]
ok github.com/novox/mesh-host/validate 1.029s
**Merge check** at `f684967c`
- `mesh/merge-gate`: **PASS** — every machine composes with the change as it did without (4 of 4 compose) (modules: mesh-host)
- `mesh/repo-check`: **PASS** — its merge-check.sh passed
**Delivery plan** — builds mesh-host → ace, g14, novox, shanks; no bus step
- tier 0: mesh-host
- ace: receives mesh-host
- g14: receives mesh-host
- novox: receives mesh-host
- shanks: receives mesh-host
Run by the build seat on ace as `build-1791544244372479958` (`builds --log build-1791544244372479958`).
```
--- the gate: mesh-host
mesh-host: ok
long-running resources without health: 0
files asking for a setting without saying whether it is trusted: 0
1 manifest(s) checked. Judged against the seats this binary carries; a claim on one of the mesh's own seats is judged fully at registration, and a seat declared by a module not given here reads as unknown. Identities judged on a 6-character machine name, against the bounds of the providers given here
judging 0 module(s) changed against 4 machine(s), as the snapshot of 2026-10-09T11:09:37Z 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-09T11:09:37Z
machines:
- a machine (f35): composes
- holds mesh-dns-resolver (idt): composes
- holds git, holds mesh-artifact-store, holds mesh-broker, holds mesh-catalog, holds mesh-delivery, holds mesh-dns-resolver, holds mesh-store, holds mesh-vault, holds npm-package-registry, the control node, the hub (ygcyr): composes
- a machine (yvbpsm): composes
a merge would rebuild 1 module(s) in 1 tier(s): mesh-host
--- its merge-check.sh (go toolchain)
ok github.com/novox/mesh-host/cmd/mesh-bootstrap 1.012s
ok github.com/novox/mesh-host/cmd/mesh-host 5.360s
ok github.com/novox/mesh-host/examples 1.017s
ok github.com/novox/mesh-host/internal/accounts 1.020s
ok github.com/novox/mesh-host/internal/apply 4.426s
ok github.com/novox/mesh-host/internal/bootstrap 1.494s
ok github.com/novox/mesh-host/internal/bundle 1.014s
ok github.com/novox/mesh-host/internal/declaration 1.048s
ok github.com/novox/mesh-host/internal/firewall 1.650s
ok github.com/novox/mesh-host/internal/identity 1.159s
ok github.com/novox/mesh-host/internal/image 1.014s
ok github.com/novox/mesh-host/internal/inventory 1.077s
ok github.com/novox/mesh-host/internal/link 10.357s
ok github.com/novox/mesh-host/internal/liveness 2.119s
ok github.com/novox/mesh-host/internal/meshcli 1.371s
ok github.com/novox/mesh-host/internal/network 1.097s
ok github.com/novox/mesh-host/internal/outward 1.088s
ok github.com/novox/mesh-host/internal/profile 1.501s
ok github.com/novox/mesh-host/internal/reachable 1.034s
ok github.com/novox/mesh-host/internal/store 1.207s
ok github.com/novox/mesh-host/internal/system 1.033s
ok github.com/novox/mesh-host/internal/tunnel 1.032s
ok github.com/novox/mesh-host/internal/units 1.023s
ok github.com/novox/mesh-host/internal/upgrade 1.138s
ok github.com/novox/mesh-host/internal/witness 4.482s
ok github.com/novox/mesh-host/packaging 1.027s
? github.com/novox/mesh-host/rootsearch [no test files]
ok github.com/novox/mesh-host/validate 1.029s
```
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.
Part of hq ADR 0272 (proposed, hq PR #243) and issue 343: the controller's terminal has no command.
What.
internal/meshcli: the engine serves/run/nox-mesh-host/cli.sock(dir 0755, socket 0666) while it serves its link. Per connection it reads the peer's user id from the kernel (SO_PEERCRED), names the account from the user database, reads one request (bounded, 30 s), and asks the controller. A connection whose credentials cannot be read, an unknown uid, a bad or oversized request, and an unreachable controller are each answered as a refusal; nothing is ever sent as anyone. At most 8 lines at once.link.CLISubject(node)=mesh.control.<node>.cli, inside the grant the engine already has;Queue.AskControllerasks it on core NATS over the link open now (never the CONTROL stream, which names its subjects).runLinkbeside the other serving goroutines; stops when the engine stands aside (the listener unlinks the socket; the successor makes a fresh one).ADR 0004. The socket has no network address and nothing sent to it acts on the machine; the engine runs nothing it receives. The comment that explains why
rouseis a signal now says so.ADR 0005. The engine imports one stdlib-only SDK package at build time; it is still one static binary with nothing installed first.
Tests (
internal/meshcli): the account sent is the kernel's for the test process and the answer comes back; unreadable credentials are refused and never asked; an unreached controller is said; an oversized request is refused; a non-socket file is kept; the request's and answer's JSON field names (the controller's PR holds the same list).merge-check.shpasses locally (with a throwaway nats-server).Dependency. Pins
git.novox.be/novox/mesh-sdk/goat a pseudo-version of mesh-sdk PRfeat/cli-local-protocol(bfe8231); move togo/v0.1.8once that merges and is tagged.Merge order. Second: mesh-sdk, this, mesh-controller, mesh-catalog. Either of this and the controller may land first: an engine whose controller does not answer yet says "the controller was not reached, nothing ran"; a controller whose engines do not ask yet answers nothing.
Do not merge before the operator accepts ADR 0272.
Delivery
novox/mesh-host@f684967c3be6— delivered since 2026-10-09T11:44:51ZDelivery plan — builds mesh-host → ace, g14, novox, shanks; no bus step
Machines
Transitions
The commit's note under
refs/notes/mesh-plankeeps every transition:git log --notes=mesh-plan.Merge check at
021d860cmesh/merge-gate: PASS — every machine composes with the change as it did without (4 of 4 compose) (modules: mesh-host)mesh/repo-check: PASS — its merge-check.sh passedDelivery plan — builds mesh-host → ace, g14, novox, shanks; no bus step
Run by the build seat on ace as
build-1791540739129727907(builds --log build-1791540739129727907).Merge check at
564948c2mesh/merge-gate: PASS — every machine composes with the change as it did without (4 of 4 compose) (modules: mesh-host)mesh/repo-check: PASS — its merge-check.sh passedDelivery plan — builds mesh-host → ace, g14, novox, shanks; no bus step
Run by the build seat on ace as
build-1791542935994283341(builds --log build-1791542935994283341).Merge check at
f684967cmesh/merge-gate: PASS — every machine composes with the change as it did without (4 of 4 compose) (modules: mesh-host)mesh/repo-check: PASS — its merge-check.sh passedDelivery plan — builds mesh-host → ace, g14, novox, shanks; no bus step
Run by the build seat on ace as
build-1791544244372479958(builds --log build-1791544244372479958).