5 Commits

Include renames

Author	SHA1	Message	Date
mesh-tools	1bc5719b8b	Feature 57 (config and provisioning): release mesh-sdk, the reviewed release branch on top of main	2026-10-16 08:24:11 +00:00
jochen	096c5562a4	A module's state through the runtime, in TypeScript and Go (novox/hq ADR 0201) ... state(name) / stdio.State(name): get, put, delete, keys and watch over the runtime's mesh/state verbs. A watch's handler is registered under the id it is asked with, so its current values — which arrive before the watch is answered — and its changes reach it and no other watch.	2026-10-04 02:47:31 +02:00
jschoubben	9b7817c8ca	Resync hq ADR references 0044-0054 -> 0039-0049 after the hq record reconciliation	2026-09-05 12:44:17 +02:00
jschoubben	f335bfb9e7	events: modules log activity to the broker, any module reacts ... The lighter sibling of provisioning — 1:many and broadcast, no credential, just the broker's topic routing. A thin, audit-ready surface over the broker's publish/subscribe: - emit(type, body): publishes an Event carrying who emitted it (MESH_MODULE), on which node (MESH_NODE) and when (ISO timestamp) — so a listener can build a real audit trail. - on(pattern, handler): react to events by topic pattern. The audit logger is just on("#", ...). Tested: a module emits; a targeted listener (module.umami.#) hears only its events, the audit sink (#) hears every module's, and the metadata audit needs is present. The declared side — a manifest's emits/consumes, so the mesh knows the event graph — and the audit-logger module are the next pieces. Claude-Session: https://claude.ai/code/session_01LrgweAeERJYBg88c5cKDzF	2026-09-03 23:28:38 +02:00
jschoubben	a19a2f5cf0	Stand up mesh-sdk — the stable spine a module builds against ... Per novox/hq ADR 0044/0045: the sdk holds only what rarely changes and is shared across modules; per-module code (a client, tool impls, a create-a-resource adapter) lives in the module. Five areas, real and tested: - contracts: the runtime shapes module code touches (grant, credential, a mesh Interface, tool + envelope types) — not the manifest schema, which the control plane owns. - provisioner: the reconcile harness every provider shares (watch grants, create via the module's adapter, seal + write the credential, remove on withdrawal). A module writes only the adapter. - tools: registerModuleTools + collectTools — the serving harness; tools and their client live in the module. - messaging: the Broker/Envelope/event contract over the mesh broker; the concrete binding is provided by the hosting runtime. - primitives: AES-256-GCM seal/unseal, semver, resolved-env access. Compiles (tsc, NodeNext) and passes tests: sealing round-trip + wrong-key rejection, semver, tool registration (a thrower is skipped not fatal), and the provisioner creating then removing a sealed grant. Claude-Session: https://claude.ai/code/session_01LrgweAeERJYBg88c5cKDzF	2026-09-03 23:01:59 +02:00