When a module's ledger binding came or went, refreshRepairs stopped every subscription of its tools and served them all again, so a call in that gap was dropped the same way as on a membership (H-A-158). serve is now the one routine that changes a module's subscriptions, by tool address: it keeps those still named, subscribes the new, then stops those no longer named; refreshRepairs and the first serve both go through it, so no tool is served twice or not at all. The ledger test's later binding now comes and goes ten times, and the module's own tool must answer the first call after each, within the tests' 2 s bound; it failed without the change at GOMAXPROCS=1 and 24. Builds: design 47 H §774, H-A-158, H-A-160; principle 11
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.