@camstack/types 1.2.236 → 1.2.237

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

@@ -6,13 +6,14 @@ import { type InferProvider } from './capability-definition.js';
  *
  * A device-scoped wrapper COLLECTION (D549 decision 2, D554): every provider a
  * camera has is a SOURCE, and they are listed beside each other — never one
- * substituted for another. The DEFAULT provider (`analytics`, registered by
- * the RECORDER — the addon that owns the footage, D560 — `defaultActive: true`)
- * composes the analytics event log (markers + thumbnails, read over `ctx.api`)
- * with the recorder's own `getPlaybackManifest` — a clip is a time-WINDOW over
- * existing footage, never a separate file. A camera that exposes NATIVE onboard
- * clips (Reolink SD card, a hub's storage, HKSV) adds its own catalog
- * ALONGSIDE that one.
+ * substituted for another, and none of them privileged by name. One source,
+ * `analytics`, is registered by the RECORDER — the addon that owns the
+ * footage, D560 — and composes the analytics event log (markers + thumbnails,
+ * read over `ctx.api`) with the recorder's own `getPlaybackManifest`: a clip
+ * is a time-WINDOW over existing footage, never a separate file. A camera that
+ * exposes NATIVE onboard clips (Reolink SD card, a hub's storage, HKSV) adds
+ * its own catalog ALONGSIDE that one. (`defaultActive` above is the CAP's
+ * auto-bind to cameras, not a ranking among these sources — there is none.)
  *
  * The mount stays per-device (`resolveCapMount` → `device-scoped`), and a
  * device's SOURCES are its BINDINGS: `deviceManager.getBindings(deviceId)` is
@@ -22,10 +23,17 @@ import { type InferProvider } from './capability-definition.js';
  * native provider, as the hub-local registration and as an
  * `<addonId>@<nodeId>` one (D554 amended 2026-09-20).
  *
- * `listClips` is asked of ONE provider at a time
- * ({@link videoclipsCapability.methods.listClips} `provider`), defaulting to
- * the bound one, which is CamStack on every camera today. It is NOT a union
- * over everything a camera has: *"l'utilizzatore è uno solo"*.
+ * `listClips` is asked of ONE provider at a time, and NAMING it is REQUIRED
+ * ({@link videoclipsCapability.methods.listClips} `provider`, D554 amended). It is not
+ * a union over everything a camera has: *"l'utilizzatore è uno solo"*. There
+ * is no default, because a collection cap's binding set is DERIVED and PLURAL
+ * (D554 amended, `getBindings` step 0) — "the bound one" does not exist to
+ * resolve to, and the one thing that could take its place is a second
+ * authority naming a provider per camera, which D554 decision 3 rejected.
+ * The pick is a SURFACE's to make, from the {@link ClipSourceSchema} rows it
+ * already holds, and it says which one it made (D569 § 1–3).
+ * {@link videoclipsCapability.methods.listSources} is the method that fans out
+ * — one row per source, by construction.
  * {@link videoclipsCapability.methods.getClipPlayback} dispatches by the
  * source namespace inside the clip id, which is why ids are self-contained.
  *
@@ -259,7 +267,7 @@ export declare const videoclipsCapability: {
             since: z.ZodNumber;
             until: z.ZodNumber;
             limit: z.ZodOptional<z.ZodNumber>;
-            provider: z.ZodOptional<z.ZodString>;
+            provider: z.ZodString;
         }, z.core.$strip>, z.ZodReadonly<z.ZodArray<z.ZodObject<{
             id: z.ZodString;
             source: z.ZodString;

package/dist/index.js

@@ -27164,13 +27164,14 @@ var vectorStoreCapability = {
 *
 * A device-scoped wrapper COLLECTION (D549 decision 2, D554): every provider a
 * camera has is a SOURCE, and they are listed beside each other — never one
-* substituted for another. The DEFAULT provider (`analytics`, registered by
-* the RECORDER — the addon that owns the footage, D560 — `defaultActive: true`)
-* composes the analytics event log (markers + thumbnails, read over `ctx.api`)
-* with the recorder's own `getPlaybackManifest` — a clip is a time-WINDOW over
-* existing footage, never a separate file. A camera that exposes NATIVE onboard
-* clips (Reolink SD card, a hub's storage, HKSV) adds its own catalog
-* ALONGSIDE that one.
+* substituted for another, and none of them privileged by name. One source,
+* `analytics`, is registered by the RECORDER — the addon that owns the
+* footage, D560 — and composes the analytics event log (markers + thumbnails,
+* read over `ctx.api`) with the recorder's own `getPlaybackManifest`: a clip
+* is a time-WINDOW over existing footage, never a separate file. A camera that
+* exposes NATIVE onboard clips (Reolink SD card, a hub's storage, HKSV) adds
+* its own catalog ALONGSIDE that one. (`defaultActive` above is the CAP's
+* auto-bind to cameras, not a ranking among these sources — there is none.)
 *
 * The mount stays per-device (`resolveCapMount` → `device-scoped`), and a
 * device's SOURCES are its BINDINGS: `deviceManager.getBindings(deviceId)` is
@@ -27180,10 +27181,17 @@ var vectorStoreCapability = {
 * native provider, as the hub-local registration and as an
 * `<addonId>@<nodeId>` one (D554 amended 2026-09-20).
 *
-* `listClips` is asked of ONE provider at a time
-* ({@link videoclipsCapability.methods.listClips} `provider`), defaulting to
-* the bound one, which is CamStack on every camera today. It is NOT a union
-* over everything a camera has: *"l'utilizzatore è uno solo"*.
+* `listClips` is asked of ONE provider at a time, and NAMING it is REQUIRED
+* ({@link videoclipsCapability.methods.listClips} `provider`, D554 amended). It is not
+* a union over everything a camera has: *"l'utilizzatore è uno solo"*. There
+* is no default, because a collection cap's binding set is DERIVED and PLURAL
+* (D554 amended, `getBindings` step 0) — "the bound one" does not exist to
+* resolve to, and the one thing that could take its place is a second
+* authority naming a provider per camera, which D554 decision 3 rejected.
+* The pick is a SURFACE's to make, from the {@link ClipSourceSchema} rows it
+* already holds, and it says which one it made (D569 § 1–3).
+* {@link videoclipsCapability.methods.listSources} is the method that fans out
+* — one row per source, by construction.
 * {@link videoclipsCapability.methods.getClipPlayback} dispatches by the
 * source namespace inside the clip id, which is why ids are self-contained.
 *
@@ -27555,22 +27563,40 @@ var videoclipsCapability = {
 			limit: zod.z.number().int().positive().optional(),
 			/**
 			* WHICH provider to ask — the `addonId` a {@link ClipSourceSchema} row
-			* carries, never a source id and never a list.
+			* carries, never a source id and never a list. **Required** (D554 amended).
 			*
-			* Absent means the device's BOUND provider, which is CamStack on every
-			* camera today because that is what `deviceManager.getBindings`
-			* answers with. A provider the device is not bound to is refused by
-			* name rather than answered by another one (D552's
-			* `rejectUnresolvedAddonPin` rule).
+			* A provider the device is not bound to is refused by name rather than
+			* answered by another one (D552's `rejectUnresolvedAddonPin` rule).
+			*
+			* It was optional, documented as "absent means the device's BOUND
+			* provider, which is CamStack on every camera". No code implemented
+			* that. Measured on the live hub 2026-09-20 — device 592, bound to
+			* `recorder` AND `provider-reolink` — a bare call with `limit: 3`
+			* answered SIX rows, three from each source, merged newest-first:
+			* `device-collection-dispatch.ts` simply left the fan-out un-narrowed,
+			* so absence bought the union this method exists not to be, and
+			* `limit` meant `limit × sources`.
+			*
+			* There is nothing to restore the default to. `getBindings` answers a
+			* collection cap with a DERIVED, PLURAL set (D554 amended, step 0);
+			* `setWrapperActive` — the singleton authority that could name one —
+			* throws for a collection cap by design. Naming CamStack here instead
+			* would privilege one addon by id inside a surface whose premise is
+			* that sources are peers, and would be wrong on the first camera with
+			* no recorder binding. So absence is REFUSED, in the schema, where the
+			* generated types make it unomittable rather than merely discouraged.
+			*
+			* The default belongs to the SURFACE, which has the `listSources` rows
+			* and can say which one it picked (D569 § 1–3; the viewer already
+			* always sends this).
 			*
 			* It replaced `sources?: string[]`, a VIEW filter over source ids that
 			* assumed the answer was a fan-out over everything a camera has. The
-			* operator settled otherwise on 2026-09-20 — *"il get videoclips
-			* prendere un provider opzionale, di default va su camstack"*,
-			* *"l'utilizzatore è uno solo"* — so the list is asked of one provider
-			* at a time and there is nothing to filter out of it.
+			* operator settled otherwise on 2026-09-20 — *"l'utilizzatore è uno
+			* solo"* — so the list is asked of one provider at a time and there is
+			* nothing to filter out of it.
 			*/
-			provider: zod.z.string().optional()
+			provider: zod.z.string().min(1)
 		}), zod.z.array(ClipSchema).readonly(), {
 			kind: "query",
 			auth: "protected"

package/dist/index.mjs

@@ -27163,13 +27163,14 @@ var vectorStoreCapability = {
 *
 * A device-scoped wrapper COLLECTION (D549 decision 2, D554): every provider a
 * camera has is a SOURCE, and they are listed beside each other — never one
-* substituted for another. The DEFAULT provider (`analytics`, registered by
-* the RECORDER — the addon that owns the footage, D560 — `defaultActive: true`)
-* composes the analytics event log (markers + thumbnails, read over `ctx.api`)
-* with the recorder's own `getPlaybackManifest` — a clip is a time-WINDOW over
-* existing footage, never a separate file. A camera that exposes NATIVE onboard
-* clips (Reolink SD card, a hub's storage, HKSV) adds its own catalog
-* ALONGSIDE that one.
+* substituted for another, and none of them privileged by name. One source,
+* `analytics`, is registered by the RECORDER — the addon that owns the
+* footage, D560 — and composes the analytics event log (markers + thumbnails,
+* read over `ctx.api`) with the recorder's own `getPlaybackManifest`: a clip
+* is a time-WINDOW over existing footage, never a separate file. A camera that
+* exposes NATIVE onboard clips (Reolink SD card, a hub's storage, HKSV) adds
+* its own catalog ALONGSIDE that one. (`defaultActive` above is the CAP's
+* auto-bind to cameras, not a ranking among these sources — there is none.)
 *
 * The mount stays per-device (`resolveCapMount` → `device-scoped`), and a
 * device's SOURCES are its BINDINGS: `deviceManager.getBindings(deviceId)` is
@@ -27179,10 +27180,17 @@ var vectorStoreCapability = {
 * native provider, as the hub-local registration and as an
 * `<addonId>@<nodeId>` one (D554 amended 2026-09-20).
 *
-* `listClips` is asked of ONE provider at a time
-* ({@link videoclipsCapability.methods.listClips} `provider`), defaulting to
-* the bound one, which is CamStack on every camera today. It is NOT a union
-* over everything a camera has: *"l'utilizzatore è uno solo"*.
+* `listClips` is asked of ONE provider at a time, and NAMING it is REQUIRED
+* ({@link videoclipsCapability.methods.listClips} `provider`, D554 amended). It is not
+* a union over everything a camera has: *"l'utilizzatore è uno solo"*. There
+* is no default, because a collection cap's binding set is DERIVED and PLURAL
+* (D554 amended, `getBindings` step 0) — "the bound one" does not exist to
+* resolve to, and the one thing that could take its place is a second
+* authority naming a provider per camera, which D554 decision 3 rejected.
+* The pick is a SURFACE's to make, from the {@link ClipSourceSchema} rows it
+* already holds, and it says which one it made (D569 § 1–3).
+* {@link videoclipsCapability.methods.listSources} is the method that fans out
+* — one row per source, by construction.
 * {@link videoclipsCapability.methods.getClipPlayback} dispatches by the
 * source namespace inside the clip id, which is why ids are self-contained.
 *
@@ -27554,22 +27562,40 @@ var videoclipsCapability = {
 			limit: z.number().int().positive().optional(),
 			/**
 			* WHICH provider to ask — the `addonId` a {@link ClipSourceSchema} row
-			* carries, never a source id and never a list.
+			* carries, never a source id and never a list. **Required** (D554 amended).
 			*
-			* Absent means the device's BOUND provider, which is CamStack on every
-			* camera today because that is what `deviceManager.getBindings`
-			* answers with. A provider the device is not bound to is refused by
-			* name rather than answered by another one (D552's
-			* `rejectUnresolvedAddonPin` rule).
+			* A provider the device is not bound to is refused by name rather than
+			* answered by another one (D552's `rejectUnresolvedAddonPin` rule).
+			*
+			* It was optional, documented as "absent means the device's BOUND
+			* provider, which is CamStack on every camera". No code implemented
+			* that. Measured on the live hub 2026-09-20 — device 592, bound to
+			* `recorder` AND `provider-reolink` — a bare call with `limit: 3`
+			* answered SIX rows, three from each source, merged newest-first:
+			* `device-collection-dispatch.ts` simply left the fan-out un-narrowed,
+			* so absence bought the union this method exists not to be, and
+			* `limit` meant `limit × sources`.
+			*
+			* There is nothing to restore the default to. `getBindings` answers a
+			* collection cap with a DERIVED, PLURAL set (D554 amended, step 0);
+			* `setWrapperActive` — the singleton authority that could name one —
+			* throws for a collection cap by design. Naming CamStack here instead
+			* would privilege one addon by id inside a surface whose premise is
+			* that sources are peers, and would be wrong on the first camera with
+			* no recorder binding. So absence is REFUSED, in the schema, where the
+			* generated types make it unomittable rather than merely discouraged.
+			*
+			* The default belongs to the SURFACE, which has the `listSources` rows
+			* and can say which one it picked (D569 § 1–3; the viewer already
+			* always sends this).
 			*
 			* It replaced `sources?: string[]`, a VIEW filter over source ids that
 			* assumed the answer was a fan-out over everything a camera has. The
-			* operator settled otherwise on 2026-09-20 — *"il get videoclips
-			* prendere un provider opzionale, di default va su camstack"*,
-			* *"l'utilizzatore è uno solo"* — so the list is asked of one provider
-			* at a time and there is nothing to filter out of it.
+			* operator settled otherwise on 2026-09-20 — *"l'utilizzatore è uno
+			* solo"* — so the list is asked of one provider at a time and there is
+			* nothing to filter out of it.
 			*/
-			provider: z.string().optional()
+			provider: z.string().min(1)
 		}), z.array(ClipSchema).readonly(), {
 			kind: "query",
 			auth: "protected"

package/package.json

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