jschoubben
816df217cd
The checker's fetch pins only the zero-version requirements a directory's go.mod names (mesh-build-go workspace.go goModOf), so a module reached only through another, such as meshhandacts through meshhandactsclient or mesh-delivery-sdk through meshcatalogclient, was never downloaded and the shut-off load failed (fetch.go:267). The join's merges had dropped these indirect requirements that the trunk's go.mod files list. Builds: design 47 G (join 11, the check's fetch of the group's modules) 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.