@camstack/addon-provider-rademacher 0.2.61 → 0.2.63
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 +42 -0
- package/dist/addon.mjs +42 -0
- package/package.json +1 -1
package/dist/addon.js
CHANGED
|
@@ -13912,6 +13912,24 @@ var deviceProviderCapability = {
|
|
|
13912
13912
|
})
|
|
13913
13913
|
}
|
|
13914
13914
|
};
|
|
13915
|
+
/**
|
|
13916
|
+
* Device Manager capability — hub-side singleton that unifies device persistence,
|
|
13917
|
+
* live registry access, and all management operations into a single tRPC surface.
|
|
13918
|
+
*
|
|
13919
|
+
* Replaces:
|
|
13920
|
+
* - `device-persistence` capability (persistence methods absorbed here)
|
|
13921
|
+
* - `device-management.router.ts` (deleted in Phase 2)
|
|
13922
|
+
* - `device-ops.router.ts` (compat layer — deleted; device-provider ops absorbed here)
|
|
13923
|
+
*
|
|
13924
|
+
* All device provider addons (rtsp, onvif, frigate, …) are hub-local: they may
|
|
13925
|
+
* fork into separate processes but never run on remote cluster agents. Therefore:
|
|
13926
|
+
* - No nodeId routing needed — this is a pure hub singleton.
|
|
13927
|
+
* - The hub's DeviceRegistry is the single source of truth for all live devices.
|
|
13928
|
+
* - No shadow registry or cross-node aggregation required.
|
|
13929
|
+
*
|
|
13930
|
+
* Forked workers register devices back to the hub via `ctx.devices`
|
|
13931
|
+
* (DeviceManagerApi → ctx.api.deviceManager.registerDevice), same as today.
|
|
13932
|
+
*/
|
|
13915
13933
|
/** One child-placement directive on a container's `childLayout`. Structurally
|
|
13916
13934
|
* identical to `ChildLayoutEntry` in `device-management.ts` — the cap wire
|
|
13917
13935
|
* shape for the same field. The child is identified by its re-sync-stable
|
|
@@ -19638,6 +19656,9 @@ var RetrainStatusSchema = _enum([
|
|
|
19638
19656
|
*
|
|
19639
19657
|
* `debug` does NOT pin; it is attention, not durability.
|
|
19640
19658
|
*
|
|
19659
|
+
* `debugNote` is the operator's own words about WHAT should be checked on this
|
|
19660
|
+
* track, and it lives and dies with `debug` — see {@link MAX_TRACK_DEBUG_NOTE_LEN}.
|
|
19661
|
+
*
|
|
19641
19662
|
* `favourited` IS a BOOLEAN pin (durability bit), not a retrain lifecycle.
|
|
19642
19663
|
* A favourited track is skipped by retention the same way `staging` is, but
|
|
19643
19664
|
* it does not enter `none|staging|trained` and has no staging budget.
|
|
@@ -19648,6 +19669,21 @@ var TrackFlagFields = {
|
|
|
19648
19669
|
markForTrain: boolean().optional(),
|
|
19649
19670
|
/** Operator marked this track for diagnostic attention. */
|
|
19650
19671
|
debug: boolean().optional(),
|
|
19672
|
+
/**
|
|
19673
|
+
* What the operator wants CHECKED on this track, in their own words.
|
|
19674
|
+
*
|
|
19675
|
+
* The flag alone says "look at this" and nothing about what for; a debug set
|
|
19676
|
+
* reviewed hours later is a list of tracks with no question attached. Bound
|
|
19677
|
+
* to `debug` on the WRITE side — the body clears it when `debug` goes off,
|
|
19678
|
+
* and refuses it on a track whose debug is off — so a note can never outlive
|
|
19679
|
+
* the attention it belongs to.
|
|
19680
|
+
*
|
|
19681
|
+
* `''` is a real value ("marked, nothing to add"); the ABSENT key means
|
|
19682
|
+
* "leave whatever is stored alone", which is what lets a surface turn debug
|
|
19683
|
+
* on without a note (a cancelled prompt) and what lets it edit the note
|
|
19684
|
+
* without touching the flag.
|
|
19685
|
+
*/
|
|
19686
|
+
debugNote: string().max(500).optional(),
|
|
19651
19687
|
/** Operator favourited this track. Pins it against pruning. */
|
|
19652
19688
|
favourited: boolean().optional()
|
|
19653
19689
|
};
|
|
@@ -19674,6 +19710,12 @@ var TrackFlagsSchema = object({
|
|
|
19674
19710
|
trackId: string(),
|
|
19675
19711
|
markForTrain: boolean(),
|
|
19676
19712
|
debug: boolean(),
|
|
19713
|
+
/** The note as it STANDS after the write — never absent here (a track with no
|
|
19714
|
+
* note reports `''`), for the same reason the booleans are required: a
|
|
19715
|
+
* surface that has just written must be able to render the note it now owns
|
|
19716
|
+
* without a re-fetch, and an absent key would read as "unchanged" on a
|
|
19717
|
+
* screen that has no previous value to keep. */
|
|
19718
|
+
debugNote: string(),
|
|
19677
19719
|
favourited: boolean(),
|
|
19678
19720
|
/** The lifecycle state the boolean was derived from. Required here (unlike on
|
|
19679
19721
|
* a track row) because this shape is only ever produced by the write body,
|
package/dist/addon.mjs
CHANGED
|
@@ -13911,6 +13911,24 @@ var deviceProviderCapability = {
|
|
|
13911
13911
|
})
|
|
13912
13912
|
}
|
|
13913
13913
|
};
|
|
13914
|
+
/**
|
|
13915
|
+
* Device Manager capability — hub-side singleton that unifies device persistence,
|
|
13916
|
+
* live registry access, and all management operations into a single tRPC surface.
|
|
13917
|
+
*
|
|
13918
|
+
* Replaces:
|
|
13919
|
+
* - `device-persistence` capability (persistence methods absorbed here)
|
|
13920
|
+
* - `device-management.router.ts` (deleted in Phase 2)
|
|
13921
|
+
* - `device-ops.router.ts` (compat layer — deleted; device-provider ops absorbed here)
|
|
13922
|
+
*
|
|
13923
|
+
* All device provider addons (rtsp, onvif, frigate, …) are hub-local: they may
|
|
13924
|
+
* fork into separate processes but never run on remote cluster agents. Therefore:
|
|
13925
|
+
* - No nodeId routing needed — this is a pure hub singleton.
|
|
13926
|
+
* - The hub's DeviceRegistry is the single source of truth for all live devices.
|
|
13927
|
+
* - No shadow registry or cross-node aggregation required.
|
|
13928
|
+
*
|
|
13929
|
+
* Forked workers register devices back to the hub via `ctx.devices`
|
|
13930
|
+
* (DeviceManagerApi → ctx.api.deviceManager.registerDevice), same as today.
|
|
13931
|
+
*/
|
|
13914
13932
|
/** One child-placement directive on a container's `childLayout`. Structurally
|
|
13915
13933
|
* identical to `ChildLayoutEntry` in `device-management.ts` — the cap wire
|
|
13916
13934
|
* shape for the same field. The child is identified by its re-sync-stable
|
|
@@ -19637,6 +19655,9 @@ var RetrainStatusSchema = _enum([
|
|
|
19637
19655
|
*
|
|
19638
19656
|
* `debug` does NOT pin; it is attention, not durability.
|
|
19639
19657
|
*
|
|
19658
|
+
* `debugNote` is the operator's own words about WHAT should be checked on this
|
|
19659
|
+
* track, and it lives and dies with `debug` — see {@link MAX_TRACK_DEBUG_NOTE_LEN}.
|
|
19660
|
+
*
|
|
19640
19661
|
* `favourited` IS a BOOLEAN pin (durability bit), not a retrain lifecycle.
|
|
19641
19662
|
* A favourited track is skipped by retention the same way `staging` is, but
|
|
19642
19663
|
* it does not enter `none|staging|trained` and has no staging budget.
|
|
@@ -19647,6 +19668,21 @@ var TrackFlagFields = {
|
|
|
19647
19668
|
markForTrain: boolean().optional(),
|
|
19648
19669
|
/** Operator marked this track for diagnostic attention. */
|
|
19649
19670
|
debug: boolean().optional(),
|
|
19671
|
+
/**
|
|
19672
|
+
* What the operator wants CHECKED on this track, in their own words.
|
|
19673
|
+
*
|
|
19674
|
+
* The flag alone says "look at this" and nothing about what for; a debug set
|
|
19675
|
+
* reviewed hours later is a list of tracks with no question attached. Bound
|
|
19676
|
+
* to `debug` on the WRITE side — the body clears it when `debug` goes off,
|
|
19677
|
+
* and refuses it on a track whose debug is off — so a note can never outlive
|
|
19678
|
+
* the attention it belongs to.
|
|
19679
|
+
*
|
|
19680
|
+
* `''` is a real value ("marked, nothing to add"); the ABSENT key means
|
|
19681
|
+
* "leave whatever is stored alone", which is what lets a surface turn debug
|
|
19682
|
+
* on without a note (a cancelled prompt) and what lets it edit the note
|
|
19683
|
+
* without touching the flag.
|
|
19684
|
+
*/
|
|
19685
|
+
debugNote: string().max(500).optional(),
|
|
19650
19686
|
/** Operator favourited this track. Pins it against pruning. */
|
|
19651
19687
|
favourited: boolean().optional()
|
|
19652
19688
|
};
|
|
@@ -19673,6 +19709,12 @@ var TrackFlagsSchema = object({
|
|
|
19673
19709
|
trackId: string(),
|
|
19674
19710
|
markForTrain: boolean(),
|
|
19675
19711
|
debug: boolean(),
|
|
19712
|
+
/** The note as it STANDS after the write — never absent here (a track with no
|
|
19713
|
+
* note reports `''`), for the same reason the booleans are required: a
|
|
19714
|
+
* surface that has just written must be able to render the note it now owns
|
|
19715
|
+
* without a re-fetch, and an absent key would read as "unchanged" on a
|
|
19716
|
+
* screen that has no previous value to keep. */
|
|
19717
|
+
debugNote: string(),
|
|
19676
19718
|
favourited: boolean(),
|
|
19677
19719
|
/** The lifecycle state the boolean was derived from. Required here (unlike on
|
|
19678
19720
|
* 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-provider-rademacher",
|
|
3
|
-
"version": "0.2.
|
|
3
|
+
"version": "0.2.63",
|
|
4
4
|
"description": "Rademacher HomePilot device-provider addon for CamStack — wraps the @apocaliss92/noderademacher local-hub client (roller shutters over the cover cap)",
|
|
5
5
|
"keywords": [
|
|
6
6
|
"camstack",
|