@camstack/addon-osd-manager 0.1.99 → 0.1.101

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 (19) hide show
  1. package/dist/{MotionZonesSettings-BSQaXYXm.mjs → MotionZonesSettings-BmqapaTP.mjs} +2 -2
  2. package/dist/{PrivacyMaskSettings-BsOmMQ3G.mjs → PrivacyMaskSettings-C_ENwx9Q.mjs} +4 -4
  3. package/dist/{SceneMonitorEditor-tekjBVAD.mjs → SceneMonitorEditor-G-kQWq6o.mjs} +3 -3
  4. package/dist/_stub.js +11 -11
  5. package/dist/{_virtual_mf-localSharedImportMap___mfe_internal__addon_osd_manager_page-ZjOQCsZZ.mjs → _virtual_mf-localSharedImportMap___mfe_internal__addon_osd_manager_page-COWDhvlO.mjs} +4 -4
  6. package/dist/_virtual_mf___mfe_internal__addon_osd_manager_page__loadShare___mf_0_camstack_mf_1_types__loadShare__.js-Dc2jiuWZ.mjs +26 -0
  7. package/dist/addon-osd-manager.css +1 -1
  8. package/dist/{hostInit-B8PUHWlr.mjs → hostInit-BT0t8O6C.mjs} +3 -3
  9. package/dist/index.js +403 -13
  10. package/dist/index.mjs +403 -13
  11. package/dist/{player-overlays-CU2Q1FOt.mjs → player-overlays-BXcJYuYX.mjs} +1 -1
  12. package/dist/remoteEntry.js +1 -1
  13. package/dist/{responsive-CREvujgj.mjs → responsive-DmRkhonW.mjs} +1 -1
  14. package/dist/{square-D4G_-ewV.mjs → square-LLImpVvg.mjs} +1 -1
  15. package/dist/{trash-2-UEtRGymk.mjs → trash-2-DnVYkte0.mjs} +1 -1
  16. package/dist/{use-device-snapshot-DiWS-JDe.mjs → use-device-snapshot-B3WRvUHI.mjs} +1 -1
  17. package/dist/{virtual_mf-REMOTE_ENTRY_ID___mfe_internal__addon_osd_manager_page__remoteEntry_js-m9QQayT8.mjs → virtual_mf-REMOTE_ENTRY_ID___mfe_internal__addon_osd_manager_page__remoteEntry_js-DS2cFwR0.mjs} +1 -1
  18. package/package.json +2 -2
  19. package/dist/_virtual_mf___mfe_internal__addon_osd_manager_page__loadShare___mf_0_camstack_mf_1_types__loadShare__.js-BR1kX9U-.mjs +0 -26
package/dist/index.mjs CHANGED
@@ -5359,7 +5359,7 @@ var ZodIssueCode = {
5359
5359
  var ZodFirstPartyTypeKind;
5360
5360
  ZodFirstPartyTypeKind || (ZodFirstPartyTypeKind = {});
5361
5361
  //#endregion
5362
- //#region ../types/dist/sleep-DEuj7E3j.mjs
5362
+ //#region ../types/dist/sleep-BDR76Ykr.mjs
5363
5363
  /**
5364
5364
  * The audio chunk plane's byte format, and the ONE expansion from a coded
5365
5365
  * window to float samples (D455).
@@ -12079,6 +12079,21 @@ var streamSignalsCapability = {
12079
12079
  mode: "singleton",
12080
12080
  deviceTypes: Object.values(DeviceType),
12081
12081
  runtimeState: StreamSignalsStatusSchema,
12082
+ /**
12083
+ * Runtime-state durability: **session** — mirrored in RAM, never written.
12084
+ *
12085
+ * The slice holds what the DEVICE says it can emit. That is a probed fact,
12086
+ * not an operator choice: the provider re-declares it on every registration,
12087
+ * so losing it loses nothing and persisting it would freeze an answer the
12088
+ * camera is entitled to change. Measured the same day on the sibling case —
12089
+ * `native-object-detection.supportedClasses` was persisted, and a firmware
12090
+ * class the camera really detected stayed missing for the life of the row
12091
+ * because the fix could not reach it.
12092
+ *
12093
+ * See `RuntimeStateDurability`. Enforced by
12094
+ * `scripts/check-runtime-state-durability.ts`.
12095
+ */
12096
+ durability: "session",
12082
12097
  methods: {
12083
12098
  /**
12084
12099
  * What this device can emit. Empty is a valid and common answer — most
@@ -20663,6 +20678,48 @@ var NcAlarmConfigSchema = object({
20663
20678
  settings: NcAlarmSettingsSchema,
20664
20679
  coverage: array(NcAlarmModeCoverageSchema)
20665
20680
  });
20681
+ /**
20682
+ * ONE rule's demand on ONE camera's clip ring.
20683
+ *
20684
+ * A rule, not a camera: the broker takes the MAX over the asks that reach a
20685
+ * camera, so the answer stays a faithful description of the rules and the
20686
+ * bounding (the byte budget, the broker's own ceiling) stays where the cost
20687
+ * lives. A camera that appears in no ask is being told **nothing** — which is
20688
+ * a different thing from never having been told, and only the envelope
20689
+ * (`rulesLoaded`) can tell those apart.
20690
+ */
20691
+ var NcClipRetentionAskSchema = object({
20692
+ /**
20693
+ * The camera this ask is about. **Absent = every camera**, which is what a
20694
+ * rule with no `conditions.devices` means: it can fire anywhere, so it is
20695
+ * asking everywhere.
20696
+ */
20697
+ deviceId: number().int().nonnegative().optional(),
20698
+ /** Seconds of history the rule needs held for it. Never zero — a rule that
20699
+ * needs nothing produces no ask at all. */
20700
+ seconds: number().min(0).max(60),
20701
+ /** The profile the rule cuts from, when it named one. Absent = the cheapest
20702
+ * assigned, which is what the cut defaults to. */
20703
+ profile: CamProfileSchema.optional(),
20704
+ /** Who is asking — so a retention the operator did not expect names a rule. */
20705
+ ruleId: string(),
20706
+ ruleName: string(),
20707
+ /** Why this many seconds: the rule's own window, or the occupancy ceiling. */
20708
+ reason: _enum(["window", "occupancy"])
20709
+ });
20710
+ /**
20711
+ * The whole answer, with the one bit that keeps absence from reading as zero.
20712
+ *
20713
+ * `rulesLoaded` is false until the rule ledger has completed a load at least
20714
+ * once. A centre that is up but has not read its rules yet answers with an
20715
+ * empty ask list that means nothing at all — applying it would drop every
20716
+ * camera's ring to zero for the first events after a restart, which is the
20717
+ * footage this mechanism exists to keep.
20718
+ */
20719
+ var NcClipRetentionPlanSchema = object({
20720
+ rulesLoaded: boolean(),
20721
+ asks: array(NcClipRetentionAskSchema).readonly()
20722
+ });
20666
20723
  var notificationRulesCapability = {
20667
20724
  name: "notification-rules",
20668
20725
  scope: "system",
@@ -20695,6 +20752,23 @@ var notificationRulesCapability = {
20695
20752
  auth: "admin"
20696
20753
  }),
20697
20754
  /**
20755
+ * WHAT THE RULES ACTUALLY ASK the stream broker to retain, per camera.
20756
+ *
20757
+ * The notification centre owns the rules, so it is the only thing that can
20758
+ * say how much history a camera's notifications will ever reach back for.
20759
+ * Before this the broker guessed — a flat minute on every camera — and
20760
+ * learned the PROFILE reactively, after the first clip had already been cut
20761
+ * from the wrong one. This is the same ask stated once, in front.
20762
+ *
20763
+ * A QUERY, pulled by each node's broker, not a push: brokers are per node
20764
+ * (a camera's ring lives wherever its stream is ingested) while this cap is
20765
+ * a singleton, so a push would have to enumerate the cluster. The pull also
20766
+ * makes the failure mode right — a broker that cannot reach the centre
20767
+ * keeps the plan it has, and a plan that has never arrived is UNKNOWN
20768
+ * rather than empty (D49: a read that fails changes nothing).
20769
+ */
20770
+ getClipRetentionAsks: method(object({}), NcClipRetentionPlanSchema, { auth: "admin" }),
20771
+ /**
20698
20772
  * PERMANENT per-camera mute — the notifications half of the per-camera
20699
20773
  * function switch group ([D61](../../../../docs/decisions/adr-0067.md)).
20700
20774
  *
@@ -22184,13 +22258,26 @@ var TrackAudioLabelSchema = object({
22184
22258
  * - `audio` — an audio event on the camera itself that was anomalous for
22185
22259
  * THAT camera, loud, and heard while nothing visual was happening (D62).
22186
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
+ *
22187
22272
  * The spatial subsystems (tracker association, occupancy count, re-id /
22188
22273
  * embedding, resurrection) MUST skip every synthetic source. Test for that
22189
- * with `isSpatialTrack`, which allow-lists `pipeline` — a `!== 'sensor'`
22190
- * 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.
22191
22277
  */
22192
22278
  var TrackSourceSchema = _enum([
22193
22279
  "pipeline",
22280
+ "onboard",
22194
22281
  "sensor",
22195
22282
  "audio"
22196
22283
  ]);
@@ -23573,6 +23660,33 @@ var RunReplayFrameProcessorResultSchema = object({ tracks: array(object({
23573
23660
  * solid is this track", cheaper than re-deriving it from a trajectory. */
23574
23661
  framesMatched: number().int()
23575
23662
  })).readonly() });
23663
+ /**
23664
+ * The long-term series a camera produces. A closed union so a typo cannot
23665
+ * invent one, and the ONE declaration of it — the addon's `AnalyticsLtsSeries`
23666
+ * is an alias of this, not a second list.
23667
+ */
23668
+ var AnalyticsLtsSeriesSchema = _enum([
23669
+ "motion",
23670
+ "audio-dbfs",
23671
+ "battery",
23672
+ "occupancy"
23673
+ ]);
23674
+ /**
23675
+ * One closed 5-minute bucket of a long-term series.
23676
+ *
23677
+ * `samples` is how many readings the bucket folded — it is the ACTIVITY for a
23678
+ * series like `motion`, and the confidence for one like `occupancy`. A bucket
23679
+ * that exists at all was measured; a bucket that is absent was not, which is a
23680
+ * different claim from zero and the reason this is a sparse series.
23681
+ */
23682
+ var LtsBucketSchema = object({
23683
+ scope: string(),
23684
+ bucketStart: number().int(),
23685
+ samples: number().int().nonnegative(),
23686
+ sum: number(),
23687
+ min: number(),
23688
+ max: number()
23689
+ });
23576
23690
  var pipelineAnalyticsCapability = {
23577
23691
  name: "pipeline-analytics",
23578
23692
  scope: "device",
@@ -23716,6 +23830,30 @@ var pipelineAnalyticsCapability = {
23716
23830
  getKeyEventsBatch: method(KeyEventBatchQueryInput, array(KeyEventsForDeviceSchema).readonly()),
23717
23831
  /** Server-side bucketed event counts for the 24-hour timeline.
23718
23832
  * Returns one entry per non-empty bucket; empty buckets are omitted. */
23833
+ /**
23834
+ * Read one camera's long-term series — 5-minute buckets, kept for a year.
23835
+ *
23836
+ * This is the history surface for every chart that used to be served from a
23837
+ * RAM ring: the ring dies with the process, cannot answer about last night,
23838
+ * and had a 60-minute horizon, while these rows are ~60 bytes and already
23839
+ * written. `scope` is the series' own dimension — for `occupancy`, spell it
23840
+ * with {@link occupancyScope} rather than by hand, and omit it to get every
23841
+ * scope back at once (the caller then groups with
23842
+ * {@link parseOccupancyScope}).
23843
+ *
23844
+ * Bounds are inclusive on the BUCKET START, so a range that ends mid-bucket
23845
+ * still returns the bucket it lands in — the alternative is a chart whose
23846
+ * last column silently disappears for five minutes out of every five.
23847
+ */
23848
+ readLongTermSeries: method(object({
23849
+ deviceId: number(),
23850
+ series: AnalyticsLtsSeriesSchema,
23851
+ /** Omit for EVERY scope of this series in the range. */
23852
+ scope: string().optional(),
23853
+ from: number(),
23854
+ to: number(),
23855
+ limit: number().int().positive().optional()
23856
+ }), array(LtsBucketSchema).readonly()),
23719
23857
  getEventDensity: method(object({
23720
23858
  deviceId: number(),
23721
23859
  since: number(),
@@ -24857,6 +24995,40 @@ var MotionSourceEnum = _enum([
24857
24995
  */
24858
24996
  var MotionSourcesSchema = array(MotionSourceEnum);
24859
24997
  /**
24998
+ * Which root detector a camera runs — EXACTLY ONE.
24999
+ *
25000
+ * Deliberately the SAME vocabulary post-analysis already tags every detection
25001
+ * with (`DetectionSource`) rather than a second spelling of the same two
25002
+ * ideas: the value an operator picks here is the value that comes back on the
25003
+ * track, the overlay and the debug row.
25004
+ *
25005
+ * ## Why one, and why it is still an array
25006
+ *
25007
+ * Two roots on one camera is a capability nobody asked for and the operator has
25008
+ * since ruled out. It was never free: both planes feed the SAME per-device
25009
+ * stationary registry, both can promote the same parked object, and the two
25010
+ * detectors disagree about the same box by construction — which is the
25011
+ * disagreement D505 had to arbitrate. Removing the case removes the arbitration.
25012
+ *
25013
+ * The ARRAY shape survives because the stored settings and the attach payload
25014
+ * already speak it on every camera of every fleet, and a cap input that
25015
+ * suddenly refuses a stored value makes the camera un-attachable — a fail-closed
25016
+ * in the one direction that costs an operator their cameras. So the wire stays
25017
+ * tolerant and the TYPE is exact: a longer list is truncated to its first
25018
+ * element rather than refused, and `max(1)` is what every consumer can then
25019
+ * rely on.
25020
+ *
25021
+ * AT MOST one, not exactly one. The EMPTY list is a legal, deliberate pick —
25022
+ * a camera an operator left with no root detector — and `planDetectionSources`
25023
+ * has always said so: inventing a root for them is how a default acts without
25024
+ * anybody choosing it. Tightening this to `length(1)` broke that, and the
25025
+ * suite caught it.
25026
+ *
25027
+ * Measured before tightening (2026-09-15, this fleet, 6 h of attaches): 3327
25028
+ * `["pipeline"]` and 2 `["onboard"]`. Not one camera had two.
25029
+ */
25030
+ var DetectionSourcesSchema = preprocess((value) => Array.isArray(value) && value.length > 1 ? value.slice(0, 1) : value, array(DetectionSourceSchema).max(1));
25031
+ /**
24860
25032
  * Input shape for `pipeline-runner.reportMotion` cap method. Exported
24861
25033
  * so cap-side consumers (the orchestrator forward, the runner addon's
24862
25034
  * cap implementation, tests) can reuse the type instead of redeclaring
@@ -25007,6 +25179,35 @@ var RunnerCameraConfigSchema = object({
25007
25179
  * events; the orchestrator forwards to `reportMotion`.
25008
25180
  */
25009
25181
  motionSources: MotionSourcesSchema.default(["analyzer"]),
25182
+ /**
25183
+ * WHICH root detector runs for this camera. The detection counterpart of
25184
+ * {@link motionSources}, same shape and same discipline: a per-camera list
25185
+ * of sources the system understands, vendor-agnostic, owned here.
25186
+ *
25187
+ * - `pipeline` — this runner's own root step on decoded pixels (`steps`).
25188
+ * - `onboard` — the CAMERA's own detector, admitted only when it is named
25189
+ * here. Its boxes reach post-analysis on the same
25190
+ * `PipelineInferenceResult` payload as the pipeline's, so an onboard-born
25191
+ * track gets the same tracker, the same overlay and the same detail
25192
+ * subtree (face / plate / embedding).
25193
+ *
25194
+ * `['onboard']` alone is the REPLACEMENT: this runner's root step does not
25195
+ * run, and that is where a camera with a usable onboard detector buys back
25196
+ * its share of the accelerator. It saves the root inference, not the decode
25197
+ * — the detail subtree still needs pixels to cut crops from.
25198
+ *
25199
+ * A camera whose onboard detections carry no geometry cannot serve as a root
25200
+ * step at all (there is nothing to track), and the cap that knows this says
25201
+ * so on `native-object-detection.getOptions().geometry`. On Reolink that is
25202
+ * every battery camera: the boxes ride a sub-stream a battery camera never
25203
+ * attaches, so such a camera stays on `['pipeline']` and its onboard AI is
25204
+ * worth exactly what it already is — a wake signal with a class.
25205
+ *
25206
+ * Defaults to `['pipeline']`, which is byte-for-byte today's behaviour: a
25207
+ * vendor never turns a detector on for the operator, and neither does a
25208
+ * default.
25209
+ */
25210
+ detectionSources: DetectionSourcesSchema.default(["pipeline"]),
25010
25211
  pipelineEnabled: boolean().default(true),
25011
25212
  /** Ordered tree of video steps. Absent → runner skips video detection. */
25012
25213
  steps: array(PipelineStepInputSchema).readonly().optional(),
@@ -25202,6 +25403,18 @@ var RunnerLocalMetricsSchema = object({
25202
25403
  * runner has zero knowledge of other agents, no global state, and never
25203
25404
  * makes assignment decisions itself.
25204
25405
  */
25406
+ /**
25407
+ * Why a runner declined to look at a camera out of band. Named rather than a
25408
+ * bare `false`: a camera asleep on battery (D173), one attached elsewhere, one
25409
+ * already mid-session and one already bursting are four different facts, and a
25410
+ * caller told only "no" cannot tell a protection from a bug.
25411
+ */
25412
+ var OccupancyBurstRefusalSchema = _enum([
25413
+ "not-attached",
25414
+ "battery-asleep",
25415
+ "not-watching",
25416
+ "already-bursting"
25417
+ ]);
25205
25418
  var pipelineRunnerCapability = {
25206
25419
  name: "pipeline-runner",
25207
25420
  scope: "system",
@@ -25238,6 +25451,50 @@ var pipelineRunnerCapability = {
25238
25451
  /** List the deviceIds currently attached to this runner. */
25239
25452
  getLocalCameras: method(_void(), array(number()).readonly()),
25240
25453
  /**
25454
+ * Look at a camera NOW, out of band, because something just happened that
25455
+ * only a fresh look can settle.
25456
+ *
25457
+ * The periodic recheck (`occupancyRecheckSec`, 300 s) exists to watch a
25458
+ * still scene. It is the wrong instrument for a QUESTION that has just been
25459
+ * asked: on device 617 a parked car's departure was observed, a departure
25460
+ * strike was armed — and then the motion session ended, the strike decayed
25461
+ * after its 30 s TTL, and the next periodic look arrived up to five minutes
25462
+ * later with nothing left to confirm. Every one of those departures was
25463
+ * settled by the entry ageing out 6 to 10 minutes of observed time later,
25464
+ * and the notification's clip showed an empty space with nothing leaving
25465
+ * it.
25466
+ *
25467
+ * Two numbers make the ask specific, and a caller that ignores them wastes
25468
+ * the burst: a confirmation must land at least
25469
+ * `DEPARTURE_CONFIRM_MIN_GAP_MS` (3 s) after the read that armed the
25470
+ * strike — before that it is the same optical event and is refused — and
25471
+ * `DEPARTURE_ABSENCE_MIN_READS` (5) consecutive unassociated frames are
25472
+ * needed, while `occupancyRecheckFrames` defaults to FOUR. A burst of four
25473
+ * can never confirm an absence; that is why two periodic looks were always
25474
+ * required.
25475
+ *
25476
+ * The runner answers whether it actually started one. A refusal is NAMED,
25477
+ * never a silent `false`: a camera that is asleep on battery (D173 — this
25478
+ * must not become a self-initiated wake), detached, mid-session or already
25479
+ * bursting are four different facts, and a caller told only "no" cannot
25480
+ * tell a protection from a bug.
25481
+ */
25482
+ requestOccupancyBurst: method(object({
25483
+ deviceId: number(),
25484
+ /** How many frames to collect. The caller sizes this against what its
25485
+ * own confirmation needs; the runner clamps it to the field's range. */
25486
+ frames: number().int().positive().optional(),
25487
+ /** Why, for the log. A burst nobody can attribute is a cost nobody can
25488
+ * defend — the periodic one at least has a timer to point at. */
25489
+ reason: string()
25490
+ }), object({
25491
+ started: boolean(),
25492
+ refusedBecause: OccupancyBurstRefusalSchema.optional()
25493
+ }), {
25494
+ auth: "admin",
25495
+ kind: "mutation"
25496
+ }),
25497
+ /**
25241
25498
  * Best-effort NATIVE-resolution crop of a retention-ring frame. Given the
25242
25499
  * `FrameHandle` that rode an inference-result event and a normalized `bbox`,
25243
25500
  * the runner asks the decode worker still holding that frame's NATIVE
@@ -33656,11 +33913,46 @@ var NativeObjectDetectionStatusSchema = object({
33656
33913
  supportedClasses: array(NativeObjectClassEnum).readonly(),
33657
33914
  /**
33658
33915
  * Whether forwarding of onboard AI detections is enabled for this device.
33659
- * Default FALSE (opt-in, cold-start) — onboard AI pushes are noisy/sparse and
33660
- * churn the tracker, so forwarding stays off until the operator enables it.
33916
+ *
33917
+ * Cold-start OFF on every camera. A vendor does not decide which detector a
33918
+ * camera runs — that is the operator's choice, and it is made where every
33919
+ * other detection choice is made. `geometry` on
33920
+ * {@link NativeObjectDetectionOptionsSchema} is how the form says what the
33921
+ * choice would buy this particular camera.
33661
33922
  */
33662
33923
  enabled: boolean()
33663
33924
  });
33925
+ /**
33926
+ * WHEN a camera's onboard detections carry geometry.
33927
+ *
33928
+ * - `boxed` — always. The provider holds a standing channel for the boxes, so
33929
+ * a detection is a trackable subject whenever the camera sees one.
33930
+ * - `while-streaming` — only while some stream of this camera is already open.
33931
+ * The boxes ride the video's own side-channel rather than a feed of their
33932
+ * own, so they cost nothing and they exist only when something is pulling.
33933
+ * On Reolink this is every BATTERY camera: a persistent second feed is real
33934
+ * radio drain, but a camera that is awake is awake precisely because
33935
+ * something is in front of it, and its stream is already being pulled.
33936
+ * - `flag-only` — never. The firmware ships the class and nothing else; the
33937
+ * pipeline needs geometry to make a subject, so such a push reaches the
33938
+ * tracker as motion and no further.
33939
+ *
33940
+ * Reported and not inferred, because the operator's question in front of the
33941
+ * picker is "what do I get", and these are three different answers (D14: the
33942
+ * derived form is only as honest as `getOptions`).
33943
+ */
33944
+ var NativeObjectGeometryEnum = _enum([
33945
+ "boxed",
33946
+ "while-streaming",
33947
+ "flag-only"
33948
+ ]);
33949
+ var NativeObjectDetectionOptionsSchema = object({
33950
+ /** Classes this firmware can detect — the same list the status reports. */
33951
+ supportedClasses: array(NativeObjectClassEnum).readonly(),
33952
+ /** What a detection from this camera carries. */
33953
+ geometry: NativeObjectGeometryEnum
33954
+ });
33955
+ var NativeObjectDetectionSettingsPatchSchema = object({ enabled: boolean().optional() });
33664
33956
  var NativeObjectDetectionRuntimeStateSchema = NativeObjectDetectionStatusSchema.extend({
33665
33957
  /** Required by createRuntimeStateBridge — epoch ms of last refresh. */
33666
33958
  lastFetchedAt: number() });
@@ -33670,13 +33962,23 @@ var nativeObjectDetectionCapability = {
33670
33962
  deviceNative: true,
33671
33963
  mode: "singleton",
33672
33964
  deviceTypes: [DeviceType.Camera],
33673
- methods: { setEnabled: method(object({
33674
- deviceId: number(),
33675
- enabled: boolean()
33676
- }), _void(), {
33677
- kind: "mutation",
33678
- auth: "admin"
33679
- }) },
33965
+ methods: {
33966
+ getOptions: method(object({ deviceId: number() }), NativeObjectDetectionOptionsSchema),
33967
+ setSettings: method(object({
33968
+ deviceId: number(),
33969
+ settings: NativeObjectDetectionSettingsPatchSchema
33970
+ }), _void(), {
33971
+ kind: "mutation",
33972
+ auth: "admin"
33973
+ }),
33974
+ setEnabled: method(object({
33975
+ deviceId: number(),
33976
+ enabled: boolean()
33977
+ }), _void(), {
33978
+ kind: "mutation",
33979
+ auth: "admin"
33980
+ })
33981
+ },
33680
33982
  events: { onDetected: { data: object({
33681
33983
  deviceId: number(),
33682
33984
  detection: NativeDetectionSchema
@@ -39138,7 +39440,28 @@ var PerScopeBreakdownSchema = object({
39138
39440
  /** Total tracked objects in this scope (frame / zone / unzoned). */
39139
39441
  totalObjects: number().int().nonnegative(),
39140
39442
  /** Per-class count. Keys are macro class names (e.g. `person`, `car`). */
39141
- byClass: record(string(), number().int().nonnegative())
39443
+ byClass: record(string(), number().int().nonnegative()),
39444
+ /**
39445
+ * Of `totalObjects`, how many are STANDING — objects the census holds,
39446
+ * present but not going anywhere (a parked car, a bin, a statue).
39447
+ *
39448
+ * The operator's question about a scene has two halves and they answer
39449
+ * different things: "what is parked here" is stable for hours and must not
39450
+ * flap, while "who is walking through" is the thing an alert is about. One
39451
+ * number could only serve one of them, and `totalObjects` served the first
39452
+ * badly — a passer-by moved it and every occupancy rule saw a change.
39453
+ *
39454
+ * `standing + transient === totalObjects`, always. The total keeps its old
39455
+ * meaning exactly, so no rule written against it changes behaviour.
39456
+ *
39457
+ * ABSENT means UNKNOWN, never zero (D393): a snapshot from a node older than
39458
+ * this field cannot say, and a reader that folds absence in as 0 reports "no
39459
+ * parked objects here" about a camera whose lot is full.
39460
+ */
39461
+ standingObjects: number().int().nonnegative().optional(),
39462
+ /** Of `totalObjects`, how many are passing through. See `standingObjects` —
39463
+ * same absence rule. */
39464
+ transientObjects: number().int().nonnegative().optional()
39142
39465
  });
39143
39466
  var ZoneScopeBreakdownSchema = PerScopeBreakdownSchema.extend({
39144
39467
  zoneId: string(),
@@ -39261,6 +39584,23 @@ var HistoryPointSchema = object({
39261
39584
  * triple covers the three spatial scopes (per-zone, frame-wide,
39262
39585
  * outside-any-zone). Crossing them with `className?` gives the full
39263
39586
  * combinatorial coverage the operator UI requested.
39587
+ *
39588
+ * ## ⚠️ The three history methods are DEPRECATED
39589
+ *
39590
+ * They are served from a 60-MINUTE in-memory ring. It dies with the process,
39591
+ * so after a restart they report nothing about a night that did happen, and any
39592
+ * window past an hour is silently clamped — a caller cannot tell a clamp from
39593
+ * an empty scene. The presets in the occupancy chart existed to hide that
39594
+ * horizon rather than to answer a question.
39595
+ *
39596
+ * Use `pipelineAnalytics.readLongTermSeries({ series: 'occupancy', scope })`
39597
+ * instead. Those rows are already written for every camera, ~60 bytes per
39598
+ * (camera, scope, 5-minute bucket), kept for a year, and survive a restart.
39599
+ * Spell the scope with `occupancyScope(zoneId?, className?)` — the same
39600
+ * function the writer uses, so the two cannot drift.
39601
+ *
39602
+ * The ring stays until these three go, and it is the only thing left reading
39603
+ * it. Do not add a fourth caller.
39264
39604
  */
39265
39605
  var zoneAnalyticsCapability = {
39266
39606
  name: "zone-analytics",
@@ -42425,12 +42765,24 @@ Object.freeze({
42425
42765
  addonId: null,
42426
42766
  access: "create"
42427
42767
  },
42768
+ "nativeObjectDetection.getOptions": {
42769
+ capName: "native-object-detection",
42770
+ capScope: "device",
42771
+ addonId: null,
42772
+ access: "view"
42773
+ },
42428
42774
  "nativeObjectDetection.setEnabled": {
42429
42775
  capName: "native-object-detection",
42430
42776
  capScope: "device",
42431
42777
  addonId: null,
42432
42778
  access: "create"
42433
42779
  },
42780
+ "nativeObjectDetection.setSettings": {
42781
+ capName: "native-object-detection",
42782
+ capScope: "device",
42783
+ addonId: null,
42784
+ access: "create"
42785
+ },
42434
42786
  "navigation.getFeatures": {
42435
42787
  capName: "navigation",
42436
42788
  capScope: "device",
@@ -42695,6 +43047,12 @@ Object.freeze({
42695
43047
  addonId: null,
42696
43048
  access: "view"
42697
43049
  },
43050
+ "notificationRules.getClipRetentionAsks": {
43051
+ capName: "notification-rules",
43052
+ capScope: "system",
43053
+ addonId: null,
43054
+ access: "view"
43055
+ },
42698
43056
  "notificationRules.getConditionCatalog": {
42699
43057
  capName: "notification-rules",
42700
43058
  capScope: "system",
@@ -43205,6 +43563,12 @@ Object.freeze({
43205
43563
  addonId: null,
43206
43564
  access: "create"
43207
43565
  },
43566
+ "pipelineAnalytics.readLongTermSeries": {
43567
+ capName: "pipeline-analytics",
43568
+ capScope: "device",
43569
+ addonId: null,
43570
+ access: "view"
43571
+ },
43208
43572
  "pipelineAnalytics.rebuildObjectEmbeddings": {
43209
43573
  capName: "pipeline-analytics",
43210
43574
  capScope: "device",
@@ -43877,6 +44241,12 @@ Object.freeze({
43877
44241
  addonId: null,
43878
44242
  access: "create"
43879
44243
  },
44244
+ "pipelineRunner.requestOccupancyBurst": {
44245
+ capName: "pipeline-runner",
44246
+ capScope: "system",
44247
+ addonId: null,
44248
+ access: "create"
44249
+ },
43880
44250
  "pipelineRunner.runDetailSubtree": {
43881
44251
  capName: "pipeline-runner",
43882
44252
  capScope: "system",
@@ -46657,11 +47027,21 @@ Object.freeze({
46657
47027
  form: "single",
46658
47028
  optional: false
46659
47029
  }],
47030
+ "nativeObjectDetection.getOptions": [{
47031
+ name: "deviceId",
47032
+ form: "single",
47033
+ optional: false
47034
+ }],
46660
47035
  "nativeObjectDetection.setEnabled": [{
46661
47036
  name: "deviceId",
46662
47037
  form: "single",
46663
47038
  optional: false
46664
47039
  }],
47040
+ "nativeObjectDetection.setSettings": [{
47041
+ name: "deviceId",
47042
+ form: "single",
47043
+ optional: false
47044
+ }],
46665
47045
  "navigation.getFeatures": [{
46666
47046
  name: "deviceId",
46667
47047
  form: "single",
@@ -47011,6 +47391,11 @@ Object.freeze({
47011
47391
  form: "single",
47012
47392
  optional: false
47013
47393
  }],
47394
+ "pipelineAnalytics.readLongTermSeries": [{
47395
+ name: "deviceId",
47396
+ form: "single",
47397
+ optional: false
47398
+ }],
47014
47399
  "pipelineAnalytics.rebuildObjectEmbeddings": [{
47015
47400
  name: "deviceId",
47016
47401
  form: "single",
@@ -47201,6 +47586,11 @@ Object.freeze({
47201
47586
  form: "single",
47202
47587
  optional: false
47203
47588
  }],
47589
+ "pipelineRunner.requestOccupancyBurst": [{
47590
+ name: "deviceId",
47591
+ form: "single",
47592
+ optional: false
47593
+ }],
47204
47594
  "pipelineRunner.runDetailSubtree": [{
47205
47595
  name: "deviceId",
47206
47596
  form: "single",
@@ -1,5 +1,5 @@
1
1
  import { h as e, l as t, u as n, y as r } from "./_virtual_mf___mfe_internal__addon_osd_manager_page__loadShare__react__loadShare__.js-Bs1t18EM.mjs";
2
- import { o as i, s as a } from "./responsive-CREvujgj.mjs";
2
+ import { o as i, s as a } from "./responsive-DmRkhonW.mjs";
3
3
  import { n as o, r as s, t as c } from "./_virtual_mf___mfe_internal__addon_osd_manager_page__loadShare__react_mf_1_jsx_mf_2_runtime__loadShare__.js-DalfdIDw.mjs";
4
4
  var l = a("chevron-down", [["path", {
5
5
  d: "m6 9 6 6 6-6",
@@ -1,2 +1,2 @@
1
- import { n as e, t } from "./virtual_mf-REMOTE_ENTRY_ID___mfe_internal__addon_osd_manager_page__remoteEntry_js-m9QQayT8.mjs";
1
+ import { n as e, t } from "./virtual_mf-REMOTE_ENTRY_ID___mfe_internal__addon_osd_manager_page__remoteEntry_js-DS2cFwR0.mjs";
2
2
  export { t as get, e as init };
@@ -1,6 +1,6 @@
1
1
  import { c as e, g as t, h as n, l as r, n as i, p as a, r as o, t as s, u as c, y as l } from "./_virtual_mf___mfe_internal__addon_osd_manager_page__loadShare__react__loadShare__.js-Bs1t18EM.mjs";
2
2
  import "./_virtual_mf___mfe_internal__addon_osd_manager_page__loadShare__react_mf_1_jsx_mf_2_runtime__loadShare__.js-DalfdIDw.mjs";
3
- import { n as u } from "./_virtual_mf___mfe_internal__addon_osd_manager_page__loadShare___mf_0_camstack_mf_1_types__loadShare__.js-BR1kX9U-.mjs";
3
+ import { n as u } from "./_virtual_mf___mfe_internal__addon_osd_manager_page__loadShare___mf_0_camstack_mf_1_types__loadShare__.js-Dc2jiuWZ.mjs";
4
4
  //#region ../../node_modules/lucide-react/dist/esm/shared/src/utils/mergeClasses.js
5
5
  l();
6
6
  var d = (...e) => e.filter((e, t, n) => !!e && e.trim() !== "" && n.indexOf(e) === t).join(" ").trim(), f = (e) => e.replace(/([a-z0-9])([A-Z])/g, "$1-$2").toLowerCase(), p = (e) => e.replace(/^([A-Z])|[\s-_]+(\w)/g, (e, t, n) => n ? n.toUpperCase() : t.toLowerCase()), m = (e) => {
@@ -1,4 +1,4 @@
1
- import { s as e } from "./responsive-CREvujgj.mjs";
1
+ import { s as e } from "./responsive-DmRkhonW.mjs";
2
2
  var t = e("eye-off", [
3
3
  ["path", {
4
4
  d: "M10.733 5.076a10.744 10.744 0 0 1 11.205 6.575 1 1 0 0 1 0 .696 10.747 10.747 0 0 1-1.444 2.49",
@@ -1,4 +1,4 @@
1
- import { s as e } from "./responsive-CREvujgj.mjs";
1
+ import { s as e } from "./responsive-DmRkhonW.mjs";
2
2
  var t = e("trash-2", [
3
3
  ["path", {
4
4
  d: "M10 11v6",
@@ -1,5 +1,5 @@
1
1
  import { c as e, h as t, p as n, y as r } from "./_virtual_mf___mfe_internal__addon_osd_manager_page__loadShare__react__loadShare__.js-Bs1t18EM.mjs";
2
- import { s as i } from "./responsive-CREvujgj.mjs";
2
+ import { s as i } from "./responsive-DmRkhonW.mjs";
3
3
  var a = i("camera", [["path", {
4
4
  d: "M13.997 4a2 2 0 0 1 1.76 1.05l.486.9A2 2 0 0 0 18.003 7H20a2 2 0 0 1 2 2v9a2 2 0 0 1-2 2H4a2 2 0 0 1-2-2V9a2 2 0 0 1 2-2h1.997a2 2 0 0 0 1.759-1.048l.489-.904A2 2 0 0 1 10.004 4z",
5
5
  key: "18u6gg"
@@ -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-ZjOQCsZZ.mjs")).catch((e) => {
2756
+ return tr ||= rr(() => import("./_virtual_mf-localSharedImportMap___mfe_internal__addon_osd_manager_page-COWDhvlO.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.99",
3
+ "version": "0.1.101",
4
4
  "description": "Binds camera on-screen-display slots to live state and recognitions",
5
5
  "keywords": [
6
6
  "camstack",
@@ -76,7 +76,7 @@
76
76
  "dev:page": "vite -c vite.page.config.ts",
77
77
  "typecheck": "tsc --noEmit",
78
78
  "test": "vitest run",
79
- "publish": "npm publish --access public"
79
+ "publish:npm": "npm publish --access public"
80
80
  },
81
81
  "peerDependencies": {
82
82
  "@camstack/types": "*",