@camstack/types 1.2.282 → 1.2.284

package/dist/index.js

@@ -1,7 +1,7 @@
 Object.defineProperty(exports, Symbol.toStringTag, { value: "Module" });
-const require_sleep = require("./sleep-DCbD8sdg.js");
-const require_event_category = require("./event-category-MbnB-6AN.js");
-const require_composition = require("./composition-DG4jVTfB.js");
+const require_sleep = require("./sleep-G4F3X9X_.js");
+const require_event_category = require("./event-category-DmS_tLsU.js");
+const require_composition = require("./composition-w3gBWMer.js");
 const require_err_msg = require("./err-msg-Dx2Kor0g.js");
 const require_enums = require("./enums.js");
 let zod = require("zod");
@@ -2538,7 +2538,7 @@ var RecordingTriggersSchema = zod.z.object({
 	*
 	* Cosa vuol dire "alto" dipende dal TIPO di device e non è deciso qui:
 	* `SOURCE_CAP_ACTIVE_FIELD` (`catalogs/sensor-active-state.ts`) è LA tabella,
-	* la stessa che il virtual-doorbell usa dal 2026-08-05. Ed è il FRONTE, non
+	* la stessa del campanello composto (D671). Ed è il FRONTE, non
 	* il livello: un contatto trovato già aperto al riavvio del runner non fa
 	* registrare.
 	*/
@@ -14541,8 +14541,8 @@ var deviceManagerCapability = {
 		* (`value` / `missing` / `failed`, see {@link WrapperActivationReadSchema}).
 		*
 		* The narrow read of the durable authority behind `getBindings`: a
-		* consumer that must know what the operator PERSISTED (virtual-doorbell,
-		* before it drops a press) asks this instead of pulling device-manager's
+		* consumer that must know what the operator PERSISTED (before it drops
+		* work on the strength of an unbind) asks this instead of pulling device-manager's
 		* whole addon store through `addonSettingsRaw.getGlobal` — which answered
 		* `{}` on every isolated-engine hub and so never worked (D675). It reads
 		* ONE row (the activation map, ~1.6 KB), never the ~625 KB store.
@@ -14833,107 +14833,6 @@ var deviceManagerCapability = {
 	}
 };
 //#endregion
-//#region src/capabilities/doorbell.cap.ts
-/**
-* Doorbell button cap. Two kinds of providers coexist behind this cap
-* name (same pattern as `snapshot`):
-*
-*   - **Native** providers: registered per-device by device-driver
-*     addons via `ctx.registerNativeCap` — either on a
-*     `DeviceType.Button` accessory with `role: DeviceRole.Doorbell`,
-*     or directly on the camera (Reolink registers at camera level).
-*     Emits an `onPressed` event every time the firmware pushes a
-*     ring; status tracks the last press and a pressCount since start
-*     (diagnostic).
-*
-*   - **Wrapper** provider: the `virtual-doorbell` system builtin
-*     (`@camstack/system/builtins/doorbell`). Turns ANY binary-ish
-*     device (contact / switch / event-emitter …) into a doorbell for
-*     a camera. `defaultActive: false` — the operator explicitly binds
-*     it per camera in the device-bindings UI, then picks the source
-*     device + trigger in the per-device settings.
-*
-* The DeviceEventPropagator re-emits `onPressed` on the camera parent
-* — subscribers listening at the camera level receive ring events
-* with `via[]` populated. No code on the parent needed.
-*/
-var DoorbellStatusSchema = zod.z.object({
-	/** Ms epoch of the last press. null = never observed since this provider started. */
-	lastPressedAt: zod.z.number().nullable(),
-	/** Counter since provider start. Resets on reboot. Useful for metrics/debug. */
-	pressCountSinceStart: zod.z.number()
-});
-var DoorbellPressEventSchema = zod.z.object({
-	deviceId: zod.z.number(),
-	timestamp: zod.z.number()
-});
-/**
-* The `doorbell-source` extension slot's editable value (D648): the camera's
-* virtual-doorbell trigger devices, exactly what the wrapper's
-* `doorbellSources` persists (as `{ deviceId }` records).
-*/
-var DoorbellSourceSlotValueSchema = zod.z.object({ deviceIds: zod.z.array(zod.z.number().int().positive()) });
-/**
-* The `doorbell-source` slot — which devices ring this camera's VIRTUAL
-* doorbell, owned by the `virtual-doorbell` wrapper over its
-* `doorbellSources` store (D648). A source rings when one of its
-* `SOURCE_CAPS` rises. Whether the wrapper is bound to the camera at all is a
-* different authority (`deviceManager.setWrapperActive`, D62) — the slot
-* reports it, it never writes it.
-*/
-var DOORBELL_SOURCE_SLOT = {
-	id: "doorbell-source",
-	label: "Doorbell trigger devices",
-	description: "Any of these becoming active rings this camera's virtual doorbell: a binary sensor when it goes active, a switch when it turns on.",
-	shape: "association",
-	hostDeviceTypes: [require_err_msg.DeviceType.Camera],
-	sourceCaps: require_composition.SOURCE_CAPS,
-	cardinality: "many",
-	value: DoorbellSourceSlotValueSchema
-};
-var doorbellCapability = {
-	name: "doorbell",
-	scope: "device",
-	deviceNative: true,
-	mode: "singleton",
-	kind: "wrapper",
-	defaultActive: false,
-	deviceTypes: [require_err_msg.DeviceType.Button, require_err_msg.DeviceType.Camera],
-	extensionSlots: [DOORBELL_SOURCE_SLOT],
-	methods: {},
-	events: { 
-	/**
-	* Fires once per physical press. Reolink delivers via Baichuan
-	* push (`ReolinkSimpleEvent.type === 'doorbell'`). There is no
-	* release/duration — it's a pulse.
-	*/
-onPressed: {
-		data: DoorbellPressEventSchema,
-		fromState: {
-			field: "lastPressedAt",
-			on: "advance"
-		}
-	} },
-	status: {
-		schema: DoorbellStatusSchema,
-		kind: "push"
-	},
-	/**
-	* Runtime-state slice — last press timestamp + lifetime press count.
-	* Mirrored by the kernel and readable via
-	* `device.state.doorbell.value`. UIs can show "last ring 5m ago"
-	* without subscribing.
-	*/
-	runtimeState: DoorbellStatusSchema,
-	/**
-	* Runtime-state durability: **restored** — a monotonic accumulator: the slice IS the record. `lastPressedAt` is content here, not a clock, so it is deliberately NOT volatile.
-	*
-	* See `RuntimeStateDurability`. Enforced by
-	* `scripts/check-runtime-state-durability.ts`.
-	*/
-	durability: "restored"
-};
-//#endregion
 //#region src/generated/extension-slots.ts
 /**
 * AUTO-GENERATED by scripts/generate-extension-slots.ts — DO NOT EDIT.
@@ -14943,25 +14842,18 @@ onPressed: {
 * caps' descriptors and value schemas — never the caps barrel — so
 * `device-extension.cap.ts` can import this module without a cycle.
 *
-* Coverage: 2 slot(s).
+* Coverage: 1 slot(s).
 */
 /** Every declared slot id, in table order. */
-var EXTENSION_SLOT_IDS = ["doorbell-source", "linked-devices"];
+var EXTENSION_SLOT_IDS = ["linked-devices"];
 var ExtensionSlotIdSchema = zod.z.enum(EXTENSION_SLOT_IDS);
-var EXTENSION_SLOTS = {
-	"doorbell-source": {
-		descriptor: DOORBELL_SOURCE_SLOT,
-		declaringCap: "doorbell",
-		hostDeviceTypes: [require_err_msg.DeviceType.Camera]
-	},
-	"linked-devices": {
-		descriptor: LINKED_DEVICES_SLOT,
-		declaringCap: "device-manager",
-		hostDeviceTypes: [require_err_msg.DeviceType.Camera]
-	}
-};
+var EXTENSION_SLOTS = { "linked-devices": {
+	descriptor: LINKED_DEVICES_SLOT,
+	declaringCap: "device-manager",
+	hostDeviceTypes: [require_err_msg.DeviceType.Camera]
+} };
 /** A slot's editable value, discriminated on `slot`. */
-var ExtensionSlotValueSchema = zod.z.discriminatedUnion("slot", [DoorbellSourceSlotValueSchema.extend({ slot: zod.z.literal("doorbell-source") }), LinkedDevicesSlotValueSchema.extend({ slot: zod.z.literal("linked-devices") })]);
+var ExtensionSlotValueSchema = zod.z.discriminatedUnion("slot", [LinkedDevicesSlotValueSchema.extend({ slot: zod.z.literal("linked-devices") })]);
 /** Every device type at least one slot is offered on — `device-extension`'s `deviceTypes`. */
 var EXTENSION_HOST_DEVICE_TYPES = [require_err_msg.DeviceType.Camera];
 //#endregion
@@ -14970,8 +14862,8 @@ var EXTENSION_HOST_DEVICE_TYPES = [require_err_msg.DeviceType.Camera];
 * `device-extension` — ONE place to see and author what a device is extended
 * with by OTHER devices (D648).
 *
-* **A contract, not a store.** Every slot (`linked-devices`, `doorbell-source`)
-* is declared by the cap that owns the function (`extensionSlots` in its
+* **A contract, not a store.** Every slot (today one: `linked-devices`) is
+* declared by the cap that owns the function (`extensionSlots` in its
 * `*.cap.ts`, D4) and SERVED by the addon that already owns its store, over
 * that store and its existing write path. This cap persists nothing and has no config method (guarded by
 * `scripts/check-extension-slots.ts`): D62 applied to the whole feature, and
@@ -14980,7 +14872,7 @@ var EXTENSION_HOST_DEVICE_TYPES = [require_err_msg.DeviceType.Camera];
 * **Shape.** A device-scoped wrapper COLLECTION, the D554 shape `videoclips`
 * uses: `resolveCapMount` gives it the `device-scoped` mount and
 * `requireDeviceCollection` dispatches it. Its providers are the slot owners
-* (device-manager, virtual-doorbell, …), and a device's sources are its
+* (today device-manager alone), and a device's sources are its
 * bindings (step 0 of `getBindings`, derived, persisted nowhere).
 *
 *  - `listSources` — one row per provider, the D554 source-listing convention
@@ -15040,10 +14932,11 @@ var ExtensionSlotSourceSchema = zod.z.object({
 });
 /**
 * A DIFFERENT authority that gates whether the slot's sources do anything —
-* reported read-only, named, never written through this contract (D62). The
-* virtual doorbell's sources ring only while the wrapper is bound to the
-* camera, and that binding belongs to `deviceManager.setWrapperActive`.
-* `unknown` means the gate could not be read; it is not "inactive" (D315).
+* reported read-only, named, never written through this contract (D62) — e.g.
+* a slot whose sources act only while a wrapper is bound to the host, a
+* binding that belongs to `deviceManager.setWrapperActive`. No slot reports
+* one today (`linked-devices` answers `null`). `unknown` means the gate could
+* not be read; it is not "inactive" (D315).
 */
 var ExtensionSlotActivationSchema = zod.z.object({
 	state: zod.z.enum([
@@ -15060,7 +14953,7 @@ var ExtensionSlotStateSchema = zod.z.object({
 	/** `<source>:<slotId>` — the routing key for `listCandidates` / `setSlot`. */
 	slotRef: zod.z.string(),
 	slot: ExtensionSlotIdSchema,
-	/** Names the store written (D62), e.g. `virtual-doorbell:doorbellSources`. */
+	/** Names the store written (D62), e.g. `device-manager:_linkedDeviceIds`. */
 	authority: zod.z.string(),
 	activation: ExtensionSlotActivationSchema.nullable(),
 	value: ExtensionSlotValueSchema,
@@ -15264,8 +15157,8 @@ var deviceStateCapability = {
 		* Canonical cross-layer WRITE for one cap-keyed slice. Used by
 		* everyone who needs to publish runtime state for a device:
 		* device providers (via `BaseDevice.runtimeState.setCapState`
-		* which delegates here), system-scope addons (e.g. the pipeline
-		* runner writing the `motion` slice on phase transitions), and
+		* which delegates here), system-scope addons (e.g. the orchestrator
+		* writing a camera's effective `motion` slice, D696), and
 		* direct cap-router callers in tests.
 		*
 		* Behavior on the hub:
@@ -19331,17 +19224,25 @@ var NcScheduleSchema = zod.z.object({
 */
 var NcSystemEventDeliveryModeSchema = zod.z.enum(["instant", "summary"]);
 /**
+* How a summary window is SENT (D698): `rule` (absent) = ONE notification with
+* every section; `section` = one notification per section with something to
+* say (an unavailable section included), each titled by its section.
+*/
+var NcStateSummarySplitSchema = zod.z.enum(["rule", "section"]);
+/**
 * `summary`: the rule sends NOTHING per event. When a window of `schedule`
 * CLOSES, it sends one notification with the current state of its kinds
 * (low batteries, consumables to replace, devices offline, updates
-* available, ...), after its own filters. Nothing to report sends nothing.
+* available, ...), after its own filters — or, with `split: 'section'`
+* (D698), one notification per section. Nothing to report sends nothing.
 * The schedule is the ordinary `NcSchedule` (weekly windows, IANA timezone,
 * midnight crossing); the send time is each window's END. Refused on the
 * `alarm` family, which stays instant (`systemEventDeliveryProblems`).
 */
 var NcSystemEventDeliverySchema = zod.z.discriminatedUnion("mode", [zod.z.object({ mode: zod.z.literal("instant") }), zod.z.object({
 	mode: zod.z.literal("summary"),
-	schedule: NcScheduleSchema
+	schedule: NcScheduleSchema,
+	split: NcStateSummarySplitSchema.optional()
 })]);
 /** Fuzzy plate matcher — OCR noise makes exact match useless (spec row 12/13). */
 var NcPlateMatcherSchema = zod.z.object({
@@ -20388,11 +20289,23 @@ var NcStateSummaryPreviewSectionSchema = zod.z.object({
 	reason: zod.z.string().optional()
 });
 /**
+* One notification a previewed summary would send (D698): the whole summary on
+* a `rule` split (no `section`), one section's on a `section` split.
+*/
+var NcStateSummaryPreviewRowSchema = zod.z.object({
+	section: zod.z.string().optional(),
+	/** The section's name on a per-section row; every reported section's, joined, on a combined one. */
+	title: zod.z.string(),
+	text: zod.z.string(),
+	count: zod.z.number().int().nonnegative()
+});
+/**
 * The summary a rule would send now. `empty` = nothing to report and every
 * section read: such a summary is NOT sent. `dropped` counts the open states
 * the rule's own filters (or a camera mute) left out, by reason.
 * `excludedGroups` names the kind groups selected that have no state to report
-* (backups & exports).
+* (backups & exports). `split` and `rows` (D698) say how it would be sent —
+* optional, so an older hub's answer still parses.
 */
 var NcStateSummaryPreviewSchema = zod.z.object({
 	empty: zod.z.boolean(),
@@ -20400,7 +20313,9 @@ var NcStateSummaryPreviewSchema = zod.z.object({
 	text: zod.z.string(),
 	sections: zod.z.array(NcStateSummaryPreviewSectionSchema),
 	dropped: zod.z.record(zod.z.string(), zod.z.number().int().nonnegative()),
-	excludedGroups: zod.z.array(zod.z.string())
+	excludedGroups: zod.z.array(zod.z.string()),
+	split: NcStateSummarySplitSchema.optional(),
+	rows: zod.z.array(NcStateSummaryPreviewRowSchema).optional()
 });
 var NcTestResultSchema = zod.z.object({
 	recordId: zod.z.string(),
@@ -22193,12 +22108,27 @@ var CameraSensorRefSchema = zod.z.object({
 function cameraSensorRefKey(ref) {
 	return `${ref.addonId}/${ref.stableId}`;
 }
-/** CS-1 accepts exactly one mode; CS-2 (D673) widens it to confirm / replace. */
-var CameraSensorsModeSchema = zod.z.enum(["in-addition"]);
-var CameraSensorsConfigSchema = zod.z.object({
-	mode: CameraSensorsModeSchema,
-	sensors: zod.z.array(CameraSensorRefSchema).min(1).max(8)
-}).superRefine((value, ctx) => {
+/**
+* A sensor's mode (D673). `in-addition`: its motion is the camera's motion too.
+* `replace`: its motion is the camera's, and while one is READY the camera's
+* own motion no longer counts on its own. `confirm`: while one is READY the
+* camera's own motion counts only while a confirm sensor is active — with or
+* without a replace sensor (spec C2, the controller's ruling on Q1).
+*/
+var CameraSensorModeSchema = zod.z.enum([
+	"in-addition",
+	"confirm",
+	"replace"
+]);
+/** A stored sensor with no mode — every CS-1 row — is in addition. */
+var DEFAULT_CAMERA_SENSOR_MODE = "in-addition";
+var CameraSensorEntrySchema = CameraSensorRefSchema.extend({ mode: CameraSensorModeSchema.default(DEFAULT_CAMERA_SENSOR_MODE) });
+/**
+* A camera's attached sensors. A CS-1 row carried an envelope
+* `mode: 'in-addition'`: `z.object` drops it on parse, and the PARSED value is
+* what the write stores (D672 rule 3), so it is never written again.
+*/
+var CameraSensorsConfigSchema = zod.z.object({ sensors: zod.z.array(CameraSensorEntrySchema).min(1).max(8) }).superRefine((value, ctx) => {
 	const seen = /* @__PURE__ */ new Set();
 	value.sensors.forEach((ref, index) => {
 		const key = cameraSensorRefKey(ref);
@@ -22210,39 +22140,41 @@ var CameraSensorsConfigSchema = zod.z.object({
 		seen.add(key);
 	});
 });
-var RefFields = {
+/** Every attachment names its mode; an older orchestrator that does not is in addition. */
+var AttachmentFields = {
 	addonId: zod.z.string(),
-	stableId: zod.z.string()
+	stableId: zod.z.string(),
+	mode: CameraSensorModeSchema.default(DEFAULT_CAMERA_SENSOR_MODE)
 };
 var CameraSensorAttachmentSchema = zod.z.discriminatedUnion("state", [
 	zod.z.object({
-		...RefFields,
+		...AttachmentFields,
 		state: zod.z.literal("ready"),
 		deviceId: zod.z.number(),
 		name: zod.z.string(),
 		caps: zod.z.array(zod.z.string()).readonly()
 	}),
 	zod.z.object({
-		...RefFields,
+		...AttachmentFields,
 		state: zod.z.literal("offline"),
 		deviceId: zod.z.number(),
 		name: zod.z.string(),
 		reason: zod.z.enum(["offline", "disabled"])
 	}),
 	zod.z.object({
-		...RefFields,
+		...AttachmentFields,
 		state: zod.z.literal("missing"),
 		reason: zod.z.string()
 	}),
 	zod.z.object({
-		...RefFields,
+		...AttachmentFields,
 		state: zod.z.literal("unsupported"),
 		deviceId: zod.z.number(),
 		name: zod.z.string(),
 		reason: zod.z.string()
 	}),
 	zod.z.object({
-		...RefFields,
+		...AttachmentFields,
 		state: zod.z.literal("unreadable"),
 		reason: zod.z.string()
 	})
@@ -22255,17 +22187,49 @@ var CameraSensorAttachmentSchema = zod.z.discriminatedUnion("state", [
 * say.
 */
 var CameraSensorsNotForwardedSchema = zod.z.enum(["onboard-not-listed", "no-active-detection"]);
+/** Whether the camera's OWN motion counts on its own (D673 C2), from its READY sensors (C3). */
+var CameraOwnMotionSchema = zod.z.enum([
+	"always",
+	"when-confirmed",
+	"never"
+]);
+/** Confirm / Replace cannot suppress this camera's motion: its provider still emits it directly (D673 C13). */
+var CameraSensorsNotEnforcedSchema = zod.z.enum(["provider-not-split"]);
+/**
+* The camera's OWN onboard motion (D696): the raw input the bridge combines,
+* never the effective value. The camera's `motion` slice is the effective one,
+* so a view of the camera's own row reads this.
+* - `atMs`: when the bridge received the camera's last own edge.
+* - `detected`: evaluated WHEN THE STATUS IS ASKED — the last edge said `true`
+*   AND it is younger than the window the bridge counts the camera's own motion
+*   for (`motionCooldownMs`, floored at two sustain ticks). A camera that never
+*   sends a clear (heartbeats only) therefore reads `false` once no push came
+*   within the window; a status read is a snapshot, so a live view re-asks.
+* Absent = this orchestrator has not received the camera's own motion since it
+* started (unknown, never "quiet"), or an orchestrator older than D696.
+*/
+var CameraRawLevelSchema = zod.z.object({
+	detected: zod.z.boolean(),
+	atMs: zod.z.number()
+});
 var CameraSensorsStatusSchema = zod.z.discriminatedUnion("state", [
-	zod.z.object({ state: zod.z.literal("not-configured") }),
+	zod.z.object({
+		state: zod.z.literal("not-configured"),
+		cameraLevel: CameraRawLevelSchema.optional()
+	}),
 	zod.z.object({
 		state: zod.z.literal("unreadable"),
-		reason: zod.z.string()
+		reason: zod.z.string(),
+		cameraLevel: CameraRawLevelSchema.optional()
 	}),
 	zod.z.object({
 		state: zod.z.literal("configured"),
-		mode: CameraSensorsModeSchema,
+		cameraLevel: CameraRawLevelSchema.optional(),
 		sensors: zod.z.array(CameraSensorAttachmentSchema).readonly(),
-		notForwarded: CameraSensorsNotForwardedSchema.optional()
+		/** Absent = an orchestrator older than CS-2: it does not say (D315). */
+		cameraMotion: CameraOwnMotionSchema.optional(),
+		notForwarded: CameraSensorsNotForwardedSchema.optional(),
+		notEnforced: CameraSensorsNotEnforcedSchema.optional()
 	})
 ]);
 /** What a camera reads before its first settings read ANSWERED (D315). */
@@ -26609,8 +26573,10 @@ var RunnerCameraConfigSchema = zod.z.object({
 	* - `analyzer`: ML/frame-diff motion detection (motion-wasm or other
 	*   analyzer providers) running on decoded frames in this runner.
 	* - `onboard`: camera-native motion pushes (Reolink Baichuan, ONVIF
-	*   analytics). The provider emits ProviderMotion
-	*   events; the orchestrator forwards to `reportMotion`.
+	*   analytics). The provider emits its raw push as `ProviderMotion`
+	*   (D673); the orchestrator's camera-sensors bridge re-emits the camera's
+	*   effective motion as `MotionOnMotionChanged`, which is what reaches
+	*   `reportMotion`.
 	*/
 	motionSources: MotionSourcesSchema.default(["analyzer"]),
 	/**
@@ -26975,7 +26941,15 @@ var RunnerLocalLoadSchema = zod.z.object({
 		hasGpu: zod.z.boolean(),
 		inferenceBackend: zod.z.string().optional(),
 		cpuCores: zod.z.number().optional()
-	})
+	}),
+	/**
+	* Who writes a camera's `motion` runtime slice (D696). `'orchestrator'`: this
+	* runner never writes it. ABSENT = a runner older than D696, which still
+	* writes the slice from its phase machine; the orchestrator does not write
+	* while any runner node is absent-or-unanswered, so one slice never has two
+	* writers.
+	*/
+	motionSliceWriter: zod.z.literal("orchestrator").optional()
 });
 /**
 * Aggregate runtime metrics for the runner's whole local pool. Mirrors the
@@ -34837,6 +34811,72 @@ onStatusChanged: { data: zod.z.object({
 	volatileStateFields: ["lastChangedAt"]
 };
 //#endregion
+//#region src/capabilities/doorbell.cap.ts
+var DoorbellStatusSchema = zod.z.object({
+	/** Ms epoch of the last press. null = never observed since this provider started. */
+	lastPressedAt: zod.z.number().nullable(),
+	/** Counter since provider start. Resets on reboot. Useful for metrics/debug. */
+	pressCountSinceStart: zod.z.number()
+});
+var DoorbellPressEventSchema = zod.z.object({
+	deviceId: zod.z.number(),
+	timestamp: zod.z.number()
+});
+/**
+* Doorbell button cap. Two kinds of provider serve it, and to every consumer
+* they are the same cap:
+*
+*   - **Native** providers, registered per device by a driver addon through
+*     `ctx.registerNativeCap` — a `DeviceType.Button` accessory with
+*     `role: DeviceRole.Doorbell`, or the camera itself (Reolink registers at
+*     camera level). They emit `onPressed` on every firmware ring.
+*   - **A composed doorbell** (D670, D671): a camera's customization gives it
+*     the cap, its `lastPressedAt` rising from the sources the operator
+*     assigned in Customize → Doorbell, and the composer emits `onPressed`
+*     from that field's advance (`fromState`).
+*
+* The DeviceEventPropagator re-emits `onPressed` on the camera parent.
+*/
+var doorbellCapability = {
+	name: "doorbell",
+	scope: "device",
+	deviceNative: true,
+	mode: "singleton",
+	deviceTypes: [require_err_msg.DeviceType.Button, require_err_msg.DeviceType.Camera],
+	methods: {},
+	events: { 
+	/**
+	* Fires once per physical press. Reolink delivers via Baichuan
+	* push (`ReolinkSimpleEvent.type === 'doorbell'`). There is no
+	* release/duration — it's a pulse.
+	*/
+onPressed: {
+		data: DoorbellPressEventSchema,
+		fromState: {
+			field: "lastPressedAt",
+			on: "advance"
+		}
+	} },
+	status: {
+		schema: DoorbellStatusSchema,
+		kind: "push"
+	},
+	/**
+	* Runtime-state slice — last press timestamp + lifetime press count.
+	* Mirrored by the kernel and readable via
+	* `device.state.doorbell.value`. UIs can show "last ring 5m ago"
+	* without subscribing.
+	*/
+	runtimeState: DoorbellStatusSchema,
+	/**
+	* Runtime-state durability: **restored** — a monotonic accumulator: the slice IS the record. `lastPressedAt` is content here, not a clock, so it is deliberately NOT volatile.
+	*
+	* See `RuntimeStateDurability`. Enforced by
+	* `scripts/check-runtime-state-durability.ts`.
+	*/
+	durability: "restored"
+};
+//#endregion
 //#region src/capabilities/enum-sensor.cap.ts
 /**
 * Enum-state sensor — a string value picked from a finite option set.
@@ -37284,11 +37324,11 @@ authKey: zod.z.string().optional() }), zod.z.object({
 /**
 * How long after a camera's last rising edge `pipeline-analytics` closes the
 * motion EPISODE row it kept open for it (D475) — "il delay della cap", in
-* the operator's words. One authority for the whole system: every provider
-* that seeds `autoClearAfterMs` on a `Camera` device writes this SAME
-* constant while `detected: true` (never its own number — Hikvision used to
-* seed its internal 3 s inactivity timer here, which is a different clock for
-* a different purpose), and `MotionEpisodeTracker` imports it directly rather
+* the operator's words. One authority for the whole system: the writer of a
+* `Camera` device's slice (the orchestrator, D696) writes this SAME constant
+* in `autoClearAfterMs` while `detected: true` (never a camera's own clock —
+* Hikvision used to seed its internal 3 s inactivity timer here, a different
+* clock for a different purpose), and `MotionEpisodeTracker` imports it directly rather
 * than reading the live cap value on the hot path. A `Sensor` device (HA
 * binary sensor, Homematic) gets a genuine push both ways and has no episode
 * to close on a timer, so it writes `null`, never this constant.
@@ -37299,9 +37339,9 @@ var MotionStatusSchema = zod.z.object({
 	/** Ms epoch of the last detected-true observation. Null if never detected. */
 	lastDetectedAt: zod.z.number().nullable(),
 	/**
-	* `MOTION_CLOSE_AFTER_MS` while `detected: true` on a `Camera` device,
-	* `null` while false and on every `Sensor` device (D475) — see that
-	* constant's doc for the one-authority rule.
+	* `MOTION_CLOSE_AFTER_MS` while `detected: true` on a `Camera` device (the
+	* orchestrator writes it, D696), `null` while false and on every `Sensor`
+	* device (D475) — see that constant's doc for the one-authority rule.
 	*
 	* ## Reading this field still arms nothing
 	*
@@ -37319,34 +37359,31 @@ var MotionStatusSchema = zod.z.object({
 	* `addon-export-alexa/src/motion-clear-hold.ts` and
 	* `addon-export-hap`'s `RESET_DEBOUNCE_MS` both do.
 	*
-	* ## Who writes it
+	* ## Who writes it (D696)
 	*
-	* - **Cameras** — the runner's phase machine, `active → watching` on
-	*   `cooldown_expired`, which then writes this slice with
-	*   `detected: false` (`handlePhaseChanged` in
-	*   `pipeline-runner/index.ts`). It produces the FALLING edge, which
-	*   matters most for the sources that only ever push a rising one:
-	*   Reolink emits `MotionOnMotionChanged { detected: true }` and never
-	*   a false.
-	* - **Sensors** (Home Assistant binary sensors, Homematic) — the
-	*   provider pushes the false itself, from the upstream system's own
-	*   state change. No phase machine is involved.
+	* - **Cameras** — the orchestrator, and nothing else. It writes the camera's
+	*   EFFECTIVE motion (`addon-pipeline-orchestrator`
+	*   `camera-sensors/motion-slice.ts`), alongside the effective
+	*   `MotionOnMotionChanged` it emits or receives: the camera-sensors bridge
+	*   for a split camera, an unsplit emitter's direct event, the analyzer and
+	*   device activity, as the camera's `motionSources` counts them. A source
+	*   that never sends a clear falls one window after its last `true`.
+	*   `lastDetectedAt` moves only on an effective rise. No camera provider
+	*   writes this slice (not even a boot seed), and neither does the runner's
+	*   phase machine: its phase is "a session is attached" for every on-motion
+	*   session, not motion, and it now has its own `DetectionPhaseTransition`.
+	*   A provider's `isDetected` answers from the hub's slice.
+	* - **Sensors** (Home Assistant binary sensors, Homematic, Matter, Alexa
+	*   imports) — the provider pushes both edges itself, from the upstream
+	*   system's own state change. That is the sensor's own fact.
 	*
-	* ### The phase machine is CANONICAL, not sole — and that is a defect
+	* `scripts/check-onboard-motion-emitters.ts` refuses any other writer of a
+	* `motion` slice; each sensor writer is a named exemption.
 	*
-	* An earlier revision of this docblock (mine, 2026-09-12) claimed the
-	* phase machine is the sole writer for a camera. It is not.
-	* `hikvision-camera.ts:3464` and `amcrest-camera.ts:445` both call
-	* `setCapSlice(motionCapability, …)` on their own rising edge, and
-	* Hikvision's comment says why: it read THIS docblock, agreed the
-	* runner is canonical, and wrote anyway to avoid per-tick churn. So
-	* two authorities can disagree about one slice, which this repo
-	* forbids, and the doc said otherwise — which is worse than saying
-	* nothing, because it reads as verification.
-	*
-	* This predates D475 and is not fixed there: the fix touches every
-	* camera provider. Recorded in D475's Consequences. Do not restore the
-	* "sole writer" wording without also removing the other writers.
+	* This replaces the D475 §4 rule ("the phase machine is the sole writer").
+	* That rule was never true: Hikvision and Amcrest wrote the slice raw beside
+	* it, every provider seeded it at boot, and every session left it
+	* `detected: true` after its detach.
 	*/
 	autoClearAfterMs: zod.z.number().nullable()
 });
@@ -37418,11 +37455,12 @@ onMotionChanged: { data: MotionOnMotionChangedDataSchema } },
 	*/
 	runtimeState: MotionStatusSchema,
 	/**
-	* Runtime-state durability: **session** — every writer of this slice
+	* Runtime-state durability: **session** — the writer of this slice
 	* writes only on an EDGE, so a restored `detected: true` would stay
 	* frozen until the next one instead of being corrected. The next edge
-	* re-publishes the real state. (On who the writers are, and why there
-	* is more than one, see `autoClearAfterMs` above.)
+	* re-publishes the real state, and the orchestrator re-publishes every
+	* camera when it starts writing (D696; on who writes it, see
+	* `autoClearAfterMs` above).
 	*
 	* See `RuntimeStateDurability`. Enforced by
 	* `scripts/check-runtime-state-durability.ts`.
@@ -40405,8 +40443,7 @@ var ptzAutotrackCapability = {
 	deviceNative: true,
 	mode: "singleton",
 	/**
-	* Two kinds of provider behind one name, the same shape `snapshot` and
-	* `doorbell` use:
+	* Two kinds of provider behind one name, the same shape `snapshot` uses:
 	*
 	*  - **Native**: the camera's own firmware autotrack, registered per device by
 	*    the driver when the probe says it exists (Reolink: yes; Hikvision:
@@ -40414,7 +40451,7 @@ var ptzAutotrackCapability = {
 	*  - **Wrapper**: the emulated implementation (`@camstack/system`'s `autotrack` builtin),
 	*    which follows a subject with `ptz.move` pulses driven by the detection
 	*    pipeline. `defaultActive: false` — the operator binds it per camera in
-	*    the bindings UI, exactly as `virtual-doorbell` is bound.
+	*    the bindings UI.
 	*
 	* The binding chooses WHICH implementation answers; `setEnabled` stays the
 	* one switch for the function either way. A camera never has both driving its
@@ -46637,10 +46674,10 @@ function feederCustomizationExample(sources) {
 //#endregion
 //#region src/composition/presets/doorbell-feature.ts
 /**
-* The doorbell of a camera as a customization (D671). ONE builder: the
-* virtual-doorbell migration and the admin UI's "Use as doorbell" preset both
-* call it, so a preset can never write a shape the migration would refuse as
-* "an unrelated existing block".
+* The doorbell of a camera as a customization (D671). ONE builder: the admin
+* UI's Customize → Doorbell card writes every doorbell feature through it, and
+* edits one only when it is exactly what this builds (`isDoorbellPresetFeature`)
+* — a composed doorbell has one canonical shape.
 */
 /** A rise closer than this to the previous one is the same press (D671). */
 var DOORBELL_RISE_DEBOUNCE_MS = 2e3;
@@ -46657,7 +46694,7 @@ function doorbellFeatureSources(source, boundCaps) {
 		}];
 	});
 }
-/** The D671 feature, byte for byte what the migration writes. Throws on zero sources. */
+/** The canonical D671 doorbell feature. Throws on zero sources. */
 function buildDoorbellCompositionFeature(input) {
 	const sources = [...input.sources].toSorted((a, b) => `${a.source.addonId}/${a.source.stableId}#${a.cap}`.localeCompare(`${b.source.addonId}/${b.source.stableId}#${b.cap}`));
 	if (sources.length === 0) throw new Error("doorbell composition needs at least one source");
@@ -65625,6 +65662,18 @@ var STATE_SUMMARY_VARS = [
 		systemEventKinds: [...SUMMARISABLE],
 		systemEventDeliveries: ["summary"]
 	},
+	{
+		name: "summarySection",
+		label: "Summary: this section",
+		description: "The section a per-section summary row is about (D698); on a summary sent as one message, every section it reports, comma-separated.",
+		example: "Batterie scariche",
+		group: "system",
+		families: ["rule"],
+		fields: [...RULE_TEXT],
+		kinds: ["system"],
+		systemEventKinds: [...SUMMARISABLE],
+		systemEventDeliveries: ["summary"]
+	},
 	...STATE_SUMMARY_SECTION_VARS.map((v) => ({
 		name: v.name,
 		label: v.label,
@@ -66467,6 +66516,15 @@ function systemEventSummaryScheduleOf(rule) {
 	const delivery = rule.systemEventDelivery;
 	return delivery?.mode === "summary" ? delivery.schedule : null;
 }
+/**
+* How a summary rule's window is sent (D698): `section` = one notification per
+* section; absent (every rule before D698) and any non-summary rule = `rule`.
+* The ONE reader — the scheduler, the rule test, the preview and both editors.
+*/
+function systemEventSummarySplitOf(rule) {
+	const delivery = rule.systemEventDelivery;
+	return delivery?.mode === "summary" ? delivery.split ?? "rule" : "rule";
+}
 /** Absent and `instant` are the same answer: a notification per event. */
 function isSystemEventSummaryRule(rule) {
 	return systemEventSummaryScheduleOf(rule) !== null;
@@ -67107,6 +67165,35 @@ function readTimelapseGeneratedAt(rule, deviceId) {
 	return rule.lastGeneratedAt ?? 0;
 }
 //#endregion
+//#region src/pipeline/motion-ownership.ts
+function cameraOwnsMotionViaSensor(motionSources) {
+	return motionSources.some((s) => s !== "analyzer");
+}
+//#endregion
+//#region src/device/hub-motion-read.ts
+async function readHubMotionDetected(deviceState, deviceId) {
+	let slice;
+	try {
+		slice = await deviceState.getCapSlice.query({
+			deviceId,
+			capName: "motion"
+		});
+	} catch (err) {
+		const reason = err instanceof Error ? err.message : String(err);
+		throw new Error(`motion state of device ${deviceId} is unreadable: ${reason}`, { cause: err });
+	}
+	const detected = slice?.["detected"];
+	if (typeof detected !== "boolean") throw new Error(`motion state of device ${deviceId} is not published yet (unknown)`);
+	return detected;
+}
+//#endregion
+//#region src/pipeline/provider-motion.ts
+/** The motion event's data without `triggeredBy`: only the bridge names a trigger. */
+var ProviderMotionDataSchema = MotionOnMotionChangedDataSchema.omit({ triggeredBy: true });
+function providerMotionEvent(source, data) {
+	return require_sleep.createEvent(require_event_category.EventCategory.ProviderMotion, source, data);
+}
+//#endregion
 //#region src/pipeline/step-format-runnable.ts
 /** True when `model` ships a build for `format`. */
 function hasBuild(model, format) {
@@ -67996,8 +68083,8 @@ function bestLocationMatch(externalName, existing, threshold = .8) {
 * So `entry.providerAddonId === this.ctx.id` is silently, permanently false
 * for a builtin — and only for a builtin, which is why it survives a green
 * suite whose fake supplies the bare id. That is exactly how camera 615's
-* virtual doorbell latched `unbound` for twelve hours on 2026-08-07 while its
-* binding was intact ([D72](../../../../docs/decisions/adr-0072.md)).
+* virtual doorbell (retired since, D671) latched `unbound` for twelve hours on
+* 2026-08-07 while its binding was intact ([D72](../../../../docs/decisions/adr-0072.md)).
 *
 * Route every comparison between `ctx.id` and a registry/store addon id
 * through {@link isSameAddonId}. `scripts/check-addon-id-comparison.ts`
@@ -69423,12 +69510,16 @@ exports.CameraMetricsSchema = CameraMetricsSchema;
 exports.CameraMetricsWithDeviceIdSchema = CameraMetricsWithDeviceIdSchema;
 exports.CameraMotionStatusSchema = CameraMotionStatusSchema;
 exports.CameraOccupancySnapshotForDeviceSchema = CameraOccupancySnapshotForDeviceSchema;
+exports.CameraOwnMotionSchema = CameraOwnMotionSchema;
+exports.CameraRawLevelSchema = CameraRawLevelSchema;
 exports.CameraRecordingModeSchema = CameraRecordingModeSchema;
 exports.CameraRecordingStatusSchema = CameraRecordingStatusSchema;
 exports.CameraSensorAttachmentSchema = CameraSensorAttachmentSchema;
+exports.CameraSensorEntrySchema = CameraSensorEntrySchema;
+exports.CameraSensorModeSchema = CameraSensorModeSchema;
 exports.CameraSensorRefSchema = CameraSensorRefSchema;
 exports.CameraSensorsConfigSchema = CameraSensorsConfigSchema;
-exports.CameraSensorsModeSchema = CameraSensorsModeSchema;
+exports.CameraSensorsNotEnforcedSchema = CameraSensorsNotEnforcedSchema;
 exports.CameraSensorsNotForwardedSchema = CameraSensorsNotForwardedSchema;
 exports.CameraSensorsStatusSchema = CameraSensorsStatusSchema;
 exports.CameraSourceStatusSchema = CameraSourceStatusSchema;
@@ -69568,6 +69659,7 @@ exports.DECLARED_DEVICE_SWEEP_LIMIT = DECLARED_DEVICE_SWEEP_LIMIT;
 exports.DECLARED_INTEGRATION_FIXED_KEY = DECLARED_INTEGRATION_FIXED_KEY;
 exports.DEFAULT_ADDON_PLACEMENT = DEFAULT_ADDON_PLACEMENT;
 exports.DEFAULT_AUDIO_ANALYZER_CONFIG = DEFAULT_AUDIO_ANALYZER_CONFIG;
+exports.DEFAULT_CAMERA_SENSOR_MODE = DEFAULT_CAMERA_SENSOR_MODE;
 exports.DEFAULT_CLUSTER_STEP_MODELS = DEFAULT_CLUSTER_STEP_MODELS;
 exports.DEFAULT_CLUSTER_STEP_SETTINGS = DEFAULT_CLUSTER_STEP_SETTINGS;
 exports.DEFAULT_DECODER_HWACCEL_CONFIG = DEFAULT_DECODER_HWACCEL_CONFIG;
@@ -69609,7 +69701,6 @@ exports.DISPLAY_ICON_KEYS = DISPLAY_ICON_KEYS;
 exports.DISPLAY_ICON_OFFERED_KEYS = DISPLAY_ICON_OFFERED_KEYS;
 exports.DISPLAY_ICON_VOCABULARY = DISPLAY_ICON_VOCABULARY;
 exports.DOORBELL_RISE_DEBOUNCE_MS = DOORBELL_RISE_DEBOUNCE_MS;
-exports.DOORBELL_SOURCE_SLOT = DOORBELL_SOURCE_SLOT;
 exports.DataStoreEngineInfoSchema = EngineInfoSchema;
 exports.DatabaseSnapshotResultSchema = DatabaseSnapshotResultSchema;
 exports.DatabaseSnapshotTableSchema = DatabaseSnapshotTableSchema;
@@ -69654,7 +69745,6 @@ exports.DiscoveredTargetSchema = DiscoveredTargetSchema;
 exports.DiskReconcileJobSchema = DiskReconcileJobSchema;
 exports.DisposerChain = require_sleep.DisposerChain;
 exports.DoorbellPressEventSchema = DoorbellPressEventSchema;
-exports.DoorbellSourceSlotValueSchema = DoorbellSourceSlotValueSchema;
 exports.DoorbellStatusSchema = DoorbellStatusSchema;
 exports.EMBEDDING_MODEL_FAILED = EMBEDDING_MODEL_FAILED;
 exports.EMBEDDING_REQUIREMENTS_FAILED = EMBEDDING_REQUIREMENTS_FAILED;
@@ -70128,8 +70218,10 @@ exports.NcSnoozeInputSchema = NcSnoozeInputSchema;
 exports.NcSnoozeSchema = NcSnoozeSchema;
 exports.NcSnoozeScopeSchema = NcSnoozeScopeSchema;
 exports.NcSnoozeSuppressedSchema = NcSnoozeSuppressedSchema;
+exports.NcStateSummaryPreviewRowSchema = NcStateSummaryPreviewRowSchema;
 exports.NcStateSummaryPreviewSchema = NcStateSummaryPreviewSchema;
 exports.NcStateSummaryPreviewSectionSchema = NcStateSummaryPreviewSectionSchema;
+exports.NcStateSummarySplitSchema = NcStateSummarySplitSchema;
 exports.NcSystemEventConditionSchema = NcSystemEventConditionSchema;
 exports.NcSystemEventDeliveryModeSchema = NcSystemEventDeliveryModeSchema;
 exports.NcSystemEventDeliverySchema = NcSystemEventDeliverySchema;
@@ -70245,6 +70337,7 @@ exports.PrivacyMaskStatusSchema = PrivacyMaskStatusSchema;
 exports.ProfileRtspEntrySchema = require_sleep.ProfileRtspEntrySchema;
 exports.ProfileSlotSchema = require_sleep.ProfileSlotSchema;
 exports.ProfileSlotStatusSchema = require_sleep.ProfileSlotStatusSchema;
+exports.ProviderMotionDataSchema = ProviderMotionDataSchema;
 exports.ProviderStatusSchema = ProviderStatusSchema;
 exports.PtzAutotrackRuntimeStateSchema = PtzAutotrackRuntimeStateSchema;
 exports.PtzAutotrackSettingsSchema = PtzAutotrackSettingsSchema;
@@ -70700,6 +70793,7 @@ exports.builtCapabilityBlockers = builtCapabilityBlockers;
 exports.buttonCapability = buttonCapability;
 exports.cameraCredentialsCapability = cameraCredentialsCapability;
 exports.cameraGridLayoutCapability = cameraGridLayoutCapability;
+exports.cameraOwnsMotionViaSensor = cameraOwnsMotionViaSensor;
 exports.cameraPipelineConfigCapability = cameraPipelineConfigCapability;
 exports.cameraSensorRefKey = cameraSensorRefKey;
 exports.cameraStreamsCapability = cameraStreamsCapability;
@@ -71074,6 +71168,7 @@ exports.pressureSensorCapability = pressureSensorCapability;
 exports.principalMayReachAddon = principalMayReachAddon;
 exports.privacyMaskCapability = privacyMaskCapability;
 exports.procedureAuthKey = procedureAuthKey;
+exports.providerMotionEvent = providerMotionEvent;
 exports.ptzAutotrackCapability = ptzAutotrackCapability;
 exports.ptzCapability = ptzCapability;
 exports.publicEventCategories = require_event_category.publicEventCategories;
@@ -71083,6 +71178,7 @@ exports.readClusterStepModels = readClusterStepModels;
 exports.readClusterStepSettings = readClusterStepSettings;
 exports.readDetailCropConvention = readDetailCropConvention;
 exports.readDeviceStateFrom = readDeviceStateFrom;
+exports.readHubMotionDetected = readHubMotionDetected;
 exports.readMotionTriggeredBy = readMotionTriggeredBy;
 exports.readNativeLeaseOverride = readNativeLeaseOverride;
 exports.readNodePin = require_sleep.readNodePin;
@@ -71204,6 +71300,7 @@ exports.systemEventFilterAppliesToAnyKind = systemEventFilterAppliesToAnyKind;
 exports.systemEventKindNamesOf = systemEventKindNamesOf;
 exports.systemEventKindsOfFamily = systemEventKindsOfFamily;
 exports.systemEventSummaryScheduleOf = systemEventSummaryScheduleOf;
+exports.systemEventSummarySplitOf = systemEventSummarySplitOf;
 exports.systemFamilyOfKind = systemFamilyOfKind;
 exports.systemRuleKindOf = systemRuleKindOf;
 exports.tamperCapability = tamperCapability;