@camstack/types 1.2.414 → 1.2.415

package/dist/capabilities/camera-grid-layout.cap.d.ts

@@ -78,7 +78,7 @@ declare const GridLayoutCellSchema: z.ZodObject<{
  *
  * A grid's `high` composes its sources' `high` and its `low` their `low`, so a
  * profile is on offer only when EVERY source can serve it. The refusal NAMES
- * the sources, because "this grid has no low" is not a finding — "615 has no
+ * the sources, because "this grid has no low" is not a finding — "101 has no
  * low" is, and it is the one an operator can act on.
  */
 declare const GridProfileOfferSchema: z.ZodObject<{

package/dist/capabilities/device-history.cap.d.ts

@@ -385,7 +385,7 @@ export declare const deviceHistoryCapability: {
         }, z.core.$strip>>>, import("./capability-definition.js").CapabilityMethodKind>;
         /**
          * A NODE's series. The subject is `forNodeId`, never `nodeId`: a top-level
-         * `nodeId` is the cap ROUTING key, and `nodeId: 'little-unraid'` sent the
+         * `nodeId` is the cap ROUTING key, and `nodeId: 'agent-a'` sent the
          * read to that agent, which hosts no device-history.
          */
         readonly listNodeSeries: import("./capability-definition.js").CapabilityMethodSchema<z.ZodObject<{

package/dist/capabilities/device-manager.cap.d.ts

@@ -790,7 +790,7 @@ export declare const deviceManagerCapability: {
          *  The room's ICON travels with the rename, including when `from` was
          *  never registered — otherwise it orphans on a key no location carries
          *  any more. A merge keeps the TARGET's icon when it has one: renaming
-         *  "Sala" into "Salone" moves devices into Salone, it does not restyle
+         *  "Sala" into "Hall" moves devices into Hall, it does not restyle
          *  it. */
         readonly renameLocation: import("./capability-definition.js").CapabilityMethodSchema<z.ZodObject<{
             from: z.ZodString;
@@ -861,7 +861,7 @@ export declare const deviceManagerCapability: {
             description: z.ZodNullable<z.ZodString>;
         }, z.core.$strip>, z.ZodVoid, "mutation">;
         /** Every SITE ZONE — a named part of the property that groups locations
-         *  ("Zona notte" holds the bedrooms). One call answers the whole picture:
+         *  ("Night zone" holds the bedrooms). One call answers the whole picture:
          *  key, the label as typed, the icon, and the locations inside.
          *
          *  Together, because a surface that asked for membership separately could

package/dist/capabilities/notification-rules.cap.d.ts

@@ -4476,8 +4476,8 @@ export type NcAlarmSensors = z.infer<typeof NcAlarmSensorsSchema>;
  * own `sustainSeconds` (29 s on this hub), so its clip is anchored well in the
  * past — and the other source, the recordings, cannot cover a recent moment:
  * measured against `recording.getAvailability` for a 10 s window at several
- * anchors, full coverage arrived at −18 s on device 590 and −26 s on 615 and
- * 617. That edge is a PHASE of the 10-second segment cycle, not a number. The
+ * anchors, full coverage arrived at −18 s on device 104 and −26 s on 101 and
+ * 102. That edge is a PHASE of the 10-second segment cycle, not a number. The
  * ring therefore has to hold the moment until the recordings can take it over:
  * the worst measured phase (26 s) plus the confirmation lag (29 s) is 55 s, and
  * 60 is the round number above it.

package/dist/capabilities/osd-manager.cap.d.ts

@@ -11,7 +11,7 @@ import { type InferProvider } from './capability-definition.js';
  * This cap owns the other half: a per-(camera, slot) BINDING that says
  * which value feeds the slot, how it is formatted, and under which
  * conditions it is shown at all. Named TEMPLATES combine many device
- * fields into one overlay string (Scrypted OSD Manager parity).
+ * fields into one overlay string (plugin catalog OSD Manager parity).
  */
 /**
  * How a parser token expands one binding. Not stored on the binding —

package/dist/capabilities/pipeline-analytics.cap.d.ts

@@ -7470,7 +7470,7 @@ export declare const pipelineAnalyticsCapability: {
          * audio, stopping at the first hit — so on the live hub, where object
          * events own no media of their own and 299 883 of 300 559 media rows are
          * motion-owned, EVERY object event resolved to its motion namesake. A
-         * track from 17:34 on camera 615 was served a snapshot from 22:35 eleven
+         * track from 17:34 on camera 101 was served a snapshot from 22:35 eleven
          * days earlier, silently.
          *
          * D476 had already disambiguated the KEY (`motion:` vs `object:`); this is

package/dist/capabilities/pipeline-runner.cap.d.ts

@@ -931,7 +931,7 @@ export declare const pipelineRunnerCapability: {
          *
          * The periodic recheck (`occupancyRecheckSec`, 300 s) exists to watch a
          * still scene. It is the wrong instrument for a QUESTION that has just been
-         * asked: on device 617 a parked car's departure was observed, a departure
+         * asked: on device 102 a parked car's departure was observed, a departure
          * strike was armed — and then the motion session ended, the strike decayed
          * after its 30 s TTL, and the next periodic look arrived up to five minutes
          * later with nothing left to confirm. Every one of those departures was

package/dist/capabilities/ptz.cap.d.ts

@@ -110,9 +110,9 @@ declare const PtzOptionsSchema: z.ZodObject<{
  * Reolink preset 0, Hikvision preset '1', Dahua preset 1 -- and on this fleet
  * not one of the three cameras honours its own:
  *
- *   592  Videocamera camera Daniel (reolink)   preset 0 holds "stanza"
- *   1438 Videocamera dispensa (hikvision)      preset 1 holds "Credenza"
- *   3836 Videocamera studio (amcrest)          preset 1 holds "Preset1"
+ *   107  Camera camera Carol (reolink)   preset 0 holds "stanza"
+ *   1438 Camera dispensa (hikvision)      preset 1 holds "Credenza"
+ *   3836 Camera studio (amcrest)          preset 1 holds "Preset1"
  *
  * So `goHome` meant "go wherever the operator happened to save in slot 0 or 1",
  * and two of the three swallowed the failure in a bare `catch`. For autotrack

package/dist/capabilities/recording-export.cap.d.ts

@@ -31,7 +31,7 @@ export declare const ExportSpeedSchema: z.ZodNumber;
  * on a 10 h window holding 29,393 s of footage every range landed late by the
  * gap accumulated before it — up to 6,607 s, well past EOF. Nothing matched,
  * the video was a uniform timelapse, and the log line reported the five ranges
- * that had been ASKED for (2026-08-13, export `57d14363`, camera 615).
+ * that had been ASKED for (2026-08-13, export `57d14363`, camera 101).
  *
  * Relative and not absolute epoch, because an absolute epoch would make every
  * call site responsible for the same subtraction.

package/dist/capabilities/scene-monitor.cap.d.ts

@@ -13,7 +13,7 @@ import { type InferNativeProvider } from './capability-definition.js';
  * which put a "Scenes" tab on one camera's detail page. That is the wrong shape
  * for the thing: a scene is a standing question about the property ("is the bin
  * still out"), and the operator's question is "which of my scenes have tripped",
- * across every camera at once — not "what does camera 617 think". Buried one
+ * across every camera at once — not "what does camera 102 think". Buried one
  * camera deep it also could not be found. The surface is now a top-level admin
  * page (`/scenes`, `pages/Scenes.tsx`) that lists every scene on every camera and
  * picks the camera inside the create flow, the same shape Events and Faces have.

package/dist/capabilities/stream-signals.cap.d.ts

@@ -5,7 +5,7 @@ import { DeviceType } from '../device/device-type.js';
  * The signals a device can emit to WAKE its own stream.
  *
  * A camera whose stream is built on demand sleeps until something asks for it,
- * and "something" cannot be a consumer that is merely attached — a Frigate-style
+ * and "something" cannot be a consumer that is merely attached — a external-catalog
  * puller holds a session open for ever, and treating that as demand would keep
  * a battery camera awake for ever, which is the whole thing the battery is for
  * (D173). So the wake has to come from the CAMERA: an event it noticed by

package/dist/capabilities/videoclips.cap.d.ts

@@ -19,7 +19,7 @@ import { type InferProvider } from './capability-definition.js';
  * device's SOURCES are its BINDINGS: `deviceManager.getBindings(deviceId)` is
  * what says a provider serves this camera, never the set of addons that
  * happen to have registered the capability somewhere in the cluster. That is
- * what stopped one addon appearing three times on 592 — as the device's
+ * what stopped one addon appearing three times on 107 — as the device's
  * native provider, as the hub-local registration and as an
  * `<addonId>@<nodeId>` one (D554 amended 2026-09-20).
  *
@@ -203,7 +203,7 @@ export type ClipPlayback = z.infer<typeof ClipPlaybackSchema>;
  * camera has no recordings", which is the defect this whole line of work is
  * about: a battery camera nobody woke (`sleeping`), a camera that could not be
  * reached at all (`unreachable`, also what a provider that THREW reports), a
- * camera whose SD card is not mounted (`no-storage`, measured on 640 —
+ * camera whose SD card is not mounted (`no-storage`, measured on 106 —
  * `HddInfo mount 0`, honestly nothing to list rather than "no clips"), and a
  * camera whose OWN index disagrees with its OWN calendar (`index-empty`,
  * measured on 618: the calendar marks 3–20 September, days 6–20 list zero

package/dist/capabilities/viewer-ui.cap.d.ts

@@ -20,7 +20,7 @@ export declare const viewerUiCapability: {
          * `getStaticDir` leaks a hub filesystem path.
          *
          * ⚠ Checked before gating: the VIEWER app IS used by a non-admin user
-         * (`roberta`), but it never calls `viewerUi.*` over tRPC. The static SPA
+         * (`bob`), but it never calls `viewerUi.*` over tRPC. The static SPA
          * it loads is served by the plain `GET /viewer/*` Fastify route in
          * `main.ts`, which reads `staticDir`/`indexPath` from a module-level
          * cache populated ONCE at boot via `capRegistry.getSingletonForNode`

package/dist/catalogs/index.d.ts

@@ -1,5 +1,5 @@
 export * from './coco-classmap.js';
-export * from './frigate-plus-classmap.js';
+export * from './plus-catalog-classmap.js';
 export * from './root-model-supply.js';
 export * from './sensor-active-state.js';
 export * from './audio-classmap.js';

package/dist/catalogs/{frigate-plus-classmap.d.ts → plus-catalog-classmap.d.ts}

@@ -3,11 +3,11 @@ import type { RootStepSupply } from '../types/models.js';
 /** A macro a detection catalog classMap may resolve to. */
 export type ClassMapMacroTarget = (typeof CLASS_MAP_MACRO_TARGETS)[number];
 /**
- * Raw Frigate+ label → detection macro. Every label of the documented
- * Frigate+ base set (docs.frigate.video/plus, verified 2026-08-21) is either
- * here or in {@link FRIGATE_PLUS_UNMAPPED_LABELS}, with the reason it is not.
+ * Raw plus catalog label → detection macro. Every label of the documented
+ * plus catalog base set (docs.frigate.video/plus, verified 2026-08-21) is either
+ * here or in {@link PLUS_CATALOG_UNMAPPED_LABELS}, with the reason it is not.
  *
- * Why this exists: a Frigate+ import used to carry NO classMap, so it inherited
+ * Why this exists: a plus catalog import used to carry NO classMap, so it inherited
  * the step's `COCO_TO_MACRO` (`preserveOriginal: false`) and the executor
  * dropped every label COCO does not name — deer, raccoon, fox, squirrel, goat,
  * rabbit, skunk, kangaroo, possum, rodent, school_bus, garbage_truck and even
@@ -15,11 +15,11 @@ export type ClassMapMacroTarget = (typeof CLASS_MAP_MACRO_TARGETS)[number];
  * label as `originalClass` whenever the map resolves it, so the fine identity
  * survives under the macro.
  */
-export declare const FRIGATE_PLUS_TO_MACRO: Readonly<Record<string, ClassMapMacroTarget>>;
+export declare const PLUS_CATALOG_TO_MACRO: Readonly<Record<string, ClassMapMacroTarget>>;
 /**
- * Frigate+ labels deliberately left OUT of {@link FRIGATE_PLUS_TO_MACRO}.
+ * plus catalog labels deliberately left OUT of {@link PLUS_CATALOG_TO_MACRO}.
  *
- * - `attribute`: Frigate+ emits these INSIDE a parent box (a face inside a
+ * - `attribute`: plus catalog emits these INSIDE a parent box (a face inside a
  *   person, a plate or a carrier logo on a vehicle). Mapping one to its
  *   parent's macro would spawn a second, overlapping track for the same
  *   subject. `face` and `license_plate` are instead declared as CROP supplies
@@ -27,46 +27,46 @@ export declare const FRIGATE_PLUS_TO_MACRO: Readonly<Record<string, ClassMapMacr
  *   it, when the face / plate step uses the root model.
  * - `no-macro`: an object with no detection macro to live under.
  */
-export declare const FRIGATE_PLUS_UNMAPPED_LABELS: Readonly<Record<string, 'attribute' | 'no-macro'>>;
+export declare const PLUS_CATALOG_UNMAPPED_LABELS: Readonly<Record<string, 'attribute' | 'no-macro'>>;
 /**
- * The per-model classMap for a Frigate / Frigate+ detector, derived from ITS
- * labelmap: each label resolves through {@link FRIGATE_PLUS_TO_MACRO} first,
- * then `COCO_TO_MACRO` (Frigate's default model ships the COCO-91 labelmap, so
+ * The per-model classMap for a plus catalog / plus catalog detector, derived from ITS
+ * labelmap: each label resolves through {@link PLUS_CATALOG_TO_MACRO} first,
+ * then `COCO_TO_MACRO` (plus catalog's default model ships the COCO-91 labelmap, so
  * a preset import may carry either vocabulary). A label neither knows is left
  * out, and `preserveOriginal: false` drops it in the executor — the same
- * contract as the COCO map, now with the Frigate+ vocabulary in it.
+ * contract as the COCO map, now with the plus catalog vocabulary in it.
  */
-export declare function buildFrigateClassMap(labels: readonly string[]): DetectionCatalogClassMap;
-/** The label-derived fields of a Frigate catalog entry. */
-export interface FrigateLabelFields {
+export declare function buildPlusCatalogClassMap(labels: readonly string[]): DetectionCatalogClassMap;
+/** The label-derived fields of a plus catalog catalog entry. */
+export interface PlusCatalogLabelFields {
     readonly classMap: DetectionCatalogClassMap;
     readonly suppliesSteps?: readonly RootStepSupply[];
 }
 /**
- * Everything a Frigate / Frigate+ entry derives from ITS OWN labelmap: the
+ * Everything a plus catalog / plus catalog entry derives from ITS OWN labelmap: the
  * classMap and the steps it can supply (D730) — label and crop kinds alike.
- * Every Frigate builder spreads this at import, so the two cannot be derived
+ * Every plus catalog builder spreads this at import, so the two cannot be derived
  * from different label lists, and no family is assumed to carry a label it
  * does not list.
  */
-export declare function frigateLabelFields(labels: readonly string[]): FrigateLabelFields;
+export declare function plusCatalogLabelFields(labels: readonly string[]): PlusCatalogLabelFields;
 /**
- * Per-class confidence-floor defaults of an imported stock Frigate detector
+ * Per-class confidence-floor defaults of an imported stock plus catalog detector
  * (D738): its per-detection `min_score` default, 0.5, for every class. Its
  * track-level `threshold` (the median of a track's recent scores) has no
  * counterpart in CamStack's per-detection floors and is not carried.
  */
-export declare const FRIGATE_STOCK_CLASS_FLOORS: Readonly<Record<string, number>>;
+export declare const PLUS_CATALOG_STOCK_CLASS_FLOORS: Readonly<Record<string, number>>;
 /**
- * Per-class floor defaults of an imported Frigate+ detector (D738): the
- * documented starting `min_score` values for Frigate+ models, which score
+ * Per-class floor defaults of an imported plus catalog detector (D738): the
+ * documented starting `min_score` values for plus catalog models, which score
  * higher than the stock ones (person 0.65, car 0.65, cat 0.65, dog 0.70). The
  * macro `animal` takes the lower of its classes, so no class is cut above its
  * documented value.
  */
-export declare const FRIGATE_PLUS_CLASS_FLOORS: Readonly<Record<string, number>>;
+export declare const PLUS_CATALOG_CLASS_FLOORS: Readonly<Record<string, number>>;
 /**
- * The `defaultClassFloors` an imported Frigate entry carries: the import's
+ * The `defaultClassFloors` an imported plus catalog entry carries: the import's
  * own, when it states them, else the defaults of its kind. A fresh object.
  */
-export declare function frigateDefaultClassFloors(kind: 'stock' | 'plus', carried?: Readonly<Record<string, number>>): Record<string, number>;
+export declare function plusCatalogDefaultClassFloors(kind: 'stock' | 'plus', carried?: Readonly<Record<string, number>>): Record<string, number>;

package/dist/catalogs/root-model-supply.d.ts

@@ -3,9 +3,9 @@
  * detector can supply from its own output, how, and whether the camera uses it.
  *
  * A root detector's labels can already be the effect a step exists to produce:
- * a Frigate+ model emits `deer`, `car`, `package`, a COCO model emits `dog`,
+ * a plus catalog model emits `deer`, `car`, `package`, a COCO model emits `dog`,
  * `bus`. Some also emit the CHILD boxes a detail step exists to find: a
- * Frigate+ `license_plate` inside a car, a `face` inside a person. Every root
+ * plus catalog `license_plate` inside a car, a `face` inside a person. Every root
  * model DECLARES what it can supply (`ModelCatalogEntry.suppliesSteps`),
  * derived from its own labelmap and classMap by {@link deriveRootSupplies} —
  * never assumed per family. Whether a camera USES that is the step's own
@@ -128,7 +128,7 @@ export interface SupplyClassMap {
  * - label kind: a label counts for a step only when the classMap sends it to
  *   that step's macro AND it names a vocabulary entry. Every root is judged
  *   the same way — a COCO model supplies the animal classifier with the six
- *   species COCO names, exactly as a Frigate+ model supplies seven.
+ *   species COCO names, exactly as a plus catalog model supplies seven.
  * - crop kind: the labelmap carries one of the step's root labels. Those
  *   labels are deliberately left out of the classMap, so they never make a
  *   track of their own.

package/dist/client.js

@@ -23243,7 +23243,7 @@ var NcConditionsSchema = zod.z.object({
 	* with the list under it is worse than no switch (D62).
 	*
 	* MEMBERS ARE FACE-GALLERY `Identity.id`s (uuid), not display names. A name is
-	* renameable, and a rule authored on "Gianluca" went silently dark the moment
+	* renameable, and a rule authored on "Alice" went silently dark the moment
 	* the operator fixed the spelling. The id reaches the record on
 	* `LabelAttribution.identityId`; the name is what the editor shows and what
 	* `{{label}}` renders.
@@ -23807,7 +23807,7 @@ var NcRulePatchSchema = NcRuleInputSchema.partial().extend({
 	* A rule scoped to one camera and one zone silently became a rule that
 	* matches EVERY event on EVERY camera, and lost its `media` policy
 	* (zoneCrop / gif / clip / frame) and its `priority` at the same time. Seen
-	* live on 2026-08-12: a rule scoped to device 617 fired on 590 and 615
+	* live on 2026-08-12: a rule scoped to device 102 fired on 104 and 101
 	* within a minute of a two-field patch.
 	*
 	* So every defaulted field is re-declared here WITHOUT its default. The
@@ -25002,7 +25002,7 @@ var ClipSchema = zod.z.object({
 	* {@link MAX_CLIP_EVENT_IDS}. Empty on footage-only clips.
 	*
 	* Bounded because it is not a payload the surface pages through: one visit on
-	* device 615 carried 2 345 ids, and `eventIds` was 99% of a 153 KB
+	* device 101 carried 2 345 ids, and `eventIds` was 99% of a 153 KB
 	* camera-day. Read {@link eventCount} for the true total.
 	*/
 	eventIds: zod.z.array(zod.z.string()).optional(),
@@ -25147,7 +25147,7 @@ var ClipPlaybackSchema = zod.z.object({
 * camera has no recordings", which is the defect this whole line of work is
 * about: a battery camera nobody woke (`sleeping`), a camera that could not be
 * reached at all (`unreachable`, also what a provider that THREW reports), a
-* camera whose SD card is not mounted (`no-storage`, measured on 640 —
+* camera whose SD card is not mounted (`no-storage`, measured on 106 —
 * `HddInfo mount 0`, honestly nothing to list rather than "no clips"), and a
 * camera whose OWN index disagrees with its OWN calendar (`index-empty`,
 * measured on 618: the calendar marks 3–20 September, days 6–20 list zero
@@ -25461,7 +25461,7 @@ DeviceType.Camera, method(zod.z.object({
 	*
 	* It was optional, documented as "absent means the device's BOUND
 	* provider, which is CamStack on every camera". No code implemented
-	* that. Measured on the live hub 2026-09-20 — device 592, bound to
+	* that. Measured on the live hub 2026-09-20 — device 107, bound to
 	* `recorder` AND `provider-reolink` — a bare call with `limit: 3`
 	* answered SIX rows, three from each source, merged newest-first:
 	* `device-collection-dispatch.ts` simply left the fan-out un-narrowed,
@@ -25854,7 +25854,7 @@ var ExportSpeedSchema = zod.z.number().min(.25).max(32);
 * on a 10 h window holding 29,393 s of footage every range landed late by the
 * gap accumulated before it — up to 6,607 s, well past EOF. Nothing matched,
 * the video was a uniform timelapse, and the log line reported the five ranges
-* that had been ASKED for (2026-08-13, export `57d14363`, camera 615).
+* that had been ASKED for (2026-08-13, export `57d14363`, camera 101).
 *
 * Relative and not absolute epoch, because an absolute epoch would make every
 * call site responsible for the same subtraction.
@@ -28943,7 +28943,7 @@ var LABEL_CONDITION_IDS = new Set(["sensorKinds"]);
 * maps COCO onto the macro and drops the rest). A sub-type therefore names a key
 * that does not exist — the counter is 0 forever and the rule cannot fire.
 *
-* Live cost, 2026-08-12: two rules on device 617 were authored with `car`
+* Live cost, 2026-08-12: two rules on device 102 were authored with `car`
 * because this picker offered the whole taxonomy. They were silent for a day.
 */
 var COUNT_CLASS_CONDITION_IDS = new Set(["occupancy"]);
@@ -30305,7 +30305,7 @@ var STATE_SUMMARY_SECTION_VARS = [
 	{
 		name: "summaryStreams",
 		label: "Summary: streams offline",
-		example: "Ingresso (high) — since 06:40",
+		example: "Front door (high) — since 06:40",
 		kinds: ["stream-offline", "stream-online"]
 	},
 	{
@@ -30323,13 +30323,13 @@ var STATE_SUMMARY_SECTION_VARS = [
 	{
 		name: "summaryDetection",
 		label: "Summary: cameras detecting nothing",
-		example: "Ingresso — since 05:10",
+		example: "Front door — since 05:10",
 		kinds: ["detection-blind"]
 	},
 	{
 		name: "summaryNodes",
 		label: "Summary: nodes",
-		example: "little-unraid — offline since 03:00",
+		example: "agent-a — offline since 03:00",
 		kinds: [
 			"node-offline",
 			"node-online",
@@ -30413,7 +30413,7 @@ var NC_TEMPLATE_VARS = [
 	{
 		name: "camera",
 		label: "Camera",
-		example: "Ingresso",
+		example: "Front door",
 		group: "subject",
 		families: ["rule", "timelapse"],
 		systemEventKinds: [...DEVICE_EVENTS, "export-completed"]
@@ -30581,7 +30581,7 @@ var NC_TEMPLATE_VARS = [
 	{
 		name: "rule",
 		label: "Rule name",
-		example: "Ingresso notte",
+		example: "Front door notte",
 		group: "rule",
 		families: [
 			"rule",
@@ -30682,7 +30682,7 @@ var NC_TEMPLATE_VARS = [
 	{
 		name: "deviceName",
 		label: "Device",
-		example: "Ingresso",
+		example: "Front door",
 		group: "system",
 		families: ["rule"],
 		fields: [...RULE_TEXT],
@@ -30692,7 +30692,7 @@ var NC_TEMPLATE_VARS = [
 	{
 		name: "locations",
 		label: "Intrusion locations",
-		example: "Ingresso, Corridoio, Salone",
+		example: "Front door, Hallway, Hall",
 		group: "system",
 		families: ["rule"],
 		fields: [...RULE_TEXT],
@@ -30702,7 +30702,7 @@ var NC_TEMPLATE_VARS = [
 	{
 		name: "deviceId",
 		label: "Device id",
-		example: "617",
+		example: "102",
 		group: "system",
 		families: ["rule"],
 		fields: [...RULE_TEXT],
@@ -30790,7 +30790,7 @@ var NC_TEMPLATE_VARS = [
 	{
 		name: "nodeName",
 		label: "Node name",
-		example: "little-unraid",
+		example: "agent-a",
 		group: "system",
 		families: ["rule"],
 		fields: [...RULE_TEXT],
@@ -30811,7 +30811,7 @@ var NC_TEMPLATE_VARS = [
 		name: "devices",
 		label: "Devices",
 		description: "node-inference-unavailable: the affected cameras, comma-joined. Alarm arm / arming / refusal: HOW MANY devices are armed (or open).",
-		example: "Ingresso, Garage",
+		example: "Front door, Garage",
 		group: "system",
 		families: ["rule"],
 		fields: [...RULE_TEXT],
@@ -31012,7 +31012,7 @@ var NC_TEMPLATE_VARS = [
 		name: "nodes",
 		label: "Nodes",
 		description: "Comma-joined node ids, when an update spans more than one — the single-node case names it through {{nodeId}} instead. `incomingFromUpdateAvailable` (event-intake.ts) fills `nodes` from ONE shared textParams object for both addon- and server-update-available, exactly like packageName/currentVersion/latestVersion/count — only the shipped TEXT (system.server-update-available.body.onNodes) reads it today, but the var is real on both kinds.",
-		example: "hub, little-unraid",
+		example: "hub, agent-a",
 		group: "system",
 		families: ["rule"],
 		fields: [...RULE_TEXT],
@@ -31123,7 +31123,7 @@ var NC_TEMPLATE_VARS = [
 	{
 		name: "title",
 		label: "Export or alert title",
-		example: "Ingresso 08:00",
+		example: "Front door 08:00",
 		group: "system",
 		families: ["rule"],
 		fields: [...RULE_TEXT],
@@ -31237,7 +31237,7 @@ var NC_TEMPLATE_VARS = [
 		name: "names",
 		label: "Device names",
 		description: "Armed / arming: the Active devices (or every skipped name when none are Active). Refusal: the open sensors.",
-		example: "Ingresso, Garage",
+		example: "Front door, Garage",
 		group: "system",
 		families: ["rule"],
 		fields: [...RULE_TEXT],
@@ -31285,7 +31285,7 @@ var NC_TEMPLATE_VARS = [
 		name: "bypassedNames",
 		label: "Bypassed sensors",
 		description: "Sensors the operator armed around because they were open.",
-		example: "Finestra veranda",
+		example: "Finestra porch",
 		group: "system",
 		families: ["rule"],
 		fields: [...RULE_TEXT],
@@ -32102,7 +32102,7 @@ var TimelapseRuleInputSchema = zod.z.object({
 * 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.
 */
 var DEFAULT_TIMELAPSE_PREVIEW_TEXT = "Timelapse {{camera}}";