@camstack/addon-agent-ui 1.2.108 → 1.2.110

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
Files changed (2) hide show
  1. package/dist/addon.js +49 -9
  2. package/package.json +1 -1
package/dist/addon.js CHANGED
@@ -19044,13 +19044,26 @@ var TrackAudioLabelSchema = object({
19044
19044
  * - `audio` — an audio event on the camera itself that was anomalous for
19045
19045
  * THAT camera, loud, and heard while nothing visual was happening (D62).
19046
19046
  *
19047
+ * - `onboard` — the CAMERA's own firmware, paired with a decoded frame in
19048
+ * that frame's pixel space. A real root detector and a SPATIAL one: its
19049
+ * boxes are the same kind of fact `pipeline`'s are, produced by a different
19050
+ * detector.
19051
+ *
19052
+ * `onboard` was missing here while `DetectionSourceSchema` already had it, so
19053
+ * a persisted onboard track failed `safeParse` on read and came back with NO
19054
+ * source at all — which `isSpatialTrack` then admitted by accident, through the
19055
+ * `undefined` arm rather than by anybody's decision, and which `excludeSources`
19056
+ * could not name.
19057
+ *
19047
19058
  * The spatial subsystems (tracker association, occupancy count, re-id /
19048
19059
  * embedding, resurrection) MUST skip every synthetic source. Test for that
19049
- * with `isSpatialTrack`, which allow-lists `pipeline` — a `!== 'sensor'`
19050
- * check silently readmits every source added after it was written.
19060
+ * with `isSpatialTrack`, which allow-lists the spatial sources explicitly — a
19061
+ * `!== 'sensor'` check silently readmits every source added after it was
19062
+ * written.
19051
19063
  */
19052
19064
  var TrackSourceSchema = _enum([
19053
19065
  "pipeline",
19066
+ "onboard",
19054
19067
  "sensor",
19055
19068
  "audio"
19056
19069
  ]);
@@ -19638,6 +19651,7 @@ var MediaFileKindEnum = _enum([
19638
19651
  "keyFrame",
19639
19652
  "keyFrameSmall",
19640
19653
  "thumbnailSmall",
19654
+ "confirmationCrop",
19641
19655
  "sceneFrame"
19642
19656
  ]);
19643
19657
  /**
@@ -21132,13 +21146,39 @@ var MotionSourceEnum = _enum([
21132
21146
  */
21133
21147
  var MotionSourcesSchema = array(MotionSourceEnum);
21134
21148
  /**
21135
- * Which root detectors a camera runs. Deliberately the SAME vocabulary
21136
- * post-analysis already tags every detection with (`DetectionSource`) rather
21137
- * than a second spelling of the same two ideas the value an operator picks
21138
- * here is the value that comes back on the track, the overlay and the debug
21139
- * row.
21149
+ * Which root detector a camera runs EXACTLY ONE.
21150
+ *
21151
+ * Deliberately the SAME vocabulary post-analysis already tags every detection
21152
+ * with (`DetectionSource`) rather than a second spelling of the same two
21153
+ * ideas: the value an operator picks here is the value that comes back on the
21154
+ * track, the overlay and the debug row.
21155
+ *
21156
+ * ## Why one, and why it is still an array
21157
+ *
21158
+ * Two roots on one camera is a capability nobody asked for and the operator has
21159
+ * since ruled out. It was never free: both planes feed the SAME per-device
21160
+ * stationary registry, both can promote the same parked object, and the two
21161
+ * detectors disagree about the same box by construction — which is the
21162
+ * disagreement D505 had to arbitrate. Removing the case removes the arbitration.
21163
+ *
21164
+ * The ARRAY shape survives because the stored settings and the attach payload
21165
+ * already speak it on every camera of every fleet, and a cap input that
21166
+ * suddenly refuses a stored value makes the camera un-attachable — a fail-closed
21167
+ * in the one direction that costs an operator their cameras. So the wire stays
21168
+ * tolerant and the TYPE is exact: a longer list is truncated to its first
21169
+ * element rather than refused, and `max(1)` is what every consumer can then
21170
+ * rely on.
21171
+ *
21172
+ * AT MOST one, not exactly one. The EMPTY list is a legal, deliberate pick —
21173
+ * a camera an operator left with no root detector — and `planDetectionSources`
21174
+ * has always said so: inventing a root for them is how a default acts without
21175
+ * anybody choosing it. Tightening this to `length(1)` broke that, and the
21176
+ * suite caught it.
21177
+ *
21178
+ * Measured before tightening (2026-09-15, this fleet, 6 h of attaches): 3327
21179
+ * `["pipeline"]` and 2 `["onboard"]`. Not one camera had two.
21140
21180
  */
21141
- var DetectionSourcesSchema = array(DetectionSourceSchema);
21181
+ var DetectionSourcesSchema = preprocess((value) => Array.isArray(value) && value.length > 1 ? value.slice(0, 1) : value, array(DetectionSourceSchema).max(1));
21142
21182
  /**
21143
21183
  * Input shape for `pipeline-runner.reportMotion` cap method. Exported
21144
21184
  * so cap-side consumers (the orchestrator forward, the runner addon's
@@ -39800,7 +39840,7 @@ var AgentUIAddon = class extends BaseAddon {
39800
39840
  capability: adminUiCapability,
39801
39841
  provider: {
39802
39842
  getStaticDir: async () => ({ staticDir: path.resolve(__dirname) }),
39803
- getVersion: async () => ({ version: "1.2.108" })
39843
+ getVersion: async () => ({ version: "1.2.110" })
39804
39844
  }
39805
39845
  }];
39806
39846
  }
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@camstack/addon-agent-ui",
3
- "version": "1.2.108",
3
+ "version": "1.2.110",
4
4
  "description": "Agent UI — lightweight status dashboard served by every agent node",
5
5
  "keywords": [
6
6
  "camstack",