mesh-tools

5 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
mesh-tools	33d136e702	Feature 57 (config and provisioning): release mesh-tools (the provider's StateBus, the SDK pin, templates), reviewed mesh/merge-gate head 33d136e70227 merged into trunk 6b3e15042fee — pass, with a note: builds mesh-tools, node-tools (+40 dependent(s)) → ace, g14, novox, s… Details mesh/repo-check head 33d136e70227 merged into trunk 6b3e15042fee — pass: THE CHANGE ALTERS ITS OWN CHECK (merge-check.sh): main's version judged it; the ch… Details mesh/delivery delivered Details	2026-10-16 09:41:17 +00:00
jochen	d535dd5322	Serve a module's log verbs so its record outlives a bucket's cap and the events' week (ADR 0297, issues 501, 502) mesh/delivery superseded: a newer head of the same pull request Details mesh/merge-gate pass: builds mesh-tools, node-tools → ace, g14, novox, shanks; no bus step; every machine composes with the change as it did without (4 of … Details mesh/repo-check pass: THE CHANGE ALTERS ITS OWN CHECK (merge-check.sh): main's version judged it; the change's judges the pull requests after it merges; it… Details The runtime answers mesh/log.append, read, last and info for a log issued in the module's membership, by publish, batch direct get and stream info alone. A stale expect is refused as a lost state update, so a module tells it by the same code.	2026-10-11 19:18:46 +02:00
jochen	6d9906b6c9	Carry a bundle's seat traffic under its own name and kind, and start a module as its own account (hq ADR 0259)	2026-10-09 10:12:39 +02:00
jochen	1792b0d9ba	node-tools: say whose words a refused event is (hq issue 276) "plex did not take radarr.download.completed: Unexpected end of JSON input" read as the runtime failing to parse the bundle's answer. It was plex's own handler error, relayed. A bundle's error answer is now a launch.Refused, and the line says the handler answered an error, quotes it, names the event id and the delay before the next offer; the runtime's own failures (no answer in time, bundle exited) are said as before. The rule, unchanged and now tested: any mesh/event answer that is not an error takes the event, whatever its result says, including none.	2026-10-06 18:14:50 +02:00