@camstack/addon-provider-hikvision 1.2.126 → 1.2.131

package/dist/addon.js

@@ -5372,7 +5372,7 @@ var ZodIssueCode = {
 var ZodFirstPartyTypeKind;
 ZodFirstPartyTypeKind || (ZodFirstPartyTypeKind = {});
 //#endregion
-//#region ../types/dist/sleep-COWaSCAi.mjs
+//#region ../types/dist/sleep-PEo0-Fz9.mjs
 /**
 * The audio chunk plane's byte format, and the ONE expansion from a coded
 * window to float samples (D455).
@@ -6508,6 +6508,24 @@ function normalizeAddonInitResult(result) {
 	if (Array.isArray(result)) return { providers: result };
 	return result;
 }
+/** The wire shape of {@link PeerBytesTicket} — see the type for what it is. */
+var PeerBytesTicketSchema = object({
+	/** `http://127.0.0.1:<port>/<token>`. One `GET` takes it. */
+	url: string().min(1),
+	/**
+	* The HOST node this URL means something on — the hub or a named agent,
+	* never a runner. {@link AddonPeerBytes.open} compares it to its own and
+	* refuses `cross-node` by name when they differ, without dialling.
+	*/
+	hostNodeId: string().min(1),
+	expiresAtMs: number().int().nonnegative(),
+	/**
+	* What the producer DECLARED the body to be, when it knows — `null` when it
+	* does not. Never `0` for unknown (D393): a consumer sizing a bound off this
+	* must be able to tell "the producer did not say" from "the body is empty".
+	*/
+	declaredBytes: number().int().nonnegative().nullable()
+});
 /** Shared Zod schemas used across streaming capabilities. */
 var CamProfileSchema = _enum([
 	"high",
@@ -7542,24 +7560,6 @@ object({
 		unreachable: number()
 	})
 });
-/** The wire shape of {@link PeerBytesTicket} — see the type for what it is. */
-var PeerBytesTicketSchema = object({
-	/** `http://127.0.0.1:<port>/<token>`. One `GET` takes it. */
-	url: string().min(1),
-	/**
-	* The HOST node this URL means something on — the hub or a named agent,
-	* never a runner. {@link AddonPeerBytes.open} compares it to its own and
-	* refuses `cross-node` by name when they differ, without dialling.
-	*/
-	hostNodeId: string().min(1),
-	expiresAtMs: number().int().nonnegative(),
-	/**
-	* What the producer DECLARED the body to be, when it knows — `null` when it
-	* does not. Never `0` for unknown (D393): a consumer sizing a bound off this
-	* must be able to tell "the producer did not say" from "the body is empty".
-	*/
-	declaredBytes: number().int().nonnegative().nullable()
-});
 /**
 * Adoption job — the background form of `device-adoption.adopt`.
 *
@@ -7671,7 +7671,7 @@ var AdoptionJobSchema = object({
 * component's original options — detection to the detection-pipeline wrapper
 * binding, audio analysis to its own, recording to `RecordingConfig.enabled`
 * (which was always first-class; the switch was a veneer over
-* `recording.setDeviceConfig`), notifications to a notification-center
+* `recordingArchive.setDeviceConfig`), notifications to a notification-center
 * per-device setting, the two camera planes to their own components.
 *
 * What survives is {@link composeSwitchedOff}: `CameraStatus.switchedOff`, the
@@ -7697,7 +7697,7 @@ var AdoptionJobSchema = object({
 * | `stream-broker` | `deviceManager.setDisabled` | `StreamBrokerManager.reconcileAllCatalogs` releases the brokers; `ensureBroker` refuses re-creation |
 * | `object-detection` | `deviceManager.setWrapperActive('detection-pipeline')` | `PipelineSettingsStore.resolvePipelineForDevice` returns `{ steps: [], audio: null }` |
 * | `audio-analysis` | `deviceManager.setWrapperActive('audio-analysis')` | `AudioSubscriptionController.subscribeAudioStream` returns `null` before opening the stream |
-* | `recording` | `recording.setDeviceConfig` → `RecordingConfig.enabled` | `band-decision.shouldRecord` returns false; the controller detaches the device |
+* | `recording` | `recordingArchive.setDeviceConfig` → `RecordingConfig.enabled` | `band-decision.shouldRecord` returns false; the controller detaches the device |
 * | `notifications` | `notificationRules.setDeviceMuted` | `NotificationCenter.evaluateAndEnqueue` returns before any rule is evaluated |
 * | `privacy-mask` | `privacyMask.setMask({ enabled })` → the CAMERA | the camera blanks the masked regions itself; every stream and recording carries the black boxes |
 * | `device-audio` | `privacyMask.setAudioEnabled` → the CAMERA | the camera stops encoding an audio track at all; every consumer sees silent video |
@@ -11876,87 +11876,6 @@ method(ListInputSchema, array(BrokerInfoSchema$1)), method(GetInputSchema, Broke
 	auth: "admin"
 }), method(GetStateInputSchema, unknown().nullable()), method(_void(), RegistryStatusSchema);
 DeviceType.Camera;
-/**
-* 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
-* 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
-* itself, with no stream running.
-*
-* ## The vocabulary is the PROVIDER'S, not ours
-*
-* Like `consumables`, this cap declares no vocabulary of its own. A provider
-* names each signal with a `code` it chooses and a `label` an operator reads.
-* Reolink offers motion and camera-native detection; another provider may offer
-* a tamper, a doorbell press, a PIR, or something no camera in this fleet has
-* yet. A fixed enum here would mean every new signal is a framework release.
-*
-* It is deliberately NOT derived from the caps a device already binds. Whether
-* a camera CAN push firmware motion is expressed by `motionSources` containing
-* `'onboard'`, and whether it does AI on-camera by the `native-object-detection`
-* binding — but both answer "what drives the detection pipeline", which is a
-* different question from "what may wake a sleeping stream". A camera can do
-* the first and not be trusted with the second, and the operator picks per
-* camera. Two questions, two authorities.
-*
-* ## Availability is not permission
-*
-* `listSignals` says what the device CAN emit. Whether a given signal actually
-* wakes the stream is the operator's per-camera choice, held by the broker
-* alongside the cooldown — see the stream-broker cap's wake settings. A
-* provider declaring a signal is not a provider enabling it.
-*/
-/** One signal a device can emit. */
-var StreamSignalSchema = object({
-	/** Stable id chosen by the provider, e.g. `'motion'`, `'person'`, `'tamper'`. */
-	code: string().min(1),
-	/** What an operator reads in the picker. The provider's own wording. */
-	label: string().min(1),
-	/**
-	* Whether the provider recommends this signal ON when a camera is first set
-	* up. A provider knows which of its signals are cheap and reliable; an
-	* operator should not have to discover that by trial. Reolink recommends
-	* both of its own.
-	*/
-	recommended: boolean()
-});
-var StreamSignalsStatusSchema = object({
-	signals: array(StreamSignalSchema),
-	lastFetchedAt: number()
-});
-var streamSignalsCapability = {
-	name: "stream-signals",
-	scope: "device",
-	deviceNative: true,
-	mode: "singleton",
-	deviceTypes: Object.values(DeviceType),
-	runtimeState: StreamSignalsStatusSchema,
-	/**
-	* Runtime-state durability: **session** — mirrored in RAM, never written.
-	*
-	* The slice holds what the DEVICE says it can emit. That is a probed fact,
-	* not an operator choice: the provider re-declares it on every registration,
-	* so losing it loses nothing and persisting it would freeze an answer the
-	* camera is entitled to change. Measured the same day on the sibling case —
-	* `native-object-detection.supportedClasses` was persisted, and a firmware
-	* class the camera really detected stayed missing for the life of the row
-	* because the fix could not reach it.
-	*
-	* See `RuntimeStateDurability`. Enforced by
-	* `scripts/check-runtime-state-durability.ts`.
-	*/
-	durability: "session",
-	methods: { 
-	/**
-	* What this device can emit. Empty is a valid and common answer — most
-	* cameras have nothing to offer here, and an empty list is what makes the
-	* broker's picker show nothing rather than a false choice.
-	*/
-listSignals: method(_void(), array(StreamSignalSchema).readonly()) }
-};
 /** Stream delivery format. (Relocated from the retired `streaming-engine` cap.) */
 var StreamFormatSchema = _enum([
 	"webrtc",
@@ -13422,6 +13341,210 @@ method(object({ codec: string() }), boolean()), method(_void(), object({
 });
 DeviceType.Camera;
 /**
+* device-admin-link — "this device has a management page of its own, and here
+* is its address".
+*
+* ## Why this is not a `deviceConfig` cap
+*
+* There is nothing to edit. A `deviceConfig` cap (D14) exists so the framework
+* can DERIVE a settings form from `getOptions` + `getStatus` and route a flat
+* patch back through a setter; it costs a `builderId` reducer in
+* `device-config-contribution.ts` and a `*-config-schema.ts` beside it, and it
+* renders a form section. This cap answers ONE question with ONE read and
+* renders a button. Nothing about it is a form, so it carries no `deviceConfig`
+* block, no `settings`, no `runtimeState` and no reducer — exactly like
+* `reboot`, the other pure-RPC device-native cap.
+*
+* ## Absent, and the difference between "no page" and "we cannot say"
+*
+* The two are answered at DIFFERENT layers, on purpose:
+*
+*  - **"We cannot say"** → the provider never registers the cap for that
+*    device. A VeSync humidifier, a Petkit feeder, a Dreame vacuum and a Dreo
+*    fan are reached only through a vendor cloud; there is no address to hand
+*    out and no page to open. A Tuya plug, a Wyze camera and a Gree air
+*    conditioner DO have a LAN IP, and still have no HTTP management page
+*    behind it. None of them register, so `deviceManager.getBindings` never
+*    lists the cap and no surface asks.
+*  - **"This device has no page, and I know that"** → the provider registers
+*    and `getAdminLink` returns `null`. This is the answer for a device whose
+*    sibling DOES have a page: a Reolink battery camera reached over UDP by
+*    `uid` with a blank `host`, an Ecowitt gateway configured in `listener`
+*    transport, a Home Assistant broker authenticated by supervisor token
+*    (which carries no `baseUrl` at all).
+*
+* Both draw NOTHING. A button that opens a browser error is worse than no
+* button, and D62 is the same rule from the other side: an off switch is
+* reported off, never made to look broken. There is no third state where the
+* UI renders a disabled button "because the device might have a page".
+*
+* ## The URL never carries credentials
+*
+* Not in userinfo, not in a query string. Every provider builds through
+* `buildDeviceAdminUrl` (`device-admin-link-url.ts`), which takes host, port,
+* scheme and path as separate arguments — there is no parameter a secret could
+* arrive in — and re-checks its own output for the `scheme://user:pass@` shape
+* that `scripts/check-no-credential-urls-in-fixtures.ts` bans from recorded
+* output. `scripts/check-admin-link-builder-is-the-only-url-source.ts` is what
+* keeps providers from hand-rolling one anyway.
+*
+* This matters here more than anywhere else in the repo, because every provider
+* that knows a device's host knows its PASSWORD too: `{ host, port, username,
+* password }` sit in one object on Hikvision, Amcrest, Reolink and ONVIF alike,
+* and `http://admin:hunter2@192.168.50.139/` is a URL a browser accepts. The
+* camera's own page will ask for its own login. That is correct, and pre-
+* filling it is the operator's business, not ours.
+*
+* ## It is a LAN fact
+*
+* The URL addresses the device where the NODE can see it. It is not proxied,
+* not made reachable from outside, and not sent anywhere. A surface renders it
+* as a link the operator's own browser follows, on the operator's own network,
+* or renders nothing.
+*/
+/**
+* Whose page is it. The distinction is for the OPERATOR, who needs to know
+* before clicking whether he is about to land on a camera's own web server or
+* inside Home Assistant.
+*/
+var AdminLinkTargetEnum = _enum(["device", "integration"]);
+var DeviceAdminLinkSchema = object({
+	/**
+	* Absolute `http(s)://` URL. Built by `buildDeviceAdminUrl` and therefore
+	* free of userinfo and of any credential-shaped query key.
+	*/
+	url: string(),
+	/**
+	* What the surface calls it — "Web UI", "Home Assistant", "UniFi controller".
+	* The PROVIDER names it, because only the provider knows what the page is;
+	* a UI that invented the label from the addon id would call the Home
+	* Assistant device page "Provider Homeassistant".
+	*/
+	label: string(),
+	target: AdminLinkTargetEnum,
+	/**
+	* Host the URL points at, without scheme, port or path — for the tooltip, so
+	* an operator can see WHERE the button goes before he follows it. Redundant
+	* with `url` by construction; carried separately so no surface has to parse
+	* a URL to show it.
+	*/
+	host: string()
+});
+var deviceAdminLinkCapability = {
+	name: "device-admin-link",
+	scope: "device",
+	deviceNative: true,
+	mode: "singleton",
+	methods: { 
+	/**
+	* The device's management page, or `null` when this device has none.
+	*
+	* `auth: 'admin'` deliberately. This is administration, not actuation —
+	* the same bucket as `reboot` and `camera-credentials`, and explicitly NOT
+	* the actuation set `scripts/check-actuation-not-admin.ts` protects (D403).
+	* The URL is also a statement about the LAN, which a household member with
+	* a `view` grant on a light has no reason to be handed.
+	*
+	* The surfaces gate on the QUERY, never on a role they guessed: a caller
+	* without the right loses the query and draws nothing, which is the same
+	* thing a device with no page draws. There is no path on which a button
+	* appears and then fails — the D403 failure mode, from the other end.
+	*/
+getAdminLink: method(object({ deviceId: number().int().nonnegative() }), DeviceAdminLinkSchema.nullable(), { auth: "admin" }) }
+};
+/**
+* Query keys that may never appear on an admin link. A credential smuggled as
+* `?password=` is the same leak as userinfo, in a form the userinfo check
+* cannot see: it survives copy-paste, referrer headers and proxy logs
+* identically.
+*/
+var CREDENTIAL_QUERY_KEYS = [
+	"password",
+	"passwd",
+	"pwd",
+	"pass",
+	"user",
+	"username",
+	"usr",
+	"login",
+	"token",
+	"access_token",
+	"auth",
+	"authorization",
+	"apikey",
+	"api_key",
+	"secret",
+	"credential",
+	"credentials",
+	"session",
+	"sessionid",
+	"key"
+];
+/**
+* The same userinfo shape `scripts/check-no-credential-urls-in-fixtures.ts`
+* scans recorded fixtures for, applied to what we are about to EMIT. Kept
+* structurally identical on purpose: a URL this function returns is a URL that
+* guard would pass.
+*/
+var CREDENTIAL_URL = /[a-z][a-z0-9+.-]*:\/\/[^/\s:@'"]+:[^/\s:@'"]+@/i;
+/** A host that is safe to place in an authority component verbatim. */
+var PLAIN_HOST = /^[a-zA-Z0-9._-]+$/;
+/** A bracketed IPv6 literal, the only other authority form we emit. */
+var IPV6_HOST = /^\[[0-9a-fA-F:.]+\]$/;
+function defaultPortFor(scheme) {
+	return scheme === "https" ? 443 : 80;
+}
+/**
+* Build the admin-page URL, or refuse by name.
+*
+* The refusal is never thrown: a provider answering "no page for this device"
+* is an ordinary answer (`getAdminLink` → `null`), and a throw here would turn
+* a missing host on one device into a failed query for the whole surface.
+*/
+function buildDeviceAdminUrl(parts) {
+	const host = parts.host.trim();
+	if (host.length === 0) return {
+		ok: false,
+		reason: "empty-host"
+	};
+	if (host.includes("@")) return {
+		ok: false,
+		reason: "host-carries-userinfo"
+	};
+	if (!PLAIN_HOST.test(host) && !IPV6_HOST.test(host)) return {
+		ok: false,
+		reason: "host-not-plain"
+	};
+	if (parts.port !== null) {
+		if (!Number.isInteger(parts.port) || parts.port < 1 || parts.port > 65535) return {
+			ok: false,
+			reason: "port-out-of-range"
+		};
+	}
+	if (!parts.path.startsWith("/")) return {
+		ok: false,
+		reason: "path-not-absolute"
+	};
+	const query = parts.query ?? {};
+	for (const key of Object.keys(query)) if (CREDENTIAL_QUERY_KEYS.includes(key.toLowerCase())) return {
+		ok: false,
+		reason: "credential-query-key"
+	};
+	const authority = parts.port === null || parts.port === defaultPortFor(parts.scheme) ? host : `${host}:${String(parts.port)}`;
+	const search = new URLSearchParams();
+	for (const [key, value] of Object.entries(query)) search.append(key, value);
+	const suffix = search.size > 0 ? `?${search.toString()}` : "";
+	const url = `${parts.scheme}://${authority}${parts.path}${suffix}`;
+	if (CREDENTIAL_URL.test(url)) return {
+		ok: false,
+		reason: "userinfo-in-result"
+	};
+	return {
+		ok: true,
+		url
+	};
+}
+/**
 * Identity envelope for a device's upstream-system metadata.
 *
 * Two jobs:
@@ -13856,210 +13979,6 @@ method(object({ integrationId: string() }), object({ filters: array(AdoptionFilt
 	auth: "admin"
 });
 /**
-* device-admin-link — "this device has a management page of its own, and here
-* is its address".
-*
-* ## Why this is not a `deviceConfig` cap
-*
-* There is nothing to edit. A `deviceConfig` cap (D14) exists so the framework
-* can DERIVE a settings form from `getOptions` + `getStatus` and route a flat
-* patch back through a setter; it costs a `builderId` reducer in
-* `device-config-contribution.ts` and a `*-config-schema.ts` beside it, and it
-* renders a form section. This cap answers ONE question with ONE read and
-* renders a button. Nothing about it is a form, so it carries no `deviceConfig`
-* block, no `settings`, no `runtimeState` and no reducer — exactly like
-* `reboot`, the other pure-RPC device-native cap.
-*
-* ## Absent, and the difference between "no page" and "we cannot say"
-*
-* The two are answered at DIFFERENT layers, on purpose:
-*
-*  - **"We cannot say"** → the provider never registers the cap for that
-*    device. A VeSync humidifier, a Petkit feeder, a Dreame vacuum and a Dreo
-*    fan are reached only through a vendor cloud; there is no address to hand
-*    out and no page to open. A Tuya plug, a Wyze camera and a Gree air
-*    conditioner DO have a LAN IP, and still have no HTTP management page
-*    behind it. None of them register, so `deviceManager.getBindings` never
-*    lists the cap and no surface asks.
-*  - **"This device has no page, and I know that"** → the provider registers
-*    and `getAdminLink` returns `null`. This is the answer for a device whose
-*    sibling DOES have a page: a Reolink battery camera reached over UDP by
-*    `uid` with a blank `host`, an Ecowitt gateway configured in `listener`
-*    transport, a Home Assistant broker authenticated by supervisor token
-*    (which carries no `baseUrl` at all).
-*
-* Both draw NOTHING. A button that opens a browser error is worse than no
-* button, and D62 is the same rule from the other side: an off switch is
-* reported off, never made to look broken. There is no third state where the
-* UI renders a disabled button "because the device might have a page".
-*
-* ## The URL never carries credentials
-*
-* Not in userinfo, not in a query string. Every provider builds through
-* `buildDeviceAdminUrl` (`device-admin-link-url.ts`), which takes host, port,
-* scheme and path as separate arguments — there is no parameter a secret could
-* arrive in — and re-checks its own output for the `scheme://user:pass@` shape
-* that `scripts/check-no-credential-urls-in-fixtures.ts` bans from recorded
-* output. `scripts/check-admin-link-builder-is-the-only-url-source.ts` is what
-* keeps providers from hand-rolling one anyway.
-*
-* This matters here more than anywhere else in the repo, because every provider
-* that knows a device's host knows its PASSWORD too: `{ host, port, username,
-* password }` sit in one object on Hikvision, Amcrest, Reolink and ONVIF alike,
-* and `http://admin:hunter2@192.168.50.139/` is a URL a browser accepts. The
-* camera's own page will ask for its own login. That is correct, and pre-
-* filling it is the operator's business, not ours.
-*
-* ## It is a LAN fact
-*
-* The URL addresses the device where the NODE can see it. It is not proxied,
-* not made reachable from outside, and not sent anywhere. A surface renders it
-* as a link the operator's own browser follows, on the operator's own network,
-* or renders nothing.
-*/
-/**
-* Whose page is it. The distinction is for the OPERATOR, who needs to know
-* before clicking whether he is about to land on a camera's own web server or
-* inside Home Assistant.
-*/
-var AdminLinkTargetEnum = _enum(["device", "integration"]);
-var DeviceAdminLinkSchema = object({
-	/**
-	* Absolute `http(s)://` URL. Built by `buildDeviceAdminUrl` and therefore
-	* free of userinfo and of any credential-shaped query key.
-	*/
-	url: string(),
-	/**
-	* What the surface calls it — "Web UI", "Home Assistant", "UniFi controller".
-	* The PROVIDER names it, because only the provider knows what the page is;
-	* a UI that invented the label from the addon id would call the Home
-	* Assistant device page "Provider Homeassistant".
-	*/
-	label: string(),
-	target: AdminLinkTargetEnum,
-	/**
-	* Host the URL points at, without scheme, port or path — for the tooltip, so
-	* an operator can see WHERE the button goes before he follows it. Redundant
-	* with `url` by construction; carried separately so no surface has to parse
-	* a URL to show it.
-	*/
-	host: string()
-});
-var deviceAdminLinkCapability = {
-	name: "device-admin-link",
-	scope: "device",
-	deviceNative: true,
-	mode: "singleton",
-	methods: { 
-	/**
-	* The device's management page, or `null` when this device has none.
-	*
-	* `auth: 'admin'` deliberately. This is administration, not actuation —
-	* the same bucket as `reboot` and `camera-credentials`, and explicitly NOT
-	* the actuation set `scripts/check-actuation-not-admin.ts` protects (D403).
-	* The URL is also a statement about the LAN, which a household member with
-	* a `view` grant on a light has no reason to be handed.
-	*
-	* The surfaces gate on the QUERY, never on a role they guessed: a caller
-	* without the right loses the query and draws nothing, which is the same
-	* thing a device with no page draws. There is no path on which a button
-	* appears and then fails — the D403 failure mode, from the other end.
-	*/
-getAdminLink: method(object({ deviceId: number().int().nonnegative() }), DeviceAdminLinkSchema.nullable(), { auth: "admin" }) }
-};
-/**
-* Query keys that may never appear on an admin link. A credential smuggled as
-* `?password=` is the same leak as userinfo, in a form the userinfo check
-* cannot see: it survives copy-paste, referrer headers and proxy logs
-* identically.
-*/
-var CREDENTIAL_QUERY_KEYS = [
-	"password",
-	"passwd",
-	"pwd",
-	"pass",
-	"user",
-	"username",
-	"usr",
-	"login",
-	"token",
-	"access_token",
-	"auth",
-	"authorization",
-	"apikey",
-	"api_key",
-	"secret",
-	"credential",
-	"credentials",
-	"session",
-	"sessionid",
-	"key"
-];
-/**
-* The same userinfo shape `scripts/check-no-credential-urls-in-fixtures.ts`
-* scans recorded fixtures for, applied to what we are about to EMIT. Kept
-* structurally identical on purpose: a URL this function returns is a URL that
-* guard would pass.
-*/
-var CREDENTIAL_URL = /[a-z][a-z0-9+.-]*:\/\/[^/\s:@'"]+:[^/\s:@'"]+@/i;
-/** A host that is safe to place in an authority component verbatim. */
-var PLAIN_HOST = /^[a-zA-Z0-9._-]+$/;
-/** A bracketed IPv6 literal, the only other authority form we emit. */
-var IPV6_HOST = /^\[[0-9a-fA-F:.]+\]$/;
-function defaultPortFor(scheme) {
-	return scheme === "https" ? 443 : 80;
-}
-/**
-* Build the admin-page URL, or refuse by name.
-*
-* The refusal is never thrown: a provider answering "no page for this device"
-* is an ordinary answer (`getAdminLink` → `null`), and a throw here would turn
-* a missing host on one device into a failed query for the whole surface.
-*/
-function buildDeviceAdminUrl(parts) {
-	const host = parts.host.trim();
-	if (host.length === 0) return {
-		ok: false,
-		reason: "empty-host"
-	};
-	if (host.includes("@")) return {
-		ok: false,
-		reason: "host-carries-userinfo"
-	};
-	if (!PLAIN_HOST.test(host) && !IPV6_HOST.test(host)) return {
-		ok: false,
-		reason: "host-not-plain"
-	};
-	if (parts.port !== null) {
-		if (!Number.isInteger(parts.port) || parts.port < 1 || parts.port > 65535) return {
-			ok: false,
-			reason: "port-out-of-range"
-		};
-	}
-	if (!parts.path.startsWith("/")) return {
-		ok: false,
-		reason: "path-not-absolute"
-	};
-	const query = parts.query ?? {};
-	for (const key of Object.keys(query)) if (CREDENTIAL_QUERY_KEYS.includes(key.toLowerCase())) return {
-		ok: false,
-		reason: "credential-query-key"
-	};
-	const authority = parts.port === null || parts.port === defaultPortFor(parts.scheme) ? host : `${host}:${String(parts.port)}`;
-	const search = new URLSearchParams();
-	for (const [key, value] of Object.entries(query)) search.append(key, value);
-	const suffix = search.size > 0 ? `?${search.toString()}` : "";
-	const url = `${parts.scheme}://${authority}${parts.path}${suffix}`;
-	if (CREDENTIAL_URL.test(url)) return {
-		ok: false,
-		reason: "userinfo-in-result"
-	};
-	return {
-		ok: true,
-		url
-	};
-}
-/**
 * `device-export` — collection cap for addons that export camstack
 * devices to external ecosystems (HomeAssistant via MQTT discovery,
 * HomeKit/HAP, Alexa Smart Home, …).
@@ -24461,6 +24380,87 @@ method(_void(), ProviderInfoSchema, { auth: "admin" }), method(object({ config:
 	kind: "mutation",
 	auth: "admin"
 });
+/**
+* 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
+* 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
+* itself, with no stream running.
+*
+* ## The vocabulary is the PROVIDER'S, not ours
+*
+* Like `consumables`, this cap declares no vocabulary of its own. A provider
+* names each signal with a `code` it chooses and a `label` an operator reads.
+* Reolink offers motion and camera-native detection; another provider may offer
+* a tamper, a doorbell press, a PIR, or something no camera in this fleet has
+* yet. A fixed enum here would mean every new signal is a framework release.
+*
+* It is deliberately NOT derived from the caps a device already binds. Whether
+* a camera CAN push firmware motion is expressed by `motionSources` containing
+* `'onboard'`, and whether it does AI on-camera by the `native-object-detection`
+* binding — but both answer "what drives the detection pipeline", which is a
+* different question from "what may wake a sleeping stream". A camera can do
+* the first and not be trusted with the second, and the operator picks per
+* camera. Two questions, two authorities.
+*
+* ## Availability is not permission
+*
+* `listSignals` says what the device CAN emit. Whether a given signal actually
+* wakes the stream is the operator's per-camera choice, held by the broker
+* alongside the cooldown — see the stream-broker cap's wake settings. A
+* provider declaring a signal is not a provider enabling it.
+*/
+/** One signal a device can emit. */
+var StreamSignalSchema = object({
+	/** Stable id chosen by the provider, e.g. `'motion'`, `'person'`, `'tamper'`. */
+	code: string().min(1),
+	/** What an operator reads in the picker. The provider's own wording. */
+	label: string().min(1),
+	/**
+	* Whether the provider recommends this signal ON when a camera is first set
+	* up. A provider knows which of its signals are cheap and reliable; an
+	* operator should not have to discover that by trial. Reolink recommends
+	* both of its own.
+	*/
+	recommended: boolean()
+});
+var StreamSignalsStatusSchema = object({
+	signals: array(StreamSignalSchema),
+	lastFetchedAt: number()
+});
+var streamSignalsCapability = {
+	name: "stream-signals",
+	scope: "device",
+	deviceNative: true,
+	mode: "singleton",
+	deviceTypes: Object.values(DeviceType),
+	runtimeState: StreamSignalsStatusSchema,
+	/**
+	* Runtime-state durability: **session** — mirrored in RAM, never written.
+	*
+	* The slice holds what the DEVICE says it can emit. That is a probed fact,
+	* not an operator choice: the provider re-declares it on every registration,
+	* so losing it loses nothing and persisting it would freeze an answer the
+	* camera is entitled to change. Measured the same day on the sibling case —
+	* `native-object-detection.supportedClasses` was persisted, and a firmware
+	* class the camera really detected stayed missing for the life of the row
+	* because the fix could not reach it.
+	*
+	* See `RuntimeStateDurability`. Enforced by
+	* `scripts/check-runtime-state-durability.ts`.
+	*/
+	durability: "session",
+	methods: { 
+	/**
+	* What this device can emit. Empty is a valid and common answer — most
+	* cameras have nothing to offer here, and an empty list is what makes the
+	* broker's picker show nothing rather than a false choice.
+	*/
+listSignals: method(_void(), array(StreamSignalSchema).readonly()) }
+};
 /** Profile-exported FormBuilder schema. Shape is ConfigUISchema at the UI. */
 var ProfileSettingsSchemaBridge = unknown().nullable();
 var ProfileSettingsBagSchema = record(string(), unknown());
@@ -25501,27 +25501,74 @@ var ClipStreamDialSchema = object({
 	audioReason: ClipStreamAudioReasonSchema.optional()
 });
 /**
-* The playback rates a clip can be DELIVERED at, ascending, always with `1`.
+* The playback rates the broker can pace over media it HOLDS, ascending,
+* always with `1` — and the WIDEST ladder there is. It is the domain the
+* broker's `clampPlaybackRate` is derived from, at both ends.
 *
 * These are the BROKER's: it re-paces frames it has already demuxed — the
 * `MonotonicClock` divides source elapsed time by the factor and the pacer
-* pushes that much faster — so the domain is the recorded one, {0} ∪ [0.25, 4],
-* and this is the discrete ladder drawn from it. `1.5` is in it because a
-* re-pacer has no reason to refuse it.
-*
-* `8` and `16` are deliberately NOT here. They are the CAMERA's own
-* `<playSpeed>` (Reolink cmd-5 replay), a different mechanism, still unwired
-* (D597, D600) — a rate change there costs a new dial and a new stream, and
-* the camera's 8x would need a resample the clip audio path has no decoder
-* for. Offering them today accepts a rate and delivers 1x, which is the whole
-* defect this list exists to end (D612). When `playSpeed` IS wired its rates
-* join THIS array — a second list elsewhere is the second authority D62
-* forbids.
-*
-* Every entry must survive the broker's `clampPlaybackRate` unchanged: a set
-* that offers what the clamp then moves is the same lie one step later.
+* pushes that much faster. `1.5` is in it because a re-pacer has no reason to
+* refuse it.
+*
+* **`8` is here since D621, and it is the pacer's, not a camera's.** D620
+* measured the thing that was assumed for a year and was never true: a
+* Reolink `<playSpeed>` does not time-compress anything. At 1, 2, 4 and 8 the
+* transfer is byte-identical — same 947 472 bytes, same 594 access units,
+* same 39.855 s presentation span, same 624 AAC frames — and only the wall
+* clock moves. It buys SUPPLY, never speed. So there was never a second
+* mechanism to wire for 8×: there is one, this one, and what it needs is
+* media in hand and a clamp that does not move the number.
+*
+* **`16` is deliberately NOT here, and will not join by widening this array.**
+* The camera's `playSpeed 16` is not a rate at all but an I-frame-only MODE —
+* measured on 592: 10 access units for a whole 36.3 s sub clip, 20 for the
+* main twin at a 2 025 ms median spacing, and no audio track. That is
+* different CONTENT, a stream of its own, and the honest broker-side twin of
+* it would be a pacer that DROPS whole GOPs rather than one that pushes 16×
+* the bitrate at a live WebRTC track. Neither exists. A `16` in this array
+* today would be a rate accepted and delivered at 8 — D612's defect, which
+* this list exists to end, one number further along.
+*
+* Every entry must survive the broker's `clampPlaybackRate` unchanged. Since
+* D621 that is structural rather than a discipline: the clamp reads this
+* array's own ends. What still has to be proved behaviourally — and is, in
+* the broker's `clip-stream-feeder.spec` — is that the PACER really empties a
+* clip `rate` times faster, because a clamp agreeing with a ladder is a
+* constant compared against itself.
+*
+* Narrower ladders exist for transports whose SUPPLY is bounded; they are
+* subsets of this one ({@link CLIP_STREAM_SOURCE_RATES},
+* {@link CLIP_REALTIME_SOURCE_RATES}).
 */
 var CLIP_BROKER_PACED_RATES = [
+	.25,
+	.5,
+	1,
+	1.5,
+	2,
+	4,
+	8
+];
+/**
+* The rates a provider-STREAMED clip can be delivered at — a subset of
+* {@link CLIP_BROKER_PACED_RATES}, and frozen below it on purpose (D621).
+*
+* A `stream` clip's media does not exist yet: it arrives on a socket from the
+* camera while the pacer consumes it. The pacer takes `rate` seconds of media
+* per second of wall clock, so the ceiling is whatever the SOURCE supplies,
+* and that is a measurement per vendor rather than a preference.
+*
+* Reolink, the one provider on this envelope, was measured on 592
+* (2026-09-23, D620): with the `<ReplaySeek>` that 0.11.1 sends before every
+* replay, a sub clip arrives at **1.2×** and a main twin at **1.37×**. The
+* ladder below is therefore ALREADY beyond this transport above 1 — the D612
+* defect returned through a door nobody opened — and D620 fixed the repair
+* order: the supply first, the ladder after. So this array does not move with
+* the broker's, and it does not gain `8`; what it gains, when the library
+* forwards a `<playSpeed>` large enough to feed the rate being paced over it,
+* is the right to be widened on a measurement rather than shortened on one.
+*/
+var CLIP_STREAM_SOURCE_RATES = [
 	.25,
 	.5,
 	1,
@@ -26006,7 +26053,7 @@ var CLIP_PLAYBACK_OPTIONS = {
 		seek: "forward",
 		stepBack: false,
 		scrub: false,
-		rates: CLIP_BROKER_PACED_RATES
+		rates: CLIP_STREAM_SOURCE_RATES
 	},
 	/**
 	* A `stream` whose SOURCE runs at realtime — a Hikvision RTSP replay.
@@ -27390,6 +27437,143 @@ DeviceType.Camera, method(object({ deviceId: number() }), CameraCredentialsSchem
 	auth: "admin"
 });
 /**
+* camera-grid-layout — the geometry of a COMPOSITE camera, on the camera's own
+* page.
+*
+* ## Why this is a capability and not an addon settings schema
+*
+* It was one, and it did not render. The addon declared the editor as a
+* `type: 'widget'` field inside its own `deviceSettingsSchema()`; the hub
+* returned that section correctly and `ConfigFormField` renders `type:'widget'`
+* perfectly well — and nothing ever asked camera-grid for it. The Cluster →
+* Pipeline → Device Overrides page interrogates a HAND-WRITTEN list of four
+* addons (`PIPELINE_CLUSTER_DEVICE_ADDONS`), whose own comment says an addon
+* not on it "falls off silently".
+*
+* Adding a fifth name to that list would have been the wrong fix twice over:
+* that page is per-camera DETECTION tuning, and a grid's geometry belongs
+* beside PTZ and motion zones on the camera itself. The device page is
+* BINDING-driven (D12), so the way in is a capability bound to the device —
+* and this cap carries its section the way `recording` does, by RETURNING it
+* from `getDeviceSettingsContribution`.
+*
+* Seven other widgets are still declared the other way, through a
+* `deviceConfig.ui` block the framework derives a section from. That route
+* gives the addon no say in where its own panel lands and no way to decline
+* for a device the panel does not suit, which is why this one does not use it.
+*
+* ## Why one addon may implement it
+*
+* It is a device-scoped NATIVE cap, registered by the grid camera device
+* itself. Nothing else declares a composite camera, so nothing else has a
+* layout — and the device-scoped route means the widget asks THE camera, not
+* "the camera-grid addon", which is what let the old custom-action pair be
+* reached only by a caller that already knew the addon id.
+*
+* ## The tab
+*
+* `streaming`, not a top-tab of its own. A grid's geometry IS what its stream
+* is, so the Streaming tab is where it belongs; a `grid` top-tab would need an
+* entry in `WELL_KNOWN_TAB_MAP` or the device page renders the raw id as the
+* label (measured on the robot camera, 2026-09-06 — a tab called "navigation"
+* next to "PTZ").
+*/
+/** A rectangle in normalized [0,1] coordinates of whatever contains it. */
+var GridNormalizedRectSchema = object({
+	x: number().min(0).max(1),
+	y: number().min(0).max(1),
+	width: number().gt(0).max(1),
+	height: number().gt(0).max(1)
+});
+/**
+* One source camera, the part of its picture taken, and where that part lands.
+*
+* Both rectangles are NORMALIZED (D519): a source camera can change resolution
+* — a profile switch, a firmware update, a substream that comes back different
+* — and a stored PIXEL rectangle would quietly start cutting the wrong region,
+* which is the class of bug nobody files.
+*/
+var GridLayoutCellSchema = object({
+	deviceId: number().int().positive(),
+	/** The part of the SOURCE taken, normalized against the source. */
+	source: GridNormalizedRectSchema,
+	/** Where it lands, normalized against the CANVAS. */
+	cell: GridNormalizedRectSchema
+});
+/**
+* Which profiles this grid can actually compose, and why not.
+*
+* 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
+* low" is, and it is the one an operator can act on.
+*/
+var GridProfileOfferSchema = object({
+	profile: _enum([
+		"high",
+		"mid",
+		"low"
+	]),
+	offered: boolean(),
+	/** Sources that cannot serve it. Empty when it is offered, or when there are no cells. */
+	missingSources: array(number().int().positive()),
+	/**
+	* The canvas this profile composes onto, `WxH`, or empty when it is not
+	* offered. DERIVED from the cells and the sources' own size at this profile —
+	* it is reported because nothing else in the system would ever say what the
+	* grid came out as, and because it is the number an operator would otherwise
+	* expect to type.
+	*/
+	canvas: string(),
+	/**
+	* Whether this profile is PUBLISHED, of the ones the grid could serve.
+	*
+	* A grid's `high` is composed of its sources' `high`, so on a 4K fleet it is
+	* a 4K canvas built from 4K decodes — something to opt into, not something a
+	* viewer's adaptive should be handed by climbing to the top rung it can see.
+	* Default is `mid` + `low`.
+	*/
+	published: boolean()
+});
+var GridLayoutViewSchema = object({
+	/** The persisted grid row this camera was declared from. */
+	instanceId: string(),
+	deviceId: number().int().nonnegative(),
+	name: string(),
+	/**
+	* NO canvas size. A grid's resolution is not authored: each profile derives
+	* its own from the cells and its sources' dimensions. The two numbers that
+	* used to be here were a text field that silently decided both how much the
+	* composite cost and how sharp it was — see `profiles[].canvas` for what it
+	* came out as.
+	*/
+	fps: number().int(),
+	cells: array(GridLayoutCellSchema),
+	/** What the catalog will publish, and what it refuses to. Read-only. */
+	profiles: array(GridProfileOfferSchema)
+});
+var GridLayoutPatchSchema = object({
+	deviceId: number().int().nonnegative(),
+	name: string().min(1).max(160).optional(),
+	fps: number().int().min(1).max(60).optional(),
+	/** Which profiles to publish. See `GridProfileOffer.published`. */
+	publishedProfiles: array(_enum([
+		"high",
+		"mid",
+		"low"
+	])).max(3).optional(),
+	/**
+	* The whole cell list at once. A per-cell patch would need an ordering the
+	* editor does not have, and a half-applied layout is a picture nobody asked
+	* for.
+	*/
+	cells: array(GridLayoutCellSchema).max(16)
+});
+DeviceType.Camera, method(object({ deviceId: number().int().nonnegative() }), GridLayoutViewSchema.nullable(), { auth: "admin" }), method(GridLayoutPatchSchema, GridLayoutViewSchema, {
+	kind: "mutation",
+	auth: "admin"
+});
+/**
 * Carbon-monoxide alarm sensor. Drives Home Assistant `binary_sensor`
 * entries with `device_class: carbon_monoxide`. Push-driven.
 */
@@ -28192,764 +28376,224 @@ var dayNightCapability = {
 	volatileStateFields: ["lastFetchedAt"]
 };
 /**
-* Vendor-neutral **onboard** recording + storage cap — what the CAMERA
-* writes to the CAMERA's own card, on the camera's own schedule.
-*
-* This is NOT `recording.cap.ts`. That one is CamStack's recorder: our
-* footage ledger, our storage locations, our retention. This one has a
-* different authority — the camera's firmware — and per D62 it stores
-* nothing of its own. Every value here is read from the camera and every
-* write goes back to the camera; there is no CamStack-side mirror that
-* could disagree with the device.
-*
-* ## One shape, two firmwares
-*
-* Measured 2026-09-22 against the live fleet:
-*
-* | fact | Hikvision (ISAPI) | Reolink (Baichuan) |
-* | --- | --- | --- |
-* | storage | `ContentMgmt/Storage` `<hdd>` rows: status, capacity, freeSpace (MB) | `getHddInfoList` (cmd 102): `mount`, `format`, `capacity` GB + `capacityM` MB remainder |
-* | tracks | several (101 **and** 103 on both 1436 and 3833), each with its own schedule | one per channel |
-* | schedule | per track, 7 `ScheduleAction` blocks: DayOfWeek + TimeOfDay range + ONE `ActionRecordingMode` | per trigger type, a 168-char weekly HOUR mask |
-* | triggers | `CMR`, `MOTION` | `Normal`, `MD`, `people`, `vehicle`, `dog_cat`, `crossline`, `intrude`, `loitering` |
-* | pre-record | `PreRecordTimeSeconds` | `preRecordTime` |
-* | post-record | `PostRecordTimeSeconds` | `recordDelayTime` |
-* | overwrite | per track `LoopEnable` | `cycle`, with `cycleList` enumerating the accepted values |
-* | segment length | not exposed on V5.7.1 | `packageTime` (minutes) |
-*
-* The two schedule models look different and are the same thing in
-* different coordinates: both answer "for this trigger, during which
-* weekly windows does the camera record". {@link RecordWindow} is that
-* question in one shape — Hikvision's ranges map straight onto it,
-* Reolink's mask expands into hour-aligned windows.
-*
-* ## Union, not intersection
-*
-* **The same fields exist on every camera.** What differs per device is
-* which VALUES that device accepts, and that is what {@link
-* RecordingOnboardOptions} reports — a `{ readable, writable, reason }`
-* per field plus the schedule's own limits. A control a camera cannot
-* honour is rendered DISABLED WITH ITS REASON, never missing and never
-* dead: disabled must not look like broken.
-*
-* ## Refusal by name
-*
-* A write a camera cannot honour is refused with a sentence the operator
-* can read — never accepted and dropped. Both providers refuse through
-* {@link describeOnboardRefusal}, so the vocabulary is one function and
-* one test, not two hand-written vendor opinions.
+* Generic device-level status snapshot. Auto-registered by `BaseDevice`
+* for every device, regardless of provider — the kernel needs a uniform
+* cap-keyed slice for the basic device flags every consumer expects to
+* read across processes (the `online` flag in particular). Driver-specific
+* caps (`battery`, `doorbell`, …) carry their domain-specific state on
+* their own slices.
 *
-* Follows the D14 `deviceConfig` archetype (see `stream-params.cap.ts`):
-* `getOptions` advertises per-camera availability, `getStatus` (auto-
-* injected from `status`) reports the live values, and a single
-* `setSettings` mutation applies a partial change. No hand-written
-* settings-contribution methods.
+* Pattern is identical to `battery`: schema-bearing `runtimeState`,
+* empty `methods`, single change event. Reads land at
+* `runtimeState.getCapState('device-status')`; writes at
+* `runtimeState.setCapState('device-status', …)`. Cross-process
+* consumers reach the same data via the `device-state` cap router
+* (`getCapSlice({deviceId, capName: 'device-status'})`).
 */
+var DeviceStatusSchema = object({
+	/**
+	* Device-level liveness. Drivers flip via `markOnline(boolean)` on
+	* `BaseDevice`. Provider semantics vary — RTSP aggregates broker
+	* stream-health, Reolink reads firmware push events, ONVIF tracks
+	* ping responses. This cap intentionally does NOT prescribe which
+	* signal drives the flag.
+	*/
+	online: boolean(),
+	/** Ms epoch of the last `online` transition. Lets consumers tell
+	*  apart "just came online" from "still online". */
+	lastChangedAt: number()
+});
+var deviceStatusCapability = {
+	name: "device-status",
+	scope: "device",
+	deviceNative: true,
+	mode: "singleton",
+	methods: {},
+	events: { 
+	/** Emitted when `online` transitions. Mirrors the semantics of
+	*  `battery.onStatusChanged`. */
+onStatusChanged: { data: object({
+		deviceId: number(),
+		status: DeviceStatusSchema
+	}) } },
+	status: {
+		schema: DeviceStatusSchema,
+		kind: "push"
+	},
+	runtimeState: DeviceStatusSchema,
+	/**
+	* Runtime-state durability: **restored** — the previous observation is what makes the first reading after a restart a COMPARISON instead of a phantom transition (D130). 32 real flips across 16 devices in 25 min — the busiest slice in the cold half.
+	*
+	* See `RuntimeStateDurability`. Enforced by
+	* `scripts/check-runtime-state-durability.ts`.
+	*/
+	durability: "restored",
+	/** Clock fields: written, but excluded from the compare that decides
+	*  whether persisting is worth a SQLite commit. */
+	volatileStateFields: ["lastChangedAt"]
+};
 /**
-* What makes the camera start recording during a window.
+* Doorbell button cap. Two kinds of providers coexist behind this cap
+* name (same pattern as `snapshot`):
 *
-* The union of both vendors' vocabularies. `continuous` is Hikvision's
-* `CMR` and Reolink's `Normal`; `motion` is `MOTION` / `MD`. The
-* object-class triggers are Reolink-only today and the smart-event ones
-* (`lineCrossing`, `intrusion`, `loitering`) are Reolink-only on the
-* firmwares measured — a camera that cannot record on a trigger simply
-* does not list it in `options.schedule.triggers`, and a window naming
-* it is REFUSED, not dropped.
-*/
-var RecordTriggerSchema = _enum([
-	"continuous",
-	"motion",
-	"person",
-	"vehicle",
-	"animal",
-	"lineCrossing",
-	"intrusion",
-	"loitering",
-	"alarmInput"
-]);
-/**
-* One weekly recording window: "on `day`, from `startMinute` to
-* `endMinute`, record on `trigger`".
+*   - **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).
 *
-* `day` is 0 = Monday … 6 = Sunday (ISO order, which is also the order
-* both firmwares enumerate). Minutes are local camera time since
-* midnight; `endMinute` may be 1440, meaning end of day — that is
-* Hikvision's literal `24:00` and Reolink's 24th mask slot, and
-* collapsing it to 0 would turn a whole-day window into an empty one.
+*   - **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 RecordWindowSchema = object({
-	trigger: RecordTriggerSchema,
-	day: number().int().min(0).max(6),
-	startMinute: number().int().min(0).max(1439),
-	endMinute: number().int().min(1).max(1440)
+var DoorbellStatusSchema = object({
+	/** Ms epoch of the last press. null = never observed since this provider started. */
+	lastPressedAt: number().nullable(),
+	/** Counter since provider start. Resets on reboot. Useful for metrics/debug. */
+	pressCountSinceStart: number()
 });
-/** Status of one physical volume, as the camera itself describes it. */
-var OnboardStorageVolumeSchema = object({
-	/** The camera's own id for the volume (`hdd/id`, Reolink `HddInfo/number`). */
-	id: string(),
-	/** The camera's own name for it, when it gives one (`hddName`). */
-	label: string().optional(),
-	status: _enum([
-		"ok",
-		"unformatted",
-		"error",
-		"offline",
-		"unknown"
-	]),
+var DoorbellPressEventSchema = object({
+	deviceId: number(),
+	timestamp: number()
+});
+var doorbellCapability = {
+	name: "doorbell",
+	scope: "device",
+	deviceNative: true,
+	mode: "singleton",
+	kind: "wrapper",
+	defaultActive: false,
+	deviceTypes: [DeviceType.Button, DeviceType.Camera],
+	exposesDeviceSettings: true,
+	methods: {},
+	events: { 
 	/**
-	* Total size in MB, or **null when the camera did not say**.
-	*
-	* Never 0 for an unreadable value: a measurement that failed is not a
-	* measurement (D393), and a card whose size is unknown must not be
-	* rendered as a card of size zero.
+	* Fires once per physical press. Reolink delivers via Baichuan
+	* push (`ReolinkSimpleEvent.type === 'doorbell'`). There is no
+	* release/duration — it's a pulse.
 	*/
-	capacityMb: number().nullable(),
+onPressed: { data: DoorbellPressEventSchema } },
+	status: {
+		schema: DoorbellStatusSchema,
+		kind: "push"
+	},
 	/**
-	* Free space in MB, or null when unknown.
+	* 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.
 	*
-	* **Not a proxy for "has footage".** Measured 2026-09-22: 1436 and
-	* 1439 both report exactly 11776 MB free — the fixed reserve a looping
-	* card converges on once it has wrapped. At loop steady state the
-	* number is identical whether the camera recorded yesterday or stopped
-	* a month ago.
+	* See `RuntimeStateDurability`. Enforced by
+	* `scripts/check-runtime-state-durability.ts`.
 	*/
-	freeMb: number().nullable(),
-	/** True when the camera reports the volume writable (`property` RW). */
-	writable: boolean().optional()
-});
+	durability: "restored"
+};
 /**
-* What the camera is doing with its own storage, right now.
-*
-* Every scalar is nullable and **null means the camera did not answer**,
-* never a default. A form that seeds `0` from an unanswered read invites
-* the operator to save that 0 back onto the camera.
+* Enum-state sensor — a string value picked from a finite option set.
+* Drives HA `sensor` entries with `state_class: enum` (HVAC action
+* states, weather conditions, contact-source channels, mode strings).
+* The option set is stable across observations; it is persisted in the
+* device config blob (via the control slice at adoption) and is NOT
+* stored in `sourceInfo`.
 */
-var RecordingOnboardStatusSchema = object({
-	storage: discriminatedUnion("kind", [
-		object({
-			kind: literal("present"),
-			volumes: array(OnboardStorageVolumeSchema)
-		}),
-		object({
-			kind: literal("absent"),
-			reason: string()
-		}),
-		object({
-			kind: literal("unknown"),
-			reason: string()
-		})
-	]),
-	tracks: array(object({
-		id: string(),
-		enabled: boolean(),
-		isVideo: boolean(),
-		/** From the camera's own track description. Null when it does not say. */
-		codec: string().nullable(),
-		resolution: string().nullable(),
-		/** Per-track overwrite flag, where the firmware keeps it per track. */
-		overwriteWhenFull: boolean().nullable()
-	})),
+/** Locale-render shape for an ISO `value` carried by a `DateTimeSensor`-role
+*  enum sensor: `date` (date-only), `time` (time-only), `datetime` (both). */
+var EnumSensorDateTimeFormatSchema = _enum([
+	"date",
+	"time",
+	"datetime"
+]);
+var EnumSensorStatusSchema = object({
+	value: string(),
 	/**
-	* The track the write path targets — the enabled VIDEO one. Null when
-	* no track could be identified, which is itself a refusal reason.
+	* Set for `DateTimeSensor`-role sensors so the UI renders the ISO `value`
+	* as a locale date/time/datetime; absent for plain enum sensors. HA
+	* `device_class=timestamp` → `'datetime'`, `device_class=date` → `'date'`,
+	* a time-only sensor → `'time'`.
 	*/
-	primaryTrackId: string().nullable(),
-	/** Master "record to the card at all" switch. */
-	enabled: boolean().nullable(),
-	overwriteWhenFull: boolean().nullable(),
-	preRecordSec: number().nullable(),
-	postRecordSec: number().nullable(),
-	/** Length of one recorded file, in minutes. */
-	segmentMinutes: number().nullable(),
-	/** The primary track's weekly windows, flattened. */
-	windows: array(RecordWindowSchema),
+	format: EnumSensorDateTimeFormatSchema.optional(),
+	/** Ms epoch when the slice was last updated. */
+	lastFetchedAt: number()
+});
+var enumSensorCapability = {
+	name: "enum-sensor",
+	scope: "device",
+	deviceNative: true,
+	mode: "singleton",
+	deviceTypes: [DeviceType.Sensor],
+	methods: {},
+	status: {
+		schema: EnumSensorStatusSchema,
+		kind: "push"
+	},
+	runtimeState: EnumSensorStatusSchema,
 	/**
-	* How many windows the camera described that CamStack could NOT read —
-	* an unrecognised trigger, an unparseable clock, a weekday it does not
-	* name.
+	* Runtime-state durability: **restored** — as `numeric-sensor`; 80 devices.
 	*
-	* A dropped window is work the reader threw away, and a schedule that
-	* silently shows fewer rows than the camera holds is how an operator
-	* saves back a schedule shorter than the one they were looking at
-	* (D391). Non-zero means the window list is INCOMPLETE and a write
-	* that replaces it would delete what was not shown — which is why a
-	* provider reporting a non-zero count also reports the schedule as not
-	* writable.
+	* See `RuntimeStateDurability`. Enforced by
+	* `scripts/check-runtime-state-durability.ts`.
 	*/
-	unreadableWindows: number(),
+	durability: "restored",
+	/** Clock fields: written, but excluded from the compare that decides
+	*  whether persisting is worth a SQLite commit. */
+	volatileStateFields: ["lastFetchedAt"]
+};
+/**
+* Generic stateless event emitter. Installed on a `DeviceType.EventEmitter`
+* device. Carries the device's EXACT declared event vocabulary verbatim
+* (NO normalization). Two shapes:
+*  - structured source (HA `event.*` entity) → `eventTypes` is the fixed
+*    declared vocabulary (e.g. ['press_short','press_long',...]).
+*  - generic/legacy source (HA bus events, e.g. zha_event) → `eventTypes`
+*    is [] (open) and `lastEvent.data` carries the complex payload.
+* `seq` is monotonic so two identical events still produce distinct slice writes.
+*/
+var EventFireSchema = object({
+	deviceId: number(),
+	eventType: string(),
+	data: record(string(), unknown()).nullable(),
+	timestamp: number(),
+	seq: number()
+});
+var EventEmitterStatusSchema = object({
+	eventTypes: array(string()),
+	lastEvent: EventFireSchema.nullable(),
+	eventCountSinceStart: number()
+});
+var eventEmitterCapability = {
+	name: "event-emitter",
+	scope: "device",
+	deviceNative: true,
+	mode: "singleton",
+	deviceTypes: [DeviceType.EventEmitter],
+	methods: {},
+	events: { onEvent: { data: EventFireSchema } },
+	status: {
+		schema: EventEmitterStatusSchema,
+		kind: "push"
+	},
+	runtimeState: EventEmitterStatusSchema,
 	/**
-	* The camera is scheduled to record and has NO usable storage.
+	* Runtime-state durability: **session** — `eventCountSinceStart` names its own scope.
 	*
-	* A first-class fact because it is the fleet's most common silent
-	* defect: measured 2026-09-22, 1441 and 3831 are both motion-recording
-	* to a card that is not there. Neither the schedule nor the storage
-	* read says anything wrong on its own; only the pair does.
-	*/
-	recordingToNowhere: boolean(),
-	lastFetchedAt: number()
-});
-/** Numeric range descriptor — `{ min, max, step }` per the getOptions convention. */
-var RangeSchema = object({
-	min: number(),
-	max: number(),
-	step: number()
-});
-/**
-* The values a camera actually takes for a numeric field, when they are a SET
-* rather than a range.
-*
-* `{min,max,step}` cannot say what these two firmwares do. Measured on 1436
-* (I91DN) on 2026-09-22 by writing each value and reading it back:
-*
-* - pre-record: `0, 5, 10, 15, 20, 25, 30` and `2147483647` (INT32_MAX, the
-*   camera's "no limit" — `-1` and `4294967295` both land on it);
-* - post-record: `5, 10, 30, 60, 120, 300, 600`.
-*
-* Neither is expressible as a step: the first has a sentinel two billion away
-* from its neighbours, the second doubles and then jumps. A range that tried
-* would forbid values the camera takes AND permit values it silently replaces
-* with 5 — wrong in both directions at once.
-*
-* `sentinel` names the member that is not a duration, so a surface can render
-* "no limit" instead of `2147483647` seconds.
-*/
-var AllowedValuesSchema = object({
-	values: array(number()).min(1),
-	sentinel: object({
-		value: number(),
-		meaning: _enum(["no-limit", "disabled"])
-	}).optional()
-});
-/**
-* Per-field availability on ONE camera.
-*
-* The field exists on every camera — this says whether this one can be
-* read and whether it can be written, and `reason` says why not when
-* either is false. The UI renders the control DISABLED with the reason
-* rather than hiding it, so a limitation is legible instead of looking
-* like a missing feature.
-*/
-var OnboardFieldSupportSchema = object({
-	readable: boolean(),
-	writable: boolean(),
-	/** Required whenever `readable` or `writable` is false. */
-	reason: string().optional()
-});
-/** What this camera's schedule model can express. */
-var OnboardScheduleSupportSchema = object({
-	support: OnboardFieldSupportSchema,
-	/**
-	* The smallest time step the camera can express, in minutes.
-	*
-	* Hikvision takes arbitrary minutes (`00:05:00`–`23:57:00` observed on
-	* 1436's track 103). Reolink's schedule is a 7×24 HOUR mask, so 60. A
-	* window whose edges are not a multiple of this is REFUSED rather than
-	* quietly rounded — rounding is how an operator's 06:30 becomes 06:00
-	* and nothing says so.
-	*/
-	granularityMinutes: number(),
-	/** Triggers this camera can record on. A window naming another is refused. */
-	triggers: array(RecordTriggerSchema),
-	/**
-	* False when the camera stores ONE trigger per time range, so two
-	* windows overlapping on the same day cannot carry different triggers.
-	* True on Reolink, whose mask is per-trigger and independent.
-	*/
-	supportsOverlappingTriggers: boolean()
-});
-var RecordingOnboardOptionsSchema = object({
-	enabled: OnboardFieldSupportSchema,
-	overwriteWhenFull: OnboardFieldSupportSchema,
-	preRecordSec: OnboardFieldSupportSchema,
-	preRecordSecRange: RangeSchema.optional(),
-	/** Preferred over the range when the camera takes a SET, not a span. */
-	preRecordSecAllowed: AllowedValuesSchema.optional(),
-	postRecordSec: OnboardFieldSupportSchema,
-	postRecordSecRange: RangeSchema.optional(),
-	/** Preferred over the range when the camera takes a SET, not a span. */
-	postRecordSecAllowed: AllowedValuesSchema.optional(),
-	segmentMinutes: OnboardFieldSupportSchema,
-	segmentMinutesRange: RangeSchema.optional(),
-	/** Preferred over the range when the camera takes a SET, not a span. */
-	segmentMinutesAllowed: AllowedValuesSchema.optional(),
-	schedule: OnboardScheduleSupportSchema
-});
-/**
-* A partial change. Every field optional.
-*
-* Unlike the other `deviceConfig` caps, a provider here does **NOT**
-* silently ignore a field it cannot support — it refuses, by name,
-* through {@link describeOnboardRefusal}. Silence on a recording setting
-* is the failure D62 exists to prevent: the operator believes the camera
-* is recording the way the form says, and it is not.
-*/
-var RecordingOnboardPatchSchema = object({
-	enabled: boolean().optional(),
-	overwriteWhenFull: boolean().optional(),
-	preRecordSec: number().optional(),
-	postRecordSec: number().optional(),
-	segmentMinutes: number().optional(),
-	/** The complete new window set for the primary track — not a delta. */
-	windows: array(RecordWindowSchema).optional()
-});
-var recordingOnboardCapability = {
-	name: "recording-onboard",
-	scope: "device",
-	deviceNative: true,
-	mode: "singleton",
-	deviceTypes: [DeviceType.Camera],
-	deviceConfig: { ui: {
-		kind: "derived-form",
-		builderId: "recording-onboard",
-		tab: "recording"
-	} },
-	methods: {
-		getOptions: method(object({ deviceId: number() }), RecordingOnboardOptionsSchema),
-		setSettings: method(object({
-			deviceId: number(),
-			settings: RecordingOnboardPatchSchema
-		}), _void(), {
-			kind: "mutation",
-			auth: "admin"
-		})
-	},
-	status: {
-		schema: RecordingOnboardStatusSchema,
-		kind: "poll"
-	},
-	runtimeState: RecordingOnboardStatusSchema,
-	/**
-	* Runtime-state durability: **restored** — operator-set camera-side
-	* recording config; mutation-driven, and the storage half is the last
-	* thing the camera said about its own card.
-	*
-	* See `RuntimeStateDurability`. Enforced by
-	* `scripts/check-runtime-state-durability.ts`.
-	*/
-	durability: "restored",
-	/** Clock fields: written, but excluded from the compare that decides
-	*  whether persisting is worth a SQLite commit. */
-	volatileStateFields: ["lastFetchedAt"]
-};
-/**
-* Day-of-week names in the cap's index order (0 = Monday), for messages
-* an operator reads and for Hikvision's `<DayOfWeek>` element.
-*/
-var DAY_NAMES = [
-	"Monday",
-	"Tuesday",
-	"Wednesday",
-	"Thursday",
-	"Friday",
-	"Saturday",
-	"Sunday"
-];
-/**
-* Does `patch` ask this camera for something it cannot do?
-*
-* Returns the operator-readable reason, or `null` when every field in
-* the patch is within what `options` says this camera accepts. A
-* provider calls this BEFORE touching the camera and throws the string:
-* refusing is the point, and refusing identically on both vendors is why
-* this is one function.
-*
-* The order of checks is the order an operator would read them: the
-* scalar knobs first, then the schedule, because a schedule complaint is
-* longer and a scalar one is usually the real problem.
-*/
-function describeOnboardRefusal(options, patch) {
-	if (patch.enabled !== void 0 && !options.enabled.writable) return unwritable("the master recording switch", options.enabled.reason);
-	if (patch.overwriteWhenFull !== void 0 && !options.overwriteWhenFull.writable) return unwritable("overwrite-when-full", options.overwriteWhenFull.reason);
-	const preRefusal = refuseNumeric("pre-record seconds", patch.preRecordSec, options.preRecordSec, options.preRecordSecRange, options.preRecordSecAllowed);
-	if (preRefusal) return preRefusal;
-	const postRefusal = refuseNumeric("post-record seconds", patch.postRecordSec, options.postRecordSec, options.postRecordSecRange, options.postRecordSecAllowed);
-	if (postRefusal) return postRefusal;
-	const segmentRefusal = refuseNumeric("segment length (minutes)", patch.segmentMinutes, options.segmentMinutes, options.segmentMinutesRange, options.segmentMinutesAllowed);
-	if (segmentRefusal) return segmentRefusal;
-	if (patch.windows !== void 0) {
-		const scheduleRefusal = refuseSchedule(options, patch.windows);
-		if (scheduleRefusal) return scheduleRefusal;
-	}
-	return null;
-}
-function unwritable(what, reason) {
-	return reason ? `this camera cannot change ${what}: ${reason}` : `this camera cannot change ${what}`;
-}
-function refuseNumeric(what, value, support, range, allowed) {
-	if (value === void 0) return null;
-	if (!support.writable) return unwritable(what, support.reason);
-	if (!Number.isFinite(value)) return `${what} must be a number, got ${String(value)}`;
-	if (allowed) {
-		if (allowed.values.includes(value)) return null;
-		const say = (v) => allowed.sentinel !== void 0 && v === allowed.sentinel.value ? allowed.sentinel.meaning === "no-limit" ? "no limit" : "off" : String(v);
-		return `this camera accepts ${what} only as ${allowed.values.map(say).join(", ")}; ${say(value)} is not one of them`;
-	}
-	if (!range) return null;
-	if (value < range.min || value > range.max) return `this camera accepts ${what} between ${String(range.min)} and ${String(range.max)}; ${String(value)} is outside that`;
-	if (range.step > 0 && (value - range.min) % range.step !== 0) return `this camera accepts ${what} in steps of ${String(range.step)} from ${String(range.min)}; ${String(value)} is not one of them`;
-	return null;
-}
-function refuseSchedule(options, windows) {
-	const schedule = options.schedule;
-	if (!schedule.support.writable) return unwritable("the recording schedule", schedule.support.reason);
-	const allowed = new Set(schedule.triggers);
-	for (const window of windows) {
-		if (!allowed.has(window.trigger)) {
-			const offer = schedule.triggers.length > 0 ? schedule.triggers.join(", ") : "none";
-			return `this camera cannot record on "${window.trigger}"; it records on: ${offer}`;
-		}
-		if (window.endMinute <= window.startMinute) return `a window on ${dayName(window.day)} ends at or before it starts (${String(window.startMinute)} → ${String(window.endMinute)})`;
-		const step = schedule.granularityMinutes;
-		if (step > 1 && (window.startMinute % step !== 0 || window.endMinute % step !== 0)) return `this camera's schedule only moves in ${String(step)}-minute steps; the ${dayName(window.day)} window ${formatMinutes(window.startMinute)}–${formatMinutes(window.endMinute)} is not aligned to them`;
-	}
-	if (!schedule.supportsOverlappingTriggers) {
-		const clash = findOverlapWithDifferentTrigger(windows);
-		if (clash) return `this camera stores one trigger per time range, so "${clash.a.trigger}" and "${clash.b.trigger}" cannot both cover ${dayName(clash.a.day)} ${formatMinutes(Math.max(clash.a.startMinute, clash.b.startMinute))}–${formatMinutes(Math.min(clash.a.endMinute, clash.b.endMinute))}`;
-	}
-	return null;
-}
-function findOverlapWithDifferentTrigger(windows) {
-	for (let i = 0; i < windows.length; i += 1) for (let j = i + 1; j < windows.length; j += 1) {
-		const a = windows[i];
-		const b = windows[j];
-		if (!a || !b) continue;
-		if (a.day !== b.day) continue;
-		if (a.trigger === b.trigger) continue;
-		if (a.startMinute < b.endMinute && b.startMinute < a.endMinute) return {
-			a,
-			b
-		};
-	}
-	return null;
-}
-function dayName(day) {
-	return DAY_NAMES[day] ?? `day ${String(day)}`;
-}
-/** `510` → `08:30`. For messages, not for the wire. */
-function formatMinutes(minute) {
-	const hour = Math.floor(minute / 60);
-	const rest = minute % 60;
-	return `${String(hour).padStart(2, "0")}:${String(rest).padStart(2, "0")}`;
-}
-/**
-* Parse a Hikvision `<TimeOfDay>` into minutes since midnight.
-*
-* The firmware is not self-consistent and both spellings are real, on
-* the same camera in the same block: a start time reads `00:00:00` and
-* the matching end time reads `24:00`. Seconds are accepted and
-* discarded — the cap's resolution is minutes — and `24:00` maps to
-* {@link MINUTES_PER_DAY}, not to 0.
-*
-* Returns null for anything else, which a caller reports as a window it
-* could not read rather than as midnight.
-*/
-function timeOfDayToMinutes(value) {
-	const match = /^(\d{1,2}):(\d{2})(?::(\d{2}))?$/.exec(value.trim());
-	if (!match) return null;
-	const hour = Number(match[1]);
-	const minute = Number(match[2]);
-	if (!Number.isInteger(hour) || !Number.isInteger(minute)) return null;
-	if (minute > 59) return null;
-	const total = hour * 60 + minute;
-	if (total > 1440) return null;
-	return total;
-}
-/**
-* Render minutes back as a Hikvision `TimeOfDay`.
-*
-* Emits the camera's own two spellings: `24:00` for end-of-day, because
-* that is what the firmware writes and `24:00:00` is not observed, and
-* `HH:MM:SS` otherwise.
-*/
-function minutesToTimeOfDay(minute) {
-	if (minute >= 1440) return "24:00";
-	const hour = Math.floor(minute / 60);
-	const rest = minute % 60;
-	return `${String(hour).padStart(2, "0")}:${String(rest).padStart(2, "0")}:00`;
-}
-/** `'Monday'` → 0. Case-insensitive. Null for anything unrecognised. */
-function dayOfWeekToIndex(value) {
-	const needle = value.trim().toLowerCase();
-	const index = DAY_NAMES.findIndex((name) => name.toLowerCase() === needle);
-	return index >= 0 ? index : null;
-}
-/**
-* Which fields of a patch the camera did NOT take verbatim.
-*
-* Measured on a Hikvision I91DN (1436, 2026-09-22): a `PUT` of
-* `PreRecordTimeSeconds: 8` answered `200`, `statusCode 1`, `OK` — and stored
-* **5**. Neither the asked value nor the previous one. The camera declares no
-* allowed set for that field, so there is nothing to refuse against before the
-* wire: `/capabilities` returns a plain value where a constrained field would
-* carry an `opt=` list.
-*
-* So the only honest moment is after the read-back, and re-reading alone is
-* not enough — it makes the difference VISIBLE while leaving it unexplained.
-* A write that reports success for a value the camera never took is the same
-* silent substitution D599 removed from the clip path, wearing a different hat.
-*
-* Compares only the fields the patch actually named: a field nobody asked
-* about cannot have been clamped, and a read-back that could not answer it is
-* `stored: null` rather than a claim.
-*/
-function describeOnboardClamp(patch, landed) {
-	const out = [];
-	for (const [field, asked] of Object.entries(patch)) {
-		if (asked === void 0) continue;
-		if (typeof asked !== "number" && typeof asked !== "boolean" && typeof asked !== "string") continue;
-		const raw = landed === null ? void 0 : landed[field];
-		const stored = typeof raw === "number" || typeof raw === "boolean" || typeof raw === "string" ? raw : null;
-		if (stored !== asked) out.push({
-			field,
-			asked,
-			stored
-		});
-	}
-	return out;
-}
-/**
-* Generic device-level status snapshot. Auto-registered by `BaseDevice`
-* for every device, regardless of provider — the kernel needs a uniform
-* cap-keyed slice for the basic device flags every consumer expects to
-* read across processes (the `online` flag in particular). Driver-specific
-* caps (`battery`, `doorbell`, …) carry their domain-specific state on
-* their own slices.
-*
-* Pattern is identical to `battery`: schema-bearing `runtimeState`,
-* empty `methods`, single change event. Reads land at
-* `runtimeState.getCapState('device-status')`; writes at
-* `runtimeState.setCapState('device-status', …)`. Cross-process
-* consumers reach the same data via the `device-state` cap router
-* (`getCapSlice({deviceId, capName: 'device-status'})`).
-*/
-var DeviceStatusSchema = object({
-	/**
-	* Device-level liveness. Drivers flip via `markOnline(boolean)` on
-	* `BaseDevice`. Provider semantics vary — RTSP aggregates broker
-	* stream-health, Reolink reads firmware push events, ONVIF tracks
-	* ping responses. This cap intentionally does NOT prescribe which
-	* signal drives the flag.
-	*/
-	online: boolean(),
-	/** Ms epoch of the last `online` transition. Lets consumers tell
-	*  apart "just came online" from "still online". */
-	lastChangedAt: number()
-});
-var deviceStatusCapability = {
-	name: "device-status",
-	scope: "device",
-	deviceNative: true,
-	mode: "singleton",
-	methods: {},
-	events: { 
-	/** Emitted when `online` transitions. Mirrors the semantics of
-	*  `battery.onStatusChanged`. */
-onStatusChanged: { data: object({
-		deviceId: number(),
-		status: DeviceStatusSchema
-	}) } },
-	status: {
-		schema: DeviceStatusSchema,
-		kind: "push"
-	},
-	runtimeState: DeviceStatusSchema,
-	/**
-	* Runtime-state durability: **restored** — the previous observation is what makes the first reading after a restart a COMPARISON instead of a phantom transition (D130). 32 real flips across 16 devices in 25 min — the busiest slice in the cold half.
-	*
-	* See `RuntimeStateDurability`. Enforced by
-	* `scripts/check-runtime-state-durability.ts`.
-	*/
-	durability: "restored",
-	/** Clock fields: written, but excluded from the compare that decides
-	*  whether persisting is worth a SQLite commit. */
-	volatileStateFields: ["lastChangedAt"]
-};
-/**
-* 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 = object({
-	/** Ms epoch of the last press. null = never observed since this provider started. */
-	lastPressedAt: number().nullable(),
-	/** Counter since provider start. Resets on reboot. Useful for metrics/debug. */
-	pressCountSinceStart: number()
-});
-var DoorbellPressEventSchema = object({
-	deviceId: number(),
-	timestamp: number()
-});
-var doorbellCapability = {
-	name: "doorbell",
-	scope: "device",
-	deviceNative: true,
-	mode: "singleton",
-	kind: "wrapper",
-	defaultActive: false,
-	deviceTypes: [DeviceType.Button, DeviceType.Camera],
-	exposesDeviceSettings: true,
-	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 } },
-	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"
-};
-/**
-* Enum-state sensor — a string value picked from a finite option set.
-* Drives HA `sensor` entries with `state_class: enum` (HVAC action
-* states, weather conditions, contact-source channels, mode strings).
-* The option set is stable across observations; it is persisted in the
-* device config blob (via the control slice at adoption) and is NOT
-* stored in `sourceInfo`.
-*/
-/** Locale-render shape for an ISO `value` carried by a `DateTimeSensor`-role
-*  enum sensor: `date` (date-only), `time` (time-only), `datetime` (both). */
-var EnumSensorDateTimeFormatSchema = _enum([
-	"date",
-	"time",
-	"datetime"
-]);
-var EnumSensorStatusSchema = object({
-	value: string(),
-	/**
-	* Set for `DateTimeSensor`-role sensors so the UI renders the ISO `value`
-	* as a locale date/time/datetime; absent for plain enum sensors. HA
-	* `device_class=timestamp` → `'datetime'`, `device_class=date` → `'date'`,
-	* a time-only sensor → `'time'`.
-	*/
-	format: EnumSensorDateTimeFormatSchema.optional(),
-	/** Ms epoch when the slice was last updated. */
-	lastFetchedAt: number()
-});
-var enumSensorCapability = {
-	name: "enum-sensor",
-	scope: "device",
-	deviceNative: true,
-	mode: "singleton",
-	deviceTypes: [DeviceType.Sensor],
-	methods: {},
-	status: {
-		schema: EnumSensorStatusSchema,
-		kind: "push"
-	},
-	runtimeState: EnumSensorStatusSchema,
-	/**
-	* Runtime-state durability: **restored** — as `numeric-sensor`; 80 devices.
-	*
-	* See `RuntimeStateDurability`. Enforced by
-	* `scripts/check-runtime-state-durability.ts`.
-	*/
-	durability: "restored",
-	/** Clock fields: written, but excluded from the compare that decides
-	*  whether persisting is worth a SQLite commit. */
-	volatileStateFields: ["lastFetchedAt"]
-};
-/**
-* Generic stateless event emitter. Installed on a `DeviceType.EventEmitter`
-* device. Carries the device's EXACT declared event vocabulary verbatim
-* (NO normalization). Two shapes:
-*  - structured source (HA `event.*` entity) → `eventTypes` is the fixed
-*    declared vocabulary (e.g. ['press_short','press_long',...]).
-*  - generic/legacy source (HA bus events, e.g. zha_event) → `eventTypes`
-*    is [] (open) and `lastEvent.data` carries the complex payload.
-* `seq` is monotonic so two identical events still produce distinct slice writes.
-*/
-var EventFireSchema = object({
-	deviceId: number(),
-	eventType: string(),
-	data: record(string(), unknown()).nullable(),
-	timestamp: number(),
-	seq: number()
-});
-var EventEmitterStatusSchema = object({
-	eventTypes: array(string()),
-	lastEvent: EventFireSchema.nullable(),
-	eventCountSinceStart: number()
-});
-var eventEmitterCapability = {
-	name: "event-emitter",
-	scope: "device",
-	deviceNative: true,
-	mode: "singleton",
-	deviceTypes: [DeviceType.EventEmitter],
-	methods: {},
-	events: { onEvent: { data: EventFireSchema } },
-	status: {
-		schema: EventEmitterStatusSchema,
-		kind: "push"
-	},
-	runtimeState: EventEmitterStatusSchema,
-	/**
-	* Runtime-state durability: **session** — `eventCountSinceStart` names its own scope.
-	*
-	* See `RuntimeStateDurability`. Enforced by
-	* `scripts/check-runtime-state-durability.ts`.
+	* See `RuntimeStateDurability`. Enforced by
+	* `scripts/check-runtime-state-durability.ts`.
 	*/
 	durability: "session"
 };
-var EventItemSchema = object({
-	id: string(),
-	type: string(),
-	timestamp: number(),
-	label: string().optional(),
-	thumbnailUrl: string().optional(),
-	clipUrl: string().optional(),
-	metadata: record(string(), unknown()).optional()
-});
-DeviceType.Camera, method(object({
-	deviceId: number(),
-	from: number().optional(),
-	to: number().optional(),
-	limit: number().optional()
-}), array(EventItemSchema)), method(object({
-	deviceId: number(),
-	eventId: string()
-}), object({
-	base64: string(),
-	contentType: string()
-}).nullable()), method(object({
-	deviceId: number(),
-	eventId: string()
-}), string().nullable());
 var IdentitySchema = object({
 	id: string(),
 	name: string(),
@@ -31227,143 +30871,6 @@ var motionTriggerCapability = {
 	durability: "session"
 };
 /**
-* camera-grid-layout — the geometry of a COMPOSITE camera, on the camera's own
-* page.
-*
-* ## Why this is a capability and not an addon settings schema
-*
-* It was one, and it did not render. The addon declared the editor as a
-* `type: 'widget'` field inside its own `deviceSettingsSchema()`; the hub
-* returned that section correctly and `ConfigFormField` renders `type:'widget'`
-* perfectly well — and nothing ever asked camera-grid for it. The Cluster →
-* Pipeline → Device Overrides page interrogates a HAND-WRITTEN list of four
-* addons (`PIPELINE_CLUSTER_DEVICE_ADDONS`), whose own comment says an addon
-* not on it "falls off silently".
-*
-* Adding a fifth name to that list would have been the wrong fix twice over:
-* that page is per-camera DETECTION tuning, and a grid's geometry belongs
-* beside PTZ and motion zones on the camera itself. The device page is
-* BINDING-driven (D12), so the way in is a capability bound to the device —
-* and this cap carries its section the way `recording` does, by RETURNING it
-* from `getDeviceSettingsContribution`.
-*
-* Seven other widgets are still declared the other way, through a
-* `deviceConfig.ui` block the framework derives a section from. That route
-* gives the addon no say in where its own panel lands and no way to decline
-* for a device the panel does not suit, which is why this one does not use it.
-*
-* ## Why one addon may implement it
-*
-* It is a device-scoped NATIVE cap, registered by the grid camera device
-* itself. Nothing else declares a composite camera, so nothing else has a
-* layout — and the device-scoped route means the widget asks THE camera, not
-* "the camera-grid addon", which is what let the old custom-action pair be
-* reached only by a caller that already knew the addon id.
-*
-* ## The tab
-*
-* `streaming`, not a top-tab of its own. A grid's geometry IS what its stream
-* is, so the Streaming tab is where it belongs; a `grid` top-tab would need an
-* entry in `WELL_KNOWN_TAB_MAP` or the device page renders the raw id as the
-* label (measured on the robot camera, 2026-09-06 — a tab called "navigation"
-* next to "PTZ").
-*/
-/** A rectangle in normalized [0,1] coordinates of whatever contains it. */
-var GridNormalizedRectSchema = object({
-	x: number().min(0).max(1),
-	y: number().min(0).max(1),
-	width: number().gt(0).max(1),
-	height: number().gt(0).max(1)
-});
-/**
-* One source camera, the part of its picture taken, and where that part lands.
-*
-* Both rectangles are NORMALIZED (D519): a source camera can change resolution
-* — a profile switch, a firmware update, a substream that comes back different
-* — and a stored PIXEL rectangle would quietly start cutting the wrong region,
-* which is the class of bug nobody files.
-*/
-var GridLayoutCellSchema = object({
-	deviceId: number().int().positive(),
-	/** The part of the SOURCE taken, normalized against the source. */
-	source: GridNormalizedRectSchema,
-	/** Where it lands, normalized against the CANVAS. */
-	cell: GridNormalizedRectSchema
-});
-/**
-* Which profiles this grid can actually compose, and why not.
-*
-* 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
-* low" is, and it is the one an operator can act on.
-*/
-var GridProfileOfferSchema = object({
-	profile: _enum([
-		"high",
-		"mid",
-		"low"
-	]),
-	offered: boolean(),
-	/** Sources that cannot serve it. Empty when it is offered, or when there are no cells. */
-	missingSources: array(number().int().positive()),
-	/**
-	* The canvas this profile composes onto, `WxH`, or empty when it is not
-	* offered. DERIVED from the cells and the sources' own size at this profile —
-	* it is reported because nothing else in the system would ever say what the
-	* grid came out as, and because it is the number an operator would otherwise
-	* expect to type.
-	*/
-	canvas: string(),
-	/**
-	* Whether this profile is PUBLISHED, of the ones the grid could serve.
-	*
-	* A grid's `high` is composed of its sources' `high`, so on a 4K fleet it is
-	* a 4K canvas built from 4K decodes — something to opt into, not something a
-	* viewer's adaptive should be handed by climbing to the top rung it can see.
-	* Default is `mid` + `low`.
-	*/
-	published: boolean()
-});
-var GridLayoutViewSchema = object({
-	/** The persisted grid row this camera was declared from. */
-	instanceId: string(),
-	deviceId: number().int().nonnegative(),
-	name: string(),
-	/**
-	* NO canvas size. A grid's resolution is not authored: each profile derives
-	* its own from the cells and its sources' dimensions. The two numbers that
-	* used to be here were a text field that silently decided both how much the
-	* composite cost and how sharp it was — see `profiles[].canvas` for what it
-	* came out as.
-	*/
-	fps: number().int(),
-	cells: array(GridLayoutCellSchema),
-	/** What the catalog will publish, and what it refuses to. Read-only. */
-	profiles: array(GridProfileOfferSchema)
-});
-var GridLayoutPatchSchema = object({
-	deviceId: number().int().nonnegative(),
-	name: string().min(1).max(160).optional(),
-	fps: number().int().min(1).max(60).optional(),
-	/** Which profiles to publish. See `GridProfileOffer.published`. */
-	publishedProfiles: array(_enum([
-		"high",
-		"mid",
-		"low"
-	])).max(3).optional(),
-	/**
-	* The whole cell list at once. A per-cell patch would need an ordering the
-	* editor does not have, and a half-applied layout is a picture nobody asked
-	* for.
-	*/
-	cells: array(GridLayoutCellSchema).max(16)
-});
-DeviceType.Camera, method(object({ deviceId: number().int().nonnegative() }), GridLayoutViewSchema.nullable(), { auth: "admin" }), method(GridLayoutPatchSchema, GridLayoutViewSchema, {
-	kind: "mutation",
-	auth: "admin"
-});
-/**
 * Motion-zones share the same MaskShape vocabulary as privacy-mask — the
 * on-camera motion-detection mask is a single `grid` region (a row-major
 * boolean cell lattice the camera's onboard VMD evaluates). Composing it as
@@ -33909,37 +33416,37 @@ var rebootCapability = {
 		auth: "admin"
 	}) }
 };
-/**
-* `recording` cap — footage availability + HLS playback manifests + per-device
-* recording config. NOTE on events (source of truth, R5/C3): this cap carries
-* NO event surface — `getPlaybackManifest` returns playlist URLs only. Timeline
-* events (motion/object/audio) come from `pipelineAnalytics` (durable SQLite
-* rows) and are the ONLY event surface — the recorder has none. The in-RAM
-* playback markers it used to build were deleted on 2026-08-29 because nothing
-* ever read them. Event<->footage joins are by time, padded with the shared
-* `EVENT_PAD_MS` (`interfaces/recording-config.ts`).
-*/
-var RecordingStatusSchema = object({
-	deviceId: number(),
-	enabled: boolean(),
-	/** THE derived storage mode, from the one definition
-	*  (`deriveRecordingMode`) — never a second enum. A duplicated list is how
-	*  `on-device-decision` could have reached the recorder and not the status. */
-	activeMode: RecordingStorageModeSchema,
-	nodeId: string(),
-	storageBytes: number()
-});
 var RecordingRangeSchema = object({
 	profile: string(),
 	startMs: number(),
 	endMs: number()
 });
+/**
+* How a source ANSWERED, on every singular read of this cap.
+*
+* `'read'` — it looked. `ranges: []` / `days: []` is then a real claim: this
+* source has no coverage in the window. `'unreadable'` — nobody could look
+* (the camera was unreachable, the calendar rung threw, the location is
+* unmounted, the node is still on the old build), and the emptiness beside it
+* means NOTHING.
+*
+* The batch rows have carried this since the grid existed; the SINGULAR
+* answers gained it with the collection (D625 §10.4), because they are the
+* ones the single-camera picker uses and because a half-converted fleet makes
+* "nobody looked" common for the length of a deploy. Without it the timeline
+* has no vocabulary for it, and `(data ?? [])` in a viewer turns a rollout into
+* a fleet of cameras that appear to have lost their recordings (D315, D393).
+*/
+var RecordingReadSchema = _enum(["read", "unreadable"]);
 var RecordingAvailabilitySchema = object({
 	deviceId: number(),
+	/** See {@link RecordingReadSchema}. An `'unreadable'` answer carries an empty
+	*  `ranges` that means nothing — never draw it as "no footage". */
+	read: RecordingReadSchema,
 	ranges: array(RecordingRangeSchema),
 	/**
-	* Every profile this camera has footage in — not only the one `ranges`
-	* describes (D433).
+	* Every profile this camera has footage in AT THIS SOURCE — not only the one
+	* `ranges` describes (D433).
 	*
 	* `ranges` answers for ONE profile by design: the timeline is a single bar,
 	* and enumerating all of them triples the directory reads for a bar that
@@ -33954,17 +33461,287 @@ var RecordingAvailabilitySchema = object({
 	*/
 	profilesWithFootage: array(string())
 });
-var RecordingDaysSchema = object({
+var RecordingDaysSchema = object({
+	deviceId: number(),
+	/** See {@link RecordingReadSchema}. `days: []` on an `'unreadable'` answer is
+	*  "nobody could look", and the date-picker must not spell it the same as
+	*  "no footage this month". */
+	read: RecordingReadSchema,
+	/** Local-midnight epochs (UTC ms) of days that have ≥1 recorded segment. */
+	days: array(number())
+});
+var RecordingManifestSchema = object({
+	deviceId: number(),
+	/** Local filesystem path to the master playlist; null when no recording exists for the requested range. */
+	localMasterPath: string().nullable(),
+	/** HTTP(S) URL to the master playlist on the recording node's playback server
+	*  (the PRIMARY candidate); null when no recording / server. Carries the
+	*  scoped playback token in its path. */
+	playbackUrl: string().nullable(),
+	/**
+	* Candidate master-playlist URLs the client tries in order (LAN first, then
+	* remote — Tailscale/Cloudflare if the operator configured extra hosts), each
+	* carrying the same scoped token. `playbackUrl` is the first entry. Empty when
+	* there is no recording / server.
+	*/
+	playbackEndpoints: array(string())
+});
+var RecordingSourceAvailabilitySchema = object({
+	state: _enum([
+		"ok",
+		"sleeping",
+		"unreachable",
+		"no-storage",
+		"index-empty"
+	]),
+	/** Free text, shown verbatim. Names the camera's own refusal when there is one. */
+	reason: string().optional(),
+	/** When this source's coverage was last CONFIRMED. A cached answer is never
+	*  drawn as current: the surface shows the age whenever it is older than the
+	*  refresh interval. The clip catalog's `catalogAsOf`, under the name the
+	*  timeline uses for it. */
+	coverageAsOf: number().optional()
+});
+/**
+* One SOURCE of recorded coverage for a camera — a row of the picker.
+*
+* A provider lists the sources IT serves for that device, and answers for each
+* of them whether it can answer at all. A provider with nothing to offer on a
+* camera returns `[]` — it is not that camera's business. The five availability
+* states are `ClipSourceAvailability`'s verbatim: they mean exactly the same
+* things about a coverage index as about a clip catalog, and `sleeping` in
+* particular is what stops a battery camera being woken to paint a bar.
+*/
+var RecordingSourceSchema = object({
+	/** The source id. {@link RECORDING_SOURCE_CAMSTACK} for ours (RESERVED), a
+	*  vendor namespace (`native:reolink:onboard`, …) for a camera's own store. */
+	source: string(),
+	/** Operator-facing name of the source ("CamStack recordings", "SD card"). */
+	label: string(),
+	/**
+	* The addon that SERVES this row, and the value a later call passes as
+	* `provider`.
+	*
+	* Optional for version skew only. The collection dispatcher stamps it from
+	* the registry, so a row that travelled through the fan-out carries the
+	* authoritative id whatever the provider filled in (D557 §4).
+	*/
+	addonId: string().optional(),
+	availability: RecordingSourceAvailabilitySchema
+});
+/**
+* What a surface may DRAW for this (camera, source) — D612's rule applied to a
+* timeline: **the source declares what it can do, and the surface draws what
+* was declared. It never assumes, and never offers a gesture it will then
+* refuse.** D612 exists because `8` and `16` were offered as clip rates, the
+* broker clamped them to `4`, and no line anywhere said so.
+*
+* Asked once per (camera, source) before anything is drawn — never replaced by
+* a constant the surface keeps, which is the second authority D612 ends.
+*/
+var RecordingSourceOptionsSchema = object({
+	/** How this source's media reaches the player.
+	*  `archive` = our own indexed segment tree; `stream` = the provider's
+	*  forward-only fMP4 (D597); `realtime` = a replay bound to wall clock. */
+	transport: _enum([
+		"archive",
+		"stream",
+		"realtime"
+	]),
+	/** What the BAR means. `continuous` = gaps are holes in a recording;
+	*  `sparse` = gaps are the absence of one, and must be drawn as such.
+	*
+	*  Not an onboard-only concession: measured 2026-09-24, OUR bar covers 98.8 %
+	*  of 592's day and 1.2 % of 1436's. It is a fact about a (source, camera)
+	*  pair, and ours answers it per camera from `deriveRecordingMode`. */
+	coverage: _enum(["continuous", "sparse"]),
+	/** Where the playhead may be put.
+	*  `free`    — anywhere, to the frame.
+	*  `forward` — only ahead of the current position.
+	*  `segment` — a position SNAPS to the head of the covering segment; a finer
+	*              ask is accepted by the camera and SILENTLY IGNORED. Measured
+	*              on 1436 (Hikvision V5.7.1, 2026-09-23): a window-narrowed
+	*              `ContentMgmt/search` returns a row and a `playbackURI`, the
+	*              replay opens 200 and delivers media — and the burned-in OSD of
+	*              the first frame reads the SEGMENT HEAD every time. Calling
+	*              that `forward` would tell the surface it may move the playhead
+	*              ahead within a loaded segment, which it may not. */
+	seek: _enum([
+		"free",
+		"forward",
+		"segment"
+	]),
+	/** Frame-step BACKWARD is meaningful. */
+	stepBack: boolean(),
+	/** Whether the drag-scrub gesture is served, as opposed to refused by name. */
+	scrub: boolean(),
+	/** Deliverable rates, ascending, always containing `1`. The surface draws its
+	*  picker from this and from NOTHING else (D612, D620, D621). `0` is not a
+	*  member: pause is the absence of a rate. */
+	rates: array(number().positive()).min(1).readonly(),
+	/** TRUE when a read of this source HOLDS the camera's only playback session.
+	*  A surface with this set makes at most ONE read at a time and draws no
+	*  scrub-thumbnail strip, no hover preview, no prefetch and no background
+	*  refresh. The precedent is exact and expensive: filling one screen of
+	*  Hikvision thumbnails at 1.01× realtime consumed fifteen minutes of that
+	*  camera's only playback session (1.2.126, reported within minutes), and a
+	*  timeline is a screenful of reads by construction. */
+	exclusive: boolean()
+});
+/**
+* How to PLAY the instant that was asked for, from the chosen source.
+*
+* No new media transport is built for onboard sources: the `clip` arm is a
+* DELEGATION to the `videoclips` transport that vendor already has (D597 /
+* D616 / D617). The onboard half of this collection is a PROJECTION of
+* `videoclips` for coverage and a delegation to it for bytes.
+*/
+var RecordingPlaybackSchema = discriminatedUnion("kind", [
+	object({
+		kind: literal("hls"),
+		manifest: RecordingManifestSchema
+	}),
+	object({
+		kind: literal("clip"),
+		/** The `videoclips` source namespace this clip id belongs to. */
+		source: string(),
+		clipId: string(),
+		/** Where this clip actually STARTS. On a `seek: 'segment'` source the
+		*  playhead lands here, not at the requested instant — the surface must be
+		*  TOLD, not left to discover it from a burned-in OSD. */
+		startsAtMs: number()
+	}),
+	object({
+		kind: literal("none"),
+		reason: string()
+	})
+]);
+DeviceType.Camera, method(object({ deviceId: number() }), array(RecordingSourceSchema).readonly(), {
+	kind: "query",
+	auth: "protected"
+}), method(object({
+	deviceId: number(),
+	/**
+	* WHICH provider to ask — the `addonId` a {@link RecordingSourceSchema}
+	* row carries, never a source id and never a list. **REQUIRED**, in the
+	* schema, where the generated types make it unomittable rather than
+	* merely discouraged (D554 amended).
+	*
+	* It was learned the expensive way on `videoclips.listClips`: measured
+	* on the live hub 2026-09-20, device 592 bound to `recorder` AND
+	* `provider-reolink`, a bare call with `limit: 3` answered SIX rows,
+	* three from each source, merged — `device-collection-dispatch.ts`
+	* leaves an unpinned fan-out un-narrowed, so absence buys the union the
+	* method exists not to be. An un-narrowed `getAvailability` would do
+	* that to a TIMELINE: our ranges and the card's clips unioned into one
+	* bar, which is "two sources are never drawn together" broken in the
+	* one place it matters most.
+	*
+	* A provider the device is not bound to is refused BY NAME (D552's
+	* `rejectUnresolvedAddonPin`), never answered by another one.
+	*/
+	provider: string().min(1),
+	fromMs: number(),
+	toMs: number(),
+	/**
+	* Answer for THIS profile instead of the source's preferred one (D433).
+	* Absent keeps the timeline's behaviour — one bar, one profile, one set
+	* of reads. `profilesWithFootage` on the answer says what may be asked
+	* for.
+	*/
+	profile: string().optional()
+}), RecordingAvailabilitySchema, {
+	kind: "query",
+	auth: "protected"
+}), method(object({
+	deviceId: number(),
+	provider: string().min(1),
+	fromMs: number(),
+	toMs: number(),
+	tzOffsetMinutes: number()
+}), RecordingDaysSchema, {
+	kind: "query",
+	auth: "protected"
+}), method(object({
+	deviceId: number(),
+	provider: string().min(1),
+	fromMs: number(),
+	toMs: number(),
+	profile: CamProfileSchema.optional()
+}), RecordingPlaybackSchema, {
+	kind: "query",
+	auth: "protected"
+}), method(object({
+	deviceId: number(),
+	provider: string().min(1)
+}), RecordingSourceOptionsSchema, {
+	kind: "query",
+	auth: "protected"
+});
+/**
+* `recording-archive` — OUR archive, and the intent that fills it.
+*
+* The system-singleton half of the 2026-09-24 cut (D625). `recording` used to
+* be one 33-method system singleton holding two unrelated subjects: three
+* per-camera READS about coverage and playback, and everything else — storage
+* locations, retention, relocation, rebalance, the ops log, the placement
+* table and the byte-plane primitives our scrub and export are built on.
+*
+* The reads became a device-scoped COLLECTION, so a camera's own card can be a
+* source beside ours (`recording.cap.ts`). Everything that is about OUR store,
+* or unimplementable by a camera, stayed here.
+*
+* ## On the name
+*
+* `recording-storage` was the obvious choice and is wrong: this cap also holds
+* `getDeviceConfig`/`setDeviceConfig`, which are recording INTENT — bands,
+* retention, the D62 switch authority — and a name that says "storage" invites
+* the next reader to move them out again. An archive is a thing we keep, and
+* what we keep it under is a policy; the name covers both halves honestly and
+* sits in the existing family (`recording-onboard`, `recording-export`,
+* `recording-signal`).
+*
+* ## What must NOT happen to it
+*
+* It stays a SINGLETON. It is registered by `recorder`, which is
+* `placement: 'any-node'` and runs on every recording node; the hub dispatches
+* to one of them. Putting the ledger, the placement table or the relocation
+* jobs behind a fan-out is the one genuinely dangerous move in this cut.
+*
+* `getDeviceConfig` / `setDeviceConfig` in particular are the D62 recording
+* authority (`CameraSwitch.authority`). If a write reached a different provider
+* than the read — which a collection fan-out permits — two authorities would
+* decide when one camera records, and the symptom (recording silently off, or
+* a `bands` array clobbered by a partial write) is durable and silent. Keeping
+* them here means the worst case during a rollout is a 412: the switch refuses
+* to flip and SAYS so. **Do not move them into the collection, at any point,
+* for any reason.**
+*
+* ## The two batch reads
+*
+* `getAvailabilityBatch` / `getDaysWithRecordingsBatch` take `deviceIds:
+* number[]` with no single `deviceId`, and a device-scoped mount routes
+* through `getProviderForDevice(deviceId)` — there is nothing for it to route
+* on. They stay here, and on this cap the batch is explicitly OURS: a grid has
+* no per-camera picker, and a caller that wants another source's coverage asks
+* `recording.getAvailability` per device with that source's `provider`.
+*/
+var RecordingStatusSchema = object({
 	deviceId: number(),
-	/** Local-midnight epochs (UTC ms) of days that have ≥1 recorded segment. */
-	days: array(number())
+	enabled: boolean(),
+	/** THE derived storage mode, from the one definition
+	*  (`deriveRecordingMode`) — never a second enum. A duplicated list is how
+	*  `on-device-decision` could have reached the recorder and not the status. */
+	activeMode: RecordingStorageModeSchema,
+	nodeId: string(),
+	storageBytes: number()
 });
 /**
 * One camera's row in a `getAvailabilityBatch` answer.
 *
-* `ranges` is EXACTLY what `getAvailability` returns for that camera — the
-* batch collapses the transport, not the work — plus the one thing the singular
-* method never had to say:
+* `ranges` is EXACTLY what `recording.getAvailability` returns for that camera
+* at OUR source — the batch collapses the transport, not the work — plus the
+* `read` mark the singular answer now carries too (D625):
 *
 *  - `read: 'read'` — answered. `ranges: []` means "read, and this camera has
 *    no footage in the window", which is a real claim.
@@ -33996,22 +33773,6 @@ var RecordingDaysForDeviceSchema = object({
 	/** Local-midnight epochs (UTC ms) of days that have ≥1 recorded segment. */
 	days: array(number()).readonly()
 });
-var RecordingManifestSchema = object({
-	deviceId: number(),
-	/** Local filesystem path to the master playlist; null when no recording exists for the requested range. */
-	localMasterPath: string().nullable(),
-	/** HTTP(S) URL to the master playlist on the recording node's playback server
-	*  (the PRIMARY candidate); null when no recording / server. Carries the
-	*  scoped playback token in its path. */
-	playbackUrl: string().nullable(),
-	/**
-	* Candidate master-playlist URLs the client tries in order (LAN first, then
-	* remote — Tailscale/Cloudflare if the operator configured extra hosts), each
-	* carrying the same scoped token. `playbackUrl` is the first entry. Empty when
-	* there is no recording / server.
-	*/
-	playbackEndpoints: array(string())
-});
 /**
 * Recording storage usage for one camera — what the ARCHIVE holds for it,
 * across every profile and every resolvable location on this node.
@@ -34270,34 +34031,12 @@ var ReadWindowBytesResultSchema = discriminatedUnion("kind", [object({
 	segmentEndMs: number()
 })]);
 method(object({
-	deviceId: number(),
-	fromMs: number(),
-	toMs: number(),
-	/**
-	* Answer for THIS profile instead of the preferred one (D433). Absent
-	* keeps the timeline's behaviour — one bar, one profile, one set of
-	* reads. `profilesWithFootage` on the answer says what may be asked
-	* for.
-	*/
-	profile: string().optional()
-}), RecordingAvailabilitySchema, {
-	kind: "query",
-	auth: "protected"
-}), method(object({
 	deviceIds: array(number()).min(1).max(200),
 	fromMs: number(),
 	toMs: number()
 }), array(RecordingAvailabilityForDeviceSchema).readonly(), {
 	kind: "query",
 	auth: "protected"
-}), method(object({
-	deviceId: number(),
-	fromMs: number(),
-	toMs: number(),
-	tzOffsetMinutes: number()
-}), RecordingDaysSchema, {
-	kind: "query",
-	auth: "protected"
 }), method(object({
 	deviceIds: array(number()).min(1).max(200),
 	fromMs: number(),
@@ -34306,13 +34045,6 @@ method(object({
 }), array(RecordingDaysForDeviceSchema).readonly(), {
 	kind: "query",
 	auth: "protected"
-}), method(object({
-	deviceId: number(),
-	fromMs: number(),
-	toMs: number()
-}), RecordingManifestSchema, {
-	kind: "query",
-	auth: "protected"
 }), method(object({}), RecordingStorageUsageSchema, {
 	kind: "query",
 	auth: "admin"
@@ -34524,245 +34256,761 @@ var ExportTimelapseSchema = object({
 * silent. `maxLifeMs` bounds how long the finished file is kept;
 * `deleteAfterDownload` removes it shortly after the first complete download.
 */
-var ExportOptionsSchema = object({
-	speed: ExportSpeedSchema.optional(),
-	timelapse: ExportTimelapseSchema.optional(),
-	includeAudio: boolean(),
-	maxLifeMs: number().int().positive(),
-	deleteAfterDownload: boolean(),
-	title: string().max(200).optional(),
-	/** Notification-output target ids to ping when this export becomes ready. */
-	notifyTargetIds: array(string().min(1)).max(20).optional()
-}).superRefine((v, ctx) => {
-	if (v.speed !== void 0 && v.timelapse !== void 0) ctx.addIssue({
-		code: ZodIssueCode.custom,
-		message: "speed and timelapse are mutually exclusive",
-		path: ["timelapse"]
-	});
+var ExportOptionsSchema = object({
+	speed: ExportSpeedSchema.optional(),
+	timelapse: ExportTimelapseSchema.optional(),
+	includeAudio: boolean(),
+	maxLifeMs: number().int().positive(),
+	deleteAfterDownload: boolean(),
+	title: string().max(200).optional(),
+	/** Notification-output target ids to ping when this export becomes ready. */
+	notifyTargetIds: array(string().min(1)).max(20).optional()
+}).superRefine((v, ctx) => {
+	if (v.speed !== void 0 && v.timelapse !== void 0) ctx.addIssue({
+		code: ZodIssueCode.custom,
+		message: "speed and timelapse are mutually exclusive",
+		path: ["timelapse"]
+	});
+});
+var ExportStateSchema = _enum([
+	"queued",
+	"rendering",
+	"ready",
+	"failed",
+	"expired",
+	"deleted"
+]);
+/**
+* WHAT an export is — the authority, as opposed to the four top-level fields
+* the Library sorts and labels on (D558 § 2.2).
+*
+* Read it through {@link exportSubjectOf}, never off the record directly: the
+* field is optional for the history rows written before it existed, and that
+* absence has exactly one interpreter.
+*/
+var ExportSubjectSchema = discriminatedUnion("kind", [object({
+	kind: literal("footage"),
+	deviceId: number(),
+	profiles: array(string()).min(1),
+	fromMs: number(),
+	toMs: number()
+}), object({
+	kind: literal("clip"),
+	deviceId: number(),
+	provider: string().min(1),
+	source: string().min(1),
+	sourceLabel: string().min(1),
+	clipId: string().min(1),
+	/**
+	* WHERE IN THE CATALOG to confirm this clip — the day window the surface was
+	* already listing when the operator picked the segment.
+	*
+	* It is **not** a time range control and it never becomes one: the record's
+	* `fromMs`/`toMs` come from the catalog ROW and from nothing a caller
+	* supplied (D558 § 5.4.3), and a window that does not contain the clip is a
+	* `catalog-miss`, not a silently wider search. It exists because
+	* `videoclips.listClips` takes `since`/`until` and has no by-handle twin:
+	* the catalog check D558 asks for is literally that call, and a call needs a
+	* window. The surface has one — `ClipsBrowser`'s `dayWindow`, one local
+	* wall-clock day, which is also the only width measured to be cheap (one
+	* day on 592 lists 171 clips in 712 ms, a busy day 546 in 2.0 s; twenty days
+	* of one child's events took 3.6–5.4 s).
+	*/
+	catalogWindow: object({
+		sinceMs: number(),
+		untilMs: number()
+	}),
+	profile: _enum([
+		"high",
+		"mid",
+		"low"
+	]),
+	/**
+	* The operator's authorisation to wake a sleeping camera for this export.
+	* ONE definition, in the cap that owns the clip read ({@link ClipWakeSchema}),
+	* because the gate that honours it is the clip provider's sleep gate — a
+	* second enum here would be a second contract. Absent by default; never
+	* settable by a scheduler or a retry.
+	*
+	* **One authorised yes is ONE wake.** A failed clip export is retried only by
+	* an operator act that asks again; a queued job that outlived its wake fails
+	* with a reason rather than waking on its turn; and this subject carries
+	* exactly one profile precisely so one tap is never two fetches (D558 § 5.2).
+	*/
+	wake: ClipWakeSchema.optional()
+})]);
+/**
+* One export job / history row.
+*
+* **`subject` is the AUTHORITY on what was exported. `deviceId`, `profile`,
+* `fromMs` and `toMs` are its PROJECTION** — kept top-level because the whole
+* Library sorts and labels on them (`library-items.ts` orders an export by
+* `fromMs`; `export-format.ts` draws `rangeLabel` from the pair), and a row
+* that did not fill them would sort under the epoch and render a blank range.
+* Write to the subject and read from the projection and the two will disagree;
+* the projection is derived at creation and never edited afterwards.
+*
+* And they mean DIFFERENT FACTS for the two kinds, which is the part a reader
+* who knows only the recording export will get wrong:
+*
+* | field | `kind:'footage'` | `kind:'clip'` |
+* | --- | --- | --- |
+* | `fromMs`/`toMs` | the stretch the operator ASKED for | the camera's own boundaries, always `clip.timeRange`, never anything a caller supplied |
+* | `profile` | the stream rendered | the twin actually SERVED (`subject.profile` is the one asked for) |
+*
+* Same type, different fact — the shape this repo keeps getting wrong (D385's
+* two authorities, D224's second copy).
+*/
+var ExportRecordSchema = object({
+	id: string(),
+	deviceId: number(),
+	profile: string(),
+	fromMs: number(),
+	toMs: number(),
+	/**
+	* What this export IS. Optional ONLY for the rows written before D558: the
+	* store parses every row through this schema on every read, so a required
+	* field would make the export AUDIT — which is the whole reason rows survive
+	* file deletion — unreadable in one release. Absence means `footage`, and
+	* {@link exportSubjectOf} is the one place that says so.
+	*/
+	subject: ExportSubjectSchema.optional(),
+	options: ExportOptionsSchema,
+	state: ExportStateSchema,
+	/** 0–100 while rendering; null otherwise. */
+	progressPct: number().nullable(),
+	/** File size once ready; null before. */
+	fileBytes: number().nullable(),
+	expiresAt: number(),
+	deleteAfterDownload: boolean(),
+	/** Epoch of the first complete download; null until then. */
+	downloadedAt: number().nullable(),
+	createdAt: number(),
+	/** User id/name that requested the export. */
+	createdBy: string(),
+	/** Failure reason when state is 'failed'; null otherwise. */
+	error: string().nullable()
+});
+_enum([
+	"catalog-miss",
+	"catalog-unreachable",
+	"no-file-for-window",
+	"clip-in-progress",
+	"unsupported-option",
+	"sleeping",
+	"camera-refused",
+	"fetch-failed",
+	"too-large-to-transfer",
+	"wake-expired"
+]);
+/** `<token>: <prose>` — the ONE composition of a clip export's failure string. */
+function clipExportFailure(code, detail) {
+	return detail.length > 0 ? `${code}: ${detail}` : code;
+}
+/** Candidate download URLs (LAN first, then operator extra hosts). */
+var ExportDownloadSchema = object({
+	url: string(),
+	endpoints: array(string())
+});
+/**
+* A finished export's bytes, inline.
+*
+* `bytes` is the DECODED length — the number the caller bounds and logs
+* against, so nobody has to infer it from the base64 length.
+*/
+var ExportBytesSchema = object({
+	base64: string(),
+	contentType: string(),
+	/** Suggested filename, extension included. */
+	name: string(),
+	bytes: number().int().nonnegative()
+});
+/** Canonical `profiles[]`, falling back to the legacy singular `profile`. */
+function resolveExportProfiles(input) {
+	if (input.profiles !== void 0 && input.profiles.length > 0) return [...input.profiles];
+	if (typeof input.profile === "string" && input.profile.length > 0) return [input.profile];
+	return [];
+}
+method(object({
+	deviceId: number(),
+	/** @deprecated Prefer `profiles`. Kept so timelapse/notifiers keep working. */
+	profile: string().optional(),
+	profiles: array(string()).min(1).optional(),
+	/** Footage only — a clip's boundaries are the camera's. */
+	fromMs: number().optional(),
+	toMs: number().optional(),
+	/** What to export. Absent means the legacy flat footage request. */
+	subject: ExportSubjectSchema.optional(),
+	options: ExportOptionsSchema
+}).superRefine((v, ctx) => {
+	if (v.subject?.kind === "clip") {
+		if (v.subject.deviceId !== v.deviceId) ctx.addIssue({
+			code: ZodIssueCode.custom,
+			message: `subject.deviceId (${v.subject.deviceId}) must equal deviceId (${v.deviceId}) — the top-level field is what per-device scope enforcement reads`,
+			path: ["subject", "deviceId"]
+		});
+		if (v.fromMs !== void 0 || v.toMs !== void 0) ctx.addIssue({
+			code: ZodIssueCode.custom,
+			message: "a clip export asks for no time range: the camera chose the boundaries and they are read from the catalog row",
+			path: ["fromMs"]
+		});
+		return;
+	}
+	if (v.subject?.kind === "footage" && v.subject.deviceId !== v.deviceId) ctx.addIssue({
+		code: ZodIssueCode.custom,
+		message: `subject.deviceId (${v.subject.deviceId}) must equal deviceId (${v.deviceId})`,
+		path: ["subject", "deviceId"]
+	});
+	const fromMs = v.subject?.kind === "footage" ? v.subject.fromMs : v.fromMs;
+	const toMs = v.subject?.kind === "footage" ? v.subject.toMs : v.toMs;
+	if (typeof fromMs !== "number" || typeof toMs !== "number") ctx.addIssue({
+		code: ZodIssueCode.custom,
+		message: "a footage export needs fromMs and toMs",
+		path: ["fromMs"]
+	});
+	if ((v.subject?.kind === "footage" ? [...v.subject.profiles] : resolveExportProfiles(v)).length < 1) ctx.addIssue({
+		code: ZodIssueCode.custom,
+		message: "pass profiles[] (min 1) or legacy profile",
+		path: ["profiles"]
+	});
+}), ExportRecordSchema, {
+	kind: "mutation",
+	auth: "protected"
+}), method(object({ deviceId: number().optional() }), array(ExportRecordSchema), {
+	kind: "query",
+	auth: "protected"
+}), method(object({ exportId: string() }), ExportRecordSchema, {
+	kind: "query",
+	auth: "protected"
+}), method(object({ exportId: string() }), ExportRecordSchema, {
+	kind: "mutation",
+	auth: "protected"
+}), method(object({ exportId: string() }), ExportRecordSchema, {
+	kind: "mutation",
+	auth: "protected"
+}), method(object({ exportId: string() }), ExportDownloadSchema, {
+	kind: "query",
+	auth: "protected"
+}), method(object({ exportId: string() }), ExportBytesSchema, {
+	kind: "query",
+	auth: "protected"
+});
+/**
+* Vendor-neutral **onboard** recording + storage cap — what the CAMERA
+* writes to the CAMERA's own card, on the camera's own schedule.
+*
+* This is NOT `recording.cap.ts`. That one is CamStack's recorder: our
+* footage ledger, our storage locations, our retention. This one has a
+* different authority — the camera's firmware — and per D62 it stores
+* nothing of its own. Every value here is read from the camera and every
+* write goes back to the camera; there is no CamStack-side mirror that
+* could disagree with the device.
+*
+* ## One shape, two firmwares
+*
+* Measured 2026-09-22 against the live fleet:
+*
+* | fact | Hikvision (ISAPI) | Reolink (Baichuan) |
+* | --- | --- | --- |
+* | storage | `ContentMgmt/Storage` `<hdd>` rows: status, capacity, freeSpace (MB) | `getHddInfoList` (cmd 102): `mount`, `format`, `capacity` GB + `capacityM` MB remainder |
+* | tracks | several (101 **and** 103 on both 1436 and 3833), each with its own schedule | one per channel |
+* | schedule | per track, 7 `ScheduleAction` blocks: DayOfWeek + TimeOfDay range + ONE `ActionRecordingMode` | per trigger type, a 168-char weekly HOUR mask |
+* | triggers | `CMR`, `MOTION` | `Normal`, `MD`, `people`, `vehicle`, `dog_cat`, `crossline`, `intrude`, `loitering` |
+* | pre-record | `PreRecordTimeSeconds` | `preRecordTime` |
+* | post-record | `PostRecordTimeSeconds` | `recordDelayTime` |
+* | overwrite | per track `LoopEnable` | `cycle`, with `cycleList` enumerating the accepted values |
+* | segment length | not exposed on V5.7.1 | `packageTime` (minutes) |
+*
+* The two schedule models look different and are the same thing in
+* different coordinates: both answer "for this trigger, during which
+* weekly windows does the camera record". {@link RecordWindow} is that
+* question in one shape — Hikvision's ranges map straight onto it,
+* Reolink's mask expands into hour-aligned windows.
+*
+* ## Union, not intersection
+*
+* **The same fields exist on every camera.** What differs per device is
+* which VALUES that device accepts, and that is what {@link
+* RecordingOnboardOptions} reports — a `{ readable, writable, reason }`
+* per field plus the schedule's own limits. A control a camera cannot
+* honour is rendered DISABLED WITH ITS REASON, never missing and never
+* dead: disabled must not look like broken.
+*
+* ## Refusal by name
+*
+* A write a camera cannot honour is refused with a sentence the operator
+* can read — never accepted and dropped. Both providers refuse through
+* {@link describeOnboardRefusal}, so the vocabulary is one function and
+* one test, not two hand-written vendor opinions.
+*
+* Follows the D14 `deviceConfig` archetype (see `stream-params.cap.ts`):
+* `getOptions` advertises per-camera availability, `getStatus` (auto-
+* injected from `status`) reports the live values, and a single
+* `setSettings` mutation applies a partial change. No hand-written
+* settings-contribution methods.
+*/
+/**
+* What makes the camera start recording during a window.
+*
+* The union of both vendors' vocabularies. `continuous` is Hikvision's
+* `CMR` and Reolink's `Normal`; `motion` is `MOTION` / `MD`. The
+* object-class triggers are Reolink-only today and the smart-event ones
+* (`lineCrossing`, `intrusion`, `loitering`) are Reolink-only on the
+* firmwares measured — a camera that cannot record on a trigger simply
+* does not list it in `options.schedule.triggers`, and a window naming
+* it is REFUSED, not dropped.
+*/
+var RecordTriggerSchema = _enum([
+	"continuous",
+	"motion",
+	"person",
+	"vehicle",
+	"animal",
+	"lineCrossing",
+	"intrusion",
+	"loitering",
+	"alarmInput"
+]);
+/**
+* One weekly recording window: "on `day`, from `startMinute` to
+* `endMinute`, record on `trigger`".
+*
+* `day` is 0 = Monday … 6 = Sunday (ISO order, which is also the order
+* both firmwares enumerate). Minutes are local camera time since
+* midnight; `endMinute` may be 1440, meaning end of day — that is
+* Hikvision's literal `24:00` and Reolink's 24th mask slot, and
+* collapsing it to 0 would turn a whole-day window into an empty one.
+*/
+var RecordWindowSchema = object({
+	trigger: RecordTriggerSchema,
+	day: number().int().min(0).max(6),
+	startMinute: number().int().min(0).max(1439),
+	endMinute: number().int().min(1).max(1440)
+});
+/** Status of one physical volume, as the camera itself describes it. */
+var OnboardStorageVolumeSchema = object({
+	/** The camera's own id for the volume (`hdd/id`, Reolink `HddInfo/number`). */
+	id: string(),
+	/** The camera's own name for it, when it gives one (`hddName`). */
+	label: string().optional(),
+	status: _enum([
+		"ok",
+		"unformatted",
+		"error",
+		"offline",
+		"unknown"
+	]),
+	/**
+	* Total size in MB, or **null when the camera did not say**.
+	*
+	* Never 0 for an unreadable value: a measurement that failed is not a
+	* measurement (D393), and a card whose size is unknown must not be
+	* rendered as a card of size zero.
+	*/
+	capacityMb: number().nullable(),
+	/**
+	* Free space in MB, or null when unknown.
+	*
+	* **Not a proxy for "has footage".** Measured 2026-09-22: 1436 and
+	* 1439 both report exactly 11776 MB free — the fixed reserve a looping
+	* card converges on once it has wrapped. At loop steady state the
+	* number is identical whether the camera recorded yesterday or stopped
+	* a month ago.
+	*/
+	freeMb: number().nullable(),
+	/** True when the camera reports the volume writable (`property` RW). */
+	writable: boolean().optional()
+});
+/**
+* What the camera is doing with its own storage, right now.
+*
+* Every scalar is nullable and **null means the camera did not answer**,
+* never a default. A form that seeds `0` from an unanswered read invites
+* the operator to save that 0 back onto the camera.
+*/
+var RecordingOnboardStatusSchema = object({
+	storage: discriminatedUnion("kind", [
+		object({
+			kind: literal("present"),
+			volumes: array(OnboardStorageVolumeSchema)
+		}),
+		object({
+			kind: literal("absent"),
+			reason: string()
+		}),
+		object({
+			kind: literal("unknown"),
+			reason: string()
+		})
+	]),
+	tracks: array(object({
+		id: string(),
+		enabled: boolean(),
+		isVideo: boolean(),
+		/** From the camera's own track description. Null when it does not say. */
+		codec: string().nullable(),
+		resolution: string().nullable(),
+		/** Per-track overwrite flag, where the firmware keeps it per track. */
+		overwriteWhenFull: boolean().nullable()
+	})),
+	/**
+	* The track the write path targets — the enabled VIDEO one. Null when
+	* no track could be identified, which is itself a refusal reason.
+	*/
+	primaryTrackId: string().nullable(),
+	/** Master "record to the card at all" switch. */
+	enabled: boolean().nullable(),
+	overwriteWhenFull: boolean().nullable(),
+	preRecordSec: number().nullable(),
+	postRecordSec: number().nullable(),
+	/** Length of one recorded file, in minutes. */
+	segmentMinutes: number().nullable(),
+	/** The primary track's weekly windows, flattened. */
+	windows: array(RecordWindowSchema),
+	/**
+	* How many windows the camera described that CamStack could NOT read —
+	* an unrecognised trigger, an unparseable clock, a weekday it does not
+	* name.
+	*
+	* A dropped window is work the reader threw away, and a schedule that
+	* silently shows fewer rows than the camera holds is how an operator
+	* saves back a schedule shorter than the one they were looking at
+	* (D391). Non-zero means the window list is INCOMPLETE and a write
+	* that replaces it would delete what was not shown — which is why a
+	* provider reporting a non-zero count also reports the schedule as not
+	* writable.
+	*/
+	unreadableWindows: number(),
+	/**
+	* The camera is scheduled to record and has NO usable storage.
+	*
+	* A first-class fact because it is the fleet's most common silent
+	* defect: measured 2026-09-22, 1441 and 3831 are both motion-recording
+	* to a card that is not there. Neither the schedule nor the storage
+	* read says anything wrong on its own; only the pair does.
+	*/
+	recordingToNowhere: boolean(),
+	lastFetchedAt: number()
+});
+/** Numeric range descriptor — `{ min, max, step }` per the getOptions convention. */
+var RangeSchema = object({
+	min: number(),
+	max: number(),
+	step: number()
+});
+/**
+* The values a camera actually takes for a numeric field, when they are a SET
+* rather than a range.
+*
+* `{min,max,step}` cannot say what these two firmwares do. Measured on 1436
+* (I91DN) on 2026-09-22 by writing each value and reading it back:
+*
+* - pre-record: `0, 5, 10, 15, 20, 25, 30` and `2147483647` (INT32_MAX, the
+*   camera's "no limit" — `-1` and `4294967295` both land on it);
+* - post-record: `5, 10, 30, 60, 120, 300, 600`.
+*
+* Neither is expressible as a step: the first has a sentinel two billion away
+* from its neighbours, the second doubles and then jumps. A range that tried
+* would forbid values the camera takes AND permit values it silently replaces
+* with 5 — wrong in both directions at once.
+*
+* `sentinel` names the member that is not a duration, so a surface can render
+* "no limit" instead of `2147483647` seconds.
+*/
+var AllowedValuesSchema = object({
+	values: array(number()).min(1),
+	sentinel: object({
+		value: number(),
+		meaning: _enum(["no-limit", "disabled"])
+	}).optional()
 });
-var ExportStateSchema = _enum([
-	"queued",
-	"rendering",
-	"ready",
-	"failed",
-	"expired",
-	"deleted"
-]);
 /**
-* WHAT an export is — the authority, as opposed to the four top-level fields
-* the Library sorts and labels on (D558 § 2.2).
+* Per-field availability on ONE camera.
 *
-* Read it through {@link exportSubjectOf}, never off the record directly: the
-* field is optional for the history rows written before it existed, and that
-* absence has exactly one interpreter.
+* The field exists on every camera — this says whether this one can be
+* read and whether it can be written, and `reason` says why not when
+* either is false. The UI renders the control DISABLED with the reason
+* rather than hiding it, so a limitation is legible instead of looking
+* like a missing feature.
 */
-var ExportSubjectSchema = discriminatedUnion("kind", [object({
-	kind: literal("footage"),
-	deviceId: number(),
-	profiles: array(string()).min(1),
-	fromMs: number(),
-	toMs: number()
-}), object({
-	kind: literal("clip"),
-	deviceId: number(),
-	provider: string().min(1),
-	source: string().min(1),
-	sourceLabel: string().min(1),
-	clipId: string().min(1),
+var OnboardFieldSupportSchema = object({
+	readable: boolean(),
+	writable: boolean(),
+	/** Required whenever `readable` or `writable` is false. */
+	reason: string().optional()
+});
+/** What this camera's schedule model can express. */
+var OnboardScheduleSupportSchema = object({
+	support: OnboardFieldSupportSchema,
 	/**
-	* WHERE IN THE CATALOG to confirm this clip — the day window the surface was
-	* already listing when the operator picked the segment.
+	* The smallest time step the camera can express, in minutes.
 	*
-	* It is **not** a time range control and it never becomes one: the record's
-	* `fromMs`/`toMs` come from the catalog ROW and from nothing a caller
-	* supplied (D558 § 5.4.3), and a window that does not contain the clip is a
-	* `catalog-miss`, not a silently wider search. It exists because
-	* `videoclips.listClips` takes `since`/`until` and has no by-handle twin:
-	* the catalog check D558 asks for is literally that call, and a call needs a
-	* window. The surface has one — `ClipsBrowser`'s `dayWindow`, one local
-	* wall-clock day, which is also the only width measured to be cheap (one
-	* day on 592 lists 171 clips in 712 ms, a busy day 546 in 2.0 s; twenty days
-	* of one child's events took 3.6–5.4 s).
+	* Hikvision takes arbitrary minutes (`00:05:00`–`23:57:00` observed on
+	* 1436's track 103). Reolink's schedule is a 7×24 HOUR mask, so 60. A
+	* window whose edges are not a multiple of this is REFUSED rather than
+	* quietly rounded — rounding is how an operator's 06:30 becomes 06:00
+	* and nothing says so.
 	*/
-	catalogWindow: object({
-		sinceMs: number(),
-		untilMs: number()
-	}),
-	profile: _enum([
-		"high",
-		"mid",
-		"low"
-	]),
+	granularityMinutes: number(),
+	/** Triggers this camera can record on. A window naming another is refused. */
+	triggers: array(RecordTriggerSchema),
 	/**
-	* The operator's authorisation to wake a sleeping camera for this export.
-	* ONE definition, in the cap that owns the clip read ({@link ClipWakeSchema}),
-	* because the gate that honours it is the clip provider's sleep gate — a
-	* second enum here would be a second contract. Absent by default; never
-	* settable by a scheduler or a retry.
+	* False when the camera stores ONE trigger per time range, so two
+	* windows overlapping on the same day cannot carry different triggers.
+	* True on Reolink, whose mask is per-trigger and independent.
+	*/
+	supportsOverlappingTriggers: boolean()
+});
+var RecordingOnboardOptionsSchema = object({
+	enabled: OnboardFieldSupportSchema,
+	overwriteWhenFull: OnboardFieldSupportSchema,
+	preRecordSec: OnboardFieldSupportSchema,
+	preRecordSecRange: RangeSchema.optional(),
+	/** Preferred over the range when the camera takes a SET, not a span. */
+	preRecordSecAllowed: AllowedValuesSchema.optional(),
+	postRecordSec: OnboardFieldSupportSchema,
+	postRecordSecRange: RangeSchema.optional(),
+	/** Preferred over the range when the camera takes a SET, not a span. */
+	postRecordSecAllowed: AllowedValuesSchema.optional(),
+	segmentMinutes: OnboardFieldSupportSchema,
+	segmentMinutesRange: RangeSchema.optional(),
+	/** Preferred over the range when the camera takes a SET, not a span. */
+	segmentMinutesAllowed: AllowedValuesSchema.optional(),
+	schedule: OnboardScheduleSupportSchema
+});
+/**
+* A partial change. Every field optional.
+*
+* Unlike the other `deviceConfig` caps, a provider here does **NOT**
+* silently ignore a field it cannot support — it refuses, by name,
+* through {@link describeOnboardRefusal}. Silence on a recording setting
+* is the failure D62 exists to prevent: the operator believes the camera
+* is recording the way the form says, and it is not.
+*/
+var RecordingOnboardPatchSchema = object({
+	enabled: boolean().optional(),
+	overwriteWhenFull: boolean().optional(),
+	preRecordSec: number().optional(),
+	postRecordSec: number().optional(),
+	segmentMinutes: number().optional(),
+	/** The complete new window set for the primary track — not a delta. */
+	windows: array(RecordWindowSchema).optional()
+});
+var recordingOnboardCapability = {
+	name: "recording-onboard",
+	scope: "device",
+	deviceNative: true,
+	mode: "singleton",
+	deviceTypes: [DeviceType.Camera],
+	deviceConfig: { ui: {
+		kind: "derived-form",
+		builderId: "recording-onboard",
+		tab: "recording"
+	} },
+	methods: {
+		getOptions: method(object({ deviceId: number() }), RecordingOnboardOptionsSchema),
+		setSettings: method(object({
+			deviceId: number(),
+			settings: RecordingOnboardPatchSchema
+		}), _void(), {
+			kind: "mutation",
+			auth: "admin"
+		})
+	},
+	status: {
+		schema: RecordingOnboardStatusSchema,
+		kind: "poll"
+	},
+	runtimeState: RecordingOnboardStatusSchema,
+	/**
+	* Runtime-state durability: **restored** — operator-set camera-side
+	* recording config; mutation-driven, and the storage half is the last
+	* thing the camera said about its own card.
 	*
-	* **One authorised yes is ONE wake.** A failed clip export is retried only by
-	* an operator act that asks again; a queued job that outlived its wake fails
-	* with a reason rather than waking on its turn; and this subject carries
-	* exactly one profile precisely so one tap is never two fetches (D558 § 5.2).
+	* See `RuntimeStateDurability`. Enforced by
+	* `scripts/check-runtime-state-durability.ts`.
 	*/
-	wake: ClipWakeSchema.optional()
-})]);
+	durability: "restored",
+	/** Clock fields: written, but excluded from the compare that decides
+	*  whether persisting is worth a SQLite commit. */
+	volatileStateFields: ["lastFetchedAt"]
+};
 /**
-* One export job / history row.
+* Day-of-week names in the cap's index order (0 = Monday), for messages
+* an operator reads and for Hikvision's `<DayOfWeek>` element.
+*/
+var DAY_NAMES = [
+	"Monday",
+	"Tuesday",
+	"Wednesday",
+	"Thursday",
+	"Friday",
+	"Saturday",
+	"Sunday"
+];
+/**
+* Does `patch` ask this camera for something it cannot do?
 *
-* **`subject` is the AUTHORITY on what was exported. `deviceId`, `profile`,
-* `fromMs` and `toMs` are its PROJECTION** — kept top-level because the whole
-* Library sorts and labels on them (`library-items.ts` orders an export by
-* `fromMs`; `export-format.ts` draws `rangeLabel` from the pair), and a row
-* that did not fill them would sort under the epoch and render a blank range.
-* Write to the subject and read from the projection and the two will disagree;
-* the projection is derived at creation and never edited afterwards.
+* Returns the operator-readable reason, or `null` when every field in
+* the patch is within what `options` says this camera accepts. A
+* provider calls this BEFORE touching the camera and throws the string:
+* refusing is the point, and refusing identically on both vendors is why
+* this is one function.
 *
-* And they mean DIFFERENT FACTS for the two kinds, which is the part a reader
-* who knows only the recording export will get wrong:
+* The order of checks is the order an operator would read them: the
+* scalar knobs first, then the schedule, because a schedule complaint is
+* longer and a scalar one is usually the real problem.
+*/
+function describeOnboardRefusal(options, patch) {
+	if (patch.enabled !== void 0 && !options.enabled.writable) return unwritable("the master recording switch", options.enabled.reason);
+	if (patch.overwriteWhenFull !== void 0 && !options.overwriteWhenFull.writable) return unwritable("overwrite-when-full", options.overwriteWhenFull.reason);
+	const preRefusal = refuseNumeric("pre-record seconds", patch.preRecordSec, options.preRecordSec, options.preRecordSecRange, options.preRecordSecAllowed);
+	if (preRefusal) return preRefusal;
+	const postRefusal = refuseNumeric("post-record seconds", patch.postRecordSec, options.postRecordSec, options.postRecordSecRange, options.postRecordSecAllowed);
+	if (postRefusal) return postRefusal;
+	const segmentRefusal = refuseNumeric("segment length (minutes)", patch.segmentMinutes, options.segmentMinutes, options.segmentMinutesRange, options.segmentMinutesAllowed);
+	if (segmentRefusal) return segmentRefusal;
+	if (patch.windows !== void 0) {
+		const scheduleRefusal = refuseSchedule(options, patch.windows);
+		if (scheduleRefusal) return scheduleRefusal;
+	}
+	return null;
+}
+function unwritable(what, reason) {
+	return reason ? `this camera cannot change ${what}: ${reason}` : `this camera cannot change ${what}`;
+}
+function refuseNumeric(what, value, support, range, allowed) {
+	if (value === void 0) return null;
+	if (!support.writable) return unwritable(what, support.reason);
+	if (!Number.isFinite(value)) return `${what} must be a number, got ${String(value)}`;
+	if (allowed) {
+		if (allowed.values.includes(value)) return null;
+		const say = (v) => allowed.sentinel !== void 0 && v === allowed.sentinel.value ? allowed.sentinel.meaning === "no-limit" ? "no limit" : "off" : String(v);
+		return `this camera accepts ${what} only as ${allowed.values.map(say).join(", ")}; ${say(value)} is not one of them`;
+	}
+	if (!range) return null;
+	if (value < range.min || value > range.max) return `this camera accepts ${what} between ${String(range.min)} and ${String(range.max)}; ${String(value)} is outside that`;
+	if (range.step > 0 && (value - range.min) % range.step !== 0) return `this camera accepts ${what} in steps of ${String(range.step)} from ${String(range.min)}; ${String(value)} is not one of them`;
+	return null;
+}
+function refuseSchedule(options, windows) {
+	const schedule = options.schedule;
+	if (!schedule.support.writable) return unwritable("the recording schedule", schedule.support.reason);
+	const allowed = new Set(schedule.triggers);
+	for (const window of windows) {
+		if (!allowed.has(window.trigger)) {
+			const offer = schedule.triggers.length > 0 ? schedule.triggers.join(", ") : "none";
+			return `this camera cannot record on "${window.trigger}"; it records on: ${offer}`;
+		}
+		if (window.endMinute <= window.startMinute) return `a window on ${dayName(window.day)} ends at or before it starts (${String(window.startMinute)} → ${String(window.endMinute)})`;
+		const step = schedule.granularityMinutes;
+		if (step > 1 && (window.startMinute % step !== 0 || window.endMinute % step !== 0)) return `this camera's schedule only moves in ${String(step)}-minute steps; the ${dayName(window.day)} window ${formatMinutes(window.startMinute)}–${formatMinutes(window.endMinute)} is not aligned to them`;
+	}
+	if (!schedule.supportsOverlappingTriggers) {
+		const clash = findOverlapWithDifferentTrigger(windows);
+		if (clash) return `this camera stores one trigger per time range, so "${clash.a.trigger}" and "${clash.b.trigger}" cannot both cover ${dayName(clash.a.day)} ${formatMinutes(Math.max(clash.a.startMinute, clash.b.startMinute))}–${formatMinutes(Math.min(clash.a.endMinute, clash.b.endMinute))}`;
+	}
+	return null;
+}
+function findOverlapWithDifferentTrigger(windows) {
+	for (let i = 0; i < windows.length; i += 1) for (let j = i + 1; j < windows.length; j += 1) {
+		const a = windows[i];
+		const b = windows[j];
+		if (!a || !b) continue;
+		if (a.day !== b.day) continue;
+		if (a.trigger === b.trigger) continue;
+		if (a.startMinute < b.endMinute && b.startMinute < a.endMinute) return {
+			a,
+			b
+		};
+	}
+	return null;
+}
+function dayName(day) {
+	return DAY_NAMES[day] ?? `day ${String(day)}`;
+}
+/** `510` → `08:30`. For messages, not for the wire. */
+function formatMinutes(minute) {
+	const hour = Math.floor(minute / 60);
+	const rest = minute % 60;
+	return `${String(hour).padStart(2, "0")}:${String(rest).padStart(2, "0")}`;
+}
+/**
+* Parse a Hikvision `<TimeOfDay>` into minutes since midnight.
 *
-* | field | `kind:'footage'` | `kind:'clip'` |
-* | --- | --- | --- |
-* | `fromMs`/`toMs` | the stretch the operator ASKED for | the camera's own boundaries, always `clip.timeRange`, never anything a caller supplied |
-* | `profile` | the stream rendered | the twin actually SERVED (`subject.profile` is the one asked for) |
+* The firmware is not self-consistent and both spellings are real, on
+* the same camera in the same block: a start time reads `00:00:00` and
+* the matching end time reads `24:00`. Seconds are accepted and
+* discarded — the cap's resolution is minutes — and `24:00` maps to
+* {@link MINUTES_PER_DAY}, not to 0.
 *
-* Same type, different fact — the shape this repo keeps getting wrong (D385's
-* two authorities, D224's second copy).
+* Returns null for anything else, which a caller reports as a window it
+* could not read rather than as midnight.
 */
-var ExportRecordSchema = object({
-	id: string(),
-	deviceId: number(),
-	profile: string(),
-	fromMs: number(),
-	toMs: number(),
-	/**
-	* What this export IS. Optional ONLY for the rows written before D558: the
-	* store parses every row through this schema on every read, so a required
-	* field would make the export AUDIT — which is the whole reason rows survive
-	* file deletion — unreadable in one release. Absence means `footage`, and
-	* {@link exportSubjectOf} is the one place that says so.
-	*/
-	subject: ExportSubjectSchema.optional(),
-	options: ExportOptionsSchema,
-	state: ExportStateSchema,
-	/** 0–100 while rendering; null otherwise. */
-	progressPct: number().nullable(),
-	/** File size once ready; null before. */
-	fileBytes: number().nullable(),
-	expiresAt: number(),
-	deleteAfterDownload: boolean(),
-	/** Epoch of the first complete download; null until then. */
-	downloadedAt: number().nullable(),
-	createdAt: number(),
-	/** User id/name that requested the export. */
-	createdBy: string(),
-	/** Failure reason when state is 'failed'; null otherwise. */
-	error: string().nullable()
-});
-_enum([
-	"catalog-miss",
-	"catalog-unreachable",
-	"no-file-for-window",
-	"clip-in-progress",
-	"unsupported-option",
-	"sleeping",
-	"camera-refused",
-	"fetch-failed",
-	"too-large-to-transfer",
-	"wake-expired"
-]);
-/** `<token>: <prose>` — the ONE composition of a clip export's failure string. */
-function clipExportFailure(code, detail) {
-	return detail.length > 0 ? `${code}: ${detail}` : code;
+function timeOfDayToMinutes(value) {
+	const match = /^(\d{1,2}):(\d{2})(?::(\d{2}))?$/.exec(value.trim());
+	if (!match) return null;
+	const hour = Number(match[1]);
+	const minute = Number(match[2]);
+	if (!Number.isInteger(hour) || !Number.isInteger(minute)) return null;
+	if (minute > 59) return null;
+	const total = hour * 60 + minute;
+	if (total > 1440) return null;
+	return total;
 }
-/** Candidate download URLs (LAN first, then operator extra hosts). */
-var ExportDownloadSchema = object({
-	url: string(),
-	endpoints: array(string())
-});
 /**
-* A finished export's bytes, inline.
+* Render minutes back as a Hikvision `TimeOfDay`.
 *
-* `bytes` is the DECODED length — the number the caller bounds and logs
-* against, so nobody has to infer it from the base64 length.
+* Emits the camera's own two spellings: `24:00` for end-of-day, because
+* that is what the firmware writes and `24:00:00` is not observed, and
+* `HH:MM:SS` otherwise.
 */
-var ExportBytesSchema = object({
-	base64: string(),
-	contentType: string(),
-	/** Suggested filename, extension included. */
-	name: string(),
-	bytes: number().int().nonnegative()
-});
-/** Canonical `profiles[]`, falling back to the legacy singular `profile`. */
-function resolveExportProfiles(input) {
-	if (input.profiles !== void 0 && input.profiles.length > 0) return [...input.profiles];
-	if (typeof input.profile === "string" && input.profile.length > 0) return [input.profile];
-	return [];
+function minutesToTimeOfDay(minute) {
+	if (minute >= 1440) return "24:00";
+	const hour = Math.floor(minute / 60);
+	const rest = minute % 60;
+	return `${String(hour).padStart(2, "0")}:${String(rest).padStart(2, "0")}:00`;
 }
-method(object({
-	deviceId: number(),
-	/** @deprecated Prefer `profiles`. Kept so timelapse/notifiers keep working. */
-	profile: string().optional(),
-	profiles: array(string()).min(1).optional(),
-	/** Footage only — a clip's boundaries are the camera's. */
-	fromMs: number().optional(),
-	toMs: number().optional(),
-	/** What to export. Absent means the legacy flat footage request. */
-	subject: ExportSubjectSchema.optional(),
-	options: ExportOptionsSchema
-}).superRefine((v, ctx) => {
-	if (v.subject?.kind === "clip") {
-		if (v.subject.deviceId !== v.deviceId) ctx.addIssue({
-			code: ZodIssueCode.custom,
-			message: `subject.deviceId (${v.subject.deviceId}) must equal deviceId (${v.deviceId}) — the top-level field is what per-device scope enforcement reads`,
-			path: ["subject", "deviceId"]
-		});
-		if (v.fromMs !== void 0 || v.toMs !== void 0) ctx.addIssue({
-			code: ZodIssueCode.custom,
-			message: "a clip export asks for no time range: the camera chose the boundaries and they are read from the catalog row",
-			path: ["fromMs"]
+/** `'Monday'` → 0. Case-insensitive. Null for anything unrecognised. */
+function dayOfWeekToIndex(value) {
+	const needle = value.trim().toLowerCase();
+	const index = DAY_NAMES.findIndex((name) => name.toLowerCase() === needle);
+	return index >= 0 ? index : null;
+}
+/**
+* Which fields of a patch the camera did NOT take verbatim.
+*
+* Measured on a Hikvision I91DN (1436, 2026-09-22): a `PUT` of
+* `PreRecordTimeSeconds: 8` answered `200`, `statusCode 1`, `OK` — and stored
+* **5**. Neither the asked value nor the previous one. The camera declares no
+* allowed set for that field, so there is nothing to refuse against before the
+* wire: `/capabilities` returns a plain value where a constrained field would
+* carry an `opt=` list.
+*
+* So the only honest moment is after the read-back, and re-reading alone is
+* not enough — it makes the difference VISIBLE while leaving it unexplained.
+* A write that reports success for a value the camera never took is the same
+* silent substitution D599 removed from the clip path, wearing a different hat.
+*
+* Compares only the fields the patch actually named: a field nobody asked
+* about cannot have been clamped, and a read-back that could not answer it is
+* `stored: null` rather than a claim.
+*/
+function describeOnboardClamp(patch, landed) {
+	const out = [];
+	for (const [field, asked] of Object.entries(patch)) {
+		if (asked === void 0) continue;
+		if (typeof asked !== "number" && typeof asked !== "boolean" && typeof asked !== "string") continue;
+		const raw = landed === null ? void 0 : landed[field];
+		const stored = typeof raw === "number" || typeof raw === "boolean" || typeof raw === "string" ? raw : null;
+		if (stored !== asked) out.push({
+			field,
+			asked,
+			stored
 		});
-		return;
 	}
-	if (v.subject?.kind === "footage" && v.subject.deviceId !== v.deviceId) ctx.addIssue({
-		code: ZodIssueCode.custom,
-		message: `subject.deviceId (${v.subject.deviceId}) must equal deviceId (${v.deviceId})`,
-		path: ["subject", "deviceId"]
-	});
-	const fromMs = v.subject?.kind === "footage" ? v.subject.fromMs : v.fromMs;
-	const toMs = v.subject?.kind === "footage" ? v.subject.toMs : v.toMs;
-	if (typeof fromMs !== "number" || typeof toMs !== "number") ctx.addIssue({
-		code: ZodIssueCode.custom,
-		message: "a footage export needs fromMs and toMs",
-		path: ["fromMs"]
-	});
-	if ((v.subject?.kind === "footage" ? [...v.subject.profiles] : resolveExportProfiles(v)).length < 1) ctx.addIssue({
-		code: ZodIssueCode.custom,
-		message: "pass profiles[] (min 1) or legacy profile",
-		path: ["profiles"]
-	});
-}), ExportRecordSchema, {
-	kind: "mutation",
-	auth: "protected"
-}), method(object({ deviceId: number().optional() }), array(ExportRecordSchema), {
-	kind: "query",
-	auth: "protected"
-}), method(object({ exportId: string() }), ExportRecordSchema, {
-	kind: "query",
-	auth: "protected"
-}), method(object({ exportId: string() }), ExportRecordSchema, {
-	kind: "mutation",
-	auth: "protected"
-}), method(object({ exportId: string() }), ExportRecordSchema, {
-	kind: "mutation",
-	auth: "protected"
-}), method(object({ exportId: string() }), ExportDownloadSchema, {
-	kind: "query",
-	auth: "protected"
-}), method(object({ exportId: string() }), ExportBytesSchema, {
-	kind: "query",
-	auth: "protected"
-});
+	return out;
+}
 /**
 * A camera's own "record me NOW" LEVEL — a signal the device raises while
 * something it knows about is happening (a robot vacuum cleaning, a machine
@@ -42655,24 +42903,6 @@ Object.freeze({
 		addonId: null,
 		access: "view"
 	},
-	"events.getEventClipUrl": {
-		capName: "events",
-		capScope: "device",
-		addonId: null,
-		access: "view"
-	},
-	"events.getEvents": {
-		capName: "events",
-		capScope: "device",
-		addonId: null,
-		access: "view"
-	},
-	"events.getEventThumbnail": {
-		capName: "events",
-		capScope: "device",
-		addonId: null,
-		access: "view"
-	},
 	"faceGallery.assignFace": {
 		capName: "face-gallery",
 		capScope: "system",
@@ -45547,224 +45777,236 @@ Object.freeze({
 		addonId: null,
 		access: "create"
 	},
-	"recording.applyDeviceSettingsPatch": {
+	"recording.getAvailability": {
 		capName: "recording",
-		capScope: "system",
+		capScope: "device",
 		addonId: null,
-		access: "create"
+		access: "view"
 	},
-	"recording.cancelRelocateJob": {
+	"recording.getDaysWithRecordings": {
 		capName: "recording",
-		capScope: "system",
+		capScope: "device",
 		addonId: null,
-		access: "create"
+		access: "view"
 	},
-	"recording.cancelStorageMigrationMove": {
+	"recording.getPlayback": {
 		capName: "recording",
-		capScope: "system",
+		capScope: "device",
 		addonId: null,
-		access: "create"
+		access: "view"
 	},
-	"recording.deleteFootprint": {
+	"recording.getPlaybackOptions": {
 		capName: "recording",
-		capScope: "system",
+		capScope: "device",
 		addonId: null,
-		access: "delete"
+		access: "view"
 	},
-	"recording.getAvailability": {
+	"recording.listSources": {
 		capName: "recording",
-		capScope: "system",
+		capScope: "device",
 		addonId: null,
 		access: "view"
 	},
-	"recording.getAvailabilityBatch": {
-		capName: "recording",
+	"recordingArchive.applyDeviceSettingsPatch": {
+		capName: "recording-archive",
 		capScope: "system",
 		addonId: null,
-		access: "view"
+		access: "create"
 	},
-	"recording.getDaysWithRecordings": {
-		capName: "recording",
+	"recordingArchive.cancelRelocateJob": {
+		capName: "recording-archive",
 		capScope: "system",
 		addonId: null,
-		access: "view"
+		access: "create"
 	},
-	"recording.getDaysWithRecordingsBatch": {
-		capName: "recording",
+	"recordingArchive.cancelStorageMigrationMove": {
+		capName: "recording-archive",
+		capScope: "system",
+		addonId: null,
+		access: "create"
+	},
+	"recordingArchive.deleteFootprint": {
+		capName: "recording-archive",
+		capScope: "system",
+		addonId: null,
+		access: "delete"
+	},
+	"recordingArchive.getAvailabilityBatch": {
+		capName: "recording-archive",
 		capScope: "system",
 		addonId: null,
 		access: "view"
 	},
-	"recording.getDeviceConfig": {
-		capName: "recording",
+	"recordingArchive.getDaysWithRecordingsBatch": {
+		capName: "recording-archive",
 		capScope: "system",
 		addonId: null,
 		access: "view"
 	},
-	"recording.getDeviceLiveContribution": {
-		capName: "recording",
+	"recordingArchive.getDeviceConfig": {
+		capName: "recording-archive",
 		capScope: "system",
 		addonId: null,
 		access: "view"
 	},
-	"recording.getDeviceSettingsContribution": {
-		capName: "recording",
+	"recordingArchive.getDeviceLiveContribution": {
+		capName: "recording-archive",
 		capScope: "system",
 		addonId: null,
 		access: "view"
 	},
-	"recording.getPlacement": {
-		capName: "recording",
+	"recordingArchive.getDeviceSettingsContribution": {
+		capName: "recording-archive",
 		capScope: "system",
 		addonId: null,
 		access: "view"
 	},
-	"recording.getPlaybackManifest": {
-		capName: "recording",
+	"recordingArchive.getPlacement": {
+		capName: "recording-archive",
 		capScope: "system",
 		addonId: null,
 		access: "view"
 	},
-	"recording.getRelocateResidue": {
-		capName: "recording",
+	"recordingArchive.getRelocateResidue": {
+		capName: "recording-archive",
 		capScope: "system",
 		addonId: null,
 		access: "view"
 	},
-	"recording.getStatus": {
-		capName: "recording",
+	"recordingArchive.getStatus": {
+		capName: "recording-archive",
 		capScope: "system",
 		addonId: null,
 		access: "view"
 	},
-	"recording.getStorageMigrationMoveStatus": {
-		capName: "recording",
+	"recordingArchive.getStorageMigrationMoveStatus": {
+		capName: "recording-archive",
 		capScope: "system",
 		addonId: null,
 		access: "view"
 	},
-	"recording.getStorageUsage": {
-		capName: "recording",
+	"recordingArchive.getStorageUsage": {
+		capName: "recording-archive",
 		capScope: "system",
 		addonId: null,
 		access: "view"
 	},
-	"recording.listOpsLog": {
-		capName: "recording",
+	"recordingArchive.listOpsLog": {
+		capName: "recording-archive",
 		capScope: "system",
 		addonId: null,
 		access: "view"
 	},
-	"recording.listRelocateJobs": {
-		capName: "recording",
+	"recordingArchive.listRelocateJobs": {
+		capName: "recording-archive",
 		capScope: "system",
 		addonId: null,
 		access: "view"
 	},
-	"recording.locateSegment": {
-		capName: "recording",
+	"recordingArchive.locateSegment": {
+		capName: "recording-archive",
 		capScope: "system",
 		addonId: null,
 		access: "view"
 	},
-	"recording.pauseForStorageMigration": {
-		capName: "recording",
+	"recordingArchive.pauseForStorageMigration": {
+		capName: "recording-archive",
 		capScope: "system",
 		addonId: null,
 		access: "create"
 	},
-	"recording.planStorageRebalance": {
-		capName: "recording",
+	"recordingArchive.planStorageRebalance": {
+		capName: "recording-archive",
 		capScope: "system",
 		addonId: null,
 		access: "view"
 	},
-	"recording.pruneFootage": {
-		capName: "recording",
+	"recordingArchive.pruneFootage": {
+		capName: "recording-archive",
 		capScope: "system",
 		addonId: null,
 		access: "create"
 	},
-	"recording.readGopBytes": {
-		capName: "recording",
+	"recordingArchive.readGopBytes": {
+		capName: "recording-archive",
 		capScope: "system",
 		addonId: null,
 		access: "view"
 	},
-	"recording.readSegmentBytes": {
-		capName: "recording",
+	"recordingArchive.readSegmentBytes": {
+		capName: "recording-archive",
 		capScope: "system",
 		addonId: null,
 		access: "view"
 	},
-	"recording.readWindowBytes": {
-		capName: "recording",
+	"recordingArchive.readWindowBytes": {
+		capName: "recording-archive",
 		capScope: "system",
 		addonId: null,
 		access: "view"
 	},
-	"recording.reconcileLedgerAgainstDisk": {
-		capName: "recording",
+	"recordingArchive.reconcileLedgerAgainstDisk": {
+		capName: "recording-archive",
 		capScope: "system",
 		addonId: null,
 		access: "create"
 	},
-	"recording.refreshStorageLocationsForMigration": {
-		capName: "recording",
+	"recordingArchive.refreshStorageLocationsForMigration": {
+		capName: "recording-archive",
 		capScope: "system",
 		addonId: null,
 		access: "create"
 	},
-	"recording.relocateFootage": {
-		capName: "recording",
+	"recordingArchive.relocateFootage": {
+		capName: "recording-archive",
 		capScope: "system",
 		addonId: null,
 		access: "create"
 	},
-	"recording.renderClip": {
-		capName: "recording",
+	"recordingArchive.renderClip": {
+		capName: "recording-archive",
 		capScope: "system",
 		addonId: null,
 		access: "create"
 	},
-	"recording.renderGif": {
-		capName: "recording",
+	"recordingArchive.renderGif": {
+		capName: "recording-archive",
 		capScope: "system",
 		addonId: null,
 		access: "create"
 	},
-	"recording.rescanStorage": {
-		capName: "recording",
+	"recordingArchive.rescanStorage": {
+		capName: "recording-archive",
 		capScope: "system",
 		addonId: null,
 		access: "create"
 	},
-	"recording.resumeForStorageMigration": {
-		capName: "recording",
+	"recordingArchive.resumeForStorageMigration": {
+		capName: "recording-archive",
 		capScope: "system",
 		addonId: null,
 		access: "create"
 	},
-	"recording.setDeviceConfig": {
-		capName: "recording",
+	"recordingArchive.setDeviceConfig": {
+		capName: "recording-archive",
 		capScope: "system",
 		addonId: null,
 		access: "create"
 	},
-	"recording.setDevicePlacement": {
-		capName: "recording",
+	"recordingArchive.setDevicePlacement": {
+		capName: "recording-archive",
 		capScope: "system",
 		addonId: null,
 		access: "create"
 	},
-	"recording.startStorageMigrationMove": {
-		capName: "recording",
+	"recordingArchive.startStorageMigrationMove": {
+		capName: "recording-archive",
 		capScope: "system",
 		addonId: null,
 		access: "create"
 	},
-	"recording.startStorageRebalance": {
-		capName: "recording",
+	"recordingArchive.startStorageRebalance": {
+		capName: "recording-archive",
 		capScope: "system",
 		addonId: null,
 		access: "create"
@@ -48069,21 +48311,6 @@ Object.freeze({
 		form: "single",
 		optional: false
 	}],
-	"events.getEventClipUrl": [{
-		name: "deviceId",
-		form: "single",
-		optional: false
-	}],
-	"events.getEvents": [{
-		name: "deviceId",
-		form: "single",
-		optional: false
-	}],
-	"events.getEventThumbnail": [{
-		name: "deviceId",
-		form: "single",
-		optional: false
-	}],
 	"faceGallery.getFaceByTrack": [{
 		name: "deviceId",
 		form: "single",
@@ -49002,107 +49229,117 @@ Object.freeze({
 		form: "single",
 		optional: false
 	}],
-	"recording.deleteFootprint": [{
+	"recording.getAvailability": [{
 		name: "deviceId",
 		form: "single",
 		optional: false
 	}],
-	"recording.getAvailability": [{
+	"recording.getDaysWithRecordings": [{
 		name: "deviceId",
 		form: "single",
 		optional: false
 	}],
-	"recording.getAvailabilityBatch": [{
-		name: "deviceIds",
-		form: "array",
+	"recording.getPlayback": [{
+		name: "deviceId",
+		form: "single",
 		optional: false
 	}],
-	"recording.getDaysWithRecordings": [{
+	"recording.getPlaybackOptions": [{
 		name: "deviceId",
 		form: "single",
 		optional: false
 	}],
-	"recording.getDaysWithRecordingsBatch": [{
-		name: "deviceIds",
-		form: "array",
+	"recording.listSources": [{
+		name: "deviceId",
+		form: "single",
 		optional: false
 	}],
-	"recording.getDeviceConfig": [{
+	"recordingArchive.deleteFootprint": [{
 		name: "deviceId",
 		form: "single",
 		optional: false
 	}],
-	"recording.getPlaybackManifest": [{
+	"recordingArchive.getAvailabilityBatch": [{
+		name: "deviceIds",
+		form: "array",
+		optional: false
+	}],
+	"recordingArchive.getDaysWithRecordingsBatch": [{
+		name: "deviceIds",
+		form: "array",
+		optional: false
+	}],
+	"recordingArchive.getDeviceConfig": [{
 		name: "deviceId",
 		form: "single",
 		optional: false
 	}],
-	"recording.listOpsLog": [{
+	"recordingArchive.listOpsLog": [{
 		name: "deviceId",
 		form: "single",
 		optional: true
 	}],
-	"recording.locateSegment": [{
+	"recordingArchive.locateSegment": [{
 		name: "deviceId",
 		form: "single",
 		optional: false
 	}],
-	"recording.pruneFootage": [{
+	"recordingArchive.pruneFootage": [{
 		name: "deviceId",
 		form: "single",
 		optional: false
 	}],
-	"recording.readGopBytes": [{
+	"recordingArchive.readGopBytes": [{
 		name: "deviceId",
 		form: "single",
 		optional: false
 	}],
-	"recording.readSegmentBytes": [{
+	"recordingArchive.readSegmentBytes": [{
 		name: "deviceId",
 		form: "single",
 		optional: false
 	}],
-	"recording.readWindowBytes": [{
+	"recordingArchive.readWindowBytes": [{
 		name: "deviceId",
 		form: "single",
 		optional: false
 	}],
-	"recording.reconcileLedgerAgainstDisk": [{
+	"recordingArchive.reconcileLedgerAgainstDisk": [{
 		name: "deviceId",
 		form: "single",
 		optional: true
 	}],
-	"recording.relocateFootage": [{
+	"recordingArchive.relocateFootage": [{
 		name: "deviceId",
 		form: "single",
 		optional: true
 	}],
-	"recording.renderClip": [{
+	"recordingArchive.renderClip": [{
 		name: "deviceId",
 		form: "single",
 		optional: false
 	}],
-	"recording.renderGif": [{
+	"recordingArchive.renderGif": [{
 		name: "deviceId",
 		form: "single",
 		optional: false
 	}],
-	"recording.rescanStorage": [{
+	"recordingArchive.rescanStorage": [{
 		name: "deviceId",
 		form: "single",
 		optional: false
 	}],
-	"recording.setDeviceConfig": [{
+	"recordingArchive.setDeviceConfig": [{
 		name: "deviceId",
 		form: "single",
 		optional: false
 	}],
-	"recording.setDevicePlacement": [{
+	"recordingArchive.setDevicePlacement": [{
 		name: "deviceId",
 		form: "single",
 		optional: false
 	}],
-	"recording.startStorageMigrationMove": [{
+	"recordingArchive.startStorageMigrationMove": [{
 		name: "deviceId",
 		form: "single",
 		optional: true
@@ -50722,8 +50959,14 @@ function createClipThumbHandler(deps) {
 * The 204, with everything the tile needs to decide what to draw next.
 *
 * A FINAL refusal is work that was dropped, so it is warned, per camera. A
-* DEFERRED one dropped nothing — the still is queued behind the camera's one
-* replay slot — and warning it would put a line on the log per tile of a page.
+* DEFERRED one dropped nothing — the camera's one playback slot is busy, or an
+* operator's tap evicted this mint mid-replay — and warning it would put a
+* line on the log per tile of a page.
+*
+* There was briefly a third rule here, exempting `media-not-held` from the
+* warn because it was the steady state of every list. That code is gone
+* because its cause is: a clip whose bytes are not held now MINTS, in about
+* half a second off the camera, instead of refusing.
 */
 function writeStillRefusal(res, refusal, deviceId, logger, clipKey) {
 	const line = "videoclips: thumbnail not minted";
@@ -50961,25 +51204,58 @@ var CLIP_STREAM_PCMU_RATE_HZ = 8e3;
 /**
 * How much of an input ffmpeg may READ before it will write a header.
 *
-* ffmpeg probes every input to discover what is in it. Both defaults are
-* enormous for this use — `probesize` 5 MB, `analyzeduration` 5 s — and both
+* ffmpeg probes every input to discover what is in it, and both defaults are
+* enormous for this use — `probesize` 5 MB, `analyzeduration` 5 s — which here
 * are paid in the operator's wait, because a Hikvision replay arrives at 1×
-* (measured 1.01× on 1436, 2026-09-23) so "5 MB of input" is seconds of wall
-* clock, not microseconds of buffer.
-*
-* **Nothing here is being discovered.** The demuxer is named (`-f hevc` /
-* `-f h264`, from the SDP's own `a=rtpmap`), the frame rate is named (`-r`,
-* measured from the replay's RTP clock and refused when it cannot be), and the
-* µ-law input is named down to its sample rate and channel count. A probe can
-* only re-derive what the caller already stated.
-*
-* Measured end to end against the real 1436 clip (18 s, 4K HEVC, 12.5 fps,
-* GOP 50): with the defaults the init segment reached the peer at 3889 ms and
-* the first media fragment at 3891 ms; with these two flags, 171 ms and
-* 2269 ms. 32 KiB is two orders of magnitude over the parameter sets the hevc
-* demuxer needs and still one one-hundred-and-fiftieth of the default.
-*/
-var CLIP_MUX_PROBE_BYTES = 32768;
+* and "5 MB of input" is seconds of wall clock. `-analyzeduration 0` goes with
+* it: the demuxer is named (`-f hevc`/`-f h264`, from the SDP's own
+* `a=rtpmap`), the rate is named (`-r`, measured), and the µ-law input is
+* named down to its sample rate. A probe can only re-derive what was stated.
+*
+* **256 KiB, and the number is a compromise between two measurements.** This
+* shipped at 32 KiB, which is six per cent of ONE access unit — the first unit
+* of a 3840×2160 HEVC replay on 1436 measures **550 354 bytes**, a whole 4K
+* keyframe with its parameter sets — and a bound that cannot hold a single
+* frame is uncomfortable whatever it gets away with. But widening it is not
+* free and it fixes nothing: measured against the pinned jellyfin 8.1.2 build
+* on the real camera, first byte to the peer was **721 ms at 32 KiB, 752 ms at
+* 256 KiB, 1 126 ms at 768 KiB**. 256 KiB buys eight times the headroom for
+* 31 ms.
+*
+* **It is explicitly NOT the cause of the header-and-no-media failure** that
+* cost the fleet an afternoon, and it was the first suspect. Every probe size
+* from 32 KiB to 768 KiB reproduced that fault identically, and removing the
+* flags altogether reproduced it too; the cause was
+* {@link CLIP_STREAM_MAX_INTERLEAVE_DELTA_US}. Written down so the hypothesis
+* is not re-tried.
+*/
+var CLIP_MUX_PROBE_BYTES = 256 * 1024;
+/**
+* How long the muxer may hold one track's packets WAITING for the other.
+*
+* **This is the whole reason a clip with sound would not play.** Measured on
+* 1436, 2026-09-23, through the real producer against the real camera with the
+* pinned build: a SILENT stream delivered 1 299 KiB to the peer by the
+* halfway point of a six-second clip, and the same clip with `opus` or `pcmu`
+* delivered **1 KiB** — the init segment, and nothing else — until the inputs
+* ENDED, at which point all 3.78 MB arrived in one burst. From the operator's
+* own session: 129 access units in, `bytesOut: 1298` out, `pushed: 0` on the
+* broker, and a player that gave up after 10.6 s with nothing to show.
+*
+* ffmpeg buffers packets to interleave two inputs, and with video on stdin and
+* µ-law on `pipe:3` it decided to wait rather than write. It is not a rate
+* mismatch — the two timelines measured 4.80 s of video against 4.80 s of
+* audio, a ratio of 1.000 — it is the muxer's own interleaving window, and for
+* a LIVE fragmented stream any window at all is wrong.
+*
+* **`0` does not mean "no window". It means UNLIMITED**, and it reproduced the
+* fault exactly. The value has to be small and positive. 100 ms is two and a
+* half of this camera's 40 ms µ-law frames — long enough that ordinary jitter
+* does not split a fragment, short enough that no consumer notices.
+*
+* With it, all three audio asks deliver ~1 278 KiB by the same halfway point.
+*/
+var CLIP_STREAM_MAX_INTERLEAVE_DELTA_US = 1e5;
 /**
 * How long a fragment may run before it is CLOSED, keyframe or not.
 *
@@ -51070,6 +51346,8 @@ function buildClipStreamMuxArgs(input) {
 		CLIP_STREAM_MOVFLAGS,
 		"-frag_duration",
 		String(CLIP_STREAM_FRAG_DURATION_US),
+		"-max_interleave_delta",
+		String(CLIP_STREAM_MAX_INTERLEAVE_DELTA_US),
 		"-flush_packets",
 		"1",
 		"-f",
@@ -51131,12 +51409,19 @@ function createDrainGate(deps) {
 	return {
 		wrote(accepted) {
 			if (accepted || handle !== null || stalled) return;
-			handle = setTimeout(() => {
-				handle = null;
-				if (stalled) return;
-				stalled = true;
-				deps.onStall();
-			}, deps.timeoutMs);
+			const arm = () => {
+				handle = setTimeout(() => {
+					handle = null;
+					if (stalled) return;
+					if (deps.stillMoving?.() === true) {
+						arm();
+						return;
+					}
+					stalled = true;
+					deps.onStall();
+				}, deps.timeoutMs);
+			};
+			arm();
 		},
 		drained() {
 			disarm();
@@ -52111,26 +52396,8 @@ async function prepareClipFile(input, deps) {
 			detail: err instanceof Error ? err.message : String(err)
 		};
 	}
-	const abort = () => void session.close();
-	deps.signal?.addEventListener("abort", abort, { once: true });
 	const end = await session.ended;
-	deps.signal?.removeEventListener("abort", abort);
 	await session.close();
-	if (deps.signal?.aborted === true) {
-		deps.logger.debug("videoclips: a clip fetch gave the slot back", {
-			tags,
-			meta: {
-				...meta,
-				branch: "preempted",
-				accessUnits: units.length
-			}
-		});
-		return {
-			kind: "refused",
-			code: "fetch-failed",
-			detail: "preempted: the camera’s one replay slot was wanted by a stream"
-		};
-	}
 	if (end.kind === "failed") return {
 		kind: "refused",
 		code: "camera-refused",
@@ -52245,19 +52512,7 @@ async function prepareClipFile(input, deps) {
 * than that is a holder that is still playing.
 */
 var REPLAY_LANE_WAIT_MS = RTSP_TEARDOWN_FLUSH_MS + 1e3;
-/**
-* Which purposes are SPECULATIVE — work nobody is waiting on.
-*
-* A still is minted for a tile that is not on screen yet. A stream and a file
-* are an operator who has already tapped. When the two want the same camera,
-* the operator wins: the speculative holder is asked to give the slot back
-* (`yield`) and the ask waits for it, instead of being refused for want of
-* work that could have been done a minute later.
-*
-* Without this, opening a list of clips would start a realtime fetch per tile
-* and every playback tap during it would meet `replay-busy` — which is a
-* regression traded for a thumbnail, and not a trade anyone asked for.
-*/
+/** Work nobody is waiting on, which an operator's tap may evict. */
 var SPECULATIVE = new Set(["still"]);
 function createReplayLane(deps) {
 	const now = deps.now ?? (() => Date.now());
@@ -52369,14 +52624,65 @@ function buildClipStillArgs(input) {
 	];
 }
 /**
+* What ffmpeg is told to cut a still out of RAW ACCESS UNITS.
+*
+* The other half of the same job. A clip whose bytes are not on this disk is
+* never FETCHED — that costs the camera its playback session for the clip's
+* whole duration — so its FIRST frame is taken off the camera in about half a
+* second (`clip-first-frame.ts`) and decoded here, from an elementary stream
+* on stdin rather than from a file.
+*
+* No `-ss`: the units ARE the head, and there is no seek inside a Hikvision
+* replay to reach anything else. No `-r`: one frame carries no rate, which is
+* the single case `clip-replay-rate.ts`'s rule does not reach.
+*/
+function buildFirstFrameStillArgs(codec) {
+	return [
+		"-hide_banner",
+		"-loglevel",
+		"error",
+		"-nostdin",
+		"-analyzeduration",
+		"0",
+		"-probesize",
+		String(CLIP_MUX_PROBE_BYTES),
+		"-f",
+		codec === "h265" ? "hevc" : "h264",
+		"-i",
+		"pipe:0",
+		"-frames:v",
+		"1",
+		"-vf",
+		`scale=${String(640)}:-2:flags=bicubic`,
+		"-q:v",
+		String(4),
+		"-f",
+		"mjpeg",
+		"pipe:1"
+	];
+}
+/** The first frame the camera handed over, as a JPEG. Never throws. */
+async function cutStillFromAccessUnits(units, codec, deps) {
+	return await runStillFfmpeg(buildFirstFrameStillArgs(codec), Buffer.concat(units.map((unit) => Buffer.from(unit.bytes))), deps, "the camera’s first access units");
+}
+/**
 * Cut one still. Never throws: every dead end is a named refusal.
 */
 async function cutClipStill(input, deps) {
-	const args = buildClipStillArgs(input);
+	return await runStillFfmpeg(buildClipStillArgs(input), null, deps, `${clipStillSeekSeconds(input.durationMs).toFixed(3)} s into the held file`);
+}
+/**
+* One bounded ffmpeg that answers with a JPEG or a named refusal.
+*
+* `stdin` carries the elementary stream when the source is the camera, and is
+* `null` when the source is a path. Shared, so the two cannot drift apart on
+* the timeout, the kill, or what an empty answer means.
+*/
+async function runStillFfmpeg(args, stdin, deps, where) {
 	let child;
 	try {
 		child = deps.spawnStill?.([...args]) ?? (0, node_child_process.spawn)(deps.ffmpegBinaryPath ?? "ffmpeg", [...args], { stdio: [
-			"ignore",
+			stdin === null ? "ignore" : "pipe",
 			"pipe",
 			"pipe"
 		] });
@@ -52393,6 +52699,10 @@ async function cutClipStill(input, deps) {
 	child.stderr?.on("data", (chunk) => {
 		stderr += chunk.toString("utf8");
 	});
+	if (stdin !== null) {
+		child.stdin?.on("error", () => {});
+		child.stdin?.end(stdin);
+	}
 	const timeoutMs = deps.timeoutMs ?? 1e4;
 	const exit = await new Promise((resolve) => {
 		const timer = setTimeout(() => resolve("timeout"), timeoutMs);
@@ -52415,19 +52725,100 @@ async function cutClipStill(input, deps) {
 		};
 	}
 	const bytes = Buffer.concat(chunks);
+	if (bytes.byteLength > 0) return {
+		kind: "ok",
+		bytes
+	};
 	if (exit !== 0) return {
 		kind: "refused",
 		code: "decode-failed",
 		detail: `ffmpeg exited ${String(exit)}: ${stderr.trim().slice(0, 300)}`
 	};
-	if (bytes.byteLength === 0) return {
+	return {
 		kind: "refused",
 		code: "no-keyframe",
-		detail: `ffmpeg read the clip and produced no frame at ${clipStillSeekSeconds(input.durationMs).toFixed(3)} s`
+		detail: `ffmpeg read ${where} and produced no frame`
+	};
+}
+/** Never throws: every dead end is a named refusal. */
+async function fetchFirstFrame(input, deps) {
+	const openReplay = deps.openReplay ?? openRtspReplay;
+	const want = deps.accessUnits ?? 2;
+	const timeoutMs = deps.timeoutMs ?? 5e3;
+	const startedAt = Date.now();
+	if (deps.signal?.aborted === true) return {
+		kind: "refused",
+		code: "yielded",
+		detail: "the slot was wanted before the open"
 	};
+	const units = [];
+	let enough = null;
+	const gotEnough = new Promise((resolve) => {
+		enough = resolve;
+	});
+	let session;
+	try {
+		session = await openReplay({
+			host: input.camera.host,
+			username: input.camera.username,
+			password: input.camera.password,
+			playbackPath: input.row.playbackPath
+		}, { onVideo: (unit) => {
+			if (units.length >= want) return;
+			units.push(unit);
+			if (units.length >= want) enough?.();
+		} }, {
+			logger: deps.logger,
+			deviceId: input.camera.deviceId
+		});
+	} catch (err) {
+		return {
+			kind: "refused",
+			code: "camera-refused",
+			detail: err instanceof Error ? err.message : String(err)
+		};
+	}
+	let yielded = false;
+	const onAbort = () => {
+		yielded = true;
+		enough?.();
+	};
+	deps.signal?.addEventListener("abort", onAbort, { once: true });
+	let timer = setTimeout(() => {
+		timer = null;
+		enough?.();
+	}, timeoutMs);
+	session.ended.then(() => enough?.());
+	await gotEnough;
+	if (timer !== null) clearTimeout(timer);
+	deps.signal?.removeEventListener("abort", onAbort);
+	await session.close();
+	const slotMs = Date.now() - startedAt;
+	if (yielded) return {
+		kind: "refused",
+		code: "yielded",
+		detail: `a playback wanted the slot after ${String(slotMs)} ms`
+	};
+	if (units.length === 0) return {
+		kind: "refused",
+		code: "camera-refused",
+		detail: `the replay delivered no access unit inside ${String(timeoutMs)} ms`
+	};
+	deps.logger.debug("videoclips: took a clip’s first frame off the camera", {
+		tags: { deviceId: input.camera.deviceId },
+		meta: {
+			clipKey: input.row.clipKey,
+			units: units.length,
+			bytes: units.reduce((sum, unit) => sum + unit.bytes.byteLength, 0),
+			codec: session.video.codec,
+			slotMs
+		}
+	});
 	return {
 		kind: "ok",
-		bytes
+		units,
+		codec: session.video.codec,
+		slotMs
 	};
 }
 function pathToken(req) {
@@ -52652,6 +53043,9 @@ var ClipStreamRun = class {
 	slotFreed = Promise.resolve();
 	settle = null;
 	bytesOut = 0;
+	/** {@link bytesOut} the last time the audio gate's window elapsed. */
+	bytesOutAtAudioWindow = 0;
+	audioNotHungryLogged = false;
 	accessUnits = 0;
 	audioFramesAfterMux = 0;
 	audioFramesDropped = 0;
@@ -52660,6 +53054,9 @@ var ClipStreamRun = class {
 	*  row's, which is a projection (D393). */
 	deliveredMs = null;
 	begun = false;
+	/** ffmpeg's own words, bounded. Kept so EVERY exit can carry them, not just
+	*  the one that happened to be holding the closure. */
+	stderr = "";
 	startedAt = Date.now();
 	constructor(request, deps) {
 		this.request = request;
@@ -52787,7 +53184,8 @@ var ClipStreamRun = class {
 		});
 		if (this.muxedAudio !== null) this.audioGate = createDrainGate({
 			timeoutMs: this.deps.drainTimeoutMs,
-			onStall: () => this.sever("mux-audio-stalled", "ffmpeg stopped taking audio frames")
+			onStall: () => this.sever("mux-audio-stalled", "ffmpeg stopped taking audio frames"),
+			stillMoving: () => this.muxProducedSinceLastAudioWindow()
 		});
 		this.peerGate = createDrainGate({
 			timeoutMs: this.deps.drainTimeoutMs,
@@ -52802,24 +53200,65 @@ var ClipStreamRun = class {
 			audioPipe.on("drain", () => this.audioGate?.drained());
 		}
 		child.stdout?.on("data", (chunk) => this.onMuxOutput(chunk));
-		let stderr = "";
 		child.stderr?.on("data", (chunk) => {
-			stderr = `${stderr}${chunk.toString()}`.slice(-2e3);
+			this.stderr = `${this.stderr}${chunk.toString()}`.slice(-2e3);
 		});
-		child.on("close", (code) => this.onMuxClosed(code, stderr));
-		this.request.sink.onceDrain(() => this.peerGate?.drained());
+		child.on("close", (code) => this.onMuxClosed(code, this.stderr));
 		for (const unit of this.heldVideo) this.writeVideo(unit);
 		this.heldVideo = [];
 		if (this.muxedAudio !== null) for (const payload of this.heldAudio) this.writeAudio(payload);
 		else this.audioFramesDropped += this.heldAudio.length;
 		this.heldAudio = [];
 	}
+	/**
+	* Has this mux taken frames and produced no MEDIA?
+	*
+	* Checked as units go in, because that is the only place that knows the mux
+	* is being fed. A header and nothing else is not a slow stream, it is a
+	* broken one, and the peer will otherwise sit on it until it gives up with
+	* nothing to show the operator but a blank player.
+	*/
+	checkMuxProducedMedia() {
+		if (this.answered || this.mux === null) return;
+		if (this.accessUnits < 64) return;
+		if (this.bytesOut > 65536) return;
+		this.sever("mux-no-media", `ffmpeg took ${String(this.accessUnits)} access units and produced ${String(this.bytesOut)} bytes — a header and no media` + (this.stderr.trim() === "" ? " (ffmpeg said nothing)" : `: ${this.stderr.trim().slice(-300)}`));
+	}
 	writeVideo(unit) {
 		const stdin = this.mux?.stdin;
 		if (stdin === null || stdin === void 0 || stdin.destroyed) return;
 		this.accessUnits += 1;
+		this.checkMuxProducedMedia();
+		if (this.answered) return;
 		this.videoGate?.wrote(stdin.write(unit.bytes));
 	}
+	/**
+	* Did the mux hand the peer anything during the window the audio gate just
+	* waited out?
+	*
+	* The gate's question is "has this hop stopped for good", and on fd 3 the
+	* answer cannot be read from the pipe alone: 64 KiB of µ-law is eight
+	* seconds of sound, so a muxer that is merely AHEAD on audio looks exactly
+	* like one that has died. ffmpeg's own output settles it — bytes on stdout
+	* are proof it is running — and each window is judged on its own, so a
+	* mux that really stops is still cut one window later.
+	*/
+	muxProducedSinceLastAudioWindow() {
+		const moved = this.bytesOut > this.bytesOutAtAudioWindow;
+		this.bytesOutAtAudioWindow = this.bytesOut;
+		if (moved && !this.audioNotHungryLogged) {
+			this.audioNotHungryLogged = true;
+			this.deps.logger.info("videoclips: the mux is not taking audio but is still producing", {
+				tags: this.tags,
+				meta: {
+					...this.meta,
+					bytesOut: this.bytesOut,
+					accessUnits: this.accessUnits
+				}
+			});
+		}
+		return moved;
+	}
 	writeAudio(payload) {
 		const pipe = writableStdio(this.mux?.stdio[3]);
 		if (pipe === null) return;
@@ -52833,7 +53272,14 @@ var ClipStreamRun = class {
 			this.request.sink.begin(clipStreamContentTypeFor(this.muxedAudio));
 		}
 		this.bytesOut += chunk.byteLength;
-		this.peerGate?.wrote(this.request.sink.write(chunk));
+		const accepted = this.request.sink.write(chunk);
+		this.peerGate?.wrote(accepted);
+		if (accepted) return;
+		this.mux?.stdout?.pause();
+		this.request.sink.onceDrain(() => {
+			this.peerGate?.drained();
+			this.mux?.stdout?.resume();
+		});
 	}
 	finishInputs(deliveredMs) {
 		if (this.answered) return;
@@ -52915,6 +53361,7 @@ var ClipStreamRun = class {
 				...this.meta,
 				branch,
 				reason: detail,
+				muxStderr: this.stderr.trim().slice(-500),
 				accessUnits: this.accessUnits,
 				bytesOut: this.bytesOut,
 				elapsedMs: Date.now() - this.startedAt
@@ -53821,7 +54268,7 @@ function createClipService(deps) {
 		maxFilesPerDevice: THUMB_MAX_FILES_PER_DEVICE,
 		maxBytesPerDevice: THUMB_MAX_BYTES_PER_DEVICE
 	});
-	const lane = createReplayLane({
+	const lane = deps.lane ?? createReplayLane({
 		logger,
 		...deps.replayWaitMs !== void 0 ? { waitMs: deps.replayWaitMs } : {}
 	});
@@ -53946,30 +54393,32 @@ function createClipService(deps) {
 			detail: "no-catalog-row: list the window that holds this clip first"
 		};
 		if (await store.pathIfPresent(deviceId, clipKey) === null) {
-			const preempt = new AbortController();
-			const lease = await lane.acquire(deviceId, purpose, () => preempt.abort());
+			const lease = await lane.acquire(deviceId, purpose);
 			if (lease.kind === "busy") return {
 				kind: "refused",
 				code: "replay-busy",
 				detail: lease.detail
 			};
+			let fetched;
 			try {
-				return await prepareClipFile({
+				fetched = await prepareClipFile({
 					camera: cameraFor(camera),
 					row,
 					audio: true
 				}, {
 					logger,
 					store,
-					signal: preempt.signal,
 					...deps.ffmpegBinaryPath !== void 0 ? { ffmpegBinaryPath: deps.ffmpegBinaryPath } : {},
-					...deps.openReplay !== void 0 ? { openReplay: deps.openReplay } : {}
+					...deps.openReplay !== void 0 ? { openReplay: deps.openReplay } : {},
+					...deps.spawnMux !== void 0 ? { spawnMux: deps.spawnMux } : {}
 				});
 			} finally {
 				lease.release();
 			}
+			if (fetched.kind === "ok") await mintPassing(deviceId, clipKey, fetched);
+			return fetched;
 		}
-		return await prepareClipFile({
+		const cached = await prepareClipFile({
 			camera: cameraFor(camera),
 			row,
 			audio: true
@@ -53977,8 +54426,46 @@ function createClipService(deps) {
 			logger,
 			store,
 			...deps.ffmpegBinaryPath !== void 0 ? { ffmpegBinaryPath: deps.ffmpegBinaryPath } : {},
-			...deps.openReplay !== void 0 ? { openReplay: deps.openReplay } : {}
+			...deps.openReplay !== void 0 ? { openReplay: deps.openReplay } : {},
+			...deps.spawnMux !== void 0 ? { spawnMux: deps.spawnMux } : {}
 		});
+		if (cached.kind === "ok") await mintPassing(deviceId, clipKey, cached);
+		return cached;
+	};
+	/**
+	* Mint the still of a clip whose bytes have just been put on this disk.
+	*
+	* Cheap and idempotent: a `stat` says whether one is already held, and the
+	* cut itself is one frame of a local file. It is AWAITED rather than fired
+	* and forgotten, because an unhandled rejection in a detached promise is
+	* exactly the silence D391 forbids — and because a caller that just waited
+	* 30 s for a fetch is not harmed by 1.8 s of decode.
+	*
+	* A failure here NEVER fails the fetch. The caller asked for a clip, not a
+	* picture, and a still that could not be cut is named and left absent.
+	*/
+	const mintPassing = async (deviceId, clipKey, file) => {
+		if (await thumbs.has(deviceId, clipKey)) return;
+		try {
+			const minted = await cutHeldStill(deviceId, clipKey, file.path, file.durationMs);
+			if (minted.ok) return;
+			logger.debug("videoclips: no still was cut from a clip that was just fetched", {
+				tags: { deviceId },
+				meta: {
+					clipKey,
+					branch: minted.code,
+					reason: minted.reason
+				}
+			});
+		} catch (err) {
+			logger.warn("videoclips: the passing still mint threw", {
+				tags: { deviceId },
+				meta: {
+					clipKey,
+					error: err instanceof Error ? err.message : String(err)
+				}
+			});
+		}
 	};
 	/**
 	* `fileFor`'s vocabulary, in the one a clip EXPORT answers on.
@@ -54005,19 +54492,84 @@ function createClipService(deps) {
 	* about which clip a key means. Its whole job is to turn `fileFor`'s answer
 	* into the still vocabulary, and to cut one frame when there is a file.
 	*/
+	/**
+	* One clip's STILL, at the cheapest source that can give one.
+	*
+	* **Held bytes first, and they are free.** A clip the operator has played or
+	* exported is already on this disk: one frame of local decode, no network.
+	*
+	* **Otherwise the camera's FIRST frame, for ~0.5 s of its playback slot.**
+	* The clip is never FETCHED for a still — that was shipped once and cost
+	* 898 s of camera time to fill one 20-row screen. A first-frame mint holds
+	* the slot for 433–528 ms whatever the clip's length, and it is speculative:
+	* the lane evicts it the moment an operator taps anything (`yielded`), and
+	* an eviction or a busy slot is DEFERRED, because half a second that lost a
+	* race is worth coming back for where twenty seconds was not.
+	*
+	* The midpoint the operator asked for is not reachable: a narrowed
+	* `ContentMgmt/search` window is accepted with 200 and silently served from
+	* the segment head (`clip-first-frame.ts` has the measurement).
+	*/
 	const mintStill = async (deviceId, clipKey) => {
-		const file = await fileFor(deviceId, clipKey, "still");
-		if (file.kind === "refused") {
-			if (file.code === "replay-busy") return deferStill("queue-full", file.detail, REPLAY_LANE_WAIT_MS);
-			if (file.code === "unknown-device") return refuseStill("unknown-device", file.detail);
-			if (file.code === "no-catalog-row") return refuseStill("no-catalog-row", file.detail);
-			return refuseStill("camera-refused", file.detail);
+		const camera = await deps.resolveCamera(deviceId);
+		if (camera === null) return refuseStill("unknown-device", `device ${String(deviceId)} is not a Hikvision camera`);
+		const row = rowsByKey.get(rowKey(deviceId, clipKey));
+		if (row === void 0) return refuseStill("no-catalog-row", "no-catalog-row: list the window that holds this clip first");
+		const held = await store.pathIfPresent(deviceId, clipKey);
+		if (held !== null) return await cutHeldStill(deviceId, clipKey, held, null);
+		const evict = new AbortController();
+		const lease = await lane.acquire(deviceId, "still", () => evict.abort());
+		if (lease.kind === "busy") return deferStill("queue-full", lease.detail, REPLAY_LANE_WAIT_MS);
+		let frame;
+		try {
+			frame = await fetchFirstFrame({
+				camera: cameraFor(camera),
+				row
+			}, {
+				logger,
+				signal: evict.signal,
+				...deps.openReplay !== void 0 ? { openReplay: deps.openReplay } : {}
+			});
+		} finally {
+			lease.release();
+		}
+		if (frame.kind === "refused") {
+			if (frame.code === "yielded") return deferStill("queue-full", frame.detail, REPLAY_LANE_WAIT_MS);
+			return refuseStill("camera-refused", frame.detail);
 		}
+		const cut = await cutStillFromAccessUnits(frame.units, frame.codec, {
+			logger,
+			...deps.ffmpegBinaryPath !== void 0 ? { ffmpegBinaryPath: deps.ffmpegBinaryPath } : {},
+			...deps.spawnStill !== void 0 ? { spawnStill: deps.spawnStill } : {}
+		});
+		if (cut.kind === "refused") return refuseStill(cut.code, cut.detail);
+		await thumbs.put(deviceId, clipKey, cut.bytes);
+		logger.debug("videoclips: a clip still was minted from the camera’s first frame", {
+			tags: { deviceId },
+			meta: {
+				clipKey,
+				bytes: cut.bytes.byteLength,
+				slotMs: frame.slotMs
+			}
+		});
+		return {
+			ok: true,
+			bytes: cut.bytes
+		};
+	};
+	/**
+	* The cut itself, over bytes already on this disk. Touches no camera.
+	*
+	* `measuredMs` is the span the fetch really delivered when one has just run;
+	* `null` falls back to the catalog row, which is the number the operator was
+	* already shown. Zero is refused rather than seeked to (D393/D382).
+	*/
+	const cutHeldStill = async (deviceId, clipKey, path, measuredMs) => {
 		const row = rowsByKey.get(rowKey(deviceId, clipKey));
-		const durationMs = file.durationMs ?? (row === void 0 ? 0 : row.endMs - row.startMs);
+		const durationMs = measuredMs ?? (row === void 0 ? 0 : row.endMs - row.startMs);
 		if (durationMs <= 0) return refuseStill("no-keyframe", "this clip has no length to take a midpoint of — nothing measured it and its catalog row spans nothing");
 		const cut = await cutClipStill({
-			path: file.path,
+			path,
 			durationMs
 		}, {
 			logger,
@@ -54032,7 +54584,7 @@ function createClipService(deps) {
 				clipKey,
 				bytes: cut.bytes.byteLength,
 				durationMs,
-				measured: file.durationMs !== null
+				measured: measuredMs !== null
 			}
 		});
 		return {