10 Commits

Include renames

Author	SHA1	Message	Date
jschoubben	54680238a0	Read memberships from the grants part's state, what the mesh holds from the indexer and placement, and give bundles newest, since and watch on logs, so the tool runner asks the controller for nothing it keeps (issue 1955, ADR 0571 clauses 1, 4, 5, 7) ... Pins mesh-sdk bb993dd. The assignments stream stays the membership's fallback until the lease write; a log another module keeps is read as <module>.<log>.	2026-10-29 23:42:43 +01:00
jschoubben	67850457ef	Read seat verbs' replaces from mesh-sdk's seat contract and seat holders from placement's seat-holders state, so the console asks the controller for neither (issue 1955, ADR 0571 clauses 4 and 5) ... Pins mesh-sdk f9a496d. The controller's nodes and modules reads remain.	2026-10-29 23:13:42 +01:00
jschoubben	9d67b0995f	Bind node-tools' consumers by mesh-provisioner's plans and provisions alone, dropping the read of the controller's assignments the sdk's helper no longer makes (issue 1954 L6-T1) ... Pins mesh-sdk 692dbf9 (L6-P3).	2026-10-29 22:43:58 +01:00
jschoubben	9fc97e45c9	Let node-tools' provider helper read mesh-provisioner's provisions and plans by mesh-sdk's names, so the runtime follows ADR 0570's records off the controller (issue 1954 L6-T1) ... Pins mesh-sdk 4a96793 (go/provisions). The assignments read stays while the sdk's helper still reads plans there (until L6-P3). A watch's expire now reads as a removed key.	2026-10-29 22:34:34 +01:00
jschoubben	1583fa85d9	Let a bundle write a state key with its own time to live and hear its end, so wakes need no in-process timer (issue 1952) ... mesh/state.create and mesh/state.put take ttl_seconds (mesh-sdk 32f5ce3's CreateTTL/RenewTTL contract); a bucket not declared key-ttl is refused, naming it; a watch hands an expired key as op "expire". Pins mesh-sdk 32f5ce3.	2026-10-29 22:11:39 +01:00
jschoubben	860043fd7f	Pin mesh-sdk at feat/r4g's head a2c813a6, its test fixture fix, with go.sum tidied	2026-10-23 17:06:12 +02:00
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