@camstack/system 1.2.201 → 1.2.203

package/dist/{dist-CcV3k-hD.js → dist-BFvWv_bz.js}

@@ -1,5 +1,5 @@
 let zod = require("zod");
-//#region ../types/dist/event-category-zAv7pMUz.mjs
+//#region ../types/dist/event-category-CnLqLOKs.mjs
 var EventCategory = /* @__PURE__ */ function(EventCategory) {
 	EventCategory["SystemBoot"] = "system.boot";
 	EventCategory["SystemAddonsReady"] = "system.addons-ready";
@@ -194,6 +194,19 @@ var EventCategory = /* @__PURE__ */ function(EventCategory) {
 	EventCategory["ProcessCrashed"] = "process.crashed";
 	EventCategory["ProcessRestartScheduled"] = "process.restart_scheduled";
 	EventCategory["ProcessRestarted"] = "process.restarted";
+	/**
+	* The SET of storage locations changed — one was created, edited, enabled,
+	* disabled or deleted through `storage.upsertLocation` / `deleteLocation`.
+	*
+	* Telemetry, not a transaction (D8/D11): every consumer that re-resolves on
+	* it must also converge on its own periodic path, because a dropped event
+	* must not leave a node writing to yesterday's disk set forever. It exists
+	* because there was NO signal at all — an operator who added a second
+	* recordings disk in the admin UI got nothing, and the recorder kept its
+	* resolved locations until something else happened to re-resolve them
+	* (D387). Payload `StorageLocationsChangedPayload`.
+	*/
+	EventCategory["StorageLocationsChanged"] = "storage.locations-changed";
 	EventCategory["RecordingStarted"] = "recording.started";
 	EventCategory["RecordingStopped"] = "recording.stopped";
 	EventCategory["RecordingError"] = "recording.error";
@@ -3815,111 +3828,6 @@ function logLevelAtMost(level, threshold) {
 	return LOG_LEVEL_RANK[level] <= LOG_LEVEL_RANK[threshold];
 }
 /**
-* Per-component log CHANNELS — the gate a hot path consults, and the registry
-* an addon declares its channels in.
-*
-* ## Two axes, deliberately separated
-*
-* - **DECLARATION** — which channels exist. Only the addon knows:
-*   `stream-broker` knows webrtc/ICE/RTP, `provider-reolink` knows
-*   baichuan/handshake. A hand-wired central list rots at the first addition,
-*   and rots silently. So a channel is declared where it is consulted, and the
-*   `log-channels` capability enumerates the declarations.
-* - **VALUE** — at which level, for which scope, until when. That stays ONE
-*   thing: the logging settings document on the `system` cap. Two authorities
-*   over the values is the exact defect
-*   `docs/design/plans/2026-08-26-logging-per-componente.md` was written to
-*   remove; re-introducing it from the cure side would be grotesque.
-*
-* Nothing in this file reads a clock, an env var or a store. The registry is
-* a MIRROR: it is moved only by {@link LogChannelRegistry.apply}, called off
-* the hot path with a value somebody actually read, and by
-* {@link LogChannelRegistry.tick}, called on a timer. A store read that fails
-* never reaches here, so it can neither disarm an armed channel nor arm a
-* disarmed one (D49).
-*
-* ## The canonical call shape
-*
-* ```ts
-* if (CH_RTP.on && CH_RTP.wants(deviceId)) {
-*   CH_RTP.log(logger, 'rtp subscriber added', { tags: { deviceId }, meta: { ssrc } })
-* }
-* ```
-*
-* `on` is a plain boolean FIELD — never a getter — and it is the FIRST thing
-* read. Disarmed, a call site costs one load and one branch, and the `extras`
-* object literal is never constructed because it lives inside the branch. It
-* is the same shape already proven in production at `stream-broker.ts:1650`,
-* and the same discipline `LoggingGate.allowsDestination` uses for the
-* destination floor (measured at 1.93 ns/call when off).
-*
-* ## Why a channel emits at `info`
-*
-* `loki-logging.addon.ts` pins the destination default at `info` and
-* `loki-destination.ts` drops everything below it, so a line emitted at
-* `debug` never reaches Loki and the hub's in-memory ring only holds ~35
-* minutes. A diagnostic that cannot be read an hour later is worse than no
-* diagnostic, because it looks done. {@link LogChannelGate.log} therefore
-* emits at the channel's declared level, whose schema floor is `info`.
-*/
-/**
-* The level a channel writes at once armed.
-*
-* `debug` is absent ON PURPOSE and not by omission: below `info` the line does
-* not leave the process for Loki, and the whole point of arming a channel is
-* to read it later.
-*/
-var LogChannelLevelSchema = zod.z.enum([
-	"info",
-	"warn",
-	"error"
-]);
-/**
-* What an addon declares about one channel. No value, no state — a
-* declaration is inert.
-*/
-var LogChannelDescriptorSchema = zod.z.object({
-	/**
-	* Dotted `area.thing`, unique across the workspace. `area` is conventionally
-	* the addon's short name so an operator reading a channel list can tell who
-	* owns it without a second lookup.
-	*/
-	name: zod.z.string().min(3).regex(/^[a-z0-9-]+(\.[a-z0-9-]+)+$/, "a channel name is dotted lower-kebab, e.g. area.thing"),
-	/** One sentence: what the operator will SEE after arming it. */
-	description: zod.z.string().min(1),
-	/** The level its lines are emitted at. Never below `info`. */
-	defaultLevel: LogChannelLevelSchema,
-	/**
-	* Whether this channel can be narrowed to a camera.
-	*
-	* `true` is a PROMISE with two halves, and both must hold: the gate is
-	* consulted with the numeric device id, AND every line the channel admits
-	* carries `tags: { deviceId }` with that same numeric id. The second half is
-	* what makes `| json | deviceId="617"` work in Loki — `loki-payload.ts`
-	* keeps `deviceId` out of the stream labels for cardinality, so the tag in
-	* the body is the only way to filter.
-	*
-	* A channel whose lines carry the device only in `meta` (or not at all) is
-	* declared `false`. Declaring it `true` anyway would be a lie the UI repeats:
-	* the operator narrows to one camera, sees nothing, and concludes the code
-	* path was never taken.
-	*/
-	perDevice: zod.z.boolean()
-});
-/**
-* An armed window over one channel, as the document hands it to a mirror.
-*
-* A window is a DEADLINE, never a flag (ADR-0244): a channel somebody forgot
-* expires by itself, which is the one failure a boolean cannot avoid.
-*/
-var LogChannelWindowSchema = zod.z.object({
-	channel: zod.z.string().min(1),
-	/** Epoch ms the window closes at. */
-	armedUntilMs: zod.z.number(),
-	/** `null` = every camera. A non-empty list narrows to those numeric ids. */
-	deviceIds: zod.z.array(zod.z.number().int()).readonly().nullable()
-});
-/**
 * Ops-log — the durable, append-only operations audit shared by the
 * recordings and events management surfaces.
 *
@@ -4873,6 +4781,144 @@ var StorageCleanupJobSchema = zod.z.object({
 });
 var StorageCleanupStatusInputSchema = zod.z.object({ jobId: zod.z.string().optional() });
 /**
+* The storage-location STATE MODEL (D385) — one typed state, one policy module.
+*
+* A location's state used to be split across two authorities: the typed
+* `enabled` field (THE write switch since D383) and an untyped `config.readOnly`
+* key. They did not mean the same thing — `enabled: false` was still evicted
+* under disk pressure while `config.readOnly` was deliberately excluded — and
+* neither name said which. Every consumer re-derived the difference, and the
+* three questions that actually matter were answered in six places.
+*
+* This module is the ONLY place in the repo allowed to interpret the state. It
+* answers three questions and nothing else:
+*
+*   - may this location be WRITTEN to?   {@link modeMayWrite}
+*   - may this location be READ?          {@link modeMayRead}
+*   - what is its eviction policy?        {@link evictionPolicyForMode}
+*
+* | mode       | write | read | eviction                       |
+* | ---------- | ----- | ---- | ------------------------------ |
+* | `active`   | yes   | yes  | `normal` (pressure + usage cap) |
+* | `readonly` | no    | yes  | `never`                        |
+* | `drain`    | no    | yes  | `drain` (paced, until empty)   |
+* | `disabled` | no    | no   | `never`                        |
+*
+* `scripts/check-storage-location-mode-single-owner.ts` fails the build when
+* anything outside this module reads `config['readOnly']` or compares `enabled`
+* directly. A rule nothing checks has already been broken somewhere.
+*/
+var STORAGE_LOCATION_MODES = [
+	"active",
+	"readonly",
+	"drain",
+	"disabled"
+];
+/**
+* The one typed state of a storage location. Authoritative Zod schema — the TS
+* alias below is `z.infer<>` of it, never a second spelling.
+*/
+var StorageLocationModeSchema = zod.z.enum(STORAGE_LOCATION_MODES);
+zod.z.enum([
+	"normal",
+	"never",
+	"drain"
+]);
+/**
+* The legacy untyped drain key. Named ONCE, here, so the guard has exactly one
+* sanctioned reader and the string never appears anywhere else.
+*/
+var LEGACY_READ_ONLY_CONFIG_KEY = "readOnly";
+/** Is this mode a write target? Only `active` is. */
+function modeMayWrite(mode) {
+	return mode === "active";
+}
+/** May this mode be read (playback, timeline, scrub, relocate source)? */
+function modeMayRead(mode) {
+	return mode !== "disabled";
+}
+/** What eviction may do here. See {@link StorageEvictionPolicy}. */
+function evictionPolicyForMode(mode) {
+	switch (mode) {
+		case "active": return "normal";
+		case "drain": return "drain";
+		case "readonly":
+		case "disabled": return "never";
+	}
+}
+/**
+* The mode a LEGACY row implies, or `null` when it implies nothing — the row is
+* already stamped, or it carried neither flag.
+*
+* Both legacy flags fold to `readonly`, which is the CONSERVATIVE direction: a
+* state change must never start deleting footage on its own, and it must never
+* make footage that was still being served disappear. `enabled: false` used to
+* leave the location evictable under pressure; folding it to `readonly` stops
+* that, which is a strictly safer answer than the one it replaces.
+*/
+function legacyModeOf(location) {
+	if (location.mode !== void 0) return null;
+	if (location.config["readOnly"] === true) return "readonly";
+	if (location.enabled === false) return "readonly";
+	return null;
+}
+/**
+* The state of a location, stamped or folded. THE one interpretation: a row
+* that predates D385 is never ambiguous, and a stamped `mode` always wins over
+* whatever the legacy pair still says.
+*/
+function resolveLocationMode(location) {
+	return (isStorageLocationMode(location.mode) ? location.mode : void 0) ?? legacyModeOf(location) ?? "active";
+}
+/** Is this one of the four states? The stamped value crosses a wire, and a
+*  value nobody defined must not be rendered as if it were a state. */
+function isStorageLocationMode(value) {
+	return STORAGE_LOCATION_MODES.some((mode) => mode === value);
+}
+/** May this location be written to? */
+function mayWriteToLocation(location) {
+	return modeMayWrite(resolveLocationMode(location));
+}
+/** May this location be read? A `disabled` one may not — and that is an
+*  operator CHOICE, which callers must report as unavailable rather than as an
+*  unknown-location fault. */
+function mayReadLocation(location) {
+	return modeMayRead(resolveLocationMode(location));
+}
+/** What eviction may do to this location. */
+function evictionPolicyOfLocation(location) {
+	return evictionPolicyForMode(resolveLocationMode(location));
+}
+/**
+* The config blob with the retired drain key removed. Returns the SAME object
+* when there was nothing to strip, so a caller can tell "changed" from
+* "unchanged" by identity and skip a pointless persist.
+*/
+function strippedOfLegacyReadOnly(config) {
+	if (!("readOnly" in config)) return config;
+	const next = { ...config };
+	delete next[LEGACY_READ_ONLY_CONFIG_KEY];
+	return next;
+}
+/**
+* Set a location's mode, and with it everything that must agree with it.
+*
+* `enabled` stays readable for one release as a DERIVED value (`mode ===
+* 'active'`) so consumers that have not moved yet keep working, and the legacy
+* `config.readOnly` key is DELETED. This function is the only way to write
+* either, which is what makes it impossible for the two to disagree.
+*
+* Returns a new object — the input is never mutated.
+*/
+function withLocationMode(location, mode) {
+	return {
+		...location,
+		mode,
+		enabled: modeMayWrite(mode),
+		config: strippedOfLegacyReadOnly(location.config)
+	};
+}
+/**
 * `StorageLocationType` — an addon-declared id that identifies the *kind* of
 * storage a location serves. Defined here (not in `capabilities/storage.cap.ts`)
 * so the persisted record schema and the consumer-facing cap can both consume it
@@ -4897,8 +4943,11 @@ var StorageLocationTypeSchema = zod.z.string().regex(/^[a-z][a-zA-Z0-9-]*$/);
 * `STORAGE_LOCATION_CARDINALITY` map has been removed.
 *
 * `id` is a stable namespaced string of the form `<type>:<slug>`.
-* The default location for a type uses `id === <type>:default` by
-* convention (the bare type ref like `'backups'` resolves to it).
+* The seed names its first instance `<type>:default` — a NAME, not a flag.
+* There is no default location any more (D383): `enabled` is the whole write
+* model, and a bare type ref resolves to the sole location of the type, or —
+* transitionally, only while legacy NULL-stamped rows exist — to the row whose
+* slug is `default`.
 *
 * `isSystem` is a legacy persisted flag. Seed still creates the initial
 * `<type>:default` locations; the flag is no longer a lock, a badge, or a
@@ -4919,23 +4968,37 @@ var StorageLocationSchema = zod.z.object({
 	* flag at upsert time, not here (the schema is provider-agnostic).
 	*/
 	nodeId: zod.z.string().optional(),
-	isDefault: zod.z.boolean().default(false),
 	isSystem: zod.z.boolean().default(false),
 	/**
-	* Operator opt-in: whether consumers that BALANCE across several locations
-	* of a type may write here. Recordings reads it today; event media and
-	* backups are the next consumers, which is why the flag lives on the
-	* location rather than in any one addon's store — nothing has to be
-	* extended to add the next consumer.
+	* THE write switch, and the only one (D383). `enabled: true` means every
+	* consumer that chooses a write target for this type may write here, and all
+	* enabled locations of a type are used TOGETHER; `false` means read-only —
+	* still read, still played back, still age-swept, still drained, never
+	* written.
 	*
-	* OPTIONAL, and ABSENT MEANS ACTIVE. Every location persisted before the
-	* flag existed reads back with no flag and keeps working exactly as before;
-	* that is the whole compat story, and it is why no migration ships with it.
-	* A newly CREATED sibling is stamped `false` by the orchestrator (creating a
-	* disk must not silently start writing to it); the default of a type is
-	* always stamped `true`.
+	* OPTIONAL only for the wire: an upsert that omits it means "leave what is
+	* stored" on an update and "born inert unless it is the first location of its
+	* type" on a create. On a PERSISTED row absence is legacy and it means
+	* enabled — {@link isLocationEnabled} is the one place that says so, and the
+	* orchestrator stamps every flagless row `true` once at hydrate so absence
+	* stops existing rather than being re-derived on every read.
 	*/
 	enabled: zod.z.boolean().optional(),
+	/**
+	* THE state of this location (D385), and the only authority on what may be
+	* written, read or evicted here. Interpreted in exactly one place —
+	* `storage-location-mode.ts` — which also folds the legacy
+	* `enabled` / `config.readOnly` pair into a mode so an old row is never
+	* ambiguous.
+	*
+	* OPTIONAL only for the wire and for rows written before D385: absence is
+	* resolved by `resolveLocationMode`, and the orchestrator stamps every
+	* unstamped row ONCE at hydrate so absence stops existing rather than being
+	* re-derived on every read. `enabled` survives one release as a DERIVED
+	* mirror (`mode === 'active'`); `withLocationMode` is the only writer of
+	* either, so the two cannot disagree.
+	*/
+	mode: StorageLocationModeSchema.optional(),
 	/** COMPUTED at read time by the orchestrator (statfs of the backing volume
 	*  for node-local locations it can reach) — never persisted, absent when the
 	*  volume is remote/unreachable. The single capacity truth every UI reads. */
@@ -4943,13 +5006,83 @@ var StorageLocationSchema = zod.z.object({
 		totalBytes: zod.z.number(),
 		availableBytes: zod.z.number()
 	}).nullable().optional(),
+	/**
+	* How much of that volume CamStack ITSELF holds on this location (D388) —
+	* COMPUTED at read time from the `storage-occupancy` providers' own figures,
+	* never persisted, never a filesystem walk.
+	*
+	* **ABSENT MEANS UNKNOWN, never zero.** No provider has reported for this
+	* location yet — nobody stores here, the owning addon is down, or the first
+	* refresh has not completed. A UI must omit the segment rather than draw it
+	* at zero, which would claim we occupy nothing (D315). It is an OBJECT and
+	* not a bare number precisely so that a `?? 0` on the consuming side has to
+	* be spelled out loud instead of appearing by accident.
+	*
+	* `measuredAtMs` is the OLDEST contributing measurement, so it is honest
+	* about the whole figure rather than about its freshest part.
+	*/
+	owned: zod.z.object({
+		bytes: zod.z.number().int().nonnegative(),
+		measuredAtMs: zod.z.number().int().nonnegative()
+	}).optional(),
 	createdAt: zod.z.number(),
 	updatedAt: zod.z.number()
 });
 /**
+* The retired `isDefault` key, DECLARED rather than dropped.
+*
+* A key removed from a non-strict `z.object` is stripped in silence (D380,
+* D381): a reader that still needs the old value gets `undefined` and cannot
+* tell "absent" from "never sent". The one reader that legitimately needs it —
+* the location store's boot migration, which turns the old default flag into
+* the `enabled` write set — parses THIS schema against the raw row instead, so
+* the migration is explicit and the live schema stays clean. Nothing else in
+* the repo may read it; `scripts/check-no-storage-default.ts` enforces that.
+*/
+var LegacyStorageLocationDefaultSchema = zod.z.object({ isDefault: zod.z.boolean().optional() });
+function isLocationEnabled(location) {
+	return mayWriteToLocation({
+		...location,
+		config: location.config ?? {}
+	});
+}
+/**
+* Bytes in one GB, for every storage figure an operator types.
+*
+* BINARY (1024³), everywhere. The repo had both: the orchestrator's
+* `maxUsedGb` → bytes conversion used 1024³ while the recorder's placement
+* headroom used 10⁹ for the SAME stored key, so a location with a cap set was
+* silently 7.4% off depending on which side of the pipe asked. The persisted
+* values were entered against the binary unit and the admin UI reads it, so
+* that is the one that stays. Every GB knob — `maxUsedGb`, `minFreeGb` —
+* converts through {@link gbToBytes} and nowhere else.
+*/
+var STORAGE_BYTES_PER_GB = 1024 ** 3;
+/** GB → bytes, binary. Fractional GB is admitted and floored. */
+function gbToBytes(gb) {
+	return Math.floor(gb * STORAGE_BYTES_PER_GB);
+}
+/**
+* How far a `drain` has got (D386) — the read a UI renders, and nothing more.
+*
+* `estimatedEmptyAtMs` is derived from the growth the ratchet has actually
+* OBSERVED and is `null` when it has observed none. Never a fabricated date: a
+* drain with no observed growth has no honest ETA, and inventing one is how an
+* operator learns not to believe the screen.
+*/
+var StorageDrainProgressSchema = zod.z.object({
+	locationId: zod.z.string(),
+	startedAtMs: zod.z.number(),
+	startBytes: zod.z.number(),
+	bytesRemaining: zod.z.number(),
+	drained: zod.z.boolean(),
+	estimatedEmptyAtMs: zod.z.number().nullable()
+});
+/**
 * Reference accepted by consumer-facing `api.storage.*` calls.
 * Either:
-*  - a `StorageLocationType` (e.g. `'backups'`) → orchestrator resolves to the default of that type
+*  - a `StorageLocationType` (e.g. `'backups'`) → the sole location of that type
+*    (transitionally, the `<type>:default`-slugged row when several exist)
 *  - a fully-qualified id (e.g. `'backups:nas-01'`) → addresses a specific instance
 *
 * The orchestrator's `resolveRef(ref)` handles both cases.
@@ -5131,6 +5264,111 @@ var DecoderSessionConfigSchema = zod.z.object({
 	*/
 	debug: zod.z.boolean().optional()
 });
+/**
+* Per-component log CHANNELS — the gate a hot path consults, and the registry
+* an addon declares its channels in.
+*
+* ## Two axes, deliberately separated
+*
+* - **DECLARATION** — which channels exist. Only the addon knows:
+*   `stream-broker` knows webrtc/ICE/RTP, `provider-reolink` knows
+*   baichuan/handshake. A hand-wired central list rots at the first addition,
+*   and rots silently. So a channel is declared where it is consulted, and the
+*   `log-channels` capability enumerates the declarations.
+* - **VALUE** — at which level, for which scope, until when. That stays ONE
+*   thing: the logging settings document on the `system` cap. Two authorities
+*   over the values is the exact defect
+*   `docs/design/plans/2026-08-26-logging-per-componente.md` was written to
+*   remove; re-introducing it from the cure side would be grotesque.
+*
+* Nothing in this file reads a clock, an env var or a store. The registry is
+* a MIRROR: it is moved only by {@link LogChannelRegistry.apply}, called off
+* the hot path with a value somebody actually read, and by
+* {@link LogChannelRegistry.tick}, called on a timer. A store read that fails
+* never reaches here, so it can neither disarm an armed channel nor arm a
+* disarmed one (D49).
+*
+* ## The canonical call shape
+*
+* ```ts
+* if (CH_RTP.on && CH_RTP.wants(deviceId)) {
+*   CH_RTP.log(logger, 'rtp subscriber added', { tags: { deviceId }, meta: { ssrc } })
+* }
+* ```
+*
+* `on` is a plain boolean FIELD — never a getter — and it is the FIRST thing
+* read. Disarmed, a call site costs one load and one branch, and the `extras`
+* object literal is never constructed because it lives inside the branch. It
+* is the same shape already proven in production at `stream-broker.ts:1650`,
+* and the same discipline `LoggingGate.allowsDestination` uses for the
+* destination floor (measured at 1.93 ns/call when off).
+*
+* ## Why a channel emits at `info`
+*
+* `loki-logging.addon.ts` pins the destination default at `info` and
+* `loki-destination.ts` drops everything below it, so a line emitted at
+* `debug` never reaches Loki and the hub's in-memory ring only holds ~35
+* minutes. A diagnostic that cannot be read an hour later is worse than no
+* diagnostic, because it looks done. {@link LogChannelGate.log} therefore
+* emits at the channel's declared level, whose schema floor is `info`.
+*/
+/**
+* The level a channel writes at once armed.
+*
+* `debug` is absent ON PURPOSE and not by omission: below `info` the line does
+* not leave the process for Loki, and the whole point of arming a channel is
+* to read it later.
+*/
+var LogChannelLevelSchema = zod.z.enum([
+	"info",
+	"warn",
+	"error"
+]);
+/**
+* What an addon declares about one channel. No value, no state — a
+* declaration is inert.
+*/
+var LogChannelDescriptorSchema = zod.z.object({
+	/**
+	* Dotted `area.thing`, unique across the workspace. `area` is conventionally
+	* the addon's short name so an operator reading a channel list can tell who
+	* owns it without a second lookup.
+	*/
+	name: zod.z.string().min(3).regex(/^[a-z0-9-]+(\.[a-z0-9-]+)+$/, "a channel name is dotted lower-kebab, e.g. area.thing"),
+	/** One sentence: what the operator will SEE after arming it. */
+	description: zod.z.string().min(1),
+	/** The level its lines are emitted at. Never below `info`. */
+	defaultLevel: LogChannelLevelSchema,
+	/**
+	* Whether this channel can be narrowed to a camera.
+	*
+	* `true` is a PROMISE with two halves, and both must hold: the gate is
+	* consulted with the numeric device id, AND every line the channel admits
+	* carries `tags: { deviceId }` with that same numeric id. The second half is
+	* what makes `| json | deviceId="617"` work in Loki — `loki-payload.ts`
+	* keeps `deviceId` out of the stream labels for cardinality, so the tag in
+	* the body is the only way to filter.
+	*
+	* A channel whose lines carry the device only in `meta` (or not at all) is
+	* declared `false`. Declaring it `true` anyway would be a lie the UI repeats:
+	* the operator narrows to one camera, sees nothing, and concludes the code
+	* path was never taken.
+	*/
+	perDevice: zod.z.boolean()
+});
+/**
+* An armed window over one channel, as the document hands it to a mirror.
+*
+* A window is a DEADLINE, never a flag (ADR-0244): a channel somebody forgot
+* expires by itself, which is the one failure a boolean cannot avoid.
+*/
+var LogChannelWindowSchema = zod.z.object({
+	channel: zod.z.string().min(1),
+	/** Epoch ms the window closes at. */
+	armedUntilMs: zod.z.number(),
+	/** `null` = every camera. A non-empty list narrows to those numeric ids. */
+	deviceIds: zod.z.array(zod.z.number().int()).readonly().nullable()
+});
 /** Bucket key for rows no addon owns. Stable, so its series is continuous. */
 var UNATTRIBUTED_BUCKET_KEY = "__unattributed__";
 var ROOT_BUCKET_KEY = "__root__";
@@ -22090,7 +22328,6 @@ var storageCapability = {
 		}), zod.z.instanceof(Uint8Array)),
 		endDownload: method(zod.z.object({ downloadId: zod.z.string() }), zod.z.void(), { kind: "mutation" }),
 		listLocations: method(zod.z.object({ type: StorageLocationTypeSchema.optional() }), zod.z.array(StorageLocationSchema).readonly()),
-		getDefaultLocation: method(zod.z.object({ type: StorageLocationTypeSchema }), StorageLocationSchema.nullable()),
 		listLocationDeclarations: method(zod.z.void(), zod.z.array(StorageLocationDeclarationSchema).readonly()),
 		upsertLocation: method(StorageLocationSchema.omit({
 			createdAt: true,
@@ -22120,6 +22357,12 @@ var storageCapability = {
 			kind: "mutation",
 			auth: "admin"
 		}),
+		/**
+		* How far each draining location has got (D386). A pure READ of what the
+		* last pressure sweep computed — it starts no work, and a location that is
+		* not draining simply does not appear.
+		*/
+		listDrainProgress: method(zod.z.void(), zod.z.array(StorageDrainProgressSchema).readonly()),
 		testLocation: method(zod.z.object({ id: zod.z.string() }), zod.z.object({
 			ok: zod.z.boolean(),
 			error: zod.z.string().optional()
@@ -22267,6 +22510,71 @@ var storageMigrationCapability = {
 		history: method(zod.z.object({}), zod.z.array(StorageMigrationJobSchema).readonly(), { auth: "admin" })
 	}
 };
+/**
+* `storage-occupancy` — how many bytes an addon actually HOLDS on a storage
+* location (D388).
+*
+* ## Why this is not `storage-evictable`
+*
+* `storage-evictable.getEvictableUsage` looks like the same question and is
+* not, in two ways that both matter and both bite hardest on the locations an
+* operator most wants a figure for:
+*
+*  - it reports the whole eviction DOMAIN, not the location. `recordings:default`
+*    and `recordingsLow:default` deliberately share one root and evict as one
+*    oldest-first pool, so both answer with the SAME combined total. As an
+*    occupancy figure that double-counts the disk.
+*  - it reports ZERO for a location whose eviction policy is `never` (D385) —
+*    a `readonly` or `disabled` disk. Those are exactly the disks an operator
+*    is retiring and staring at.
+*
+* So this is its own contract with its own quantity, and the quantity is
+* OCCUPIED: every byte the addon holds on that location, whether or not it
+* would ever be willing to delete it. A provider that can only answer
+* "evictable" must not register here — a number that silently means different
+* things per class is worse than no number.
+*
+* ## Absence is an answer
+*
+* A location nobody reports for is UNKNOWN, never zero (D315). The orchestrator
+* stamps `StorageLocation.owned` only for locations it has a report for, and
+* the field is an OBJECT rather than a bare number so that a `?? 0` on the
+* consuming side has to be written out loud instead of appearing by accident.
+*
+* `internal: true` — consumed by the orchestrator's `listLocations` stamp, never
+* a public client surface. Clients read the stamped `StorageLocation.owned`.
+*/
+/** One provider's occupancy answer for one location. */
+var StorageOccupancyReportSchema = zod.z.object({
+	locationId: zod.z.string(),
+	/** Bytes this provider holds on THAT location — not its eviction domain, and
+	*  not net of what it is willing to delete. */
+	ownedBytes: zod.z.number().int().nonnegative(),
+	/** When the provider last actually measured this. The orchestrator carries it
+	*  through so a UI can say how old the figure is instead of implying "now". */
+	measuredAtMs: zod.z.number().int().nonnegative()
+});
+var storageOccupancyCapability = {
+	name: "storage-occupancy",
+	scope: "system",
+	mode: "collection",
+	internal: true,
+	methods: { 
+	/**
+	* Occupancy for the given locations, in ONE round trip.
+	*
+	* A provider answers only for the locations it actually holds bytes on and
+	* OMITS the rest — an omitted location is "I hold nothing measurable here",
+	* which the orchestrator merges as a contribution of nothing rather than as
+	* a claim that the location is empty. Only a location no provider reports
+	* at all stays unknown.
+	*
+	* This must be CHEAP and must never walk a filesystem: it is on the admin
+	* UI's `listLocations` path. The owner keeps its own figure fresh (D224) and
+	* answers from what it already has.
+	*/
+getOccupancy: method(zod.z.object({ locationIds: zod.z.array(zod.z.string()).readonly() }), zod.z.array(StorageOccupancyReportSchema).readonly(), { auth: "admin" }) }
+};
 var ProviderInfoSchema = zod.z.discriminatedUnion("shouldSaveDiskSpace", [zod.z.object({
 	providerId: zod.z.string().min(1),
 	displayName: zod.z.string().min(1),
@@ -24631,88 +24939,6 @@ onStatusChanged: { data: zod.z.object({
 	volatileStateFields: ["lastUpdated"]
 };
 /**
-* Network-link snapshot. Same shape for every provider (a Reolink wifi
-* camera, a Home Assistant device with a signal-strength sensor, a Tapo
-* plug): one slice under `device.runtimeState['network-link']`, one badge,
-* one Home Assistant projection.
-*/
-var NetworkLinkStatusSchema = zod.z.object({
-	/** The link the device is on. `'unknown'` = not read yet, not "no link". */
-	type: zod.z.enum([
-		"wifi",
-		"ethernet",
-		"cellular",
-		"unknown"
-	]),
-	/**
-	* Link quality, 0..100 inclusive, normalised by the provider from whatever
-	* the firmware reports (bars, RSSI, a vendor scale). **`null` means NOT
-	* KNOWN or NOT APPLICABLE** — a wired link has no signal, and a wireless
-	* one whose reading has not landed must not be drawn at 0 %. Consumers
-	* SKIP a null rather than coerce it.
-	*/
-	signalPercent: zod.z.number().min(0).max(100).nullable(),
-	/** Raw received signal strength in dBm, when the firmware reports one. */
-	rssiDbm: zod.z.number().optional(),
-	/** Network name of a wireless link, when the firmware reports it. */
-	ssid: zod.z.string().optional(),
-	/** Ms epoch of the last observation. Lets consumers reason about freshness. */
-	lastUpdated: zod.z.number()
-});
-var networkLinkCapability = {
-	name: "network-link",
-	scope: "device",
-	deviceNative: true,
-	mode: "singleton",
-	deviceTypes: [
-		DeviceType.Camera,
-		DeviceType.Sensor,
-		DeviceType.Button,
-		DeviceType.Switch,
-		DeviceType.Light,
-		DeviceType.Lock,
-		DeviceType.Siren
-	],
-	methods: {},
-	events: { 
-	/**
-	* Emitted whenever the cached status changes (a link switch, a signal
-	* reading that moved). Mirrored on the parent chain by the
-	* DeviceEventPropagator like `battery.onStatusChanged`.
-	*/
-onStatusChanged: { data: zod.z.object({
-		deviceId: zod.z.number(),
-		status: NetworkLinkStatusSchema
-	}) } },
-	status: {
-		schema: NetworkLinkStatusSchema,
-		kind: "push",
-		empty: {
-			type: "unknown",
-			signalPercent: null,
-			lastUpdated: 0
-		}
-	},
-	/**
-	* Runtime-state slice — every provider stores the same shape under
-	* `device.runtimeState['network-link']`, read once by the badge and the
-	* Home Assistant projector regardless of the driver.
-	*/
-	runtimeState: NetworkLinkStatusSchema,
-	/**
-	* Runtime-state durability: **restored** — a link reading is slow to
-	* change and a sleeping battery camera may not report for hours; the
-	* restored slice is what the badge shows until the next read.
-	*
-	* 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: ["lastUpdated"]
-};
-/**
 * Generic boolean sensor — last-resort fallback when no domain-
 * specific binary cap fits (Home Assistant `binary_sensor` without a
 * known `device_class`, or a domain we haven't typed yet). Pure
@@ -28590,6 +28816,371 @@ var nativeObjectDetectionCapability = {
 	volatileStateFields: ["lastFetchedAt"]
 };
 /**
+* `navigation` — a device-scoped capability that natively expresses the FULL
+* navigation / action surface of a robot that DRIVES ITSELF and carries an
+* on-board camera (the Dreame robot-vacuum camera is the first provider).
+*
+* Why a NEW cap rather than overloading `ptz`:
+*   - `ptz` moves a *gimbal* on a fixed camera (pan/tilt/zoom of the lens). A
+*     robot vacuum has no gimbal — the whole chassis drives, turns and spins.
+*     The two are different physical models: PTZ is absolute-position + presets,
+*     navigation is momentary drive nudges + discrete robot ACTIONS
+*     (dock / spot-clean / follow-pet / go-to-point / …).
+*   - This cap is the SOURCE OF TRUTH. Two consumers adapt from it rather than
+*     the reverse:
+*       1. a native CamStack navigation panel (data-driven from `listActions`
+*          / `getOptions`), and
+*       2. the PTZ surface — a thin adapter mimics `ptz` from `navigation` so a
+*          robot camera shows up in the existing PTZ control path without every
+*          PTZ provider learning about robots. The mapping lives in the adapter,
+*          not here (see the addon design note):
+*            ptz.continuousMove({pan,tilt}) → navigation.move({pan,tilt})
+*            ptz.stop()                      → navigation.stop()
+*            ptz.goHome()                    → navigation.runAction('goHome')
+*            ptz.getPresets()                → navigation.listActions()  (id→preset)
+*            ptz.goToPreset(id)              → navigation.runAction(id)
+*
+* ## Continuous drive
+*
+* `move` is MOMENTARY. Fluid navigation comes from the UI (or the PTZ adapter)
+* sending `move({pan,tilt})` REPEATEDLY at ~1 Hz while a direction is held, and
+* one `stop()` on release — exactly like the robot app's remote-drive joystick.
+* The provider forwards EACH `move` to one drive write; it must NOT debounce or
+* coalesce them. The UI owns the cadence.
+*
+* ## The action dictionary
+*
+* The discrete controls (dock / locate / spot-clean / follow / flash / sounds)
+* are a DATA-DRIVEN dictionary the cap exposes via `listActions()`. Each entry
+* carries `{ id, kind, label, icon }` (plus `soundId` for sound entries) so the
+* native panel AND the PTZ mimic render buttons WITHOUT hardcoding a
+* vendor-specific list. `kind: 'action'` entries are triggered with
+* `runAction({ actionId })`; `kind: 'sound'` entries with `playSound({ soundId })`
+* (the entry carries the `soundId` to pass). The general primitives — `move`,
+* `stop`, `goToPoint` — stay as first-class methods, not dictionary entries.
+*
+* NOTE (provider wiring): the first provider (Dreame) drives this with the RAW
+* `callAction(siid,aiid,in)` / `setProperty({siid,piid,value})` MIoT primitives
+* that the currently-published `@apocaliss92/nodedreame` already exposes on
+* every device handle. A future nodedreame publish adds a typed
+* `DreameCameraController` (drive / playPetSound / spotClean / findPet / …); the
+* provider can then swap the raw calls for the typed methods with no change to
+* THIS contract.
+*/
+/**
+* A momentary drive nudge. The robot MOVES (no gimbal) for as long as the caller
+* keeps sending nudges (~1 Hz); an explicit `stop` (or letting the nudges lapse)
+* halts it.
+*
+*   - `pan`   — turn: negative = left, positive = right, 0 = straight.
+*   - `tilt`  — throttle: positive = forward, negative = spin / turn-around.
+*   - `speed` — optional intensity hint [0, 1]; the provider may scale the drive
+*               vector by it (drivers without proportional drive ignore it).
+*
+* `pan` / `tilt` are normalized [-1, 1]. Both optional so a caller can nudge one
+* axis alone; an all-undefined nudge is a no-op.
+*/
+var NavigationMoveCommandSchema = zod.z.object({
+	pan: zod.z.number().min(-1).max(1).optional(),
+	tilt: zod.z.number().min(-1).max(1).optional(),
+	speed: zod.z.number().min(0).max(1).optional()
+});
+/**
+* The enumerated discrete actions a navigation-capable robot can perform via
+* `runAction`. This is the CLOSED vocabulary; a given device advertises the
+* subset it supports through `listActions`. Sounds are NOT here — they go through
+* `playSound` (see the `sound` dictionary entries).
+*/
+var NavigationActionIdSchema = zod.z.enum([
+	"goHome",
+	"locate",
+	"spotClean",
+	"findPet",
+	"personFollow",
+	"stop",
+	"startClean",
+	"pauseClean",
+	"dockWash",
+	"autoEmpty",
+	"flashOn",
+	"flashOff"
+]);
+/** Whether a dictionary entry is a `runAction` action or a `playSound` sound. */
+var NavigationEntryKindSchema = zod.z.enum(["action", "sound"]);
+/**
+* One entry in the navigation action dictionary — the DATA-DRIVEN unit both the
+* native panel and the PTZ mimic render as a button.
+*
+*   - `id`      — stable id. For `kind:'action'` it is a {@link NavigationActionId}
+*                 (pass to `runAction`); for `kind:'sound'` it is a namespaced id
+*                 (`sound:meow`) whose `soundId` is passed to `playSound`.
+*   - `icon`    — icon HINT (lucide-style name; the UI maps it to its own set).
+*   - `label`   — operator-facing English label.
+*   - `soundId` — wire sound id, present only on `kind:'sound'` entries.
+*   - `enabled` — per-device FEATURE FLAG. `listActions` reports it so the UI /
+*                 PTZ render ONLY enabled entries. Data-driven: the provider
+*                 flips it from config, never by editing code.
+*/
+var NavigationActionEntrySchema = zod.z.object({
+	id: zod.z.string(),
+	kind: NavigationEntryKindSchema,
+	label: zod.z.string(),
+	icon: zod.z.string(),
+	/** Present only on `kind:'sound'` entries — the id to pass to `playSound`. */
+	soundId: zod.z.number().int().optional(),
+	/** Per-device feature flag — render this entry only when true. */
+	enabled: zod.z.boolean()
+});
+/** Coordinates for `goToPoint` — a point on the robot's live map. */
+var NavigationPointSchema = zod.z.object({
+	x: zod.z.number(),
+	y: zod.z.number()
+});
+/**
+* Per-device FEATURE-FLAG report for the general (non-dictionary) primitives.
+* The cap reports which are enabled so the UI / PTZ render only the controls
+* that are turned on for THIS device. Data-driven: the provider derives these
+* from config + probe, never hardcoded in the UI. The per-DICTIONARY-entry flags
+* live on {@link NavigationActionEntrySchema.enabled}; these gate the primitives
+* that are not dictionary entries.
+*
+*   - `move` / `stop`   — the momentary drive joystick.
+*   - `goToPoint`       — send-to-map-coordinate. Ships OFF on Dreame until the
+*                         map-coordinate plumbing is wired.
+*   - `runAction`       — the discrete action buttons (dictionary `kind:'action'`).
+*   - `playSound`       — the sound buttons (dictionary `kind:'sound'`).
+*   - `light`           — the on/off fill-light toggle (works anytime).
+*   - `lightMode`       — the auto/manual selector + manual level slider (a
+*                         camera-service control; needs an active stream).
+*/
+var NavigationFeaturesSchema = zod.z.object({
+	move: zod.z.boolean(),
+	stop: zod.z.boolean(),
+	goToPoint: zod.z.boolean(),
+	runAction: zod.z.boolean(),
+	playSound: zod.z.boolean(),
+	light: zod.z.boolean(),
+	lightMode: zod.z.boolean()
+});
+/** Light mode: `auto` lets the camera choose brightness; `manual` uses `level`. */
+var NavigationLightModeSchema = zod.z.enum(["auto", "manual"]);
+/** Coarse work mode the robot reports — drives the UI's active-state chips. */
+var NavigationModeSchema = zod.z.enum([
+	"idle",
+	"cleaning",
+	"spot",
+	"following",
+	"goto",
+	"returning",
+	"paused",
+	"unknown"
+]);
+/**
+* Live navigation state so the UI can reflect what the robot is doing:
+*   - `mode`       — coarse activity (idle / cleaning / following / …).
+*   - `following`  — person/pet follow is currently armed.
+*   - `flash`      — the on-camera fill light is on.
+*   - `lightMode`  — auto vs manual fill-light mode.
+*   - `lightLevel` — manual fill-light level (40..100); meaningful when
+*                    `lightMode === 'manual'`.
+*/
+var NavigationStatusSchema = zod.z.object({
+	mode: NavigationModeSchema,
+	following: zod.z.boolean(),
+	flash: zod.z.boolean(),
+	lightMode: NavigationLightModeSchema,
+	lightLevel: zod.z.number().min(40).max(100),
+	/** Ms epoch when the slice was last updated. */
+	lastChangedAt: zod.z.number()
+});
+/**
+* Runtime-state slice owned by this cap (kernel-managed: validated, mirrored,
+* observable). Adds `lastFetchedAt` on top of the status shape per the
+* convention.
+*/
+var NavigationRuntimeStateSchema = NavigationStatusSchema.extend({ lastFetchedAt: zod.z.number() });
+var navigationCapability = {
+	name: "navigation",
+	scope: "device",
+	deviceNative: true,
+	mode: "singleton",
+	deviceTypes: [DeviceType.Camera],
+	deviceConfig: { ui: {
+		kind: "widget",
+		widgetId: "host/navigation-panel",
+		tab: "navigation",
+		topTab: true,
+		label: "Navigation",
+		order: 0
+	} },
+	methods: {
+		/**
+		* Momentary drive nudge (the robot moves). `protected` — mirrors
+		* `ptz.continuousMove` so the Viewer navigation panel (and the PTZ-mimic
+		* path) works for any authenticated user, not admin-only. The UI sends
+		* these at ~1 Hz while a control is held; the provider forwards each one to
+		* a single drive write WITHOUT debouncing.
+		*/
+		move: method(NavigationMoveCommandSchema.extend({ deviceId: zod.z.number() }), zod.z.void(), { kind: "mutation" }),
+		/** Halt all motion immediately (zero drive vector). */
+		stop: method(zod.z.object({ deviceId: zod.z.number() }), zod.z.void(), { kind: "mutation" }),
+		/** Send the robot to a point on its live map. */
+		goToPoint: method(NavigationPointSchema.extend({ deviceId: zod.z.number() }), zod.z.void(), { kind: "mutation" }),
+		/**
+		* Enumerate the discrete controls THIS device supports (data-driven UI +
+		* PTZ mimic). Camera-probed subset of {@link NAVIGATION_ACTION_CATALOG}.
+		*/
+		listActions: method(zod.z.object({ deviceId: zod.z.number() }), zod.z.array(NavigationActionEntrySchema)),
+		/**
+		* Run one discrete action (a `kind:'action'` dictionary entry). Invalid /
+		* unsupported action ids are rejected by the provider.
+		*/
+		runAction: method(zod.z.object({
+			deviceId: zod.z.number(),
+			actionId: NavigationActionIdSchema
+		}), zod.z.void(), { kind: "mutation" }),
+		/** Play a sound by its wire id (the `soundId` of a `kind:'sound'` entry). */
+		playSound: method(zod.z.object({
+			deviceId: zod.z.number(),
+			soundId: zod.z.number().int()
+		}), zod.z.void(), { kind: "mutation" }),
+		/**
+		* Turn the on-camera fill light on / off (the `OpenFullLight` control —
+		* works anytime, no active stream required).
+		*/
+		setLightOn: method(zod.z.object({
+			deviceId: zod.z.number(),
+			on: zod.z.boolean()
+		}), zod.z.void(), { kind: "mutation" }),
+		/**
+		* Set the fill-light mode (auto vs manual). `manual` optionally carries the
+		* initial `level`. The auto/manual + level control is a CAMERA-service
+		* action that generally needs an active camera stream/monitor session — the
+		* UI shows the manual level slider ONLY when `mode === 'manual'`.
+		*/
+		setLightMode: method(zod.z.object({
+			deviceId: zod.z.number(),
+			mode: NavigationLightModeSchema,
+			level: zod.z.number().min(40).max(100).optional()
+		}), zod.z.void(), { kind: "mutation" }),
+		/** Set the MANUAL fill-light level (40..100). Implies `manual` mode. */
+		setLightLevel: method(zod.z.object({
+			deviceId: zod.z.number(),
+			level: zod.z.number().min(40).max(100)
+		}), zod.z.void(), { kind: "mutation" }),
+		/**
+		* Per-device FEATURE-FLAG report for the general primitives — drives which
+		* controls the UI shows (the per-entry flags for the dictionary come back on
+		* `listActions`).
+		*/
+		getFeatures: method(zod.z.object({ deviceId: zod.z.number() }), NavigationFeaturesSchema)
+	},
+	events: { onStatusChanged: { data: zod.z.object({
+		deviceId: zod.z.number(),
+		status: NavigationStatusSchema
+	}) } },
+	status: {
+		schema: NavigationStatusSchema,
+		kind: "push"
+	},
+	/**
+	* Runtime-state slice mirrored by the kernel. The navigation panel watches it
+	* for live mode / follow / flash changes.
+	*/
+	runtimeState: NavigationRuntimeStateSchema,
+	/**
+	* Runtime-state durability: **session** — like `vacuum-control`, a restored
+	* `mode: cleaning` / `following: true` is a robot that is not actually doing
+	* that. The live handle re-publishes on connect.
+	*
+	* See `RuntimeStateDurability`. Enforced by
+	* `scripts/check-runtime-state-durability.ts`.
+	*/
+	durability: "session"
+};
+/**
+* Network-link snapshot. Same shape for every provider (a Reolink wifi
+* camera, a Home Assistant device with a signal-strength sensor, a Tapo
+* plug): one slice under `device.runtimeState['network-link']`, one badge,
+* one Home Assistant projection.
+*/
+var NetworkLinkStatusSchema = zod.z.object({
+	/** The link the device is on. `'unknown'` = not read yet, not "no link". */
+	type: zod.z.enum([
+		"wifi",
+		"ethernet",
+		"cellular",
+		"unknown"
+	]),
+	/**
+	* Link quality, 0..100 inclusive, normalised by the provider from whatever
+	* the firmware reports (bars, RSSI, a vendor scale). **`null` means NOT
+	* KNOWN or NOT APPLICABLE** — a wired link has no signal, and a wireless
+	* one whose reading has not landed must not be drawn at 0 %. Consumers
+	* SKIP a null rather than coerce it.
+	*/
+	signalPercent: zod.z.number().min(0).max(100).nullable(),
+	/** Raw received signal strength in dBm, when the firmware reports one. */
+	rssiDbm: zod.z.number().optional(),
+	/** Network name of a wireless link, when the firmware reports it. */
+	ssid: zod.z.string().optional(),
+	/** Ms epoch of the last observation. Lets consumers reason about freshness. */
+	lastUpdated: zod.z.number()
+});
+var networkLinkCapability = {
+	name: "network-link",
+	scope: "device",
+	deviceNative: true,
+	mode: "singleton",
+	deviceTypes: [
+		DeviceType.Camera,
+		DeviceType.Sensor,
+		DeviceType.Button,
+		DeviceType.Switch,
+		DeviceType.Light,
+		DeviceType.Lock,
+		DeviceType.Siren
+	],
+	methods: {},
+	events: { 
+	/**
+	* Emitted whenever the cached status changes (a link switch, a signal
+	* reading that moved). Mirrored on the parent chain by the
+	* DeviceEventPropagator like `battery.onStatusChanged`.
+	*/
+onStatusChanged: { data: zod.z.object({
+		deviceId: zod.z.number(),
+		status: NetworkLinkStatusSchema
+	}) } },
+	status: {
+		schema: NetworkLinkStatusSchema,
+		kind: "push",
+		empty: {
+			type: "unknown",
+			signalPercent: null,
+			lastUpdated: 0
+		}
+	},
+	/**
+	* Runtime-state slice — every provider stores the same shape under
+	* `device.runtimeState['network-link']`, read once by the badge and the
+	* Home Assistant projector regardless of the driver.
+	*/
+	runtimeState: NetworkLinkStatusSchema,
+	/**
+	* Runtime-state durability: **restored** — a link reading is slow to
+	* change and a sleeping battery camera may not report for hours; the
+	* restored slice is what the badge shows until the next read.
+	*
+	* 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: ["lastUpdated"]
+};
+/**
 * network-quality — system-scoped singleton capability tracking RTT,
 * jitter, and observed/peak bandwidth per device + per client.
 *
@@ -30440,289 +31031,6 @@ var ptzAutotrackCapability = {
 	durability: "session"
 };
 /**
-* `navigation` — a device-scoped capability that natively expresses the FULL
-* navigation / action surface of a robot that DRIVES ITSELF and carries an
-* on-board camera (the Dreame robot-vacuum camera is the first provider).
-*
-* Why a NEW cap rather than overloading `ptz`:
-*   - `ptz` moves a *gimbal* on a fixed camera (pan/tilt/zoom of the lens). A
-*     robot vacuum has no gimbal — the whole chassis drives, turns and spins.
-*     The two are different physical models: PTZ is absolute-position + presets,
-*     navigation is momentary drive nudges + discrete robot ACTIONS
-*     (dock / spot-clean / follow-pet / go-to-point / …).
-*   - This cap is the SOURCE OF TRUTH. Two consumers adapt from it rather than
-*     the reverse:
-*       1. a native CamStack navigation panel (data-driven from `listActions`
-*          / `getOptions`), and
-*       2. the PTZ surface — a thin adapter mimics `ptz` from `navigation` so a
-*          robot camera shows up in the existing PTZ control path without every
-*          PTZ provider learning about robots. The mapping lives in the adapter,
-*          not here (see the addon design note):
-*            ptz.continuousMove({pan,tilt}) → navigation.move({pan,tilt})
-*            ptz.stop()                      → navigation.stop()
-*            ptz.goHome()                    → navigation.runAction('goHome')
-*            ptz.getPresets()                → navigation.listActions()  (id→preset)
-*            ptz.goToPreset(id)              → navigation.runAction(id)
-*
-* ## Continuous drive
-*
-* `move` is MOMENTARY. Fluid navigation comes from the UI (or the PTZ adapter)
-* sending `move({pan,tilt})` REPEATEDLY at ~1 Hz while a direction is held, and
-* one `stop()` on release — exactly like the robot app's remote-drive joystick.
-* The provider forwards EACH `move` to one drive write; it must NOT debounce or
-* coalesce them. The UI owns the cadence.
-*
-* ## The action dictionary
-*
-* The discrete controls (dock / locate / spot-clean / follow / flash / sounds)
-* are a DATA-DRIVEN dictionary the cap exposes via `listActions()`. Each entry
-* carries `{ id, kind, label, icon }` (plus `soundId` for sound entries) so the
-* native panel AND the PTZ mimic render buttons WITHOUT hardcoding a
-* vendor-specific list. `kind: 'action'` entries are triggered with
-* `runAction({ actionId })`; `kind: 'sound'` entries with `playSound({ soundId })`
-* (the entry carries the `soundId` to pass). The general primitives — `move`,
-* `stop`, `goToPoint` — stay as first-class methods, not dictionary entries.
-*
-* NOTE (provider wiring): the first provider (Dreame) drives this with the RAW
-* `callAction(siid,aiid,in)` / `setProperty({siid,piid,value})` MIoT primitives
-* that the currently-published `@apocaliss92/nodedreame` already exposes on
-* every device handle. A future nodedreame publish adds a typed
-* `DreameCameraController` (drive / playPetSound / spotClean / findPet / …); the
-* provider can then swap the raw calls for the typed methods with no change to
-* THIS contract.
-*/
-/**
-* A momentary drive nudge. The robot MOVES (no gimbal) for as long as the caller
-* keeps sending nudges (~1 Hz); an explicit `stop` (or letting the nudges lapse)
-* halts it.
-*
-*   - `pan`   — turn: negative = left, positive = right, 0 = straight.
-*   - `tilt`  — throttle: positive = forward, negative = spin / turn-around.
-*   - `speed` — optional intensity hint [0, 1]; the provider may scale the drive
-*               vector by it (drivers without proportional drive ignore it).
-*
-* `pan` / `tilt` are normalized [-1, 1]. Both optional so a caller can nudge one
-* axis alone; an all-undefined nudge is a no-op.
-*/
-var NavigationMoveCommandSchema = zod.z.object({
-	pan: zod.z.number().min(-1).max(1).optional(),
-	tilt: zod.z.number().min(-1).max(1).optional(),
-	speed: zod.z.number().min(0).max(1).optional()
-});
-/**
-* The enumerated discrete actions a navigation-capable robot can perform via
-* `runAction`. This is the CLOSED vocabulary; a given device advertises the
-* subset it supports through `listActions`. Sounds are NOT here — they go through
-* `playSound` (see the `sound` dictionary entries).
-*/
-var NavigationActionIdSchema = zod.z.enum([
-	"goHome",
-	"locate",
-	"spotClean",
-	"findPet",
-	"personFollow",
-	"stop",
-	"startClean",
-	"pauseClean",
-	"dockWash",
-	"autoEmpty",
-	"flashOn",
-	"flashOff"
-]);
-/** Whether a dictionary entry is a `runAction` action or a `playSound` sound. */
-var NavigationEntryKindSchema = zod.z.enum(["action", "sound"]);
-/**
-* One entry in the navigation action dictionary — the DATA-DRIVEN unit both the
-* native panel and the PTZ mimic render as a button.
-*
-*   - `id`      — stable id. For `kind:'action'` it is a {@link NavigationActionId}
-*                 (pass to `runAction`); for `kind:'sound'` it is a namespaced id
-*                 (`sound:meow`) whose `soundId` is passed to `playSound`.
-*   - `icon`    — icon HINT (lucide-style name; the UI maps it to its own set).
-*   - `label`   — operator-facing English label.
-*   - `soundId` — wire sound id, present only on `kind:'sound'` entries.
-*   - `enabled` — per-device FEATURE FLAG. `listActions` reports it so the UI /
-*                 PTZ render ONLY enabled entries. Data-driven: the provider
-*                 flips it from config, never by editing code.
-*/
-var NavigationActionEntrySchema = zod.z.object({
-	id: zod.z.string(),
-	kind: NavigationEntryKindSchema,
-	label: zod.z.string(),
-	icon: zod.z.string(),
-	/** Present only on `kind:'sound'` entries — the id to pass to `playSound`. */
-	soundId: zod.z.number().int().optional(),
-	/** Per-device feature flag — render this entry only when true. */
-	enabled: zod.z.boolean()
-});
-/** Coordinates for `goToPoint` — a point on the robot's live map. */
-var NavigationPointSchema = zod.z.object({
-	x: zod.z.number(),
-	y: zod.z.number()
-});
-/**
-* Per-device FEATURE-FLAG report for the general (non-dictionary) primitives.
-* The cap reports which are enabled so the UI / PTZ render only the controls
-* that are turned on for THIS device. Data-driven: the provider derives these
-* from config + probe, never hardcoded in the UI. The per-DICTIONARY-entry flags
-* live on {@link NavigationActionEntrySchema.enabled}; these gate the primitives
-* that are not dictionary entries.
-*
-*   - `move` / `stop`   — the momentary drive joystick.
-*   - `goToPoint`       — send-to-map-coordinate. Ships OFF on Dreame until the
-*                         map-coordinate plumbing is wired.
-*   - `runAction`       — the discrete action buttons (dictionary `kind:'action'`).
-*   - `playSound`       — the sound buttons (dictionary `kind:'sound'`).
-*   - `light`           — the on/off fill-light toggle (works anytime).
-*   - `lightMode`       — the auto/manual selector + manual level slider (a
-*                         camera-service control; needs an active stream).
-*/
-var NavigationFeaturesSchema = zod.z.object({
-	move: zod.z.boolean(),
-	stop: zod.z.boolean(),
-	goToPoint: zod.z.boolean(),
-	runAction: zod.z.boolean(),
-	playSound: zod.z.boolean(),
-	light: zod.z.boolean(),
-	lightMode: zod.z.boolean()
-});
-/** Light mode: `auto` lets the camera choose brightness; `manual` uses `level`. */
-var NavigationLightModeSchema = zod.z.enum(["auto", "manual"]);
-/** Coarse work mode the robot reports — drives the UI's active-state chips. */
-var NavigationModeSchema = zod.z.enum([
-	"idle",
-	"cleaning",
-	"spot",
-	"following",
-	"goto",
-	"returning",
-	"paused",
-	"unknown"
-]);
-/**
-* Live navigation state so the UI can reflect what the robot is doing:
-*   - `mode`       — coarse activity (idle / cleaning / following / …).
-*   - `following`  — person/pet follow is currently armed.
-*   - `flash`      — the on-camera fill light is on.
-*   - `lightMode`  — auto vs manual fill-light mode.
-*   - `lightLevel` — manual fill-light level (40..100); meaningful when
-*                    `lightMode === 'manual'`.
-*/
-var NavigationStatusSchema = zod.z.object({
-	mode: NavigationModeSchema,
-	following: zod.z.boolean(),
-	flash: zod.z.boolean(),
-	lightMode: NavigationLightModeSchema,
-	lightLevel: zod.z.number().min(40).max(100),
-	/** Ms epoch when the slice was last updated. */
-	lastChangedAt: zod.z.number()
-});
-/**
-* Runtime-state slice owned by this cap (kernel-managed: validated, mirrored,
-* observable). Adds `lastFetchedAt` on top of the status shape per the
-* convention.
-*/
-var NavigationRuntimeStateSchema = NavigationStatusSchema.extend({ lastFetchedAt: zod.z.number() });
-var navigationCapability = {
-	name: "navigation",
-	scope: "device",
-	deviceNative: true,
-	mode: "singleton",
-	deviceTypes: [DeviceType.Camera],
-	deviceConfig: { ui: {
-		kind: "widget",
-		widgetId: "host/navigation-panel",
-		tab: "navigation",
-		topTab: true,
-		label: "Navigation",
-		order: 0
-	} },
-	methods: {
-		/**
-		* Momentary drive nudge (the robot moves). `protected` — mirrors
-		* `ptz.continuousMove` so the Viewer navigation panel (and the PTZ-mimic
-		* path) works for any authenticated user, not admin-only. The UI sends
-		* these at ~1 Hz while a control is held; the provider forwards each one to
-		* a single drive write WITHOUT debouncing.
-		*/
-		move: method(NavigationMoveCommandSchema.extend({ deviceId: zod.z.number() }), zod.z.void(), { kind: "mutation" }),
-		/** Halt all motion immediately (zero drive vector). */
-		stop: method(zod.z.object({ deviceId: zod.z.number() }), zod.z.void(), { kind: "mutation" }),
-		/** Send the robot to a point on its live map. */
-		goToPoint: method(NavigationPointSchema.extend({ deviceId: zod.z.number() }), zod.z.void(), { kind: "mutation" }),
-		/**
-		* Enumerate the discrete controls THIS device supports (data-driven UI +
-		* PTZ mimic). Camera-probed subset of {@link NAVIGATION_ACTION_CATALOG}.
-		*/
-		listActions: method(zod.z.object({ deviceId: zod.z.number() }), zod.z.array(NavigationActionEntrySchema)),
-		/**
-		* Run one discrete action (a `kind:'action'` dictionary entry). Invalid /
-		* unsupported action ids are rejected by the provider.
-		*/
-		runAction: method(zod.z.object({
-			deviceId: zod.z.number(),
-			actionId: NavigationActionIdSchema
-		}), zod.z.void(), { kind: "mutation" }),
-		/** Play a sound by its wire id (the `soundId` of a `kind:'sound'` entry). */
-		playSound: method(zod.z.object({
-			deviceId: zod.z.number(),
-			soundId: zod.z.number().int()
-		}), zod.z.void(), { kind: "mutation" }),
-		/**
-		* Turn the on-camera fill light on / off (the `OpenFullLight` control —
-		* works anytime, no active stream required).
-		*/
-		setLightOn: method(zod.z.object({
-			deviceId: zod.z.number(),
-			on: zod.z.boolean()
-		}), zod.z.void(), { kind: "mutation" }),
-		/**
-		* Set the fill-light mode (auto vs manual). `manual` optionally carries the
-		* initial `level`. The auto/manual + level control is a CAMERA-service
-		* action that generally needs an active camera stream/monitor session — the
-		* UI shows the manual level slider ONLY when `mode === 'manual'`.
-		*/
-		setLightMode: method(zod.z.object({
-			deviceId: zod.z.number(),
-			mode: NavigationLightModeSchema,
-			level: zod.z.number().min(40).max(100).optional()
-		}), zod.z.void(), { kind: "mutation" }),
-		/** Set the MANUAL fill-light level (40..100). Implies `manual` mode. */
-		setLightLevel: method(zod.z.object({
-			deviceId: zod.z.number(),
-			level: zod.z.number().min(40).max(100)
-		}), zod.z.void(), { kind: "mutation" }),
-		/**
-		* Per-device FEATURE-FLAG report for the general primitives — drives which
-		* controls the UI shows (the per-entry flags for the dictionary come back on
-		* `listActions`).
-		*/
-		getFeatures: method(zod.z.object({ deviceId: zod.z.number() }), NavigationFeaturesSchema)
-	},
-	events: { onStatusChanged: { data: zod.z.object({
-		deviceId: zod.z.number(),
-		status: NavigationStatusSchema
-	}) } },
-	status: {
-		schema: NavigationStatusSchema,
-		kind: "push"
-	},
-	/**
-	* Runtime-state slice mirrored by the kernel. The navigation panel watches it
-	* for live mode / follow / flash changes.
-	*/
-	runtimeState: NavigationRuntimeStateSchema,
-	/**
-	* Runtime-state durability: **session** — like `vacuum-control`, a restored
-	* `mode: cleaning` / `following: true` is a robot that is not actually doing
-	* that. The live handle re-publishes on connect.
-	*
-	* See `RuntimeStateDurability`. Enforced by
-	* `scripts/check-runtime-state-durability.ts`.
-	*/
-	durability: "session"
-};
-/**
 * reboot — device-scoped capability for "soft" device reboots (firmware
 * reboot via vendor protocol; cameras, NVRs, doorbells). Surfaces a
 * single mutation so the UI can offer a confirm-and-reboot button for
@@ -34609,6 +34917,63 @@ var RUNTIME_DEFAULTS = {
 	"auth.tokenExpiry": "30d"
 };
 /**
+* Accessory device helpers — shared across drivers.
+*
+* Many vendor-specific drivers register accessory child devices on
+* top of a parent (Reolink: siren / floodlight / PIR / autotrack /
+* chime; ONVIF: relay outputs; future: Tapo Hub child devices). Each
+* driver picks the right `DeviceType` + `DeviceRole` explicitly when
+* spawning, builds a name derived from the parent, and produces a
+* stableId tied to the parent so boot-restore can reconstruct the
+* relationship.
+*
+* Centralised `(kind → DeviceType)` mapping was dropped on purpose:
+* drivers may reasonably disagree on the right type for an accessory
+* (a Reolink PIR exposes a switch on/off + sensitivity, while a hypothetical
+* read-only motion-only sensor might be `DeviceType.Sensor`). Forcing
+* one canonical mapping was over-prescriptive and added a layer of
+* indirection without saving meaningful code at call sites — the
+* driver knows its own hardware best.
+*/
+/**
+* Subset of `DeviceRole` values that drivers register as child
+* accessories of a parent device. Sourced verbatim from `DeviceRole`
+* — `AccessoryKind` is the alias drivers use when building accessory
+* children, so the call site reads as
+* `accessoryStableId(parent, AccessoryKind.Siren)` rather than
+* `accessoryStableId(parent, DeviceRole.Siren)` (which would imply
+* any role works, including non-accessory ones like Doorbell).
+*/
+var AccessoryKind = {
+	Siren: DeviceRole.Siren,
+	Floodlight: DeviceRole.Floodlight,
+	Spotlight: DeviceRole.Spotlight,
+	PirSensor: DeviceRole.PirSensor,
+	Chime: DeviceRole.Chime,
+	Autotrack: DeviceRole.Autotrack,
+	Nightvision: DeviceRole.Nightvision,
+	PrivacyMask: DeviceRole.PrivacyMask
+};
+AccessoryKind.Siren, AccessoryKind.Floodlight, AccessoryKind.Spotlight, AccessoryKind.PirSensor, AccessoryKind.Chime, AccessoryKind.Autotrack, AccessoryKind.Nightvision, AccessoryKind.PrivacyMask;
+/**
+* THE derivation. One crop rectangle, one presence verdict — see D52 for why
+* this repo insists a derived value has exactly one implementation.
+*
+* `undefined` status ⇒ `sleeping`. A device with no slice has made no claim,
+* and the caller decides separately whether it is even battery-operated
+* (`DeviceFeature.BatteryOperated`); this function never answers that
+* question, only what a battery device is doing.
+*/
+function deriveBatteryPresence(input) {
+	const status = input.status;
+	if (!status) return "sleeping";
+	if (status.sleeping !== true) return "awake";
+	const lastContactAt = status.lastContactAt;
+	if (typeof lastContactAt !== "number" || lastContactAt <= 0) return "sleeping";
+	const budget = input.unreachableAfterMs ?? 216e5;
+	return input.nowMs - lastContactAt > budget ? "unreachable" : "sleeping";
+}
+/**
 * WHICH child a container stands for — one definition, for every consumer.
 *
 * A CONTAINER device has no controllable surface of its own: it groups entity
@@ -34734,63 +35099,6 @@ function resolveContainerPrimaryChild(children, overrideEntityId, containerName)
 	const namesake = (c) => containerName !== void 0 && containerName.length > 0 && c.name !== void 0 && c.name.toLowerCase() === containerName.toLowerCase() ? 0 : 1;
 	return [...children].toSorted((a, b) => roleRank(a.role) - roleRank(b.role) || namesake(a) - namesake(b) || rank(a.type) - rank(b.type))[0] ?? null;
 }
-/**
-* Accessory device helpers — shared across drivers.
-*
-* Many vendor-specific drivers register accessory child devices on
-* top of a parent (Reolink: siren / floodlight / PIR / autotrack /
-* chime; ONVIF: relay outputs; future: Tapo Hub child devices). Each
-* driver picks the right `DeviceType` + `DeviceRole` explicitly when
-* spawning, builds a name derived from the parent, and produces a
-* stableId tied to the parent so boot-restore can reconstruct the
-* relationship.
-*
-* Centralised `(kind → DeviceType)` mapping was dropped on purpose:
-* drivers may reasonably disagree on the right type for an accessory
-* (a Reolink PIR exposes a switch on/off + sensitivity, while a hypothetical
-* read-only motion-only sensor might be `DeviceType.Sensor`). Forcing
-* one canonical mapping was over-prescriptive and added a layer of
-* indirection without saving meaningful code at call sites — the
-* driver knows its own hardware best.
-*/
-/**
-* Subset of `DeviceRole` values that drivers register as child
-* accessories of a parent device. Sourced verbatim from `DeviceRole`
-* — `AccessoryKind` is the alias drivers use when building accessory
-* children, so the call site reads as
-* `accessoryStableId(parent, AccessoryKind.Siren)` rather than
-* `accessoryStableId(parent, DeviceRole.Siren)` (which would imply
-* any role works, including non-accessory ones like Doorbell).
-*/
-var AccessoryKind = {
-	Siren: DeviceRole.Siren,
-	Floodlight: DeviceRole.Floodlight,
-	Spotlight: DeviceRole.Spotlight,
-	PirSensor: DeviceRole.PirSensor,
-	Chime: DeviceRole.Chime,
-	Autotrack: DeviceRole.Autotrack,
-	Nightvision: DeviceRole.Nightvision,
-	PrivacyMask: DeviceRole.PrivacyMask
-};
-AccessoryKind.Siren, AccessoryKind.Floodlight, AccessoryKind.Spotlight, AccessoryKind.PirSensor, AccessoryKind.Chime, AccessoryKind.Autotrack, AccessoryKind.Nightvision, AccessoryKind.PrivacyMask;
-/**
-* THE derivation. One crop rectangle, one presence verdict — see D52 for why
-* this repo insists a derived value has exactly one implementation.
-*
-* `undefined` status ⇒ `sleeping`. A device with no slice has made no claim,
-* and the caller decides separately whether it is even battery-operated
-* (`DeviceFeature.BatteryOperated`); this function never answers that
-* question, only what a battery device is doing.
-*/
-function deriveBatteryPresence(input) {
-	const status = input.status;
-	if (!status) return "sleeping";
-	if (status.sleeping !== true) return "awake";
-	const lastContactAt = status.lastContactAt;
-	if (typeof lastContactAt !== "number" || lastContactAt <= 0) return "sleeping";
-	const budget = input.unreachableAfterMs ?? 216e5;
-	return input.nowMs - lastContactAt > budget ? "unreachable" : "sleeping";
-}
 /** Marker written to a declared integration's `info`. */
 var DECLARED_INTEGRATION_FIXED_KEY = "fixed";
 /**
@@ -35303,6 +35611,7 @@ var ALL_CAPABILITY_DEFINITIONS = [
 	storageCapability,
 	storageEvictableCapability,
 	storageMigrationCapability,
+	storageOccupancyCapability,
 	storageProviderCapability,
 	streamBrokerCapability,
 	streamCatalogCapability,
@@ -40269,13 +40578,13 @@ var METHOD_ACCESS_MAP = Object.freeze({
 		addonId: null,
 		access: "view"
 	},
-	"storage.getDefaultLocation": {
+	"storage.list": {
 		capName: "storage",
 		capScope: "system",
 		addonId: null,
 		access: "view"
 	},
-	"storage.list": {
+	"storage.listDrainProgress": {
 		capName: "storage",
 		capScope: "system",
 		addonId: null,
@@ -40425,6 +40734,12 @@ var METHOD_ACCESS_MAP = Object.freeze({
 		addonId: null,
 		access: "view"
 	},
+	"storageOccupancy.getOccupancy": {
+		capName: "storage-occupancy",
+		capScope: "system",
+		addonId: null,
+		access: "view"
+	},
 	"storageProvider.abortUpload": {
 		capName: "storage-provider",
 		capScope: "system",
@@ -44391,6 +44706,12 @@ Object.defineProperty(exports, "LOG_LEVEL_RANK", {
 		return LOG_LEVEL_RANK;
 	}
 });
+Object.defineProperty(exports, "LegacyStorageLocationDefaultSchema", {
+	enumerable: true,
+	get: function() {
+		return LegacyStorageLocationDefaultSchema;
+	}
+});
 Object.defineProperty(exports, "METHOD_ACCESS_MAP", {
 	enumerable: true,
 	get: function() {
@@ -44463,6 +44784,12 @@ Object.defineProperty(exports, "StorageCleanupJobSchema", {
 		return StorageCleanupJobSchema;
 	}
 });
+Object.defineProperty(exports, "StorageLocationModeSchema", {
+	enumerable: true,
+	get: function() {
+		return StorageLocationModeSchema;
+	}
+});
 Object.defineProperty(exports, "StorageLocationTypeSchema", {
 	enumerable: true,
 	get: function() {
@@ -44673,6 +45000,12 @@ Object.defineProperty(exports, "evaluateSensorEdge", {
 		return evaluateSensorEdge;
 	}
 });
+Object.defineProperty(exports, "evictionPolicyOfLocation", {
+	enumerable: true,
+	get: function() {
+		return evictionPolicyOfLocation;
+	}
+});
 Object.defineProperty(exports, "expandCapMethods", {
 	enumerable: true,
 	get: function() {
@@ -44697,6 +45030,12 @@ Object.defineProperty(exports, "foldSnapshotByFunction", {
 		return foldSnapshotByFunction;
 	}
 });
+Object.defineProperty(exports, "gbToBytes", {
+	enumerable: true,
+	get: function() {
+		return gbToBytes;
+	}
+});
 Object.defineProperty(exports, "hydrateSchema", {
 	enumerable: true,
 	get: function() {
@@ -44721,6 +45060,12 @@ Object.defineProperty(exports, "isDeviceConfigCap", {
 		return isDeviceConfigCap;
 	}
 });
+Object.defineProperty(exports, "isLocationEnabled", {
+	enumerable: true,
+	get: function() {
+		return isLocationEnabled;
+	}
+});
 Object.defineProperty(exports, "isObjectInput", {
 	enumerable: true,
 	get: function() {
@@ -44751,6 +45096,12 @@ Object.defineProperty(exports, "kebabToCamel", {
 		return kebabToCamel;
 	}
 });
+Object.defineProperty(exports, "legacyModeOf", {
+	enumerable: true,
+	get: function() {
+		return legacyModeOf;
+	}
+});
 Object.defineProperty(exports, "lifecycleJobSchema", {
 	enumerable: true,
 	get: function() {
@@ -44781,12 +45132,30 @@ Object.defineProperty(exports, "looseSchema", {
 		return looseSchema;
 	}
 });
+Object.defineProperty(exports, "mayReadLocation", {
+	enumerable: true,
+	get: function() {
+		return mayReadLocation;
+	}
+});
+Object.defineProperty(exports, "mayWriteToLocation", {
+	enumerable: true,
+	get: function() {
+		return mayWriteToLocation;
+	}
+});
 Object.defineProperty(exports, "metricsProviderCapability", {
 	enumerable: true,
 	get: function() {
 		return metricsProviderCapability;
 	}
 });
+Object.defineProperty(exports, "modeMayWrite", {
+	enumerable: true,
+	get: function() {
+		return modeMayWrite;
+	}
+});
 Object.defineProperty(exports, "nodePin", {
 	enumerable: true,
 	get: function() {
@@ -44865,6 +45234,12 @@ Object.defineProperty(exports, "resolveContainerPrimaryChild", {
 		return resolveContainerPrimaryChild;
 	}
 });
+Object.defineProperty(exports, "resolveLocationMode", {
+	enumerable: true,
+	get: function() {
+		return resolveLocationMode;
+	}
+});
 Object.defineProperty(exports, "resolveMethodAuth", {
 	enumerable: true,
 	get: function() {
@@ -44931,6 +45306,12 @@ Object.defineProperty(exports, "storageMigrationCapability", {
 		return storageMigrationCapability;
 	}
 });
+Object.defineProperty(exports, "storageOccupancyCapability", {
+	enumerable: true,
+	get: function() {
+		return storageOccupancyCapability;
+	}
+});
 Object.defineProperty(exports, "storageProviderCapability", {
 	enumerable: true,
 	get: function() {
@@ -44961,3 +45342,9 @@ Object.defineProperty(exports, "vectorStoreCapability", {
 		return vectorStoreCapability;
 	}
 });
+Object.defineProperty(exports, "withLocationMode", {
+	enumerable: true,
+	get: function() {
+		return withLocationMode;
+	}
+});