@camstack/addon-decoder-ffmpeg 1.2.63 → 1.2.65

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/index.js CHANGED
@@ -12768,6 +12768,24 @@ method(_void(), _void(), { kind: "mutation" }), method(_void(), _void(), { kind:
12768
12768
  kind: "mutation",
12769
12769
  auth: "admin"
12770
12770
  });
12771
+ /**
12772
+ * Device Manager capability — hub-side singleton that unifies device persistence,
12773
+ * live registry access, and all management operations into a single tRPC surface.
12774
+ *
12775
+ * Replaces:
12776
+ * - `device-persistence` capability (persistence methods absorbed here)
12777
+ * - `device-management.router.ts` (deleted in Phase 2)
12778
+ * - `device-ops.router.ts` (compat layer — deleted; device-provider ops absorbed here)
12779
+ *
12780
+ * All device provider addons (rtsp, onvif, frigate, …) are hub-local: they may
12781
+ * fork into separate processes but never run on remote cluster agents. Therefore:
12782
+ * - No nodeId routing needed — this is a pure hub singleton.
12783
+ * - The hub's DeviceRegistry is the single source of truth for all live devices.
12784
+ * - No shadow registry or cross-node aggregation required.
12785
+ *
12786
+ * Forked workers register devices back to the hub via `ctx.devices`
12787
+ * (DeviceManagerApi → ctx.api.deviceManager.registerDevice), same as today.
12788
+ */
12771
12789
  /** One child-placement directive on a container's `childLayout`. Structurally
12772
12790
  * identical to `ChildLayoutEntry` in `device-management.ts` — the cap wire
12773
12791
  * shape for the same field. The child is identified by its re-sync-stable
@@ -12866,7 +12884,12 @@ var ConfigEntrySchema = object({
12866
12884
  value: unknown(),
12867
12885
  description: string().optional()
12868
12886
  });
12869
- var LinkedDevicesModeSchema = _enum(["auto", "manual"]);
12887
+ /**
12888
+ * Only `manual` since D356: the operator picks, nothing links itself. The
12889
+ * field survives on the wire because a viewer already OTA'd parses it —
12890
+ * drop it once no shipped client reads `mode`.
12891
+ */
12892
+ var LinkedDevicesModeSchema = _enum(["manual"]);
12870
12893
  /** One resolved linked device — the compact projection consumers need. */
12871
12894
  var LinkedDeviceSchema = object({
12872
12895
  deviceId: number(),
@@ -18416,6 +18439,9 @@ var RetrainStatusSchema = _enum([
18416
18439
  *
18417
18440
  * `debug` does NOT pin; it is attention, not durability.
18418
18441
  *
18442
+ * `debugNote` is the operator's own words about WHAT should be checked on this
18443
+ * track, and it lives and dies with `debug` — see {@link MAX_TRACK_DEBUG_NOTE_LEN}.
18444
+ *
18419
18445
  * `favourited` IS a BOOLEAN pin (durability bit), not a retrain lifecycle.
18420
18446
  * A favourited track is skipped by retention the same way `staging` is, but
18421
18447
  * it does not enter `none|staging|trained` and has no staging budget.
@@ -18426,6 +18452,21 @@ var TrackFlagFields = {
18426
18452
  markForTrain: boolean().optional(),
18427
18453
  /** Operator marked this track for diagnostic attention. */
18428
18454
  debug: boolean().optional(),
18455
+ /**
18456
+ * What the operator wants CHECKED on this track, in their own words.
18457
+ *
18458
+ * The flag alone says "look at this" and nothing about what for; a debug set
18459
+ * reviewed hours later is a list of tracks with no question attached. Bound
18460
+ * to `debug` on the WRITE side — the body clears it when `debug` goes off,
18461
+ * and refuses it on a track whose debug is off — so a note can never outlive
18462
+ * the attention it belongs to.
18463
+ *
18464
+ * `''` is a real value ("marked, nothing to add"); the ABSENT key means
18465
+ * "leave whatever is stored alone", which is what lets a surface turn debug
18466
+ * on without a note (a cancelled prompt) and what lets it edit the note
18467
+ * without touching the flag.
18468
+ */
18469
+ debugNote: string().max(500).optional(),
18429
18470
  /** Operator favourited this track. Pins it against pruning. */
18430
18471
  favourited: boolean().optional()
18431
18472
  };
@@ -18452,6 +18493,12 @@ var TrackFlagsSchema = object({
18452
18493
  trackId: string(),
18453
18494
  markForTrain: boolean(),
18454
18495
  debug: boolean(),
18496
+ /** The note as it STANDS after the write — never absent here (a track with no
18497
+ * note reports `''`), for the same reason the booleans are required: a
18498
+ * surface that has just written must be able to render the note it now owns
18499
+ * without a re-fetch, and an absent key would read as "unchanged" on a
18500
+ * screen that has no previous value to keep. */
18501
+ debugNote: string(),
18455
18502
  favourited: boolean(),
18456
18503
  /** The lifecycle state the boolean was derived from. Required here (unlike on
18457
18504
  * a track row) because this shape is only ever produced by the write body,
package/dist/index.mjs CHANGED
@@ -12764,6 +12764,24 @@ method(_void(), _void(), { kind: "mutation" }), method(_void(), _void(), { kind:
12764
12764
  kind: "mutation",
12765
12765
  auth: "admin"
12766
12766
  });
12767
+ /**
12768
+ * Device Manager capability — hub-side singleton that unifies device persistence,
12769
+ * live registry access, and all management operations into a single tRPC surface.
12770
+ *
12771
+ * Replaces:
12772
+ * - `device-persistence` capability (persistence methods absorbed here)
12773
+ * - `device-management.router.ts` (deleted in Phase 2)
12774
+ * - `device-ops.router.ts` (compat layer — deleted; device-provider ops absorbed here)
12775
+ *
12776
+ * All device provider addons (rtsp, onvif, frigate, …) are hub-local: they may
12777
+ * fork into separate processes but never run on remote cluster agents. Therefore:
12778
+ * - No nodeId routing needed — this is a pure hub singleton.
12779
+ * - The hub's DeviceRegistry is the single source of truth for all live devices.
12780
+ * - No shadow registry or cross-node aggregation required.
12781
+ *
12782
+ * Forked workers register devices back to the hub via `ctx.devices`
12783
+ * (DeviceManagerApi → ctx.api.deviceManager.registerDevice), same as today.
12784
+ */
12767
12785
  /** One child-placement directive on a container's `childLayout`. Structurally
12768
12786
  * identical to `ChildLayoutEntry` in `device-management.ts` — the cap wire
12769
12787
  * shape for the same field. The child is identified by its re-sync-stable
@@ -12862,7 +12880,12 @@ var ConfigEntrySchema = object({
12862
12880
  value: unknown(),
12863
12881
  description: string().optional()
12864
12882
  });
12865
- var LinkedDevicesModeSchema = _enum(["auto", "manual"]);
12883
+ /**
12884
+ * Only `manual` since D356: the operator picks, nothing links itself. The
12885
+ * field survives on the wire because a viewer already OTA'd parses it —
12886
+ * drop it once no shipped client reads `mode`.
12887
+ */
12888
+ var LinkedDevicesModeSchema = _enum(["manual"]);
12866
12889
  /** One resolved linked device — the compact projection consumers need. */
12867
12890
  var LinkedDeviceSchema = object({
12868
12891
  deviceId: number(),
@@ -18412,6 +18435,9 @@ var RetrainStatusSchema = _enum([
18412
18435
  *
18413
18436
  * `debug` does NOT pin; it is attention, not durability.
18414
18437
  *
18438
+ * `debugNote` is the operator's own words about WHAT should be checked on this
18439
+ * track, and it lives and dies with `debug` — see {@link MAX_TRACK_DEBUG_NOTE_LEN}.
18440
+ *
18415
18441
  * `favourited` IS a BOOLEAN pin (durability bit), not a retrain lifecycle.
18416
18442
  * A favourited track is skipped by retention the same way `staging` is, but
18417
18443
  * it does not enter `none|staging|trained` and has no staging budget.
@@ -18422,6 +18448,21 @@ var TrackFlagFields = {
18422
18448
  markForTrain: boolean().optional(),
18423
18449
  /** Operator marked this track for diagnostic attention. */
18424
18450
  debug: boolean().optional(),
18451
+ /**
18452
+ * What the operator wants CHECKED on this track, in their own words.
18453
+ *
18454
+ * The flag alone says "look at this" and nothing about what for; a debug set
18455
+ * reviewed hours later is a list of tracks with no question attached. Bound
18456
+ * to `debug` on the WRITE side — the body clears it when `debug` goes off,
18457
+ * and refuses it on a track whose debug is off — so a note can never outlive
18458
+ * the attention it belongs to.
18459
+ *
18460
+ * `''` is a real value ("marked, nothing to add"); the ABSENT key means
18461
+ * "leave whatever is stored alone", which is what lets a surface turn debug
18462
+ * on without a note (a cancelled prompt) and what lets it edit the note
18463
+ * without touching the flag.
18464
+ */
18465
+ debugNote: string().max(500).optional(),
18425
18466
  /** Operator favourited this track. Pins it against pruning. */
18426
18467
  favourited: boolean().optional()
18427
18468
  };
@@ -18448,6 +18489,12 @@ var TrackFlagsSchema = object({
18448
18489
  trackId: string(),
18449
18490
  markForTrain: boolean(),
18450
18491
  debug: boolean(),
18492
+ /** The note as it STANDS after the write — never absent here (a track with no
18493
+ * note reports `''`), for the same reason the booleans are required: a
18494
+ * surface that has just written must be able to render the note it now owns
18495
+ * without a re-fetch, and an absent key would read as "unchanged" on a
18496
+ * screen that has no previous value to keep. */
18497
+ debugNote: string(),
18451
18498
  favourited: boolean(),
18452
18499
  /** The lifecycle state the boolean was derived from. Required here (unlike on
18453
18500
  * a track row) because this shape is only ever produced by the write body,
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@camstack/addon-decoder-ffmpeg",
3
- "version": "1.2.63",
3
+ "version": "1.2.65",
4
4
  "description": "Standalone ffmpeg-subprocess decoder fallback addon for CamStack",
5
5
  "keywords": [
6
6
  "camstack",