mesh-cli: the operator's command on every node, nox in zsh (hq ADR 0272) #156

Merged
mesh-admin merged 3 commits from feat/272-mesh-cli into main 2026-10-09 11:38:44 +00:00
Contributor

Part of hq ADR 0272 (proposed, hq PR #243) and issue 343.

What.

  • New module modules/mesh-cli, built from its own directory (ADR 0267): one Go bundle program (binary mesh-cli), unpacked by an archive resource into /usr/local/bin, so the program is /usr/local/bin/mesh-cli. One file, no link, no copy; the node-engine refuses to write over a file it did not place and removes only that file when the module goes.
  • Its shell contribution, zsh normal slot: alias nox=mesh-cli (interactive zsh only; scripts, sudo and docs say mesh-cli). No environment contribution: /usr/local/bin is on PATH already.
  • The program holds no credential: it writes one request to the engine's socket (SDK go/cli) and prints the controller's answer, says why a line was not the terminal or was refused, says a cut, exits with the command's status. A process carrying MESH_VERB is refused before asking. Interrupting stops the wait, not the command.
  • The agent module's refusals (AtTheTerminal, the shared-text and tool-server refusals) and README, and the route adapter's README, now say mesh-cli settings set … on the control-node instead of a mesh-controller command nobody could type. A settings file is passed inline ("$(cat settings.json)"), since a path would be read where the controller runs.

Checks. merge-check.sh passes locally with a controller from mesh-controller PR feat/272-answer-mesh-cli as MESH_GATE (mesh-cli: ok, health count 70 as kept) and MESH_CHECK_MODULES=mesh-cli,claude-code,route-adapter: words, paths, claude-code and mesh-cli tests.

After merge (operator's acts, not in this PR). Assign mesh-cli to every node (mesh-controller.assign). The command then works on the control-node once mesh-host and mesh-controller are live.

Dependency. Pins mesh-sdk/go at a pseudo-version of mesh-sdk feat/cli-local-protocol (bfe8231); move to go/v0.1.8 once tagged.

Merge order. Last: mesh-sdk, mesh-host, mesh-controller, this.

Do not merge before the operator accepts ADR 0272.

Part of hq ADR 0272 (proposed, hq PR #243) and issue 343. **What.** - New module `modules/mesh-cli`, built from its own directory (ADR 0267): one Go bundle `program` (binary `mesh-cli`), unpacked by an `archive` resource into `/usr/local/bin`, so the program is `/usr/local/bin/mesh-cli`. One file, no link, no copy; the node-engine refuses to write over a file it did not place and removes only that file when the module goes. - Its `shell` contribution, zsh `normal` slot: `alias nox=mesh-cli` (interactive zsh only; scripts, sudo and docs say `mesh-cli`). No environment contribution: `/usr/local/bin` is on PATH already. - The program holds no credential: it writes one request to the engine's socket (SDK `go/cli`) and prints the controller's answer, says why a line was not the terminal or was refused, says a cut, exits with the command's status. A process carrying `MESH_VERB` is refused before asking. Interrupting stops the wait, not the command. - The agent module's refusals (`AtTheTerminal`, the shared-text and tool-server refusals) and README, and the route adapter's README, now say `mesh-cli settings set …` on the control-node instead of a `mesh-controller` command nobody could type. A settings file is passed inline (`"$(cat settings.json)"`), since a path would be read where the controller runs. **Checks.** `merge-check.sh` passes locally with a controller from mesh-controller PR `feat/272-answer-mesh-cli` as `MESH_GATE` (`mesh-cli: ok`, health count 70 as kept) and `MESH_CHECK_MODULES=mesh-cli,claude-code,route-adapter`: words, paths, claude-code and mesh-cli tests. **After merge (operator's acts, not in this PR).** Assign `mesh-cli` to every node (`mesh-controller.assign`). The command then works on the control-node once mesh-host and mesh-controller are live. **Dependency.** Pins mesh-sdk/go at a pseudo-version of mesh-sdk `feat/cli-local-protocol` (bfe8231); move to `go/v0.1.8` once tagged. **Merge order.** Last: mesh-sdk, mesh-host, mesh-controller, this. Do not merge before the operator accepts ADR 0272.
mesh-admin added 1 commit 2026-10-09 10:12:15 +00:00
mesh-cli: the operator's command on every node, nox in zsh (hq ADR 0272)
mesh/merge-gate pass: builds claude-code, mounts, route-adapter, new: modules/mesh-cli → ace, g14, novox, shanks; no bus step; every machine composes with …
mesh/repo-check pass: its merge-check.sh passed, each part in its toolchain: merge-check.sh (go), merge-check-typescript.sh (typescript)
mesh/delivery superseded: a newer head of the same pull request
2594a24b35
The records send the operator to "the controller's terminal", and on the
control-node nothing answered (hq issue 343). mesh-cli is a module of its
own, assigned to every node and built from its own directory: its program
is unpacked into /usr/local/bin by an archive resource (one file, no link,
no copy), and its zsh contribution makes nox its alias. It holds no
credential: it asks the node-engine on its machine over the SDK's go/cli
socket, and prints the controller's answer with its exit.

The agent module's refusals and README, and the route adapter's README, now
name `mesh-cli settings set …` on the control-node instead of a
mesh-controller command nobody could type; a settings file is passed inline,
since a path would be read where the controller runs.
Author
Contributor

Delivery novox/mesh-catalog@6f1c559d9375 — delivered since 2026-10-09T11:44:13Z

Delivery plan — builds claude-code, route-adapter, new: modules/mesh-cli → ace, g14, novox, shanks; no bus step

  • tier 0: claude-code, route-adapter
  • ace: receives claude-code
  • g14: receives claude-code
  • novox: receives claude-code
  • shanks: receives claude-code
  • claude-code keeps data (ADR 0233): what it holds is backed up before it moves

Machines

  • betterbird on every machine running it: sent
  • claude-code on ace: passed — healthy 3 times over 2m46s
  • route-adapter on every machine running it: sent
  • claude-code on the rest running it: sent

Transitions

  • 2026-10-09 10:49 (new) → proposed (announced): novox/mesh-catalog#156's head announced
  • 2026-10-09 10:52 proposed → checked (checked): the verdict names this commit
  • 2026-10-09 10:52 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-catalog@6f1c559d9375` — **delivered** since 2026-10-09T11:44:13Z **Delivery plan** — builds claude-code, route-adapter, new: modules/mesh-cli → ace, g14, novox, shanks; no bus step - tier 0: claude-code, route-adapter - ace: receives claude-code - g14: receives claude-code - novox: receives claude-code - shanks: receives claude-code - claude-code keeps data (ADR 0233): what it holds is backed up before it moves **Machines** - betterbird on every machine running it: sent - claude-code on ace: passed — healthy 3 times over 2m46s - route-adapter on every machine running it: sent - claude-code on the rest running it: sent **Transitions** - 2026-10-09 10:49 (new) → proposed (announced): novox/mesh-catalog#156's head announced - 2026-10-09 10:52 proposed → checked (checked): the verdict names this commit - 2026-10-09 10:52 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`.
Author
Contributor

Merge check at 2594a24b

  • mesh/merge-gate: PASS — every machine composes with the change as it did without (4 of 4 compose) (modules: claude-code, mounts, route-adapter, new:modules/mesh-cli)
  • mesh/repo-check: PASS — its merge-check.sh passed, each part in its toolchain: merge-check.sh (go), merge-check-typescript.sh (typescript)

Delivery plan — builds claude-code, mounts, route-adapter, new: modules/mesh-cli → ace, g14, novox, shanks; no bus step

  • tier 0: claude-code, mounts, route-adapter
  • ace: receives claude-code
  • g14: receives claude-code
  • novox: receives claude-code
  • shanks: receives claude-code
  • claude-code keeps data (ADR 0233): what it holds is backed up before it moves

Run by the build seat on g14 as build-1791540737920541748 (builds --log build-1791540737920541748).

--- the gate: claude-code, mounts, route-adapter, new:modules/mesh-cli
claude-code: ok, 41 tool(s), keeps state servers, holdings, config, reads claude-licence-manager.bindings, keeps agent-home (valuable); WARNING: settings 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)
mesh-cli: ok
mounts: ok, 3 tool(s), invokes seat:mesh-controller.data, keeps state shares, reads nfs-server.exports, ready: apply by unit every 30s; watch by its tool mounts_health every 1m0s; WARNING: config 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)
route-adapter: ok; WARNING: config 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)
long-running resources without health: 0
files asking for a setting without saying whether it is trusted: 3
4 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 2 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

modules the change moves:
  - mesh-cli (added)
  - route-adapter (changed)

machines:
  - a machine (f35): composes
  - holds mesh-dns-resolver (idt): composes
  - holds git, holds mesh-artifact-store, holds mesh-broker, holds mesh-catalog, holds mesh-delivery, holds mesh-dns-resolver, holds mesh-store, holds mesh-vault, holds npm-package-registry, the control node, the hub (ygcyr): composes
  - a machine (yvbpsm): composes

a merge would rebuild 3 module(s) in 1 tier(s): claude-code, mounts, route-adapter
--- its merge-check.sh (go toolchain)
ok  	git.novox.be/novox/mesh-catalog/checks/words	0.001s
words: 12 retired words, none in the 34130 strings of 605 files
ok  	git.novox.be/novox/mesh-catalog/checks/paths	0.005s
paths: no module names another's state on its machine (3 known, listed to go)
long-running resources without health: 70, as kept
testing modules/claude-code
ok  	claude-code/cmd/claude-code	1.460s
testing modules/mesh-cli
ok  	mesh-cli/cmd/mesh-cli	1.009s
testing modules/mounts
ok  	mounts/cmd/mounts	1.068s
modules/route-adapter is TypeScript: merge-check-typescript.sh type-checks and tests it
--- its merge-check-typescript.sh (typescript toolchain)
type-checking modules/route-adapter (TypeScript)
testing modules/route-adapter (TypeScript)
✔ it writes one route file per contribution, in the predecessor's own shape (5.343254ms)
✔ it removes the file it wrote when that contribution goes (2.770248ms)
✔ it never touches a file it did not write (3.036207ms)
✔ the target port follows what the contributor publishes (1.333547ms)
✔ a contributor on another node is reached at the address the mesh gave it (0.92602ms)
✔ a node's settings are laid over the module's defaults, and nothing else changes (0.825261ms)
✔ a contribution it cannot act on is skipped and named (0.15988ms)
✔ a contribution the file shape cannot say is skipped and says which part (0.189196ms)
✔ it refuses when the predecessor's directory is not there, and says why (1.10131ms)
✔ a body limit is written as the predecessor's buffering middleware (1.269316ms)
✔ a body limit that is not a whole number of bytes is skipped and named (0.235182ms)
ℹ tests 11
ℹ suites 0
ℹ pass 11
ℹ fail 0
ℹ cancelled 0
ℹ skipped 0
ℹ todo 0
ℹ duration_ms 91.617941
**Merge check** at `2594a24b` - `mesh/merge-gate`: **PASS** — every machine composes with the change as it did without (4 of 4 compose) (modules: claude-code, mounts, route-adapter, new:modules/mesh-cli) - `mesh/repo-check`: **PASS** — its merge-check.sh passed, each part in its toolchain: merge-check.sh (go), merge-check-typescript.sh (typescript) **Delivery plan** — builds claude-code, mounts, route-adapter, new: modules/mesh-cli → ace, g14, novox, shanks; no bus step - tier 0: claude-code, mounts, route-adapter - ace: receives claude-code - g14: receives claude-code - novox: receives claude-code - shanks: receives claude-code - claude-code keeps data (ADR 0233): what it holds is backed up before it moves Run by the build seat on g14 as `build-1791540737920541748` (`builds --log build-1791540737920541748`). ``` --- the gate: claude-code, mounts, route-adapter, new:modules/mesh-cli claude-code: ok, 41 tool(s), keeps state servers, holdings, config, reads claude-licence-manager.bindings, keeps agent-home (valuable); WARNING: settings 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) mesh-cli: ok mounts: ok, 3 tool(s), invokes seat:mesh-controller.data, keeps state shares, reads nfs-server.exports, ready: apply by unit every 30s; watch by its tool mounts_health every 1m0s; WARNING: config 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) route-adapter: ok; WARNING: config 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) long-running resources without health: 0 files asking for a setting without saying whether it is trusted: 3 4 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 2 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 modules the change moves: - mesh-cli (added) - route-adapter (changed) machines: - a machine (f35): composes - holds mesh-dns-resolver (idt): composes - holds git, holds mesh-artifact-store, holds mesh-broker, holds mesh-catalog, holds mesh-delivery, holds mesh-dns-resolver, holds mesh-store, holds mesh-vault, holds npm-package-registry, the control node, the hub (ygcyr): composes - a machine (yvbpsm): composes a merge would rebuild 3 module(s) in 1 tier(s): claude-code, mounts, route-adapter --- its merge-check.sh (go toolchain) ok git.novox.be/novox/mesh-catalog/checks/words 0.001s words: 12 retired words, none in the 34130 strings of 605 files ok git.novox.be/novox/mesh-catalog/checks/paths 0.005s paths: no module names another's state on its machine (3 known, listed to go) long-running resources without health: 70, as kept testing modules/claude-code ok claude-code/cmd/claude-code 1.460s testing modules/mesh-cli ok mesh-cli/cmd/mesh-cli 1.009s testing modules/mounts ok mounts/cmd/mounts 1.068s modules/route-adapter is TypeScript: merge-check-typescript.sh type-checks and tests it --- its merge-check-typescript.sh (typescript toolchain) type-checking modules/route-adapter (TypeScript) testing modules/route-adapter (TypeScript) ✔ it writes one route file per contribution, in the predecessor's own shape (5.343254ms) ✔ it removes the file it wrote when that contribution goes (2.770248ms) ✔ it never touches a file it did not write (3.036207ms) ✔ the target port follows what the contributor publishes (1.333547ms) ✔ a contributor on another node is reached at the address the mesh gave it (0.92602ms) ✔ a node's settings are laid over the module's defaults, and nothing else changes (0.825261ms) ✔ a contribution it cannot act on is skipped and named (0.15988ms) ✔ a contribution the file shape cannot say is skipped and says which part (0.189196ms) ✔ it refuses when the predecessor's directory is not there, and says why (1.10131ms) ✔ a body limit is written as the predecessor's buffering middleware (1.269316ms) ✔ a body limit that is not a whole number of bytes is skipped and named (0.235182ms) ℹ tests 11 ℹ suites 0 ℹ pass 11 ℹ fail 0 ℹ cancelled 0 ℹ skipped 0 ℹ todo 0 ℹ duration_ms 91.617941 ```
jschoubben added 1 commit 2026-10-09 10:17:01 +00:00
Take out a mounts binary a local build left in this branch
mesh/merge-gate pass: builds claude-code, route-adapter, new: modules/mesh-cli → ace, g14, novox, shanks; no bus step; every machine composes with the chan…
mesh/repo-check pass: its merge-check.sh passed, each part in its toolchain: merge-check.sh (go), merge-check-typescript.sh (typescript)
mesh/delivery superseded: a newer head of the same pull request
e1e043c088
Author
Contributor

Merge check at e1e043c0

  • mesh/merge-gate: PASS — every machine composes with the change as it did without (4 of 4 compose) (modules: claude-code, route-adapter, new:modules/mesh-cli)
  • mesh/repo-check: PASS — its merge-check.sh passed, each part in its toolchain: merge-check.sh (go), merge-check-typescript.sh (typescript)

Delivery plan — builds claude-code, route-adapter, new: modules/mesh-cli → ace, g14, novox, shanks; no bus step

  • tier 0: claude-code, route-adapter
  • ace: receives claude-code
  • g14: receives claude-code
  • novox: receives claude-code
  • shanks: receives claude-code
  • claude-code keeps data (ADR 0233): what it holds is backed up before it moves

Run by the build seat on g14 as build-1791541043599588497 (builds --log build-1791541043599588497).

--- the gate: claude-code, route-adapter, new:modules/mesh-cli
claude-code: ok, 41 tool(s), keeps state servers, holdings, config, reads claude-licence-manager.bindings, keeps agent-home (valuable); WARNING: settings 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)
mesh-cli: ok
route-adapter: ok; WARNING: config 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)
long-running resources without health: 0
files asking for a setting without saying whether it is trusted: 2
3 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 2 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

modules the change moves:
  - mesh-cli (added)
  - route-adapter (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 1 tier(s): claude-code, route-adapter
--- its merge-check.sh (go toolchain)
ok  	git.novox.be/novox/mesh-catalog/checks/words	0.002s
words: 12 retired words, none in the 34130 strings of 605 files
ok  	git.novox.be/novox/mesh-catalog/checks/paths	0.004s
paths: no module names another's state on its machine (3 known, listed to go)
long-running resources without health: 70, as kept
testing modules/claude-code
ok  	claude-code/cmd/claude-code	1.523s
testing modules/mesh-cli
ok  	mesh-cli/cmd/mesh-cli	1.009s
modules/route-adapter is TypeScript: merge-check-typescript.sh type-checks and tests it
--- its merge-check-typescript.sh (typescript toolchain)
type-checking modules/route-adapter (TypeScript)
testing modules/route-adapter (TypeScript)
✔ it writes one route file per contribution, in the predecessor's own shape (6.148913ms)
✔ it removes the file it wrote when that contribution goes (2.71248ms)
✔ it never touches a file it did not write (3.049505ms)
✔ the target port follows what the contributor publishes (1.333452ms)
✔ a contributor on another node is reached at the address the mesh gave it (0.956872ms)
✔ a node's settings are laid over the module's defaults, and nothing else changes (1.033407ms)
✔ a contribution it cannot act on is skipped and named (0.171543ms)
✔ a contribution the file shape cannot say is skipped and says which part (0.184278ms)
✔ it refuses when the predecessor's directory is not there, and says why (1.057372ms)
✔ a body limit is written as the predecessor's buffering middleware (1.442137ms)
✔ a body limit that is not a whole number of bytes is skipped and named (0.239792ms)
ℹ tests 11
ℹ suites 0
ℹ pass 11
ℹ fail 0
ℹ cancelled 0
ℹ skipped 0
ℹ todo 0
ℹ duration_ms 84.728759
**Merge check** at `e1e043c0` - `mesh/merge-gate`: **PASS** — every machine composes with the change as it did without (4 of 4 compose) (modules: claude-code, route-adapter, new:modules/mesh-cli) - `mesh/repo-check`: **PASS** — its merge-check.sh passed, each part in its toolchain: merge-check.sh (go), merge-check-typescript.sh (typescript) **Delivery plan** — builds claude-code, route-adapter, new: modules/mesh-cli → ace, g14, novox, shanks; no bus step - tier 0: claude-code, route-adapter - ace: receives claude-code - g14: receives claude-code - novox: receives claude-code - shanks: receives claude-code - claude-code keeps data (ADR 0233): what it holds is backed up before it moves Run by the build seat on g14 as `build-1791541043599588497` (`builds --log build-1791541043599588497`). ``` --- the gate: claude-code, route-adapter, new:modules/mesh-cli claude-code: ok, 41 tool(s), keeps state servers, holdings, config, reads claude-licence-manager.bindings, keeps agent-home (valuable); WARNING: settings 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) mesh-cli: ok route-adapter: ok; WARNING: config 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) long-running resources without health: 0 files asking for a setting without saying whether it is trusted: 2 3 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 2 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 modules the change moves: - mesh-cli (added) - route-adapter (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 1 tier(s): claude-code, route-adapter --- its merge-check.sh (go toolchain) ok git.novox.be/novox/mesh-catalog/checks/words 0.002s words: 12 retired words, none in the 34130 strings of 605 files ok git.novox.be/novox/mesh-catalog/checks/paths 0.004s paths: no module names another's state on its machine (3 known, listed to go) long-running resources without health: 70, as kept testing modules/claude-code ok claude-code/cmd/claude-code 1.523s testing modules/mesh-cli ok mesh-cli/cmd/mesh-cli 1.009s modules/route-adapter is TypeScript: merge-check-typescript.sh type-checks and tests it --- its merge-check-typescript.sh (typescript toolchain) type-checking modules/route-adapter (TypeScript) testing modules/route-adapter (TypeScript) ✔ it writes one route file per contribution, in the predecessor's own shape (6.148913ms) ✔ it removes the file it wrote when that contribution goes (2.71248ms) ✔ it never touches a file it did not write (3.049505ms) ✔ the target port follows what the contributor publishes (1.333452ms) ✔ a contributor on another node is reached at the address the mesh gave it (0.956872ms) ✔ a node's settings are laid over the module's defaults, and nothing else changes (1.033407ms) ✔ a contribution it cannot act on is skipped and named (0.171543ms) ✔ a contribution the file shape cannot say is skipped and says which part (0.184278ms) ✔ it refuses when the predecessor's directory is not there, and says why (1.057372ms) ✔ a body limit is written as the predecessor's buffering middleware (1.442137ms) ✔ a body limit that is not a whole number of bytes is skipped and named (0.239792ms) ℹ tests 11 ℹ suites 0 ℹ pass 11 ℹ fail 0 ℹ cancelled 0 ℹ skipped 0 ℹ todo 0 ℹ duration_ms 84.728759 ```
jschoubben added 1 commit 2026-10-09 10:49:24 +00:00
mesh-cli: say an outcome not known, and hold the module to placing one file (review of hq ADR 0272)
mesh/merge-gate pass: builds claude-code, route-adapter, new: modules/mesh-cli → ace, g14, novox, shanks; no bus step; every machine composes with the chan…
mesh/repo-check pass: its merge-check.sh passed, each part in its toolchain: merge-check.sh (go), merge-check-typescript.sh (typescript)
mesh/delivery delivered
6f1c559d93
A line whose answer did not come in time is said as possibly run, with
its call, never as nothing having run. A test holds the module to one
archive resource unpacking one compiled Go bundle into /usr/local/bin.
The README says the MESH_VERB refusal is a courtesy and the controller is
the gate. SDK pinned at the go/cli branch's newest commit until go/v0.1.9.
Author
Contributor

Merge check at 6f1c559d

  • mesh/merge-gate: PASS — every machine composes with the change as it did without (4 of 4 compose) (modules: claude-code, route-adapter, new:modules/mesh-cli)
  • mesh/repo-check: PASS — its merge-check.sh passed, each part in its toolchain: merge-check.sh (go), merge-check-typescript.sh (typescript)

Delivery plan — builds claude-code, route-adapter, new: modules/mesh-cli → ace, g14, novox, shanks; no bus step

  • tier 0: claude-code, route-adapter
  • ace: receives claude-code
  • g14: receives claude-code
  • novox: receives claude-code
  • shanks: receives claude-code
  • claude-code keeps data (ADR 0233): what it holds is backed up before it moves

Run by the build seat on novox as build-1791542966523851711 (builds --log build-1791542966523851711).

--- the gate: claude-code, route-adapter, new:modules/mesh-cli
claude-code: ok, 41 tool(s), keeps state servers, holdings, config, reads claude-licence-manager.bindings, keeps agent-home (valuable); WARNING: settings 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)
mesh-cli: ok
route-adapter: ok; WARNING: config 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)
long-running resources without health: 0
files asking for a setting without saying whether it is trusted: 2
3 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 2 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

modules the change moves:
  - mesh-cli (added)
  - route-adapter (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 1 tier(s): claude-code, route-adapter
--- its merge-check.sh (go toolchain)
ok  	git.novox.be/novox/mesh-catalog/checks/words	0.002s
words: 12 retired words, none in the 34132 strings of 605 files
ok  	git.novox.be/novox/mesh-catalog/checks/paths	0.007s
paths: no module names another's state on its machine (3 known, listed to go)
long-running resources without health: 70, as kept
testing modules/claude-code
ok  	claude-code/cmd/claude-code	1.513s
testing modules/mesh-cli
ok  	mesh-cli/cmd/mesh-cli	1.012s
modules/route-adapter is TypeScript: merge-check-typescript.sh type-checks and tests it
--- its merge-check-typescript.sh (typescript toolchain)
type-checking modules/route-adapter (TypeScript)
testing modules/route-adapter (TypeScript)
✔ it writes one route file per contribution, in the predecessor's own shape (7.274187ms)
✔ it removes the file it wrote when that contribution goes (2.642393ms)
✔ it never touches a file it did not write (4.534974ms)
✔ the target port follows what the contributor publishes (1.890442ms)
✔ a contributor on another node is reached at the address the mesh gave it (1.471671ms)
✔ a node's settings are laid over the module's defaults, and nothing else changes (1.430152ms)
✔ a contribution it cannot act on is skipped and named (0.22737ms)
✔ a contribution the file shape cannot say is skipped and says which part (0.29184ms)
✔ it refuses when the predecessor's directory is not there, and says why (1.579342ms)
✔ a body limit is written as the predecessor's buffering middleware (1.920832ms)
✔ a body limit that is not a whole number of bytes is skipped and named (0.32462ms)
ℹ tests 11
ℹ suites 0
ℹ pass 11
ℹ fail 0
ℹ cancelled 0
ℹ skipped 0
ℹ todo 0
ℹ duration_ms 117.734138
**Merge check** at `6f1c559d` - `mesh/merge-gate`: **PASS** — every machine composes with the change as it did without (4 of 4 compose) (modules: claude-code, route-adapter, new:modules/mesh-cli) - `mesh/repo-check`: **PASS** — its merge-check.sh passed, each part in its toolchain: merge-check.sh (go), merge-check-typescript.sh (typescript) **Delivery plan** — builds claude-code, route-adapter, new: modules/mesh-cli → ace, g14, novox, shanks; no bus step - tier 0: claude-code, route-adapter - ace: receives claude-code - g14: receives claude-code - novox: receives claude-code - shanks: receives claude-code - claude-code keeps data (ADR 0233): what it holds is backed up before it moves Run by the build seat on novox as `build-1791542966523851711` (`builds --log build-1791542966523851711`). ``` --- the gate: claude-code, route-adapter, new:modules/mesh-cli claude-code: ok, 41 tool(s), keeps state servers, holdings, config, reads claude-licence-manager.bindings, keeps agent-home (valuable); WARNING: settings 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) mesh-cli: ok route-adapter: ok; WARNING: config 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) long-running resources without health: 0 files asking for a setting without saying whether it is trusted: 2 3 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 2 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 modules the change moves: - mesh-cli (added) - route-adapter (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 1 tier(s): claude-code, route-adapter --- its merge-check.sh (go toolchain) ok git.novox.be/novox/mesh-catalog/checks/words 0.002s words: 12 retired words, none in the 34132 strings of 605 files ok git.novox.be/novox/mesh-catalog/checks/paths 0.007s paths: no module names another's state on its machine (3 known, listed to go) long-running resources without health: 70, as kept testing modules/claude-code ok claude-code/cmd/claude-code 1.513s testing modules/mesh-cli ok mesh-cli/cmd/mesh-cli 1.012s modules/route-adapter is TypeScript: merge-check-typescript.sh type-checks and tests it --- its merge-check-typescript.sh (typescript toolchain) type-checking modules/route-adapter (TypeScript) testing modules/route-adapter (TypeScript) ✔ it writes one route file per contribution, in the predecessor's own shape (7.274187ms) ✔ it removes the file it wrote when that contribution goes (2.642393ms) ✔ it never touches a file it did not write (4.534974ms) ✔ the target port follows what the contributor publishes (1.890442ms) ✔ a contributor on another node is reached at the address the mesh gave it (1.471671ms) ✔ a node's settings are laid over the module's defaults, and nothing else changes (1.430152ms) ✔ a contribution it cannot act on is skipped and named (0.22737ms) ✔ a contribution the file shape cannot say is skipped and says which part (0.29184ms) ✔ it refuses when the predecessor's directory is not there, and says why (1.579342ms) ✔ a body limit is written as the predecessor's buffering middleware (1.920832ms) ✔ a body limit that is not a whole number of bytes is skipped and named (0.32462ms) ℹ tests 11 ℹ suites 0 ℹ pass 11 ℹ fail 0 ℹ cancelled 0 ℹ skipped 0 ℹ todo 0 ℹ duration_ms 117.734138 ```
mesh-admin merged commit 8ff8197a32 into main 2026-10-09 11:38:44 +00:00
mesh-admin deleted branch feat/272-mesh-cli 2026-10-09 11:38:45 +00:00
Sign in to join this conversation.
No Reviewers
2 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: novox/mesh-catalog#156