@camstack/types 1.2.161 → 1.2.162

package/dist/interfaces/storage-location.d.ts

@@ -30,8 +30,11 @@ export type StorageLocationType = z.infer<typeof StorageLocationTypeSchema>;
  * `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
@@ -45,7 +48,6 @@ export declare const StorageLocationSchema: z.ZodObject<{
     providerId: z.ZodString;
     config: z.ZodRecord<z.ZodString, z.ZodUnknown>;
     nodeId: z.ZodOptional<z.ZodString>;
-    isDefault: z.ZodDefault<z.ZodBoolean>;
     isSystem: z.ZodDefault<z.ZodBoolean>;
     enabled: z.ZodOptional<z.ZodBoolean>;
     capacity: z.ZodOptional<z.ZodNullable<z.ZodObject<{
@@ -56,10 +58,35 @@ export declare const StorageLocationSchema: z.ZodObject<{
     updatedAt: z.ZodNumber;
 }, z.core.$strip>;
 export type StorageLocation = z.infer<typeof StorageLocationSchema>;
+/**
+ * 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.
+ */
+export declare const LegacyStorageLocationDefaultSchema: z.ZodObject<{
+    isDefault: z.ZodOptional<z.ZodBoolean>;
+}, z.core.$strip>;
+export type LegacyStorageLocationDefault = z.infer<typeof LegacyStorageLocationDefaultSchema>;
+/**
+ * Is this location a write target? THE one place that decides what an absent
+ * `enabled` means on a persisted row — legacy rows predate the flag and were
+ * active, so absence is enabled. Every consumer asks here rather than spelling
+ * `enabled !== false` again, so the tri-state has exactly one interpretation.
+ */
+export declare function isLocationEnabled(location: {
+    readonly enabled?: boolean;
+}): boolean;
 /**
  * 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.

package/package.json

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