4 Commits

Include renames

Author	SHA1	Message	Date
jschoubben	3b5a38e4a4	Pin mesh-sdk at feat/r4g's head 9205222a, the merge of lanes A, B, S8 and F1, so every module r4g touches builds against one SDK ... go.sum gains its lines from go mod tidy once mesh-sdk feat/r4g is pushed.	2026-10-23 16:22:02 +02:00
mesh-tools	33d136e702	Feature 57 (config and provisioning): release mesh-tools (the provider's StateBus, the SDK pin, templates), reviewed	2026-10-16 09:41:17 +00:00
jochen	14bff5dfd7	Check the tool runtime's own code before it merges, every test on a bus of its own (hq ADR 0237) ... A merge-check.sh, the repository's layer of the mesh's merge check (mesh/repo-check): format, vet, and node-tools' suite under the race detector. The tests shared one bus and had to run one package at a time; like the controller's (#97), each now starts a server of its own at the release go.mod pins, held to the catalogue's bus image by a test. What cannot run in the check — bundles that need @novox/mesh-sdk — is said as not tested.	2026-10-06 22:04:46 +02:00
jochen	e45389f75a	node-tools in Go: the node's runtime, launch-only, wire-compatible with the TypeScript (hq ADR 0193) ... The runtime knows no language, so nothing ties it to Node.js. This ports its serve mode — the pinned bus connection and patient connect, following memberships, launching every served bundle over MCP on stdio with its own environment, a child's emit published as its module, each tool, the tools verb and seat verbs served where the mesh issued them, and the console on loopback — to one static binary. Same subjects, request and reply bodies, event headers and MCP answers. The TypeScript stays: it is still the runtime inside the per-module containers until WP4c. Tests run against a real bus and share the TypeScript fixtures.	2026-10-03 21:21:52 +02:00