@camstack/addon-smtp-nodemailer 1.2.91 → 1.2.93

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.
@@ -16163,6 +16163,7 @@ var NcSystemEventKindSchema = _enum([
16163
16163
  "addon-crash-loop",
16164
16164
  "addon-update-available",
16165
16165
  "server-update-available",
16166
+ "wrapper-update-available",
16166
16167
  "alarm-triggered",
16167
16168
  "alarm-armed",
16168
16169
  "alarm-disarmed",
@@ -19568,7 +19569,17 @@ var EventDensityBucketSchema = object({
19568
19569
  bucketStart: number(),
19569
19570
  motion: number().int(),
19570
19571
  object: number().int(),
19571
- audio: number().int()
19572
+ audio: number().int(),
19573
+ /**
19574
+ * Energy-weighted mean dBFS of the audio events in this bucket — the LEVEL,
19575
+ * as opposed to `audio`, which is their COUNT (D431).
19576
+ *
19577
+ * ABSENT when the bucket holds no audio event. Absence means "nothing was
19578
+ * measured", which is not the same claim as silence, and a lane that cannot
19579
+ * tell them apart paints a quiet hour at full scale — which is exactly what
19580
+ * the count-on-a-level-meter did.
19581
+ */
19582
+ audioDbfs: number().optional()
19572
19583
  });
19573
19584
  /**
19574
19585
  * One camera's row in a `getEventDensityBatch` answer.
@@ -21669,6 +21680,53 @@ var ImageContractSchema = object({
21669
21680
  /** One operator-grade sentence: this node runs image X; the contract says Y. */
21670
21681
  message: string()
21671
21682
  });
21683
+ /**
21684
+ * The shell verdict (see {@link WrapperKindSchema}) with the proofs that
21685
+ * produced it.
21686
+ *
21687
+ * There is deliberately NO `canSelfUpdate` and no apply action: a wrapper
21688
+ * update is an ANNOUNCEMENT. The notification body carries the exact command
21689
+ * for a `docker` shell and says the app restarts into the new build for
21690
+ * `electron`, and that sentence is chosen from `kind` alone — a boolean
21691
+ * nothing reads is the defect this repo keeps paying for.
21692
+ */
21693
+ var WrapperIdentitySchema = object({
21694
+ kind: _enum([
21695
+ "docker",
21696
+ "electron",
21697
+ "native",
21698
+ "contradictory",
21699
+ "unknown"
21700
+ ]),
21701
+ /** Every probe that ran, in a stable order. Never empty. */
21702
+ evidence: array(object({
21703
+ /** Which probe this row reports. */
21704
+ fact: _enum([
21705
+ "dockerenv-file",
21706
+ "proc-1-cgroup",
21707
+ "platform",
21708
+ "electron-app-version-env"
21709
+ ]),
21710
+ /**
21711
+ * `observed` — this process read it itself. `declared` — the shell told the
21712
+ * process and nothing here can check it. Only the Electron app version is
21713
+ * ever `declared`, and only because a child cannot see its parent.
21714
+ */
21715
+ mode: _enum(["observed", "declared"]),
21716
+ /** Did the probe support the fact it names? A `false` row is still evidence. */
21717
+ holds: boolean(),
21718
+ /** What was actually read, verbatim enough for an operator to argue with. */
21719
+ detail: string()
21720
+ })),
21721
+ /**
21722
+ * The version of the SHELL, when the shell has one it can state: the
21723
+ * Electron app version it declared, or the baked seed closure that
21724
+ * fingerprints a container / app bundle. `null` for `contradictory` and
21725
+ * `unknown` — which version belongs to the shell is precisely what is not
21726
+ * known there.
21727
+ */
21728
+ currentVersion: string().nullable()
21729
+ });
21672
21730
  var ServerRollbackInfoSchema = object({
21673
21731
  /** The version that failed (or was manually rolled back). */
21674
21732
  fromVersion: string(),
@@ -21710,7 +21768,13 @@ var ServerPackageStatusSchema = object({
21710
21768
  * Seed-vs-contract verdict (see {@link ImageContractSchema}). Optional for
21711
21769
  * version skew: an older provider's payload simply omits it.
21712
21770
  */
21713
- imageContract: ImageContractSchema.optional()
21771
+ imageContract: ImageContractSchema.optional(),
21772
+ /**
21773
+ * What this node runs INSIDE (see {@link WrapperIdentitySchema}). Optional
21774
+ * for version skew: an older provider's payload simply omits it, and an
21775
+ * absent wrapper is unknown — never `native`.
21776
+ */
21777
+ wrapper: WrapperIdentitySchema.optional()
21714
21778
  });
21715
21779
  var ServerUpdateCheckResultSchema = object({
21716
21780
  packageName: string(),
@@ -27748,7 +27812,23 @@ var RecordingRangeSchema = object({
27748
27812
  });
27749
27813
  var RecordingAvailabilitySchema = object({
27750
27814
  deviceId: number(),
27751
- ranges: array(RecordingRangeSchema)
27815
+ ranges: array(RecordingRangeSchema),
27816
+ /**
27817
+ * Every profile this camera has footage in — not only the one `ranges`
27818
+ * describes (D433).
27819
+ *
27820
+ * `ranges` answers for ONE profile by design: the timeline is a single bar,
27821
+ * and enumerating all of them triples the directory reads for a bar that
27822
+ * would look identical. But the answer used to say nothing about that, so a
27823
+ * caller asking "what can I export?" read the single preferred profile as
27824
+ * the only one that exists — on this deployment every camera records `high`
27825
+ * AND `low`, the low tree holding 14 GB for camera 615 alone, and the export
27826
+ * UI could not see it.
27827
+ *
27828
+ * Cheap: it is the same shallow directory read the profile CHOICE already
27829
+ * makes. Ask for a specific profile's ranges with the `profile` input.
27830
+ */
27831
+ profilesWithFootage: array(string())
27752
27832
  });
27753
27833
  var RecordingDaysSchema = object({
27754
27834
  deviceId: number(),
@@ -27774,7 +27854,11 @@ var RecordingDaysSchema = object({
27774
27854
  var RecordingAvailabilityForDeviceSchema = object({
27775
27855
  deviceId: number(),
27776
27856
  read: _enum(["read", "unreadable"]),
27777
- ranges: array(RecordingRangeSchema).readonly()
27857
+ ranges: array(RecordingRangeSchema).readonly(),
27858
+ /** Same field, same meaning, as the singular answer (D433). A row that
27859
+ * dropped it would tell a grid caller the archive holds one profile.
27860
+ * Empty on an `'unreadable'` row: nobody looked. */
27861
+ profilesWithFootage: array(string()).readonly()
27778
27862
  });
27779
27863
  /**
27780
27864
  * One camera's row in a `getDaysWithRecordingsBatch` answer. Same rule as
@@ -28064,7 +28148,14 @@ var ReadWindowBytesResultSchema = discriminatedUnion("kind", [object({
28064
28148
  method(object({
28065
28149
  deviceId: number(),
28066
28150
  fromMs: number(),
28067
- toMs: number()
28151
+ toMs: number(),
28152
+ /**
28153
+ * Answer for THIS profile instead of the preferred one (D433). Absent
28154
+ * keeps the timeline's behaviour — one bar, one profile, one set of
28155
+ * reads. `profilesWithFootage` on the answer says what may be asked
28156
+ * for.
28157
+ */
28158
+ profile: string().optional()
28068
28159
  }), RecordingAvailabilitySchema, {
28069
28160
  kind: "query",
28070
28161
  auth: "protected"
@@ -16161,6 +16161,7 @@ var NcSystemEventKindSchema = _enum([
16161
16161
  "addon-crash-loop",
16162
16162
  "addon-update-available",
16163
16163
  "server-update-available",
16164
+ "wrapper-update-available",
16164
16165
  "alarm-triggered",
16165
16166
  "alarm-armed",
16166
16167
  "alarm-disarmed",
@@ -19566,7 +19567,17 @@ var EventDensityBucketSchema = object({
19566
19567
  bucketStart: number(),
19567
19568
  motion: number().int(),
19568
19569
  object: number().int(),
19569
- audio: number().int()
19570
+ audio: number().int(),
19571
+ /**
19572
+ * Energy-weighted mean dBFS of the audio events in this bucket — the LEVEL,
19573
+ * as opposed to `audio`, which is their COUNT (D431).
19574
+ *
19575
+ * ABSENT when the bucket holds no audio event. Absence means "nothing was
19576
+ * measured", which is not the same claim as silence, and a lane that cannot
19577
+ * tell them apart paints a quiet hour at full scale — which is exactly what
19578
+ * the count-on-a-level-meter did.
19579
+ */
19580
+ audioDbfs: number().optional()
19570
19581
  });
19571
19582
  /**
19572
19583
  * One camera's row in a `getEventDensityBatch` answer.
@@ -21667,6 +21678,53 @@ var ImageContractSchema = object({
21667
21678
  /** One operator-grade sentence: this node runs image X; the contract says Y. */
21668
21679
  message: string()
21669
21680
  });
21681
+ /**
21682
+ * The shell verdict (see {@link WrapperKindSchema}) with the proofs that
21683
+ * produced it.
21684
+ *
21685
+ * There is deliberately NO `canSelfUpdate` and no apply action: a wrapper
21686
+ * update is an ANNOUNCEMENT. The notification body carries the exact command
21687
+ * for a `docker` shell and says the app restarts into the new build for
21688
+ * `electron`, and that sentence is chosen from `kind` alone — a boolean
21689
+ * nothing reads is the defect this repo keeps paying for.
21690
+ */
21691
+ var WrapperIdentitySchema = object({
21692
+ kind: _enum([
21693
+ "docker",
21694
+ "electron",
21695
+ "native",
21696
+ "contradictory",
21697
+ "unknown"
21698
+ ]),
21699
+ /** Every probe that ran, in a stable order. Never empty. */
21700
+ evidence: array(object({
21701
+ /** Which probe this row reports. */
21702
+ fact: _enum([
21703
+ "dockerenv-file",
21704
+ "proc-1-cgroup",
21705
+ "platform",
21706
+ "electron-app-version-env"
21707
+ ]),
21708
+ /**
21709
+ * `observed` — this process read it itself. `declared` — the shell told the
21710
+ * process and nothing here can check it. Only the Electron app version is
21711
+ * ever `declared`, and only because a child cannot see its parent.
21712
+ */
21713
+ mode: _enum(["observed", "declared"]),
21714
+ /** Did the probe support the fact it names? A `false` row is still evidence. */
21715
+ holds: boolean(),
21716
+ /** What was actually read, verbatim enough for an operator to argue with. */
21717
+ detail: string()
21718
+ })),
21719
+ /**
21720
+ * The version of the SHELL, when the shell has one it can state: the
21721
+ * Electron app version it declared, or the baked seed closure that
21722
+ * fingerprints a container / app bundle. `null` for `contradictory` and
21723
+ * `unknown` — which version belongs to the shell is precisely what is not
21724
+ * known there.
21725
+ */
21726
+ currentVersion: string().nullable()
21727
+ });
21670
21728
  var ServerRollbackInfoSchema = object({
21671
21729
  /** The version that failed (or was manually rolled back). */
21672
21730
  fromVersion: string(),
@@ -21708,7 +21766,13 @@ var ServerPackageStatusSchema = object({
21708
21766
  * Seed-vs-contract verdict (see {@link ImageContractSchema}). Optional for
21709
21767
  * version skew: an older provider's payload simply omits it.
21710
21768
  */
21711
- imageContract: ImageContractSchema.optional()
21769
+ imageContract: ImageContractSchema.optional(),
21770
+ /**
21771
+ * What this node runs INSIDE (see {@link WrapperIdentitySchema}). Optional
21772
+ * for version skew: an older provider's payload simply omits it, and an
21773
+ * absent wrapper is unknown — never `native`.
21774
+ */
21775
+ wrapper: WrapperIdentitySchema.optional()
21712
21776
  });
21713
21777
  var ServerUpdateCheckResultSchema = object({
21714
21778
  packageName: string(),
@@ -27746,7 +27810,23 @@ var RecordingRangeSchema = object({
27746
27810
  });
27747
27811
  var RecordingAvailabilitySchema = object({
27748
27812
  deviceId: number(),
27749
- ranges: array(RecordingRangeSchema)
27813
+ ranges: array(RecordingRangeSchema),
27814
+ /**
27815
+ * Every profile this camera has footage in — not only the one `ranges`
27816
+ * describes (D433).
27817
+ *
27818
+ * `ranges` answers for ONE profile by design: the timeline is a single bar,
27819
+ * and enumerating all of them triples the directory reads for a bar that
27820
+ * would look identical. But the answer used to say nothing about that, so a
27821
+ * caller asking "what can I export?" read the single preferred profile as
27822
+ * the only one that exists — on this deployment every camera records `high`
27823
+ * AND `low`, the low tree holding 14 GB for camera 615 alone, and the export
27824
+ * UI could not see it.
27825
+ *
27826
+ * Cheap: it is the same shallow directory read the profile CHOICE already
27827
+ * makes. Ask for a specific profile's ranges with the `profile` input.
27828
+ */
27829
+ profilesWithFootage: array(string())
27750
27830
  });
27751
27831
  var RecordingDaysSchema = object({
27752
27832
  deviceId: number(),
@@ -27772,7 +27852,11 @@ var RecordingDaysSchema = object({
27772
27852
  var RecordingAvailabilityForDeviceSchema = object({
27773
27853
  deviceId: number(),
27774
27854
  read: _enum(["read", "unreadable"]),
27775
- ranges: array(RecordingRangeSchema).readonly()
27855
+ ranges: array(RecordingRangeSchema).readonly(),
27856
+ /** Same field, same meaning, as the singular answer (D433). A row that
27857
+ * dropped it would tell a grid caller the archive holds one profile.
27858
+ * Empty on an `'unreadable'` row: nobody looked. */
27859
+ profilesWithFootage: array(string()).readonly()
27776
27860
  });
27777
27861
  /**
27778
27862
  * One camera's row in a `getDaysWithRecordingsBatch` answer. Same rule as
@@ -28062,7 +28146,14 @@ var ReadWindowBytesResultSchema = discriminatedUnion("kind", [object({
28062
28146
  method(object({
28063
28147
  deviceId: number(),
28064
28148
  fromMs: number(),
28065
- toMs: number()
28149
+ toMs: number(),
28150
+ /**
28151
+ * Answer for THIS profile instead of the preferred one (D433). Absent
28152
+ * keeps the timeline's behaviour — one bar, one profile, one set of
28153
+ * reads. `profilesWithFootage` on the answer says what may be asked
28154
+ * for.
28155
+ */
28156
+ profile: string().optional()
28066
28157
  }), RecordingAvailabilitySchema, {
28067
28158
  kind: "query",
28068
28159
  auth: "protected"
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@camstack/addon-smtp-nodemailer",
3
- "version": "1.2.91",
3
+ "version": "1.2.93",
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",