@camstack/system 1.2.69 → 1.2.70

package/dist/kernel/capability-registry.d.ts

@@ -30,6 +30,19 @@ export declare class CapabilityRegistry {
     private _ready;
     /** Boot-time dependency graph: capability → dependsOn names (from CapabilityDeclaration) */
     private readonly capabilityDeps;
+    /**
+     * capability → addon ids whose MANIFEST declares it.
+     *
+     * Populated by {@link declareFromManifest}, which runs at addon-LOAD time —
+     * before a forked addon's runner has spawned, let alone registered anything.
+     * So this map answers a question `providers` cannot: **which addons still owe
+     * this capability a provider**, i.e. is an absence final or merely early.
+     *
+     * It is not a second registry and nothing waits on it: it stores an argument
+     * `declareFromManifest` was already being handed and dropping, and it is read
+     * synchronously at the moment a caller needs the answer ([D3](../../../../docs/decisions/adr-0003.md)).
+     */
+    private readonly manifestDeclarers;
     /** Per-device singleton overrides: deviceId → (capability → addonId) */
     private readonly deviceOverrides;
     /** capName → (nodeId → bare addonId) per-node singleton overrides. */
@@ -147,6 +160,19 @@ export declare class CapabilityRegistry {
      * re-register the same pair must unregister first.
      */
     hasProvider(capabilityName: string, addonId: string): boolean;
+    /**
+     * Addon ids whose manifest declares `capabilityName`, whether or not they
+     * have registered a provider yet.
+     *
+     * Pair it with {@link hasProvider} to separate "this capability's collection
+     * is still filling up" from "this is everything there will ever be" — the
+     * difference between a 503 a client should retry and a 400 it should not.
+     * Every entry is an addon INSTALLED on this node; an addon that is installed
+     * but disabled therefore stays listed, which is the honest answer (the
+     * capability is owed by something that is not going to supply it, and naming
+     * it is the diagnosis).
+     */
+    getManifestDeclarers(capabilityName: string): readonly string[];
     /** Unregister a provider. For singleton: clears active. For collection: removes from list. */
     unregisterProvider(capabilityName: string, addonId: string): void;
     /** Enable a previously disabled collection provider. */

package/dist/kernel/config-schema.d.ts

@@ -5,8 +5,8 @@ export declare const DEFAULT_DATA_PATH = "camstack-data";
  *  All other settings live in SQL (system_settings table). */
 export declare const bootstrapSchema: z.ZodObject<{
     mode: z.ZodDefault<z.ZodEnum<{
-        hub: "hub";
         agent: "agent";
+        hub: "hub";
     }>>;
     server: z.ZodDefault<z.ZodObject<{
         port: z.ZodDefault<z.ZodNumber>;

package/dist/{manifest-python-deps-Dz1ryHIN.mjs → manifest-python-deps-DKrHcUZj.mjs}

@@ -1,16 +1,16 @@
-import { ensureBinary, ensureFfmpeg, ensurePython, installPythonPackages, installPythonRequirements } from "@camstack/types/node";
 import * as crypto$1 from "node:crypto";
 import { randomBytes, randomUUID } from "node:crypto";
-import { createServer } from "node:http";
-import * as fs from "node:fs";
+import { ensureBinary, ensureFfmpeg, ensurePython, installPythonPackages, installPythonRequirements } from "@camstack/types/node";
+import { unlink } from "node:fs/promises";
 import * as path$1 from "node:path";
 import { isAbsolute, join } from "node:path";
-import { promisify } from "node:util";
-import { DATAPLANE_SECRET_HEADER, DeviceType, DisposerChain, EventCategory, ReadinessRegistry, asJsonObject, asString, createDeviceProxy, deviceOpsCapability, emitReadiness, errMsg, expandCapMethods, readNodePin, scopeKey, sleep, withCapInputDefaults } from "@camstack/types/addon";
 import { execFile } from "node:child_process";
+import { promisify } from "node:util";
 import * as os from "node:os";
 import { tmpdir } from "node:os";
-import { unlink } from "node:fs/promises";
+import * as fs from "node:fs";
+import { createServer } from "node:http";
+import { DATAPLANE_SECRET_HEADER, DeviceType, DisposerChain, EventCategory, ReadinessRegistry, asJsonObject, asString, createDeviceProxy, deviceOpsCapability, emitReadiness, errMsg, expandCapMethods, readNodePin, scopeKey, sleep, withCapInputDefaults } from "@camstack/types/addon";
 import { TRPCClientError, createTRPCClient } from "@trpc/client";
 import { connect, createServer as createServer$1 } from "node:net";
 //#region src/kernel/moleculer/addon-data-plane-facility.ts
@@ -129,46 +129,6 @@ function createAddonDataPlaneFacility(args) {
 	};
 }
 //#endregion
-//#region src/kernel/addon-class-resolver.ts
-function isRecord(value) {
-	return typeof value === "object" && value !== null && !Array.isArray(value);
-}
-/**
-* Resolve the addon class from a dynamically imported module.
-*
-* Two compilation patterns to handle:
-*   1. ESM with explicit `export default class …` — `mod.default` is the class.
-*   2. CJS via tsup that emits only named exports (no `module.exports = …`)
-*      — `mod.default` is undefined; we must pick the right named export.
-*
-* The CJS path is the trap: an addon bundle can also re-export device
-* classes (e.g. `ReolinkCamera` extends `BaseDevice`) and helper
-* functions. Picking `Object.keys(mod)[0]` is bundler-order-dependent —
-* the first named export today is `ReolinkCamera`, whose `new` requires
-* a `DeviceContext` and crashes on `new MyClass()`.
-*
-* The contract is: the addon class extends `BaseAddon`, which has an
-* `initialize` method on its prototype. Device classes (`BaseDevice`)
-* do not. We probe for that method to disambiguate.
-*/
-function isAddonConstructor(fn) {
-	if (typeof fn !== "function") return false;
-	const proto = fn.prototype;
-	if (!isRecord(proto)) return false;
-	return typeof proto["initialize"] === "function";
-}
-function resolveAddonClass(mod) {
-	let candidate = mod["default"];
-	if (isRecord(candidate) && "default" in candidate) candidate = candidate["default"];
-	if (isAddonConstructor(candidate)) return candidate;
-	if (isRecord(candidate)) {
-		const fn = Object.values(candidate).find(isAddonConstructor);
-		if (fn) return fn;
-	}
-	const namedAddon = Object.values(mod).find(isAddonConstructor);
-	if (namedAddon) return namedAddon;
-}
-//#endregion
 //#region src/kernel/deps/npm-command.ts
 /**
 * npm invocation resolver — makes "is npm available?" a solved problem for
@@ -298,6 +258,46 @@ async function resolveUncached(options) {
 	}
 }
 //#endregion
+//#region src/kernel/addon-class-resolver.ts
+function isRecord(value) {
+	return typeof value === "object" && value !== null && !Array.isArray(value);
+}
+/**
+* Resolve the addon class from a dynamically imported module.
+*
+* Two compilation patterns to handle:
+*   1. ESM with explicit `export default class …` — `mod.default` is the class.
+*   2. CJS via tsup that emits only named exports (no `module.exports = …`)
+*      — `mod.default` is undefined; we must pick the right named export.
+*
+* The CJS path is the trap: an addon bundle can also re-export device
+* classes (e.g. `ReolinkCamera` extends `BaseDevice`) and helper
+* functions. Picking `Object.keys(mod)[0]` is bundler-order-dependent —
+* the first named export today is `ReolinkCamera`, whose `new` requires
+* a `DeviceContext` and crashes on `new MyClass()`.
+*
+* The contract is: the addon class extends `BaseAddon`, which has an
+* `initialize` method on its prototype. Device classes (`BaseDevice`)
+* do not. We probe for that method to disambiguate.
+*/
+function isAddonConstructor(fn) {
+	if (typeof fn !== "function") return false;
+	const proto = fn.prototype;
+	if (!isRecord(proto)) return false;
+	return typeof proto["initialize"] === "function";
+}
+function resolveAddonClass(mod) {
+	let candidate = mod["default"];
+	if (isRecord(candidate) && "default" in candidate) candidate = candidate["default"];
+	if (isAddonConstructor(candidate)) return candidate;
+	if (isRecord(candidate)) {
+		const fn = Object.values(candidate).find(isAddonConstructor);
+		if (fn) return fn;
+	}
+	const namedAddon = Object.values(mod).find(isAddonConstructor);
+	if (namedAddon) return namedAddon;
+}
+//#endregion
 //#region src/kernel/deps/manifest-native-deps.ts
 var execFileAsync = promisify(execFile);
 /**
@@ -7614,4 +7614,4 @@ async function installManifestPythonDeps(declaration, addonDir, deps, logger) {
 	await deps.installPythonRequirements(reqAbs);
 }
 //#endregion
-export { buildNativeCapProxy as $, createHubCapForwardService as A, AGENT_CAP_FWD_ACTION as B, brokerTransportLink as C, resolveAddonClass as Ct, localProviderLink as D, ipcParentLink as E, createUdsLogger as F, callWithServiceDiscovery as G, CapRouteResolver as H, createUdsLoggerWithControl as I, UdsLocalTransportServer as J, createLocalTransport as K, LocalChildClient as L, createUdsEventBridge as M, createUdsEventBus as N, HUB_CAP_FWD_ACTION as O, udsChildLogToWorkerEntry as P, encodeFrame as Q, LocalChildRegistry as R, brokerCallForCap as S, runNpm as St, ipcChildLink as T, CapRouteError as U, AGENT_CAP_FWD_SERVICE as V, classifyCapRoute as W, localEndpointPath as X, SocketChannel as Y, FrameDecoder as Z, createKernelHwAccel as _, CapabilityHandle as _t, getWorkerDeviceRegistry as a, setWorkerNativeCapsChangeListener as at, __resetCapUsageRegistryForTests as b, installManifestNativeDeps as bt, setHubConnected as c, NATIVE_PROVIDER_SERVICE_INFIX as ct, getBrokerEventBus as d, capBareAction as dt, buildUdsNativeCapProxy as et, getMoleculerEventStats as f, capServiceName as ft, AddonDepsManager as g, DeviceRegistry as gt, subscribePassthrough as h, serializeTypedArrays as ht, createUdsAddonContext as i, mountNativeCapService as it, createParentUnownedCallHandler as j, HUB_CAP_FWD_SERVICE as k, EVENT_TOPIC_PREFIX as l, capActionName as lt, setNodeEventInterest as m, deserializeTypedArrays as mt, adaptBrokerToCluster as n, getWorkerNativeCapProvider as nt, getOrInitReadinessRegistry as o, createAddonService as ot, registerEventBusService as p, parseCapAction as pt, UdsLocalTransportClient as q, createAddonContext as r, getWorkerNativeCapSnapshot as rt, getOrInitReadinessRegistryForClient as s, validateProviderRegistrations as st, installManifestPythonDeps as t, createBrokerDeviceManagerApi as tt, clusterEventTopic as u, capActionSuffix as ut, resolveHwAccel as v, CapabilityUnavailableError as vt, buildLinkChain as w, createAddonDataPlaneFacility as wt, getCapUsageRegistry as x, resolveNpmInvocation as xt, CapUsageRegistry as y, copyBundledNativeModules as yt, UDS_NO_ROUTE_PREFIX as z };
+export { buildNativeCapProxy as $, createHubCapForwardService as A, AGENT_CAP_FWD_ACTION as B, brokerTransportLink as C, runNpm as Ct, localProviderLink as D, ipcParentLink as E, createUdsLogger as F, callWithServiceDiscovery as G, CapRouteResolver as H, createUdsLoggerWithControl as I, UdsLocalTransportServer as J, createLocalTransport as K, LocalChildClient as L, createUdsEventBridge as M, createUdsEventBus as N, HUB_CAP_FWD_ACTION as O, udsChildLogToWorkerEntry as P, encodeFrame as Q, LocalChildRegistry as R, brokerCallForCap as S, resolveNpmInvocation as St, ipcChildLink as T, CapRouteError as U, AGENT_CAP_FWD_SERVICE as V, classifyCapRoute as W, localEndpointPath as X, SocketChannel as Y, FrameDecoder as Z, createKernelHwAccel as _, CapabilityHandle as _t, getWorkerDeviceRegistry as a, setWorkerNativeCapsChangeListener as at, __resetCapUsageRegistryForTests as b, installManifestNativeDeps as bt, setHubConnected as c, NATIVE_PROVIDER_SERVICE_INFIX as ct, getBrokerEventBus as d, capBareAction as dt, buildUdsNativeCapProxy as et, getMoleculerEventStats as f, capServiceName as ft, AddonDepsManager as g, DeviceRegistry as gt, subscribePassthrough as h, serializeTypedArrays as ht, createUdsAddonContext as i, mountNativeCapService as it, createParentUnownedCallHandler as j, HUB_CAP_FWD_SERVICE as k, EVENT_TOPIC_PREFIX as l, capActionName as lt, setNodeEventInterest as m, deserializeTypedArrays as mt, adaptBrokerToCluster as n, getWorkerNativeCapProvider as nt, getOrInitReadinessRegistry as o, createAddonService as ot, registerEventBusService as p, parseCapAction as pt, UdsLocalTransportClient as q, createAddonContext as r, getWorkerNativeCapSnapshot as rt, getOrInitReadinessRegistryForClient as s, validateProviderRegistrations as st, installManifestPythonDeps as t, createBrokerDeviceManagerApi as tt, clusterEventTopic as u, capActionSuffix as ut, resolveHwAccel as v, CapabilityUnavailableError as vt, buildLinkChain as w, createAddonDataPlaneFacility as wt, getCapUsageRegistry as x, resolveAddonClass as xt, CapUsageRegistry as y, copyBundledNativeModules as yt, UDS_NO_ROUTE_PREFIX as z };

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@camstack/system",
-  "version": "1.2.69",
+  "version": "1.2.70",
   "description": "Core addon for CamStack — builtins, pipeline, process management, auth, logging, events",
   "keywords": [
     "camstack",
@@ -267,9 +267,6 @@
           },
           {
             "name": "user-management"
-          },
-          {
-            "name": "oauth-integration"
           }
         ]
       },

package/dist/builtins/local-auth/homeassistant-integration.d.ts

@@ -1,7 +0,0 @@
-import { OauthIntegrationDescriptor } from '@camstack/types';
-/**
- * Scopes granted to a linked Home Assistant, derived from the tRPC paths the
- * component actually calls. `category:system [create]` was rejected: it would
- * hand `addons.installPackage` to a home-automation bridge.
- */
-export declare const HOME_ASSISTANT_OAUTH_INTEGRATION: OauthIntegrationDescriptor;