@camstack/types 1.2.32 → 1.2.33

package/dist/capabilities/broker.cap.d.ts

@@ -96,6 +96,7 @@ export type BrokerProviderInfo = z.infer<typeof BrokerProviderInfoSchema>;
 declare const AddInputSchema: z.ZodObject<{
     kind: z.ZodString;
     name: z.ZodString;
+    id: z.ZodOptional<z.ZodString>;
     settings: z.ZodRecord<z.ZodString, z.ZodUnknown>;
 }, z.core.$strip>;
 declare const TestConnectionResultSchema: z.ZodDiscriminatedUnion<[z.ZodObject<{
@@ -204,6 +205,7 @@ export declare const brokerCapability: {
         readonly add: import("./capability-definition.js").CapabilityMethodSchema<z.ZodObject<{
             kind: z.ZodString;
             name: z.ZodString;
+            id: z.ZodOptional<z.ZodString>;
             settings: z.ZodRecord<z.ZodString, z.ZodUnknown>;
         }, z.core.$strip>, z.ZodObject<{
             id: z.ZodString;

package/dist/index.js

@@ -17621,6 +17621,20 @@ var GetInputSchema = zod.z.object({ id: zod.z.string() });
 var AddInputSchema = zod.z.object({
 	kind: zod.z.string().min(1),
 	name: zod.z.string().min(1),
+	/**
+	* ADOPT an existing id instead of minting a new one.
+	*
+	* Written the day this cost an outage. A broker's id is not a detail: HA
+	* devices carry it inside their `stableId` (`ha:ha_004:dev:…`), so a broker
+	* lost from config and re-added as `ha_001` leaves every one of its devices
+	* bound to a broker that no longer exists. Re-entering the password under the
+	* ORIGINAL id turns a multi-step device migration back into re-entering a
+	* password.
+	*
+	* A provider MUST refuse an id that is already in use — adopting a live
+	* broker's id would silently take it over.
+	*/
+	id: zod.z.string().min(1).optional(),
 	/** Kind-specific settings (e.g. MQTT `{url,username,password}` or HA
 	*  `{baseUrl,accessToken}`). Validated by the kind-specific provider
 	*  branch on receipt — invalid shape rejects the add. */

package/dist/index.mjs

@@ -17620,6 +17620,20 @@ var GetInputSchema = z.object({ id: z.string() });
 var AddInputSchema = z.object({
 	kind: z.string().min(1),
 	name: z.string().min(1),
+	/**
+	* ADOPT an existing id instead of minting a new one.
+	*
+	* Written the day this cost an outage. A broker's id is not a detail: HA
+	* devices carry it inside their `stableId` (`ha:ha_004:dev:…`), so a broker
+	* lost from config and re-added as `ha_001` leaves every one of its devices
+	* bound to a broker that no longer exists. Re-entering the password under the
+	* ORIGINAL id turns a multi-step device migration back into re-entering a
+	* password.
+	*
+	* A provider MUST refuse an id that is already in use — adopting a live
+	* broker's id would silently take it over.
+	*/
+	id: z.string().min(1).optional(),
 	/** Kind-specific settings (e.g. MQTT `{url,username,password}` or HA
 	*  `{baseUrl,accessToken}`). Validated by the kind-specific provider
 	*  branch on receipt — invalid shape rejects the add. */

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@camstack/types",
-  "version": "1.2.32",
+  "version": "1.2.33",
   "description": "Shared types, interfaces, and model catalogs for the CamStack detection ecosystem",
   "keywords": [
     "camstack",