@camstack/addon-post-analysis 1.2.280 → 1.2.281

package/dist/{dist-VeiAavYR.js → dist-BtqlSCQT.js}

@@ -29,6 +29,7 @@ var __toESM = (mod, isNodeMode, target) => (target = mod != null ? __create(__ge
 	enumerable: true
 }) : target, mod));
 //#endregion
+let node_crypto = require("node:crypto");
 //#region ../types/dist/event-category-BVDXG4tB.mjs
 var EventCategory = /* @__PURE__ */ function(EventCategory) {
 	EventCategory["SystemBoot"] = "system.boot";
@@ -7598,6 +7599,39 @@ function sleep(ms) {
 	return new Promise((resolve) => setTimeout(resolve, Math.max(0, ms)));
 }
 //#endregion
+//#region ../types/dist/canonical-hash-CPK2Dy60.mjs
+/**
+* Deterministic SHA-256 hash of an arbitrary serialisable value. The
+* canonical form sorts object keys alphabetically at every depth so two
+* structurally-equal inputs with different key insertion orders produce
+* the same hash. Returns a 64-char lowercase hex digest.
+*
+* Used by export adapters (Alexa, HAP) to short-circuit re-discovery /
+* accessory-rebuild work when the upstream shape is byte-identical to
+* the last applied state — preventing user-visible "re-discovery"
+* notifications on every addon-runner respawn. Each respawn re-fires
+* `DeviceBindingsChanged` for every cap registration, which without
+* this guard would propagate redundant pushes.
+*
+* Note: this is a SYMPTOMATIC fix layered on top of the binding-change
+* subscription. The proper fix is a single "device ready" lifecycle
+* barrier so exports react only when the full cap set has landed —
+* tracked separately for post-HA-integration work.
+*/
+function canonicalHash(value) {
+	const canonical = JSON.stringify(value, replaceWithSortedKeys);
+	return (0, node_crypto.createHash)("sha256").update(canonical ?? "").digest("hex");
+}
+function replaceWithSortedKeys(_key, value) {
+	if (value && typeof value === "object" && !Array.isArray(value)) {
+		const obj = value;
+		const out = {};
+		for (const k of Object.keys(obj).toSorted()) out[k] = obj[k];
+		return out;
+	}
+	return value;
+}
+//#endregion
 //#region ../types/dist/err-msg-IQTHeDzc.mjs
 /**
 import { errMsg } from '@camstack/types'
@@ -18996,9 +19030,29 @@ var NcTestResultSchema = object({
 	className: string().optional(),
 	label: string().optional()
 });
-/** The five rule kinds, as data. `NcRuleKind` in `notification/rule-kinds.ts`
-*  is the same union; the template-vars spec pins the two together. */
+/** The rule kinds, as data. `NcRuleKind` in `notification/rule-kinds.ts` is the
+*  same union; the template-vars spec pins the two together. `mixed` is DERIVED
+*  (a stored system rule whose kinds span families, D637) and never authored. */
 var NcRuleKindSchema = _enum([
+	"detection",
+	"sensor",
+	"occupancy",
+	"sound",
+	"device-events",
+	"system",
+	"alarm",
+	"mixed"
+]);
+/**
+* The kinds a SERVED template-variable descriptor may name: the five that
+* existed before D637, frozen. `getTemplateCatalog` ships `kinds` to every
+* installed viewer, and a viewer at `@camstack/types` 1.2.25x parses them with a
+* strict five-member enum — one `device-events` in one descriptor fails the
+* whole catalog parse. So the WIRE says `system`, and the MATCH widens it:
+* `templateVarKindApplies` reads a `system` descriptor as applying to every
+* system rule kind (`device-events`, `system`, `alarm`, `mixed`).
+*/
+var NcTemplateVarKindSchema = _enum([
 	"detection",
 	"sensor",
 	"occupancy",
@@ -19036,7 +19090,7 @@ var NcTemplateVarGroupSchema = _enum([
 *
 * `families` / `fields` / `kinds` / `deliveries` / `systemEventKinds` say WHERE
 * it has a value; absent = no restriction on that axis. `systemEventKinds` is
-* read only for a `system` rule. `dynamic` declares a FAMILY of names
+* read only for a system-event rule (any family, or `mixed`). `dynamic` declares a FAMILY of names
 * (`count_<class>`): the descriptor's `name` is the example member.
 */
 var NcTemplateVarDescriptorSchema = object({
@@ -19047,7 +19101,7 @@ var NcTemplateVarDescriptorSchema = object({
 	group: NcTemplateVarGroupSchema,
 	families: array(NcTemplateFamilySchema).min(1),
 	fields: array(NcTemplateFieldSchema).optional(),
-	kinds: array(NcRuleKindSchema).optional(),
+	kinds: array(NcTemplateVarKindSchema).optional(),
 	deliveries: array(NcDeliverySchema).optional(),
 	systemEventKinds: array(NcSystemEventKindSchema).optional(),
 	dynamic: object({
@@ -33200,7 +33254,30 @@ var RenameNodeResultSchema = object({
 	nodeId: string(),
 	name: string()
 });
-method(_void(), array(TopologyNodeSchema).readonly(), { auth: "admin" }), method(NodeAddonInputSchema, SuccessSchema, {
+/**
+* The cheap node list. A consumer's rule for a STORED node id (a rule's
+* `nodeIds`) that is missing from `nodes`, whatever `complete` says: render it
+* as a removable chip labelled unknown, never drop it (D49). Even a complete
+* list omits a node that joined and left between two history captures, so a
+* missing id means "not known to the hub", never "removed". Only the operator
+* removes it.
+*
+* `complete` changes only the WORDING: `false` = no history read has ever
+* answered, so the list may be missing offline nodes the hub does know (D315).
+*
+* `name` is the history row's name (≤ 30 s behind a rename), or the id when
+* the history has none.
+*/
+var NodeDirectorySchema = object({
+	nodes: array(object({
+		id: string(),
+		name: string(),
+		isHub: boolean(),
+		isOnline: boolean()
+	})).readonly(),
+	complete: boolean()
+});
+method(_void(), array(TopologyNodeSchema).readonly(), { auth: "admin" }), method(_void(), NodeDirectorySchema, { auth: "admin" }), method(NodeAddonInputSchema, SuccessSchema, {
 	kind: "mutation",
 	auth: "admin"
 }), method(NodeAddonInputSchema, SuccessSchema, {
@@ -44726,6 +44803,12 @@ Object.freeze({
 		addonId: null,
 		access: "create"
 	},
+	"nodes.directory": {
+		capName: "nodes",
+		capScope: "system",
+		addonId: null,
+		access: "view"
+	},
 	"nodes.executeQuery": {
 		capName: "nodes",
 		capScope: "system",
@@ -50510,6 +50593,253 @@ function audioModeOf(value) {
 	return null;
 }
 new Set(["devices", "classes"]);
+/** Every filter, for the callers that must cover all four (guards, tests). */
+var NC_SYSTEM_EVENT_FILTER_KEYS = [
+	"deviceIds",
+	"deviceTypes",
+	"nodeIds",
+	"packageNames"
+];
+/**
+* Does `filter` say anything about `kind`?
+*
+* `false` means the filter is not part of this kind's vocabulary: the engine
+* ignores it and an editor hides its input. It never means "excluded".
+*/
+function systemEventFilterApplies(kind, filter) {
+	switch (filter) {
+		case "deviceIds": return kind.startsWith("device-") || kind.startsWith("stream-") || kind === "detection-blind" || kind === "alarm-triggered";
+		case "deviceTypes": return kind.startsWith("device-") || kind === "detection-blind";
+		case "nodeIds": return kind.startsWith("node-") || kind === "addon-crash-loop" || kind === "addon-update-available" || kind === "addon-updated" || kind === "server-update-available" || kind === "wrapper-update-available" || kind === "server-updated";
+		case "packageNames": return kind.endsWith("update-available") || kind === "addon-updated" || kind === "server-updated";
+	}
+}
+/**
+* WHICH FAMILY every system-event kind belongs to, and which narrowing filters
+* each family may carry: one table, read by the hub validator, by `ruleKindOf`
+* and by both rule editors (D637).
+*
+* A system rule used to be one editor for thirty-one kinds and five filters.
+* "Eventi di sistema" carried battery kinds under a liveness `deviceTypes` filter
+* and went silent for two weeks (D636). The three families are three questions:
+* about devices, about the installation, and about the alarm panel. A rule
+* answers one of them. The engine never needed to know, and it still does not:
+* a mixed stored rule keeps firing. Only AUTHORING is strict.
+*
+* The legacy `camera-*` tail has no family (`null`). It is parsed, never produced,
+* never offered.
+*/
+var NC_SYSTEM_EVENT_FAMILIES = [
+	"device-events",
+	"system",
+	"alarm"
+];
+function isSystemEventFamily(value) {
+	return NC_SYSTEM_EVENT_FAMILIES.some((family) => family === value);
+}
+/** Total over the enum: a kind added to the cap without a family fails tsc here. */
+var NC_SYSTEM_EVENT_FAMILY = {
+	"device-online": "device-events",
+	"device-offline": "device-events",
+	"device-disabled": "device-events",
+	"device-enabled": "device-events",
+	"device-battery-low": "device-events",
+	"device-battery-normal": "device-events",
+	"device-consumable-low": "device-events",
+	"device-consumable-normal": "device-events",
+	"stream-online": "device-events",
+	"stream-offline": "device-events",
+	"detection-blind": "device-events",
+	"node-online": "system",
+	"node-offline": "system",
+	"node-inference-unavailable": "system",
+	"addon-crash-loop": "system",
+	"addon-update-available": "system",
+	"addon-updated": "system",
+	"server-update-available": "system",
+	"server-updated": "system",
+	"wrapper-update-available": "system",
+	"backup-completed": "system",
+	"export-completed": "system",
+	"alarm-triggered": "alarm",
+	"alarm-armed": "alarm",
+	"alarm-disarmed": "alarm",
+	"alarm-arming": "alarm",
+	"alarm-arm-refused": "alarm",
+	"alarm-pending": "alarm",
+	"alarm-rearmed": "alarm",
+	"alarm-sensor-bypass": "alarm",
+	"alarm-check-failed": "alarm",
+	"camera-online": null,
+	"camera-offline": null,
+	"camera-disabled": null,
+	"camera-enabled": null
+};
+new Map(Object.entries(NC_SYSTEM_EVENT_FAMILY));
+var NC_SYSTEM_EVENT_CONDITION_FILTER_KEYS = [...NC_SYSTEM_EVENT_FILTER_KEYS, "excludeDeviceIds"];
+/**
+* The filters a family may carry. The four base filters are the union of
+* `systemEventFilterApplies` over the family's kinds (the spec pins that
+* equality). `excludeDeviceIds` is a device-events filter only: an alarm is
+* narrowed to the camera that triggered it and excludes nothing.
+*/
+var NC_SYSTEM_EVENT_FAMILY_FILTERS = {
+	"device-events": [
+		"deviceIds",
+		"excludeDeviceIds",
+		"deviceTypes"
+	],
+	system: ["nodeIds", "packageNames"],
+	alarm: ["deviceIds"]
+};
+var NC_SYSTEM_EVENT_KIND_GROUP_SPECS = [
+	{
+		id: "device-state",
+		family: "device-events",
+		label: "Device state",
+		kinds: [
+			"device-offline",
+			"device-online",
+			"device-disabled",
+			"device-enabled"
+		]
+	},
+	{
+		id: "streams",
+		family: "device-events",
+		label: "Streams",
+		kinds: ["stream-offline", "stream-online"]
+	},
+	{
+		id: "battery",
+		family: "device-events",
+		label: "Battery",
+		kinds: ["device-battery-low", "device-battery-normal"]
+	},
+	{
+		id: "consumables",
+		family: "device-events",
+		label: "Consumables",
+		kinds: ["device-consumable-low", "device-consumable-normal"]
+	},
+	{
+		id: "detection-blind",
+		family: "device-events",
+		label: "Detecting nothing",
+		kinds: ["detection-blind"]
+	},
+	{
+		id: "nodes",
+		family: "system",
+		label: "Nodes",
+		kinds: [
+			"node-offline",
+			"node-online",
+			"node-inference-unavailable"
+		]
+	},
+	{
+		id: "addons",
+		family: "system",
+		label: "Addons",
+		kinds: [
+			"addon-crash-loop",
+			"addon-update-available",
+			"addon-updated"
+		]
+	},
+	{
+		id: "updates",
+		family: "system",
+		label: "Server & container updates",
+		kinds: [
+			"server-update-available",
+			"server-updated",
+			"wrapper-update-available"
+		]
+	},
+	{
+		id: "backups-exports",
+		family: "system",
+		label: "Backups & exports",
+		kinds: ["backup-completed", "export-completed"]
+	},
+	{
+		id: "alarm",
+		family: "alarm",
+		label: "Alarm",
+		kinds: NC_ALARM_SYSTEM_EVENT_KINDS
+	}
+];
+function systemEventKindsOfFamily(family) {
+	return NC_SYSTEM_EVENT_KIND_GROUP_SPECS.filter((g) => g.family === family).flatMap((g) => g.kinds);
+}
+/**
+* Why the hub refuses this condition on a new or updated rule. Empty = accepted.
+* Families are reported in `NC_SYSTEM_EVENT_FAMILIES` order, and filters in
+* `NC_SYSTEM_EVENT_CONDITION_FILTER_KEYS` order, so a refusal reads the same
+* every time.
+*/
+function systemEventFamilyProblems(condition) {
+	if (condition === void 0 || condition.kinds.length === 0) return [{ code: "no-kinds" }];
+	const problems = [];
+	const present = /* @__PURE__ */ new Set();
+	for (const kind of condition.kinds) {
+		const family = NC_SYSTEM_EVENT_FAMILY[kind];
+		if (family === null) problems.push({
+			code: "legacy-kind",
+			kind
+		});
+		else present.add(family);
+	}
+	const families = NC_SYSTEM_EVENT_FAMILIES.filter((f) => present.has(f));
+	if (families.length > 1) problems.push({
+		code: "mixed-families",
+		families
+	});
+	const [family] = families;
+	if (families.length !== 1 || family === void 0) return problems;
+	const allowed = NC_SYSTEM_EVENT_FAMILY_FILTERS[family];
+	for (const filter of NC_SYSTEM_EVENT_CONDITION_FILTER_KEYS) if (condition[filter] !== void 0 && !allowed.includes(filter)) problems.push({
+		code: "filter-outside-family",
+		filter,
+		family
+	});
+	return problems;
+}
+function describeSystemEventFamilyProblem(problem) {
+	switch (problem.code) {
+		case "no-kinds": return "a system-event rule needs at least one event kind";
+		case "legacy-kind": return `'${problem.kind}' is a legacy kind and cannot be authored`;
+		case "mixed-families": return `event kinds span ${problem.families.join(" + ")} — one rule per family`;
+		case "filter-outside-family": return `filter '${problem.filter}' is not allowed on a ${problem.family} rule`;
+	}
+}
+/** Every kind a `system-event` rule can derive — the three families and `mixed`. */
+var NC_SYSTEM_RULE_KINDS = [
+	"device-events",
+	"system",
+	"alarm",
+	"mixed"
+];
+/** Is this a kind a `system-event` rule derives (any family, or `mixed`)? */
+function isSystemRuleKind(kind) {
+	return NC_SYSTEM_RULE_KINDS.some((k) => k === kind);
+}
+/** The family a kind authors, or undefined (a camera kind, or `mixed`). */
+function systemFamilyOfKind(kind) {
+	return isSystemEventFamily(kind) ? kind : void 0;
+}
+/** The delivery a system rule rides — named once, compared everywhere. */
+var NC_SYSTEM_DELIVERY = "system-event";
+/**
+* Is this a SYSTEM rule — one about the installation rather than about anything
+* a camera saw? Takes a plain `string` so a rule carrying a delivery this build
+* has never heard of still gets an answer instead of a type error.
+*/
+function isSystemDelivery(delivery) {
+	return delivery === NC_SYSTEM_DELIVERY;
+}
 NC_AUDIO_DEFAULTS.hitPercent, NC_AUDIO_DEFAULTS.samplingSeconds;
 var WEEKDAY_TO_DAY = {
 	Sun: 0,
@@ -51308,10 +51638,38 @@ var CAPTION_VARS = {
 function onAxis(declared, asked) {
 	return declared === void 0 || asked === void 0 || declared.includes(asked);
 }
-function onSystemAxis(d, ctx) {
-	if (ctx.kind !== "system" || d.systemEventKinds === void 0) return true;
+/**
+* Does a descriptor declared for `declared` kinds have a value for a rule of
+* `kind`?
+*
+* `system` on the WIRE stands for every system rule kind (D637): the served
+* catalog keeps the five pre-D637 tokens so installed viewers still parse it
+* (`NcTemplateVarKindSchema`), and the family split lives here, in the match.
+* Exported so the admin's local interpreter of the served catalog asks the
+* same question instead of restating it.
+*/
+function templateVarKindApplies(declared, kind) {
+	if (declared === void 0 || kind === void 0) return true;
+	if (declared.some((k) => k === kind)) return true;
+	return isSystemRuleKind(kind) && declared.includes("system");
+}
+/**
+* Is a descriptor that names `systemEventKinds` on the event-kind axis of a
+* system rule? Read only for a system rule kind; any other kind ignores it.
+*
+* Event kinds chosen: the descriptor must speak about one of them. None chosen
+* yet: a FAMILY kind watches its own family's event kinds (a device-events rule
+* is never offered the alarm's `{{mode}}`), and `mixed` watches all of them.
+*/
+function templateVarSystemEventApplies(d, ctx) {
+	if (!isSystemRuleKind(ctx.kind) || d.systemEventKinds === void 0) return true;
+	const declared = d.systemEventKinds;
 	const asked = ctx.systemEventKinds ?? [];
-	return asked.length === 0 || asked.some((k) => d.systemEventKinds?.includes(k) === true);
+	if (asked.length > 0) return asked.some((k) => declared.includes(k));
+	const family = ctx.kind === void 0 ? void 0 : systemFamilyOfKind(ctx.kind);
+	if (family === void 0) return true;
+	const own = systemEventKindsOfFamily(family);
+	return declared.some((k) => own.includes(k));
 }
 /**
 * The variables that have a value in `ctx`, in catalog order. Pure.
@@ -51325,27 +51683,13 @@ function templateVarsFor(ctx) {
 		const allowed = CAPTION_VARS[ctx.field];
 		return NC_TEMPLATE_VARS.filter((d) => d.families.includes(ctx.family) && allowed.includes(d.name) && d.dynamic === void 0);
 	}
-	return NC_TEMPLATE_VARS.filter((d) => d.families.includes(ctx.family) && onAxis(d.fields, ctx.field) && onAxis(d.kinds, ctx.kind) && onAxis(d.deliveries, ctx.delivery) && onSystemAxis(d, ctx));
+	return NC_TEMPLATE_VARS.filter((d) => d.families.includes(ctx.family) && onAxis(d.fields, ctx.field) && templateVarKindApplies(d.kinds, ctx.kind) && onAxis(d.deliveries, ctx.delivery) && templateVarSystemEventApplies(d, ctx));
 }
 /** True when `name` is supplied in `ctx`, dynamic families (`count_<class>`) included. */
 function isKnownTemplateVar(name, ctx) {
 	return templateVarsFor(ctx).some((d) => d.dynamic !== void 0 ? name.startsWith(d.dynamic.prefix) && name.length > d.dynamic.prefix.length : d.name === name);
 }
 /**
-* Does `filter` say anything about `kind`?
-*
-* `false` means the filter is not part of this kind's vocabulary: the engine
-* ignores it and an editor hides its input. It never means "excluded".
-*/
-function systemEventFilterApplies(kind, filter) {
-	switch (filter) {
-		case "deviceIds": return kind.startsWith("device-") || kind.startsWith("stream-") || kind === "detection-blind" || kind === "alarm-triggered" || kind === "export-completed";
-		case "deviceTypes": return kind.startsWith("device-") || kind === "detection-blind";
-		case "nodeIds": return kind.startsWith("node-") || kind === "addon-crash-loop" || kind === "addon-update-available" || kind === "addon-updated" || kind === "server-update-available" || kind === "wrapper-update-available" || kind === "server-updated";
-		case "packageNames": return kind.endsWith("update-available") || kind === "addon-updated" || kind === "server-updated";
-	}
-}
-/**
 * TimelapseRule — the STANDALONE scheduled timelapse producer's rule model.
 *
 * Spec: `docs/superpowers/specs/2026-07-24-nc-occupancy-timelapse-design.md`
@@ -52583,6 +52927,12 @@ Object.defineProperty(exports, "NcConditionDescriptorSchema", {
 		return NcConditionDescriptorSchema;
 	}
 });
+Object.defineProperty(exports, "NcConditionsSchema", {
+	enumerable: true,
+	get: function() {
+		return NcConditionsSchema;
+	}
+});
 Object.defineProperty(exports, "NcRuleInputSchema", {
 	enumerable: true,
 	get: function() {
@@ -52823,6 +53173,12 @@ Object.defineProperty(exports, "buildEventKindDescriptor", {
 		return buildEventKindDescriptor;
 	}
 });
+Object.defineProperty(exports, "canonicalHash", {
+	enumerable: true,
+	get: function() {
+		return canonicalHash;
+	}
+});
 Object.defineProperty(exports, "cosineSimilarity", {
 	enumerable: true,
 	get: function() {
@@ -52853,6 +53209,12 @@ Object.defineProperty(exports, "deriveRecordingMode", {
 		return deriveRecordingMode;
 	}
 });
+Object.defineProperty(exports, "describeSystemEventFamilyProblem", {
+	enumerable: true,
+	get: function() {
+		return describeSystemEventFamilyProblem;
+	}
+});
 Object.defineProperty(exports, "discriminatedUnion", {
 	enumerable: true,
 	get: function() {
@@ -52955,6 +53317,12 @@ Object.defineProperty(exports, "isSourceCap", {
 		return isSourceCap;
 	}
 });
+Object.defineProperty(exports, "isSystemDelivery", {
+	enumerable: true,
+	get: function() {
+		return isSystemDelivery;
+	}
+});
 Object.defineProperty(exports, "kebabToCamel", {
 	enumerable: true,
 	get: function() {
@@ -53093,6 +53461,12 @@ Object.defineProperty(exports, "subKindsOf", {
 		return subKindsOf;
 	}
 });
+Object.defineProperty(exports, "systemEventFamilyProblems", {
+	enumerable: true,
+	get: function() {
+		return systemEventFamilyProblems;
+	}
+});
 Object.defineProperty(exports, "systemEventFilterApplies", {
 	enumerable: true,
 	get: function() {