@camstack/system 1.1.52 → 1.1.54

package/dist/{manifest-python-deps-CIyvuHAB.mjs → manifest-python-deps-CWom-eqp.mjs}

@@ -1,4 +1,4 @@
-import { K as readNodePin } from "./dist-B_PSvr-m.mjs";
+import { K as readNodePin } from "./dist-DssImRC5.mjs";
 import { ensureBinary, ensureFfmpeg, ensurePython, installPythonPackages, installPythonRequirements } from "@camstack/types/node";
 import { createServer } from "node:http";
 import * as fs from "node:fs";
@@ -6619,6 +6619,20 @@ var brokerReadinessRegistries = /* @__PURE__ */ new WeakMap();
 */
 var clientReadinessRegistries = /* @__PURE__ */ new Map();
 /**
+* Fixed-period authoritative snapshot re-pull (D8 reconcile). Readiness
+* deltas are telemetry — lossy across the UDS/Moleculer hops — and the
+* on-(re)connect hydrate alone cannot repair a delta lost while
+* CONNECTED (2026-07-17: the agent's platform-probe `ready` never
+* reached the detection runner child; the child held `starting` forever
+* and every waiter wedged). With `ReadinessRegistry.hydrate` able to
+* ADVANCE stale records, this periodic re-pull bounds the damage of any
+* lost delta to one reconcile round. Not a retry backoff — a
+* steady-state reconcile against the authority. `unref()`d so the timer
+* never keeps a process alive; registries are process-lifetime, so the
+* interval is never cleared.
+*/
+var READINESS_RECONCILE_INTERVAL_MS = 6e4;
+/**
 * Return the shared ReadinessRegistry for this broker — one per
 * process is enough. Every addon context on the same broker gets the
 * same instance via `ctx.kernel.readinessRegistry`.
@@ -6669,6 +6683,10 @@ function getOrInitReadinessRegistry(broker, eventBus, logger) {
 			}, 200);
 		};
 		bkr.localBus.on("$services.changed", scheduleRehydrate);
+		const reconcileTimer = setInterval(() => {
+			hydrateFromHub();
+		}, READINESS_RECONCILE_INTERVAL_MS);
+		if (typeof reconcileTimer.unref === "function") reconcileTimer.unref();
 	}
 	return registry;
 }
@@ -6687,14 +6705,18 @@ function getOrInitReadinessRegistry(broker, eventBus, logger) {
 *     (Phase C) — the registry ingests them through its own event-bus
 *     subscription, exactly as in broker mode.
 *
-* **No `$services.changed` reconcile signal needed:**
-*   The broker-mode `$services.changed` reconcile existed because Moleculer
-*   broadcasts can be dropped during the boot window. Over UDS the parent
-*   reliably forwards every `system.ready-state` delta to each child (via
-*   the event bridge wired in Phase C). Dropped deltas are not a concern;
-*   the initial snapshot + live event bus is sufficient. A new
-*   parent-to-child "topology changed, re-pull" signal is therefore NOT
-*   added — it would be redundant and would complicate the protocol.
+* **Periodic reconcile (D8):**
+*   The original design assumed the parent reliably forwards every
+*   `system.ready-state` delta over UDS, so no reconcile signal beyond
+*   the (re)connect hydrate was added. The 2026-07-17 incident disproved
+*   the assumption end-to-end: a delta can be lost across the full
+*   producer→parent→child path (restart churn, subscription races), and
+*   a child that saw `starting` then never got `ready` wedged forever.
+*   The registry therefore ALSO re-pulls the parent snapshot every
+*   `READINESS_RECONCILE_INTERVAL_MS` while connected — combined with
+*   `hydrate`'s advance semantics, a lost delta costs one reconcile
+*   round, never forever. No new parent-to-child protocol message is
+*   needed (the existing snapshot request is reused).
 *
 * **`awaitReady`/`acquireCapability`/`onReadyState` semantics unchanged.**
 *
@@ -6725,6 +6747,10 @@ function getOrInitReadinessRegistryForClient(client, eventBus, logger, nodeId) {
 		hydrateFromParent();
 	});
 	if (client.isConnected) hydrateFromParent();
+	const reconcileTimer = setInterval(() => {
+		if (client.isConnected) hydrateFromParent();
+	}, READINESS_RECONCILE_INTERVAL_MS);
+	if (typeof reconcileTimer.unref === "function") reconcileTimer.unref();
 	return registry;
 }
 //#endregion

package/dist/{manifest-python-deps-CPAMH5gV.js → manifest-python-deps-kkvku9yU.js}

@@ -1,5 +1,5 @@
 const require_chunk = require("./chunk-Cek0wNdY.js");
-const require_dist = require("./dist-BduBhv6N.js");
+const require_dist = require("./dist-B5C4dVvO.js");
 let _camstack_types_node = require("@camstack/types/node");
 let node_http = require("node:http");
 let node_fs = require("node:fs");
@@ -6621,6 +6621,20 @@ var brokerReadinessRegistries = /* @__PURE__ */ new WeakMap();
 */
 var clientReadinessRegistries = /* @__PURE__ */ new Map();
 /**
+* Fixed-period authoritative snapshot re-pull (D8 reconcile). Readiness
+* deltas are telemetry — lossy across the UDS/Moleculer hops — and the
+* on-(re)connect hydrate alone cannot repair a delta lost while
+* CONNECTED (2026-07-17: the agent's platform-probe `ready` never
+* reached the detection runner child; the child held `starting` forever
+* and every waiter wedged). With `ReadinessRegistry.hydrate` able to
+* ADVANCE stale records, this periodic re-pull bounds the damage of any
+* lost delta to one reconcile round. Not a retry backoff — a
+* steady-state reconcile against the authority. `unref()`d so the timer
+* never keeps a process alive; registries are process-lifetime, so the
+* interval is never cleared.
+*/
+var READINESS_RECONCILE_INTERVAL_MS = 6e4;
+/**
 * Return the shared ReadinessRegistry for this broker — one per
 * process is enough. Every addon context on the same broker gets the
 * same instance via `ctx.kernel.readinessRegistry`.
@@ -6671,6 +6685,10 @@ function getOrInitReadinessRegistry(broker, eventBus, logger) {
 			}, 200);
 		};
 		bkr.localBus.on("$services.changed", scheduleRehydrate);
+		const reconcileTimer = setInterval(() => {
+			hydrateFromHub();
+		}, READINESS_RECONCILE_INTERVAL_MS);
+		if (typeof reconcileTimer.unref === "function") reconcileTimer.unref();
 	}
 	return registry;
 }
@@ -6689,14 +6707,18 @@ function getOrInitReadinessRegistry(broker, eventBus, logger) {
 *     (Phase C) — the registry ingests them through its own event-bus
 *     subscription, exactly as in broker mode.
 *
-* **No `$services.changed` reconcile signal needed:**
-*   The broker-mode `$services.changed` reconcile existed because Moleculer
-*   broadcasts can be dropped during the boot window. Over UDS the parent
-*   reliably forwards every `system.ready-state` delta to each child (via
-*   the event bridge wired in Phase C). Dropped deltas are not a concern;
-*   the initial snapshot + live event bus is sufficient. A new
-*   parent-to-child "topology changed, re-pull" signal is therefore NOT
-*   added — it would be redundant and would complicate the protocol.
+* **Periodic reconcile (D8):**
+*   The original design assumed the parent reliably forwards every
+*   `system.ready-state` delta over UDS, so no reconcile signal beyond
+*   the (re)connect hydrate was added. The 2026-07-17 incident disproved
+*   the assumption end-to-end: a delta can be lost across the full
+*   producer→parent→child path (restart churn, subscription races), and
+*   a child that saw `starting` then never got `ready` wedged forever.
+*   The registry therefore ALSO re-pulls the parent snapshot every
+*   `READINESS_RECONCILE_INTERVAL_MS` while connected — combined with
+*   `hydrate`'s advance semantics, a lost delta costs one reconcile
+*   round, never forever. No new parent-to-child protocol message is
+*   needed (the existing snapshot request is reused).
 *
 * **`awaitReady`/`acquireCapability`/`onReadyState` semantics unchanged.**
 *
@@ -6727,6 +6749,10 @@ function getOrInitReadinessRegistryForClient(client, eventBus, logger, nodeId) {
 		hydrateFromParent();
 	});
 	if (client.isConnected) hydrateFromParent();
+	const reconcileTimer = setInterval(() => {
+		if (client.isConnected) hydrateFromParent();
+	}, READINESS_RECONCILE_INTERVAL_MS);
+	if (typeof reconcileTimer.unref === "function") reconcileTimer.unref();
 	return registry;
 }
 //#endregion

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@camstack/system",
-  "version": "1.1.52",
+  "version": "1.1.54",
   "description": "Core addon for CamStack — builtins, pipeline, process management, auth, logging, events",
   "keywords": [
     "camstack",
@@ -156,7 +156,7 @@
         "id": "virtual-doorbell",
         "category": "system",
         "name": "Virtual Doorbell",
-        "description": "Wrapper over the `doorbell` cap — turns any binary-ish device (contact sensor, switch, event emitter, flood/gas/CO sensor) into a per-camera doorbell. Operator binds it per camera and picks the source device + trigger in the camera's settings.",
+        "description": "Wrapper over the `doorbell` cap — turns any binary sensor or switch (contact, motion, flood/gas/CO/smoke, vibration, tamper, or a switch) into a per-camera doorbell. Operator binds it per camera and picks the trigger devices from a searchable list in the camera's general settings; the reaction is automatic (sensor active / switch on).",
         "entry": "./dist/builtins/doorbell/index.js",
         "capabilities": [
           {