@camstack/addon-agent-ui 1.2.108 → 1.2.109
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.
- package/dist/addon.js +48 -9
- 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
|
|
19050
|
-
* check silently readmits every source added after it was
|
|
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
|
]);
|
|
@@ -21132,13 +21145,39 @@ var MotionSourceEnum = _enum([
|
|
|
21132
21145
|
*/
|
|
21133
21146
|
var MotionSourcesSchema = array(MotionSourceEnum);
|
|
21134
21147
|
/**
|
|
21135
|
-
* Which root
|
|
21136
|
-
*
|
|
21137
|
-
*
|
|
21138
|
-
*
|
|
21139
|
-
*
|
|
21148
|
+
* Which root detector a camera runs — EXACTLY ONE.
|
|
21149
|
+
*
|
|
21150
|
+
* Deliberately the SAME vocabulary post-analysis already tags every detection
|
|
21151
|
+
* with (`DetectionSource`) rather than a second spelling of the same two
|
|
21152
|
+
* ideas: the value an operator picks here is the value that comes back on the
|
|
21153
|
+
* track, the overlay and the debug row.
|
|
21154
|
+
*
|
|
21155
|
+
* ## Why one, and why it is still an array
|
|
21156
|
+
*
|
|
21157
|
+
* Two roots on one camera is a capability nobody asked for and the operator has
|
|
21158
|
+
* since ruled out. It was never free: both planes feed the SAME per-device
|
|
21159
|
+
* stationary registry, both can promote the same parked object, and the two
|
|
21160
|
+
* detectors disagree about the same box by construction — which is the
|
|
21161
|
+
* disagreement D505 had to arbitrate. Removing the case removes the arbitration.
|
|
21162
|
+
*
|
|
21163
|
+
* The ARRAY shape survives because the stored settings and the attach payload
|
|
21164
|
+
* already speak it on every camera of every fleet, and a cap input that
|
|
21165
|
+
* suddenly refuses a stored value makes the camera un-attachable — a fail-closed
|
|
21166
|
+
* in the one direction that costs an operator their cameras. So the wire stays
|
|
21167
|
+
* tolerant and the TYPE is exact: a longer list is truncated to its first
|
|
21168
|
+
* element rather than refused, and `max(1)` is what every consumer can then
|
|
21169
|
+
* rely on.
|
|
21170
|
+
*
|
|
21171
|
+
* AT MOST one, not exactly one. The EMPTY list is a legal, deliberate pick —
|
|
21172
|
+
* a camera an operator left with no root detector — and `planDetectionSources`
|
|
21173
|
+
* has always said so: inventing a root for them is how a default acts without
|
|
21174
|
+
* anybody choosing it. Tightening this to `length(1)` broke that, and the
|
|
21175
|
+
* suite caught it.
|
|
21176
|
+
*
|
|
21177
|
+
* Measured before tightening (2026-09-15, this fleet, 6 h of attaches): 3327
|
|
21178
|
+
* `["pipeline"]` and 2 `["onboard"]`. Not one camera had two.
|
|
21140
21179
|
*/
|
|
21141
|
-
var DetectionSourcesSchema = array(DetectionSourceSchema);
|
|
21180
|
+
var DetectionSourcesSchema = preprocess((value) => Array.isArray(value) && value.length > 1 ? value.slice(0, 1) : value, array(DetectionSourceSchema).max(1));
|
|
21142
21181
|
/**
|
|
21143
21182
|
* Input shape for `pipeline-runner.reportMotion` cap method. Exported
|
|
21144
21183
|
* so cap-side consumers (the orchestrator forward, the runner addon's
|
|
@@ -39800,7 +39839,7 @@ var AgentUIAddon = class extends BaseAddon {
|
|
|
39800
39839
|
capability: adminUiCapability,
|
|
39801
39840
|
provider: {
|
|
39802
39841
|
getStaticDir: async () => ({ staticDir: path.resolve(__dirname) }),
|
|
39803
|
-
getVersion: async () => ({ version: "1.2.
|
|
39842
|
+
getVersion: async () => ({ version: "1.2.109" })
|
|
39804
39843
|
}
|
|
39805
39844
|
}];
|
|
39806
39845
|
}
|