@camstack/addon-smtp-nodemailer 1.2.96 → 1.2.98

package/dist/smtp.addon.js

@@ -7324,6 +7324,23 @@ method(object({ deviceId: number() }), array(StreamSourceEntrySchema)), method(o
 	action: string().min(1),
 	input: unknown()
 }), unknown(), { kind: "mutation" }), method(object({ deviceId: number() }), _void(), { kind: "mutation" }), method(object({ deviceId: number() }), unknown().nullable()), method(object({ deviceId: number() }), RawStateResultSchema.nullable(), { auth: "protected" });
+new Set([
+	"track",
+	"summary",
+	"face",
+	"identity",
+	"plate",
+	"vehicle",
+	"scene",
+	"motion",
+	"object",
+	"audio"
+]);
+new Set([
+	"motion",
+	"object",
+	"audio"
+]);
 var EncodeProfileSchema = object({
 	video: object({
 		codec: _enum([
@@ -12422,8 +12439,17 @@ method(object({
 }), array(SettingsRecordSchema).readonly()), method(object({
 	namespace: string().optional(),
 	collection: string(),
-	record: SettingsRecordSchema
-}), _void(), { kind: "mutation" }), method(object({
+	record: object({
+		id: string().optional(),
+		data: record(string(), unknown())
+	})
+}), object({ 
+/**
+* The id the row ACTUALLY got (D473): the one supplied, the UUID minted
+* for an absent one, or the ROWID SQLite assigned on an `INTEGER`
+* primary key — which is the only place an auto key is knowable.
+*/
+id: union([string(), number()]) }), { kind: "mutation" }), method(object({
 	namespace: string().optional(),
 	collection: string(),
 	records: array(BulkRecordSchema).readonly()
@@ -12532,8 +12558,17 @@ method(_void(), EngineInfoSchema, { auth: "admin" }), method(object({
 }), array(SettingsRecordSchema).readonly(), { auth: "admin" }), method(object({
 	namespace: string().optional(),
 	collection: string(),
-	record: SettingsRecordSchema
-}), _void(), {
+	record: object({
+		id: string().optional(),
+		data: record(string(), unknown())
+	})
+}), object({ 
+/**
+* The id the row ACTUALLY got (D473): the one supplied, the UUID minted
+* for an absent one, or the ROWID SQLite assigned on an `INTEGER`
+* primary key — which is the only place an auto key is knowable.
+*/
+id: union([string(), number()]) }), {
 	kind: "mutation",
 	auth: "admin"
 }), method(object({
@@ -19175,7 +19210,20 @@ var TrackSchema = object({
 	...TrackRetrainFields
 });
 var BaseEventFields = {
-	id: string(),
+	/**
+	* A SQLite ROWID, assigned by the database (D474).
+	*
+	* Was a 36-character UUID and cost 263 MB of a 1 117 MB database — paid
+	* TWICE per row, in the row and in the primary-key index, across 2.1 million
+	* motion, audio and object events. An `INTEGER PRIMARY KEY` in SQLite **is**
+	* the rowid: the table itself is that B-tree, so the index stops existing
+	* rather than getting smaller. No shorter string does that.
+	*
+	* Defined once here for all three event kinds, which is why they move
+	* together: a per-table migration would have forked this and
+	* `COMMON_BASE_COLUMNS` and reunited them two stages later.
+	*/
+	id: number().int(),
 	deviceId: number(),
 	timestamp: number()
 };
@@ -19194,7 +19242,34 @@ var MotionEventSchema = object({
 	/** Omitted in slim projection. */
 	frameHeight: number().optional(),
 	/** Populated by B5 (recording playback URL for this event). */
-	mediaUrl: string().optional()
+	mediaUrl: string().optional(),
+	/**
+	* One row per motion EPISODE, not one per push (D475). `null` while the
+	* episode is still open — a further rising edge extends it in place rather
+	* than inserting a new row. Set once, at close, to `lastOnAt - startedAt`
+	* (the span from the first rising edge to the LAST one, deliberately NOT
+	* `closedAt - startedAt` — the close delay is a quiet CONFIRMATION, not
+	* movement, and folding it in would report `MOTION_CLOSE_AFTER_MS` of
+	* motion for an instantaneous trigger).
+	*
+	* **Absent** (not merely `null`) on a row written before D475 — that means
+	* "closed the old way, before this column existed", never "still open".
+	* Nothing in this codebase may read an absent `durationMs` as an open
+	* episode; only `null` means open.
+	*/
+	durationMs: number().nullable().optional(),
+	/**
+	* 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
+	* 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
+	* elapses produces another. Stored compactly — see `motion-edge-codec.ts`
+	* — and decoded back to this shape on read. Absent/empty on a legacy row,
+	* which must never be read as "no episode happened here".
+	*/
+	edges: array(number()).readonly().optional()
 });
 /**
 * Which detection SOURCE produced an object event. `pipeline` = the ML
@@ -19249,6 +19324,23 @@ var ObjectEventSchema = object({
 	* includes it (it is light). Absent on rows written before this field.
 	*/
 	frameId: string().optional(),
+	/**
+	* A PRODUCER-chosen key that makes a synthetic event's emission idempotent
+	* (D474).
+	*
+	* Only the package detector writes it, and it exists because the event id
+	* stopped being choosable: the delivery and pick-up rows used to BE their
+	* dedupe key (`pa-pkg-<entryId>-delivered`), which is how "never emit a
+	* second delivery for this entry" survived a restart. An `INTEGER` rowid is
+	* assigned by SQLite, so that key had to move off the primary key rather
+	* than be dropped — a detector that cannot recognise its own row re-delivers
+	* every parcel on every boot.
+	*
+	* Absent on every other object event, and on every row written before this
+	* field. Never a substitute for `id`: it is unique per (producer, occasion),
+	* not per row, and nothing addresses a row by it.
+	*/
+	idempotencyKey: string().optional(),
 	/** Omitted in slim projection. */
 	trackId: string().optional(),
 	className: string(),
@@ -26328,9 +26420,54 @@ object({
 	/** Ms epoch of the last detected-true observation. Null if never detected. */
 	lastDetectedAt: number().nullable(),
 	/**
-	* Ms after which `detected` auto-reverts to false if no fresh push
-	* arrives. Null means the provider leaves detected state until a
-	* native "clear" event.
+	* `MOTION_CLOSE_AFTER_MS` while `detected: true` on a `Camera` device,
+	* `null` while false and on every `Sensor` device (D475) — see that
+	* constant's doc for the one-authority rule.
+	*
+	* ## Reading this field still arms nothing
+	*
+	* It reads like an instruction to the consumer ("revert after N ms if
+	* no fresh push arrives") and it is not one: nothing in this repo reads
+	* the LIVE cap value to drive a timer. `pipeline-analytics`'s motion-episode
+	* close DOES now use the same number — `MOTION_CLOSE_AFTER_MS` — but as an
+	* imported constant, not as a read of `device.state.motion.value`, so this
+	* field stays what it always was: DESCRIPTIVE output, mirroring an answer
+	* computed elsewhere. Building a self-clear timer out of a READ of this
+	* field would add a second falling-edge authority beside whichever one
+	* already owns the device, and two that can disagree are worse than one.
+	* Consumers that need a falling edge SHAPED differently — held open across
+	* a flapping source — debounce on their own side and say so, as
+	* `addon-export-alexa/src/motion-clear-hold.ts` and
+	* `addon-export-hap`'s `RESET_DEBOUNCE_MS` both do.
+	*
+	* ## Who writes it
+	*
+	* - **Cameras** — the runner's phase machine, `active → watching` on
+	*   `cooldown_expired`, which then writes this slice with
+	*   `detected: false` (`handlePhaseChanged` in
+	*   `pipeline-runner/index.ts`). It produces the FALLING edge, which
+	*   matters most for the sources that only ever push a rising one:
+	*   Reolink emits `MotionOnMotionChanged { detected: true }` and never
+	*   a false.
+	* - **Sensors** (Home Assistant binary sensors, Homematic) — the
+	*   provider pushes the false itself, from the upstream system's own
+	*   state change. No phase machine is involved.
+	*
+	* ### The phase machine is CANONICAL, not sole — and that is a defect
+	*
+	* An earlier revision of this docblock (mine, 2026-09-12) claimed the
+	* phase machine is the sole writer for a camera. It is not.
+	* `hikvision-camera.ts:3464` and `amcrest-camera.ts:445` both call
+	* `setCapSlice(motionCapability, …)` on their own rising edge, and
+	* Hikvision's comment says why: it read THIS docblock, agreed the
+	* runner is canonical, and wrote anyway to avoid per-tick churn. So
+	* two authorities can disagree about one slice, which this repo
+	* forbids, and the doc said otherwise — which is worse than saying
+	* nothing, because it reads as verification.
+	*
+	* This predates D475 and is not fixed there: the fix touches every
+	* camera provider. Recorded in D475's Consequences. Do not restore the
+	* "sole writer" wording without also removing the other writers.
 	*/
 	autoClearAfterMs: number().nullable()
 });

package/dist/smtp.addon.mjs

@@ -7322,6 +7322,23 @@ method(object({ deviceId: number() }), array(StreamSourceEntrySchema)), method(o
 	action: string().min(1),
 	input: unknown()
 }), unknown(), { kind: "mutation" }), method(object({ deviceId: number() }), _void(), { kind: "mutation" }), method(object({ deviceId: number() }), unknown().nullable()), method(object({ deviceId: number() }), RawStateResultSchema.nullable(), { auth: "protected" });
+new Set([
+	"track",
+	"summary",
+	"face",
+	"identity",
+	"plate",
+	"vehicle",
+	"scene",
+	"motion",
+	"object",
+	"audio"
+]);
+new Set([
+	"motion",
+	"object",
+	"audio"
+]);
 var EncodeProfileSchema = object({
 	video: object({
 		codec: _enum([
@@ -12420,8 +12437,17 @@ method(object({
 }), array(SettingsRecordSchema).readonly()), method(object({
 	namespace: string().optional(),
 	collection: string(),
-	record: SettingsRecordSchema
-}), _void(), { kind: "mutation" }), method(object({
+	record: object({
+		id: string().optional(),
+		data: record(string(), unknown())
+	})
+}), object({ 
+/**
+* The id the row ACTUALLY got (D473): the one supplied, the UUID minted
+* for an absent one, or the ROWID SQLite assigned on an `INTEGER`
+* primary key — which is the only place an auto key is knowable.
+*/
+id: union([string(), number()]) }), { kind: "mutation" }), method(object({
 	namespace: string().optional(),
 	collection: string(),
 	records: array(BulkRecordSchema).readonly()
@@ -12530,8 +12556,17 @@ method(_void(), EngineInfoSchema, { auth: "admin" }), method(object({
 }), array(SettingsRecordSchema).readonly(), { auth: "admin" }), method(object({
 	namespace: string().optional(),
 	collection: string(),
-	record: SettingsRecordSchema
-}), _void(), {
+	record: object({
+		id: string().optional(),
+		data: record(string(), unknown())
+	})
+}), object({ 
+/**
+* The id the row ACTUALLY got (D473): the one supplied, the UUID minted
+* for an absent one, or the ROWID SQLite assigned on an `INTEGER`
+* primary key — which is the only place an auto key is knowable.
+*/
+id: union([string(), number()]) }), {
 	kind: "mutation",
 	auth: "admin"
 }), method(object({
@@ -19173,7 +19208,20 @@ var TrackSchema = object({
 	...TrackRetrainFields
 });
 var BaseEventFields = {
-	id: string(),
+	/**
+	* A SQLite ROWID, assigned by the database (D474).
+	*
+	* Was a 36-character UUID and cost 263 MB of a 1 117 MB database — paid
+	* TWICE per row, in the row and in the primary-key index, across 2.1 million
+	* motion, audio and object events. An `INTEGER PRIMARY KEY` in SQLite **is**
+	* the rowid: the table itself is that B-tree, so the index stops existing
+	* rather than getting smaller. No shorter string does that.
+	*
+	* Defined once here for all three event kinds, which is why they move
+	* together: a per-table migration would have forked this and
+	* `COMMON_BASE_COLUMNS` and reunited them two stages later.
+	*/
+	id: number().int(),
 	deviceId: number(),
 	timestamp: number()
 };
@@ -19192,7 +19240,34 @@ var MotionEventSchema = object({
 	/** Omitted in slim projection. */
 	frameHeight: number().optional(),
 	/** Populated by B5 (recording playback URL for this event). */
-	mediaUrl: string().optional()
+	mediaUrl: string().optional(),
+	/**
+	* One row per motion EPISODE, not one per push (D475). `null` while the
+	* episode is still open — a further rising edge extends it in place rather
+	* than inserting a new row. Set once, at close, to `lastOnAt - startedAt`
+	* (the span from the first rising edge to the LAST one, deliberately NOT
+	* `closedAt - startedAt` — the close delay is a quiet CONFIRMATION, not
+	* movement, and folding it in would report `MOTION_CLOSE_AFTER_MS` of
+	* motion for an instantaneous trigger).
+	*
+	* **Absent** (not merely `null`) on a row written before D475 — that means
+	* "closed the old way, before this column existed", never "still open".
+	* Nothing in this codebase may read an absent `durationMs` as an open
+	* episode; only `null` means open.
+	*/
+	durationMs: number().nullable().optional(),
+	/**
+	* 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
+	* 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
+	* elapses produces another. Stored compactly — see `motion-edge-codec.ts`
+	* — and decoded back to this shape on read. Absent/empty on a legacy row,
+	* which must never be read as "no episode happened here".
+	*/
+	edges: array(number()).readonly().optional()
 });
 /**
 * Which detection SOURCE produced an object event. `pipeline` = the ML
@@ -19247,6 +19322,23 @@ var ObjectEventSchema = object({
 	* includes it (it is light). Absent on rows written before this field.
 	*/
 	frameId: string().optional(),
+	/**
+	* A PRODUCER-chosen key that makes a synthetic event's emission idempotent
+	* (D474).
+	*
+	* Only the package detector writes it, and it exists because the event id
+	* stopped being choosable: the delivery and pick-up rows used to BE their
+	* dedupe key (`pa-pkg-<entryId>-delivered`), which is how "never emit a
+	* second delivery for this entry" survived a restart. An `INTEGER` rowid is
+	* assigned by SQLite, so that key had to move off the primary key rather
+	* than be dropped — a detector that cannot recognise its own row re-delivers
+	* every parcel on every boot.
+	*
+	* Absent on every other object event, and on every row written before this
+	* field. Never a substitute for `id`: it is unique per (producer, occasion),
+	* not per row, and nothing addresses a row by it.
+	*/
+	idempotencyKey: string().optional(),
 	/** Omitted in slim projection. */
 	trackId: string().optional(),
 	className: string(),
@@ -26326,9 +26418,54 @@ object({
 	/** Ms epoch of the last detected-true observation. Null if never detected. */
 	lastDetectedAt: number().nullable(),
 	/**
-	* Ms after which `detected` auto-reverts to false if no fresh push
-	* arrives. Null means the provider leaves detected state until a
-	* native "clear" event.
+	* `MOTION_CLOSE_AFTER_MS` while `detected: true` on a `Camera` device,
+	* `null` while false and on every `Sensor` device (D475) — see that
+	* constant's doc for the one-authority rule.
+	*
+	* ## Reading this field still arms nothing
+	*
+	* It reads like an instruction to the consumer ("revert after N ms if
+	* no fresh push arrives") and it is not one: nothing in this repo reads
+	* the LIVE cap value to drive a timer. `pipeline-analytics`'s motion-episode
+	* close DOES now use the same number — `MOTION_CLOSE_AFTER_MS` — but as an
+	* imported constant, not as a read of `device.state.motion.value`, so this
+	* field stays what it always was: DESCRIPTIVE output, mirroring an answer
+	* computed elsewhere. Building a self-clear timer out of a READ of this
+	* field would add a second falling-edge authority beside whichever one
+	* already owns the device, and two that can disagree are worse than one.
+	* Consumers that need a falling edge SHAPED differently — held open across
+	* a flapping source — debounce on their own side and say so, as
+	* `addon-export-alexa/src/motion-clear-hold.ts` and
+	* `addon-export-hap`'s `RESET_DEBOUNCE_MS` both do.
+	*
+	* ## Who writes it
+	*
+	* - **Cameras** — the runner's phase machine, `active → watching` on
+	*   `cooldown_expired`, which then writes this slice with
+	*   `detected: false` (`handlePhaseChanged` in
+	*   `pipeline-runner/index.ts`). It produces the FALLING edge, which
+	*   matters most for the sources that only ever push a rising one:
+	*   Reolink emits `MotionOnMotionChanged { detected: true }` and never
+	*   a false.
+	* - **Sensors** (Home Assistant binary sensors, Homematic) — the
+	*   provider pushes the false itself, from the upstream system's own
+	*   state change. No phase machine is involved.
+	*
+	* ### The phase machine is CANONICAL, not sole — and that is a defect
+	*
+	* An earlier revision of this docblock (mine, 2026-09-12) claimed the
+	* phase machine is the sole writer for a camera. It is not.
+	* `hikvision-camera.ts:3464` and `amcrest-camera.ts:445` both call
+	* `setCapSlice(motionCapability, …)` on their own rising edge, and
+	* Hikvision's comment says why: it read THIS docblock, agreed the
+	* runner is canonical, and wrote anyway to avoid per-tick churn. So
+	* two authorities can disagree about one slice, which this repo
+	* forbids, and the doc said otherwise — which is worse than saying
+	* nothing, because it reads as verification.
+	*
+	* This predates D475 and is not fixed there: the fix touches every
+	* camera provider. Recorded in D475's Consequences. Do not restore the
+	* "sole writer" wording without also removing the other writers.
 	*/
 	autoClearAfterMs: number().nullable()
 });

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@camstack/addon-smtp-nodemailer",
-  "version": "1.2.96",
+  "version": "1.2.98",
   "description": "SMTP email provider addon for CamStack — wraps `nodemailer` and registers a `smtp-provider` cap collection entry. Used by magic-link login + notifier addons.",
   "keywords": [
     "camstack",