@camstack/addon-ai 0.4.65 → 0.4.67

package/dist/addon.js

@@ -7756,7 +7756,8 @@ var CameraSwitchAuthoritySchema = discriminatedUnion("kind", [
 var CameraSwitchUnavailableReasonSchema = _enum([
 	"no-provider",
 	"source-unreachable",
-	"not-configured"
+	"not-configured",
+	"device-disabled"
 ]);
 /**
 * One switch, resolved for one camera.
@@ -12956,7 +12957,12 @@ var ConfigEntrySchema = object({
 	value: unknown(),
 	description: string().optional()
 });
-var LinkedDevicesModeSchema = _enum(["auto", "manual"]);
+/**
+* Only `manual` since D356: the operator picks, nothing links itself. The
+* field survives on the wire because a viewer already OTA'd parses it —
+* drop it once no shipped client reads `mode`.
+*/
+var LinkedDevicesModeSchema = _enum(["manual"]);
 /** One resolved linked device — the compact projection consumers need. */
 var LinkedDeviceSchema = object({
 	deviceId: number$1(),
@@ -23368,12 +23374,20 @@ var BatteryStatusSchema = object({
 	* Charging source. `'dc'` covers wall/USB adapters; `'solar'` is
 	* Reolink-specific for the Solar Panel 2 accessory (will become
 	* common on other battery cams). `'none'` means running on battery
-	* alone.
+	* alone — a NEGATIVE the firmware actually reported.
+	*
+	* `'unknown'` is the absence of an answer: the provider has not read the
+	* power fields yet, or the firmware reported neither. Before it existed,
+	* two unreadable fields produced `'none'`, and a camera nobody had reached
+	* was drawn "on battery alone" — the same D315 defect `percentage` closed
+	* by going nullable. Consumers SKIP it (no charger state published, no
+	* glyph, no HomeKit ChargingState) rather than coerce it either way.
 	*/
 	charging: _enum([
 		"dc",
 		"solar",
-		"none"
+		"none",
+		"unknown"
 	]),
 	/**
 	* True when the camera firmware has gone into low-power mode. Battery

package/dist/addon.mjs

@@ -7783,7 +7783,8 @@ var CameraSwitchAuthoritySchema = discriminatedUnion("kind", [
 var CameraSwitchUnavailableReasonSchema = _enum([
 	"no-provider",
 	"source-unreachable",
-	"not-configured"
+	"not-configured",
+	"device-disabled"
 ]);
 /**
 * One switch, resolved for one camera.
@@ -12983,7 +12984,12 @@ var ConfigEntrySchema = object({
 	value: unknown(),
 	description: string().optional()
 });
-var LinkedDevicesModeSchema = _enum(["auto", "manual"]);
+/**
+* Only `manual` since D356: the operator picks, nothing links itself. The
+* field survives on the wire because a viewer already OTA'd parses it —
+* drop it once no shipped client reads `mode`.
+*/
+var LinkedDevicesModeSchema = _enum(["manual"]);
 /** One resolved linked device — the compact projection consumers need. */
 var LinkedDeviceSchema = object({
 	deviceId: number$1(),
@@ -23395,12 +23401,20 @@ var BatteryStatusSchema = object({
 	* Charging source. `'dc'` covers wall/USB adapters; `'solar'` is
 	* Reolink-specific for the Solar Panel 2 accessory (will become
 	* common on other battery cams). `'none'` means running on battery
-	* alone.
+	* alone — a NEGATIVE the firmware actually reported.
+	*
+	* `'unknown'` is the absence of an answer: the provider has not read the
+	* power fields yet, or the firmware reported neither. Before it existed,
+	* two unreadable fields produced `'none'`, and a camera nobody had reached
+	* was drawn "on battery alone" — the same D315 defect `percentage` closed
+	* by going nullable. Consumers SKIP it (no charger state published, no
+	* glyph, no HomeKit ChargingState) rather than coerce it either way.
 	*/
 	charging: _enum([
 		"dc",
 		"solar",
-		"none"
+		"none",
+		"unknown"
 	]),
 	/**
 	* True when the camera firmware has gone into low-power mode. Battery

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@camstack/addon-ai",
-  "version": "0.4.65",
+  "version": "0.4.67",
   "description": "AI addon for CamStack — the `llm` collection provider (cloud, LAN, and camstack-managed local llama.cpp profiles) plus the per-node `llm-runtime` managed executor.",
   "keywords": [
     "camstack",