@camstack/types 1.2.239 → 1.2.240

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

@@ -465,6 +465,7 @@ export declare const videoclipsCapability: {
         readonly readClipBytes: import("./capability-definition.js").CapabilityMethodSchema<z.ZodObject<{
             deviceId: z.ZodNumber;
             clipId: z.ZodString;
+            provider: z.ZodString;
             profile: z.ZodOptional<z.ZodEnum<{
                 high: "high";
                 mid: "mid";

package/dist/index.js

@@ -27743,6 +27743,23 @@ var videoclipsCapability = {
 			deviceId: zod.z.number(),
 			clipId: zod.z.string().min(1),
 			/**
+			* WHICH provider holds the bytes — the `addonId` a
+			* {@link ClipSourceSchema} row carries. **Required**, for the reason
+			* `listClips` states one method above and for a second one this method
+			* learned the hard way.
+			*
+			* The caller is the stream broker, and the broker lives in
+			* `addon-pipeline` — the same addon that registers the RECORDER's
+			* videoclips provider. With no provider named, the in-process
+			* resolution handed it its own sibling, which implements this method
+			* solely to explain that an analytics visit has no file behind it. So
+			* every onboard clip answered with that sentence, a flash of video and
+			* nothing more, while the SAME call from outside the addon reached the
+			* right provider and returned the bytes (measured on 3628,
+			* 2026-09-21).
+			*/
+			provider: zod.z.string().min(1),
+			/**
 			* Which twin to fetch, on the mapping D549 15 already fixed:
 			* `low | mid` → the sub file, `high` → the main twin. `auto` is not
 			* accepted here for the same reason it is not accepted by

package/dist/index.mjs

@@ -27742,6 +27742,23 @@ var videoclipsCapability = {
 			deviceId: z.number(),
 			clipId: z.string().min(1),
 			/**
+			* WHICH provider holds the bytes — the `addonId` a
+			* {@link ClipSourceSchema} row carries. **Required**, for the reason
+			* `listClips` states one method above and for a second one this method
+			* learned the hard way.
+			*
+			* The caller is the stream broker, and the broker lives in
+			* `addon-pipeline` — the same addon that registers the RECORDER's
+			* videoclips provider. With no provider named, the in-process
+			* resolution handed it its own sibling, which implements this method
+			* solely to explain that an analytics visit has no file behind it. So
+			* every onboard clip answered with that sentence, a flash of video and
+			* nothing more, while the SAME call from outside the addon reached the
+			* right provider and returned the bytes (measured on 3628,
+			* 2026-09-21).
+			*/
+			provider: z.string().min(1),
+			/**
 			* Which twin to fetch, on the mapping D549 15 already fixed:
 			* `low | mid` → the sub file, `high` → the main twin. `auto` is not
 			* accepted here for the same reason it is not accepted by

package/package.json

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