node-tools: a tool call names its caller, and the module is told it from the subject (hq issue 365) #27

Merged
mesh-admin merged 2 commits from fix/365-a-tool-call-names-its-caller into main 2026-10-11 09:31:41 +00:00
Contributor

Fixes the tool-runner part of hq issue 365: a module is never told who called its tool. Built to the issue's decision (2026-10-11 02:37), by ADR 0259 section 3's precedent for asks.

Subjects. Each tool and seat verb is also served on its caller-named subject: mesh.mod.<m>.call.<tool>[.<node>].<caller>, mesh.seat.<s>.call.<verb>[.<node>].<caller>. The caller token is the publishing bus user, dots written ~ (shanks~node-tools, person~jochen), which no part of a user's name may hold. A kind of its own, call, rather than the tool subject with a token appended: every existing grant to call a tool is a wildcard over tool (.tool.<t>.* for @node addressing, mesh.mod.*.tool.>), which would match any caller appended, so a caller could name another. Under call only the caller-named grants (mesh-controller, same branch) reach the last token.

Serving. HandleCalled / HandleSubjectCalled answer the subject and its caller-named pattern in one queue; the caller is taken from the subject the call arrived on (callerOn), never from the body, and handed to the bundle in the tools/call's _meta (mesh/caller, read by mesh-sdk's stdio.CallerOf). The old subject is still served for one release and hands no caller (the module says unproven); its retirement is hq issue 464.

Calling. Every call through the runtime (Conn.Ask: the console's MCP calls and modules' invokes via AskAs) asks the caller-named subject first, as its own bus user, and the old subject only when the first reached nobody: no responders (a runtime or holder from before this, or the controller's own seat, which moves with issue 464), or the bus refused the publish (grant not delivered yet). The refusal ends the call at once rather than after the 30 s request timeout, so the order of roll-out never strands a caller. A call that reached a responder is never asked twice.

Tests (fail first). internal/runtime/caller_test.go with a Python fixture bundle (no SDK): a call on the caller-named subject reaches the module with that caller, for a tool, its @node address and a seat verb, while a caller and a _meta in the arguments arrive only as arguments (fails on main: caller ""); the old subjects still work and name no caller. internal/bus: subject shapes and caller parsing; fall-back at once where nothing serves the new subject; fall-back at once when the bus refuses the publish (said in the log); with the controller's grant a caller is heard as itself and the bus refuses one naming another. sh merge-check.sh passes, including the bundle suites with the TypeScript SDK present (race detector on).

Not changed: node-tools/src (TypeScript, not what nodes run; listed in issue 464).

Companion pull requests, branch fix/365-a-tool-call-names-its-caller: mesh-sdk#20 (CallerOf), mesh-controller (grants), mesh-catalog (mesh-issues reads the caller). Roll after the controller's grants are delivered to the bus, though the refusal fall-back keeps calls working either way.

Fixes the tool-runner part of hq issue 365: a module is never told who called its tool. Built to the issue's decision (2026-10-11 02:37), by ADR 0259 section 3's precedent for asks. **Subjects.** Each tool and seat verb is also served on its caller-named subject: `mesh.mod.<m>.call.<tool>[.<node>].<caller>`, `mesh.seat.<s>.call.<verb>[.<node>].<caller>`. The caller token is the publishing bus user, dots written `~` (`shanks~node-tools`, `person~jochen`), which no part of a user's name may hold. **A kind of its own, `call`, rather than the `tool` subject with a token appended**: every existing grant to call a tool is a wildcard over `tool` (`.tool.<t>.*` for @node addressing, `mesh.mod.*.tool.>`), which would match any caller appended, so a caller could name another. Under `call` only the caller-named grants (mesh-controller, same branch) reach the last token. **Serving.** `HandleCalled` / `HandleSubjectCalled` answer the subject and its caller-named pattern in one queue; the caller is taken from the subject the call arrived on (`callerOn`), never from the body, and handed to the bundle in the `tools/call`'s `_meta` (`mesh/caller`, read by mesh-sdk's `stdio.CallerOf`). The old subject is still served for one release and hands no caller (the module says `unproven`); its retirement is hq issue 464. **Calling.** Every call through the runtime (`Conn.Ask`: the console's MCP calls and modules' invokes via `AskAs`) asks the caller-named subject first, as its own bus user, and the old subject only when the first reached nobody: no responders (a runtime or holder from before this, or the controller's own seat, which moves with issue 464), or the bus refused the publish (grant not delivered yet). The refusal ends the call at once rather than after the 30 s request timeout, so the order of roll-out never strands a caller. A call that reached a responder is never asked twice. **Tests (fail first).** internal/runtime/caller_test.go with a Python fixture bundle (no SDK): a call on the caller-named subject reaches the module with that caller, for a tool, its @node address and a seat verb, while a caller and a `_meta` in the arguments arrive only as arguments (fails on main: caller ""); the old subjects still work and name no caller. internal/bus: subject shapes and caller parsing; fall-back at once where nothing serves the new subject; fall-back at once when the bus refuses the publish (said in the log); with the controller's grant a caller is heard as itself and the bus refuses one naming another. `sh merge-check.sh` passes, including the bundle suites with the TypeScript SDK present (race detector on). **Not changed:** node-tools/src (TypeScript, not what nodes run; listed in issue 464). Companion pull requests, branch fix/365-a-tool-call-names-its-caller: mesh-sdk#20 (CallerOf), mesh-controller (grants), mesh-catalog (mesh-issues reads the caller). Roll after the controller's grants are delivered to the bus, though the refusal fall-back keeps calls working either way.
mesh-admin added 1 commit 2026-10-11 03:26:07 +00:00
node-tools: a tool call names its caller, and the module is told it from the subject (hq issue 365)
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/delivery-group group fix/365-a-tool-call-names-its-caller delivering: 0 of 4 delivered
mesh/delivery superseded: a newer head of the same pull request
ab0f888d67
Each tool and seat verb is also served on its caller-named subject, kind call
with the caller's bus user last, which the controller grants each user with its
own name alone; the runtime hands the module that caller in the call's _meta,
never from the body. Calls through the runtime (the console and modules'
invokes) ask the caller-named subject first and the old one only when the first
reached nobody: nothing serves it yet, or the bus refused it because the grant
is not delivered yet, which ends the call at once rather than after 30 s. The
old subjects stay served and say no caller for one release (hq issue 464).
Author
Contributor

Delivery novox/mesh-tools@541de48e040f — delivered since 2026-10-11T09:51:47Z

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

Machines

  • mesh-controller on novox: passed — healthy 3 times over 4m7s
  • mesh-controller on the rest running it: sent
  • build-agent on ace: passed — healthy 3 times over 3m24s
  • build-agent on the rest running it: sent
  • node-tools on ace: passed — judged with mesh-host: healthy 3 times over 3m43s
  • mesh-host on ace: passed — healthy 3 times over 3m43s
  • mesh-tools on every machine running it: sent
  • route-proxy on ace: passed — judged with mesh-host: healthy 3 times over 3m43s
  • mesh-host on the rest running it: sent
  • node-tools on the rest running it: sent
  • route-proxy on the rest running it: sent

Transitions

  • 2026-10-11 09:22 (new) → proposed (announced): novox/mesh-tools#27's head announced
  • 2026-10-11 09:26 proposed → checked (checked): the verdict names this commit
  • 2026-10-11 09:26 checked → ready (accepted): the gate passed or warned, and the repository's own check did not fail
  • 2026-10-11 09:33 ready → published (merged): on the trunk its modules follow: merged there, and its walk opened — or nothing for a walk to move
  • 2026-10-11 09:33 published → delivering (go): its walk started: let go by this owner in its group's order, by a person, or on the controller's own path — not a failed walk that carried a later commit for it, after which it waits for a walk of its own commit
  • 2026-10-11 09:51 delivering → delivered (done): its walk is done, carrying its own commit: every machine of its deploy plan passed, or was left as its policy says

The commit's note under refs/notes/mesh-plan keeps every transition: git log --notes=mesh-plan.

<!-- mesh-delivery:view --> **Delivery** `novox/mesh-tools@541de48e040f` — **delivered** since 2026-10-11T09:51:47Z **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 **Machines** - mesh-controller on novox: passed — healthy 3 times over 4m7s - mesh-controller on the rest running it: sent - build-agent on ace: passed — healthy 3 times over 3m24s - build-agent on the rest running it: sent - node-tools on ace: passed — judged with mesh-host: healthy 3 times over 3m43s - mesh-host on ace: passed — healthy 3 times over 3m43s - mesh-tools on every machine running it: sent - route-proxy on ace: passed — judged with mesh-host: healthy 3 times over 3m43s - mesh-host on the rest running it: sent - node-tools on the rest running it: sent - route-proxy on the rest running it: sent **Transitions** - 2026-10-11 09:22 (new) → proposed (announced): novox/mesh-tools#27's head announced - 2026-10-11 09:26 proposed → checked (checked): the verdict names this commit - 2026-10-11 09:26 checked → ready (accepted): the gate passed or warned, and the repository's own check did not fail - 2026-10-11 09:33 ready → published (merged): on the trunk its modules follow: merged there, and its walk opened — or nothing for a walk to move - 2026-10-11 09:33 published → delivering (go): its walk started: let go by this owner in its group's order, by a person, or on the controller's own path — not a failed walk that carried a later commit for it, after which it waits for a walk of its own commit - 2026-10-11 09:51 delivering → delivered (done): its walk is done, carrying its own commit: every machine of its deploy plan passed, or was left as its policy says The commit's note under `refs/notes/mesh-plan` keeps every transition: `git log --notes=mesh-plan`.
Author
Contributor

Merge check at ab0f888d

  • 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-1791689172128218365 (builds --log build-1791689172128218365).

--- 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-11T03:09:01Z 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-11T03:09:01Z

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.191s
ok  	github.com/novox/mesh-tools/node-tools/internal/announce	4.361s
ok  	github.com/novox/mesh-tools/node-tools/internal/bus	12.362s
ok  	github.com/novox/mesh-tools/node-tools/internal/launch	1.090s
ok  	github.com/novox/mesh-tools/node-tools/internal/meshtest	1.125s
?   	github.com/novox/mesh-tools/node-tools/internal/wire	[no test files]
ok  	github.com/novox/mesh-tools/node-tools/internal/console	0.004s
ok  	github.com/novox/mesh-tools/node-tools/internal/runtime	1.418s
NOT TESTED HERE: node-tools/src (TypeScript) needs @novox/mesh-sdk from the package registry
**Merge check** at `ab0f888d` - `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-1791689172128218365` (`builds --log build-1791689172128218365`). ``` --- 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-11T03:09:01Z 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-11T03:09:01Z 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.191s ok github.com/novox/mesh-tools/node-tools/internal/announce 4.361s ok github.com/novox/mesh-tools/node-tools/internal/bus 12.362s ok github.com/novox/mesh-tools/node-tools/internal/launch 1.090s ok github.com/novox/mesh-tools/node-tools/internal/meshtest 1.125s ? github.com/novox/mesh-tools/node-tools/internal/wire [no test files] ok github.com/novox/mesh-tools/node-tools/internal/console 0.004s ok github.com/novox/mesh-tools/node-tools/internal/runtime 1.418s NOT TESTED HERE: node-tools/src (TypeScript) needs @novox/mesh-sdk from the package registry ```
Author
Contributor

Companions for hq issue 365: mesh-sdk#20, mesh-controller#224 (grants; roll before this), mesh-catalog#207. Merge order: mesh-sdk#20, mesh-controller#224, mesh-tools#27, mesh-catalog#207.

Companions for hq issue 365: mesh-sdk#20, mesh-controller#224 (grants; roll before this), mesh-catalog#207. Merge order: mesh-sdk#20, mesh-controller#224, mesh-tools#27, mesh-catalog#207.
jschoubben added 1 commit 2026-10-11 09:22:31 +00:00
node-tools: only a call pattern names a caller, and a fall-back for want of a responder is said (hq issue 365, review)
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/delivery delivered
541de48e04
callerOn reads a caller only under the call kind, so a tool subscription ending
in a wildcard never yields one. A caller-named call that reached nobody is said
once per subject before it is asked on the old subject, so a runtime or grant
that drifted behind is seen rather than a quiet unproven. The caller tests wait
for their bundle's exit, which reads the launcher's restart pauses another test
sets.
Author
Contributor

Merge check at 541de48e

  • 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 novox as build-1791710571852513082 (builds --log build-1791710571852513082).

--- 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-11T09:21:02Z 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-11T09:21:02Z

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.189s
ok  	github.com/novox/mesh-tools/node-tools/internal/announce	4.367s
ok  	github.com/novox/mesh-tools/node-tools/internal/bus	12.569s
ok  	github.com/novox/mesh-tools/node-tools/internal/launch	1.096s
ok  	github.com/novox/mesh-tools/node-tools/internal/meshtest	1.140s
?   	github.com/novox/mesh-tools/node-tools/internal/wire	[no test files]
ok  	github.com/novox/mesh-tools/node-tools/internal/console	0.005s
ok  	github.com/novox/mesh-tools/node-tools/internal/runtime	1.781s
NOT TESTED HERE: node-tools/src (TypeScript) needs @novox/mesh-sdk from the package registry
**Merge check** at `541de48e` - `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 novox as `build-1791710571852513082` (`builds --log build-1791710571852513082`). ``` --- 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-11T09:21:02Z 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-11T09:21:02Z 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.189s ok github.com/novox/mesh-tools/node-tools/internal/announce 4.367s ok github.com/novox/mesh-tools/node-tools/internal/bus 12.569s ok github.com/novox/mesh-tools/node-tools/internal/launch 1.096s ok github.com/novox/mesh-tools/node-tools/internal/meshtest 1.140s ? github.com/novox/mesh-tools/node-tools/internal/wire [no test files] ok github.com/novox/mesh-tools/node-tools/internal/console 0.005s ok github.com/novox/mesh-tools/node-tools/internal/runtime 1.781s NOT TESTED HERE: node-tools/src (TypeScript) needs @novox/mesh-sdk from the package registry ```
mesh-admin merged commit 336a2b1328 into main 2026-10-11 09:31:41 +00:00
mesh-admin deleted branch fix/365-a-tool-call-names-its-caller 2026-10-11 09:31:41 +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-tools#27