@camstack/types 1.2.286 → 1.2.288

package/dist/capabilities/device-manager.cap.d.ts

@@ -1473,7 +1473,7 @@ export declare const 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

package/dist/capabilities/failure-contribution.cap.d.ts

@@ -29,7 +29,7 @@
  * 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.

package/dist/capabilities/motion.cap.d.ts

@@ -15,7 +15,7 @@ import { type InferProvider } from './capability-definition.js';
  */
 /**
  * How long after a camera's last rising edge `pipeline-analytics` closes the
- * motion EPISODE row it kept open for it (D475) — "il delay della cap", in
+ * motion EPISODE row it kept open for it (D475) — "il delay della cap" [the cap's delay], in
  * the operator's words. One authority for the whole system: the writer of a
  * `Camera` device's slice (the orchestrator, D696) writes this SAME constant
  * in `autoClearAfterMs` while `detected: true` (never a camera's own clock —

package/dist/capabilities/recording-archive.cap.d.ts

@@ -342,7 +342,7 @@ export type ReadGopBytesResult = z.infer<typeof ReadGopBytesResultSchema>;
 /**
  * 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`

package/dist/capabilities/system.cap.d.ts

@@ -835,7 +835,7 @@ export declare const 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.
          *

package/dist/capabilities/videoclips.cap.d.ts

@@ -25,7 +25,7 @@ import { type InferProvider } from './capability-definition.js';
  *
  * `listClips` is asked of ONE provider at a time, and NAMING it is REQUIRED
  * ({@link videoclipsCapability.methods.listClips} `provider`, D554 amended). It is not
- * a union over everything a camera has: *"l'utilizzatore è uno solo"*. There
+ * a union over everything a camera has: *"l'utilizzatore è uno solo"* [there is only one user]. There
  * is no default, because a collection cap's binding set is DERIVED and PLURAL
  * (D554 amended, `getBindings` step 0) — "the bound one" does not exist to
  * resolve to, and the one thing that could take its place is a second
@@ -230,7 +230,7 @@ export type ClipPlayback = z.infer<typeof ClipPlaybackSchema>;
  * **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").
  */
 export declare const ClipWakeSchema: z.ZodEnum<{
@@ -570,7 +570,7 @@ export declare const 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

package/dist/catalogs/sensor-active-state.d.ts

@@ -1,18 +1,18 @@
 /**
- * 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
@@ -64,8 +64,8 @@ export declare function sliceActiveValue(capName: string, slice: Readonly<Record
  *  it is absent, non-numeric or the zero "never observed" sentinel. */
 export declare function sliceChangedAt(capName: string, slice: Readonly<Record<string, unknown>>): number | null;
 /**
- * Perché una slice non ha portato un fronte alto. UN enum, così "perché non è
- * scattato niente" ha una risposta sola, chiunque lo chieda.
+ * Why a slice did not carry a rising edge. ONE enum, so "why did nothing
+ * fire" has a single answer, whoever asks.
  */
 export type SensorEdgeIgnoreReason = 
 /** Not a recognised binary/switch source cap. */
@@ -87,19 +87,19 @@ export type SensorEdgeIgnoreReason =
 export interface SensorEdgeInput {
     readonly capName: string;
     readonly slice: Readonly<Record<string, unknown>>;
-    /** Ultimo booleano osservato per questa `(device, cap)`; `undefined` = mai vista. */
+    /** Last boolean observed for this `(device, cap)`; `undefined` = never seen. */
     readonly prior: boolean | undefined;
-    /** Quando l'OSSERVATORE ha iniziato a guardare — il pavimento per una prima
-     *  osservazione già attiva. Ogni osservatore ha il suo. */
+    /** When the OBSERVER started watching — the floor for a first
+     *  already-active observation. Each observer has its own. */
     readonly startedAtMs: number;
     readonly nowMs: number;
     readonly firstSightingFreshnessMs: number;
 }
 /**
- * `value` è restituito su ogni cammino in cui la slice PORTAVA un booleano,
- * anche quando non c'è fronte: il chiamante aggiorna la sua memoria con quello
- * e non rilegge la slice. Su `unknown-cap` / `non-boolean-value` è `null` e la
- * memoria non va toccata.
+ * `value` is returned on every path where the slice CARRIED a boolean,
+ * even when there is no edge: the caller updates its memory with that
+ * and does not re-read the slice. On `unknown-cap` / `non-boolean-value` it is `null` and the
+ * memory must not be touched.
  */
 export type SensorEdgeVerdict = {
     readonly edge: 'rising';
@@ -137,16 +137,16 @@ export type SensorLevelEdgeVerdict = {
  */
 export declare function evaluateSensorLevelEdge(input: SensorLevelEdgeInput): SensorLevelEdgeVerdict;
 /**
- * IL fronte. Puro: nessun orologio proprio, nessuna memoria — il chiamante
- * porta `prior`, `nowMs` e il proprio `startedAtMs`.
+ * THE edge. Pure: no clock of its own, no memory — the caller
+ * brings `prior`, `nowMs` and its own `startedAtMs`.
  *
- * Il caso della PRIMA slice già attiva è trattato esplicitamente e vale come
- * fronte solo se il timestamp UPSTREAM della transizione è posteriore a
- * `startedAtMs` **e** entro `firstSightingFreshnessMs`. Entrambe le metà
- * servono: la sola freschezza scatterebbe su un'idratazione al boot di uno
- * stato flippato pochi secondi prima del riavvio, e il solo "dopo che abbiamo
- * iniziato" scatterebbe, su un processo di lunga vita, per una sorgente
- * adottata oggi il cui stato è cambiato ieri. Il caso ambiguo ERRA VERSO IL
- * SILENZIO e lo dichiara (`baseline-seeded-stale-active`).
+ * The case of the FIRST slice already active is treated explicitly and counts as an
+ * edge only if the UPSTREAM timestamp of the transition is later than
+ * `startedAtMs` **and** within `firstSightingFreshnessMs`. Both halves
+ * are needed: freshness alone would fire on a boot-time hydration of a
+ * state flipped a few seconds before the restart, and "after we started"
+ * alone would fire, on a long-lived process, for a source
+ * adopted today whose state changed yesterday. The ambiguous case ERRS TOWARD
+ * SILENCE and declares it (`baseline-seeded-stale-active`).
  */
 export declare function evaluateSensorEdge(input: SensorEdgeInput): SensorEdgeVerdict;

package/dist/{composition-43aqsZQj.mjs → composition-D7ULvLdD.mjs}

@@ -901,20 +901,20 @@ function chooseFfmpegBinary(input) {
 //#endregion
 //#region src/catalogs/sensor-active-state.ts
 /**
-* 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
@@ -1030,17 +1030,17 @@ function evaluateSensorLevelEdge(input) {
 	};
 }
 /**
-* IL fronte. Puro: nessun orologio proprio, nessuna memoria — il chiamante
-* porta `prior`, `nowMs` e il proprio `startedAtMs`.
+* THE edge. Pure: no clock of its own, no memory — the caller
+* brings `prior`, `nowMs` and its own `startedAtMs`.
 *
-* Il caso della PRIMA slice già attiva è trattato esplicitamente e vale come
-* fronte solo se il timestamp UPSTREAM della transizione è posteriore a
-* `startedAtMs` **e** entro `firstSightingFreshnessMs`. Entrambe le metà
-* servono: la sola freschezza scatterebbe su un'idratazione al boot di uno
-* stato flippato pochi secondi prima del riavvio, e il solo "dopo che abbiamo
-* iniziato" scatterebbe, su un processo di lunga vita, per una sorgente
-* adottata oggi il cui stato è cambiato ieri. Il caso ambiguo ERRA VERSO IL
-* SILENZIO e lo dichiara (`baseline-seeded-stale-active`).
+* The case of the FIRST slice already active is treated explicitly and counts as an
+* edge only if the UPSTREAM timestamp of the transition is later than
+* `startedAtMs` **and** within `firstSightingFreshnessMs`. Both halves
+* are needed: freshness alone would fire on a boot-time hydration of a
+* state flipped a few seconds before the restart, and "after we started"
+* alone would fire, on a long-lived process, for a source
+* adopted today whose state changed yesterday. The ambiguous case ERRS TOWARD
+* SILENCE and declares it (`baseline-seeded-stale-active`).
 */
 function evaluateSensorEdge(input) {
 	const value = sliceActiveValue(input.capName, input.slice);

package/dist/{composition-w3gBWMer.js → composition-DexM_etk.js}

@@ -901,20 +901,20 @@ function chooseFfmpegBinary(input) {
 //#endregion
 //#region src/catalogs/sensor-active-state.ts
 /**
-* 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
@@ -1030,17 +1030,17 @@ function evaluateSensorLevelEdge(input) {
 	};
 }
 /**
-* IL fronte. Puro: nessun orologio proprio, nessuna memoria — il chiamante
-* porta `prior`, `nowMs` e il proprio `startedAtMs`.
+* THE edge. Pure: no clock of its own, no memory — the caller
+* brings `prior`, `nowMs` and its own `startedAtMs`.
 *
-* Il caso della PRIMA slice già attiva è trattato esplicitamente e vale come
-* fronte solo se il timestamp UPSTREAM della transizione è posteriore a
-* `startedAtMs` **e** entro `firstSightingFreshnessMs`. Entrambe le metà
-* servono: la sola freschezza scatterebbe su un'idratazione al boot di uno
-* stato flippato pochi secondi prima del riavvio, e il solo "dopo che abbiamo
-* iniziato" scatterebbe, su un processo di lunga vita, per una sorgente
-* adottata oggi il cui stato è cambiato ieri. Il caso ambiguo ERRA VERSO IL
-* SILENZIO e lo dichiara (`baseline-seeded-stale-active`).
+* The case of the FIRST slice already active is treated explicitly and counts as an
+* edge only if the UPSTREAM timestamp of the transition is later than
+* `startedAtMs` **and** within `firstSightingFreshnessMs`. Both halves
+* are needed: freshness alone would fire on a boot-time hydration of a
+* state flipped a few seconds before the restart, and "after we started"
+* alone would fire, on a long-lived process, for a source
+* adopted today whose state changed yesterday. The ambiguous case ERRS TOWARD
+* SILENCE and declares it (`baseline-seeded-stale-active`).
 */
 function evaluateSensorEdge(input) {
 	const value = sliceActiveValue(input.capName, input.slice);

package/dist/generated/method-device-selectors.d.ts

@@ -6,8 +6,8 @@
  * system-scope cap that takes a deviceId was previously never device-filtered
  * — see the generator header).
  *
- * Coverage: 409 methods carry a device reference, of which
- * 146 are on SYSTEM-scope caps.
+ * Coverage: 509 methods carry a device reference, of which
+ * 160 are on SYSTEM-scope caps.
  *
  * Top-level fields, number arrays, and one-level arrays of objects carrying
  * a numeric device field (targets[].deviceId) are all mapped; the matcher