@camstack/addon-provider-tuya 0.2.76 → 0.2.77

package/dist/addon.js

@@ -8771,13 +8771,28 @@ var RecordingBandSchema = object({
 	end: string().regex(HHMM),
 	mode: RecordingBandModeSchema,
 	triggers: RecordingBandTriggersSchema.optional(),
+	/**
+	* RETIRED (D381). A band no longer carries a pre-buffer of its own.
+	*
+	* It was the retroactive KEEP bound — which already-written segments survive
+	* a trigger — and it had to be at least as wide as the widest pre-roll the
+	* broker could serve, or the gate would delete the seconds the ring had just
+	* handed the writer. That "at least as wide as" is the tell: it was a second
+	* expression of the broker's retention, in different units, in a different
+	* addon, with an invariant the operator had to maintain by hand. The keep
+	* bound is now derived from the one prebuffer ceiling and there is nothing
+	* left to configure here.
+	*
+	* The key survives in the SHAPE so a config written before that record still
+	* parses and can be migrated deliberately — `RecordingBandSchema` is not
+	* strict, so simply deleting it would strip an operator's value in silence on
+	* the next save (the failure D380 came one commit from shipping). Nothing
+	* reads it: {@link stripRetiredBandPreBufferSec} removes it on load.
+	*/
 	preBufferSec: number().min(0).optional(),
 	postBufferSec: number().min(0).optional()
 });
-({
-	preBufferSec: 15,
-	postBufferSec: 30
-}).postBufferSec * 1e3;
+({ postBufferSec: 30 }).postBufferSec * 1e3;
 /**
 * Per-device retention overrides. Every field is optional; an unset or `0`
 * value inherits the node-wide recorder default. Only footage-lifetime limits

package/dist/addon.mjs

@@ -8770,13 +8770,28 @@ var RecordingBandSchema = object({
 	end: string().regex(HHMM),
 	mode: RecordingBandModeSchema,
 	triggers: RecordingBandTriggersSchema.optional(),
+	/**
+	* RETIRED (D381). A band no longer carries a pre-buffer of its own.
+	*
+	* It was the retroactive KEEP bound — which already-written segments survive
+	* a trigger — and it had to be at least as wide as the widest pre-roll the
+	* broker could serve, or the gate would delete the seconds the ring had just
+	* handed the writer. That "at least as wide as" is the tell: it was a second
+	* expression of the broker's retention, in different units, in a different
+	* addon, with an invariant the operator had to maintain by hand. The keep
+	* bound is now derived from the one prebuffer ceiling and there is nothing
+	* left to configure here.
+	*
+	* The key survives in the SHAPE so a config written before that record still
+	* parses and can be migrated deliberately — `RecordingBandSchema` is not
+	* strict, so simply deleting it would strip an operator's value in silence on
+	* the next save (the failure D380 came one commit from shipping). Nothing
+	* reads it: {@link stripRetiredBandPreBufferSec} removes it on load.
+	*/
 	preBufferSec: number().min(0).optional(),
 	postBufferSec: number().min(0).optional()
 });
-({
-	preBufferSec: 15,
-	postBufferSec: 30
-}).postBufferSec * 1e3;
+({ postBufferSec: 30 }).postBufferSec * 1e3;
 /**
 * Per-device retention overrides. Every field is optional; an unset or `0`
 * value inherits the node-wide recorder default. Only footage-lifetime limits

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@camstack/addon-provider-tuya",
-  "version": "0.2.76",
+  "version": "0.2.77",
   "description": "Tuya / Smart Life device-provider addon for CamStack — account-onboarded (Tuya IoT cloud fetch of device localKeys) + LOCAL DP control via the @apocaliss92/nodetuya encrypted-LAN client, exposing switch / water-heater-family kettle entities",
   "keywords": [
     "camstack",