Step 1b of hq ADR 0259 (hq #211). The tool runner carries what a bundle says on the seats that name their caller or their kind, and only as far as the module's membership lists.
Changed after the security and correctness reviews of 2026-10-08:
The user switch (MESH_RUN_AS) is gone. It could not work from a runner that is not root, and it trusted names. A module of its own account is now served by a runtime of its own, as that account, on its own credential. The controller composes that runtime (mesh-controller #154, runs-as); this runner only accepts serving its own module, and that module alone, when it runs on a module's credential.
No bus variable reaches a bundle:MESH_BROKER_FILE, MESH_BROKER_URL, MESH_TOOL_ENV, MESH_TOOL_MODULES and MESH_CONSOLE_LISTEN are stripped (BundleEnv).
Work is never stranded. A failed piece of seat work is offered again from 5 s, doubling, up to 10 min; the controller sets no delivery limit on these workers. Work still being done is kept alive every 15 s, well inside the ack wait.
A deleted or refused worker is logged, never silent.
A seat message's de-duplication id is prefixed with the publishing module, so one module cannot suppress another's warrant. The bundle is told whether a publish was a duplicate.
A lost compare-and-set is answered with error code -32010, so the SDK tells it by type, not by words. An update with revision 0 is refused.
mesh/seat.record with no bucket named reads the one record the membership lists.
Tests
internal/bus/seat_test.go, against a real bus (as before).
internal/runtime/own_account_test.go: a runtime on a module's own account serves that module alone; no bus variable reaches a bundle; a tool call never reaches a seat's event, accept or proof.
internal/runtime/seat_traffic_test.go, against a real bus: moduleBus.Seat publish, duplicate, record, take bound once, refusals; a lost compare-and-set carries its code; update with revision 0 refused.
merge-check.sh now runs these runtime tests even where node is missing.
merge-check.sh passes locally, also without node on PATH.
Merge order: mesh-sdk #12 (tagged), then this, then mesh-controller #154. Do not merge without review.
Step 1b of hq ADR 0259 (hq #211). The tool runner carries what a bundle says on the seats that name their caller or their kind, and only as far as the module's membership lists.
**Changed after the security and correctness reviews of 2026-10-08:**
- **The user switch (`MESH_RUN_AS`) is gone.** It could not work from a runner that is not root, and it trusted names. A module of its own account is now served by a runtime of its own, as that account, on its own credential. The controller composes that runtime (mesh-controller #154, `runs-as`); this runner only accepts serving its own module, and that module alone, when it runs on a module's credential.
- **No bus variable reaches a bundle:** `MESH_BROKER_FILE`, `MESH_BROKER_URL`, `MESH_TOOL_ENV`, `MESH_TOOL_MODULES` and `MESH_CONSOLE_LISTEN` are stripped (`BundleEnv`).
- **Work is never stranded.** A failed piece of seat work is offered again from 5 s, doubling, up to 10 min; the controller sets no delivery limit on these workers. Work still being done is kept alive every 15 s, well inside the ack wait.
- **A deleted or refused worker is logged**, never silent.
- **A seat message's de-duplication id is prefixed with the publishing module**, so one module cannot suppress another's warrant. The bundle is told whether a publish was a duplicate.
- **A lost compare-and-set is answered with error code -32010**, so the SDK tells it by type, not by words. An update with revision 0 is refused.
- **`mesh/seat.record`** with no bucket named reads the one record the membership lists.
**Tests**
- `internal/bus/seat_test.go`, against a real bus (as before).
- `internal/runtime/own_account_test.go`: a runtime on a module's own account serves that module alone; no bus variable reaches a bundle; a tool call never reaches a seat's event, accept or proof.
- `internal/runtime/seat_traffic_test.go`, against a real bus: `moduleBus.Seat` publish, duplicate, record, take bound once, refusals; a lost compare-and-set carries its code; update with revision 0 refused.
- `merge-check.sh` now runs these runtime tests even where node is missing.
`merge-check.sh` passes locally, also without node on PATH.
Merge order: mesh-sdk #12 (tagged), then this, then mesh-controller #154. Do not merge without review.
node-tools on ace: passed — healthy 3 times over 2m23s
node-tools on novox: judging — carried by release-1791555560543135916
node-tools on the rest running it: sent
Transitions
2026-10-09 09:09 (new) → proposed (announced): novox/mesh-tools#23's head announced
2026-10-09 09:15 proposed → checked (checked): the verdict names this commit
2026-10-09 09:15 checked → ready (accepted): the gate passed or warned, and the repository's own check did not fail
2026-10-09 14:18 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 14:18 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 14:22 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-tools@127047edd665` — **delivered** since 2026-10-09T14:22:42Z
**Delivery plan** — builds mesh-tools, node-tools → ace, g14, novox, shanks; no bus step
- tier 0: mesh-tools, node-tools
- ace: receives node-tools
- g14: receives node-tools
- novox: receives node-tools
- shanks: receives node-tools
- node-tools provides mcp-endpoint: its consumers are sent again after it
**Group** `feat/asks-answered-on-any-channel`, in order: novox/mesh-controller@c544c2a17bef → novox/mesh-catalog@e19671a88ba6 → novox/mesh-sdk@16984aafc689 → novox/mesh-tools@127047edd665
- novox/mesh-controller@c544c2a17bef before novox/mesh-catalog@e19671a88ba6: built by
- novox/mesh-controller@c544c2a17bef before novox/mesh-sdk@16984aafc689: built by
- novox/mesh-controller@c544c2a17bef before novox/mesh-tools@127047edd665: built by
**Machines**
- mesh-tools on every machine running it: sent
- node-tools on ace: passed — healthy 3 times over 2m23s
- node-tools on novox: judging — carried by release-1791555560543135916
- node-tools on the rest running it: sent
**Transitions**
- 2026-10-09 09:09 (new) → proposed (announced): novox/mesh-tools#23's head announced
- 2026-10-09 09:15 proposed → checked (checked): the verdict names this commit
- 2026-10-09 09:15 checked → ready (accepted): the gate passed or warned, and the repository's own check did not fail
- 2026-10-09 14:18 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 14:18 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 14:22 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-tools, node-tools)
mesh/repo-check: PASS — its merge-check.sh passed
Delivery plan — builds mesh-tools, node-tools → ace, g14, novox, shanks; no bus step
tier 0: mesh-tools, node-tools
ace: receives node-tools
g14: receives node-tools
novox: receives node-tools
shanks: receives node-tools
node-tools provides mcp-endpoint: its consumers are sent again after it
Run by the build seat on g14 as build-1791469890514958911 (builds --log build-1791469890514958911).
--- the gate: mesh-tools, node-tools
mesh-tools: ok
node-tools: ok, invokes every tool
long-running resources without health: 0
2 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-08T14:30:42Z 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-08T14:30:42Z
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): mesh-tools, node-tools
--- its merge-check.sh (go toolchain)
NOT TESTED HERE: internal/runtime and internal/console launch bundles that need node and @novox/mesh-sdk
? github.com/novox/mesh-tools/node-tools/cmd/node-tools [no test files]
ok github.com/novox/mesh-tools/node-tools/internal/alive 1.193s
ok github.com/novox/mesh-tools/node-tools/internal/announce 4.369s
ok github.com/novox/mesh-tools/node-tools/internal/bus 7.902s
ok github.com/novox/mesh-tools/node-tools/internal/launch 1.054s
ok github.com/novox/mesh-tools/node-tools/internal/meshtest 1.119s
? github.com/novox/mesh-tools/node-tools/internal/wire [no test files]
ok github.com/novox/mesh-tools/node-tools/internal/console 0.005s
NOT TESTED HERE: node-tools/src (TypeScript) needs @novox/mesh-sdk from the package registry
**Merge check** at `1c3ece81`
- `mesh/merge-gate`: **PASS** — every machine composes with the change as it did without (4 of 4 compose) (modules: mesh-tools, node-tools)
- `mesh/repo-check`: **PASS** — its merge-check.sh passed
**Delivery plan** — builds mesh-tools, node-tools → ace, g14, novox, shanks; no bus step
- tier 0: mesh-tools, node-tools
- ace: receives node-tools
- g14: receives node-tools
- novox: receives node-tools
- shanks: receives node-tools
- node-tools provides mcp-endpoint: its consumers are sent again after it
Run by the build seat on g14 as `build-1791469890514958911` (`builds --log build-1791469890514958911`).
```
--- the gate: mesh-tools, node-tools
mesh-tools: ok
node-tools: ok, invokes every tool
long-running resources without health: 0
2 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-08T14:30:42Z 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-08T14:30:42Z
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): mesh-tools, node-tools
--- its merge-check.sh (go toolchain)
NOT TESTED HERE: internal/runtime and internal/console launch bundles that need node and @novox/mesh-sdk
? github.com/novox/mesh-tools/node-tools/cmd/node-tools [no test files]
ok github.com/novox/mesh-tools/node-tools/internal/alive 1.193s
ok github.com/novox/mesh-tools/node-tools/internal/announce 4.369s
ok github.com/novox/mesh-tools/node-tools/internal/bus 7.902s
ok github.com/novox/mesh-tools/node-tools/internal/launch 1.054s
ok github.com/novox/mesh-tools/node-tools/internal/meshtest 1.119s
? github.com/novox/mesh-tools/node-tools/internal/wire [no test files]
ok github.com/novox/mesh-tools/node-tools/internal/console 0.005s
NOT TESTED HERE: node-tools/src (TypeScript) needs @novox/mesh-sdk from the package registry
```
mesh/merge-gate: PASS — every machine composes with the change as it did without (4 of 4 compose) (modules: mesh-tools, node-tools)
mesh/repo-check: PASS — its merge-check.sh passed
Delivery plan — builds mesh-tools, node-tools → ace, g14, novox, shanks; no bus step
tier 0: mesh-tools, node-tools
ace: receives node-tools
g14: receives node-tools
novox: receives node-tools
shanks: receives node-tools
node-tools provides mcp-endpoint: its consumers are sent again after it
Run by the build seat on shanks as build-1791469969409791456 (builds --log build-1791469969409791456).
--- the gate: mesh-tools, node-tools
mesh-tools: ok
node-tools: ok, invokes every tool
long-running resources without health: 0
2 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-08T14:30:42Z 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-08T14:30:42Z
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): mesh-tools, node-tools
--- its merge-check.sh (go toolchain)
NOT TESTED HERE: internal/runtime and internal/console launch bundles that need node and @novox/mesh-sdk
? github.com/novox/mesh-tools/node-tools/cmd/node-tools [no test files]
ok github.com/novox/mesh-tools/node-tools/internal/alive 1.191s
ok github.com/novox/mesh-tools/node-tools/internal/announce 4.367s
ok github.com/novox/mesh-tools/node-tools/internal/bus 7.732s
ok github.com/novox/mesh-tools/node-tools/internal/launch 1.090s
ok github.com/novox/mesh-tools/node-tools/internal/meshtest 1.130s
? github.com/novox/mesh-tools/node-tools/internal/wire [no test files]
ok github.com/novox/mesh-tools/node-tools/internal/console 0.005s
NOT TESTED HERE: node-tools/src (TypeScript) needs @novox/mesh-sdk from the package registry
**Merge check** at `363bc7a1`
- `mesh/merge-gate`: **PASS** — every machine composes with the change as it did without (4 of 4 compose) (modules: mesh-tools, node-tools)
- `mesh/repo-check`: **PASS** — its merge-check.sh passed
**Delivery plan** — builds mesh-tools, node-tools → ace, g14, novox, shanks; no bus step
- tier 0: mesh-tools, node-tools
- ace: receives node-tools
- g14: receives node-tools
- novox: receives node-tools
- shanks: receives node-tools
- node-tools provides mcp-endpoint: its consumers are sent again after it
Run by the build seat on shanks as `build-1791469969409791456` (`builds --log build-1791469969409791456`).
```
--- the gate: mesh-tools, node-tools
mesh-tools: ok
node-tools: ok, invokes every tool
long-running resources without health: 0
2 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-08T14:30:42Z 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-08T14:30:42Z
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): mesh-tools, node-tools
--- its merge-check.sh (go toolchain)
NOT TESTED HERE: internal/runtime and internal/console launch bundles that need node and @novox/mesh-sdk
? github.com/novox/mesh-tools/node-tools/cmd/node-tools [no test files]
ok github.com/novox/mesh-tools/node-tools/internal/alive 1.191s
ok github.com/novox/mesh-tools/node-tools/internal/announce 4.367s
ok github.com/novox/mesh-tools/node-tools/internal/bus 7.732s
ok github.com/novox/mesh-tools/node-tools/internal/launch 1.090s
ok github.com/novox/mesh-tools/node-tools/internal/meshtest 1.130s
? github.com/novox/mesh-tools/node-tools/internal/wire [no test files]
ok github.com/novox/mesh-tools/node-tools/internal/console 0.005s
NOT TESTED HERE: node-tools/src (TypeScript) needs @novox/mesh-sdk from the package registry
```
mesh/merge-gate: PASS — every machine composes with the change as it did without (4 of 4 compose) (modules: mesh-tools, node-tools)
mesh/repo-check: PASS — its merge-check.sh passed
Delivery plan — builds mesh-tools, node-tools → ace, g14, novox, shanks; no bus step
tier 0: mesh-tools, node-tools
ace: receives node-tools
g14: receives node-tools
novox: receives node-tools
shanks: receives node-tools
node-tools provides mcp-endpoint: its consumers are sent again after it
Run by the build seat on novox as build-1791470272298104619 (builds --log build-1791470272298104619).
--- the gate: mesh-tools, node-tools
mesh-tools: ok
node-tools: ok, invokes every tool
long-running resources without health: 0
2 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-08T14:30:42Z 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-08T14:30:42Z
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): mesh-tools, node-tools
--- its merge-check.sh (go toolchain)
NOT TESTED HERE: internal/runtime and internal/console launch bundles that need node and @novox/mesh-sdk
? github.com/novox/mesh-tools/node-tools/cmd/node-tools [no test files]
ok github.com/novox/mesh-tools/node-tools/internal/alive 1.191s
ok github.com/novox/mesh-tools/node-tools/internal/announce 4.369s
ok github.com/novox/mesh-tools/node-tools/internal/bus 7.743s
ok github.com/novox/mesh-tools/node-tools/internal/launch 1.070s
ok github.com/novox/mesh-tools/node-tools/internal/meshtest 1.133s
? github.com/novox/mesh-tools/node-tools/internal/wire [no test files]
ok github.com/novox/mesh-tools/node-tools/internal/console 0.005s
NOT TESTED HERE: node-tools/src (TypeScript) needs @novox/mesh-sdk from the package registry
**Merge check** at `db697d9f`
- `mesh/merge-gate`: **PASS** — every machine composes with the change as it did without (4 of 4 compose) (modules: mesh-tools, node-tools)
- `mesh/repo-check`: **PASS** — its merge-check.sh passed
**Delivery plan** — builds mesh-tools, node-tools → ace, g14, novox, shanks; no bus step
- tier 0: mesh-tools, node-tools
- ace: receives node-tools
- g14: receives node-tools
- novox: receives node-tools
- shanks: receives node-tools
- node-tools provides mcp-endpoint: its consumers are sent again after it
Run by the build seat on novox as `build-1791470272298104619` (`builds --log build-1791470272298104619`).
```
--- the gate: mesh-tools, node-tools
mesh-tools: ok
node-tools: ok, invokes every tool
long-running resources without health: 0
2 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-08T14:30:42Z 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-08T14:30:42Z
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): mesh-tools, node-tools
--- its merge-check.sh (go toolchain)
NOT TESTED HERE: internal/runtime and internal/console launch bundles that need node and @novox/mesh-sdk
? github.com/novox/mesh-tools/node-tools/cmd/node-tools [no test files]
ok github.com/novox/mesh-tools/node-tools/internal/alive 1.191s
ok github.com/novox/mesh-tools/node-tools/internal/announce 4.369s
ok github.com/novox/mesh-tools/node-tools/internal/bus 7.743s
ok github.com/novox/mesh-tools/node-tools/internal/launch 1.070s
ok github.com/novox/mesh-tools/node-tools/internal/meshtest 1.133s
? github.com/novox/mesh-tools/node-tools/internal/wire [no test files]
ok github.com/novox/mesh-tools/node-tools/internal/console 0.005s
NOT TESTED HERE: node-tools/src (TypeScript) needs @novox/mesh-sdk from the package registry
```
mesh/merge-gate: PASS — every machine composes with the change as it did without (4 of 4 compose) (modules: mesh-tools, node-tools)
mesh/repo-check: PASS — THE CHANGE ALTERS ITS OWN CHECK (merge-check.sh): main's version judged it; the change's judges the pull requests after it merges; its merge-check.sh passed
Delivery plan — builds mesh-tools, node-tools → ace, g14, novox, shanks; no bus step
tier 0: mesh-tools, node-tools
ace: receives node-tools
g14: receives node-tools
novox: receives node-tools
shanks: receives node-tools
node-tools provides mcp-endpoint: its consumers are sent again after it
Run by the build seat on ace as build-1791476618663757197 (builds --log build-1791476618663757197).
--- the gate: mesh-tools, node-tools
mesh-tools: ok
node-tools: ok, invokes every tool
long-running resources without health: 0
2 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-08T16:16:42Z 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-08T16:16:42Z
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): mesh-tools, node-tools
--- THE CHANGE ALTERS ITS OWN CHECK (merge-check.sh): main's version judged it; the change's judges the pull requests after it merges
--- its merge-check.sh (go toolchain)
go: downloading github.com/nats-io/nats-server/v2 v2.11.17
go: downloading github.com/nats-io/jwt/v2 v2.8.1
go: downloading github.com/antithesishq/antithesis-sdk-go v0.7.0-default-no-op
go: downloading github.com/minio/highwayhash v1.0.4
go: downloading golang.org/x/time v0.15.0
NOT TESTED HERE: internal/runtime and internal/console launch bundles that need node and @novox/mesh-sdk
? github.com/novox/mesh-tools/node-tools/cmd/node-tools [no test files]
ok github.com/novox/mesh-tools/node-tools/internal/alive 1.191s
ok github.com/novox/mesh-tools/node-tools/internal/announce 4.369s
ok github.com/novox/mesh-tools/node-tools/internal/bus 7.685s
ok github.com/novox/mesh-tools/node-tools/internal/launch 1.077s
ok github.com/novox/mesh-tools/node-tools/internal/meshtest 1.128s
? github.com/novox/mesh-tools/node-tools/internal/wire [no test files]
ok github.com/novox/mesh-tools/node-tools/internal/console 0.005s
NOT TESTED HERE: node-tools/src (TypeScript) needs @novox/mesh-sdk from the package registry
**Merge check** at `8505e1cc`
- `mesh/merge-gate`: **PASS** — every machine composes with the change as it did without (4 of 4 compose) (modules: mesh-tools, node-tools)
- `mesh/repo-check`: **PASS** — THE CHANGE ALTERS ITS OWN CHECK (merge-check.sh): main's version judged it; the change's judges the pull requests after it merges; its merge-check.sh passed
**Delivery plan** — builds mesh-tools, node-tools → ace, g14, novox, shanks; no bus step
- tier 0: mesh-tools, node-tools
- ace: receives node-tools
- g14: receives node-tools
- novox: receives node-tools
- shanks: receives node-tools
- node-tools provides mcp-endpoint: its consumers are sent again after it
Run by the build seat on ace as `build-1791476618663757197` (`builds --log build-1791476618663757197`).
```
--- the gate: mesh-tools, node-tools
mesh-tools: ok
node-tools: ok, invokes every tool
long-running resources without health: 0
2 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-08T16:16:42Z 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-08T16:16:42Z
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): mesh-tools, node-tools
--- THE CHANGE ALTERS ITS OWN CHECK (merge-check.sh): main's version judged it; the change's judges the pull requests after it merges
--- its merge-check.sh (go toolchain)
go: downloading github.com/nats-io/nats-server/v2 v2.11.17
go: downloading github.com/nats-io/jwt/v2 v2.8.1
go: downloading github.com/antithesishq/antithesis-sdk-go v0.7.0-default-no-op
go: downloading github.com/minio/highwayhash v1.0.4
go: downloading golang.org/x/time v0.15.0
NOT TESTED HERE: internal/runtime and internal/console launch bundles that need node and @novox/mesh-sdk
? github.com/novox/mesh-tools/node-tools/cmd/node-tools [no test files]
ok github.com/novox/mesh-tools/node-tools/internal/alive 1.191s
ok github.com/novox/mesh-tools/node-tools/internal/announce 4.369s
ok github.com/novox/mesh-tools/node-tools/internal/bus 7.685s
ok github.com/novox/mesh-tools/node-tools/internal/launch 1.077s
ok github.com/novox/mesh-tools/node-tools/internal/meshtest 1.128s
? github.com/novox/mesh-tools/node-tools/internal/wire [no test files]
ok github.com/novox/mesh-tools/node-tools/internal/console 0.005s
NOT TESTED HERE: node-tools/src (TypeScript) needs @novox/mesh-sdk from the package registry
```
mesh/merge-gate pass: builds mesh-tools, node-tools → ace, g14, novox, shanks; no bus step; every machine composes with the change as it did without (4 of …
mesh/repo-check pass: THE CHANGE ALTERS ITS OWN CHECK (merge-check.sh): main's version judged it; the change's judges the pull requests after it merges; it…
mesh/merge-gate: PASS — every machine composes with the change as it did without (4 of 4 compose) (modules: mesh-tools, node-tools)
mesh/repo-check: PASS — THE CHANGE ALTERS ITS OWN CHECK (merge-check.sh): main's version judged it; the change's judges the pull requests after it merges; its merge-check.sh passed
Delivery plan — builds mesh-tools, node-tools → ace, g14, novox, shanks; no bus step
tier 0: mesh-tools, node-tools
ace: receives node-tools
g14: receives node-tools
novox: receives node-tools
shanks: receives node-tools
node-tools provides mcp-endpoint: its consumers are sent again after it
Run by the build seat on shanks as build-1791536953101740357 (builds --log build-1791536953101740357).
--- the gate: mesh-tools, node-tools
mesh-tools: ok
node-tools: ok, invokes every tool
long-running resources without health: 0
files asking for a setting without saying whether it is trusted: 0
2 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 2 module(s) in 1 tier(s): mesh-tools, node-tools
--- THE CHANGE ALTERS ITS OWN CHECK (merge-check.sh): main's version judged it; the change's judges the pull requests after it merges
--- its merge-check.sh (go toolchain)
NOT TESTED HERE: internal/runtime and internal/console launch bundles that need node and @novox/mesh-sdk
? github.com/novox/mesh-tools/node-tools/cmd/node-tools [no test files]
ok github.com/novox/mesh-tools/node-tools/internal/alive 1.190s
ok github.com/novox/mesh-tools/node-tools/internal/announce 4.366s
ok github.com/novox/mesh-tools/node-tools/internal/bus 7.738s
ok github.com/novox/mesh-tools/node-tools/internal/launch 1.072s
ok github.com/novox/mesh-tools/node-tools/internal/meshtest 1.133s
? github.com/novox/mesh-tools/node-tools/internal/wire [no test files]
ok github.com/novox/mesh-tools/node-tools/internal/console 0.005s
NOT TESTED HERE: node-tools/src (TypeScript) needs @novox/mesh-sdk from the package registry
**Merge check** at `127047ed`
- `mesh/merge-gate`: **PASS** — every machine composes with the change as it did without (4 of 4 compose) (modules: mesh-tools, node-tools)
- `mesh/repo-check`: **PASS** — THE CHANGE ALTERS ITS OWN CHECK (merge-check.sh): main's version judged it; the change's judges the pull requests after it merges; its merge-check.sh passed
**Delivery plan** — builds mesh-tools, node-tools → ace, g14, novox, shanks; no bus step
- tier 0: mesh-tools, node-tools
- ace: receives node-tools
- g14: receives node-tools
- novox: receives node-tools
- shanks: receives node-tools
- node-tools provides mcp-endpoint: its consumers are sent again after it
Run by the build seat on shanks as `build-1791536953101740357` (`builds --log build-1791536953101740357`).
```
--- the gate: mesh-tools, node-tools
mesh-tools: ok
node-tools: ok, invokes every tool
long-running resources without health: 0
files asking for a setting without saying whether it is trusted: 0
2 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 2 module(s) in 1 tier(s): mesh-tools, node-tools
--- THE CHANGE ALTERS ITS OWN CHECK (merge-check.sh): main's version judged it; the change's judges the pull requests after it merges
--- its merge-check.sh (go toolchain)
NOT TESTED HERE: internal/runtime and internal/console launch bundles that need node and @novox/mesh-sdk
? github.com/novox/mesh-tools/node-tools/cmd/node-tools [no test files]
ok github.com/novox/mesh-tools/node-tools/internal/alive 1.190s
ok github.com/novox/mesh-tools/node-tools/internal/announce 4.366s
ok github.com/novox/mesh-tools/node-tools/internal/bus 7.738s
ok github.com/novox/mesh-tools/node-tools/internal/launch 1.072s
ok github.com/novox/mesh-tools/node-tools/internal/meshtest 1.133s
? github.com/novox/mesh-tools/node-tools/internal/wire [no test files]
ok github.com/novox/mesh-tools/node-tools/internal/console 0.005s
NOT TESTED HERE: node-tools/src (TypeScript) needs @novox/mesh-sdk from the package registry
```
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.
Step 1b of hq ADR 0259 (hq #211). The tool runner carries what a bundle says on the seats that name their caller or their kind, and only as far as the module's membership lists.
Changed after the security and correctness reviews of 2026-10-08:
MESH_RUN_AS) is gone. It could not work from a runner that is not root, and it trusted names. A module of its own account is now served by a runtime of its own, as that account, on its own credential. The controller composes that runtime (mesh-controller #154,runs-as); this runner only accepts serving its own module, and that module alone, when it runs on a module's credential.MESH_BROKER_FILE,MESH_BROKER_URL,MESH_TOOL_ENV,MESH_TOOL_MODULESandMESH_CONSOLE_LISTENare stripped (BundleEnv).mesh/seat.recordwith no bucket named reads the one record the membership lists.Tests
internal/bus/seat_test.go, against a real bus (as before).internal/runtime/own_account_test.go: a runtime on a module's own account serves that module alone; no bus variable reaches a bundle; a tool call never reaches a seat's event, accept or proof.internal/runtime/seat_traffic_test.go, against a real bus:moduleBus.Seatpublish, duplicate, record, take bound once, refusals; a lost compare-and-set carries its code; update with revision 0 refused.merge-check.shnow runs these runtime tests even where node is missing.merge-check.shpasses locally, also without node on PATH.Merge order: mesh-sdk #12 (tagged), then this, then mesh-controller #154. Do not merge without review.
Delivery
novox/mesh-tools@127047edd665— delivered since 2026-10-09T14:22:42ZDelivery plan — builds mesh-tools, node-tools → ace, g14, novox, shanks; no bus step
Group
feat/asks-answered-on-any-channel, in order: novox/mesh-controller@c544c2a17b → novox/mesh-catalog@e19671a88b → novox/mesh-sdk@16984aafc6 → novox/mesh-tools@127047edd6Machines
Transitions
The commit's note under
refs/notes/mesh-plankeeps every transition:git log --notes=mesh-plan.Merge check at
1c3ece81mesh/merge-gate: PASS — every machine composes with the change as it did without (4 of 4 compose) (modules: mesh-tools, node-tools)mesh/repo-check: PASS — its merge-check.sh passedDelivery plan — builds mesh-tools, node-tools → ace, g14, novox, shanks; no bus step
Run by the build seat on g14 as
build-1791469890514958911(builds --log build-1791469890514958911).Merge check at
363bc7a1mesh/merge-gate: PASS — every machine composes with the change as it did without (4 of 4 compose) (modules: mesh-tools, node-tools)mesh/repo-check: PASS — its merge-check.sh passedDelivery plan — builds mesh-tools, node-tools → ace, g14, novox, shanks; no bus step
Run by the build seat on shanks as
build-1791469969409791456(builds --log build-1791469969409791456).Merge check at
db697d9fmesh/merge-gate: PASS — every machine composes with the change as it did without (4 of 4 compose) (modules: mesh-tools, node-tools)mesh/repo-check: PASS — its merge-check.sh passedDelivery plan — builds mesh-tools, node-tools → ace, g14, novox, shanks; no bus step
Run by the build seat on novox as
build-1791470272298104619(builds --log build-1791470272298104619).Merge check at
8505e1ccmesh/merge-gate: PASS — every machine composes with the change as it did without (4 of 4 compose) (modules: mesh-tools, node-tools)mesh/repo-check: PASS — THE CHANGE ALTERS ITS OWN CHECK (merge-check.sh): main's version judged it; the change's judges the pull requests after it merges; its merge-check.sh passedDelivery plan — builds mesh-tools, node-tools → ace, g14, novox, shanks; no bus step
Run by the build seat on ace as
build-1791476618663757197(builds --log build-1791476618663757197).8505e1ccd1to127047edd6Merge check at
127047edmesh/merge-gate: PASS — every machine composes with the change as it did without (4 of 4 compose) (modules: mesh-tools, node-tools)mesh/repo-check: PASS — THE CHANGE ALTERS ITS OWN CHECK (merge-check.sh): main's version judged it; the change's judges the pull requests after it merges; its merge-check.sh passedDelivery plan — builds mesh-tools, node-tools → ace, g14, novox, shanks; no bus step
Run by the build seat on shanks as
build-1791536953101740357(builds --log build-1791536953101740357).