jschoubben
28bece26b0
The tests of A-249 and A-257 served the verb on one connection and asked it from another at once; the subscription was still in the holder's buffer when the ask reached the bus, so the ask was answered 503 no responders (13 of 300 runs with -cpu 1 before, 0 of 2000 after). The runner flushes after serving (runtime.go:352, :807); the tests now do as it does. Builds: design 47 G A-249, A-257 Claude-Session: https://claude.ai/code/session_01NcbgfGKaxw984XyAPfLm4h
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 mesh 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.