jschoubben
a479a90fb2
The tool runner unmarshalled the state's value straight into its membership; the grants part had written its wrapper there, so every module decoded empty, was marked as given by the grants part, and the correct copy on the assignments stream was passed over: novox served no tool. followGrants now reads with membership.BareGrantsMembership, which takes the bare membership, still takes the old wrapper (what the live mesh holds until the part writes again), and refuses a value naming no node or module, leaving the stream's copy in force. The fixture IssueInGrants built its value by hand from this package's type and so agreed with the mistake; it now writes through mesh-sdk's encoder, and IssueInGrantsWrapped writes the old wrapper for one integration test that proves tools and state are served from it (it fails without this fix with the empty membership seen live). Issue 774 (the bus login list, L3). Quick fix: unwrap here alone. Thorough, chosen: one codec in mesh-sdk the writer and this reader share, so the two cannot drift again. Pins mesh-sdk at the head of its fix/memberships-shape.
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.