jochen
52e275ad2f
The lab installs node-tools with npm ci, which refuses a lock that no longer describes package.json; the SDK's range and the toolchain's development dependencies had moved in package.json alone, so every lab run stopped at setup. The image's build runs npm install and never read the lock, so nothing noticed.
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.