@camstack/server 1.2.34 → 1.2.36

package/dist/core/addon/addon-registry.service.js

@@ -2261,11 +2261,41 @@ class AddonRegistryService {
                     if (!provider)
                         return;
                     this.activeSettingsBackend = provider;
-                    if (isSettingsStore(provider)) {
-                        this.configService.setSettingsStore(provider);
+                    // ConfigManager needs the SYNC legacy surface (`getAllAddon`,
+                    // `setAddonDevice`, …), which is not part of the cap. Since D44 the
+                    // `settings-store` provider is the storage-orchestrator's
+                    // DISPATCHER, and a dispatcher has none of those methods — so this
+                    // predicate started returning false and ConfigManager was left
+                    // without a store. Nothing said so: `readAddonStore()` then answered
+                    // `{}` for every addon, device-manager restored ZERO devices, and no
+                    // camera published a stream. Fall back to the ENGINE behind the door
+                    // (`data-store-provider` — the SQLite backend does implement both
+                    // surfaces), the same move `storage-orchestrator` makes for its
+                    // location store. And if neither can serve it, SAY SO: this is the
+                    // branch whose silence cost an evening.
+                    const syncStore = isSettingsStore(provider)
+                        ? provider
+                        : this.capabilityRegistry
+                            .getCollection('data-store-provider')
+                            .find((engine) => isSettingsStore(engine));
+                    if (syncStore) {
+                        this.configService.setSettingsStore(syncStore);
+                    }
+                    else {
+                        this.logger.error('settings-store provider does not implement the sync ConfigManager surface and no data-store-provider engine does either — every addon store reads empty, devices will NOT be restored', { meta: { addonId, phase: 'v2' } });
                     }
                     this.storageService.setSettingsBackend(provider);
-                    this.integrationRegistry = new system_4.IntegrationRegistry(provider);
+                    // The registry needs the DOOR's own shape, not `ISettingsBackend`.
+                    // `CapabilityProviderMap` still types this cap as the hand-written
+                    // interface, which has drifted from the cap definition it is meant
+                    // to describe — it never grew `deleteWhere` / `updateWhere`. The
+                    // same provider object satisfies both; reconciling the two types is
+                    // its own change (it makes `query` / `insert` non-generic for every
+                    // `ISettingsBackend` consumer in the backend).
+                    const store = this.capabilityRegistry.getProviderByAddon('settings-store', addonId);
+                    if (!store)
+                        return;
+                    this.integrationRegistry = new system_4.IntegrationRegistry(store);
                     void this.integrationRegistry.initialize().then(() => {
                         this.logger.info('IntegrationRegistry initialized', { meta: { phase: 'v2' } });
                     });

package/dist/launcher.js

@@ -413,6 +413,28 @@ async function launch() {
         Module._initPaths();
         console.log(`[launcher] NODE_PATH extended with: ${extraNodePaths.join(sep)}`);
     }
+    // WHICH COPY did this node just commit to? ([D45](../../../docs/decisions/adr-0045.md))
+    //
+    // A node can hold several copies of a host-provided package — the image seed
+    // under /opt, a legacy /data/framework on NODE_PATH, the active closure, an
+    // installed copy under /data/addons. Which one wins is a resolution outcome,
+    // and on 2026-08-03 three consecutive deductions about it were each disproved
+    // by the next measurement, while every status surface reported the version of
+    // a copy nobody was running. Resolution happens HERE, right after NODE_PATH
+    // is final and before the runtime imports anything — so this is the one place
+    // that can answer it, and it costs a stat call per package.
+    //
+    // A version number without a path is not evidence. Log both.
+    for (const pkg of ['@camstack/system', '@camstack/types']) {
+        try {
+            const resolved = require.resolve(`${pkg}/package.json`);
+            const version = JSON.parse(fs.readFileSync(resolved, 'utf-8')).version;
+            console.log(`[launcher] resolved ${pkg}@${String(version)} from ${resolved}`);
+        }
+        catch (err) {
+            console.warn(`[launcher] could NOT resolve ${pkg}: ${err instanceof Error ? err.message : String(err)}`);
+        }
+    }
     // Now safe to load the role's runtime entry (both have static imports from
     // @camstack/system, resolved only after the framework dir + NODE_PATH setup
     // above). The agent boots from THIS same @camstack/server closure — there is

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@camstack/server",
-  "version": "1.2.34",
+  "version": "1.2.36",
   "private": false,
   "files": [
     "dist",
@@ -40,11 +40,11 @@
     "@camstack/addon-notifiers": "1.2.11",
     "@camstack/addon-pipeline": "1.2.39",
     "@camstack/addon-pipeline-orchestrator": "1.2.19",
-    "@camstack/addon-post-analysis": "1.2.23",
+    "@camstack/addon-post-analysis": "1.2.24",
     "@camstack/sdk": "1.2.9",
     "@camstack/shm-ring": "1.1.9",
-    "@camstack/system": "1.2.30",
-    "@camstack/types": "1.2.22",
+    "@camstack/system": "1.2.31",
+    "@camstack/types": "1.2.23",
     "@camstack/ui-library": "1.2.18",
     "@fastify/compress": "^9.0.0",
     "@fastify/cookie": "^11.0.2",