@camstack/addon-notifiers 1.2.20 → 1.2.21

package/dist/addon.js

@@ -13111,11 +13111,33 @@ var NotificationFormatSchema = _enum([
 * Named by INTENT, never by glyph. "check" would tie the vocabulary to one
 * renderer's icon set; "acknowledge" survives an adapter that draws it
 * differently.
+*
+* ── A TOKEN IS NOT A WIRE VALUE ─────────────────────────────────────
+*
+* These names are for US. **No adapter may forward one verbatim.** Each maps
+* the whole set onto its own renderer's vocabulary through a
+* `Record<NotificationActionIcon, string>` — a Record, never a lookup with a
+* fallback, so adding a member here fails every adapter's build until someone
+* decides its glyph, which is the only place that decision can be made
+* honestly.
+*
+* This paragraph is the bug. Zentik declared `actionIcons: true` and passed
+* `disarm` straight through; iOS feeds that string to
+* `UNNotificationActionIcon(systemImageName:)`, `disarm` is not an SF Symbol,
+* and every snooze and alarm button arrived BLANK. A pass-through is not a
+* mapping, and "the field is documented" is not "the value renders".
+*
+* Adding a member is TRAIN-BOUND. The enum lives in the published
+* `@camstack/server` closure and the cap seam validates against the HUB's copy,
+* so an addon that emits a token the running hub does not know does not lose an
+* icon — its whole `send` fails Zod validation and the notification never
+* arrives. Never emit a new token from an addon before the train carrying it.
 */
 var NotificationActionIconSchema = _enum([
 	"acknowledge",
 	"dismiss",
 	"silence",
+	"snooze",
 	"view",
 	"play",
 	"open",
@@ -13123,9 +13145,13 @@ var NotificationActionIconSchema = _enum([
 	"lock",
 	"unlock",
 	"arm",
+	"arm-home",
+	"arm-away",
+	"arm-night",
 	"disarm",
 	"light",
-	"alert"
+	"alert",
+	"camera"
 ]);
 /** A single tap-through action button. */
 var NotificationActionSchema = object({
@@ -13339,6 +13365,24 @@ var notificationOutputCapability = {
 		}), _void(), { kind: "mutation" })
 	}
 };
+new Set([
+	{
+		id: "person",
+		name: "Person"
+	},
+	{
+		id: "vehicle",
+		name: "Vehicle"
+	},
+	{
+		id: "animal",
+		name: "Animal"
+	},
+	{
+		id: "package",
+		name: "Package"
+	}
+].map((l) => l.id));
 var COCO_TO_MACRO = {
 	mapping: {
 		person: "person",
@@ -14136,6 +14180,8 @@ var NcSystemEventKindSchema = _enum([
 	"alarm-triggered",
 	"alarm-armed",
 	"alarm-disarmed",
+	"alarm-arming",
+	"alarm-arm-refused",
 	"camera-online",
 	"camera-offline",
 	"camera-disabled",
@@ -17368,6 +17414,22 @@ var detectionFpsField = {
 	default: 10,
 	step: 1
 };
+/**
+* The occupancy re-check interval. DEFAULT 300 s (2026-08-13 — was 30 s).
+*
+* The recheck is now on by default (a parked car is invisible to occupancy
+* rules until the stationary registry has been rebuilt by motion, which after a
+* restart may be never on a quiet camera). Each cycle re-subscribes a detection
+* session — an RTSP re-dial — so the switch is only affordable at a WIDE
+* interval: 300 s is ~12 re-dials an hour per camera, against 120 at the old
+* 30 s. A parked car is therefore counted within 5 minutes of a restart.
+*
+* Why not wider: `max` is 300 and raising it is TRAIN-BOUND, not addon-bound —
+* the host validates `attachCamera` against ITS copy of this schema, so a
+* runner asked for 600 would be rejected by the hub until a `@camstack/server`
+* carrying the wider bound is installed everywhere. 300 is the widest value
+* that ships with an addon deploy.
+*/
 var occupancyRecheckSecField = {
 	min: 0,
 	max: 300,
@@ -17569,15 +17631,21 @@ var RunnerCameraConfigSchema = object({
 	*/
 	onboardMotionDrivesAnalyzer: boolean().default(true),
 	/**
-	* Master toggle for the occupancy re-check. When `false` (DEFAULT) the runner
-	* never arms the periodic recheck timer, regardless of `occupancyRecheckSec` —
-	* this is off by default because the recheck re-subscribes a detection session
-	* every N seconds while `watching`, a major source of pull-decoder re-dial
-	* churn (each cycle creates+tears a session → RTSP re-dial → latency). The
+	* Master toggle for the occupancy re-check. When `false` the runner never arms
+	* the periodic recheck timer, regardless of `occupancyRecheckSec`; the
 	* `occupancyRecheckSec` / `occupancyRecheckFrames` sliders only take effect
 	* (and only render) when this is enabled.
-	*/
-	occupancyRecheckEnabled: boolean().default(false),
+	*
+	* DEFAULT `true` since 2026-08-13 (was `false`). It was off because the
+	* recheck re-subscribes a detection session every N seconds while `watching`
+	* — each cycle creates+tears a session ⇒ an RTSP re-dial ⇒ latency, a major
+	* pull-decoder churn source. What that bought was a blind spot: a STATIONARY
+	* object is counted only while the stationary registry holds it, and the
+	* registry rebuilds from motion, so after a restart a parked car was invisible
+	* to every occupancy rule until something moved in front of it. The churn is
+	* now paid on the interval instead — see `occupancyRecheckSecField`.
+	*/
+	occupancyRecheckEnabled: boolean().default(true),
 	occupancyRecheckSec: number().min(occupancyRecheckSecField.min).max(occupancyRecheckSecField.max).default(occupancyRecheckSecField.default),
 	occupancyRecheckFrames: number().min(occupancyRecheckFramesField.min).max(occupancyRecheckFramesField.max).default(occupancyRecheckFramesField.default),
 	/**
@@ -32433,6 +32501,21 @@ var ntfyAdapter = {
 				max: 1
 			},
 			actions: MAX_ACTIONS$1,
+			/**
+			* ntfy has NO per-action icon, and this says so out loud.
+			*
+			* Its action object is `{action, label, url, clear, headers, body}` and the
+			* `X-Actions` header form is `action, label, url[, extras]` — there is no
+			* icon field in either, and the `icon` ntfy does have is the NOTIFICATION's
+			* icon (an attachment URL, handled above), not a per-button one.
+			*
+			* Left EXPLICIT rather than absent: absent and `false` behave identically
+			* (the degrade engine reads a missing value as unsupported), but only one
+			* of them proves somebody checked. The degrade engine then strips the icon
+			* centrally and puts `actionIcons` in `renderedAs.dropped`, so the loss is
+			* reported instead of being discovered on a phone.
+			*/
+			actionIcons: false,
 			levels: [
 				{
 					id: "min",
@@ -33616,6 +33699,82 @@ function userIdsFrom(config) {
 	return [];
 }
 /**
+* Canonical icon token → the string Zentik's client actually renders.
+*
+* ── EVIDENCE (read from the Zentik sources, not guessed) ────────────
+* `NotificationActionDto.icon` is `@IsOptional() @IsString()` — the BACKEND
+* validates nothing, so a wrong value is accepted, stored and delivered. The
+* rendering happens on the client, and both iOS paths do the same thing
+* (`ZentikNotificationService/NotificationService.swift`,
+* `ZentikNotificationContentExtension/NotificationViewController.swift`):
+*
+*     let actualIconName = iconName.hasPrefix("sfsymbols:")
+*       ? String(iconName.dropFirst("sfsymbols:".count)) : iconName
+*     icon = UNNotificationActionIcon(systemImageName: actualIconName)
+*
+* So the value is an **SF Symbol name**, with an optional `sfsymbols:` prefix
+* that is stripped. Zentik's own UI confirms the convention: its icon field
+* placeholder is "e.g., house.fill, heart, gear" and its picker writes
+* `sfsymbols:${iconName}`.
+*
+* `UNNotificationActionIcon(systemImageName:)` with a name iOS does not know
+* renders NOTHING — silently. That is the whole failure: we sent `silence`,
+* `arm` and `disarm`, none of which are SF Symbols, and every button arrived
+* blank with nothing anywhere saying why.
+*
+* The prefix is emitted explicitly even though bare names work, because the
+* bare form is indistinguishable from an un-translated intent token in a
+* captured payload — and telling those two apart is what cost the time.
+*
+* A `Record` over the closed enum, NOT a lookup with a fallback: adding a
+* vocabulary member without deciding its glyph fails the build here.
+*
+* Android: Zentik's Android client does not render per-action icons at all
+* (an Android notification action needs a bundled drawable, not a name), so
+* this is an iOS/watchOS enrichment and a no-op elsewhere — which is a
+* cosmetic loss, not a wrong glyph.
+*/
+var ZENTIK_ACTION_ICONS = {
+	acknowledge: "checkmark.circle",
+	dismiss: "xmark.circle",
+	silence: "bell.slash",
+	snooze: "zzz",
+	view: "eye",
+	play: "play.fill",
+	open: "door.left.hand.open",
+	close: "door.left.hand.closed",
+	lock: "lock.fill",
+	unlock: "lock.open.fill",
+	arm: "shield.fill",
+	"arm-home": "house.fill",
+	"arm-away": "figure.walk",
+	"arm-night": "moon.fill",
+	disarm: "shield.slash.fill",
+	light: "lightbulb.fill",
+	alert: "exclamationmark.triangle.fill",
+	camera: "video.fill"
+};
+/** The `sfsymbols:` prefix Zentik's clients strip before resolving the symbol. */
+var SFSYMBOLS_PREFIX = "sfsymbols:";
+/**
+* The Zentik value for one icon token, or `undefined` when there is none.
+*
+* Typed on `string`, not on `NotificationActionIcon`, because that is what this
+* boundary actually receives: an addon deployed against a hub whose vocabulary
+* moved on hands over a token this build has never heard of. Omitting it is the
+* honest answer — forwarding it raw would put a string iOS ignores on the wire
+* and produce exactly the blank button this map exists to fix.
+*
+* `Object.hasOwn` and not a truthiness check: an inherited `toString` must not
+* read as a mapping.
+*/
+function zentikActionIcon(icon) {
+	const table = ZENTIK_ACTION_ICONS;
+	if (!Object.hasOwn(ZENTIK_ACTION_ICONS, icon)) return void 0;
+	const symbol = table[icon];
+	return symbol === void 0 ? void 0 : `${SFSYMBOLS_PREFIX}${symbol}`;
+}
+/**
 * How a `BACKGROUND_CALL` names its request: `METHOD::url`.
 *
 * The whole reason the type exists here: a "silence this for 30 minutes"
@@ -33627,9 +33786,10 @@ var BACKGROUND_CALL_PREFIX = "POST::";
 function actionsFor(prepared) {
 	const out = [];
 	for (const action of prepared.actions.slice(0, MAX_ACTIONS)) {
+		const symbol = action.icon === void 0 ? void 0 : zentikActionIcon(action.icon);
 		const decoration = {
 			...action.destructive !== void 0 ? { destructive: action.destructive } : {},
-			...action.icon !== void 0 ? { icon: action.icon } : {}
+			...symbol !== void 0 ? { icon: symbol } : {}
 		};
 		if (action.url === void 0 || action.url.length === 0) {
 			out.push({
@@ -33821,12 +33981,14 @@ var zentikAdapter = {
 			format: ["text"],
 			clickUrl: true,
 			/**
-			* `NotificationActionDto.icon` is a documented field, so the engine hands
-			* the icon over instead of stripping it centrally. What Zentik's client
-			* DRAWS for a given name is not documented — so the intent name travels
-			* verbatim, exactly as the webhook kind forwards it, and a name the app
-			* does not know renders as no icon rather than as a wrong one. This is a
-			* pass-through claim, not a rendering claim.
+			* A RENDERING claim, which it was not before.
+			*
+			* This used to say the intent name "travels verbatim … a name the app does
+			* not know renders as no icon rather than as a wrong one" — true, and it
+			* described a feature that never once drew an icon, because NO intent name
+			* is an SF Symbol. The engine handed the icon over and the adapter put it
+			* on the wire untranslated. `ZENTIK_ACTION_ICONS` is what makes this claim
+			* honest; keep it exhaustive or this reverts to a pass-through that lies.
 			*/
 			actionIcons: true,
 			sound: true,

package/dist/addon.mjs

@@ -13084,11 +13084,33 @@ var NotificationFormatSchema = _enum([
 * Named by INTENT, never by glyph. "check" would tie the vocabulary to one
 * renderer's icon set; "acknowledge" survives an adapter that draws it
 * differently.
+*
+* ── A TOKEN IS NOT A WIRE VALUE ─────────────────────────────────────
+*
+* These names are for US. **No adapter may forward one verbatim.** Each maps
+* the whole set onto its own renderer's vocabulary through a
+* `Record<NotificationActionIcon, string>` — a Record, never a lookup with a
+* fallback, so adding a member here fails every adapter's build until someone
+* decides its glyph, which is the only place that decision can be made
+* honestly.
+*
+* This paragraph is the bug. Zentik declared `actionIcons: true` and passed
+* `disarm` straight through; iOS feeds that string to
+* `UNNotificationActionIcon(systemImageName:)`, `disarm` is not an SF Symbol,
+* and every snooze and alarm button arrived BLANK. A pass-through is not a
+* mapping, and "the field is documented" is not "the value renders".
+*
+* Adding a member is TRAIN-BOUND. The enum lives in the published
+* `@camstack/server` closure and the cap seam validates against the HUB's copy,
+* so an addon that emits a token the running hub does not know does not lose an
+* icon — its whole `send` fails Zod validation and the notification never
+* arrives. Never emit a new token from an addon before the train carrying it.
 */
 var NotificationActionIconSchema = _enum([
 	"acknowledge",
 	"dismiss",
 	"silence",
+	"snooze",
 	"view",
 	"play",
 	"open",
@@ -13096,9 +13118,13 @@ var NotificationActionIconSchema = _enum([
 	"lock",
 	"unlock",
 	"arm",
+	"arm-home",
+	"arm-away",
+	"arm-night",
 	"disarm",
 	"light",
-	"alert"
+	"alert",
+	"camera"
 ]);
 /** A single tap-through action button. */
 var NotificationActionSchema = object({
@@ -13312,6 +13338,24 @@ var notificationOutputCapability = {
 		}), _void(), { kind: "mutation" })
 	}
 };
+new Set([
+	{
+		id: "person",
+		name: "Person"
+	},
+	{
+		id: "vehicle",
+		name: "Vehicle"
+	},
+	{
+		id: "animal",
+		name: "Animal"
+	},
+	{
+		id: "package",
+		name: "Package"
+	}
+].map((l) => l.id));
 var COCO_TO_MACRO = {
 	mapping: {
 		person: "person",
@@ -14109,6 +14153,8 @@ var NcSystemEventKindSchema = _enum([
 	"alarm-triggered",
 	"alarm-armed",
 	"alarm-disarmed",
+	"alarm-arming",
+	"alarm-arm-refused",
 	"camera-online",
 	"camera-offline",
 	"camera-disabled",
@@ -17341,6 +17387,22 @@ var detectionFpsField = {
 	default: 10,
 	step: 1
 };
+/**
+* The occupancy re-check interval. DEFAULT 300 s (2026-08-13 — was 30 s).
+*
+* The recheck is now on by default (a parked car is invisible to occupancy
+* rules until the stationary registry has been rebuilt by motion, which after a
+* restart may be never on a quiet camera). Each cycle re-subscribes a detection
+* session — an RTSP re-dial — so the switch is only affordable at a WIDE
+* interval: 300 s is ~12 re-dials an hour per camera, against 120 at the old
+* 30 s. A parked car is therefore counted within 5 minutes of a restart.
+*
+* Why not wider: `max` is 300 and raising it is TRAIN-BOUND, not addon-bound —
+* the host validates `attachCamera` against ITS copy of this schema, so a
+* runner asked for 600 would be rejected by the hub until a `@camstack/server`
+* carrying the wider bound is installed everywhere. 300 is the widest value
+* that ships with an addon deploy.
+*/
 var occupancyRecheckSecField = {
 	min: 0,
 	max: 300,
@@ -17542,15 +17604,21 @@ var RunnerCameraConfigSchema = object({
 	*/
 	onboardMotionDrivesAnalyzer: boolean().default(true),
 	/**
-	* Master toggle for the occupancy re-check. When `false` (DEFAULT) the runner
-	* never arms the periodic recheck timer, regardless of `occupancyRecheckSec` —
-	* this is off by default because the recheck re-subscribes a detection session
-	* every N seconds while `watching`, a major source of pull-decoder re-dial
-	* churn (each cycle creates+tears a session → RTSP re-dial → latency). The
+	* Master toggle for the occupancy re-check. When `false` the runner never arms
+	* the periodic recheck timer, regardless of `occupancyRecheckSec`; the
 	* `occupancyRecheckSec` / `occupancyRecheckFrames` sliders only take effect
 	* (and only render) when this is enabled.
-	*/
-	occupancyRecheckEnabled: boolean().default(false),
+	*
+	* DEFAULT `true` since 2026-08-13 (was `false`). It was off because the
+	* recheck re-subscribes a detection session every N seconds while `watching`
+	* — each cycle creates+tears a session ⇒ an RTSP re-dial ⇒ latency, a major
+	* pull-decoder churn source. What that bought was a blind spot: a STATIONARY
+	* object is counted only while the stationary registry holds it, and the
+	* registry rebuilds from motion, so after a restart a parked car was invisible
+	* to every occupancy rule until something moved in front of it. The churn is
+	* now paid on the interval instead — see `occupancyRecheckSecField`.
+	*/
+	occupancyRecheckEnabled: boolean().default(true),
 	occupancyRecheckSec: number().min(occupancyRecheckSecField.min).max(occupancyRecheckSecField.max).default(occupancyRecheckSecField.default),
 	occupancyRecheckFrames: number().min(occupancyRecheckFramesField.min).max(occupancyRecheckFramesField.max).default(occupancyRecheckFramesField.default),
 	/**
@@ -32406,6 +32474,21 @@ var ntfyAdapter = {
 				max: 1
 			},
 			actions: MAX_ACTIONS$1,
+			/**
+			* ntfy has NO per-action icon, and this says so out loud.
+			*
+			* Its action object is `{action, label, url, clear, headers, body}` and the
+			* `X-Actions` header form is `action, label, url[, extras]` — there is no
+			* icon field in either, and the `icon` ntfy does have is the NOTIFICATION's
+			* icon (an attachment URL, handled above), not a per-button one.
+			*
+			* Left EXPLICIT rather than absent: absent and `false` behave identically
+			* (the degrade engine reads a missing value as unsupported), but only one
+			* of them proves somebody checked. The degrade engine then strips the icon
+			* centrally and puts `actionIcons` in `renderedAs.dropped`, so the loss is
+			* reported instead of being discovered on a phone.
+			*/
+			actionIcons: false,
 			levels: [
 				{
 					id: "min",
@@ -33589,6 +33672,82 @@ function userIdsFrom(config) {
 	return [];
 }
 /**
+* Canonical icon token → the string Zentik's client actually renders.
+*
+* ── EVIDENCE (read from the Zentik sources, not guessed) ────────────
+* `NotificationActionDto.icon` is `@IsOptional() @IsString()` — the BACKEND
+* validates nothing, so a wrong value is accepted, stored and delivered. The
+* rendering happens on the client, and both iOS paths do the same thing
+* (`ZentikNotificationService/NotificationService.swift`,
+* `ZentikNotificationContentExtension/NotificationViewController.swift`):
+*
+*     let actualIconName = iconName.hasPrefix("sfsymbols:")
+*       ? String(iconName.dropFirst("sfsymbols:".count)) : iconName
+*     icon = UNNotificationActionIcon(systemImageName: actualIconName)
+*
+* So the value is an **SF Symbol name**, with an optional `sfsymbols:` prefix
+* that is stripped. Zentik's own UI confirms the convention: its icon field
+* placeholder is "e.g., house.fill, heart, gear" and its picker writes
+* `sfsymbols:${iconName}`.
+*
+* `UNNotificationActionIcon(systemImageName:)` with a name iOS does not know
+* renders NOTHING — silently. That is the whole failure: we sent `silence`,
+* `arm` and `disarm`, none of which are SF Symbols, and every button arrived
+* blank with nothing anywhere saying why.
+*
+* The prefix is emitted explicitly even though bare names work, because the
+* bare form is indistinguishable from an un-translated intent token in a
+* captured payload — and telling those two apart is what cost the time.
+*
+* A `Record` over the closed enum, NOT a lookup with a fallback: adding a
+* vocabulary member without deciding its glyph fails the build here.
+*
+* Android: Zentik's Android client does not render per-action icons at all
+* (an Android notification action needs a bundled drawable, not a name), so
+* this is an iOS/watchOS enrichment and a no-op elsewhere — which is a
+* cosmetic loss, not a wrong glyph.
+*/
+var ZENTIK_ACTION_ICONS = {
+	acknowledge: "checkmark.circle",
+	dismiss: "xmark.circle",
+	silence: "bell.slash",
+	snooze: "zzz",
+	view: "eye",
+	play: "play.fill",
+	open: "door.left.hand.open",
+	close: "door.left.hand.closed",
+	lock: "lock.fill",
+	unlock: "lock.open.fill",
+	arm: "shield.fill",
+	"arm-home": "house.fill",
+	"arm-away": "figure.walk",
+	"arm-night": "moon.fill",
+	disarm: "shield.slash.fill",
+	light: "lightbulb.fill",
+	alert: "exclamationmark.triangle.fill",
+	camera: "video.fill"
+};
+/** The `sfsymbols:` prefix Zentik's clients strip before resolving the symbol. */
+var SFSYMBOLS_PREFIX = "sfsymbols:";
+/**
+* The Zentik value for one icon token, or `undefined` when there is none.
+*
+* Typed on `string`, not on `NotificationActionIcon`, because that is what this
+* boundary actually receives: an addon deployed against a hub whose vocabulary
+* moved on hands over a token this build has never heard of. Omitting it is the
+* honest answer — forwarding it raw would put a string iOS ignores on the wire
+* and produce exactly the blank button this map exists to fix.
+*
+* `Object.hasOwn` and not a truthiness check: an inherited `toString` must not
+* read as a mapping.
+*/
+function zentikActionIcon(icon) {
+	const table = ZENTIK_ACTION_ICONS;
+	if (!Object.hasOwn(ZENTIK_ACTION_ICONS, icon)) return void 0;
+	const symbol = table[icon];
+	return symbol === void 0 ? void 0 : `${SFSYMBOLS_PREFIX}${symbol}`;
+}
+/**
 * How a `BACKGROUND_CALL` names its request: `METHOD::url`.
 *
 * The whole reason the type exists here: a "silence this for 30 minutes"
@@ -33600,9 +33759,10 @@ var BACKGROUND_CALL_PREFIX = "POST::";
 function actionsFor(prepared) {
 	const out = [];
 	for (const action of prepared.actions.slice(0, MAX_ACTIONS)) {
+		const symbol = action.icon === void 0 ? void 0 : zentikActionIcon(action.icon);
 		const decoration = {
 			...action.destructive !== void 0 ? { destructive: action.destructive } : {},
-			...action.icon !== void 0 ? { icon: action.icon } : {}
+			...symbol !== void 0 ? { icon: symbol } : {}
 		};
 		if (action.url === void 0 || action.url.length === 0) {
 			out.push({
@@ -33794,12 +33954,14 @@ var zentikAdapter = {
 			format: ["text"],
 			clickUrl: true,
 			/**
-			* `NotificationActionDto.icon` is a documented field, so the engine hands
-			* the icon over instead of stripping it centrally. What Zentik's client
-			* DRAWS for a given name is not documented — so the intent name travels
-			* verbatim, exactly as the webhook kind forwards it, and a name the app
-			* does not know renders as no icon rather than as a wrong one. This is a
-			* pass-through claim, not a rendering claim.
+			* A RENDERING claim, which it was not before.
+			*
+			* This used to say the intent name "travels verbatim … a name the app does
+			* not know renders as no icon rather than as a wrong one" — true, and it
+			* described a feature that never once drew an icon, because NO intent name
+			* is an SF Symbol. The engine handed the icon over and the adapter put it
+			* on the wire untranslated. `ZENTIK_ACTION_ICONS` is what makes this claim
+			* honest; keep it exhaustive or this reverts to a pass-through that lies.
 			*/
 			actionIcons: true,
 			sound: true,

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@camstack/addon-notifiers",
-  "version": "1.2.20",
+  "version": "1.2.21",
   "description": "System notifiers addon for CamStack — a `notification-output` collection provider hosting per-kind notifier adapters (ntfy, pushover, gotify, telegram, discord, webhook, zentik).",
   "keywords": [
     "camstack",