@camstack/addon-matter-broker 0.2.62 → 0.2.64
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 -1
- package/dist/addon.mjs +48 -1
- package/package.json +1 -1
package/dist/addon.js
CHANGED
|
@@ -13007,6 +13007,24 @@ var deviceProviderCapability = {
|
|
|
13007
13007
|
})
|
|
13008
13008
|
}
|
|
13009
13009
|
};
|
|
13010
|
+
/**
|
|
13011
|
+
* Device Manager capability — hub-side singleton that unifies device persistence,
|
|
13012
|
+
* live registry access, and all management operations into a single tRPC surface.
|
|
13013
|
+
*
|
|
13014
|
+
* Replaces:
|
|
13015
|
+
* - `device-persistence` capability (persistence methods absorbed here)
|
|
13016
|
+
* - `device-management.router.ts` (deleted in Phase 2)
|
|
13017
|
+
* - `device-ops.router.ts` (compat layer — deleted; device-provider ops absorbed here)
|
|
13018
|
+
*
|
|
13019
|
+
* All device provider addons (rtsp, onvif, frigate, …) are hub-local: they may
|
|
13020
|
+
* fork into separate processes but never run on remote cluster agents. Therefore:
|
|
13021
|
+
* - No nodeId routing needed — this is a pure hub singleton.
|
|
13022
|
+
* - The hub's DeviceRegistry is the single source of truth for all live devices.
|
|
13023
|
+
* - No shadow registry or cross-node aggregation required.
|
|
13024
|
+
*
|
|
13025
|
+
* Forked workers register devices back to the hub via `ctx.devices`
|
|
13026
|
+
* (DeviceManagerApi → ctx.api.deviceManager.registerDevice), same as today.
|
|
13027
|
+
*/
|
|
13010
13028
|
/** One child-placement directive on a container's `childLayout`. Structurally
|
|
13011
13029
|
* identical to `ChildLayoutEntry` in `device-management.ts` — the cap wire
|
|
13012
13030
|
* shape for the same field. The child is identified by its re-sync-stable
|
|
@@ -13105,7 +13123,12 @@ var ConfigEntrySchema = object({
|
|
|
13105
13123
|
value: unknown(),
|
|
13106
13124
|
description: string$2().optional()
|
|
13107
13125
|
});
|
|
13108
|
-
|
|
13126
|
+
/**
|
|
13127
|
+
* Only `manual` since D356: the operator picks, nothing links itself. The
|
|
13128
|
+
* field survives on the wire because a viewer already OTA'd parses it —
|
|
13129
|
+
* drop it once no shipped client reads `mode`.
|
|
13130
|
+
*/
|
|
13131
|
+
var LinkedDevicesModeSchema = _enum(["manual"]);
|
|
13109
13132
|
/** One resolved linked device — the compact projection consumers need. */
|
|
13110
13133
|
var LinkedDeviceSchema = object({
|
|
13111
13134
|
deviceId: number(),
|
|
@@ -18733,6 +18756,9 @@ var RetrainStatusSchema = _enum([
|
|
|
18733
18756
|
*
|
|
18734
18757
|
* `debug` does NOT pin; it is attention, not durability.
|
|
18735
18758
|
*
|
|
18759
|
+
* `debugNote` is the operator's own words about WHAT should be checked on this
|
|
18760
|
+
* track, and it lives and dies with `debug` — see {@link MAX_TRACK_DEBUG_NOTE_LEN}.
|
|
18761
|
+
*
|
|
18736
18762
|
* `favourited` IS a BOOLEAN pin (durability bit), not a retrain lifecycle.
|
|
18737
18763
|
* A favourited track is skipped by retention the same way `staging` is, but
|
|
18738
18764
|
* it does not enter `none|staging|trained` and has no staging budget.
|
|
@@ -18743,6 +18769,21 @@ var TrackFlagFields = {
|
|
|
18743
18769
|
markForTrain: boolean().optional(),
|
|
18744
18770
|
/** Operator marked this track for diagnostic attention. */
|
|
18745
18771
|
debug: boolean().optional(),
|
|
18772
|
+
/**
|
|
18773
|
+
* What the operator wants CHECKED on this track, in their own words.
|
|
18774
|
+
*
|
|
18775
|
+
* The flag alone says "look at this" and nothing about what for; a debug set
|
|
18776
|
+
* reviewed hours later is a list of tracks with no question attached. Bound
|
|
18777
|
+
* to `debug` on the WRITE side — the body clears it when `debug` goes off,
|
|
18778
|
+
* and refuses it on a track whose debug is off — so a note can never outlive
|
|
18779
|
+
* the attention it belongs to.
|
|
18780
|
+
*
|
|
18781
|
+
* `''` is a real value ("marked, nothing to add"); the ABSENT key means
|
|
18782
|
+
* "leave whatever is stored alone", which is what lets a surface turn debug
|
|
18783
|
+
* on without a note (a cancelled prompt) and what lets it edit the note
|
|
18784
|
+
* without touching the flag.
|
|
18785
|
+
*/
|
|
18786
|
+
debugNote: string$2().max(500).optional(),
|
|
18746
18787
|
/** Operator favourited this track. Pins it against pruning. */
|
|
18747
18788
|
favourited: boolean().optional()
|
|
18748
18789
|
};
|
|
@@ -18769,6 +18810,12 @@ var TrackFlagsSchema = object({
|
|
|
18769
18810
|
trackId: string$2(),
|
|
18770
18811
|
markForTrain: boolean(),
|
|
18771
18812
|
debug: boolean(),
|
|
18813
|
+
/** The note as it STANDS after the write — never absent here (a track with no
|
|
18814
|
+
* note reports `''`), for the same reason the booleans are required: a
|
|
18815
|
+
* surface that has just written must be able to render the note it now owns
|
|
18816
|
+
* without a re-fetch, and an absent key would read as "unchanged" on a
|
|
18817
|
+
* screen that has no previous value to keep. */
|
|
18818
|
+
debugNote: string$2(),
|
|
18772
18819
|
favourited: boolean(),
|
|
18773
18820
|
/** The lifecycle state the boolean was derived from. Required here (unlike on
|
|
18774
18821
|
* a track row) because this shape is only ever produced by the write body,
|
package/dist/addon.mjs
CHANGED
|
@@ -13005,6 +13005,24 @@ var deviceProviderCapability = {
|
|
|
13005
13005
|
})
|
|
13006
13006
|
}
|
|
13007
13007
|
};
|
|
13008
|
+
/**
|
|
13009
|
+
* Device Manager capability — hub-side singleton that unifies device persistence,
|
|
13010
|
+
* live registry access, and all management operations into a single tRPC surface.
|
|
13011
|
+
*
|
|
13012
|
+
* Replaces:
|
|
13013
|
+
* - `device-persistence` capability (persistence methods absorbed here)
|
|
13014
|
+
* - `device-management.router.ts` (deleted in Phase 2)
|
|
13015
|
+
* - `device-ops.router.ts` (compat layer — deleted; device-provider ops absorbed here)
|
|
13016
|
+
*
|
|
13017
|
+
* All device provider addons (rtsp, onvif, frigate, …) are hub-local: they may
|
|
13018
|
+
* fork into separate processes but never run on remote cluster agents. Therefore:
|
|
13019
|
+
* - No nodeId routing needed — this is a pure hub singleton.
|
|
13020
|
+
* - The hub's DeviceRegistry is the single source of truth for all live devices.
|
|
13021
|
+
* - No shadow registry or cross-node aggregation required.
|
|
13022
|
+
*
|
|
13023
|
+
* Forked workers register devices back to the hub via `ctx.devices`
|
|
13024
|
+
* (DeviceManagerApi → ctx.api.deviceManager.registerDevice), same as today.
|
|
13025
|
+
*/
|
|
13008
13026
|
/** One child-placement directive on a container's `childLayout`. Structurally
|
|
13009
13027
|
* identical to `ChildLayoutEntry` in `device-management.ts` — the cap wire
|
|
13010
13028
|
* shape for the same field. The child is identified by its re-sync-stable
|
|
@@ -13103,7 +13121,12 @@ var ConfigEntrySchema = object({
|
|
|
13103
13121
|
value: unknown(),
|
|
13104
13122
|
description: string$2().optional()
|
|
13105
13123
|
});
|
|
13106
|
-
|
|
13124
|
+
/**
|
|
13125
|
+
* Only `manual` since D356: the operator picks, nothing links itself. The
|
|
13126
|
+
* field survives on the wire because a viewer already OTA'd parses it —
|
|
13127
|
+
* drop it once no shipped client reads `mode`.
|
|
13128
|
+
*/
|
|
13129
|
+
var LinkedDevicesModeSchema = _enum(["manual"]);
|
|
13107
13130
|
/** One resolved linked device — the compact projection consumers need. */
|
|
13108
13131
|
var LinkedDeviceSchema = object({
|
|
13109
13132
|
deviceId: number(),
|
|
@@ -18731,6 +18754,9 @@ var RetrainStatusSchema = _enum([
|
|
|
18731
18754
|
*
|
|
18732
18755
|
* `debug` does NOT pin; it is attention, not durability.
|
|
18733
18756
|
*
|
|
18757
|
+
* `debugNote` is the operator's own words about WHAT should be checked on this
|
|
18758
|
+
* track, and it lives and dies with `debug` — see {@link MAX_TRACK_DEBUG_NOTE_LEN}.
|
|
18759
|
+
*
|
|
18734
18760
|
* `favourited` IS a BOOLEAN pin (durability bit), not a retrain lifecycle.
|
|
18735
18761
|
* A favourited track is skipped by retention the same way `staging` is, but
|
|
18736
18762
|
* it does not enter `none|staging|trained` and has no staging budget.
|
|
@@ -18741,6 +18767,21 @@ var TrackFlagFields = {
|
|
|
18741
18767
|
markForTrain: boolean().optional(),
|
|
18742
18768
|
/** Operator marked this track for diagnostic attention. */
|
|
18743
18769
|
debug: boolean().optional(),
|
|
18770
|
+
/**
|
|
18771
|
+
* What the operator wants CHECKED on this track, in their own words.
|
|
18772
|
+
*
|
|
18773
|
+
* The flag alone says "look at this" and nothing about what for; a debug set
|
|
18774
|
+
* reviewed hours later is a list of tracks with no question attached. Bound
|
|
18775
|
+
* to `debug` on the WRITE side — the body clears it when `debug` goes off,
|
|
18776
|
+
* and refuses it on a track whose debug is off — so a note can never outlive
|
|
18777
|
+
* the attention it belongs to.
|
|
18778
|
+
*
|
|
18779
|
+
* `''` is a real value ("marked, nothing to add"); the ABSENT key means
|
|
18780
|
+
* "leave whatever is stored alone", which is what lets a surface turn debug
|
|
18781
|
+
* on without a note (a cancelled prompt) and what lets it edit the note
|
|
18782
|
+
* without touching the flag.
|
|
18783
|
+
*/
|
|
18784
|
+
debugNote: string$2().max(500).optional(),
|
|
18744
18785
|
/** Operator favourited this track. Pins it against pruning. */
|
|
18745
18786
|
favourited: boolean().optional()
|
|
18746
18787
|
};
|
|
@@ -18767,6 +18808,12 @@ var TrackFlagsSchema = object({
|
|
|
18767
18808
|
trackId: string$2(),
|
|
18768
18809
|
markForTrain: boolean(),
|
|
18769
18810
|
debug: boolean(),
|
|
18811
|
+
/** The note as it STANDS after the write — never absent here (a track with no
|
|
18812
|
+
* note reports `''`), for the same reason the booleans are required: a
|
|
18813
|
+
* surface that has just written must be able to render the note it now owns
|
|
18814
|
+
* without a re-fetch, and an absent key would read as "unchanged" on a
|
|
18815
|
+
* screen that has no previous value to keep. */
|
|
18816
|
+
debugNote: string$2(),
|
|
18770
18817
|
favourited: boolean(),
|
|
18771
18818
|
/** The lifecycle state the boolean was derived from. Required here (unlike on
|
|
18772
18819
|
* 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-matter-broker",
|
|
3
|
-
"version": "0.2.
|
|
3
|
+
"version": "0.2.64",
|
|
4
4
|
"description": "Matter broker addon for CamStack — owns a Matter fabric (commissioning + the long-lived controller) via the matter.js controller and brokers commissioned Matter nodes into CamStack",
|
|
5
5
|
"keywords": [
|
|
6
6
|
"camstack",
|