@camstack/addon-provider-tuya 0.2.62 → 0.2.64

package/dist/addon.js

@@ -13764,6 +13764,24 @@ var deviceProviderCapability = {
 		})
 	}
 };
+/**
+* Device Manager capability — hub-side singleton that unifies device persistence,
+* live registry access, and all management operations into a single tRPC surface.
+*
+* Replaces:
+*   - `device-persistence` capability (persistence methods absorbed here)
+*   - `device-management.router.ts` (deleted in Phase 2)
+*   - `device-ops.router.ts` (compat layer — deleted; device-provider ops absorbed here)
+*
+* All device provider addons (rtsp, onvif, frigate, …) are hub-local: they may
+* fork into separate processes but never run on remote cluster agents. Therefore:
+*   - No nodeId routing needed — this is a pure hub singleton.
+*   - The hub's DeviceRegistry is the single source of truth for all live devices.
+*   - No shadow registry or cross-node aggregation required.
+*
+* Forked workers register devices back to the hub via `ctx.devices`
+* (DeviceManagerApi → ctx.api.deviceManager.registerDevice), same as today.
+*/
 /** One child-placement directive on a container's `childLayout`. Structurally
 *  identical to `ChildLayoutEntry` in `device-management.ts` — the cap wire
 *  shape for the same field. The child is identified by its re-sync-stable
@@ -19490,6 +19508,9 @@ var RetrainStatusSchema = _enum([
 *
 * `debug` does NOT pin; it is attention, not durability.
 *
+* `debugNote` is the operator's own words about WHAT should be checked on this
+* track, and it lives and dies with `debug` — see {@link MAX_TRACK_DEBUG_NOTE_LEN}.
+*
 * `favourited` IS a BOOLEAN pin (durability bit), not a retrain lifecycle.
 * A favourited track is skipped by retention the same way `staging` is, but
 * it does not enter `none|staging|trained` and has no staging budget.
@@ -19500,6 +19521,21 @@ var TrackFlagFields = {
 	markForTrain: boolean().optional(),
 	/** Operator marked this track for diagnostic attention. */
 	debug: boolean().optional(),
+	/**
+	* What the operator wants CHECKED on this track, in their own words.
+	*
+	* The flag alone says "look at this" and nothing about what for; a debug set
+	* reviewed hours later is a list of tracks with no question attached. Bound
+	* to `debug` on the WRITE side — the body clears it when `debug` goes off,
+	* and refuses it on a track whose debug is off — so a note can never outlive
+	* the attention it belongs to.
+	*
+	* `''` is a real value ("marked, nothing to add"); the ABSENT key means
+	* "leave whatever is stored alone", which is what lets a surface turn debug
+	* on without a note (a cancelled prompt) and what lets it edit the note
+	* without touching the flag.
+	*/
+	debugNote: string().max(500).optional(),
 	/** Operator favourited this track. Pins it against pruning. */
 	favourited: boolean().optional()
 };
@@ -19526,6 +19562,12 @@ var TrackFlagsSchema = object({
 	trackId: string(),
 	markForTrain: boolean(),
 	debug: boolean(),
+	/** The note as it STANDS after the write — never absent here (a track with no
+	*  note reports `''`), for the same reason the booleans are required: a
+	*  surface that has just written must be able to render the note it now owns
+	*  without a re-fetch, and an absent key would read as "unchanged" on a
+	*  screen that has no previous value to keep. */
+	debugNote: string(),
 	favourited: boolean(),
 	/** The lifecycle state the boolean was derived from. Required here (unlike on
 	*  a track row) because this shape is only ever produced by the write body,

package/dist/addon.mjs

@@ -13763,6 +13763,24 @@ var deviceProviderCapability = {
 		})
 	}
 };
+/**
+* Device Manager capability — hub-side singleton that unifies device persistence,
+* live registry access, and all management operations into a single tRPC surface.
+*
+* Replaces:
+*   - `device-persistence` capability (persistence methods absorbed here)
+*   - `device-management.router.ts` (deleted in Phase 2)
+*   - `device-ops.router.ts` (compat layer — deleted; device-provider ops absorbed here)
+*
+* All device provider addons (rtsp, onvif, frigate, …) are hub-local: they may
+* fork into separate processes but never run on remote cluster agents. Therefore:
+*   - No nodeId routing needed — this is a pure hub singleton.
+*   - The hub's DeviceRegistry is the single source of truth for all live devices.
+*   - No shadow registry or cross-node aggregation required.
+*
+* Forked workers register devices back to the hub via `ctx.devices`
+* (DeviceManagerApi → ctx.api.deviceManager.registerDevice), same as today.
+*/
 /** One child-placement directive on a container's `childLayout`. Structurally
 *  identical to `ChildLayoutEntry` in `device-management.ts` — the cap wire
 *  shape for the same field. The child is identified by its re-sync-stable
@@ -19489,6 +19507,9 @@ var RetrainStatusSchema = _enum([
 *
 * `debug` does NOT pin; it is attention, not durability.
 *
+* `debugNote` is the operator's own words about WHAT should be checked on this
+* track, and it lives and dies with `debug` — see {@link MAX_TRACK_DEBUG_NOTE_LEN}.
+*
 * `favourited` IS a BOOLEAN pin (durability bit), not a retrain lifecycle.
 * A favourited track is skipped by retention the same way `staging` is, but
 * it does not enter `none|staging|trained` and has no staging budget.
@@ -19499,6 +19520,21 @@ var TrackFlagFields = {
 	markForTrain: boolean().optional(),
 	/** Operator marked this track for diagnostic attention. */
 	debug: boolean().optional(),
+	/**
+	* What the operator wants CHECKED on this track, in their own words.
+	*
+	* The flag alone says "look at this" and nothing about what for; a debug set
+	* reviewed hours later is a list of tracks with no question attached. Bound
+	* to `debug` on the WRITE side — the body clears it when `debug` goes off,
+	* and refuses it on a track whose debug is off — so a note can never outlive
+	* the attention it belongs to.
+	*
+	* `''` is a real value ("marked, nothing to add"); the ABSENT key means
+	* "leave whatever is stored alone", which is what lets a surface turn debug
+	* on without a note (a cancelled prompt) and what lets it edit the note
+	* without touching the flag.
+	*/
+	debugNote: string().max(500).optional(),
 	/** Operator favourited this track. Pins it against pruning. */
 	favourited: boolean().optional()
 };
@@ -19525,6 +19561,12 @@ var TrackFlagsSchema = object({
 	trackId: string(),
 	markForTrain: boolean(),
 	debug: boolean(),
+	/** The note as it STANDS after the write — never absent here (a track with no
+	*  note reports `''`), for the same reason the booleans are required: a
+	*  surface that has just written must be able to render the note it now owns
+	*  without a re-fetch, and an absent key would read as "unchanged" on a
+	*  screen that has no previous value to keep. */
+	debugNote: string(),
 	favourited: boolean(),
 	/** The lifecycle state the boolean was derived from. Required here (unlike on
 	*  a track row) because this shape is only ever produced by the write body,

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@camstack/addon-provider-tuya",
-  "version": "0.2.62",
+  "version": "0.2.64",
   "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",