@camstack/types 1.2.256 → 1.2.257

package/dist/index.js

@@ -17196,6 +17196,9 @@ var NcSystemEventKindSchema = zod.z.enum([
 	"device-battery-normal",
 	"device-consumable-low",
 	"device-consumable-normal",
+	"device-tank-low",
+	"device-tank-full",
+	"device-tank-normal",
 	"stream-online",
 	"stream-offline",
 	"node-online",
@@ -17276,6 +17279,31 @@ var NC_BATTERY_CONSUMABLE_SYSTEM_EVENT_KINDS = [
 	"device-consumable-normal"
 ];
 /**
+* The two kinds a RULE's consumable threshold speaks about (D642). Named once:
+* the filter scoping (`systemEventFilterApplies`), the hub's threshold census
+* and both editors read it.
+*/
+var NC_CONSUMABLE_SYSTEM_EVENT_KINDS = ["device-consumable-low", "device-consumable-normal"];
+/** A vacuum's tank alerts (D642) — raised on the provider's own verdict. */
+var NC_TANK_SYSTEM_EVENT_KINDS = [
+	"device-tank-low",
+	"device-tank-full",
+	"device-tank-normal"
+];
+/**
+* The consumable threshold a rule that does not state one judges at (D642).
+* The operator's number ("default 15 %, configurable on the rule"), and the
+* value the cluster-wide setting it replaces shipped with.
+*/
+var NC_CONSUMABLE_LOW_PERCENT_DEFAULT = 15;
+/**
+* The highest consumable threshold a rule may state (D642 review M1): 100 minus
+* the band's 5-point recovery hysteresis (`consumable-band.ts`). Above it the
+* recovery point passes 100 % and an episode could never clear, even for a
+* part just replaced. A spec in the notification centre pins the sum.
+*/
+var NC_CONSUMABLE_LOW_PERCENT_MAX = 95;
+/**
 * One coherent system-event condition. `kinds` is the required opt-in safety
 * gate; the remaining lists are optional narrowing filters relevant to the
 * selected kinds.
@@ -17309,8 +17337,27 @@ var NcSystemEventConditionSchema = zod.z.object({
 	*/
 	excludeDeviceIds: zod.z.array(zod.z.number().int()).min(1).optional(),
 	nodeIds: zod.z.array(zod.z.string().min(1)).min(1).optional(),
-	packageNames: zod.z.array(zod.z.string().min(1)).min(1).optional()
-});
+	packageNames: zod.z.array(zod.z.string().min(1)).min(1).optional(),
+	/**
+	* At or below this remaining-life %, a consumable is LOW for THIS rule
+	* (D642). Absent = {@link NC_CONSUMABLE_LOW_PERCENT_DEFAULT}; at most
+	* {@link NC_CONSUMABLE_LOW_PERCENT_MAX}, so every episode can recover. Scoped to the
+	* consumable kinds (`systemEventFilterApplies`) and to the device-events
+	* family; ignored on every other kind.
+	*
+	* It is a property of the RULE because the operator decided so: a rule at
+	* 25 must be told about a filter at 20 %, a rule at 10 must not. The hub
+	* keeps one episode per (threshold, device, item) — its own hysteresis, its
+	* own reminder — and a rule hears only the episode judged at ITS threshold,
+	* exactly as an occupancy rule hears only the edge of its own count. A
+	* provider's own `replace` verdict is low at every threshold.
+	*/
+	consumableLowPercent: zod.z.number().int().min(1).max(95).optional()
+});
+/** The consumable threshold a system-event condition judges at (D642). */
+function consumableLowPercentOf(condition) {
+	return condition.consumableLowPercent ?? 15;
+}
 /**
 * `maxPerTrack` for `immediate` rules is FIXED at 1 (D-3): a single track
 * fires an immediate rule at most once, enforced durably by the outbox
@@ -18628,6 +18675,18 @@ var NC_CONDITION_CATALOG = [
 				value: "device-consumable-normal",
 				label: "Consumable replaced"
 			},
+			{
+				value: "device-tank-low",
+				label: "Tank low (water, detergent)"
+			},
+			{
+				value: "device-tank-full",
+				label: "Tank full (dirty water, dust)"
+			},
+			{
+				value: "device-tank-normal",
+				label: "Tank back to normal"
+			},
 			{
 				value: "export-completed",
 				label: "Export completed"
@@ -31774,12 +31833,20 @@ reset: require_sleep.method(zod.z.object({
 	},
 	runtimeState: ConsumablesStatusSchema.extend({ lastFetchedAt: zod.z.number() }),
 	/**
-	* Runtime-state durability: **session** — the authority is the appliance; the provider re-reads the whole item array on connect.
+	* Runtime-state durability: **restored** — nothing else holds the value
+	* (D642). A consumable can often be read only in a device's wake window (the
+	* Dreame mower's CMS counters answer only while it charges), so a restart
+	* that wiped the slice left the panel empty and the alerts blind until the
+	* next wake — 2026-09-26, mower 503 idle with `items: []`. A restored item is
+	* the previous observation, not a claim about now; the provider overwrites it
+	* the moment it reads the device again.
 	*
 	* See `RuntimeStateDurability`. Enforced by
 	* `scripts/check-runtime-state-durability.ts`.
 	*/
-	durability: "session"
+	durability: "restored",
+	/** Clocks, not content: a re-read that changed no item costs no commit. */
+	volatileStateFields: ["lastChangedAt", "lastFetchedAt"]
 };
 //#endregion
 //#region src/capabilities/contact.cap.ts
@@ -59039,7 +59106,7 @@ function getCapsByProviderKind(kind) {
 //#region src/generated/runtime-state-durability.ts
 /**
 * Per-cap runtime-state policy, projected from every `*.cap.ts` that declares
-* `runtimeState`. 69 caps: 36 `restored`, 33 `session`.
+* `runtimeState`. 69 caps: 37 `restored`, 32 `session`.
 *
 * A cap absent from this map has no runtime-state slice at all. A cap PRESENT
 * with `durability: 'session'` has one and has decided not to keep it.
@@ -59098,8 +59165,8 @@ var RUNTIME_STATE_POLICY = {
 		volatileFields: ["lastChangedAt"]
 	},
 	"consumables": {
-		durability: "session",
-		volatileFields: []
+		durability: "restored",
+		volatileFields: ["lastChangedAt", "lastFetchedAt"]
 	},
 	"contact": {
 		durability: "restored",
@@ -59350,6 +59417,7 @@ var RESTORED_CAP_NAMES = [
 	"binary",
 	"carbon-monoxide",
 	"connectivity",
+	"consumables",
 	"contact",
 	"cover",
 	"day-night",
@@ -60865,12 +60933,55 @@ function prepareNotification(caps, n) {
 }
 //#endregion
 //#region src/notification/system-event-filters.ts
-/** Every filter, for the callers that must cover all four (guards, tests). */
+/**
+* WHICH narrowing filter speaks about WHICH system-event kind — one predicate,
+* consumed by the rule ENGINE and by every rule EDITOR.
+*
+* ── The failure this file exists for ───────────────────────────────────────
+* `NcSystemEventConditionSchema` carries four optional narrowing lists
+* (`deviceIds`, `deviceTypes`, `nodeIds`, `packageNames`) beside a required
+* `kinds` gate. They are not four filters over one vocabulary: each belongs to
+* a FAMILY of kinds and is meaningless outside it. A node going away has no
+* device type; a completed export has no package; `stream-offline` deliberately
+* carries no device type at all (a stream belongs to a camera by construction).
+*
+* The engine applied all four to every kind, so a filter from one family failed
+* a kind from another family CLOSED. The operator's live rule "Eventi di
+* sistema" selected eleven kinds and set `deviceTypes: ['camera']` — the only
+* way to say "only my cameras" about the two liveness kinds — and NINE of the
+* eleven silently stopped being deliverable. Four days of history contained
+* `device-online` and `device-offline` and nothing else, across a window in
+* which agents were restarted and addons were updated.
+*
+* Both editors already computed this scoping, to decide which filter boxes to
+* render; the cap's own docblock already promised it ("Narrow a `device-*` kind
+* to these device TYPES"). Only the engine disagreed, and it disagreed in the
+* destructive direction. So the rule is stated ONCE, here, and the engine and
+* the editors are readers of it rather than three independent authors.
+*
+* ── The direction ─────────────────────────────────────────────────────────
+* Out of family ⇒ the filter is IGNORED, never fail-closed. An editor that
+* hides a box has already told the operator this filter does not speak about
+* these kinds, so honouring it as an exclusion contradicts the only
+* explanation the operator was ever given. Inside its family the filter still
+* narrows, and still fails CLOSED on a subject that cannot produce the identity
+* it tests (a device the mirror cannot name is not evidence of a camera).
+*/
+/**
+* Every filter, for the callers that must cover all of them (guards, tests).
+*
+* `consumableLowPercent` (D642) is not a list but it is a filter in exactly
+* this sense: it belongs to a family of kinds (the consumable pair) and the
+* engine consults it only there. It differs in one way the readers must know —
+* its ABSENCE is not "no narrowing" but the default threshold, because a
+* consumable episode is always judged at SOME threshold.
+*/
 var NC_SYSTEM_EVENT_FILTER_KEYS = [
 	"deviceIds",
 	"deviceTypes",
 	"nodeIds",
-	"packageNames"
+	"packageNames",
+	"consumableLowPercent"
 ];
 /**
 * Does `filter` say anything about `kind`?
@@ -60884,6 +60995,7 @@ function systemEventFilterApplies(kind, filter) {
 		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";
+		case "consumableLowPercent": return NC_CONSUMABLE_SYSTEM_EVENT_KINDS.includes(kind);
 	}
 }
 /**
@@ -60932,6 +61044,9 @@ var NC_SYSTEM_EVENT_FAMILY = {
 	"device-battery-normal": "device-events",
 	"device-consumable-low": "device-events",
 	"device-consumable-normal": "device-events",
+	"device-tank-low": "device-events",
+	"device-tank-full": "device-events",
+	"device-tank-normal": "device-events",
 	"stream-online": "device-events",
 	"stream-offline": "device-events",
 	"detection-blind": "device-events",
@@ -60964,7 +61079,7 @@ var NC_SYSTEM_EVENT_FAMILY = {
 var FAMILY_BY_NAME = 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
+* The filters a family may carry. The 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.
@@ -60973,7 +61088,8 @@ var NC_SYSTEM_EVENT_FAMILY_FILTERS = {
 	"device-events": [
 		"deviceIds",
 		"excludeDeviceIds",
-		"deviceTypes"
+		"deviceTypes",
+		"consumableLowPercent"
 	],
 	system: ["nodeIds", "packageNames"],
 	alarm: ["deviceIds"]
@@ -61008,6 +61124,16 @@ var NC_SYSTEM_EVENT_KIND_GROUP_SPECS = [
 		label: "Consumables",
 		kinds: ["device-consumable-low", "device-consumable-normal"]
 	},
+	{
+		id: "tanks",
+		family: "device-events",
+		label: "Tanks",
+		kinds: [
+			"device-tank-low",
+			"device-tank-full",
+			"device-tank-normal"
+		]
+	},
 	{
 		id: "detection-blind",
 		family: "device-events",
@@ -61746,6 +61872,11 @@ var RULE_BODY_ONLY = ["body"];
 var RULE_TEXT = ["title", "body"];
 var BATTERY = ["device-battery-low", "device-battery-normal"];
 var CONSUMABLE = ["device-consumable-low", "device-consumable-normal"];
+var TANK = [
+	"device-tank-low",
+	"device-tank-full",
+	"device-tank-normal"
+];
 var UPDATES = [
 	"addon-update-available",
 	"server-update-available",
@@ -61771,6 +61902,7 @@ var DEVICE_EVENTS = [
 	"device-enabled",
 	...BATTERY,
 	...CONSUMABLE,
+	...TANK,
 	"stream-online",
 	"stream-offline",
 	"detection-blind",
@@ -62068,6 +62200,17 @@ var NC_TEMPLATE_VARS = [
 		kinds: ["system"],
 		systemEventKinds: [...CONSUMABLE]
 	},
+	{
+		name: "tank",
+		label: "Tank",
+		description: "Which tank: clean water, dirty water, detergent or dust bin.",
+		example: "clean water",
+		group: "system",
+		families: ["rule"],
+		fields: [...RULE_TEXT],
+		kinds: ["system"],
+		systemEventKinds: [...TANK]
+	},
 	{
 		name: "profile",
 		label: "Stream profile",
@@ -62460,6 +62603,38 @@ var NC_TEMPLATE_VARS = [
 		fields: [...RULE_TEXT]
 	}
 ];
+/**
+* System-event kinds the SERVED catalog holds back (D642): the kinds the hub
+* produces before the installed viewers can parse them.
+*
+* The viewer parses `getTemplateCatalog` WHOLE, with its own strict
+* `NcSystemEventKindSchema` on every descriptor's `systemEventKinds`, so one
+* kind it does not know — in `{{deviceName}}`, which every device event names —
+* empties every {{var}} picker on every phone (the same trap
+* `NcTemplateVarKindSchema` froze the rule kinds for). The in-process catalog
+* keeps them: the producer parity and the preview render read it.
+*
+* SELF-EXPIRING: `scripts/check-nc-mirrors-in-sync.ts` reads this list as the
+* viewer's allowance and fails the day the viewer mirrors one of these kinds —
+* delete it from here then, and the served catalog names it again.
+*/
+var NC_TEMPLATE_HELD_BACK_SYSTEM_EVENT_KINDS = [
+	"device-tank-low",
+	"device-tank-full",
+	"device-tank-normal"
+];
+/**
+* The catalog as `getTemplateCatalog` SERVES it: every descriptor, with the
+* held-back kinds removed from its `systemEventKinds`. A descriptor that named
+* only held-back kinds is served with an empty list — offered to no system
+* rule an installed viewer can author, which is exactly true.
+*/
+function servedTemplateVars() {
+	return NC_TEMPLATE_VARS.map((d) => d.systemEventKinds === void 0 ? d : {
+		...d,
+		systemEventKinds: d.systemEventKinds.filter((kind) => !NC_TEMPLATE_HELD_BACK_SYSTEM_EVENT_KINDS.includes(kind))
+	});
+}
 /** The caption fields see a fixed, smaller vocabulary (`timelapsePreviewText`,
 *  `summaryCaptionText`). Declared here rather than as `fields` on every
 *  descriptor so the whole rule stays in one line of code. */
@@ -66179,6 +66354,9 @@ exports.NC_CONFIRM_DEFAULT_MAX_IMAGE_PX = NC_CONFIRM_DEFAULT_MAX_IMAGE_PX;
 exports.NC_CONFIRM_DEFAULT_TIMEOUT_MS = NC_CONFIRM_DEFAULT_TIMEOUT_MS;
 exports.NC_CONFIRM_MAX_TIMEOUT_MS = NC_CONFIRM_MAX_TIMEOUT_MS;
 exports.NC_CONFIRM_MIN_TIMEOUT_MS = NC_CONFIRM_MIN_TIMEOUT_MS;
+exports.NC_CONSUMABLE_LOW_PERCENT_DEFAULT = NC_CONSUMABLE_LOW_PERCENT_DEFAULT;
+exports.NC_CONSUMABLE_LOW_PERCENT_MAX = NC_CONSUMABLE_LOW_PERCENT_MAX;
+exports.NC_CONSUMABLE_SYSTEM_EVENT_KINDS = NC_CONSUMABLE_SYSTEM_EVENT_KINDS;
 exports.NC_DEFAULT_SNOOZE_MINUTES = NC_DEFAULT_SNOOZE_MINUTES;
 exports.NC_HISTORY_LIMIT_DEFAULT = NC_HISTORY_LIMIT_DEFAULT;
 exports.NC_HISTORY_LIMIT_MAX = NC_HISTORY_LIMIT_MAX;
@@ -66202,7 +66380,9 @@ exports.NC_SYSTEM_EVENT_FAMILY_FILTERS = NC_SYSTEM_EVENT_FAMILY_FILTERS;
 exports.NC_SYSTEM_EVENT_FILTER_KEYS = NC_SYSTEM_EVENT_FILTER_KEYS;
 exports.NC_SYSTEM_EVENT_KIND_GROUP_SPECS = NC_SYSTEM_EVENT_KIND_GROUP_SPECS;
 exports.NC_SYSTEM_RULE_KINDS = NC_SYSTEM_RULE_KINDS;
+exports.NC_TANK_SYSTEM_EVENT_KINDS = NC_TANK_SYSTEM_EVENT_KINDS;
 exports.NC_TAXONOMY = NC_TAXONOMY;
+exports.NC_TEMPLATE_HELD_BACK_SYSTEM_EVENT_KINDS = NC_TEMPLATE_HELD_BACK_SYSTEM_EVENT_KINDS;
 exports.NC_TEMPLATE_VARS = NC_TEMPLATE_VARS;
 exports.NC_UPDATE_EVENT_PACKAGE_NAMES = NC_UPDATE_EVENT_PACKAGE_NAMES;
 exports.NETWORK_LINK_TYPES = NETWORK_LINK_TYPES;
@@ -66851,6 +67031,7 @@ exports.conditionExclusionReason = conditionExclusionReason;
 exports.conditionVisibleForKind = conditionVisibleForKind;
 exports.connectionTestCapability = connectionTestCapability;
 exports.connectivityCapability = connectivityCapability;
+exports.consumableLowPercentOf = consumableLowPercentOf;
 exports.consumablesCapability = consumablesCapability;
 exports.contactCapability = contactCapability;
 exports.controlCapability = controlCapability;
@@ -67199,6 +67380,7 @@ exports.selectAssignedProfileSlots = require_sleep.selectAssignedProfileSlots;
 exports.sensorRaisedOf = sensorRaisedOf;
 exports.sensorTransitionNeverFires = sensorTransitionNeverFires;
 exports.sensorTransitionOffered = sensorTransitionOffered;
+exports.servedTemplateVars = servedTemplateVars;
 exports.serverManagementCapability = serverManagementCapability;
 exports.setByPath = setByPath;
 exports.settingsStoreCapability = settingsStoreCapability;