@camstack/types 1.2.200 → 1.2.201

package/dist/capabilities/pipeline-analytics.cap.d.ts

@@ -236,15 +236,28 @@ export type TrackAudioLabel = z.infer<typeof TrackAudioLabelSchema>;
  *  - `audio` — an audio event on the camera itself that was anomalous for
  *    THAT camera, loud, and heard while nothing visual was happening (D62).
  *
+ *  - `onboard` — the CAMERA's own firmware, paired with a decoded frame in
+ *    that frame's pixel space. A real root detector and a SPATIAL one: its
+ *    boxes are the same kind of fact `pipeline`'s are, produced by a different
+ *    detector.
+ *
+ * `onboard` was missing here while `DetectionSourceSchema` already had it, so
+ * a persisted onboard track failed `safeParse` on read and came back with NO
+ * source at all — which `isSpatialTrack` then admitted by accident, through the
+ * `undefined` arm rather than by anybody's decision, and which `excludeSources`
+ * could not name.
+ *
  * The spatial subsystems (tracker association, occupancy count, re-id /
  * embedding, resurrection) MUST skip every synthetic source. Test for that
- * with `isSpatialTrack`, which allow-lists `pipeline` — a `!== 'sensor'`
- * check silently readmits every source added after it was written.
+ * with `isSpatialTrack`, which allow-lists the spatial sources explicitly — a
+ * `!== 'sensor'` check silently readmits every source added after it was
+ * written.
  */
 export declare const TrackSourceSchema: z.ZodEnum<{
     sensor: "sensor";
     pipeline: "pipeline";
     audio: "audio";
+    onboard: "onboard";
 }>;
 export type TrackSource = z.infer<typeof TrackSourceSchema>;
 /**
@@ -431,6 +444,7 @@ declare const TrackSchema: z.ZodObject<{
         sensor: "sensor";
         pipeline: "pipeline";
         audio: "audio";
+        onboard: "onboard";
     }>>;
     firstSeen: z.ZodNumber;
     lastSeen: z.ZodNumber;
@@ -1208,6 +1222,7 @@ declare const RecentTracksQueryInput: z.ZodObject<{
         sensor: "sensor";
         pipeline: "pipeline";
         audio: "audio";
+        onboard: "onboard";
     }>>>;
 }, z.core.$strip>;
 export type RecentTracksQuery = z.infer<typeof RecentTracksQueryInput>;
@@ -1337,6 +1352,7 @@ declare const RecentTracksPageSchema: z.ZodObject<{
             sensor: "sensor";
             pipeline: "pipeline";
             audio: "audio";
+            onboard: "onboard";
         }>>;
         firstSeen: z.ZodNumber;
         lastSeen: z.ZodNumber;
@@ -1876,6 +1892,7 @@ export declare const pipelineAnalyticsCapability: {
                 sensor: "sensor";
                 pipeline: "pipeline";
                 audio: "audio";
+                onboard: "onboard";
             }>>;
             firstSeen: z.ZodNumber;
             lastSeen: z.ZodNumber;
@@ -1985,6 +2002,7 @@ export declare const pipelineAnalyticsCapability: {
                 sensor: "sensor";
                 pipeline: "pipeline";
                 audio: "audio";
+                onboard: "onboard";
             }>>;
             firstSeen: z.ZodNumber;
             lastSeen: z.ZodNumber;
@@ -2107,6 +2125,7 @@ export declare const pipelineAnalyticsCapability: {
                 sensor: "sensor";
                 pipeline: "pipeline";
                 audio: "audio";
+                onboard: "onboard";
             }>>>;
         }, z.core.$strip>, z.ZodReadonly<z.ZodArray<z.ZodObject<{
             retrainStatus: z.ZodOptional<z.ZodEnum<{
@@ -2123,6 +2142,7 @@ export declare const pipelineAnalyticsCapability: {
                 sensor: "sensor";
                 pipeline: "pipeline";
                 audio: "audio";
+                onboard: "onboard";
             }>>;
             firstSeen: z.ZodNumber;
             lastSeen: z.ZodNumber;
@@ -2240,6 +2260,7 @@ export declare const pipelineAnalyticsCapability: {
                 sensor: "sensor";
                 pipeline: "pipeline";
                 audio: "audio";
+                onboard: "onboard";
             }>>>;
         }, z.core.$strip>, z.ZodObject<{
             tracks: z.ZodReadonly<z.ZodArray<z.ZodObject<{
@@ -2257,6 +2278,7 @@ export declare const pipelineAnalyticsCapability: {
                     sensor: "sensor";
                     pipeline: "pipeline";
                     audio: "audio";
+                    onboard: "onboard";
                 }>>;
                 firstSeen: z.ZodNumber;
                 lastSeen: z.ZodNumber;

package/dist/capabilities/pipeline-runner.cap.d.ts

@@ -197,16 +197,42 @@ export declare const MotionSourcesSchema: z.ZodArray<z.ZodEnum<{
 }>>;
 export type MotionSources = z.infer<typeof MotionSourcesSchema>;
 /**
- * Which root detectors a camera runs. Deliberately the SAME vocabulary
- * post-analysis already tags every detection with (`DetectionSource`) rather
- * than a second spelling of the same two ideas — the value an operator picks
- * here is the value that comes back on the track, the overlay and the debug
- * row.
+ * Which root detector a camera runs — EXACTLY ONE.
+ *
+ * Deliberately the SAME vocabulary post-analysis already tags every detection
+ * with (`DetectionSource`) rather than a second spelling of the same two
+ * ideas: the value an operator picks here is the value that comes back on the
+ * track, the overlay and the debug row.
+ *
+ * ## Why one, and why it is still an array
+ *
+ * Two roots on one camera is a capability nobody asked for and the operator has
+ * since ruled out. It was never free: both planes feed the SAME per-device
+ * stationary registry, both can promote the same parked object, and the two
+ * detectors disagree about the same box by construction — which is the
+ * disagreement D505 had to arbitrate. Removing the case removes the arbitration.
+ *
+ * The ARRAY shape survives because the stored settings and the attach payload
+ * already speak it on every camera of every fleet, and a cap input that
+ * suddenly refuses a stored value makes the camera un-attachable — a fail-closed
+ * in the one direction that costs an operator their cameras. So the wire stays
+ * tolerant and the TYPE is exact: a longer list is truncated to its first
+ * element rather than refused, and `max(1)` is what every consumer can then
+ * rely on.
+ *
+ * AT MOST one, not exactly one. The EMPTY list is a legal, deliberate pick —
+ * a camera an operator left with no root detector — and `planDetectionSources`
+ * has always said so: inventing a root for them is how a default acts without
+ * anybody choosing it. Tightening this to `length(1)` broke that, and the
+ * suite caught it.
+ *
+ * Measured before tightening (2026-09-15, this fleet, 6 h of attaches): 3327
+ * `["pipeline"]` and 2 `["onboard"]`. Not one camera had two.
  */
-export declare const DetectionSourcesSchema: z.ZodArray<z.ZodEnum<{
+export declare const DetectionSourcesSchema: z.ZodPreprocess<z.ZodArray<z.ZodEnum<{
     pipeline: "pipeline";
     onboard: "onboard";
-}>>;
+}>>>;
 export type DetectionSources = z.infer<typeof DetectionSourcesSchema>;
 /**
  * Input shape for `pipeline-runner.reportMotion` cap method. Exported
@@ -311,10 +337,10 @@ declare const RunnerCameraConfigSchema: z.ZodObject<{
         analyzer: "analyzer";
         "device-activity": "device-activity";
     }>>>;
-    detectionSources: z.ZodDefault<z.ZodArray<z.ZodEnum<{
+    detectionSources: z.ZodDefault<z.ZodPreprocess<z.ZodArray<z.ZodEnum<{
         pipeline: "pipeline";
         onboard: "onboard";
-    }>>>;
+    }>>>>;
     pipelineEnabled: z.ZodDefault<z.ZodBoolean>;
     steps: z.ZodOptional<z.ZodReadonly<z.ZodArray<z.ZodType<import("./pipeline-executor.cap.js").PipelineStepInputOutput, unknown, z.core.$ZodTypeInternals<import("./pipeline-executor.cap.js").PipelineStepInputOutput, unknown>>>>>;
     audio: z.ZodOptional<z.ZodNullable<z.ZodObject<{
@@ -590,10 +616,10 @@ export declare const pipelineRunnerCapability: {
                 analyzer: "analyzer";
                 "device-activity": "device-activity";
             }>>>;
-            detectionSources: z.ZodDefault<z.ZodArray<z.ZodEnum<{
+            detectionSources: z.ZodDefault<z.ZodPreprocess<z.ZodArray<z.ZodEnum<{
                 pipeline: "pipeline";
                 onboard: "onboard";
-            }>>>;
+            }>>>>;
             pipelineEnabled: z.ZodDefault<z.ZodBoolean>;
             steps: z.ZodOptional<z.ZodReadonly<z.ZodArray<z.ZodType<import("./pipeline-executor.cap.js").PipelineStepInputOutput, unknown, z.core.$ZodTypeInternals<import("./pipeline-executor.cap.js").PipelineStepInputOutput, unknown>>>>>;
             audio: z.ZodOptional<z.ZodNullable<z.ZodObject<{

package/dist/index.js

@@ -19719,13 +19719,26 @@ var TrackAudioLabelSchema = zod.z.object({
 *  - `audio` — an audio event on the camera itself that was anomalous for
 *    THAT camera, loud, and heard while nothing visual was happening (D62).
 *
+*  - `onboard` — the CAMERA's own firmware, paired with a decoded frame in
+*    that frame's pixel space. A real root detector and a SPATIAL one: its
+*    boxes are the same kind of fact `pipeline`'s are, produced by a different
+*    detector.
+*
+* `onboard` was missing here while `DetectionSourceSchema` already had it, so
+* a persisted onboard track failed `safeParse` on read and came back with NO
+* source at all — which `isSpatialTrack` then admitted by accident, through the
+* `undefined` arm rather than by anybody's decision, and which `excludeSources`
+* could not name.
+*
 * The spatial subsystems (tracker association, occupancy count, re-id /
 * embedding, resurrection) MUST skip every synthetic source. Test for that
-* with `isSpatialTrack`, which allow-lists `pipeline` — a `!== 'sensor'`
-* check silently readmits every source added after it was written.
+* with `isSpatialTrack`, which allow-lists the spatial sources explicitly — a
+* `!== 'sensor'` check silently readmits every source added after it was
+* written.
 */
 var TrackSourceSchema = zod.z.enum([
 	"pipeline",
+	"onboard",
 	"sensor",
 	"audio"
 ]);
@@ -22555,13 +22568,39 @@ var MotionSourceEnum = zod.z.enum([
 */
 var MotionSourcesSchema = zod.z.array(MotionSourceEnum);
 /**
-* Which root detectors a camera runs. Deliberately the SAME vocabulary
-* post-analysis already tags every detection with (`DetectionSource`) rather
-* than a second spelling of the same two ideas — the value an operator picks
-* here is the value that comes back on the track, the overlay and the debug
-* row.
+* Which root detector a camera runs — EXACTLY ONE.
+*
+* Deliberately the SAME vocabulary post-analysis already tags every detection
+* with (`DetectionSource`) rather than a second spelling of the same two
+* ideas: the value an operator picks here is the value that comes back on the
+* track, the overlay and the debug row.
+*
+* ## Why one, and why it is still an array
+*
+* Two roots on one camera is a capability nobody asked for and the operator has
+* since ruled out. It was never free: both planes feed the SAME per-device
+* stationary registry, both can promote the same parked object, and the two
+* detectors disagree about the same box by construction — which is the
+* disagreement D505 had to arbitrate. Removing the case removes the arbitration.
+*
+* The ARRAY shape survives because the stored settings and the attach payload
+* already speak it on every camera of every fleet, and a cap input that
+* suddenly refuses a stored value makes the camera un-attachable — a fail-closed
+* in the one direction that costs an operator their cameras. So the wire stays
+* tolerant and the TYPE is exact: a longer list is truncated to its first
+* element rather than refused, and `max(1)` is what every consumer can then
+* rely on.
+*
+* AT MOST one, not exactly one. The EMPTY list is a legal, deliberate pick —
+* a camera an operator left with no root detector — and `planDetectionSources`
+* has always said so: inventing a root for them is how a default acts without
+* anybody choosing it. Tightening this to `length(1)` broke that, and the
+* suite caught it.
+*
+* Measured before tightening (2026-09-15, this fleet, 6 h of attaches): 3327
+* `["pipeline"]` and 2 `["onboard"]`. Not one camera had two.
 */
-var DetectionSourcesSchema = zod.z.array(DetectionSourceSchema);
+var DetectionSourcesSchema = zod.z.preprocess((value) => Array.isArray(value) && value.length > 1 ? value.slice(0, 1) : value, zod.z.array(DetectionSourceSchema).max(1));
 /**
 * Input shape for `pipeline-runner.reportMotion` cap method. Exported
 * so cap-side consumers (the orchestrator forward, the runner addon's

package/dist/index.mjs

@@ -19718,13 +19718,26 @@ var TrackAudioLabelSchema = z.object({
 *  - `audio` — an audio event on the camera itself that was anomalous for
 *    THAT camera, loud, and heard while nothing visual was happening (D62).
 *
+*  - `onboard` — the CAMERA's own firmware, paired with a decoded frame in
+*    that frame's pixel space. A real root detector and a SPATIAL one: its
+*    boxes are the same kind of fact `pipeline`'s are, produced by a different
+*    detector.
+*
+* `onboard` was missing here while `DetectionSourceSchema` already had it, so
+* a persisted onboard track failed `safeParse` on read and came back with NO
+* source at all — which `isSpatialTrack` then admitted by accident, through the
+* `undefined` arm rather than by anybody's decision, and which `excludeSources`
+* could not name.
+*
 * The spatial subsystems (tracker association, occupancy count, re-id /
 * embedding, resurrection) MUST skip every synthetic source. Test for that
-* with `isSpatialTrack`, which allow-lists `pipeline` — a `!== 'sensor'`
-* check silently readmits every source added after it was written.
+* with `isSpatialTrack`, which allow-lists the spatial sources explicitly — a
+* `!== 'sensor'` check silently readmits every source added after it was
+* written.
 */
 var TrackSourceSchema = z.enum([
 	"pipeline",
+	"onboard",
 	"sensor",
 	"audio"
 ]);
@@ -22554,13 +22567,39 @@ var MotionSourceEnum = z.enum([
 */
 var MotionSourcesSchema = z.array(MotionSourceEnum);
 /**
-* Which root detectors a camera runs. Deliberately the SAME vocabulary
-* post-analysis already tags every detection with (`DetectionSource`) rather
-* than a second spelling of the same two ideas — the value an operator picks
-* here is the value that comes back on the track, the overlay and the debug
-* row.
+* Which root detector a camera runs — EXACTLY ONE.
+*
+* Deliberately the SAME vocabulary post-analysis already tags every detection
+* with (`DetectionSource`) rather than a second spelling of the same two
+* ideas: the value an operator picks here is the value that comes back on the
+* track, the overlay and the debug row.
+*
+* ## Why one, and why it is still an array
+*
+* Two roots on one camera is a capability nobody asked for and the operator has
+* since ruled out. It was never free: both planes feed the SAME per-device
+* stationary registry, both can promote the same parked object, and the two
+* detectors disagree about the same box by construction — which is the
+* disagreement D505 had to arbitrate. Removing the case removes the arbitration.
+*
+* The ARRAY shape survives because the stored settings and the attach payload
+* already speak it on every camera of every fleet, and a cap input that
+* suddenly refuses a stored value makes the camera un-attachable — a fail-closed
+* in the one direction that costs an operator their cameras. So the wire stays
+* tolerant and the TYPE is exact: a longer list is truncated to its first
+* element rather than refused, and `max(1)` is what every consumer can then
+* rely on.
+*
+* AT MOST one, not exactly one. The EMPTY list is a legal, deliberate pick —
+* a camera an operator left with no root detector — and `planDetectionSources`
+* has always said so: inventing a root for them is how a default acts without
+* anybody choosing it. Tightening this to `length(1)` broke that, and the
+* suite caught it.
+*
+* Measured before tightening (2026-09-15, this fleet, 6 h of attaches): 3327
+* `["pipeline"]` and 2 `["onboard"]`. Not one camera had two.
 */
-var DetectionSourcesSchema = z.array(DetectionSourceSchema);
+var DetectionSourcesSchema = z.preprocess((value) => Array.isArray(value) && value.length > 1 ? value.slice(0, 1) : value, z.array(DetectionSourceSchema).max(1));
 /**
 * Input shape for `pipeline-runner.reportMotion` cap method. Exported
 * so cap-side consumers (the orchestrator forward, the runner addon's

package/package.json

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