@camstack/system 1.2.87 → 1.2.89

package/dist/index.js

@@ -1,6 +1,6 @@
 Object.defineProperty(exports, Symbol.toStringTag, { value: "Module" });
 const require_chunk = require("./chunk-Cek0wNdY.js");
-const require_dist = require("./dist-D4nuaPdd.js");
+const require_dist = require("./dist-Dq0ebOuS.js");
 const require_builtins_alerts_alerts_addon = require("./builtins/alerts/alerts.addon.js");
 require("./builtins/alerts/index.js");
 const require_formatter = require("./formatter-DqAKDlvN.js");

package/dist/index.mjs

@@ -1,5 +1,5 @@
 import { a as __toCommonJS, i as __require, n as __esmMin, o as __toESM$1, r as __exportAll, t as __commonJSMin$1 } from "./chunk-CNf5ZN-e.mjs";
-import { $ as objectInputDeclaresAddonId, At as createEvent, B as isArrayOutputSchema, Bt as resolveCapMount, Dt as asJsonObject$1, G as kebabToCamel, H as isObjectInput, K as lifecycleJobSchema, Lt as parseJsonObject, Nt as expandCapMethods, Ot as asNumber, R as extractNestedAddonId, Rt as parseJsonUnknown$1, Tt as ReadinessTimeoutError, Ut as EventCategory$1, V as isCollectionArrayMethod, Vt as scopeKey, W as isVoidInput, X as looseSchema, Y as logLevelAtMost, at as scopesAllowDeviceCap, bt as DEVICE_STATUS_METHOD, d as METHOD_ACCESS_MAP, f as RUNTIME_DEFAULTS, gt as errMsg$1, it as scopesAllowAddon, jt as emitDownForOwnedCaps, kt as asString$1, nt as procedureAuthKey, t as ALL_CAPABILITY_DEFINITIONS, vt as DATAPLANE_SECRET_HEADER$1, wt as ReadinessRegistry, y as addonSettingsCapability, yt as DEVICE_SETTINGS_CONTRIBUTION_METHODS, zt as readinessKey } from "./dist-CuAaqtdt.mjs";
+import { $ as objectInputDeclaresAddonId, At as createEvent, B as isArrayOutputSchema, Bt as resolveCapMount, Dt as asJsonObject$1, G as kebabToCamel, H as isObjectInput, K as lifecycleJobSchema, Lt as parseJsonObject, Nt as expandCapMethods, Ot as asNumber, R as extractNestedAddonId, Rt as parseJsonUnknown$1, Tt as ReadinessTimeoutError, Ut as EventCategory$1, V as isCollectionArrayMethod, Vt as scopeKey, W as isVoidInput, X as looseSchema, Y as logLevelAtMost, at as scopesAllowDeviceCap, bt as DEVICE_STATUS_METHOD, d as METHOD_ACCESS_MAP, f as RUNTIME_DEFAULTS, gt as errMsg$1, it as scopesAllowAddon, jt as emitDownForOwnedCaps, kt as asString$1, nt as procedureAuthKey, t as ALL_CAPABILITY_DEFINITIONS, vt as DATAPLANE_SECRET_HEADER$1, wt as ReadinessRegistry, y as addonSettingsCapability, yt as DEVICE_SETTINGS_CONTRIBUTION_METHODS, zt as readinessKey } from "./dist-Bij6agsS.mjs";
 import { AlertCenterAddon } from "./builtins/alerts/alerts.addon.mjs";
 import "./builtins/alerts/index.mjs";
 import { t as formatLogLine } from "./formatter-B7qW8bPJ.mjs";

package/dist/kernel/moleculer/init-watchdog.d.ts

@@ -0,0 +1,60 @@
+/**
+ * The initialize() stall watchdog.
+ *
+ * ## What it is guarding
+ *
+ * A runner publishes its capability manifest ONLY once every hosted addon's
+ * `initialize()` has returned: `addon-runner.ts` appends to `runnerManifest`
+ * AFTER the await, and `refreshChildCaps('post-init')` runs after the whole
+ * loop. So an `initialize()` that does not return is not a slow feature — it
+ * takes every capability that addon owns OFF the cluster. Callers get
+ * `no provider registered for cap "…"`, and the admin UI renders "provider not
+ * available".
+ *
+ * ## Why a log line and not a bound
+ *
+ * 2026-08-14: `pipeline-analytics` awaited a timelapse back-fill render inside
+ * `initialize()`. The window was 19:00→05:00, the export rendered for over half
+ * an hour, and for that whole time `notification-rules`, `pipeline-analytics`,
+ * `zone-analytics`, `audio-metrics`, `videoclips`, `face-gallery`,
+ * `plate-gallery` and `addon-widgets-source` had ZERO providers cluster-wide.
+ * The runner was healthy and chatty throughout — its 30 s tick kept logging —
+ * which is exactly why nothing looked wrong. Not one line said the manifest had
+ * never been published, and the diagnosis cost hours of log correlation.
+ *
+ * Killing the runner mid-init would be worse than the stall (a half-initialised
+ * addon respawning in a loop), so this does not bound anything. It makes the
+ * stall NAMED, periodic, and attributable to the addon and the exact
+ * capabilities it is holding hostage — which is the one thing that was missing.
+ */
+/** First warning after this long without `initialize()` returning. */
+export declare const INIT_WATCHDOG_FIRST_MS = 60000;
+/** And every this often afterwards, for as long as it stays stuck. */
+export declare const INIT_WATCHDOG_REPEAT_MS = 300000;
+/** The warn sink — narrow on purpose, so this module needs no logger type. */
+export type InitWatchdogWarn = (message: string, meta: Record<string, unknown>) => void;
+export interface InitWatchdogOptions {
+    /** The addon whose `initialize()` is being awaited. */
+    readonly addonId: string;
+    /**
+     * The capability names the addon's manifest declares. They are what the
+     * cluster is missing while the stall lasts, so they belong in the line — a
+     * reader must not have to open the manifest to learn what is offline.
+     */
+    readonly declaredCapabilities: readonly string[];
+    readonly warn: InitWatchdogWarn;
+    readonly now?: () => number;
+    readonly firstMs?: number;
+    readonly repeatMs?: number;
+}
+export interface InitWatchdogHandle {
+    /** Stop warning. Safe to call more than once, and after the last warning. */
+    clear(): void;
+}
+/**
+ * Start warning if `initialize()` has not returned within `firstMs`.
+ *
+ * The caller MUST `clear()` in a `finally`, so a throwing initialize (which the
+ * runner turns into `process.exit(1)`) does not keep the timer alive.
+ */
+export declare function startInitWatchdog(options: InitWatchdogOptions): InitWatchdogHandle;

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@camstack/system",
-  "version": "1.2.87",
+  "version": "1.2.89",
   "description": "Core addon for CamStack — builtins, pipeline, process management, auth, logging, events",
   "keywords": [
     "camstack",