@camstack/addon-smtp-nodemailer 1.2.74 → 1.2.76

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
@@ -7870,17 +7870,29 @@ var HHMM = /^([01]\d|2[0-3]):[0-5]\d$/;
7870
7870
  /**
7871
7871
  * DERIVED per-camera storage summary — the single field cheap consumers read
7872
7872
  * (the viewer's status dot, the camera list) instead of walking `bands`:
7873
- * - `off` — no band covers the camera (or it is disabled).
7874
- * - `events` — every band records around triggers only.
7875
- * - `continuous` — at least one band records continuously.
7876
- *
7877
- * NEVER authored: the recorder stamps it from the authoritative `bands` on
7878
- * every save (`activeModeForConfig`). Writing it has no effect.
7873
+ * - `off` — no band covers the camera (or it is disabled).
7874
+ * - `events` — every band records around triggers only.
7875
+ * - `continuous` — at least one band records continuously.
7876
+ * - `on-device-decision`— the DEVICE decides: recording runs for as long as the
7877
+ * camera raises its own `recording-signal` level (a robot that cleans). There
7878
+ * is no schedule to author, because there is no hour to program — see
7879
+ * {@link RecordingConfigSchema}`.deviceDecision`.
7880
+ *
7881
+ * NEVER authored: the recorder stamps it from the authoritative intent
7882
+ * (`bands` + `deviceDecision`) on every save (`activeModeForConfig`). Writing it
7883
+ * has no effect.
7884
+ *
7885
+ * `on-device-decision` is named for WHO decides, not for how the recording is
7886
+ * requested. `on-demand` was rejected: in this repo's vocabulary a "demand" is
7887
+ * something the operator makes (the live gate is the recorder's own "demand
7888
+ * window"), and a knob whose name suggests the operator starts it while the
7889
+ * device actually does is the D62 shape — a control nobody can predict.
7879
7890
  */
7880
7891
  var RecordingStorageModeSchema = _enum([
7881
7892
  "off",
7882
7893
  "events",
7883
- "continuous"
7894
+ "continuous",
7895
+ "on-device-decision"
7884
7896
  ]);
7885
7897
  /**
7886
7898
  * Le macro classi che possono aprire una finestra di registrazione — le stesse
@@ -7930,22 +7942,7 @@ var RecordingTriggersSchema = object({
7930
7942
  * il livello: un contatto trovato già aperto al riavvio del runner non fa
7931
7943
  * registrare.
7932
7944
  */
7933
- sensorDeviceIds: array(number().int().positive()).min(1).max(16).refine(noDuplicates, { message: "sensorDeviceIds must not repeat a device" }).optional(),
7934
- /**
7935
- * La camera registra per tutta la durata del SEGNALE che lei stessa
7936
- * pubblica — la cap `recording-signal` (`active: true` mentre il device è in
7937
- * funzione: un robot che pulisce). È un LIVELLO, non un fronte: la finestra
7938
- * resta aperta finché il segnale è alto e si chiude `postBufferSec` dopo la
7939
- * caduta, così una pulizia di quaranta minuti è UNA clip.
7940
- *
7941
- * Non nomina un device: il segnale è della camera stessa, tenuto fresco dal
7942
- * suo provider (D224); il recorder lo ascolta su `DeviceStateChanged` e lo
7943
- * riconcilia leggendo la slice via RPC, con un tetto oltre il quale un
7944
- * segnale mai abbassato (un evento perso) non può tenere aperta una
7945
- * registrazione (D11). Vedi `recorder/addon/band-decision.ts`
7946
- * (`holdTrigger` / `releaseTrigger`).
7947
- */
7948
- deviceSignal: boolean().optional()
7945
+ sensorDeviceIds: array(number().int().positive()).min(1).max(16).refine(noDuplicates, { message: "sensorDeviceIds must not repeat a device" }).optional()
7949
7946
  });
7950
7947
  /**
7951
7948
  * Mode of a single recording band — the recorder per-band vocabulary.
@@ -7975,13 +7972,28 @@ var RecordingBandSchema = object({
7975
7972
  end: string().regex(HHMM),
7976
7973
  mode: RecordingBandModeSchema,
7977
7974
  triggers: RecordingBandTriggersSchema.optional(),
7975
+ /**
7976
+ * RETIRED (D381). A band no longer carries a pre-buffer of its own.
7977
+ *
7978
+ * It was the retroactive KEEP bound — which already-written segments survive
7979
+ * a trigger — and it had to be at least as wide as the widest pre-roll the
7980
+ * broker could serve, or the gate would delete the seconds the ring had just
7981
+ * handed the writer. That "at least as wide as" is the tell: it was a second
7982
+ * expression of the broker's retention, in different units, in a different
7983
+ * addon, with an invariant the operator had to maintain by hand. The keep
7984
+ * bound is now derived from the one prebuffer ceiling and there is nothing
7985
+ * left to configure here.
7986
+ *
7987
+ * The key survives in the SHAPE so a config written before that record still
7988
+ * parses and can be migrated deliberately — `RecordingBandSchema` is not
7989
+ * strict, so simply deleting it would strip an operator's value in silence on
7990
+ * the next save (the failure D380 came one commit from shipping). Nothing
7991
+ * reads it: {@link stripRetiredBandPreBufferSec} removes it on load.
7992
+ */
7978
7993
  preBufferSec: number().min(0).optional(),
7979
7994
  postBufferSec: number().min(0).optional()
7980
7995
  });
7981
- ({
7982
- preBufferSec: 15,
7983
- postBufferSec: 30
7984
- }).postBufferSec * 1e3;
7996
+ ({ postBufferSec: 30 }).postBufferSec * 1e3;
7985
7997
  /**
7986
7998
  * Per-device retention overrides. Every field is optional; an unset or `0`
7987
7999
  * value inherits the node-wide recorder default. Only footage-lifetime limits
@@ -8029,8 +8041,29 @@ var RecordingConfigSchema = object({
8029
8041
  * "off" is the absence of a covering band, never a band value.
8030
8042
  */
8031
8043
  bands: array(RecordingBandSchema).default([]),
8044
+ /**
8045
+ * THE device-decided intent: record for as long as the camera itself raises
8046
+ * `recording-signal` (`active: true` while the device is in function — a
8047
+ * robot that cleans). AUTHORED, unlike `mode`, and the only authored
8048
+ * recording intent that is not a band.
8049
+ *
8050
+ * It carries NO schedule on purpose. A band is an HOUR, and this feature has
8051
+ * no hour to program: the device decides. What it costs the operator is one
8052
+ * flag — "this camera can record on its own" — and what it buys is the same
8053
+ * hold/release the recorder already implements (D371, `holdTrigger` /
8054
+ * `releaseTrigger`): the window opens on the rise, stays open for the whole
8055
+ * job however long it is, and closes one pad after the fall.
8056
+ *
8057
+ * EXCLUSIVE with `bands` (below): two authorities deciding when the same
8058
+ * camera records is the D62 failure. `off` remains `enabled: false`, so an
8059
+ * operator switching this camera off is REPORTED off, never as broken.
8060
+ */
8061
+ deviceDecision: boolean().optional(),
8032
8062
  retention: RecordingRetentionSchema.optional()
8033
- }).strict();
8063
+ }).strict().refine((config) => config.deviceDecision !== true || config.bands.length === 0, {
8064
+ message: "deviceDecision is a whole-config mode and carries no schedule: it cannot be combined with bands",
8065
+ path: ["bands"]
8066
+ });
8034
8067
  /**
8035
8068
  * Entity-relocation job state (storage entity-routing spec, Phase 4).
8036
8069
  *
@@ -20678,11 +20711,7 @@ var CameraAudioStatusSchema = object({
20678
20711
  });
20679
20712
  /** Recording block — null when no recording cap is active for this device. */
20680
20713
  var CameraRecordingStatusSchema = object({
20681
- mode: _enum([
20682
- "off",
20683
- "continuous",
20684
- "events"
20685
- ]),
20714
+ mode: RecordingStorageModeSchema,
20686
20715
  active: boolean(),
20687
20716
  storageBytes: number()
20688
20717
  });
@@ -27101,11 +27130,10 @@ DeviceType.Camera, DeviceType.Sensor, DeviceType.Switch, method(object({ deviceI
27101
27130
  var RecordingStatusSchema = object({
27102
27131
  deviceId: number(),
27103
27132
  enabled: boolean(),
27104
- activeMode: _enum([
27105
- "off",
27106
- "continuous",
27107
- "events"
27108
- ]),
27133
+ /** THE derived storage mode, from the one definition
27134
+ * (`deriveRecordingMode`) — never a second enum. A duplicated list is how
27135
+ * `on-device-decision` could have reached the recorder and not the status. */
27136
+ activeMode: RecordingStorageModeSchema,
27109
27137
  nodeId: string(),
27110
27138
  storageBytes: number()
27111
27139
  });
@@ -7868,17 +7868,29 @@ var HHMM = /^([01]\d|2[0-3]):[0-5]\d$/;
7868
7868
  /**
7869
7869
  * DERIVED per-camera storage summary — the single field cheap consumers read
7870
7870
  * (the viewer's status dot, the camera list) instead of walking `bands`:
7871
- * - `off` — no band covers the camera (or it is disabled).
7872
- * - `events` — every band records around triggers only.
7873
- * - `continuous` — at least one band records continuously.
7874
- *
7875
- * NEVER authored: the recorder stamps it from the authoritative `bands` on
7876
- * every save (`activeModeForConfig`). Writing it has no effect.
7871
+ * - `off` — no band covers the camera (or it is disabled).
7872
+ * - `events` — every band records around triggers only.
7873
+ * - `continuous` — at least one band records continuously.
7874
+ * - `on-device-decision`— the DEVICE decides: recording runs for as long as the
7875
+ * camera raises its own `recording-signal` level (a robot that cleans). There
7876
+ * is no schedule to author, because there is no hour to program — see
7877
+ * {@link RecordingConfigSchema}`.deviceDecision`.
7878
+ *
7879
+ * NEVER authored: the recorder stamps it from the authoritative intent
7880
+ * (`bands` + `deviceDecision`) on every save (`activeModeForConfig`). Writing it
7881
+ * has no effect.
7882
+ *
7883
+ * `on-device-decision` is named for WHO decides, not for how the recording is
7884
+ * requested. `on-demand` was rejected: in this repo's vocabulary a "demand" is
7885
+ * something the operator makes (the live gate is the recorder's own "demand
7886
+ * window"), and a knob whose name suggests the operator starts it while the
7887
+ * device actually does is the D62 shape — a control nobody can predict.
7877
7888
  */
7878
7889
  var RecordingStorageModeSchema = _enum([
7879
7890
  "off",
7880
7891
  "events",
7881
- "continuous"
7892
+ "continuous",
7893
+ "on-device-decision"
7882
7894
  ]);
7883
7895
  /**
7884
7896
  * Le macro classi che possono aprire una finestra di registrazione — le stesse
@@ -7928,22 +7940,7 @@ var RecordingTriggersSchema = object({
7928
7940
  * il livello: un contatto trovato già aperto al riavvio del runner non fa
7929
7941
  * registrare.
7930
7942
  */
7931
- sensorDeviceIds: array(number().int().positive()).min(1).max(16).refine(noDuplicates, { message: "sensorDeviceIds must not repeat a device" }).optional(),
7932
- /**
7933
- * La camera registra per tutta la durata del SEGNALE che lei stessa
7934
- * pubblica — la cap `recording-signal` (`active: true` mentre il device è in
7935
- * funzione: un robot che pulisce). È un LIVELLO, non un fronte: la finestra
7936
- * resta aperta finché il segnale è alto e si chiude `postBufferSec` dopo la
7937
- * caduta, così una pulizia di quaranta minuti è UNA clip.
7938
- *
7939
- * Non nomina un device: il segnale è della camera stessa, tenuto fresco dal
7940
- * suo provider (D224); il recorder lo ascolta su `DeviceStateChanged` e lo
7941
- * riconcilia leggendo la slice via RPC, con un tetto oltre il quale un
7942
- * segnale mai abbassato (un evento perso) non può tenere aperta una
7943
- * registrazione (D11). Vedi `recorder/addon/band-decision.ts`
7944
- * (`holdTrigger` / `releaseTrigger`).
7945
- */
7946
- deviceSignal: boolean().optional()
7943
+ sensorDeviceIds: array(number().int().positive()).min(1).max(16).refine(noDuplicates, { message: "sensorDeviceIds must not repeat a device" }).optional()
7947
7944
  });
7948
7945
  /**
7949
7946
  * Mode of a single recording band — the recorder per-band vocabulary.
@@ -7973,13 +7970,28 @@ var RecordingBandSchema = object({
7973
7970
  end: string().regex(HHMM),
7974
7971
  mode: RecordingBandModeSchema,
7975
7972
  triggers: RecordingBandTriggersSchema.optional(),
7973
+ /**
7974
+ * RETIRED (D381). A band no longer carries a pre-buffer of its own.
7975
+ *
7976
+ * It was the retroactive KEEP bound — which already-written segments survive
7977
+ * a trigger — and it had to be at least as wide as the widest pre-roll the
7978
+ * broker could serve, or the gate would delete the seconds the ring had just
7979
+ * handed the writer. That "at least as wide as" is the tell: it was a second
7980
+ * expression of the broker's retention, in different units, in a different
7981
+ * addon, with an invariant the operator had to maintain by hand. The keep
7982
+ * bound is now derived from the one prebuffer ceiling and there is nothing
7983
+ * left to configure here.
7984
+ *
7985
+ * The key survives in the SHAPE so a config written before that record still
7986
+ * parses and can be migrated deliberately — `RecordingBandSchema` is not
7987
+ * strict, so simply deleting it would strip an operator's value in silence on
7988
+ * the next save (the failure D380 came one commit from shipping). Nothing
7989
+ * reads it: {@link stripRetiredBandPreBufferSec} removes it on load.
7990
+ */
7976
7991
  preBufferSec: number().min(0).optional(),
7977
7992
  postBufferSec: number().min(0).optional()
7978
7993
  });
7979
- ({
7980
- preBufferSec: 15,
7981
- postBufferSec: 30
7982
- }).postBufferSec * 1e3;
7994
+ ({ postBufferSec: 30 }).postBufferSec * 1e3;
7983
7995
  /**
7984
7996
  * Per-device retention overrides. Every field is optional; an unset or `0`
7985
7997
  * value inherits the node-wide recorder default. Only footage-lifetime limits
@@ -8027,8 +8039,29 @@ var RecordingConfigSchema = object({
8027
8039
  * "off" is the absence of a covering band, never a band value.
8028
8040
  */
8029
8041
  bands: array(RecordingBandSchema).default([]),
8042
+ /**
8043
+ * THE device-decided intent: record for as long as the camera itself raises
8044
+ * `recording-signal` (`active: true` while the device is in function — a
8045
+ * robot that cleans). AUTHORED, unlike `mode`, and the only authored
8046
+ * recording intent that is not a band.
8047
+ *
8048
+ * It carries NO schedule on purpose. A band is an HOUR, and this feature has
8049
+ * no hour to program: the device decides. What it costs the operator is one
8050
+ * flag — "this camera can record on its own" — and what it buys is the same
8051
+ * hold/release the recorder already implements (D371, `holdTrigger` /
8052
+ * `releaseTrigger`): the window opens on the rise, stays open for the whole
8053
+ * job however long it is, and closes one pad after the fall.
8054
+ *
8055
+ * EXCLUSIVE with `bands` (below): two authorities deciding when the same
8056
+ * camera records is the D62 failure. `off` remains `enabled: false`, so an
8057
+ * operator switching this camera off is REPORTED off, never as broken.
8058
+ */
8059
+ deviceDecision: boolean().optional(),
8030
8060
  retention: RecordingRetentionSchema.optional()
8031
- }).strict();
8061
+ }).strict().refine((config) => config.deviceDecision !== true || config.bands.length === 0, {
8062
+ message: "deviceDecision is a whole-config mode and carries no schedule: it cannot be combined with bands",
8063
+ path: ["bands"]
8064
+ });
8032
8065
  /**
8033
8066
  * Entity-relocation job state (storage entity-routing spec, Phase 4).
8034
8067
  *
@@ -20676,11 +20709,7 @@ var CameraAudioStatusSchema = object({
20676
20709
  });
20677
20710
  /** Recording block — null when no recording cap is active for this device. */
20678
20711
  var CameraRecordingStatusSchema = object({
20679
- mode: _enum([
20680
- "off",
20681
- "continuous",
20682
- "events"
20683
- ]),
20712
+ mode: RecordingStorageModeSchema,
20684
20713
  active: boolean(),
20685
20714
  storageBytes: number()
20686
20715
  });
@@ -27099,11 +27128,10 @@ DeviceType.Camera, DeviceType.Sensor, DeviceType.Switch, method(object({ deviceI
27099
27128
  var RecordingStatusSchema = object({
27100
27129
  deviceId: number(),
27101
27130
  enabled: boolean(),
27102
- activeMode: _enum([
27103
- "off",
27104
- "continuous",
27105
- "events"
27106
- ]),
27131
+ /** THE derived storage mode, from the one definition
27132
+ * (`deriveRecordingMode`) — never a second enum. A duplicated list is how
27133
+ * `on-device-decision` could have reached the recorder and not the status. */
27134
+ activeMode: RecordingStorageModeSchema,
27107
27135
  nodeId: string(),
27108
27136
  storageBytes: number()
27109
27137
  });
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@camstack/addon-smtp-nodemailer",
3
- "version": "1.2.74",
3
+ "version": "1.2.76",
4
4
  "description": "SMTP email provider addon for CamStack — wraps `nodemailer` and registers a `smtp-provider` cap collection entry. Used by magic-link login + notifier addons.",
5
5
  "keywords": [
6
6
  "camstack",