Files

T

jschoubben 331fa06b54 The tool runner reads the memberships state again until it can, instead of giving a module up at its one follow

A JetStream 503 or a timeout at the follow (a bus right after its boot) left the module with no membership for good, since
Follow runs once per module and the stream fallback is gone. The read is now tried again with a growing wait (1 s doubling
to 30 s) until it watches the key or the connection closes; the failure is said once, and its reading once it succeeds.
Tests: none added; a step added to an existing unit test (TestAModuleHearsEveryStreamItsMembershipNames), which fails
without the retry.

(issue 774, 774/S32, review g1 round 1)
Claude-Session: https://claude.ai/code/session_01NcbgfJ9Gum47zkFKWRaovL

2026-11-02 00:51:19 +01:00

cmd/node-tools

node-tools: start no bundle again once the runtime itself is stopping (issue 1126)

2026-10-28 15:30:12 +01:00

internal

The tool runner reads the memberships state again until it can, instead of giving a module up at its one follow

2026-11-02 00:51:19 +01:00

src

Let the TypeScript mesh client take every role's tools from the console on its machine, so it asks the controller for none (issue 1955, ADR 0571 clause 5)

2026-10-29 23:19:55 +01:00

test

Let the TypeScript mesh client take every role's tools from the console on its machine, so it asks the controller for none (issue 1955, ADR 0571 clause 5)

2026-10-29 23:19:55 +01:00

go.mod

Pin group A's mesh-sdk head on main

2026-11-01 09:57:49 +01:00

go.sum

Pin group A's mesh-sdk head on main

2026-11-01 09:57:49 +01:00

module.json

node-tools waits on the self-check's checked, not the controller's (ADR 0571 clause 13, issue 1955)

2026-11-01 09:54:39 +01:00

package-lock.json

Bring node-tools' lock back in step with package.json, and fail the check when it falls behind (hq issue 624)

2026-10-13 15:12:10 +02:00

package.json

Give the TypeScript toolchain pg, mongodb and mssql, so a catalogue check can type-check the modules that use them (issue 385)

2026-10-12 12:27:46 +02:00

README.md

node-tools is a module beside mesh-tools: the runtime as a bundle, and serve is the console (hq ADR 0175, to-be 38 WP3)

2026-10-02 21:43:37 +02:00

tsconfig.json

node-tools is a module beside mesh-tools: the runtime as a bundle, and serve is the console (hq ADR 0175, to-be 38 WP3)

2026-10-02 21:43:37 +02:00

README.md

node-tools

The node's tool runtime as a module (novox/hq ADR 0175, to-be 38 WP3). Assigned to a machine, it is one process the host runs from this bundle, as the operator's account: it serves every assigned module's tools and every held seat's verbs on the bus, and answers MCP on the machine's loopback — the console (design 34). The controller composes the process (which bundles to load, where the credential is, whose machine it is); this manifest says only what the machine must have for it: the interpreter, a place for the credential, the loopback port, and leave to call every tool.

The code is the mesh-tools package in this directory; the module at the repository root, mesh-tools, builds the images TypeScript bundles are compiled in. See the repository README.