@camstack/types 1.2.414 → 1.2.415

package/dist/interfaces/addon-peer-bytes.d.ts

@@ -46,7 +46,7 @@
  * is preserved by leaving it alone rather than by widening it.
  *
  * **Same host only, refused by name across a node boundary.** The listener
- * binds loopback, so a ticket minted on `little-unraid` names a URL that means
+ * binds loopback, so a ticket minted on `agent-a` names a URL that means
  * something else entirely on the hub. Every ticket therefore carries the
  * {@link PeerBytesTicket.hostNodeId} it was minted on, and
  * {@link AddonPeerBytes.open} refuses `cross-node` when that is not this

package/dist/interfaces/agent.d.ts

@@ -114,7 +114,7 @@ export interface HubHealthAgentCounts {
     /**
      * Node ids of the offline agents. Optional (added later) — consumers
      * must tolerate absence on older hubs. Lets health surfaces name the
-     * degraded node ("node little-unraid not responding") instead of
+     * degraded node ("node agent-a not responding") instead of
      * only counting it.
      */
     readonly offlineIds?: readonly string[];

package/dist/interfaces/birth-decision-ledger.d.ts

@@ -26,7 +26,7 @@
  * ── Why a TABLE and not a log line ─────────────────────────────────────────
  * `logs.query` is an in-memory ring. Measured on the live hub on 2026-09-08 it
  * held 40 000 entries covering 38 minutes — the whole ring is under an hour of
- * fleet traffic. Every question this data is for ("how often, on camera 617,
+ * fleet traffic. Every question this data is for ("how often, on camera 102,
  * over the week the operator complained about") outlives that ring by two
  * orders of magnitude, and a previous investigation in this repo was blocked
  * for precisely this reason. The gate ALREADY writes a log line per decision

package/dist/interfaces/debug-note-archive.d.ts

@@ -35,7 +35,7 @@ import { z } from 'zod';
  *  - A per-device bound multiplies by the fleet — 30 cameras at 500 each is
  *    15 000 rows to protect a corpus that only ever gets read fleet-wide (the
  *    thing being mined is "what keeps going wrong", not "what goes wrong on
- *    617"). One global ceiling is one number to reason about.
+ *    102"). One global ceiling is one number to reason about.
  *  - An AGE bound would delete the corpus for being old, which is the failure
  *    being fixed: a note from six months ago is the most valuable row in the
  *    table precisely because the pattern it describes has had time to repeat.

package/dist/interfaces/inference-engine.d.ts

@@ -28,7 +28,7 @@ interface InferenceInputCommon {
      * A `SharedInferencePool` serves every camera on its
      * `(node, runtime, device)`, so its `inference request timed out` and
      * `worker saturated` lines could describe the pool and nothing else — and
-     * "why is 617 worse than 615?" is the question those lines always get asked.
+     * "why is 102 worse than 101?" is the question those lines always get asked.
      *
      * Omitted by callers with no camera (commands, model loads, the benchmark);
      * the failure line then carries no `deviceId` tag rather than a fabricated

package/dist/interfaces/logging.d.ts

@@ -39,7 +39,7 @@ export interface LogTags {
      * device-manager.
      */
     readonly deviceId?: number;
-    /** Human-readable device name (e.g., 'Salone') */
+    /** Human-readable device name (e.g., 'Hall') */
     readonly deviceName?: string;
     /** Integration ID (e.g., 'int_0001') */
     readonly integrationId?: string;

package/dist/metrics/failure-counters.d.ts

@@ -22,8 +22,8 @@
  *
  * The key is the numeric `deviceId` — the same value every log line in this
  * repo carries as `tags.deviceId`. There is no fleet-total mode and no
- * device-less bucket, because the question is always "why is 617 worse than
- * 615?" and a fleet total cannot answer it. A caller that cannot name the
+ * device-less bucket, because the question is always "why is 102 worse than
+ * 101?" and a fleet total cannot answer it. A caller that cannot name the
  * camera must not note anything: an unnamed per-camera count is
  * indistinguishable from a shared one, which is how one camera's failures
  * quietly become everybody's.

package/dist/node.js

@@ -21,7 +21,7 @@ var __toESM = (mod, isNodeMode, target) => (target = mod != null ? __create(__ge
 	enumerable: true
 }) : target, mod));
 //#endregion
-const require_composition = require("./composition-CSLSFGTO.js");
+const require_composition = require("./composition-DsmkwP9-.js");
 const require_err_msg = require("./err-msg-BhVbr0NX.js");
 let node_crypto = require("node:crypto");
 let node_fs = require("node:fs");
@@ -2049,7 +2049,7 @@ function pinnedFfmpegSpawner(seam, ffmpegBinaryPath, options) {
 * ## Where a claim is made, and where it is released
 *
 * At the spawn site, and nowhere else. It is the only place that knows both
-* halves: the recorder's controller knows it is starting ffmpeg for camera 615
+* halves: the recorder's controller knows it is starting ffmpeg for camera 101
 * profile `high`; the decode coordinator knows the session it is forking a
 * worker for. Nothing has to deduce it afterwards, and no entity needs a
 * global list of which pid belongs to which camera.

package/dist/node.mjs

@@ -1,4 +1,4 @@
-import { At as Fmp4BoxSplitter, Ct as FFMPEG_PATH_ENV, Dt as getFfmpegArtifact, Et as FFMPEG_RELEASE, Ot as getFfmpegDownloadUrl, P as compositionSourceKey, Pt as buildFfmpegArgs, Rt as isSoftwareDecode, Tt as ffmpegBinaryName, a as CUSTOMIZATION_BLOCK_NAME_PREFIX, kt as canonicalHash, wt as chooseFfmpegBinary } from "./composition-BJ8iAZb3.mjs";
+import { At as Fmp4BoxSplitter, Ct as FFMPEG_PATH_ENV, Dt as getFfmpegArtifact, Et as FFMPEG_RELEASE, Ot as getFfmpegDownloadUrl, P as compositionSourceKey, Pt as buildFfmpegArgs, Rt as isSoftwareDecode, Tt as ffmpegBinaryName, a as CUSTOMIZATION_BLOCK_NAME_PREFIX, kt as canonicalHash, wt as chooseFfmpegBinary } from "./composition-kEl9mevu.mjs";
 import { t as errMsg } from "./err-msg-BXKzRBwg.mjs";
 import { createHash, createHmac, randomUUID, timingSafeEqual } from "node:crypto";
 import * as fs from "node:fs";
@@ -2026,7 +2026,7 @@ function pinnedFfmpegSpawner(seam, ffmpegBinaryPath, options) {
 * ## Where a claim is made, and where it is released
 *
 * At the spawn site, and nowhere else. It is the only place that knows both
-* halves: the recorder's controller knows it is starting ffmpeg for camera 615
+* halves: the recorder's controller knows it is starting ffmpeg for camera 101
 * profile `high`; the decode coordinator knows the session it is forking a
 * worker for. Nothing has to deduce it afterwards, and no entity needs a
 * global list of which pid belongs to which camera.

package/dist/notification/timelapse-rule.d.ts

@@ -100,7 +100,7 @@ export type TimelapseRuleInput = z.infer<typeof TimelapseRuleInputSchema>;
  * The caption a rule that never set one gets.
  *
  * Rendered through the ordinary `{{var}}` pass at delivery, so a rule created
- * before this field existed still reads "Timelapse Videocamera ingresso" and
+ * before this field existed still reads "Timelapse Camera front door" and
  * not the literal braces.
  */
 export declare const DEFAULT_TIMELAPSE_PREVIEW_TEXT = "Timelapse {{camera}}";

package/dist/pipeline/root-face-crop.d.ts

@@ -2,7 +2,7 @@
  * The ONE face-scoped crop of a root-supplied face (D731): the rectangle a
  * root model's `face` box is refined in before it can be recognised.
  *
- * A root face box (a Frigate+ `face`) carries no landmarks, and an unaligned
+ * A root face box (a plus catalog `face`) carries no landmarks, and an unaligned
  * crop must never reach the face embedder (D52: one vector index, one crop
  * derivation — and the face gallery's derivation is the landmark alignment).
  * So the box is only a LOCATION: a square around it is cut from the frame's

package/dist/pipeline/second-pass/motion-crop-plan.d.ts

@@ -8,7 +8,7 @@
  * mostly NOT accounted for by a full-frame box. That rule was built to find a
  * subject standing NEXT TO one the detector already sees, and it works.
  *
- * The measurement says the cheaper question is the better one. On camera 615,
+ * The measurement says the cheaper question is the better one. On camera 101,
  * against the production detector (`yolov9m-320-int8`, python+openvino) on the
  * node that runs that camera, over 38 visually confirmed positive frames from
  * six real animal pass-bys: full-frame recall at our animal floor **24%**,

package/dist/pipeline/second-pass/small-subject-recovery.d.ts

@@ -6,13 +6,13 @@
  *
  * The first-level detector sees the frame at its input size (320 px on every
  * hardware-aware default). A 4K frame is reduced 12×: a dog measured at
- * 89–277 px in the source is 7–38 px for the model and is not emitted. Camera 615, six
+ * 89–277 px in the source is 7–38 px for the model and is not emitted. Camera 101, six
  * instants with a dog in the scene, five with no `animal` detection at all —
  * nothing downstream (tracker, gate, notifications) ever saw a subject. The
  * confirmation gate, which re-runs the same detector on a 320 px native crop
  * of the PERSON, found the dog at 0.74–0.91 as `bestIncompatibleClass`. The
  * measurement that decided the constants below is
- * `docs/benchmarks/pipeline-frame-model-eval.md`, case `miss-dog-615`: a
+ * `docs/benchmarks/pipeline-frame-model-eval.md`, case `miss-dog-101`: a
  * 640–800 px native square around the moving region brings the dog to
  * 0.82–0.91 with the SAME 320 model; a 1280 px square loses it again.
  *
@@ -28,7 +28,7 @@
  * ## When it runs — NOT only when the frame is empty
  *
  * The trigger is an UNCOVERED MOTION REGION, deliberately broader than "the
- * full-frame pass found nothing". Camera 615, 2026-09-06 19:54:33 local: the
+ * full-frame pass found nothing". Camera 101, 2026-09-06 19:54:33 local: the
  * gate DID confirm an `animal` birth (bestScore 0.8983) — and the track held
  * 9 positions over 1 666 ms, then coasted out its `maxMissedMs` (4 000 ms) and
  * died at 19:54:39, before the dog reached the Aiuola zone. Both of its object
@@ -183,7 +183,7 @@ export interface RecoverySkipCounts {
  * The pass report counts the passes that RAN, so "the second pass stops running
  * when a person is beside the dog" — a plausible reading of
  * {@link RECOVERY_MAX_REGION_FRAME_FRACTION} and
- * {@link RECOVERY_MIN_UNCOVERED_FRACTION}, and a live hypothesis on camera 615
+ * {@link RECOVERY_MIN_UNCOVERED_FRACTION}, and a live hypothesis on camera 101
  * — could not be confirmed or killed from the logs at all. This classifies the
  * regions a frame offered, against the same predicate the planner filters on.
  */

package/dist/process/child-cost-registry.d.ts

@@ -9,7 +9,7 @@ export interface ChildCostClaimInput {
      * and would turn one camera's cost into everybody's.
      */
     readonly deviceId: number | null;
-    /** What this one child is, in the contributor's own words: `615/high`. */
+    /** What this one child is, in the contributor's own words: `101/high`. */
     readonly unit: string;
     /**
      * Defaults to `measured` — the ordinary case for a child that serves exactly