@camstack/types 1.2.183 → 1.2.184

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

@@ -466,6 +466,7 @@ declare const LoggingSettingsPatchSchema: z.ZodObject<{
         armMs: z.ZodNumber;
         deviceIds: z.ZodOptional<z.ZodNullable<z.ZodReadonly<z.ZodArray<z.ZodNumber>>>>;
     }, z.core.$strip>>>>;
+    opsLogRetentionDays: z.ZodOptional<z.ZodNumber>;
 }, z.core.$strip>;
 /**
  * Which LAYER of the hierarchy is addressed. Absent = the cluster layer.
@@ -555,6 +556,7 @@ declare const SetLoggingSettingsInputSchema: z.ZodObject<{
             armMs: z.ZodNumber;
             deviceIds: z.ZodOptional<z.ZodNullable<z.ZodReadonly<z.ZodArray<z.ZodNumber>>>>;
         }, z.core.$strip>>>>;
+        opsLogRetentionDays: z.ZodOptional<z.ZodNumber>;
     }, z.core.$strip>;
 }, z.core.$strip>;
 /**
@@ -626,6 +628,7 @@ declare const LoggingSettingsStateSchema: z.ZodObject<{
         remainingMs: z.ZodNumber;
         deviceIds: z.ZodNullable<z.ZodReadonly<z.ZodArray<z.ZodNumber>>>;
     }, z.core.$strip>>>;
+    opsLogRetentionDays: z.ZodNumber;
     persisted: z.ZodBoolean;
 }, z.core.$strip>;
 export declare const systemCapability: {
@@ -931,6 +934,7 @@ export declare const systemCapability: {
                 remainingMs: z.ZodNumber;
                 deviceIds: z.ZodNullable<z.ZodReadonly<z.ZodArray<z.ZodNumber>>>;
             }, z.core.$strip>>>;
+            opsLogRetentionDays: z.ZodNumber;
             persisted: z.ZodBoolean;
         }, z.core.$strip>, import("./capability-definition.js").CapabilityMethodKind>;
         /**
@@ -964,6 +968,7 @@ export declare const systemCapability: {
                     armMs: z.ZodNumber;
                     deviceIds: z.ZodOptional<z.ZodNullable<z.ZodReadonly<z.ZodArray<z.ZodNumber>>>>;
                 }, z.core.$strip>>>>;
+                opsLogRetentionDays: z.ZodOptional<z.ZodNumber>;
             }, z.core.$strip>;
         }, z.core.$strip>, z.ZodObject<{
             scopeNodeId: z.ZodNullable<z.ZodString>;
@@ -1025,6 +1030,7 @@ export declare const systemCapability: {
                 remainingMs: z.ZodNumber;
                 deviceIds: z.ZodNullable<z.ZodReadonly<z.ZodArray<z.ZodNumber>>>;
             }, z.core.$strip>>>;
+            opsLogRetentionDays: z.ZodNumber;
             persisted: z.ZodBoolean;
         }, z.core.$strip>, "mutation">;
     };

package/dist/index.js

@@ -36465,7 +36465,29 @@ var LoggingSettingsPatchSchema = zod.z.object({
 	* disarmed the channels it did not mention would make the Levels page and
 	* the Diagnostics page fight over the same value.
 	*/
-	channels: zod.z.array(LogChannelWindowPatchSchema).readonly().optional()
+	channels: zod.z.array(LogChannelWindowPatchSchema).readonly().optional(),
+	/**
+	* How many days the analytics OPS LOG is kept — the audit trail of what
+	* retention actually deleted.
+	*
+	* It lives HERE, on the logging document, and not on the analytics addon's
+	* settings form, on the operator's instruction: every other log-ish window in
+	* this system is configured through this one document, and a retention audit
+	* configured somewhere else is a second place to look when the question is
+	* "what happened to my data".
+	*
+	* That placement has a cost worth stating: this document ships in the
+	* framework closure, so this knob needs a published `@camstack/server` while
+	* the four windows beside it (D485) reach a node on `camstack deploy`.
+	*
+	* `retention-model.ts` argued this one must NOT follow a device window,
+	* because the audit trail is the history of the SWEEP and not of the camera.
+	* That argument stands and is untouched — what changes is that 30 days stops
+	* being a constant nobody can reach. `0` keeps it forever. The floor is 1 day
+	* rather than 0-as-delete: an audit log truncated to nothing is precisely the
+	* state in which the next 9.5 GiB leak cannot be explained.
+	*/
+	opsLogRetentionDays: zod.z.number().int().min(0).max(3650).optional()
 });
 /**
 * Which LAYER of the hierarchy is addressed. Absent = the cluster layer.
@@ -36538,6 +36560,14 @@ var LoggingSettingsStateSchema = zod.z.object({
 	channels: zod.z.array(LogChannelDescriptorSchema).readonly(),
 	/** The channels ARMED right now, each with its deadline. */
 	activeChannels: zod.z.array(LogChannelWindowStateSchema).readonly(),
+	/**
+	* The ops-log window in days, as it is in force. `0` = kept forever.
+	*
+	* Reported rather than left to the caller's memory of what it wrote: this is
+	* the value the analytics sweep will actually use, and an operator asking how
+	* long their audit trail lives should not have to infer it from a default.
+	*/
+	opsLogRetentionDays: zod.z.number().int().min(0),
 	persisted: zod.z.boolean()
 });
 var systemCapability = {

package/dist/index.mjs

@@ -36457,7 +36457,29 @@ var LoggingSettingsPatchSchema = z.object({
 	* disarmed the channels it did not mention would make the Levels page and
 	* the Diagnostics page fight over the same value.
 	*/
-	channels: z.array(LogChannelWindowPatchSchema).readonly().optional()
+	channels: z.array(LogChannelWindowPatchSchema).readonly().optional(),
+	/**
+	* How many days the analytics OPS LOG is kept — the audit trail of what
+	* retention actually deleted.
+	*
+	* It lives HERE, on the logging document, and not on the analytics addon's
+	* settings form, on the operator's instruction: every other log-ish window in
+	* this system is configured through this one document, and a retention audit
+	* configured somewhere else is a second place to look when the question is
+	* "what happened to my data".
+	*
+	* That placement has a cost worth stating: this document ships in the
+	* framework closure, so this knob needs a published `@camstack/server` while
+	* the four windows beside it (D485) reach a node on `camstack deploy`.
+	*
+	* `retention-model.ts` argued this one must NOT follow a device window,
+	* because the audit trail is the history of the SWEEP and not of the camera.
+	* That argument stands and is untouched — what changes is that 30 days stops
+	* being a constant nobody can reach. `0` keeps it forever. The floor is 1 day
+	* rather than 0-as-delete: an audit log truncated to nothing is precisely the
+	* state in which the next 9.5 GiB leak cannot be explained.
+	*/
+	opsLogRetentionDays: z.number().int().min(0).max(3650).optional()
 });
 /**
 * Which LAYER of the hierarchy is addressed. Absent = the cluster layer.
@@ -36530,6 +36552,14 @@ var LoggingSettingsStateSchema = z.object({
 	channels: z.array(LogChannelDescriptorSchema).readonly(),
 	/** The channels ARMED right now, each with its deadline. */
 	activeChannels: z.array(LogChannelWindowStateSchema).readonly(),
+	/**
+	* The ops-log window in days, as it is in force. `0` = kept forever.
+	*
+	* Reported rather than left to the caller's memory of what it wrote: this is
+	* the value the analytics sweep will actually use, and an operator asking how
+	* long their audit trail lives should not have to infer it from a default.
+	*/
+	opsLogRetentionDays: z.number().int().min(0),
 	persisted: z.boolean()
 });
 var systemCapability = {

package/package.json

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