@camstack/addon-osd-manager 0.1.153 → 0.1.155

package/dist/index.js

@@ -7523,7 +7523,7 @@ var DeviceRole = /* @__PURE__ */ function(DeviceRole) {
 	return DeviceRole;
 }({});
 //#endregion
-//#region ../types/dist/composition-43aqsZQj.mjs
+//#region ../types/dist/composition-D7ULvLdD.mjs
 /**
 * The ffmpeg build every CamStack node downloads, per platform and arch.
 *
@@ -7577,20 +7577,20 @@ function portable(target) {
 }
 portable("linux64"), portable("linuxarm64"), portable("macarm64"), portable("mac64");
 /**
-* LA tabella "quale booleano di questo tipo di device conta come ALTO", e il
-* valutatore puro del suo FRONTE.
+* THE table "which boolean of this device type counts as HIGH", and the
+* pure evaluator of its EDGE.
 *
-* UNA tabella per tutti quelli che chiedono "questo device è ALTO?": il
-* trigger `RecordingTriggers.sensorDeviceIds` del recorder, i marker dei
-* sensori della post-analysis, il bridge camera-sensors dell'orchestratore e
-* le sorgenti di un campanello composto (`doorbellFeatureSources`, D671).
-* Una seconda copia divergerebbe alla prima cap aggiunta, e il sintomo — "il
-* sensore fa suonare il campanello ma non registra" — è esattamente D62.
+* ONE table for everyone who asks "is this device HIGH?": the
+* recorder's `RecordingTriggers.sensorDeviceIds` trigger, the post-analysis
+* sensor markers, the orchestrator's camera-sensors bridge and
+* the sources of a composite doorbell (`doorbellFeatureSources`, D671).
+* A second copy would diverge at the first cap added, and the symptom — "the
+* sensor rings the doorbell but does not record" — is exactly D62.
 *
-* ⚠ NON è `DEVICE_STATE_READERS` (`catalogs/device-state-vocabulary.ts`), e le
-* due non vanno unificate: quella risponde a "qual è la PAROLA di stato per una
-* regola" (e include `presence`, `cover`, `alarm-panel`), questa a "qual è il
-* booleano il cui FRONTE conta". Vocabolari deliberatamente diversi.
+* ⚠ NOT `DEVICE_STATE_READERS` (`catalogs/device-state-vocabulary.ts`), and the
+* two must not be unified: that one answers "what is the state WORD for a
+* rule" (and includes `presence`, `cover`, `alarm-panel`), this one "which
+* boolean's EDGE counts". Deliberately different vocabularies.
 */
 /**
 * Known binary / switch source caps → the boolean slice field whose
@@ -9197,22 +9197,22 @@ var CLASS_MAP_MACRO_TARGETS = [
 	"package"
 ];
 /**
-* Le macro classi di PRIMO LIVELLO: quelle che un object detector emette e che
-* un operatore può selezionare.
+* The FIRST-LEVEL macro classes: those an object detector emits and that
+* an operator can select.
 *
-* Sono le tre offerte dallo step `object-detection`
+* They are the three offered by the `object-detection` step
 * (`addon-pipeline/src/detection-pipeline/registry/step-definitions.ts`,
-* `enabledMacroClasses`). `package` sta in {@link CLASS_MAP_MACRO_TARGETS} e in
-* `MACRO_LABELS` — è una macro vera — ma NON qui: appartiene allo step
-* `package-detection`, la cui abilitazione è guidata dalle zone, e offrire la
-* stessa parola due volte ha già fatto accendere a un operatore il proxy COCO
+* `enabledMacroClasses`). `package` is in {@link CLASS_MAP_MACRO_TARGETS} and in
+* `MACRO_LABELS` — it is a true macro — but NOT here: it belongs to the step
+* `package-detection`, whose enablement is driven by zones, and offering the
+* same word twice has already made an operator turn on the COCO proxy
 * (suitcase/backpack/handbag) lasciando spento il detector dedicato.
 *
-* UNA lista. Prima di oggi le stesse tre erano scritte a mano nell'offerta
-* dello step e una seconda volta come union `FirstLevelMacro`
-* (`types/detection.ts`); una terza copia per il trigger di registrazione
-* (`RecordingTriggers.objectClasses`) avrebbe reso invisibile la divergenza
-* successiva.
+* ONE list. Before today the same three were hand-written in the step's offer
+* and a second time as the union `FirstLevelMacro`
+* (`types/detection.ts`); a third copy for the recording trigger
+* (`RecordingTriggers.objectClasses`) would have made the later divergence
+* invisible.
 */
 var FIRST_LEVEL_MACRO_CLASSES = [
 	"person",
@@ -9277,17 +9277,17 @@ var RecordingStorageModeSchema = _enum([
 	"on-device-decision"
 ]);
 /**
-* Le macro classi che possono aprire una finestra di registrazione — le stesse
-* tre offerte dallo step `object-detection`, da UNA lista
+* The macro classes that can open a recording window — the same
+* three offered by the `object-detection` step, from ONE list
 * ({@link FIRST_LEVEL_MACRO_CLASSES}).
 */
 var RecordingObjectTriggerClassSchema = _enum(FIRST_LEVEL_MACRO_CLASSES);
 /**
-* True quando `values` non ripete un elemento.
+* True when `values` does not repeat an element.
 *
-* Un duplicato non è innocuo: ogni voce di `objectClasses` / `sensorDeviceIds`
-* diventa una SORGENTE in `bandTriggerSources`, e la stessa sorgente due volte
-* conterebbe due volte le sue finestre in `segmentMissedByMs`.
+* A duplicate is not harmless: every entry of `objectClasses` / `sensorDeviceIds`
+* becomes a SOURCE in `bandTriggerSources`, and the same source twice
+* would count its windows twice in `segmentMissedByMs`.
 */
 var noDuplicates = (values) => new Set(values).size === values.length;
 /** Which detectors trigger an `events`-mode band. */
@@ -9295,34 +9295,34 @@ var RecordingTriggersSchema = object({
 	motion: boolean().optional(),
 	audioThresholdDbfs: number().optional(),
 	/**
-	* Le macro classi la cui detection apre una finestra. ASSENTE = la sorgente
-	* non è ascoltata; un array VUOTO è rifiutato, perché "banda events, trigger
-	* object acceso, nessuna classe" è la stessa forma "abilitata e non registra
-	* nulla, per sempre" contro cui è scritto `eventsBandCanEverDemand`.
+	* The macro classes whose detection opens a window. ABSENT = the source
+	* is not listened to; an EMPTY array is rejected, because "events band, object
+	* trigger on, no class" is the same shape "enabled and records
+	* nothing, forever" that `eventsBandCanEverDemand` is written against.
 	*
-	* Il segnale letto è GIÀ FILTRATO: solo detection `source: 'pipeline'`, cioè
-	* quelle che hanno attraversato `enabledMacroClasses`, i
-	* `minConfidence<Macro>` e il full-frame guard. L'AI a bordo camera
-	* (`source: 'onboard'`) non attraversa nessuno di quei gate e NON apre
-	* finestre — vedi `recorder/object-trigger.ts`.
+	* The signal read is ALREADY FILTERED: only `source: 'pipeline'` detections, i.e.
+	* those that went through `enabledMacroClasses`, the
+	* `minConfidence<Macro>` and the full-frame guard. The camera's onboard AI
+	* (`source: 'onboard'`) goes through none of those gates and does NOT open
+	* windows — see `recorder/object-trigger.ts`.
 	*/
 	objectClasses: array(RecordingObjectTriggerClassSchema).min(1).refine(noDuplicates, { message: "objectClasses must not repeat a class" }).optional(),
 	/**
-	* I device LINKED il cui FRONTE ALTO apre una finestra. Assente = la sorgente
-	* non è ascoltata; un array vuoto è rifiutato per la stessa ragione di
+	* The LINKED devices whose RISING EDGE opens a window. Absent = the source
+	* is not listened to; an empty array is rejected for the same reason as
 	* `objectClasses`.
 	*
-	* Sono id di device SORGENTE, non camere: la banda li nomina, quindi il
-	* percorso caldo (`DeviceStateChanged`, a ritmo di bus su tutta la flotta)
-	* non fa RPC. L'OFFERTA da cui l'operatore li sceglie è un'altra domanda, e
-	* si risolve con `deviceManager.getLinkedDevices` + `getBindingsBatch` per
-	* device (D12) — mai un elenco globale di cap.
+	* These are SOURCE device ids, not cameras: the band names them, so the
+	* hot path (`DeviceStateChanged`, at bus rate across the whole fleet)
+	* does no RPC. The OFFER from which the operator picks them is another question, and
+	* is resolved with `deviceManager.getLinkedDevices` + `getBindingsBatch` per
+	* device (D12) — never a global list of caps.
 	*
-	* Cosa vuol dire "alto" dipende dal TIPO di device e non è deciso qui:
-	* `SOURCE_CAP_ACTIVE_FIELD` (`catalogs/sensor-active-state.ts`) è LA tabella,
-	* la stessa del campanello composto (D671). Ed è il FRONTE, non
-	* il livello: un contatto trovato già aperto al riavvio del runner non fa
-	* registrare.
+	* What "high" means depends on the device TYPE and is not decided here:
+	* `SOURCE_CAP_ACTIVE_FIELD` (`catalogs/sensor-active-state.ts`) is THE table,
+	* the same one as the composite doorbell (D671). And it is the EDGE, not
+	* the level: a contact found already open at runner restart does not
+	* record.
 	*/
 	sensorDeviceIds: array(number().int().positive()).min(1).max(16).refine(noDuplicates, { message: "sensorDeviceIds must not repeat a device" }).optional()
 });
@@ -10399,7 +10399,7 @@ var DecoderSessionConfigSchema = object({
 * - **VALUE** — at which level, for which scope, until when. That stays ONE
 *   thing: the logging settings document on the `system` cap. Two authorities
 *   over the values is the exact defect
-*   `docs/design/plans/2026-08-26-logging-per-componente.md` was written to
+*   `docs/design/plans/2026-08-26-per-component-logging.md` was written to
 *   remove; re-introducing it from the cure side would be grotesque.
 *
 * Nothing in this file reads a clock, an env var or a store. The registry is
@@ -15030,7 +15030,7 @@ var dataStoreProviderCapability = {
 			*
 			* ⚠ An earlier version of this comment blamed Zod stripping, and that
 			* was wrong — corrected 2026-08-26 after the hop map
-			* (`docs/design/2026-08-26-mappa-hop-argomenti.md`) traced the path.
+			* (`docs/design/2026-08-26-topic-hop-map.md`) traced the path.
 			* There is **no Zod parse at all** between the door and the engine: the
 			* dispatcher forwards the payload verbatim and UDS carries it whole. A
 			* field declared here reaches `SqliteSettingsBackend` either way.
@@ -15992,7 +15992,17 @@ var SiteZoneSchema = object({
 var ProviderStatusSchema = object({
 	connected: boolean(),
 	deviceCount: number(),
-	error: string().optional()
+	error: string().optional(),
+	/**
+	* `'orchestrator'`: this provider writes NO camera's `motion` runtime slice
+	* — the orchestrator is its only writer (D696). Set by `BaseDeviceProvider`,
+	* which every provider bundles, so only a provider BUILT from D696-amended
+	* code says it. ABSENT means an older provider that may still write it (raw
+	* VMD writes, a boot seed), and the orchestrator's provider gate keeps that
+	* provider's cameras unwritten (`camera-sensors/motion-slice-provider-gate.ts`)
+	* — the provider twin of the runner's `getLocalLoad().motionSliceWriter`.
+	*/
+	motionSliceWriter: literal("orchestrator").optional()
 });
 object({
 	externalId: string(),
@@ -17183,7 +17193,7 @@ var deviceManagerCapability = {
 		* sources could be switched off without switching off the rest (D556, then
 		* D555's re-key by source). The operator removed the whole idea the same
 		* day: *"tutti i providers funzionano sempre, non serve
-		* disattivarli/attivarli … loro vivono lì"* (D557 amended, third). A
+		* disattivarli/attivarli … loro vivono lì"* [all the providers always work, there is no need to deactivate/activate them … they live there] (D557 amended, third). A
 		* collection cap's providers are a DERIVED set — every addon that provides
 		* the cap for this device type, computed on every read and persisted
 		* nowhere — so there is nothing here to activate, and a verb that accepted
@@ -18021,7 +18031,7 @@ var embeddingEncoderCapability = {
 * per-device window, `KeyFrameCaptureLog`, `bumpCropMetric`. Every one of them
 * ends in a log line, and a log line is the thing the operator asked to stop
 * needing: *"possiamo armare questi errori intanto? Così al prossimo giro
-* ricontrolliamo tutti questi punti"*. Reading them meant grepping Loki and
+* ricontrolliamo tutti questi punti"* [can we instrument these errors in the meantime? That way next round we recheck all these points]. Reading them meant grepping Loki and
 * hand-correlating timestamps, which is how a 22% thumbnail gap and a 3-hour
 * media blackout were both diagnosed. The counters stay; this is where they can
 * be READ.
@@ -23124,6 +23134,29 @@ object({
 	firstAt: number(),
 	lastAt: number()
 });
+var NC_ALARM_TRIGGERED_MAX_SEC = 3600;
+var NcAlarmDelaySecSchema = number().int().min(0).max(600);
+var NcAlarmTriggeredSecSchema = number().int().min(0).max(NC_ALARM_TRIGGERED_MAX_SEC);
+var uniqueModes = (entries) => new Set(entries.map((e) => e.mode)).size === entries.length;
+var NcAlarmModeDelaysListSchema = array(object({
+	mode: AlarmArmModeSchema,
+	exitDelaySec: NcAlarmDelaySecSchema.optional(),
+	entryDelaySec: NcAlarmDelaySecSchema.optional(),
+	triggeredDurationSec: NcAlarmTriggeredSecSchema.optional()
+})).max(8).refine(uniqueModes, { message: "modeDelays: at most one entry per arm mode" });
+var NcAlarmModeDelaysEditListSchema = array(object({
+	mode: AlarmArmModeSchema,
+	exitDelaySec: NcAlarmDelaySecSchema.nullable().optional(),
+	entryDelaySec: NcAlarmDelaySecSchema.nullable().optional(),
+	triggeredDurationSec: NcAlarmTriggeredSecSchema.nullable().optional()
+})).max(8).refine(uniqueModes, { message: "modeDelays: at most one edit per arm mode" });
+/** One switch of the alarm table: put ONE device on, or take it off, ONE mode's list. */
+var NcAlarmNonBlockingEditSchema = object({
+	mode: AlarmArmModeSchema,
+	deviceId: number().int().positive(),
+	/** true = on the list (may be open, does not block); false = off the list (blocks). */
+	nonBlocking: boolean()
+});
 /**
 * The per-mode lists, at most one per mode. Two lists for one mode have no
 * meaning a reader could agree on (union? the last one?), so they are refused
@@ -23132,10 +23165,10 @@ object({
 var NcAlarmNonBlockingListSchema = array(object({
 	mode: AlarmArmModeSchema,
 	deviceIds: array(number().int()).max(200)
-})).max(8).refine((lists) => new Set(lists.map((l) => l.mode)).size === lists.length, { message: "nonBlocking: at most one list per arm mode" });
+})).max(8).refine(uniqueModes, { message: "nonBlocking: at most one list per arm mode" });
 /**
-* The three durations the panel's state machine runs on, who hears about its
-* transitions, and which openings each mode tolerates.
+* The three durations — global, and per mode since D697 — the panel's state
+* machine runs on, who hears about its transitions, and which openings each mode tolerates.
 *
 * They live on the NOTIFICATION-RULES cap, not on `alarm-panel`, on purpose:
 * `alarm-panel` is `deviceNative` and its other provider mirrors somebody
@@ -23145,15 +23178,15 @@ var NcAlarmNonBlockingListSchema = array(object({
 */
 var NcAlarmSettingsSchema = object({
 	/** Grace period between arming and the mode taking effect. 0 = immediate. */
-	exitDelaySec: number().int().min(0).max(600),
+	exitDelaySec: NcAlarmDelaySecSchema,
 	/** Grace period between a trigger and the alarm firing. 0 = immediate. */
-	entryDelaySec: number().int().min(0).max(600),
+	entryDelaySec: NcAlarmDelaySecSchema,
 	/**
 	* How long `triggered` lasts before the panel re-arms itself.
 	* **0 = until an operator disarms it** — the behaviour before this field
 	* existed, and therefore what an untouched install keeps doing.
 	*/
-	triggeredDurationSec: number().int().min(0).max(3600),
+	triggeredDurationSec: NcAlarmTriggeredSecSchema,
 	/**
 	* Deprecated by D630 — every transition is announced. Parsed, never read;
 	* remove after one release. Optional so an older admin's patch (which still
@@ -23176,17 +23209,30 @@ var NcAlarmSettingsSchema = object({
 	* per mode is meaningful. Defaulted to `[]` so a blob stored before D630
 	* parses as "every opening blocks" — the behaviour it was written under.
 	*/
-	nonBlocking: NcAlarmNonBlockingListSchema.default([])
+	nonBlocking: NcAlarmNonBlockingListSchema.default([]),
+	/**
+	* Per arm mode, the delays that mode OVERRIDES (D697). A mode with no entry, or an entry
+	* without a field, uses the global value above — so `[]`, the default, is exactly the
+	* behaviour of a blob stored before this field existed. Read through `resolveModeDelays`.
+	*/
+	modeDelays: NcAlarmModeDelaysListSchema.default([])
 });
 /**
 * Every field optional — a tab edits one control at a time.
 *
-* `nonBlocking` is re-declared WITHOUT its default: `.partial()` does not
-* remove an inner `.default()`, so a patch that never named the field would
-* parse to `nonBlocking: []` and wipe every mode's list on an unrelated edit
-* (the same trap {@link NcRulePatchSchema} documents).
+* `nonBlocking` and `modeDelays` are re-declared WITHOUT their defaults:
+* `.partial()` does not remove an inner `.default()`, so a patch that never
+* named the field would parse to `[]` and wipe every mode's list on an
+* unrelated edit (the same trap {@link NcRulePatchSchema} documents). Here
+* `modeDelays` means EDITS, not the stored overrides.
 */
-var NcAlarmSettingsPatchSchema = NcAlarmSettingsSchema.extend({ nonBlocking: NcAlarmNonBlockingListSchema }).partial();
+var NcAlarmSettingsPatchSchema = NcAlarmSettingsSchema.extend({
+	nonBlocking: NcAlarmNonBlockingListSchema,
+	/** Per-mode, per-field edits — NOT the whole list (see NcAlarmModeDelaysEditSchema). */
+	modeDelays: NcAlarmModeDelaysEditListSchema,
+	/** ONE membership change; the panel applies it to the list it holds at its turn. */
+	nonBlockingEdit: NcAlarmNonBlockingEditSchema
+}).partial().refine((p) => p.nonBlocking === void 0 || p.nonBlockingEdit === void 0, { message: "nonBlocking and nonBlockingEdit are exclusive — send the whole lists or one edit" });
 /**
 * What one arm mode actually arms, DERIVED from the enabled rules gated on it.
 * Never authored, never stored — see `alarm-mode-coverage.ts` for why a stored
@@ -23286,6 +23332,28 @@ var NcAlarmConfigSchema = object({
 	*/
 	live: NcAlarmLiveSchema.optional()
 });
+var NcAlarmSensorReadingSchema = _enum([
+	"open",
+	"closed",
+	"unknown",
+	"not-opening"
+]);
+/** One device's state as the alarm reads it — the classifier the arm check uses. */
+var NcAlarmSensorStateSchema = object({
+	deviceId: number().int().positive(),
+	reading: NcAlarmSensorReadingSchema,
+	/** The word as read (`open`, `closed`, `unlocked`, `stopped`, …); null when unknown / not an opening. */
+	state: string().nullable(),
+	/** Why `unknown`: the read failed, or the slice holds no word its cap defines (a placeholder included). */
+	unknownWhy: _enum(["read-failed", "unknown-word"]).nullable(),
+	/** The device manager's liveness as the centre mirrors it; null = not known. */
+	online: boolean().nullable()
+});
+var NcAlarmSensorsInputSchema = object({ deviceIds: array(number().int().positive()).max(500) });
+var NcAlarmSensorsSchema = object({
+	sensors: array(NcAlarmSensorStateSchema),
+	readAt: number().int().nonnegative()
+});
 /**
 * ONE rule's demand on ONE camera's clip ring.
 *
@@ -23527,8 +23595,9 @@ var notificationRulesCapability = {
 		*/
 		getAlarmConfig: method(object({}), NcAlarmConfigSchema, { auth: "admin" }),
 		/**
-		* Patch the settings (durations, recipients, per-mode non-blocking lists;
-		* `announceArm` is accepted and ignored — D630). Returns the WHOLE config,
+		* Patch the settings (durations — global and per mode —, recipients,
+		* per-mode non-blocking lists or one membership edit; `announceArm` is
+		* accepted and ignored — D630). Returns the WHOLE config,
 		* coverage and `live` included, so a
 		* client never has to guess what the server settled on — the panel clamps
 		* and normalises, and a form that re-rendered from its own input would
@@ -23537,7 +23606,15 @@ var notificationRulesCapability = {
 		setAlarmConfig: method(object({ patch: NcAlarmSettingsPatchSchema }), NcAlarmConfigSchema, {
 			kind: "mutation",
 			auth: "admin"
-		})
+		}),
+		/**
+		* The CURRENT state of each asked device as the alarm reads it (D697) — open, closed,
+		* unknown (why) or not an opening, plus liveness. Classified by the same table the arm
+		* check uses (`alarm-openings.ts`), so the editor and the arm can never disagree. The
+		* caller names the ids (the household openings it already holds); at most
+		* `NC_ALARM_SENSORS_MAX`.
+		*/
+		getAlarmSensors: method(NcAlarmSensorsInputSchema, NcAlarmSensorsSchema, { auth: "admin" })
 	}
 };
 /**
@@ -24707,14 +24784,14 @@ var TrackSchema = object({
 	* `derive-returned-null tile=standin`,
 	* `native-tile tile=native no-key-frame-at-close`, …) written at close and
 	* CLEARED by the late-keyFrame upgrade when a native tile lands after all.
-	* The operator-facing answer to "perché manca l'immagine?" on a track whose
+	* The operator-facing answer to "perché manca l'immagine?" [why is the image missing?] on a track whose
 	* tile is a face/plate stand-in, a raster crop, or an icon.
 	*
 	* **`no-key-frame-at-close` (D400).** The line used to be written ONLY when
 	* the TILE ranked below native, so a track whose thumbnail landed natively
 	* while its key frame missed carried no reason at all — three of the four
 	* `MISSING_KEYFRAME` tracks in the 2026-09-07 operator audit were exactly
-	* that shape, and their "niente ultimo" had no cause anywhere on the row.
+	* that shape, and their "niente ultimo" [no last frame] had no cause anywhere on the row.
 	* The key frame is the head of a cascade (`keyFrame ⇒ keyFrameSmall ⇒ the
 	* lastFrame copy source`), so its absence is now on this line whatever the
 	* tile ended up being.
@@ -24801,7 +24878,7 @@ var MotionEventSchema = object({
 	/**
 	* Ms offsets from `timestamp` (the episode's own first rising edge, so the
 	* first entry is always `0`) of every genuine off→on transition the
-	* episode saw — "ogni evento on si deve salvare" (D475). NOT one entry per
+	* episode saw — "ogni evento on si deve salvare" [every ON event must be saved] (D475). NOT one entry per
 	* push: a firmware source that keepalives at ~1 Hz for the whole burst
 	* (Reolink, Hikvision) produces exactly one edge; a source that reports an
 	* explicit `false` mid-episode and then resumes before the quiet window
@@ -32009,7 +32086,7 @@ var ClipPlaybackSchema = object({
 * **One authorised yes is one wake.** `next-natural` — take the clip the next
 * time the camera is awake for its own reasons — is deliberately not a member:
 * it was proposed, it is free on the battery, and the operator declined it on
-* 2026-09-20 (*"Quando un export viene richiesto si sveglia la camera."*,
+* 2026-09-20 (*"Quando un export viene richiesto si sveglia la camera."* [When an export is requested the camera wakes up],
 * D558 "Considered and not taken").
 */
 var ClipWakeSchema = _enum(["authorised"]);
@@ -32254,7 +32331,7 @@ var videoclipsCapability = {
 	* **It is a SECTION of the Recording tab, at the end of it — not a tab of
 	* its own.** It shipped as a `clips` top-tab and the operator rejected the
 	* placement: *"utilizzerei la stessa tab recordings, lì abbiamo già tutto il
-	* necessario, una nuova sezione alla fine per le clips"*. The Recording tab
+	* necessario, una nuova sezione alla fine per le clips"* [I would use the same recordings tab, there we already have everything necessary, a new section at the end for the clips]. The Recording tab
 	* already holds the recorder's panel, the schedule bands and the unified
 	* retention policy; footage the camera itself holds is the same question,
 	* asked of a different store. `order: 100` puts it after all of them with
@@ -32315,7 +32392,7 @@ var videoclipsCapability = {
 			* It replaced `sources?: string[]`, a VIEW filter over source ids that
 			* assumed the answer was a fan-out over everything a camera has. The
 			* operator settled otherwise on 2026-09-20 — *"l'utilizzatore è uno
-			* solo"* — so the list is asked of one provider at a time and there is
+			* solo"* [there is only one user] — so the list is asked of one provider at a time and there is
 			* nothing to filter out of it.
 			*/
 			provider: string().min(1)
@@ -41456,7 +41533,7 @@ var ReadGopBytesResultSchema = object({
 /**
 * A time WINDOW of one finalized segment, cut by byte range — the multi-GOP
 * twin of {@link ReadGopBytesResultSchema}'s single instant. Built for the
-* replay clip's `recording` source (`docs/design/plans/2026-08-26-replay-clip-su-pipeline.md`):
+* replay clip's `recording` source (`docs/design/plans/2026-08-26-clip-replay-on-pipeline.md`):
 * a replay needs several seconds of native pixels, not one frame.
 *
 * `ok.data` is standalone-demuxable, same as a GOP read. `ok.reachesRequestedEnd`
@@ -44064,7 +44141,7 @@ var systemCapability = {
 		*
 		* This is the surface the operator asked for on 2026-08-28 (*"possiamo
 		* armare questi errori intanto? Così al prossimo giro ricontrolliamo tutti
-		* questi punti"*). Before it, four live failure modes could only be counted
+		* questi punti"* [can we instrument these errors in the meantime? That way next round we recheck all these points]). Before it, four live failure modes could only be counted
 		* by grepping Loki and hand-correlating timestamps, which is exactly how a
 		* 22% thumbnail gap and a 3-hour media blackout were diagnosed — twice.
 		*
@@ -50430,6 +50507,12 @@ Object.freeze({
 		addonId: null,
 		access: "view"
 	},
+	"notificationRules.getAlarmSensors": {
+		capName: "notification-rules",
+		capScope: "system",
+		addonId: null,
+		access: "view"
+	},
 	"notificationRules.getClipRetentionAsks": {
 		capName: "notification-rules",
 		capScope: "system",
@@ -54913,6 +54996,11 @@ Object.freeze({
 		form: "single",
 		optional: false
 	}],
+	"notificationRules.getAlarmSensors": [{
+		name: "deviceIds",
+		form: "array",
+		optional: false
+	}],
 	"notificationRules.setDeviceMuted": [{
 		name: "deviceId",
 		form: "single",
@@ -56790,7 +56878,7 @@ var PreviewTextField = string().max(200);
 * Whether the notification's preview is a STILL or a short animation.
 *
 * The operator's ask, verbatim: *"inviato come gif o video (come per le altre
-* rule)"* — the other rules already offer an animated preview, and a ten-hour
+* rule)"* [sent as a gif or video (as for the other rules)] — the other rules already offer an animated preview, and a ten-hour
 * night reads better as three seconds of motion than as one frame of it. Both
 * modes get the SAME treatment (blurred frame, large centred title); `'gif'`
 * simply applies it to a dozen frames sampled across the render and assembles