@camstack/addon-post-analysis 1.2.281 → 1.2.283

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

@@ -5391,7 +5391,7 @@ var ZodIssueCode = {
 var ZodFirstPartyTypeKind;
 ZodFirstPartyTypeKind || (ZodFirstPartyTypeKind = {});
 //#endregion
-//#region ../types/dist/sleep-D_4W7xuQ.mjs
+//#region ../types/dist/sleep-DU7mu4wb.mjs
 /**
 * The audio chunk plane's byte format, and the ONE expansion from a coded
 * window to float samples (D455).
@@ -17956,6 +17956,9 @@ var NcSystemEventKindSchema = _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",
@@ -18016,6 +18019,18 @@ var NC_ALARM_SYSTEM_EVENT_KINDS = [
 	"alarm-disarmed"
 ];
 /**
+* 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"
+];
+/**
 * 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.
@@ -18049,8 +18064,27 @@ var NcSystemEventConditionSchema = object({
 	*/
 	excludeDeviceIds: array(number().int()).min(1).optional(),
 	nodeIds: array(string().min(1)).min(1).optional(),
-	packageNames: array(string().min(1)).min(1).optional()
+	packageNames: array(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: number().int().min(1).max(95).optional()
 });
+/** The consumable threshold a system-event condition judges at (D642). */
+function consumableLowPercentOf(condition) {
+	return condition.consumableLowPercent ?? 15;
+}
 /** Hard ceiling on a window (24h). A snooze that could not expire would be an
 *  outage the operator asked for once and forgot. */
 var NC_SNOOZE_MAX_MINUTES = 1440;
@@ -18209,6 +18243,16 @@ var NcCrossingSchema = _enum([
 	"exit",
 	"any"
 ]);
+/**
+* Which edge of a BOOLEAN sensor fires a device-event rule (D640).
+*  - `raised`  — the sensor went high: water detected, smoke, open, tampered.
+*  - `cleared` — it went back: dry, clear, closed.
+*  - absent    — both edges, which is what every rule authored before this did.
+*
+* There is no third member for "both": absence already says it, and a value
+* that means the same as absence is a second way to write one rule.
+*/
+var NcSensorTransitionSchema = _enum(["raised", "cleared"]);
 /** Admin-zone membership condition (zone IDs as stamped by the ZoneEngine). */
 var NcZoneConditionSchema = object({
 	ids: array(string().min(1)).min(1),
@@ -18398,6 +18442,20 @@ var NcConditionsSchema = object({
 	scene: NcSceneConditionSchema.optional(),
 	/** Device scope — absent = all devices. */
 	devices: array(number()).optional(),
+	/**
+	* Device EXCLUSION (D641) — "every device except these". Judged on the SAME
+	* subject ids {@link devices} is judged on (the camera, the sensor that
+	* fired, a linked set's sensor and row cameras), so a sensor fanned out per
+	* linked camera is excluded exactly where an include would have tested it.
+	* `min(1)`: an empty exclusion excludes nothing and is written as absent.
+	*
+	* Not for `system-event` rules — those carry their own
+	* `systemEvent.excludeDeviceIds` (D636), and the hub refuses this key there.
+	* Editors present the two lists as ONE field (All | Only these | All except
+	* these); the engine evaluates each independently, so a legacy rule
+	* carrying both still means "these, minus those".
+	*/
+	devicesExclude: array(number()).min(1).optional(),
 	/** Detector class names (any overlap with the record's class set). */
 	classes: array(string().min(1)).optional(),
 	/** Veto classes — any overlap fails the rule. */
@@ -18531,6 +18589,16 @@ var NcConditionsSchema = object({
 	*/
 	sensorKinds: array(string().min(1)).optional(),
 	/**
+	* DEVICE-EVENT only (D640). Fire on one edge of a boolean sensor —
+	* {@link NcSensorTransitionSchema}. Which field of the slice means "raised"
+	* is `@camstack/types` → `notification/sensor-raised.ts`. A reading the
+	* engine cannot place (a kind with no raise, an unreadable slice) PASSES:
+	* the condition fails open towards notifying, never towards silence. Editors
+	* offer it only when every chosen {@link sensorKinds} member has a raise
+	* (`sensorTransitionOffered`), and the hub refuses it on any other delivery.
+	*/
+	sensorTransition: NcSensorTransitionSchema.optional(),
+	/**
 	* PACKAGE-EVENT only. Which package phase fires the rule — `delivered`
 	* (a parked parcel appeared), `picked-up` (it departed), or `both`. Fails
 	* when the subject's phase does not match (a subject always carries a phase
@@ -19149,6 +19217,7 @@ var NcConditionDescriptorSchema = object({
 	/** Editor widget the UI renders — never hardcode per-condition forms. */
 	valueType: _enum([
 		"deviceIdList",
+		"deviceIdExcludeList",
 		"stringList",
 		"number01",
 		"number",
@@ -19159,6 +19228,7 @@ var NcConditionDescriptorSchema = object({
 		"plateMatcher",
 		"packagePhase",
 		"crossingSelect",
+		"sensorTransition",
 		"polygonDraw",
 		"occupancy",
 		"audio",
@@ -19292,6 +19362,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"
@@ -19357,6 +19439,21 @@ var NC_CONDITION_CATALOG = [
 		phase: "P1",
 		description: "Restrict the rule to these devices; absent = all devices. A sensor event matches either the SENSOR that fired or the camera it is attributed to, so a rule may name either one."
 	},
+	{
+		id: "devicesExclude",
+		group: "scope",
+		label: "Excluded devices",
+		valueType: "deviceIdExcludeList",
+		operator: "notIn",
+		appliesTo: [
+			"immediate",
+			"track-end",
+			"device-event",
+			"package-event"
+		],
+		phase: "P1",
+		description: "Every device except these. Judged on the same device ids as Devices: a sensor event is excluded by the SENSOR that fired or by the camera it is attributed to."
+	},
 	{
 		id: "classes",
 		group: "class",
@@ -19613,6 +19710,33 @@ var NC_CONDITION_CATALOG = [
 		phase: "P1",
 		description: "Raw device event-type tokens (e.g. doorbell press / press_long) from the event-emitter slice; absent on doorbell-pulse / passive sensors."
 	},
+	{
+		id: "sensorTransition",
+		group: "device",
+		label: "Notify when",
+		valueType: "sensorTransition",
+		options: [
+			{
+				value: "",
+				label: "It triggers and when it clears",
+				hint: "Every change: water detected, and back to dry."
+			},
+			{
+				value: "raised",
+				label: "Only when it triggers",
+				hint: "Water detected, smoke, a contact opening — never the return to normal."
+			},
+			{
+				value: "cleared",
+				label: "Only when it clears",
+				hint: "Back to dry, smoke gone, a contact closing — never the alert itself."
+			}
+		],
+		operator: "in",
+		appliesTo: ["device-event"],
+		phase: "P2",
+		description: "Fire on one edge of a boolean sensor. Offered only when every chosen sensor kind raises and clears; a reading that cannot be placed still notifies."
+	},
 	{
 		id: "packagePhase",
 		group: "package",
@@ -19796,6 +19920,28 @@ var NcHistoryFilterSchema = object({
 	limit: number().int().min(1).max(500).default(100)
 });
 /**
+* Every rule's last run, in one answer.
+*
+* A rule ABSENT from `runs` produced no delivery inside `horizonMs` — how far
+* back this answer looked, in ms before the hub's now. It is the outbox prune
+* window (7 days by default, operator-configurable), NARROWED when the read hit
+* its row bound: the answer never claims a window it did not read. `null` means
+* the operator keeps the outbox forever AND the read reached its end, so absent
+* means "never on record". A UI derives its "not in the last N days" from this
+* value, never from a constant — and only when the call ANSWERED (D315).
+*/
+var NcRuleLastRunsSchema = object({
+	runs: array(object({
+		ruleId: string(),
+		/** Fire time of the newest row (`createdAt`, epoch ms). */
+		lastAt: number(),
+		status: NcHistoryStatusSchema,
+		/** The camera/device of that row (a digest row files under its first camera). */
+		deviceId: number()
+	})),
+	horizonMs: number().nonnegative().nullable()
+});
+/**
 * What a snooze covers. Broader scopes win when several overlap, so one window
 * leaves ONE digest rather than a rule snooze and a whole-feed snooze both
 * summarising the same silence.
@@ -19977,6 +20123,14 @@ var NcAlarmModeCoverageSchema = object({
 	/** Ids named by the covering rules. A SUBSET when `allDevices` is true. */
 	deviceIds: array(number().int()),
 	/**
+	* D641: the ids NOT covered although `allDevices` is true — every unscoped
+	* covering rule EXCLUDES them (`conditions.devicesExclude`) and no named rule
+	* covers them. Always `[]` when `allDevices` is false. Excluded by the rules,
+	* which is not the same as skipped by a switch: never in `skippedDevices`.
+	* Defaulted so an answer computed before this field parses as "none".
+	*/
+	allDevicesExcept: array(number().int()).default([]),
+	/**
 	* Devices this mode NAMES but cannot actually arm, each with the switch that
 	* excludes it.
 	*
@@ -20200,6 +20354,15 @@ var notificationRulesCapability = {
 		*/
 		getHistory: method(object({ filter: NcHistoryFilterSchema.default({ limit: 100 }) }), object({ entries: array(NcHistoryEntrySchema) }), { auth: "admin" }),
 		/**
+		* The newest delivery of every rule, in ONE bounded read of the outbox —
+		* the "Last run" column. Never a `getHistory` per rule. A rule with no
+		* delivery inside `horizonMs` is absent from `runs`; see
+		* {@link NcRuleLastRunsSchema} for what absent means. A store that cannot
+		* answer FAILS the call rather than answering "nothing ran". Admin-only,
+		* like `getHistory`, of which it is a projection.
+		*/
+		getRuleLastRuns: method(object({}), NcRuleLastRunsSchema, { auth: "admin" }),
+		/**
 		* Mint a fresh, externally-reachable URL for one artefact a history row
 		* named in {@link NcHistoryEntrySchema.shape.artifactIds} — the SAME
 		* signed-link mechanism the dispatcher uses to attach media to an
@@ -29606,12 +29769,20 @@ reset: method(object({
 	},
 	runtimeState: ConsumablesStatusSchema.extend({ lastFetchedAt: 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"]
 };
 /**
 * Door / window / opening / garage / valve contact sensor. Boolean
@@ -44977,6 +45148,12 @@ Object.freeze({
 		addonId: null,
 		access: "view"
 	},
+	"notificationRules.getRuleLastRuns": {
+		capName: "notification-rules",
+		capScope: "system",
+		addonId: null,
+		access: "view"
+	},
 	"notificationRules.getTemplateCatalog": {
 		capName: "notification-rules",
 		capScope: "system",
@@ -50593,12 +50770,55 @@ function audioModeOf(value) {
 	return null;
 }
 new Set(["devices", "classes"]);
-/** 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`?
@@ -50612,6 +50832,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);
 	}
 }
 /**
@@ -50647,6 +50868,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",
@@ -50678,7 +50902,7 @@ var NC_SYSTEM_EVENT_FAMILY = {
 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.
@@ -50687,7 +50911,8 @@ var NC_SYSTEM_EVENT_FAMILY_FILTERS = {
 	"device-events": [
 		"deviceIds",
 		"excludeDeviceIds",
-		"deviceTypes"
+		"deviceTypes",
+		"consumableLowPercent"
 	],
 	system: ["nodeIds", "packageNames"],
 	alarm: ["deviceIds"]
@@ -50722,6 +50947,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",
@@ -50901,10 +51136,75 @@ function isScheduleActive(schedule, atMs) {
 	}
 	return schedule.invert === true ? !inside : inside;
 }
+var ARMED_WORD_PREFIX = "armed_";
+var ALARM_PANEL_CAP = "alarm-panel";
+var ALARM_PANEL_TRIGGER_METHOD = "trigger";
+/**
+* A rule belongs to the alarm when its `deviceState` gate names ANY device's
+* `armed_*` word, or an ENABLED `onTrigger` sequence pulls the alarm panel's
+* trigger (D630).
+*/
+function ruleBelongsToAlarm(rule) {
+	if ((rule.conditions.deviceState?.states ?? []).some((s) => s.trim().toLowerCase().startsWith(ARMED_WORD_PREFIX))) return true;
+	return (rule.onTrigger ?? []).some((sequence) => sequence.enabled && sequence.actions.some((step) => step.kind === "cap" && step.cap === ALARM_PANEL_CAP && step.method === ALARM_PANEL_TRIGGER_METHOD));
+}
+/**
+* WHICH WAY A BOOLEAN SENSOR MOVED — read off the one slice a sensor event
+* persists (D640 "a sensor rule fires on the raise, the clear, or both").
+*
+* A device-event rule over a flood sensor notified on BOTH edges: water
+* detected, and back to dry. `NcConditions.sensorTransition` lets the rule
+* name one edge; this file answers, for one `SensorEvent`, which edge it is.
+*
+* NOT A SECOND TABLE. The "which boolean of this cap counts as HIGH" question
+* already has one answer, `SOURCE_CAP_ACTIVE_FIELD`
+* (`catalogs/sensor-active-state.ts`, the doorbell's and the recorder's edge
+* table), and a sensor event names its kind, not its cap. So the table here is
+* DERIVED: event kind → cap (`EVENT_KIND_BY_CAP`) → that cap's active field.
+* Only kinds whose taxonomy category is `sensor` take part — a switch has an
+* `on` boolean too, but "it triggers / it clears" is not a sentence about a
+* light, and offering it there would be a knob with a misleading label.
+* `presence` is a WORD (`home` / `not_home` / a zone), not a boolean, and is
+* absent from the source table, so it is absent here.
+*
+* `undefined` = never guessed: a kind with no raise (a doorbell press, a
+* button, a cover), or a slice whose field is missing or not a boolean. The
+* engine then does NOT filter — a flood alert must not go silent because one
+* read came back unreadable (the same stance as the alarm's `sensorEdgeOf`).
+*
+* Pure, RN-safe: the viewer imports the support rule from here.
+*/
+/** Event kind → the boolean field of its cap slice that means "raised". */
+var NC_SENSOR_RAISED_FIELD_BY_KIND = Object.freeze(Object.fromEntries(Object.entries(EVENT_KIND_BY_CAP).flatMap(([capName, descriptor]) => {
+	const field = SOURCE_CAP_ACTIVE_FIELD[capName];
+	if (field === void 0 || descriptor.category !== "sensor") return [];
+	return [[descriptor.kind, field]];
+})));
+/** The sensor kinds `sensorTransition` means something for. */
+var NC_SENSOR_TRANSITION_KINDS = Object.freeze(Object.keys(NC_SENSOR_RAISED_FIELD_BY_KIND));
+function normaliseKind(kind) {
+	return kind.trim().toLowerCase();
+}
+/**
+* true = the sensor is raised (water, smoke, open, tampered…), false = it
+* cleared, undefined = this kind has no raise or the slice cannot say.
+*/
+function sensorRaisedOf(kind, value) {
+	if (value === null) return void 0;
+	const field = NC_SENSOR_RAISED_FIELD_BY_KIND[normaliseKind(kind)];
+	if (field === void 0) return void 0;
+	const raw = Object.entries(value).find(([key]) => key === field)?.[1];
+	return typeof raw === "boolean" ? raw : void 0;
+}
 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",
@@ -50930,6 +51230,7 @@ var DEVICE_EVENTS = [
 	"device-enabled",
 	...BATTERY,
 	...CONSUMABLE,
+	...TANK,
 	"stream-online",
 	"stream-offline",
 	"detection-blind",
@@ -51227,6 +51528,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",
@@ -51619,6 +51931,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. */
@@ -52885,18 +53229,36 @@ Object.defineProperty(exports, "NC_CONDITION_CATALOG", {
 		return NC_CONDITION_CATALOG;
 	}
 });
+Object.defineProperty(exports, "NC_CONSUMABLE_SYSTEM_EVENT_KINDS", {
+	enumerable: true,
+	get: function() {
+		return NC_CONSUMABLE_SYSTEM_EVENT_KINDS;
+	}
+});
 Object.defineProperty(exports, "NC_DEFAULT_SNOOZE_MINUTES", {
 	enumerable: true,
 	get: function() {
 		return NC_DEFAULT_SNOOZE_MINUTES;
 	}
 });
+Object.defineProperty(exports, "NC_SENSOR_TRANSITION_KINDS", {
+	enumerable: true,
+	get: function() {
+		return NC_SENSOR_TRANSITION_KINDS;
+	}
+});
 Object.defineProperty(exports, "NC_SNOOZE_MAX_MINUTES", {
 	enumerable: true,
 	get: function() {
 		return NC_SNOOZE_MAX_MINUTES;
 	}
 });
+Object.defineProperty(exports, "NC_TANK_SYSTEM_EVENT_KINDS", {
+	enumerable: true,
+	get: function() {
+		return NC_TANK_SYSTEM_EVENT_KINDS;
+	}
+});
 Object.defineProperty(exports, "NC_TAXONOMY", {
 	enumerable: true,
 	get: function() {
@@ -53179,6 +53541,12 @@ Object.defineProperty(exports, "canonicalHash", {
 		return canonicalHash;
 	}
 });
+Object.defineProperty(exports, "consumableLowPercentOf", {
+	enumerable: true,
+	get: function() {
+		return consumableLowPercentOf;
+	}
+});
 Object.defineProperty(exports, "cosineSimilarity", {
 	enumerable: true,
 	get: function() {
@@ -53431,12 +53799,30 @@ Object.defineProperty(exports, "resolvePoolMemoryPolicy", {
 		return resolvePoolMemoryPolicy;
 	}
 });
+Object.defineProperty(exports, "ruleBelongsToAlarm", {
+	enumerable: true,
+	get: function() {
+		return ruleBelongsToAlarm;
+	}
+});
 Object.defineProperty(exports, "sceneMonitorCapability", {
 	enumerable: true,
 	get: function() {
 		return sceneMonitorCapability;
 	}
 });
+Object.defineProperty(exports, "sensorRaisedOf", {
+	enumerable: true,
+	get: function() {
+		return sensorRaisedOf;
+	}
+});
+Object.defineProperty(exports, "servedTemplateVars", {
+	enumerable: true,
+	get: function() {
+		return servedTemplateVars;
+	}
+});
 Object.defineProperty(exports, "sleep", {
 	enumerable: true,
 	get: function() {