@camstack/types 1.2.392 → 1.2.394

package/dist/notification/media-image.d.ts

@@ -7,7 +7,7 @@
  * one event and a boxed scene on the next depending on what had landed. The
  * picture is now rendered at send time from a clean frame, and the rule says
  * only what it wants to SEE: `image` (`scene-boxes` | `crop` | `clean` |
- * `none`) plus `showTriggerZone`.
+ * `none`) plus `showTriggerZone` and `showSubjectPath` (D903).
  *
  * This module is the only reader of the legacy triple. The rule store applies
  * {@link normalizeNcMediaPolicy} on load (a READ projection, like the retired
@@ -53,12 +53,19 @@ export interface NcMediaRuleSubject extends NcRuleSectionSubject {
 }
 /**
  * The stored shape of a media policy: `image` set, the legacy triple gone.
+ * `showSubjectPath` survives on a kind with a tracked subject and a picture.
  * `showTriggerZone` survives only where it can be drawn — a zone trigger and a
  * mode other than `crop`/`none`; a legacy `zoneCrop` on a zone rule becomes it.
  * Every other field (gif, clip, rolls, speed, profile, linked cameras) is
  * carried through untouched. Pure; never throws.
  */
 export declare function normalizeNcMediaPolicy(media: NcMediaPolicy, rule: NcMediaRuleSubject): NcMediaPolicy;
+/**
+ * True when a rule of this kind has a TRACKED subject whose path can be drawn
+ * (`showSubjectPath`): the kinds whose subject owns a region of the frame. A
+ * sound owns none, and a kind that carries no media has no picture.
+ */
+export declare function subjectHasPath(kind: NcRuleKind): boolean;
 /**
  * Why a media policy cannot be SAVED on this rule, or null. Server-side and
  * editor alike: `showTriggerZone` on a rule whose trigger is not a zone, and a

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@camstack/types",
-  "version": "1.2.392",
+  "version": "1.2.394",
   "description": "Shared types, interfaces, and model catalogs for the CamStack detection ecosystem",
   "keywords": [
     "camstack",