jochen
1eaa1abbe9
The issues module will hand out numbers through mesh/state.create and update. Two writers incrementing one counter a thousand times each through the module's bus now end at two thousand with every number handed out once; a stale, zero or future revision is refused with the lost-write code and writes nothing; a deleted key can be created again; and the lost-write code reaches a bundle wrapped or not, and no other refusal carries it. Both runtime tests run in the check's bundleless list, so mesh/repo-check runs them. Part of the issue tracker decision, hq research 042.
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.