@camstack/addon-osd-manager 0.1.100 → 0.1.102

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/_stub.js CHANGED
@@ -1,5 +1,5 @@
1
1
  import "./virtualExposes-BgZ5Cn7S.mjs";
2
- import "./virtual_mf-REMOTE_ENTRY_ID___mfe_internal__addon_osd_manager_page__remoteEntry_js-DJ2oo3wz.mjs";
2
+ import "./virtual_mf-REMOTE_ENTRY_ID___mfe_internal__addon_osd_manager_page__remoteEntry_js-Cm4fb0xt.mjs";
3
3
  import { _ as e, c as t, d as n, h as r, i, l as a, m as o, p as s, r as c, t as l, u, y as d } from "./_virtual_mf___mfe_internal__addon_osd_manager_page__loadShare__react__loadShare__.js-Bs1t18EM.mjs";
4
4
  import { i as f, o as p, r as m, s as h } from "./responsive-DmRkhonW.mjs";
5
5
  import { d as g, l as _, u as v } from "./use-device-snapshot-B3WRvUHI.mjs";
@@ -1,9 +1,9 @@
1
- import "./virtual_mf-REMOTE_ENTRY_ID___mfe_internal__addon_osd_manager_page__remoteEntry_js-DJ2oo3wz.mjs";
1
+ import "./virtual_mf-REMOTE_ENTRY_ID___mfe_internal__addon_osd_manager_page__remoteEntry_js-Cm4fb0xt.mjs";
2
2
  //#region \0virtual:mf-localSharedImportMap:__mfe_internal__addon_osd_manager_page
3
3
  var e = {
4
4
  "@camstack/sdk": {
5
5
  name: "@camstack/sdk",
6
- version: "1.2.106",
6
+ version: "1.2.108",
7
7
  scope: ["default"],
8
8
  loaded: !1,
9
9
  from: "addon_osd_manager_page",
@@ -18,7 +18,7 @@ var e = {
18
18
  },
19
19
  "@camstack/types": {
20
20
  name: "@camstack/types",
21
- version: "1.2.200",
21
+ version: "1.2.202",
22
22
  scope: ["default"],
23
23
  loaded: !1,
24
24
  from: "addon_osd_manager_page",
@@ -33,7 +33,7 @@ var e = {
33
33
  },
34
34
  "@camstack/ui-library": {
35
35
  name: "@camstack/ui-library",
36
- version: "1.2.165",
36
+ version: "1.2.167",
37
37
  scope: ["default"],
38
38
  loaded: !1,
39
39
  from: "addon_osd_manager_page",
@@ -36,7 +36,7 @@ async function r() {
36
36
  }
37
37
  },
38
38
  "@camstack/types": {
39
- version: "1.2.200",
39
+ version: "1.2.202",
40
40
  scope: "default",
41
41
  shareConfig: {
42
42
  singleton: !0,
@@ -45,7 +45,7 @@ async function r() {
45
45
  }
46
46
  },
47
47
  "@camstack/sdk": {
48
- version: "1.2.106",
48
+ version: "1.2.108",
49
49
  scope: "default",
50
50
  shareConfig: {
51
51
  singleton: !0,
@@ -81,7 +81,7 @@ async function r() {
81
81
  }
82
82
  },
83
83
  "@camstack/ui-library": {
84
- version: "1.2.165",
84
+ version: "1.2.167",
85
85
  scope: "default",
86
86
  shareConfig: {
87
87
  singleton: !0,
package/dist/index.js CHANGED
@@ -22262,13 +22262,26 @@ var TrackAudioLabelSchema = object({
22262
22262
  * - `audio` — an audio event on the camera itself that was anomalous for
22263
22263
  * THAT camera, loud, and heard while nothing visual was happening (D62).
22264
22264
  *
22265
+ * - `onboard` — the CAMERA's own firmware, paired with a decoded frame in
22266
+ * that frame's pixel space. A real root detector and a SPATIAL one: its
22267
+ * boxes are the same kind of fact `pipeline`'s are, produced by a different
22268
+ * detector.
22269
+ *
22270
+ * `onboard` was missing here while `DetectionSourceSchema` already had it, so
22271
+ * a persisted onboard track failed `safeParse` on read and came back with NO
22272
+ * source at all — which `isSpatialTrack` then admitted by accident, through the
22273
+ * `undefined` arm rather than by anybody's decision, and which `excludeSources`
22274
+ * could not name.
22275
+ *
22265
22276
  * The spatial subsystems (tracker association, occupancy count, re-id /
22266
22277
  * embedding, resurrection) MUST skip every synthetic source. Test for that
22267
- * with `isSpatialTrack`, which allow-lists `pipeline` — a `!== 'sensor'`
22268
- * check silently readmits every source added after it was written.
22278
+ * with `isSpatialTrack`, which allow-lists the spatial sources explicitly — a
22279
+ * `!== 'sensor'` check silently readmits every source added after it was
22280
+ * written.
22269
22281
  */
22270
22282
  var TrackSourceSchema = _enum([
22271
22283
  "pipeline",
22284
+ "onboard",
22272
22285
  "sensor",
22273
22286
  "audio"
22274
22287
  ]);
@@ -22856,6 +22869,7 @@ var MediaFileKindEnum = _enum([
22856
22869
  "keyFrame",
22857
22870
  "keyFrameSmall",
22858
22871
  "thumbnailSmall",
22872
+ "confirmationCrop",
22859
22873
  "sceneFrame"
22860
22874
  ]);
22861
22875
  /**
@@ -24986,13 +25000,39 @@ var MotionSourceEnum = _enum([
24986
25000
  */
24987
25001
  var MotionSourcesSchema = array(MotionSourceEnum);
24988
25002
  /**
24989
- * Which root detectors a camera runs. Deliberately the SAME vocabulary
24990
- * post-analysis already tags every detection with (`DetectionSource`) rather
24991
- * than a second spelling of the same two ideas — the value an operator picks
24992
- * here is the value that comes back on the track, the overlay and the debug
24993
- * row.
25003
+ * Which root detector a camera runs — EXACTLY ONE.
25004
+ *
25005
+ * Deliberately the SAME vocabulary post-analysis already tags every detection
25006
+ * with (`DetectionSource`) rather than a second spelling of the same two
25007
+ * ideas: the value an operator picks here is the value that comes back on the
25008
+ * track, the overlay and the debug row.
25009
+ *
25010
+ * ## Why one, and why it is still an array
25011
+ *
25012
+ * Two roots on one camera is a capability nobody asked for and the operator has
25013
+ * since ruled out. It was never free: both planes feed the SAME per-device
25014
+ * stationary registry, both can promote the same parked object, and the two
25015
+ * detectors disagree about the same box by construction — which is the
25016
+ * disagreement D505 had to arbitrate. Removing the case removes the arbitration.
25017
+ *
25018
+ * The ARRAY shape survives because the stored settings and the attach payload
25019
+ * already speak it on every camera of every fleet, and a cap input that
25020
+ * suddenly refuses a stored value makes the camera un-attachable — a fail-closed
25021
+ * in the one direction that costs an operator their cameras. So the wire stays
25022
+ * tolerant and the TYPE is exact: a longer list is truncated to its first
25023
+ * element rather than refused, and `max(1)` is what every consumer can then
25024
+ * rely on.
25025
+ *
25026
+ * AT MOST one, not exactly one. The EMPTY list is a legal, deliberate pick —
25027
+ * a camera an operator left with no root detector — and `planDetectionSources`
25028
+ * has always said so: inventing a root for them is how a default acts without
25029
+ * anybody choosing it. Tightening this to `length(1)` broke that, and the
25030
+ * suite caught it.
25031
+ *
25032
+ * Measured before tightening (2026-09-15, this fleet, 6 h of attaches): 3327
25033
+ * `["pipeline"]` and 2 `["onboard"]`. Not one camera had two.
24994
25034
  */
24995
- var DetectionSourcesSchema = array(DetectionSourceSchema);
25035
+ var DetectionSourcesSchema = preprocess((value) => Array.isArray(value) && value.length > 1 ? value.slice(0, 1) : value, array(DetectionSourceSchema).max(1));
24996
25036
  /**
24997
25037
  * Input shape for `pipeline-runner.reportMotion` cap method. Exported
24998
25038
  * so cap-side consumers (the orchestrator forward, the runner addon's
package/dist/index.mjs CHANGED
@@ -22258,13 +22258,26 @@ var TrackAudioLabelSchema = object({
22258
22258
  * - `audio` — an audio event on the camera itself that was anomalous for
22259
22259
  * THAT camera, loud, and heard while nothing visual was happening (D62).
22260
22260
  *
22261
+ * - `onboard` — the CAMERA's own firmware, paired with a decoded frame in
22262
+ * that frame's pixel space. A real root detector and a SPATIAL one: its
22263
+ * boxes are the same kind of fact `pipeline`'s are, produced by a different
22264
+ * detector.
22265
+ *
22266
+ * `onboard` was missing here while `DetectionSourceSchema` already had it, so
22267
+ * a persisted onboard track failed `safeParse` on read and came back with NO
22268
+ * source at all — which `isSpatialTrack` then admitted by accident, through the
22269
+ * `undefined` arm rather than by anybody's decision, and which `excludeSources`
22270
+ * could not name.
22271
+ *
22261
22272
  * The spatial subsystems (tracker association, occupancy count, re-id /
22262
22273
  * embedding, resurrection) MUST skip every synthetic source. Test for that
22263
- * with `isSpatialTrack`, which allow-lists `pipeline` — a `!== 'sensor'`
22264
- * check silently readmits every source added after it was written.
22274
+ * with `isSpatialTrack`, which allow-lists the spatial sources explicitly — a
22275
+ * `!== 'sensor'` check silently readmits every source added after it was
22276
+ * written.
22265
22277
  */
22266
22278
  var TrackSourceSchema = _enum([
22267
22279
  "pipeline",
22280
+ "onboard",
22268
22281
  "sensor",
22269
22282
  "audio"
22270
22283
  ]);
@@ -22852,6 +22865,7 @@ var MediaFileKindEnum = _enum([
22852
22865
  "keyFrame",
22853
22866
  "keyFrameSmall",
22854
22867
  "thumbnailSmall",
22868
+ "confirmationCrop",
22855
22869
  "sceneFrame"
22856
22870
  ]);
22857
22871
  /**
@@ -24982,13 +24996,39 @@ var MotionSourceEnum = _enum([
24982
24996
  */
24983
24997
  var MotionSourcesSchema = array(MotionSourceEnum);
24984
24998
  /**
24985
- * Which root detectors a camera runs. Deliberately the SAME vocabulary
24986
- * post-analysis already tags every detection with (`DetectionSource`) rather
24987
- * than a second spelling of the same two ideas — the value an operator picks
24988
- * here is the value that comes back on the track, the overlay and the debug
24989
- * row.
24999
+ * Which root detector a camera runs — EXACTLY ONE.
25000
+ *
25001
+ * Deliberately the SAME vocabulary post-analysis already tags every detection
25002
+ * with (`DetectionSource`) rather than a second spelling of the same two
25003
+ * ideas: the value an operator picks here is the value that comes back on the
25004
+ * track, the overlay and the debug row.
25005
+ *
25006
+ * ## Why one, and why it is still an array
25007
+ *
25008
+ * Two roots on one camera is a capability nobody asked for and the operator has
25009
+ * since ruled out. It was never free: both planes feed the SAME per-device
25010
+ * stationary registry, both can promote the same parked object, and the two
25011
+ * detectors disagree about the same box by construction — which is the
25012
+ * disagreement D505 had to arbitrate. Removing the case removes the arbitration.
25013
+ *
25014
+ * The ARRAY shape survives because the stored settings and the attach payload
25015
+ * already speak it on every camera of every fleet, and a cap input that
25016
+ * suddenly refuses a stored value makes the camera un-attachable — a fail-closed
25017
+ * in the one direction that costs an operator their cameras. So the wire stays
25018
+ * tolerant and the TYPE is exact: a longer list is truncated to its first
25019
+ * element rather than refused, and `max(1)` is what every consumer can then
25020
+ * rely on.
25021
+ *
25022
+ * AT MOST one, not exactly one. The EMPTY list is a legal, deliberate pick —
25023
+ * a camera an operator left with no root detector — and `planDetectionSources`
25024
+ * has always said so: inventing a root for them is how a default acts without
25025
+ * anybody choosing it. Tightening this to `length(1)` broke that, and the
25026
+ * suite caught it.
25027
+ *
25028
+ * Measured before tightening (2026-09-15, this fleet, 6 h of attaches): 3327
25029
+ * `["pipeline"]` and 2 `["onboard"]`. Not one camera had two.
24990
25030
  */
24991
- var DetectionSourcesSchema = array(DetectionSourceSchema);
25031
+ var DetectionSourcesSchema = preprocess((value) => Array.isArray(value) && value.length > 1 ? value.slice(0, 1) : value, array(DetectionSourceSchema).max(1));
24992
25032
  /**
24993
25033
  * Input shape for `pipeline-runner.reportMotion` cap method. Exported
24994
25034
  * so cap-side consumers (the orchestrator forward, the runner addon's
@@ -1,2 +1,2 @@
1
- import { n as e, t } from "./virtual_mf-REMOTE_ENTRY_ID___mfe_internal__addon_osd_manager_page__remoteEntry_js-DJ2oo3wz.mjs";
1
+ import { n as e, t } from "./virtual_mf-REMOTE_ENTRY_ID___mfe_internal__addon_osd_manager_page__remoteEntry_js-Cm4fb0xt.mjs";
2
2
  export { t as get, e as init };
@@ -2753,7 +2753,7 @@ async function rr(e) {
2753
2753
  }
2754
2754
  }
2755
2755
  async function ir() {
2756
- return tr ||= rr(() => import("./_virtual_mf-localSharedImportMap___mfe_internal__addon_osd_manager_page-CDVsNfKC.mjs")).catch((e) => {
2756
+ return tr ||= rr(() => import("./_virtual_mf-localSharedImportMap___mfe_internal__addon_osd_manager_page-D7ZVftYR.mjs")).catch((e) => {
2757
2757
  throw tr = void 0, e;
2758
2758
  }), tr;
2759
2759
  }
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@camstack/addon-osd-manager",
3
- "version": "0.1.100",
3
+ "version": "0.1.102",
4
4
  "description": "Binds camera on-screen-display slots to live state and recognitions",
5
5
  "keywords": [
6
6
  "camstack",