One SDK per runtime: a bundle's SDK import resolves to the runtime's copy (hq issue 209) #32

Merged
mesh-admin merged 1 commits from fix/issue-209-one-sdk-per-runtime into main 2026-10-03 11:07:08 +00:00
1 Commits
Author SHA1 Message Date
jochen 7152148410 One SDK per runtime: a bundle's SDK import resolves to the runtime's copy (hq issue 209)
A bundle carries its dependencies, the SDK among them; imported in-process that copy was a
second SDK with its own tool registry, so a bundle registered its tools into a list the
runtime never read and served nothing, silently. A resolve hook (module.registerHooks, in
thread; module.register is deprecated from Node 26) now sends every import of
@novox/mesh-sdk, from whichever bundle, to the runtime's own copy: one registry, one broker.
The test loads a bundle from a directory holding its own SDK copy and sees its tool served.
2026-10-03 13:00:19 +02:00