@camstack/addon-ai 0.4.95 → 0.4.96

package/dist/addon.js

@@ -19844,7 +19844,17 @@ var EventDensityBucketSchema = object({
 	bucketStart: number$1(),
 	motion: number$1().int(),
 	object: number$1().int(),
-	audio: number$1().int()
+	audio: number$1().int(),
+	/**
+	* Energy-weighted mean dBFS of the audio events in this bucket — the LEVEL,
+	* as opposed to `audio`, which is their COUNT (D431).
+	*
+	* ABSENT when the bucket holds no audio event. Absence means "nothing was
+	* measured", which is not the same claim as silence, and a lane that cannot
+	* tell them apart paints a quiet hour at full scale — which is exactly what
+	* the count-on-a-level-meter did.
+	*/
+	audioDbfs: number$1().optional()
 });
 /**
 * One camera's row in a `getEventDensityBatch` answer.
@@ -28011,7 +28021,23 @@ var RecordingRangeSchema = object({
 });
 var RecordingAvailabilitySchema = object({
 	deviceId: number$1(),
-	ranges: array(RecordingRangeSchema)
+	ranges: array(RecordingRangeSchema),
+	/**
+	* Every profile this camera has footage in — not only the one `ranges`
+	* describes (D433).
+	*
+	* `ranges` answers for ONE profile by design: the timeline is a single bar,
+	* and enumerating all of them triples the directory reads for a bar that
+	* would look identical. But the answer used to say nothing about that, so a
+	* caller asking "what can I export?" read the single preferred profile as
+	* the only one that exists — on this deployment every camera records `high`
+	* AND `low`, the low tree holding 14 GB for camera 615 alone, and the export
+	* UI could not see it.
+	*
+	* Cheap: it is the same shallow directory read the profile CHOICE already
+	* makes. Ask for a specific profile's ranges with the `profile` input.
+	*/
+	profilesWithFootage: array(string())
 });
 var RecordingDaysSchema = object({
 	deviceId: number$1(),
@@ -28037,7 +28063,11 @@ var RecordingDaysSchema = object({
 var RecordingAvailabilityForDeviceSchema = object({
 	deviceId: number$1(),
 	read: _enum(["read", "unreadable"]),
-	ranges: array(RecordingRangeSchema).readonly()
+	ranges: array(RecordingRangeSchema).readonly(),
+	/** Same field, same meaning, as the singular answer (D433). A row that
+	*  dropped it would tell a grid caller the archive holds one profile.
+	*  Empty on an `'unreadable'` row: nobody looked. */
+	profilesWithFootage: array(string()).readonly()
 });
 /**
 * One camera's row in a `getDaysWithRecordingsBatch` answer. Same rule as
@@ -28327,7 +28357,14 @@ var ReadWindowBytesResultSchema = discriminatedUnion("kind", [object({
 method(object({
 	deviceId: number$1(),
 	fromMs: number$1(),
-	toMs: number$1()
+	toMs: number$1(),
+	/**
+	* Answer for THIS profile instead of the preferred one (D433). Absent
+	* keeps the timeline's behaviour — one bar, one profile, one set of
+	* reads. `profilesWithFootage` on the answer says what may be asked
+	* for.
+	*/
+	profile: string().optional()
 }), RecordingAvailabilitySchema, {
 	kind: "query",
 	auth: "protected"

package/dist/addon.mjs

@@ -19871,7 +19871,17 @@ var EventDensityBucketSchema = object({
 	bucketStart: number$1(),
 	motion: number$1().int(),
 	object: number$1().int(),
-	audio: number$1().int()
+	audio: number$1().int(),
+	/**
+	* Energy-weighted mean dBFS of the audio events in this bucket — the LEVEL,
+	* as opposed to `audio`, which is their COUNT (D431).
+	*
+	* ABSENT when the bucket holds no audio event. Absence means "nothing was
+	* measured", which is not the same claim as silence, and a lane that cannot
+	* tell them apart paints a quiet hour at full scale — which is exactly what
+	* the count-on-a-level-meter did.
+	*/
+	audioDbfs: number$1().optional()
 });
 /**
 * One camera's row in a `getEventDensityBatch` answer.
@@ -28038,7 +28048,23 @@ var RecordingRangeSchema = object({
 });
 var RecordingAvailabilitySchema = object({
 	deviceId: number$1(),
-	ranges: array(RecordingRangeSchema)
+	ranges: array(RecordingRangeSchema),
+	/**
+	* Every profile this camera has footage in — not only the one `ranges`
+	* describes (D433).
+	*
+	* `ranges` answers for ONE profile by design: the timeline is a single bar,
+	* and enumerating all of them triples the directory reads for a bar that
+	* would look identical. But the answer used to say nothing about that, so a
+	* caller asking "what can I export?" read the single preferred profile as
+	* the only one that exists — on this deployment every camera records `high`
+	* AND `low`, the low tree holding 14 GB for camera 615 alone, and the export
+	* UI could not see it.
+	*
+	* Cheap: it is the same shallow directory read the profile CHOICE already
+	* makes. Ask for a specific profile's ranges with the `profile` input.
+	*/
+	profilesWithFootage: array(string())
 });
 var RecordingDaysSchema = object({
 	deviceId: number$1(),
@@ -28064,7 +28090,11 @@ var RecordingDaysSchema = object({
 var RecordingAvailabilityForDeviceSchema = object({
 	deviceId: number$1(),
 	read: _enum(["read", "unreadable"]),
-	ranges: array(RecordingRangeSchema).readonly()
+	ranges: array(RecordingRangeSchema).readonly(),
+	/** Same field, same meaning, as the singular answer (D433). A row that
+	*  dropped it would tell a grid caller the archive holds one profile.
+	*  Empty on an `'unreadable'` row: nobody looked. */
+	profilesWithFootage: array(string()).readonly()
 });
 /**
 * One camera's row in a `getDaysWithRecordingsBatch` answer. Same rule as
@@ -28354,7 +28384,14 @@ var ReadWindowBytesResultSchema = discriminatedUnion("kind", [object({
 method(object({
 	deviceId: number$1(),
 	fromMs: number$1(),
-	toMs: number$1()
+	toMs: number$1(),
+	/**
+	* Answer for THIS profile instead of the preferred one (D433). Absent
+	* keeps the timeline's behaviour — one bar, one profile, one set of
+	* reads. `profilesWithFootage` on the answer says what may be asked
+	* for.
+	*/
+	profile: string().optional()
 }), RecordingAvailabilitySchema, {
 	kind: "query",
 	auth: "protected"

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@camstack/addon-ai",
-  "version": "0.4.95",
+  "version": "0.4.96",
   "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",