@camstack/system 1.2.135 → 1.2.136

package/dist/builtins/device-manager/device-manager.addon.js

@@ -1315,7 +1315,10 @@ async function listAll(pctx, input) {
 	const idFilter = input.deviceIds === void 0 ? null : new Set(input.deviceIds);
 	const results = [];
 	const seen = /* @__PURE__ */ new Set();
-	const fleet = addonId ? await pctx.metaStore.rows.listByAddon(addonId) : await pctx.metaStore.rows.listAll();
+	const fleet = addonId ? await pctx.metaStore.rows.listByAddon(addonId) : await pctx.metaStore.rows.listFleet({
+		...input.deviceIds !== void 0 ? { deviceIds: input.deviceIds } : {},
+		slim
+	});
 	const rowById = /* @__PURE__ */ new Map();
 	for (const row of fleet) rowById.set(row.meta.id, row);
 	if (pctx.registry) {
@@ -4051,6 +4054,36 @@ var DEVICE_ROWS_COLUMNS = [
 		type: "JSON"
 	}
 ];
+/**
+* The columns a SLIM fleet read selects: every declared column except the
+* primary key (always returned) and `metadata`.
+*
+* ## Why this is a DENYLIST and must stay one
+*
+* `decodeDeviceRow` returns `null` when `deviceId`, `addonId`, `stableId`,
+* `type` or `name` is missing, and `list()` then SKIPS the row with a warn. A
+* hand-written allowlist that forgot one of the five would not make the fleet
+* slower — it would make devices vanish from every listing, quietly, and the
+* only trace would be a log line nobody is reading at the time. Deriving the
+* list by subtraction means a column added tomorrow is carried by default and
+* the only way to lose one is to name it here.
+*
+* `metadata` is the one slim provably discards: `device-queries.ts#listAll`
+* sets `metadata: null` on every slim row. It is also the largest JSON column
+* on the row, which is why this is worth doing at all.
+*
+* ## What is NOT here, and will not be
+*
+* There is no `where: { type: 'camera' }` companion to this. `isCameraDevice`
+* is a method-presence check (`getStreamSources`), not the persisted `type`, so
+* a doorbell with a camera answers YES while its row says `doorbell`. Filtering
+* the rows by type would strip exactly those devices of their row — and
+* `toDeviceInfo` reads `name` / `location` / `disabled` from the ROW precisely
+* because the live device's copies are stale by construction. The fleet would
+* keep working and start reporting pre-rename names on doorbells. The
+* `isCamera` filter stays in JS.
+*/
+var DEVICE_ROWS_SLIM_COLUMNS = DEVICE_ROWS_COLUMNS.map((c) => c.name).filter((name) => name !== "id" && name !== "metadata");
 var DEVICE_ROWS_INDEXES = [
 	{
 		name: "idx_dm_devices_addon_stable",
@@ -4269,6 +4302,33 @@ var DeviceRowStore = class {
 		});
 	}
 	/**
+	* The fleet, read as narrowly as the question allows.
+	*
+	* `listAll` is a full-table `SELECT … ORDER BY "deviceId"` — ~1 017 rows a
+	* call on the live hub, 14–54 calls a minute — and its callers then filtered
+	* the result in JS. The two filters that CAN be pushed down are here:
+	*
+	*  - `deviceIds` becomes a `whereIn`. The viewer's linked-devices panel asks
+	*    about ~8 named ids; it was answered by reading the whole ledger. An
+	*    EMPTY set reads nothing at all rather than degrading to "everything" —
+	*    a request for no devices is a request, not an omission.
+	*  - `slim` becomes a column projection, {@link DEVICE_ROWS_SLIM_COLUMNS}.
+	*
+	* `isCamera` is deliberately NOT one of them — see that constant's note and
+	* `device-row-store-filtered.spec.ts`.
+	*/
+	async listFleet(opts) {
+		if (opts.deviceIds !== void 0 && opts.deviceIds.length === 0) return [];
+		return this.list({
+			...opts.deviceIds !== void 0 ? { whereIn: { deviceId: [...new Set(opts.deviceIds)] } } : {},
+			orderBy: {
+				field: "deviceId",
+				direction: "asc"
+			},
+			limit: DEVICE_ROWS_FLEET_LIMIT
+		}, opts.slim === true ? DEVICE_ROWS_SLIM_COLUMNS : void 0);
+	}
+	/**
 	* The device an addon knows as `stableId`, or `null`.
 	*
 	* `(addonId, stableId)` is the addon-facing identity — unique by
@@ -4339,11 +4399,12 @@ var DeviceRowStore = class {
 		await this.declare();
 		return this.backend.count({ collection: DEVICE_ROWS_COLLECTION });
 	}
-	async list(filter) {
+	async list(filter, columns) {
 		await this.declare();
 		const records = await this.backend.query({
 			collection: DEVICE_ROWS_COLLECTION,
-			filter
+			filter,
+			...columns === void 0 ? {} : { columns }
 		});
 		const out = [];
 		for (const record of records) {

package/dist/builtins/device-manager/device-manager.addon.mjs

@@ -1310,7 +1310,10 @@ async function listAll(pctx, input) {
 	const idFilter = input.deviceIds === void 0 ? null : new Set(input.deviceIds);
 	const results = [];
 	const seen = /* @__PURE__ */ new Set();
-	const fleet = addonId ? await pctx.metaStore.rows.listByAddon(addonId) : await pctx.metaStore.rows.listAll();
+	const fleet = addonId ? await pctx.metaStore.rows.listByAddon(addonId) : await pctx.metaStore.rows.listFleet({
+		...input.deviceIds !== void 0 ? { deviceIds: input.deviceIds } : {},
+		slim
+	});
 	const rowById = /* @__PURE__ */ new Map();
 	for (const row of fleet) rowById.set(row.meta.id, row);
 	if (pctx.registry) {
@@ -4046,6 +4049,36 @@ var DEVICE_ROWS_COLUMNS = [
 		type: "JSON"
 	}
 ];
+/**
+* The columns a SLIM fleet read selects: every declared column except the
+* primary key (always returned) and `metadata`.
+*
+* ## Why this is a DENYLIST and must stay one
+*
+* `decodeDeviceRow` returns `null` when `deviceId`, `addonId`, `stableId`,
+* `type` or `name` is missing, and `list()` then SKIPS the row with a warn. A
+* hand-written allowlist that forgot one of the five would not make the fleet
+* slower — it would make devices vanish from every listing, quietly, and the
+* only trace would be a log line nobody is reading at the time. Deriving the
+* list by subtraction means a column added tomorrow is carried by default and
+* the only way to lose one is to name it here.
+*
+* `metadata` is the one slim provably discards: `device-queries.ts#listAll`
+* sets `metadata: null` on every slim row. It is also the largest JSON column
+* on the row, which is why this is worth doing at all.
+*
+* ## What is NOT here, and will not be
+*
+* There is no `where: { type: 'camera' }` companion to this. `isCameraDevice`
+* is a method-presence check (`getStreamSources`), not the persisted `type`, so
+* a doorbell with a camera answers YES while its row says `doorbell`. Filtering
+* the rows by type would strip exactly those devices of their row — and
+* `toDeviceInfo` reads `name` / `location` / `disabled` from the ROW precisely
+* because the live device's copies are stale by construction. The fleet would
+* keep working and start reporting pre-rename names on doorbells. The
+* `isCamera` filter stays in JS.
+*/
+var DEVICE_ROWS_SLIM_COLUMNS = DEVICE_ROWS_COLUMNS.map((c) => c.name).filter((name) => name !== "id" && name !== "metadata");
 var DEVICE_ROWS_INDEXES = [
 	{
 		name: "idx_dm_devices_addon_stable",
@@ -4264,6 +4297,33 @@ var DeviceRowStore = class {
 		});
 	}
 	/**
+	* The fleet, read as narrowly as the question allows.
+	*
+	* `listAll` is a full-table `SELECT … ORDER BY "deviceId"` — ~1 017 rows a
+	* call on the live hub, 14–54 calls a minute — and its callers then filtered
+	* the result in JS. The two filters that CAN be pushed down are here:
+	*
+	*  - `deviceIds` becomes a `whereIn`. The viewer's linked-devices panel asks
+	*    about ~8 named ids; it was answered by reading the whole ledger. An
+	*    EMPTY set reads nothing at all rather than degrading to "everything" —
+	*    a request for no devices is a request, not an omission.
+	*  - `slim` becomes a column projection, {@link DEVICE_ROWS_SLIM_COLUMNS}.
+	*
+	* `isCamera` is deliberately NOT one of them — see that constant's note and
+	* `device-row-store-filtered.spec.ts`.
+	*/
+	async listFleet(opts) {
+		if (opts.deviceIds !== void 0 && opts.deviceIds.length === 0) return [];
+		return this.list({
+			...opts.deviceIds !== void 0 ? { whereIn: { deviceId: [...new Set(opts.deviceIds)] } } : {},
+			orderBy: {
+				field: "deviceId",
+				direction: "asc"
+			},
+			limit: DEVICE_ROWS_FLEET_LIMIT
+		}, opts.slim === true ? DEVICE_ROWS_SLIM_COLUMNS : void 0);
+	}
+	/**
 	* The device an addon knows as `stableId`, or `null`.
 	*
 	* `(addonId, stableId)` is the addon-facing identity — unique by
@@ -4334,11 +4394,12 @@ var DeviceRowStore = class {
 		await this.declare();
 		return this.backend.count({ collection: DEVICE_ROWS_COLLECTION });
 	}
-	async list(filter) {
+	async list(filter, columns) {
 		await this.declare();
 		const records = await this.backend.query({
 			collection: DEVICE_ROWS_COLLECTION,
-			filter
+			filter,
+			...columns === void 0 ? {} : { columns }
 		});
 		const out = [];
 		for (const record of records) {

package/dist/builtins/device-manager/device-row-store.d.ts

@@ -43,6 +43,36 @@ export declare const DEVICE_ROWS_COLLECTION = "device-manager:devices";
  */
 export declare const DEVICE_ROWS_FLEET_LIMIT = 20000;
 export declare const DEVICE_ROWS_COLUMNS: readonly CollectionColumn[];
+/**
+ * The columns a SLIM fleet read selects: every declared column except the
+ * primary key (always returned) and `metadata`.
+ *
+ * ## Why this is a DENYLIST and must stay one
+ *
+ * `decodeDeviceRow` returns `null` when `deviceId`, `addonId`, `stableId`,
+ * `type` or `name` is missing, and `list()` then SKIPS the row with a warn. A
+ * hand-written allowlist that forgot one of the five would not make the fleet
+ * slower — it would make devices vanish from every listing, quietly, and the
+ * only trace would be a log line nobody is reading at the time. Deriving the
+ * list by subtraction means a column added tomorrow is carried by default and
+ * the only way to lose one is to name it here.
+ *
+ * `metadata` is the one slim provably discards: `device-queries.ts#listAll`
+ * sets `metadata: null` on every slim row. It is also the largest JSON column
+ * on the row, which is why this is worth doing at all.
+ *
+ * ## What is NOT here, and will not be
+ *
+ * There is no `where: { type: 'camera' }` companion to this. `isCameraDevice`
+ * is a method-presence check (`getStreamSources`), not the persisted `type`, so
+ * a doorbell with a camera answers YES while its row says `doorbell`. Filtering
+ * the rows by type would strip exactly those devices of their row — and
+ * `toDeviceInfo` reads `name` / `location` / `disabled` from the ROW precisely
+ * because the live device's copies are stale by construction. The fleet would
+ * keep working and start reporting pre-rename names on doorbells. The
+ * `isCamera` filter stays in JS.
+ */
+export declare const DEVICE_ROWS_SLIM_COLUMNS: readonly string[];
 export declare const DEVICE_ROWS_INDEXES: readonly CollectionIndex[];
 /**
  * The settings-store door this store needs, as a plain object surface.
@@ -193,6 +223,26 @@ export declare class DeviceRowStore {
     get(deviceId: number): Promise<DeviceRow | null>;
     /** Every device, ordered by numeric id. */
     listAll(): Promise<readonly DeviceRow[]>;
+    /**
+     * The fleet, read as narrowly as the question allows.
+     *
+     * `listAll` is a full-table `SELECT … ORDER BY "deviceId"` — ~1 017 rows a
+     * call on the live hub, 14–54 calls a minute — and its callers then filtered
+     * the result in JS. The two filters that CAN be pushed down are here:
+     *
+     *  - `deviceIds` becomes a `whereIn`. The viewer's linked-devices panel asks
+     *    about ~8 named ids; it was answered by reading the whole ledger. An
+     *    EMPTY set reads nothing at all rather than degrading to "everything" —
+     *    a request for no devices is a request, not an omission.
+     *  - `slim` becomes a column projection, {@link DEVICE_ROWS_SLIM_COLUMNS}.
+     *
+     * `isCamera` is deliberately NOT one of them — see that constant's note and
+     * `device-row-store-filtered.spec.ts`.
+     */
+    listFleet(opts: {
+        readonly deviceIds?: readonly number[];
+        readonly slim?: boolean;
+    }): Promise<readonly DeviceRow[]>;
     /**
      * The device an addon knows as `stableId`, or `null`.
      *

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@camstack/system",
-  "version": "1.2.135",
+  "version": "1.2.136",
   "description": "Core addon for CamStack — builtins, pipeline, process management, auth, logging, events",
   "keywords": [
     "camstack",