@wildo-ai/saas-models 1.1.3 → 1.1.5

package/dist/esm/features/scope-features.shared.schemas.d.ts

@@ -41,4 +41,57 @@ export declare const ScopeFeaturesWithOverridesSchema: z.ZodObject<{
     }, z.core.$strip>>>;
 }, z.core.$strip>;
 export type ScopeFeaturesWithOverrides = z.infer<typeof ScopeFeaturesWithOverridesSchema>;
+/**
+ * The PERSISTED shape of a scope's feature ledger — the shared payload above plus the two things a
+ * row needs to exist: its own id, and the scope it belongs to.
+ *
+ * ## Why these exist rather than the bare payload being the main schema
+ *
+ * `ScopeFeaturesWithOverridesSchema` is shared across scopes, so it can model neither
+ * `organizationId` nor `applicationId` — and until 2026-09-19 both feature resources used it
+ * DIRECTLY as their `mainSchema`. The column was contributed by the relationship and the table had
+ * it, but the schema did not, with two consequences that only look unrelated:
+ *
+ *   - **No business-key identity.** `resolveBusinessKeyFieldNames` walks the SCHEMA, so every
+ *     business-key repository helper refused these resources outright — "Schema declares no
+ *     business-key identity". That is what made the ledger unseedable by any mode, and the
+ *     Administration → Entitlements pane read a row that nothing could ever create.
+ *   - **The FK was invisible to every schema-driven mechanism**, which is the same class of defect
+ *     as the `appId` misspelling fixed the day before: the column exists, and nothing that reads
+ *     declarations can see it.
+ *
+ * The polymorphic config singletons (SSO / SCIM / SIEM / webhooks) never had this problem because
+ * `createPolymorphicResourceConfigurations` contributes the scope FK to each variant's schema. These
+ * two are built by the plain factory, so they declare it themselves — exactly as
+ * `ApplicationMetadataSchema` does, and for the same stated reason.
+ *
+ * `.isBusinessKey().isUnique()` says the same thing twice on purpose: the marker gives the seeding
+ * and upsert helpers an identity to address the row by, and the unique index carries the 1:1 down to
+ * the database so two concurrent creates cannot leave a scope with two ledgers.
+ */
+export declare const ApplicationFeaturesSchema: z.ZodObject<{
+    features: import("@wildo-ai/zod-decorators").DecoratedPrimitiveZodType<import("@wildo-ai/zod-decorators").DecoratedPrimitiveZodType<z.ZodDefault<z.ZodArray<z.ZodUnion<readonly [z.ZodEnum<typeof CoreFeature>, z.ZodString]>>>>>;
+    limits: import("@wildo-ai/zod-decorators").DecoratedPrimitiveZodType<import("@wildo-ai/zod-decorators").DecoratedPrimitiveZodType<z.ZodDefault<z.ZodRecord<z.ZodString, z.ZodNumber>>>>;
+    manualOverrides: import("@wildo-ai/zod-decorators").DecoratedPrimitiveZodType<z.ZodDefault<z.ZodObject<{
+        addedFeatures: z.ZodDefault<z.ZodArray<z.ZodString>>;
+        removedFeatures: z.ZodDefault<z.ZodArray<z.ZodString>>;
+        limitOverrides: z.ZodDefault<z.ZodRecord<z.ZodString, z.ZodNumber>>;
+    }, z.core.$strip>>>;
+    _id: import("@wildo-ai/zod-decorators").DecoratedPrimitiveZodType<import("@wildo-ai/zod-decorators").DecoratedPrimitiveZodType<z.ZodString>>;
+    applicationId: import("@wildo-ai/zod-decorators").DecoratedPrimitiveZodType<import("@wildo-ai/zod-decorators").DecoratedPrimitiveZodType<import("@wildo-ai/zod-decorators").DecoratedPrimitiveZodType<import("@wildo-ai/zod-decorators").DecoratedPrimitiveZodType<import("@wildo-ai/zod-decorators").DecoratedPrimitiveZodType<import("@wildo-ai/zod-decorators").DecoratedPrimitiveZodType<z.ZodString>>>>>>;
+}, z.core.$strip>;
+export type ApplicationFeatures = z.infer<typeof ApplicationFeaturesSchema>;
+/** The ORGANIZATION twin — same shape, same reasoning, one scope down. */
+export declare const OrganizationFeaturesSchema: z.ZodObject<{
+    features: import("@wildo-ai/zod-decorators").DecoratedPrimitiveZodType<import("@wildo-ai/zod-decorators").DecoratedPrimitiveZodType<z.ZodDefault<z.ZodArray<z.ZodUnion<readonly [z.ZodEnum<typeof CoreFeature>, z.ZodString]>>>>>;
+    limits: import("@wildo-ai/zod-decorators").DecoratedPrimitiveZodType<import("@wildo-ai/zod-decorators").DecoratedPrimitiveZodType<z.ZodDefault<z.ZodRecord<z.ZodString, z.ZodNumber>>>>;
+    manualOverrides: import("@wildo-ai/zod-decorators").DecoratedPrimitiveZodType<z.ZodDefault<z.ZodObject<{
+        addedFeatures: z.ZodDefault<z.ZodArray<z.ZodString>>;
+        removedFeatures: z.ZodDefault<z.ZodArray<z.ZodString>>;
+        limitOverrides: z.ZodDefault<z.ZodRecord<z.ZodString, z.ZodNumber>>;
+    }, z.core.$strip>>>;
+    _id: import("@wildo-ai/zod-decorators").DecoratedPrimitiveZodType<import("@wildo-ai/zod-decorators").DecoratedPrimitiveZodType<z.ZodString>>;
+    organizationId: import("@wildo-ai/zod-decorators").DecoratedPrimitiveZodType<import("@wildo-ai/zod-decorators").DecoratedPrimitiveZodType<import("@wildo-ai/zod-decorators").DecoratedPrimitiveZodType<import("@wildo-ai/zod-decorators").DecoratedPrimitiveZodType<import("@wildo-ai/zod-decorators").DecoratedPrimitiveZodType<import("@wildo-ai/zod-decorators").DecoratedPrimitiveZodType<z.ZodString>>>>>>;
+}, z.core.$strip>;
+export type OrganizationFeatures = z.infer<typeof OrganizationFeaturesSchema>;
 //# sourceMappingURL=scope-features.shared.schemas.d.ts.map

package/dist/esm/features/scope-features.shared.schemas.d.ts.map

@@ -1 +1 @@
-{"version":3,"file":"scope-features.shared.schemas.d.ts","sourceRoot":"","sources":["../../../../src/features/scope-features.shared.schemas.ts"],"names":[],"mappings":"AAAA;;;;;;;;;;;GAWG;AAEH,OAAO,EAAE,CAAC,EAAE,MAAM,KAAK,CAAC;AACxB,OAAO,EAAE,WAAW,EAAE,MAAM,uDAAuD,CAAC;AAMpF;;;;GAIG;AACH,eAAO,MAAM,mBAAmB;;;iBAY9B,CAAC;AACH,MAAM,MAAM,aAAa,GAAG,CAAC,CAAC,KAAK,CAAC,OAAO,mBAAmB,CAAC,CAAC;AAMhE;;;;;;;;GAQG;AACH,eAAO,MAAM,gCAAgC;;;;;;;;iBAe3C,CAAC;AACH,MAAM,MAAM,0BAA0B,GAAG,CAAC,CAAC,KAAK,CAAC,OAAO,gCAAgC,CAAC,CAAC"}
+{"version":3,"file":"scope-features.shared.schemas.d.ts","sourceRoot":"","sources":["../../../../src/features/scope-features.shared.schemas.ts"],"names":[],"mappings":"AAAA;;;;;;;;;;;GAWG;AAEH,OAAO,EAAE,CAAC,EAAE,MAAM,KAAK,CAAC;AACxB,OAAO,EAAE,WAAW,EAAE,MAAM,uDAAuD,CAAC;AAMpF;;;;GAIG;AACH,eAAO,MAAM,mBAAmB;;;iBAY9B,CAAC;AACH,MAAM,MAAM,aAAa,GAAG,CAAC,CAAC,KAAK,CAAC,OAAO,mBAAmB,CAAC,CAAC;AAMhE;;;;;;;;GAQG;AACH,eAAO,MAAM,gCAAgC;;;;;;;;iBAe3C,CAAC;AACH,MAAM,MAAM,0BAA0B,GAAG,CAAC,CAAC,KAAK,CAAC,OAAO,gCAAgC,CAAC,CAAC;AAE1F;;;;;;;;;;;;;;;;;;;;;;;;;;;GA2BG;AACH,eAAO,MAAM,yBAAyB;;;;;;;;;;iBAGpC,CAAC;AACH,MAAM,MAAM,mBAAmB,GAAG,CAAC,CAAC,KAAK,CAAC,OAAO,yBAAyB,CAAC,CAAC;AAE5E,0EAA0E;AAC1E,eAAO,MAAM,0BAA0B;;;;;;;;;;iBAGrC,CAAC;AACH,MAAM,MAAM,oBAAoB,GAAG,CAAC,CAAC,KAAK,CAAC,OAAO,0BAA0B,CAAC,CAAC"}

package/dist/esm/features/scope-features.shared.schemas.js

@@ -61,4 +61,41 @@ export const ScopeFeaturesWithOverridesSchema = ScopeFeaturesSchema.extend({
         limitOverrides: z.record(z.string(), z.number()).default({}),
     }).default({ addedFeatures: [], removedFeatures: [], limitOverrides: {} }).isAuditEvidence(),
 });
+/**
+ * The PERSISTED shape of a scope's feature ledger — the shared payload above plus the two things a
+ * row needs to exist: its own id, and the scope it belongs to.
+ *
+ * ## Why these exist rather than the bare payload being the main schema
+ *
+ * `ScopeFeaturesWithOverridesSchema` is shared across scopes, so it can model neither
+ * `organizationId` nor `applicationId` — and until 2026-09-19 both feature resources used it
+ * DIRECTLY as their `mainSchema`. The column was contributed by the relationship and the table had
+ * it, but the schema did not, with two consequences that only look unrelated:
+ *
+ *   - **No business-key identity.** `resolveBusinessKeyFieldNames` walks the SCHEMA, so every
+ *     business-key repository helper refused these resources outright — "Schema declares no
+ *     business-key identity". That is what made the ledger unseedable by any mode, and the
+ *     Administration → Entitlements pane read a row that nothing could ever create.
+ *   - **The FK was invisible to every schema-driven mechanism**, which is the same class of defect
+ *     as the `appId` misspelling fixed the day before: the column exists, and nothing that reads
+ *     declarations can see it.
+ *
+ * The polymorphic config singletons (SSO / SCIM / SIEM / webhooks) never had this problem because
+ * `createPolymorphicResourceConfigurations` contributes the scope FK to each variant's schema. These
+ * two are built by the plain factory, so they declare it themselves — exactly as
+ * `ApplicationMetadataSchema` does, and for the same stated reason.
+ *
+ * `.isBusinessKey().isUnique()` says the same thing twice on purpose: the marker gives the seeding
+ * and upsert helpers an identity to address the row by, and the unique index carries the 1:1 down to
+ * the database so two concurrent creates cannot leave a scope with two ledgers.
+ */
+export const ApplicationFeaturesSchema = ScopeFeaturesWithOverridesSchema.extend({
+    _id: z.string().isPrimaryKey().isSummaryField(),
+    applicationId: z.string().isDBIndexed().isForeignKey().isBusinessKey().isUnique().isSummaryField().excludeFromUpdate(),
+});
+/** The ORGANIZATION twin — same shape, same reasoning, one scope down. */
+export const OrganizationFeaturesSchema = ScopeFeaturesWithOverridesSchema.extend({
+    _id: z.string().isPrimaryKey().isSummaryField(),
+    organizationId: z.string().isDBIndexed().isForeignKey().isBusinessKey().isUnique().isSummaryField().excludeFromUpdate(),
+});
 //# sourceMappingURL=scope-features.shared.schemas.js.map

package/dist/esm/features/scope-features.shared.schemas.js.map

@@ -1 +1 @@
-{"version":3,"file":"scope-features.shared.schemas.js","sourceRoot":"","sources":["../../../../src/features/scope-features.shared.schemas.ts"],"names":[],"mappings":"AAAA;;;;;;;;;;;GAWG;AAEH,OAAO,EAAE,CAAC,EAAE,MAAM,KAAK,CAAC;AACxB,OAAO,EAAE,WAAW,EAAE,MAAM,uDAAuD,CAAC;AAEpF,wDAAwD;AACxD,wBAAwB;AACxB,wDAAwD;AAExD;;;;GAIG;AACH,MAAM,CAAC,MAAM,mBAAmB,GAAG,CAAC,CAAC,MAAM,CAAC;IAC1C,oDAAoD;IACpD,+FAA+F;IAC/F,0FAA0F;IAC1F,8FAA8F;IAC9F,0FAA0F;IAC1F,sCAAsC;IACtC,8FAA8F;IAC9F,6CAA6C;IAC7C,QAAQ,EAAE,CAAC,CAAC,KAAK,CAAC,CAAC,CAAC,KAAK,CAAC,CAAC,CAAC,CAAC,IAAI,CAAC,WAAW,CAAC,EAAE,CAAC,CAAC,MAAM,EAAE,CAAC,GAAG,CAAC,CAAC,CAAC,CAAC,CAAC,CAAC,CAAC,OAAO,CAAC,EAAE,CAAC,CAAC,cAAc,EAAE,CAAC,eAAe,EAAE;IACnH,gGAAgG;IAChG,MAAM,EAAE,CAAC,CAAC,MAAM,CAAC,CAAC,CAAC,MAAM,EAAE,EAAE,CAAC,CAAC,MAAM,EAAE,CAAC,CAAC,OAAO,CAAC,EAAE,CAAC,CAAC,cAAc,EAAE,CAAC,eAAe,EAAE;CACxF,CAAC,CAAC;AAGH,wDAAwD;AACxD,uCAAuC;AACvC,wDAAwD;AAExD;;;;;;;;GAQG;AACH,MAAM,CAAC,MAAM,gCAAgC,GAAG,mBAAmB,CAAC,MAAM,CAAC;IACzE;;;;;;;;OAQG;IACH,eAAe,EAAE,CAAC,CAAC,MAAM,CAAC;QACxB,aAAa,EAAE,CAAC,CAAC,KAAK,CAAC,CAAC,CAAC,MAAM,EAAE,CAAC,CAAC,OAAO,CAAC,EAAE,CAAC;QAC9C,eAAe,EAAE,CAAC,CAAC,KAAK,CAAC,CAAC,CAAC,MAAM,EAAE,CAAC,CAAC,OAAO,CAAC,EAAE,CAAC;QAChD,cAAc,EAAE,CAAC,CAAC,MAAM,CAAC,CAAC,CAAC,MAAM,EAAE,EAAE,CAAC,CAAC,MAAM,EAAE,CAAC,CAAC,OAAO,CAAC,EAAE,CAAC;KAC7D,CAAC,CAAC,OAAO,CAAC,EAAE,aAAa,EAAE,EAAE,EAAE,eAAe,EAAE,EAAE,EAAE,cAAc,EAAE,EAAE,EAAE,CAAC,CAAC,eAAe,EAAE;CAC7F,CAAC,CAAC","sourcesContent":["/**\n * Scope Features State Schemas\n * \n * Scope-agnostic feature state: what features are enabled and what limits are set\n * for any scope entity (org, user).\n * \n * Replaces the org-only OrganizationPlanFeaturesSchema with a universal shape.\n * Used by:\n * - Feature profiles in FeatureConfiguration\n * - Resource storage (ORGANIZATION_FEATURES, USER_FEATURES)\n * - Resolution service output\n */\n\nimport { z } from 'zod';\nimport { CoreFeature } from '../organizations/organization-features.shared.schemas';\n\n// =====================================================\n// Scope Features Schema\n// =====================================================\n\n/**\n * Feature state for any scope entity (org, user).\n * Same simple shape: boolean features (present = enabled) + numeric limits.\n * Replaces the org-only OrganizationPlanFeaturesSchema.\n */\nexport const ScopeFeaturesSchema = z.object({\n  /** Boolean features - present in array = enabled */\n  // `.isAuditEvidence()` — the resolved ENTITLEMENT set. Features gate real capability (and some\n  // gate security surfaces, e.g. DIRECTORY_PROVISIONING), so \"features changed\" without the\n  // before/after sets cannot answer what a tenant was entitled to on a given day — the question\n  // both an auditor and a billing dispute actually ask. Feature keys and numeric limits are\n  // configuration, never personal data.\n  // assurance-control: WILDO.ACCESS.PRIVILEGE_EVIDENCE — the resolved entitlement set is what a\n  // tenant was permitted to do on a given day.\n  features: z.array(z.union([z.enum(CoreFeature), z.string().min(1)])).default([]).isSummaryField().isAuditEvidence(),\n  /** Numeric limits - key = feature identifier, value = limit (FEATURES_UNLIMITED = unlimited) */\n  limits: z.record(z.string(), z.number()).default({}).isSummaryField().isAuditEvidence(),\n});\nexport type ScopeFeatures = z.infer<typeof ScopeFeaturesSchema>;\n\n// =====================================================\n// Scope Features With Overrides Schema\n// =====================================================\n\n/**\n * Extension on the scope features resource (not a separate resource).\n * Stores admin manual overrides that survive billing changes.\n * \n * Used as the `mainSchema` for ORGANIZATION_FEATURES, USER_FEATURES resources.\n * The resolution service computes `features` and `limits` (the effective state) from:\n *   defaults + config profile + billing-derived + manual overrides.\n * The `manualOverrides` field stores admin changes that survive subscription changes.\n */\nexport const ScopeFeaturesWithOverridesSchema = ScopeFeaturesSchema.extend({\n  /**\n   * Manual overrides by admin (persisted across billing changes).\n   *\n   * `.isAuditEvidence()` — an admin GRANTING a capability outside the billing plan is precisely the\n   * discretionary act a reviewer looks for, and it survives billing changes, so it is the durable\n   * record of who was given what by hand. No descendant is `.isBackendOnly()`, so marking the\n   * container is safe.\n   * assurance-control: WILDO.ACCESS.PRIVILEGE_EVIDENCE — a discretionary grant outside the plan.\n   */\n  manualOverrides: z.object({\n    addedFeatures: z.array(z.string()).default([]),\n    removedFeatures: z.array(z.string()).default([]),\n    limitOverrides: z.record(z.string(), z.number()).default({}),\n  }).default({ addedFeatures: [], removedFeatures: [], limitOverrides: {} }).isAuditEvidence(),\n});\nexport type ScopeFeaturesWithOverrides = z.infer<typeof ScopeFeaturesWithOverridesSchema>;\n"]}
+{"version":3,"file":"scope-features.shared.schemas.js","sourceRoot":"","sources":["../../../../src/features/scope-features.shared.schemas.ts"],"names":[],"mappings":"AAAA;;;;;;;;;;;GAWG;AAEH,OAAO,EAAE,CAAC,EAAE,MAAM,KAAK,CAAC;AACxB,OAAO,EAAE,WAAW,EAAE,MAAM,uDAAuD,CAAC;AAEpF,wDAAwD;AACxD,wBAAwB;AACxB,wDAAwD;AAExD;;;;GAIG;AACH,MAAM,CAAC,MAAM,mBAAmB,GAAG,CAAC,CAAC,MAAM,CAAC;IAC1C,oDAAoD;IACpD,+FAA+F;IAC/F,0FAA0F;IAC1F,8FAA8F;IAC9F,0FAA0F;IAC1F,sCAAsC;IACtC,8FAA8F;IAC9F,6CAA6C;IAC7C,QAAQ,EAAE,CAAC,CAAC,KAAK,CAAC,CAAC,CAAC,KAAK,CAAC,CAAC,CAAC,CAAC,IAAI,CAAC,WAAW,CAAC,EAAE,CAAC,CAAC,MAAM,EAAE,CAAC,GAAG,CAAC,CAAC,CAAC,CAAC,CAAC,CAAC,CAAC,OAAO,CAAC,EAAE,CAAC,CAAC,cAAc,EAAE,CAAC,eAAe,EAAE;IACnH,gGAAgG;IAChG,MAAM,EAAE,CAAC,CAAC,MAAM,CAAC,CAAC,CAAC,MAAM,EAAE,EAAE,CAAC,CAAC,MAAM,EAAE,CAAC,CAAC,OAAO,CAAC,EAAE,CAAC,CAAC,cAAc,EAAE,CAAC,eAAe,EAAE;CACxF,CAAC,CAAC;AAGH,wDAAwD;AACxD,uCAAuC;AACvC,wDAAwD;AAExD;;;;;;;;GAQG;AACH,MAAM,CAAC,MAAM,gCAAgC,GAAG,mBAAmB,CAAC,MAAM,CAAC;IACzE;;;;;;;;OAQG;IACH,eAAe,EAAE,CAAC,CAAC,MAAM,CAAC;QACxB,aAAa,EAAE,CAAC,CAAC,KAAK,CAAC,CAAC,CAAC,MAAM,EAAE,CAAC,CAAC,OAAO,CAAC,EAAE,CAAC;QAC9C,eAAe,EAAE,CAAC,CAAC,KAAK,CAAC,CAAC,CAAC,MAAM,EAAE,CAAC,CAAC,OAAO,CAAC,EAAE,CAAC;QAChD,cAAc,EAAE,CAAC,CAAC,MAAM,CAAC,CAAC,CAAC,MAAM,EAAE,EAAE,CAAC,CAAC,MAAM,EAAE,CAAC,CAAC,OAAO,CAAC,EAAE,CAAC;KAC7D,CAAC,CAAC,OAAO,CAAC,EAAE,aAAa,EAAE,EAAE,EAAE,eAAe,EAAE,EAAE,EAAE,cAAc,EAAE,EAAE,EAAE,CAAC,CAAC,eAAe,EAAE;CAC7F,CAAC,CAAC;AAGH;;;;;;;;;;;;;;;;;;;;;;;;;;;GA2BG;AACH,MAAM,CAAC,MAAM,yBAAyB,GAAG,gCAAgC,CAAC,MAAM,CAAC;IAC/E,GAAG,EAAE,CAAC,CAAC,MAAM,EAAE,CAAC,YAAY,EAAE,CAAC,cAAc,EAAE;IAC/C,aAAa,EAAE,CAAC,CAAC,MAAM,EAAE,CAAC,WAAW,EAAE,CAAC,YAAY,EAAE,CAAC,aAAa,EAAE,CAAC,QAAQ,EAAE,CAAC,cAAc,EAAE,CAAC,iBAAiB,EAAE;CACvH,CAAC,CAAC;AAGH,0EAA0E;AAC1E,MAAM,CAAC,MAAM,0BAA0B,GAAG,gCAAgC,CAAC,MAAM,CAAC;IAChF,GAAG,EAAE,CAAC,CAAC,MAAM,EAAE,CAAC,YAAY,EAAE,CAAC,cAAc,EAAE;IAC/C,cAAc,EAAE,CAAC,CAAC,MAAM,EAAE,CAAC,WAAW,EAAE,CAAC,YAAY,EAAE,CAAC,aAAa,EAAE,CAAC,QAAQ,EAAE,CAAC,cAAc,EAAE,CAAC,iBAAiB,EAAE;CACxH,CAAC,CAAC","sourcesContent":["/**\n * Scope Features State Schemas\n * \n * Scope-agnostic feature state: what features are enabled and what limits are set\n * for any scope entity (org, user).\n * \n * Replaces the org-only OrganizationPlanFeaturesSchema with a universal shape.\n * Used by:\n * - Feature profiles in FeatureConfiguration\n * - Resource storage (ORGANIZATION_FEATURES, USER_FEATURES)\n * - Resolution service output\n */\n\nimport { z } from 'zod';\nimport { CoreFeature } from '../organizations/organization-features.shared.schemas';\n\n// =====================================================\n// Scope Features Schema\n// =====================================================\n\n/**\n * Feature state for any scope entity (org, user).\n * Same simple shape: boolean features (present = enabled) + numeric limits.\n * Replaces the org-only OrganizationPlanFeaturesSchema.\n */\nexport const ScopeFeaturesSchema = z.object({\n  /** Boolean features - present in array = enabled */\n  // `.isAuditEvidence()` — the resolved ENTITLEMENT set. Features gate real capability (and some\n  // gate security surfaces, e.g. DIRECTORY_PROVISIONING), so \"features changed\" without the\n  // before/after sets cannot answer what a tenant was entitled to on a given day — the question\n  // both an auditor and a billing dispute actually ask. Feature keys and numeric limits are\n  // configuration, never personal data.\n  // assurance-control: WILDO.ACCESS.PRIVILEGE_EVIDENCE — the resolved entitlement set is what a\n  // tenant was permitted to do on a given day.\n  features: z.array(z.union([z.enum(CoreFeature), z.string().min(1)])).default([]).isSummaryField().isAuditEvidence(),\n  /** Numeric limits - key = feature identifier, value = limit (FEATURES_UNLIMITED = unlimited) */\n  limits: z.record(z.string(), z.number()).default({}).isSummaryField().isAuditEvidence(),\n});\nexport type ScopeFeatures = z.infer<typeof ScopeFeaturesSchema>;\n\n// =====================================================\n// Scope Features With Overrides Schema\n// =====================================================\n\n/**\n * Extension on the scope features resource (not a separate resource).\n * Stores admin manual overrides that survive billing changes.\n * \n * Used as the `mainSchema` for ORGANIZATION_FEATURES, USER_FEATURES resources.\n * The resolution service computes `features` and `limits` (the effective state) from:\n *   defaults + config profile + billing-derived + manual overrides.\n * The `manualOverrides` field stores admin changes that survive subscription changes.\n */\nexport const ScopeFeaturesWithOverridesSchema = ScopeFeaturesSchema.extend({\n  /**\n   * Manual overrides by admin (persisted across billing changes).\n   *\n   * `.isAuditEvidence()` — an admin GRANTING a capability outside the billing plan is precisely the\n   * discretionary act a reviewer looks for, and it survives billing changes, so it is the durable\n   * record of who was given what by hand. No descendant is `.isBackendOnly()`, so marking the\n   * container is safe.\n   * assurance-control: WILDO.ACCESS.PRIVILEGE_EVIDENCE — a discretionary grant outside the plan.\n   */\n  manualOverrides: z.object({\n    addedFeatures: z.array(z.string()).default([]),\n    removedFeatures: z.array(z.string()).default([]),\n    limitOverrides: z.record(z.string(), z.number()).default({}),\n  }).default({ addedFeatures: [], removedFeatures: [], limitOverrides: {} }).isAuditEvidence(),\n});\nexport type ScopeFeaturesWithOverrides = z.infer<typeof ScopeFeaturesWithOverridesSchema>;\n\n/**\n * The PERSISTED shape of a scope's feature ledger — the shared payload above plus the two things a\n * row needs to exist: its own id, and the scope it belongs to.\n *\n * ## Why these exist rather than the bare payload being the main schema\n *\n * `ScopeFeaturesWithOverridesSchema` is shared across scopes, so it can model neither\n * `organizationId` nor `applicationId` — and until 2026-09-19 both feature resources used it\n * DIRECTLY as their `mainSchema`. The column was contributed by the relationship and the table had\n * it, but the schema did not, with two consequences that only look unrelated:\n *\n *   - **No business-key identity.** `resolveBusinessKeyFieldNames` walks the SCHEMA, so every\n *     business-key repository helper refused these resources outright — \"Schema declares no\n *     business-key identity\". That is what made the ledger unseedable by any mode, and the\n *     Administration → Entitlements pane read a row that nothing could ever create.\n *   - **The FK was invisible to every schema-driven mechanism**, which is the same class of defect\n *     as the `appId` misspelling fixed the day before: the column exists, and nothing that reads\n *     declarations can see it.\n *\n * The polymorphic config singletons (SSO / SCIM / SIEM / webhooks) never had this problem because\n * `createPolymorphicResourceConfigurations` contributes the scope FK to each variant's schema. These\n * two are built by the plain factory, so they declare it themselves — exactly as\n * `ApplicationMetadataSchema` does, and for the same stated reason.\n *\n * `.isBusinessKey().isUnique()` says the same thing twice on purpose: the marker gives the seeding\n * and upsert helpers an identity to address the row by, and the unique index carries the 1:1 down to\n * the database so two concurrent creates cannot leave a scope with two ledgers.\n */\nexport const ApplicationFeaturesSchema = ScopeFeaturesWithOverridesSchema.extend({\n  _id: z.string().isPrimaryKey().isSummaryField(),\n  applicationId: z.string().isDBIndexed().isForeignKey().isBusinessKey().isUnique().isSummaryField().excludeFromUpdate(),\n});\nexport type ApplicationFeatures = z.infer<typeof ApplicationFeaturesSchema>;\n\n/** The ORGANIZATION twin — same shape, same reasoning, one scope down. */\nexport const OrganizationFeaturesSchema = ScopeFeaturesWithOverridesSchema.extend({\n  _id: z.string().isPrimaryKey().isSummaryField(),\n  organizationId: z.string().isDBIndexed().isForeignKey().isBusinessKey().isUnique().isSummaryField().excludeFromUpdate(),\n});\nexport type OrganizationFeatures = z.infer<typeof OrganizationFeaturesSchema>;\n"]}

package/dist/esm/features/user-features.shared.resources-config.schemas.d.ts

@@ -7,7 +7,7 @@
  */
 import { CoreResourceOperation } from '../resources/resources.shared.core.definitions';
 import { ResourceRelationship } from '../resources/resources.shared.schemas';
-type UserFeaturesCoreOperations = CoreResourceOperation.CREATE | CoreResourceOperation.READ | CoreResourceOperation.LIST | CoreResourceOperation.UPDATE_MANY | CoreResourceOperation.SEARCH | CoreResourceOperation.UPDATE | CoreResourceOperation.DELETE;
+type UserFeaturesCoreOperations = CoreResourceOperation.CREATE | CoreResourceOperation.READ | CoreResourceOperation.SEARCH | CoreResourceOperation.UPDATE | CoreResourceOperation.DELETE;
 export declare const userFeaturesResourceConfiguration_InitializationFactory: (resourcesRelationships: ResourceRelationship[]) => import("..").ResourceConfiguration<Record<string, never>, UserFeaturesCoreOperations, import("zod").ZodObject<{
     features: import("@wildo-ai/zod-decorators").DecoratedPrimitiveZodType<import("@wildo-ai/zod-decorators").DecoratedPrimitiveZodType<import("zod").ZodDefault<import("zod").ZodArray<import("zod").ZodUnion<readonly [import("zod").ZodEnum<typeof import("..").CoreFeature>, import("zod").ZodString]>>>>>;
     limits: import("@wildo-ai/zod-decorators").DecoratedPrimitiveZodType<import("@wildo-ai/zod-decorators").DecoratedPrimitiveZodType<import("zod").ZodDefault<import("zod").ZodRecord<import("zod").ZodString, import("zod").ZodNumber>>>>;

package/dist/esm/features/user-features.shared.resources-config.schemas.d.ts.map

@@ -1 +1 @@
-{"version":3,"file":"user-features.shared.resources-config.schemas.d.ts","sourceRoot":"","sources":["../../../../src/features/user-features.shared.resources-config.schemas.ts"],"names":[],"mappings":"AAAA;;;;;;GAMG;AAKH,OAAO,EAAE,qBAAqB,EAAE,MAAM,gDAAgD,CAAC;AACvF,OAAO,EAA8B,oBAAoB,EAAE,MAAM,uCAAuC,CAAC;AAQzG,KAAK,0BAA0B,GAC3B,qBAAqB,CAAC,MAAM,GAC5B,qBAAqB,CAAC,IAAI,GAC1B,qBAAqB,CAAC,IAAI,GAC1B,qBAAqB,CAAC,WAAW,GACjC,qBAAqB,CAAC,MAAM,GAC5B,qBAAqB,CAAC,MAAM,GAC5B,qBAAqB,CAAC,MAAM,CAAC;AAEjC,eAAO,MAAM,uDAAuD,GAAI,wBAAwB,oBAAoB,EAAE;;;;;;;;iCA+IpH,CAAC"}
+{"version":3,"file":"user-features.shared.resources-config.schemas.d.ts","sourceRoot":"","sources":["../../../../src/features/user-features.shared.resources-config.schemas.ts"],"names":[],"mappings":"AAAA;;;;;;GAMG;AAIH,OAAO,EAAE,qBAAqB,EAAE,MAAM,gDAAgD,CAAC;AACvF,OAAO,EAA8B,oBAAoB,EAAE,MAAM,uCAAuC,CAAC;AAQzG,KAAK,0BAA0B,GAC3B,qBAAqB,CAAC,MAAM,GAC5B,qBAAqB,CAAC,IAAI,GAC1B,qBAAqB,CAAC,MAAM,GAC5B,qBAAqB,CAAC,MAAM,GAC5B,qBAAqB,CAAC,MAAM,CAAC;AAEjC,eAAO,MAAM,uDAAuD,GAAI,wBAAwB,oBAAoB,EAAE;;;;;;;;iCAyIpH,CAAC"}

package/dist/esm/features/user-features.shared.resources-config.schemas.js

@@ -6,7 +6,6 @@
  * Uses ScopeFeaturesWithOverridesSchema as mainSchema (same pattern as org features).
  */
 import { ScopeFeaturesWithOverridesSchema } from './scope-features.shared.schemas.js';
-import { ErasureRetentionMode, ResourceDataSubjectKind } from '../compliance/privacy/impersonalization.shared.schemas.js';
 import { CoreResourceOperation } from '../resources/resources.shared.core.definitions.js';
 import { ResourceOperationRiskLevel } from '../resources/resources.shared.schemas.js';
 import { CoreResourceType, coreResourceShared_FieldIdentifier } from '../resources/resources.shared.core.definitions.js';
@@ -24,67 +23,54 @@ export const userFeaturesResourceConfiguration_InitializationFactory = (resource
     /** Subject-export disclosure. The subject's own data. Secrets and backend-only values are withheld by the export's security floor regardless of this grant. */
     systemAccessPolicy: { exportSubject: ResourceSystemAccessMode.ALLOWED },
     portabilityPolicy: { defaultProvenance: DataPortabilityProvenance.DERIVED },
-    /**
-     * Subject erasure RETAINS this row and scrubs nothing, because there is nothing here to scrub.
+    /*
+     * NO `retentionPolicy`, so a subject erasure DESTROYS this row (#1569, decided by Paul 2026-09-24).
      *
-     * `RETAIN_ONLY` is a positive assertion, not a default: this resource holds feature toggles, added
-     * and removed feature keys, and numeric limit overrides. Its only link to a person is the scope
-     * foreign key, which the never-scrub floor protects in every mode. Declaring the mode is what lets a
-     * notice say what erasure does to these rows instead of reporting them as undeclared.
+     * It declared `RETAIN_ONLY` — "feature toggles and limit overrides, nothing to scrub" — and since
+     * #1279 an erasure takes a silent edge's treatment from that declaration, so an erased person's
+     * entitlement overrides stayed live on a scrubbed profile. A per-person entitlement has no retention
+     * value once the person is erased, so the USERS → USER_FEATURES edge AUTHORS `strategy: DELETE`,
+     * dispatched through the DELETE below exactly as the parent-delete cascade dispatches it; re-adding a
+     * retention mode here would be refused as a contradiction.
      *
-     * The assertion is CHECKED: the factory refuses `RETAIN_ONLY` if any field declares an impersonalize
-     * treatment, because a treatment that would never run is a config claiming something the runtime
-     * would not honour.
+     * And so no `dataSubjectPolicy` either: the factory pairs the two in both directions, because only a
+     * retention-governed resource can be passed to an erasure as its SUBJECT. This row is never the
+     * subject of an erasure; it is a child an erasure destroys.
      */
-    retentionPolicy: {
-        mode: ErasureRetentionMode.RETAIN_ONLY,
-    },
-    /** The subject is the person whose features these are, reached through the scope key. */
-    dataSubjectPolicy: { kind: ResourceDataSubjectKind.SELF_PRINCIPAL },
     coreOperations: [
         CoreResourceOperation.CREATE,
         CoreResourceOperation.READ,
         CoreResourceOperation.SEARCH,
         CoreResourceOperation.UPDATE,
-        // Route-less; `retentionPolicy` requires READ + LIST + UPDATE_MANY (see the variants).
-        CoreResourceOperation.LIST,
-        CoreResourceOperation.UPDATE_MANY,
         // DELETE is REPOSITORY_ONLY (no HTTP route): the scope-features ledger is not
         // API-deletable, but the composition `onParentDelete` cascade must physically
-        // delete the row when its owning user is deleted. Without a DELETE op the cascade
-        // (`deleteChildrenImmediate`) throws ErrorType.CONFIGURATION on any user that has a
-        // features row. See .claude/plans/composition-oncreate-lifecycle.md (FEATURES wave).
+        // delete the row when its owning user is deleted, and a subject erasure dispatches
+        // the same teardown (#1569). Without a DELETE op the cascade (`deleteChildrenImmediate`)
+        // throws ErrorType.CONFIGURATION on any user that has a features row. The edge is 1:1,
+        // so discovery READs the row — no LIST is needed.
         CoreResourceOperation.DELETE,
     ],
     customOperation: {},
+    // assurance-control: WILDO.ENTITLEMENT.NO_SELF_GRANT — a user cannot widen its own entitlements.
+    //
+    // The subject of this row is the person it belongs to, which is exactly why the write gate matters
+    // more here than the read gate: READ and SEARCH are `ORG_MEMBER` so a principal can see its own
+    // entitlements, and every write — CREATE, UPDATE, DELETE — is `APP_ADMIN_SUPER_ADMIN`, which no
+    // organization-scope role confers.
+    // So the self-grant this objective names is refused for the principal best placed to attempt it.
+    //
+    // The role decides WHO may write; WHOSE row is decided one level down, by the USER_SELF scope.
+    // That scope refuses any row that is not the caller's unless the variant admits cross-subject
+    // administration, and until #1030 the UPDATE variant did not — so the one routable write to a
+    // user's entitlements let a super-administrator widen exactly their own, which is the inverse of
+    // what this comment claimed. The UPDATE variant now declares `admitsCrossSubjectUserAdministration`;
+    // the ORG_MEMBER reads deliberately do not.
+    //
+    // The role is the whole control for the same reason as the sibling ledgers: the super-admin path
+    // writes these fields, so they cannot be field-protected. No route-less door exists either:
+    // the retention-only LIST/UPDATE_MANY went with the retention policy (#1569). Pinned by
+    // `security-sensitive-operation-reachability.backend.test.ts`.
     operationsConfiguration: {
-        /*
-         * Route-less retention plumbing — INTERNAL_CALL registers no route. Not REPOSITORY_ONLY: the
-         * retention primitives resolve through `getServiceOperationPathDefault`, which excludes it, so
-         * that spelling passes the boot guard and fails when an erasure runs. LIST is LOW because a
-         * read-shaped operation may not claim the HIGH/CRITICAL band — that band carries an audit-emission
-         * obligation, checked over the real engine catalogue.
-         */
-        [CoreResourceOperation.LIST]: {
-            variants: [
-                {
-                    variantType: ResourceOperationVariantType.INTERNAL_CALL,
-                    isDefault: true,
-                    roles: [CORE_APP_ROLES.APP_ADMIN_SUPER_ADMIN],
-                    riskLevel: ResourceOperationRiskLevel.LOW,
-                },
-            ],
-        },
-        [CoreResourceOperation.UPDATE_MANY]: {
-            variants: [
-                {
-                    variantType: ResourceOperationVariantType.INTERNAL_CALL,
-                    isDefault: true,
-                    roles: [CORE_APP_ROLES.APP_ADMIN_SUPER_ADMIN],
-                    riskLevel: ResourceOperationRiskLevel.CRITICAL,
-                },
-            ],
-        },
         [CoreResourceOperation.CREATE]: {
             variants: [
                 {
@@ -127,6 +113,14 @@ export const userFeaturesResourceConfiguration_InitializationFactory = (resource
                     roles: [CORE_APP_ROLES.APP_ADMIN_SUPER_ADMIN],
                     riskLevel: ResourceOperationRiskLevel.HIGH,
                     requestDto: ScopeFeaturesWithOverridesSchema.partial(),
+                    // THE administrative write to another person's entitlements. This resource sits under the
+                    // USER_SELF scope, where `authorizeUserSelf` refuses any row whose user is not the caller
+                    // unless the VARIANT admits cross-subject addressing — so without this flag the only
+                    // routable write to a user's features let a super-administrator change exactly one user's
+                    // entitlements, their own, and nobody else's (#1030). The `roles` gate above still decides
+                    // WHO may call; this decides only WHOSE row. It stays OFF the `ORG_MEMBER` reads above:
+                    // admitting it there would let any member read any user's entitlements.
+                    admitsCrossSubjectUserAdministration: true,
                 }
             ],
         },

package/dist/esm/features/user-features.shared.resources-config.schemas.js.map

@@ -1 +1 @@
-{"version":3,"file":"user-features.shared.resources-config.schemas.js","sourceRoot":"","sources":["../../../../src/features/user-features.shared.resources-config.schemas.ts"],"names":[],"mappings":"AAAA;;;;;;GAMG;AAEH,OAAO,EAAE,gCAAgC,EAAE,MAAM,iCAAiC,CAAC;AACnF,OAAO,EAAE,oBAAoB,EAAE,uBAAuB,EAAE,MAAM,wDAAwD,CAAC;AAEvH,OAAO,EAAE,qBAAqB,EAAE,MAAM,gDAAgD,CAAC;AACvF,OAAO,EAAE,0BAA0B,EAAwB,MAAM,uCAAuC,CAAC;AACzG,OAAO,EAAE,gBAAgB,EAAE,kCAAkC,EAAE,MAAM,gDAAgD,CAAC;AACtH,OAAO,EAAE,4BAA4B,EAAE,MAAM,uCAAuC,CAAC;AACrF,OAAO,EAAE,0CAA0C,EAAE,MAAM,8CAA8C,CAAC;AAC1G,OAAO,EAAE,cAAc,EAAE,cAAc,EAAE,MAAM,iDAAiD,CAAC;AACjG,OAAO,EAAE,wBAAwB,EAAE,MAAM,8CAA8C,CAAC;AACxF,OAAO,EAAE,yBAAyB,EAAE,MAAM,qDAAqD,CAAC;AAWhG,MAAM,CAAC,MAAM,uDAAuD,GAAG,CAAC,sBAA8C,EAAE,EAAE,CAAC,0CAA0C,CAInK;IACA,UAAU,EAAE,gCAAgC;IAC5C,kBAAkB,EAAE,gBAAgB,CAAC,aAAa;IAClD,uBAAuB,EAAE,kCAAkC,CAAC,gBAAgB,CAAC,aAAa,CAAC;IAC3F,qBAAqB,EAAE,sBAAsB;IAC7C,gBAAgB,EAAE,IAAI;IAEtB,+JAA+J;IAC/J,kBAAkB,EAAE,EAAE,aAAa,EAAE,wBAAwB,CAAC,OAAO,EAAE;IACvE,iBAAiB,EAAE,EAAE,iBAAiB,EAAE,yBAAyB,CAAC,OAAO,EAAE;IAG3E;;;;;;;;;;;OAWG;IACH,eAAe,EAAE;QACf,IAAI,EAAE,oBAAoB,CAAC,WAAW;KACvC;IAED,yFAAyF;IACzF,iBAAiB,EAAE,EAAE,IAAI,EAAE,uBAAuB,CAAC,cAAc,EAAE;IAEnE,cAAc,EAAE;QACd,qBAAqB,CAAC,MAAM;QAC5B,qBAAqB,CAAC,IAAI;QAC1B,qBAAqB,CAAC,MAAM;QAC5B,qBAAqB,CAAC,MAAM;QAC5B,uFAAuF;QACvF,qBAAqB,CAAC,IAAI;QAC1B,qBAAqB,CAAC,WAAW;QACjC,8EAA8E;QAC9E,8EAA8E;QAC9E,kFAAkF;QAClF,oFAAoF;QACpF,qFAAqF;QACrF,qBAAqB,CAAC,MAAM;KAC7B;IAED,eAAe,EAAE,EAA2B;IAE5C,uBAAuB,EAAE;QACvB;;;;;;WAMG;QACH,CAAC,qBAAqB,CAAC,IAAI,CAAC,EAAE;YAC5B,QAAQ,EAAE;gBACR;oBACE,WAAW,EAAE,4BAA4B,CAAC,aAAa;oBACvD,SAAS,EAAE,IAAI;oBACf,KAAK,EAAE,CAAC,cAAc,CAAC,qBAAqB,CAAC;oBAC7C,SAAS,EAAE,0BAA0B,CAAC,GAAG;iBAC1C;aACF;SACF;QACD,CAAC,qBAAqB,CAAC,WAAW,CAAC,EAAE;YACnC,QAAQ,EAAE;gBACR;oBACE,WAAW,EAAE,4BAA4B,CAAC,aAAa;oBACvD,SAAS,EAAE,IAAI;oBACf,KAAK,EAAE,CAAC,cAAc,CAAC,qBAAqB,CAAC;oBAC7C,SAAS,EAAE,0BAA0B,CAAC,QAAQ;iBAC/C;aACF;SACF;QACD,CAAC,qBAAqB,CAAC,MAAM,CAAC,EAAE;YAC9B,QAAQ,EAAE;gBACR;oBACE,WAAW,EAAE,4BAA4B,CAAC,eAAe;oBACzD,SAAS,EAAE,IAAI;oBACf,KAAK,EAAE,CAAC,cAAc,CAAC,qBAAqB,CAAC;oBAC7C,SAAS,EAAE,0BAA0B,CAAC,MAAM;iBAC7C;aACF;SACF;QAED,CAAC,qBAAqB,CAAC,IAAI,CAAC,EAAE;YAC5B,QAAQ,EAAE;gBACR;oBACE,WAAW,EAAE,4BAA4B,CAAC,QAAQ;oBAClD,SAAS,EAAE,IAAI;oBACf,KAAK,EAAE,CAAC,cAAc,CAAC,UAAU,CAAC;oBAClC,SAAS,EAAE,0BAA0B,CAAC,GAAG;iBAC1C;aACF;SACF;QAED,CAAC,qBAAqB,CAAC,MAAM,CAAC,EAAE;YAC9B,QAAQ,EAAE,CAAC;oBACT,WAAW,EAAE,4BAA4B,CAAC,QAAQ;oBAClD,SAAS,EAAE,IAAI;oBACf,KAAK,EAAE,CAAC,cAAc,CAAC,UAAU,CAAC;oBAClC,SAAS,EAAE,0BAA0B,CAAC,GAAG;oBACzC,YAAY,EAAE,KAAK;oBACnB,gBAAgB,EAAE,EAAE;oBACpB,iBAAiB,EAAE,EAAE,aAAa,EAAE,KAAK,EAAE,aAAa,EAAE,KAAK,EAAE;oBACjE,YAAY,EAAE,EAAE;oBAChB,UAAU,EAAE,EAAE;oBACd,8BAA8B,EAAE,EAAE;iBACnC,CAAC;SACH;QAED,CAAC,qBAAqB,CAAC,MAAM,CAAC,EAAE;YAC9B,QAAQ,EAAE;gBACR;oBACE,WAAW,EAAE,4BAA4B,CAAC,QAAQ;oBAClD,SAAS,EAAE,IAAI;oBACf,KAAK,EAAE,CAAC,cAAc,CAAC,qBAAqB,CAAC;oBAC7C,SAAS,EAAE,0BAA0B,CAAC,IAAI;oBAC1C,UAAU,EAAE,gCAAgC,CAAC,OAAO,EAAE;iBACvD;aACF;SACF;QAED,kFAAkF;QAClF,4EAA4E;QAC5E,CAAC,qBAAqB,CAAC,MAAM,CAAC,EAAE;YAC9B,QAAQ,EAAE;gBACR;oBACE,WAAW,EAAE,4BAA4B,CAAC,eAAe;oBACzD,SAAS,EAAE,IAAI;oBACf,KAAK,EAAE,CAAC,cAAc,CAAC,qBAAqB,CAAC;oBAC7C,SAAS,EAAE,0BAA0B,CAAC,IAAI;iBAC3C;aACF;SACF;KACF;CACF,CAAC,CAAC","sourcesContent":["/**\n * User Features Shared Resource Configuration\n *\n * Resource configuration for user-level feature management.\n * Controls which features are available to individual users (overrides/additions).\n * Uses ScopeFeaturesWithOverridesSchema as mainSchema (same pattern as org features).\n */\n\nimport { ScopeFeaturesWithOverridesSchema } from './scope-features.shared.schemas';\nimport { ErasureRetentionMode, ResourceDataSubjectKind } from '../compliance/privacy/impersonalization.shared.schemas';\n\nimport { CoreResourceOperation } from '../resources/resources.shared.core.definitions';\nimport { ResourceOperationRiskLevel, ResourceRelationship } from '../resources/resources.shared.schemas';\nimport { CoreResourceType, coreResourceShared_FieldIdentifier } from '../resources/resources.shared.core.definitions';\nimport { ResourceOperationVariantType } from '../resources/resources.shared.schemas';\nimport { createResourceConfiguration_Initialization } from '../resources/resources-config.shared.factory';\nimport { CORE_APP_ROLES, CORE_ORG_ROLES } from '../security/authorizations/roles.shared.schemas';\nimport { ResourceSystemAccessMode } from '../resources/resources-config.shared.schemas';\nimport { DataPortabilityProvenance } from '../compliance/privacy/subject-export.shared.schemas';\n\ntype UserFeaturesCoreOperations =\n  | CoreResourceOperation.CREATE\n  | CoreResourceOperation.READ\n  | CoreResourceOperation.LIST\n  | CoreResourceOperation.UPDATE_MANY\n  | CoreResourceOperation.SEARCH\n  | CoreResourceOperation.UPDATE\n  | CoreResourceOperation.DELETE;\n\nexport const userFeaturesResourceConfiguration_InitializationFactory = (resourcesRelationships: ResourceRelationship[]) => createResourceConfiguration_Initialization<\n  Record<string, never>,\n  UserFeaturesCoreOperations,\n  typeof ScopeFeaturesWithOverridesSchema\n>({\n  mainSchema: ScopeFeaturesWithOverridesSchema,\n  resourceIdentifier: CoreResourceType.USER_FEATURES,\n  resourceFieldIdentifier: coreResourceShared_FieldIdentifier[CoreResourceType.USER_FEATURES],\n  resourceRelationships: resourcesRelationships,\n  isSystemResource: true,\n\n  /** Subject-export disclosure. The subject's own data. Secrets and backend-only values are withheld by the export's security floor regardless of this grant. */\n  systemAccessPolicy: { exportSubject: ResourceSystemAccessMode.ALLOWED },\n  portabilityPolicy: { defaultProvenance: DataPortabilityProvenance.DERIVED },\n\n\n  /**\n   * Subject erasure RETAINS this row and scrubs nothing, because there is nothing here to scrub.\n   *\n   * `RETAIN_ONLY` is a positive assertion, not a default: this resource holds feature toggles, added\n   * and removed feature keys, and numeric limit overrides. Its only link to a person is the scope\n   * foreign key, which the never-scrub floor protects in every mode. Declaring the mode is what lets a\n   * notice say what erasure does to these rows instead of reporting them as undeclared.\n   *\n   * The assertion is CHECKED: the factory refuses `RETAIN_ONLY` if any field declares an impersonalize\n   * treatment, because a treatment that would never run is a config claiming something the runtime\n   * would not honour.\n   */\n  retentionPolicy: {\n    mode: ErasureRetentionMode.RETAIN_ONLY,\n  },\n\n  /** The subject is the person whose features these are, reached through the scope key. */\n  dataSubjectPolicy: { kind: ResourceDataSubjectKind.SELF_PRINCIPAL },\n\n  coreOperations: [\n    CoreResourceOperation.CREATE,\n    CoreResourceOperation.READ,\n    CoreResourceOperation.SEARCH,\n    CoreResourceOperation.UPDATE,\n    // Route-less; `retentionPolicy` requires READ + LIST + UPDATE_MANY (see the variants).\n    CoreResourceOperation.LIST,\n    CoreResourceOperation.UPDATE_MANY,\n    // DELETE is REPOSITORY_ONLY (no HTTP route): the scope-features ledger is not\n    // API-deletable, but the composition `onParentDelete` cascade must physically\n    // delete the row when its owning user is deleted. Without a DELETE op the cascade\n    // (`deleteChildrenImmediate`) throws ErrorType.CONFIGURATION on any user that has a\n    // features row. See .claude/plans/composition-oncreate-lifecycle.md (FEATURES wave).\n    CoreResourceOperation.DELETE,\n  ],\n\n  customOperation: {} as Record<string, never>,\n\n  operationsConfiguration: {\n    /*\n     * Route-less retention plumbing — INTERNAL_CALL registers no route. Not REPOSITORY_ONLY: the\n     * retention primitives resolve through `getServiceOperationPathDefault`, which excludes it, so\n     * that spelling passes the boot guard and fails when an erasure runs. LIST is LOW because a\n     * read-shaped operation may not claim the HIGH/CRITICAL band — that band carries an audit-emission\n     * obligation, checked over the real engine catalogue.\n     */\n    [CoreResourceOperation.LIST]: {\n      variants: [\n        {\n          variantType: ResourceOperationVariantType.INTERNAL_CALL,\n          isDefault: true,\n          roles: [CORE_APP_ROLES.APP_ADMIN_SUPER_ADMIN],\n          riskLevel: ResourceOperationRiskLevel.LOW,\n        },\n      ],\n    },\n    [CoreResourceOperation.UPDATE_MANY]: {\n      variants: [\n        {\n          variantType: ResourceOperationVariantType.INTERNAL_CALL,\n          isDefault: true,\n          roles: [CORE_APP_ROLES.APP_ADMIN_SUPER_ADMIN],\n          riskLevel: ResourceOperationRiskLevel.CRITICAL,\n        },\n      ],\n    },\n    [CoreResourceOperation.CREATE]: {\n      variants: [\n        {\n          variantType: ResourceOperationVariantType.REPOSITORY_ONLY,\n          isDefault: true,\n          roles: [CORE_APP_ROLES.APP_ADMIN_SUPER_ADMIN],\n          riskLevel: ResourceOperationRiskLevel.MEDIUM,\n        }\n      ],\n    },\n\n    [CoreResourceOperation.READ]: {\n      variants: [\n        {\n          variantType: ResourceOperationVariantType.API_CALL,\n          isDefault: true,\n          roles: [CORE_ORG_ROLES.ORG_MEMBER],\n          riskLevel: ResourceOperationRiskLevel.LOW,\n        }\n      ]\n    },\n\n    [CoreResourceOperation.SEARCH]: {\n      variants: [{\n        variantType: ResourceOperationVariantType.API_CALL,\n        isDefault: true,\n        roles: [CORE_ORG_ROLES.ORG_MEMBER],\n        riskLevel: ResourceOperationRiskLevel.LOW,\n        isSearchable: false,\n        searchableFields: [],\n        searchableOptions: { caseSensitive: false, fullMatchOnly: false },\n        filterFields: {},\n        sortFields: [],\n        maxPaginatedResultPerPageLimit: 50,\n      }],\n    },\n\n    [CoreResourceOperation.UPDATE]: {\n      variants: [\n        {\n          variantType: ResourceOperationVariantType.API_CALL,\n          isDefault: true,\n          roles: [CORE_APP_ROLES.APP_ADMIN_SUPER_ADMIN],\n          riskLevel: ResourceOperationRiskLevel.HIGH,\n          requestDto: ScopeFeaturesWithOverridesSchema.partial(),\n        }\n      ],\n    },\n\n    // Internal-only (REPOSITORY_ONLY): powers the composition onParentDelete cascade,\n    // not a public API surface — the ledger is reset, never DELETEd, over HTTP.\n    [CoreResourceOperation.DELETE]: {\n      variants: [\n        {\n          variantType: ResourceOperationVariantType.REPOSITORY_ONLY,\n          isDefault: true,\n          roles: [CORE_APP_ROLES.APP_ADMIN_SUPER_ADMIN],\n          riskLevel: ResourceOperationRiskLevel.HIGH,\n        }\n      ],\n    },\n  },\n});\n"]}
+{"version":3,"file":"user-features.shared.resources-config.schemas.js","sourceRoot":"","sources":["../../../../src/features/user-features.shared.resources-config.schemas.ts"],"names":[],"mappings":"AAAA;;;;;;GAMG;AAEH,OAAO,EAAE,gCAAgC,EAAE,MAAM,iCAAiC,CAAC;AAEnF,OAAO,EAAE,qBAAqB,EAAE,MAAM,gDAAgD,CAAC;AACvF,OAAO,EAAE,0BAA0B,EAAwB,MAAM,uCAAuC,CAAC;AACzG,OAAO,EAAE,gBAAgB,EAAE,kCAAkC,EAAE,MAAM,gDAAgD,CAAC;AACtH,OAAO,EAAE,4BAA4B,EAAE,MAAM,uCAAuC,CAAC;AACrF,OAAO,EAAE,0CAA0C,EAAE,MAAM,8CAA8C,CAAC;AAC1G,OAAO,EAAE,cAAc,EAAE,cAAc,EAAE,MAAM,iDAAiD,CAAC;AACjG,OAAO,EAAE,wBAAwB,EAAE,MAAM,8CAA8C,CAAC;AACxF,OAAO,EAAE,yBAAyB,EAAE,MAAM,qDAAqD,CAAC;AAShG,MAAM,CAAC,MAAM,uDAAuD,GAAG,CAAC,sBAA8C,EAAE,EAAE,CAAC,0CAA0C,CAInK;IACA,UAAU,EAAE,gCAAgC;IAC5C,kBAAkB,EAAE,gBAAgB,CAAC,aAAa;IAClD,uBAAuB,EAAE,kCAAkC,CAAC,gBAAgB,CAAC,aAAa,CAAC;IAC3F,qBAAqB,EAAE,sBAAsB;IAC7C,gBAAgB,EAAE,IAAI;IAEtB,+JAA+J;IAC/J,kBAAkB,EAAE,EAAE,aAAa,EAAE,wBAAwB,CAAC,OAAO,EAAE;IACvE,iBAAiB,EAAE,EAAE,iBAAiB,EAAE,yBAAyB,CAAC,OAAO,EAAE;IAG3E;;;;;;;;;;;;;OAaG;IAEH,cAAc,EAAE;QACd,qBAAqB,CAAC,MAAM;QAC5B,qBAAqB,CAAC,IAAI;QAC1B,qBAAqB,CAAC,MAAM;QAC5B,qBAAqB,CAAC,MAAM;QAC5B,8EAA8E;QAC9E,8EAA8E;QAC9E,mFAAmF;QACnF,yFAAyF;QACzF,uFAAuF;QACvF,kDAAkD;QAClD,qBAAqB,CAAC,MAAM;KAC7B;IAED,eAAe,EAAE,EAA2B;IAE5C,iGAAiG;IACjG,EAAE;IACF,mGAAmG;IACnG,gGAAgG;IAChG,gGAAgG;IAChG,mCAAmC;IACnC,iGAAiG;IACjG,EAAE;IACF,+FAA+F;IAC/F,8FAA8F;IAC9F,8FAA8F;IAC9F,iGAAiG;IACjG,qGAAqG;IACrG,4CAA4C;IAC5C,EAAE;IACF,iGAAiG;IACjG,4FAA4F;IAC5F,wFAAwF;IACxF,+DAA+D;IAC/D,uBAAuB,EAAE;QACvB,CAAC,qBAAqB,CAAC,MAAM,CAAC,EAAE;YAC9B,QAAQ,EAAE;gBACR;oBACE,WAAW,EAAE,4BAA4B,CAAC,eAAe;oBACzD,SAAS,EAAE,IAAI;oBACf,KAAK,EAAE,CAAC,cAAc,CAAC,qBAAqB,CAAC;oBAC7C,SAAS,EAAE,0BAA0B,CAAC,MAAM;iBAC7C;aACF;SACF;QAED,CAAC,qBAAqB,CAAC,IAAI,CAAC,EAAE;YAC5B,QAAQ,EAAE;gBACR;oBACE,WAAW,EAAE,4BAA4B,CAAC,QAAQ;oBAClD,SAAS,EAAE,IAAI;oBACf,KAAK,EAAE,CAAC,cAAc,CAAC,UAAU,CAAC;oBAClC,SAAS,EAAE,0BAA0B,CAAC,GAAG;iBAC1C;aACF;SACF;QAED,CAAC,qBAAqB,CAAC,MAAM,CAAC,EAAE;YAC9B,QAAQ,EAAE,CAAC;oBACT,WAAW,EAAE,4BAA4B,CAAC,QAAQ;oBAClD,SAAS,EAAE,IAAI;oBACf,KAAK,EAAE,CAAC,cAAc,CAAC,UAAU,CAAC;oBAClC,SAAS,EAAE,0BAA0B,CAAC,GAAG;oBACzC,YAAY,EAAE,KAAK;oBACnB,gBAAgB,EAAE,EAAE;oBACpB,iBAAiB,EAAE,EAAE,aAAa,EAAE,KAAK,EAAE,aAAa,EAAE,KAAK,EAAE;oBACjE,YAAY,EAAE,EAAE;oBAChB,UAAU,EAAE,EAAE;oBACd,8BAA8B,EAAE,EAAE;iBACnC,CAAC;SACH;QAED,CAAC,qBAAqB,CAAC,MAAM,CAAC,EAAE;YAC9B,QAAQ,EAAE;gBACR;oBACE,WAAW,EAAE,4BAA4B,CAAC,QAAQ;oBAClD,SAAS,EAAE,IAAI;oBACf,KAAK,EAAE,CAAC,cAAc,CAAC,qBAAqB,CAAC;oBAC7C,SAAS,EAAE,0BAA0B,CAAC,IAAI;oBAC1C,UAAU,EAAE,gCAAgC,CAAC,OAAO,EAAE;oBACtD,0FAA0F;oBAC1F,0FAA0F;oBAC1F,qFAAqF;oBACrF,0FAA0F;oBAC1F,2FAA2F;oBAC3F,wFAAwF;oBACxF,wEAAwE;oBACxE,oCAAoC,EAAE,IAAI;iBAC3C;aACF;SACF;QAED,kFAAkF;QAClF,4EAA4E;QAC5E,CAAC,qBAAqB,CAAC,MAAM,CAAC,EAAE;YAC9B,QAAQ,EAAE;gBACR;oBACE,WAAW,EAAE,4BAA4B,CAAC,eAAe;oBACzD,SAAS,EAAE,IAAI;oBACf,KAAK,EAAE,CAAC,cAAc,CAAC,qBAAqB,CAAC;oBAC7C,SAAS,EAAE,0BAA0B,CAAC,IAAI;iBAC3C;aACF;SACF;KACF;CACF,CAAC,CAAC","sourcesContent":["/**\n * User Features Shared Resource Configuration\n *\n * Resource configuration for user-level feature management.\n * Controls which features are available to individual users (overrides/additions).\n * Uses ScopeFeaturesWithOverridesSchema as mainSchema (same pattern as org features).\n */\n\nimport { ScopeFeaturesWithOverridesSchema } from './scope-features.shared.schemas';\n\nimport { CoreResourceOperation } from '../resources/resources.shared.core.definitions';\nimport { ResourceOperationRiskLevel, ResourceRelationship } from '../resources/resources.shared.schemas';\nimport { CoreResourceType, coreResourceShared_FieldIdentifier } from '../resources/resources.shared.core.definitions';\nimport { ResourceOperationVariantType } from '../resources/resources.shared.schemas';\nimport { createResourceConfiguration_Initialization } from '../resources/resources-config.shared.factory';\nimport { CORE_APP_ROLES, CORE_ORG_ROLES } from '../security/authorizations/roles.shared.schemas';\nimport { ResourceSystemAccessMode } from '../resources/resources-config.shared.schemas';\nimport { DataPortabilityProvenance } from '../compliance/privacy/subject-export.shared.schemas';\n\ntype UserFeaturesCoreOperations =\n  | CoreResourceOperation.CREATE\n  | CoreResourceOperation.READ\n  | CoreResourceOperation.SEARCH\n  | CoreResourceOperation.UPDATE\n  | CoreResourceOperation.DELETE;\n\nexport const userFeaturesResourceConfiguration_InitializationFactory = (resourcesRelationships: ResourceRelationship[]) => createResourceConfiguration_Initialization<\n  Record<string, never>,\n  UserFeaturesCoreOperations,\n  typeof ScopeFeaturesWithOverridesSchema\n>({\n  mainSchema: ScopeFeaturesWithOverridesSchema,\n  resourceIdentifier: CoreResourceType.USER_FEATURES,\n  resourceFieldIdentifier: coreResourceShared_FieldIdentifier[CoreResourceType.USER_FEATURES],\n  resourceRelationships: resourcesRelationships,\n  isSystemResource: true,\n\n  /** Subject-export disclosure. The subject's own data. Secrets and backend-only values are withheld by the export's security floor regardless of this grant. */\n  systemAccessPolicy: { exportSubject: ResourceSystemAccessMode.ALLOWED },\n  portabilityPolicy: { defaultProvenance: DataPortabilityProvenance.DERIVED },\n\n\n  /*\n   * NO `retentionPolicy`, so a subject erasure DESTROYS this row (#1569, decided by Paul 2026-09-24).\n   *\n   * It declared `RETAIN_ONLY` — \"feature toggles and limit overrides, nothing to scrub\" — and since\n   * #1279 an erasure takes a silent edge's treatment from that declaration, so an erased person's\n   * entitlement overrides stayed live on a scrubbed profile. A per-person entitlement has no retention\n   * value once the person is erased, so the USERS → USER_FEATURES edge AUTHORS `strategy: DELETE`,\n   * dispatched through the DELETE below exactly as the parent-delete cascade dispatches it; re-adding a\n   * retention mode here would be refused as a contradiction.\n   *\n   * And so no `dataSubjectPolicy` either: the factory pairs the two in both directions, because only a\n   * retention-governed resource can be passed to an erasure as its SUBJECT. This row is never the\n   * subject of an erasure; it is a child an erasure destroys.\n   */\n\n  coreOperations: [\n    CoreResourceOperation.CREATE,\n    CoreResourceOperation.READ,\n    CoreResourceOperation.SEARCH,\n    CoreResourceOperation.UPDATE,\n    // DELETE is REPOSITORY_ONLY (no HTTP route): the scope-features ledger is not\n    // API-deletable, but the composition `onParentDelete` cascade must physically\n    // delete the row when its owning user is deleted, and a subject erasure dispatches\n    // the same teardown (#1569). Without a DELETE op the cascade (`deleteChildrenImmediate`)\n    // throws ErrorType.CONFIGURATION on any user that has a features row. The edge is 1:1,\n    // so discovery READs the row — no LIST is needed.\n    CoreResourceOperation.DELETE,\n  ],\n\n  customOperation: {} as Record<string, never>,\n\n  // assurance-control: WILDO.ENTITLEMENT.NO_SELF_GRANT — a user cannot widen its own entitlements.\n  //\n  // The subject of this row is the person it belongs to, which is exactly why the write gate matters\n  // more here than the read gate: READ and SEARCH are `ORG_MEMBER` so a principal can see its own\n  // entitlements, and every write — CREATE, UPDATE, DELETE — is `APP_ADMIN_SUPER_ADMIN`, which no\n  // organization-scope role confers.\n  // So the self-grant this objective names is refused for the principal best placed to attempt it.\n  //\n  // The role decides WHO may write; WHOSE row is decided one level down, by the USER_SELF scope.\n  // That scope refuses any row that is not the caller's unless the variant admits cross-subject\n  // administration, and until #1030 the UPDATE variant did not — so the one routable write to a\n  // user's entitlements let a super-administrator widen exactly their own, which is the inverse of\n  // what this comment claimed. The UPDATE variant now declares `admitsCrossSubjectUserAdministration`;\n  // the ORG_MEMBER reads deliberately do not.\n  //\n  // The role is the whole control for the same reason as the sibling ledgers: the super-admin path\n  // writes these fields, so they cannot be field-protected. No route-less door exists either:\n  // the retention-only LIST/UPDATE_MANY went with the retention policy (#1569). Pinned by\n  // `security-sensitive-operation-reachability.backend.test.ts`.\n  operationsConfiguration: {\n    [CoreResourceOperation.CREATE]: {\n      variants: [\n        {\n          variantType: ResourceOperationVariantType.REPOSITORY_ONLY,\n          isDefault: true,\n          roles: [CORE_APP_ROLES.APP_ADMIN_SUPER_ADMIN],\n          riskLevel: ResourceOperationRiskLevel.MEDIUM,\n        }\n      ],\n    },\n\n    [CoreResourceOperation.READ]: {\n      variants: [\n        {\n          variantType: ResourceOperationVariantType.API_CALL,\n          isDefault: true,\n          roles: [CORE_ORG_ROLES.ORG_MEMBER],\n          riskLevel: ResourceOperationRiskLevel.LOW,\n        }\n      ]\n    },\n\n    [CoreResourceOperation.SEARCH]: {\n      variants: [{\n        variantType: ResourceOperationVariantType.API_CALL,\n        isDefault: true,\n        roles: [CORE_ORG_ROLES.ORG_MEMBER],\n        riskLevel: ResourceOperationRiskLevel.LOW,\n        isSearchable: false,\n        searchableFields: [],\n        searchableOptions: { caseSensitive: false, fullMatchOnly: false },\n        filterFields: {},\n        sortFields: [],\n        maxPaginatedResultPerPageLimit: 50,\n      }],\n    },\n\n    [CoreResourceOperation.UPDATE]: {\n      variants: [\n        {\n          variantType: ResourceOperationVariantType.API_CALL,\n          isDefault: true,\n          roles: [CORE_APP_ROLES.APP_ADMIN_SUPER_ADMIN],\n          riskLevel: ResourceOperationRiskLevel.HIGH,\n          requestDto: ScopeFeaturesWithOverridesSchema.partial(),\n          // THE administrative write to another person's entitlements. This resource sits under the\n          // USER_SELF scope, where `authorizeUserSelf` refuses any row whose user is not the caller\n          // unless the VARIANT admits cross-subject addressing — so without this flag the only\n          // routable write to a user's features let a super-administrator change exactly one user's\n          // entitlements, their own, and nobody else's (#1030). The `roles` gate above still decides\n          // WHO may call; this decides only WHOSE row. It stays OFF the `ORG_MEMBER` reads above:\n          // admitting it there would let any member read any user's entitlements.\n          admitsCrossSubjectUserAdministration: true,\n        }\n      ],\n    },\n\n    // Internal-only (REPOSITORY_ONLY): powers the composition onParentDelete cascade,\n    // not a public API surface — the ledger is reset, never DELETEd, over HTTP.\n    [CoreResourceOperation.DELETE]: {\n      variants: [\n        {\n          variantType: ResourceOperationVariantType.REPOSITORY_ONLY,\n          isDefault: true,\n          roles: [CORE_APP_ROLES.APP_ADMIN_SUPER_ADMIN],\n          riskLevel: ResourceOperationRiskLevel.HIGH,\n        }\n      ],\n    },\n  },\n});\n"]}

package/dist/esm/files/file-remote-reference-link.shared.schemas.d.ts

@@ -0,0 +1,73 @@
+import { z } from 'zod';
+/**
+ * Linking a file that STAYS at a vendor into a resource's file field (#394 P5).
+ *
+ * A provider's picker that delivers a `REMOTE_REFERENCE` hands the browser an
+ * opaque id the vendor understands and nothing else — no bytes. The field then
+ * POSTs this body to the SAME route a byte upload uses, so the route's
+ * authorization, the field's `storageAccepted`, scope derivation and upload
+ * grants all apply once, and the backend produces a FILES row whose
+ * `storageProvider` is the vendor storage and whose `storageRef` is that id.
+ *
+ * One route, two bodies: a multipart `file` part carries bytes, a JSON
+ * `remoteReference` carries a reference. The two are distinguished by which is
+ * present, never by a header a client can get wrong.
+ */
+export declare const FILE_REMOTE_REFERENCE_LINK_BODY_KEY = "remoteReference";
+export declare const FileRemoteReferenceLinkSchema: z.ZodObject<{
+    /** The provider whose picker produced the reference — `google-drive` (the connected provider's ref), never the storage value `google_drive`. */
+    providerRef: z.ZodString;
+    /** The vendor's own id for the file, exactly as the picker returned it. */
+    externalId: z.ZodString;
+    /**
+     * What the picker showed the person. Advisory: the backend reads the vendor's
+     * own metadata before creating the row and prefers it, because a display
+     * name typed by a client is not evidence about the file.
+     */
+    displayName: z.ZodOptional<z.ZodString>;
+    mimeType: z.ZodOptional<z.ZodString>;
+    sizeBytes: z.ZodOptional<z.ZodNumber>;
+}, z.core.$strict>;
+export type FileRemoteReferenceLink = z.infer<typeof FileRemoteReferenceLinkSchema>;
+export declare const FileRemoteReferenceLinkRequestSchema: z.ZodObject<{
+    remoteReference: z.ZodObject<{
+        /** The provider whose picker produced the reference — `google-drive` (the connected provider's ref), never the storage value `google_drive`. */
+        providerRef: z.ZodString;
+        /** The vendor's own id for the file, exactly as the picker returned it. */
+        externalId: z.ZodString;
+        /**
+         * What the picker showed the person. Advisory: the backend reads the vendor's
+         * own metadata before creating the row and prefers it, because a display
+         * name typed by a client is not evidence about the file.
+         */
+        displayName: z.ZodOptional<z.ZodString>;
+        mimeType: z.ZodOptional<z.ZodString>;
+        sizeBytes: z.ZodOptional<z.ZodNumber>;
+    }, z.core.$strict>;
+}, z.core.$strip>;
+export type FileRemoteReferenceLinkRequest = z.infer<typeof FileRemoteReferenceLinkRequestSchema>;
+/** What a request body says about a remote reference — three answers, all distinct. */
+export declare enum FileRemoteReferenceLinkRead {
+    /** The body carries no `remoteReference` at all: this is a byte upload, or nothing. */
+    ABSENT = "absent",
+    /** A well-formed reference. */
+    PRESENT = "present",
+    /** The key is there and its value is not a reference — a client defect, never silently an upload. */
+    INVALID = "invalid"
+}
+export type FileRemoteReferenceLinkReadResult = {
+    readonly kind: FileRemoteReferenceLinkRead.ABSENT;
+} | {
+    readonly kind: FileRemoteReferenceLinkRead.PRESENT;
+    readonly link: FileRemoteReferenceLink;
+} | {
+    readonly kind: FileRemoteReferenceLinkRead.INVALID;
+    readonly issues: readonly string[];
+};
+/**
+ * Reads a remote reference off a parsed request body. A multipart upload
+ * arrives with an empty or `fileId`-only body and reads as ABSENT; a JSON body
+ * naming the key is either PRESENT or INVALID. Nothing else is inferred.
+ */
+export declare function readFileRemoteReferenceLinkRequest(body: unknown): FileRemoteReferenceLinkReadResult;
+//# sourceMappingURL=file-remote-reference-link.shared.schemas.d.ts.map

package/dist/esm/files/file-remote-reference-link.shared.schemas.d.ts.map

@@ -0,0 +1 @@
+{"version":3,"file":"file-remote-reference-link.shared.schemas.d.ts","sourceRoot":"","sources":["../../../../src/files/file-remote-reference-link.shared.schemas.ts"],"names":[],"mappings":"AAAA,OAAO,EAAE,CAAC,EAAE,MAAM,KAAK,CAAC;AAExB;;;;;;;;;;;;;GAaG;AACH,eAAO,MAAM,mCAAmC,oBAAoB,CAAC;AAErE,eAAO,MAAM,6BAA6B;IACxC,gJAAgJ;;IAEhJ,2EAA2E;;IAE3E;;;;OAIG;;;;kBAIH,CAAC;AACH,MAAM,MAAM,uBAAuB,GAAG,CAAC,CAAC,KAAK,CAAC,OAAO,6BAA6B,CAAC,CAAC;AAEpF,eAAO,MAAM,oCAAoC;;QAf/C,gJAAgJ;;QAEhJ,2EAA2E;;QAE3E;;;;WAIG;;;;;iBASH,CAAC;AACH,MAAM,MAAM,8BAA8B,GAAG,CAAC,CAAC,KAAK,CAAC,OAAO,oCAAoC,CAAC,CAAC;AAElG,uFAAuF;AACvF,oBAAY,2BAA2B;IACrC,uFAAuF;IACvF,MAAM,WAAW;IACjB,+BAA+B;IAC/B,OAAO,YAAY;IACnB,qGAAqG;IACrG,OAAO,YAAY;CACpB;AAED,MAAM,MAAM,iCAAiC,GACzC;IAAE,QAAQ,CAAC,IAAI,EAAE,2BAA2B,CAAC,MAAM,CAAA;CAAE,GACrD;IAAE,QAAQ,CAAC,IAAI,EAAE,2BAA2B,CAAC,OAAO,CAAC;IAAC,QAAQ,CAAC,IAAI,EAAE,uBAAuB,CAAA;CAAE,GAC9F;IAAE,QAAQ,CAAC,IAAI,EAAE,2BAA2B,CAAC,OAAO,CAAC;IAAC,QAAQ,CAAC,MAAM,EAAE,SAAS,MAAM,EAAE,CAAA;CAAE,CAAC;AAE/F;;;;GAIG;AACH,wBAAgB,kCAAkC,CAAC,IAAI,EAAE,OAAO,GAAG,iCAAiC,CAYnG"}

package/dist/esm/files/file-remote-reference-link.shared.schemas.js

@@ -0,0 +1,62 @@
+import { z } from 'zod';
+/**
+ * Linking a file that STAYS at a vendor into a resource's file field (#394 P5).
+ *
+ * A provider's picker that delivers a `REMOTE_REFERENCE` hands the browser an
+ * opaque id the vendor understands and nothing else — no bytes. The field then
+ * POSTs this body to the SAME route a byte upload uses, so the route's
+ * authorization, the field's `storageAccepted`, scope derivation and upload
+ * grants all apply once, and the backend produces a FILES row whose
+ * `storageProvider` is the vendor storage and whose `storageRef` is that id.
+ *
+ * One route, two bodies: a multipart `file` part carries bytes, a JSON
+ * `remoteReference` carries a reference. The two are distinguished by which is
+ * present, never by a header a client can get wrong.
+ */
+export const FILE_REMOTE_REFERENCE_LINK_BODY_KEY = 'remoteReference';
+export const FileRemoteReferenceLinkSchema = z.strictObject({
+    /** The provider whose picker produced the reference — `google-drive` (the connected provider's ref), never the storage value `google_drive`. */
+    providerRef: z.string().min(1),
+    /** The vendor's own id for the file, exactly as the picker returned it. */
+    externalId: z.string().min(1),
+    /**
+     * What the picker showed the person. Advisory: the backend reads the vendor's
+     * own metadata before creating the row and prefers it, because a display
+     * name typed by a client is not evidence about the file.
+     */
+    displayName: z.string().min(1).optional(),
+    mimeType: z.string().min(1).optional(),
+    sizeBytes: z.number().int().min(0).optional(),
+});
+export const FileRemoteReferenceLinkRequestSchema = z.object({
+    [FILE_REMOTE_REFERENCE_LINK_BODY_KEY]: FileRemoteReferenceLinkSchema,
+});
+/** What a request body says about a remote reference — three answers, all distinct. */
+export var FileRemoteReferenceLinkRead;
+(function (FileRemoteReferenceLinkRead) {
+    /** The body carries no `remoteReference` at all: this is a byte upload, or nothing. */
+    FileRemoteReferenceLinkRead["ABSENT"] = "absent";
+    /** A well-formed reference. */
+    FileRemoteReferenceLinkRead["PRESENT"] = "present";
+    /** The key is there and its value is not a reference — a client defect, never silently an upload. */
+    FileRemoteReferenceLinkRead["INVALID"] = "invalid";
+})(FileRemoteReferenceLinkRead || (FileRemoteReferenceLinkRead = {}));
+/**
+ * Reads a remote reference off a parsed request body. A multipart upload
+ * arrives with an empty or `fileId`-only body and reads as ABSENT; a JSON body
+ * naming the key is either PRESENT or INVALID. Nothing else is inferred.
+ */
+export function readFileRemoteReferenceLinkRequest(body) {
+    if (body === null || typeof body !== 'object' || !(FILE_REMOTE_REFERENCE_LINK_BODY_KEY in body)) {
+        return { kind: FileRemoteReferenceLinkRead.ABSENT };
+    }
+    const parsed = FileRemoteReferenceLinkRequestSchema.safeParse(body);
+    if (!parsed.success) {
+        return {
+            kind: FileRemoteReferenceLinkRead.INVALID,
+            issues: parsed.error.issues.map((issue) => `${issue.path.join('.') || '(root)'}: ${issue.message}`),
+        };
+    }
+    return { kind: FileRemoteReferenceLinkRead.PRESENT, link: parsed.data[FILE_REMOTE_REFERENCE_LINK_BODY_KEY] };
+}
+//# sourceMappingURL=file-remote-reference-link.shared.schemas.js.map

package/dist/esm/files/file-remote-reference-link.shared.schemas.js.map

@@ -0,0 +1 @@
+{"version":3,"file":"file-remote-reference-link.shared.schemas.js","sourceRoot":"","sources":["../../../../src/files/file-remote-reference-link.shared.schemas.ts"],"names":[],"mappings":"AAAA,OAAO,EAAE,CAAC,EAAE,MAAM,KAAK,CAAC;AAExB;;;;;;;;;;;;;GAaG;AACH,MAAM,CAAC,MAAM,mCAAmC,GAAG,iBAAiB,CAAC;AAErE,MAAM,CAAC,MAAM,6BAA6B,GAAG,CAAC,CAAC,YAAY,CAAC;IAC1D,gJAAgJ;IAChJ,WAAW,EAAE,CAAC,CAAC,MAAM,EAAE,CAAC,GAAG,CAAC,CAAC,CAAC;IAC9B,2EAA2E;IAC3E,UAAU,EAAE,CAAC,CAAC,MAAM,EAAE,CAAC,GAAG,CAAC,CAAC,CAAC;IAC7B;;;;OAIG;IACH,WAAW,EAAE,CAAC,CAAC,MAAM,EAAE,CAAC,GAAG,CAAC,CAAC,CAAC,CAAC,QAAQ,EAAE;IACzC,QAAQ,EAAE,CAAC,CAAC,MAAM,EAAE,CAAC,GAAG,CAAC,CAAC,CAAC,CAAC,QAAQ,EAAE;IACtC,SAAS,EAAE,CAAC,CAAC,MAAM,EAAE,CAAC,GAAG,EAAE,CAAC,GAAG,CAAC,CAAC,CAAC,CAAC,QAAQ,EAAE;CAC9C,CAAC,CAAC;AAGH,MAAM,CAAC,MAAM,oCAAoC,GAAG,CAAC,CAAC,MAAM,CAAC;IAC3D,CAAC,mCAAmC,CAAC,EAAE,6BAA6B;CACrE,CAAC,CAAC;AAGH,uFAAuF;AACvF,MAAM,CAAN,IAAY,2BAOX;AAPD,WAAY,2BAA2B;IACrC,uFAAuF;IACvF,gDAAiB,CAAA;IACjB,+BAA+B;IAC/B,kDAAmB,CAAA;IACnB,qGAAqG;IACrG,kDAAmB,CAAA;AACrB,CAAC,EAPW,2BAA2B,KAA3B,2BAA2B,QAOtC;AAOD;;;;GAIG;AACH,MAAM,UAAU,kCAAkC,CAAC,IAAa;IAC9D,IAAI,IAAI,KAAK,IAAI,IAAI,OAAO,IAAI,KAAK,QAAQ,IAAI,CAAC,CAAC,mCAAmC,IAAI,IAAI,CAAC,EAAE,CAAC;QAChG,OAAO,EAAE,IAAI,EAAE,2BAA2B,CAAC,MAAM,EAAE,CAAC;IACtD,CAAC;IACD,MAAM,MAAM,GAAG,oCAAoC,CAAC,SAAS,CAAC,IAAI,CAAC,CAAC;IACpE,IAAI,CAAC,MAAM,CAAC,OAAO,EAAE,CAAC;QACpB,OAAO;YACL,IAAI,EAAE,2BAA2B,CAAC,OAAO;YACzC,MAAM,EAAE,MAAM,CAAC,KAAK,CAAC,MAAM,CAAC,GAAG,CAAC,CAAC,KAAK,EAAE,EAAE,CAAC,GAAG,KAAK,CAAC,IAAI,CAAC,IAAI,CAAC,GAAG,CAAC,IAAI,QAAQ,KAAK,KAAK,CAAC,OAAO,EAAE,CAAC;SACpG,CAAC;IACJ,CAAC;IACD,OAAO,EAAE,IAAI,EAAE,2BAA2B,CAAC,OAAO,EAAE,IAAI,EAAE,MAAM,CAAC,IAAI,CAAC,mCAAmC,CAAC,EAAE,CAAC;AAC/G,CAAC","sourcesContent":["import { z } from 'zod';\n\n/**\n * Linking a file that STAYS at a vendor into a resource's file field (#394 P5).\n *\n * A provider's picker that delivers a `REMOTE_REFERENCE` hands the browser an\n * opaque id the vendor understands and nothing else — no bytes. The field then\n * POSTs this body to the SAME route a byte upload uses, so the route's\n * authorization, the field's `storageAccepted`, scope derivation and upload\n * grants all apply once, and the backend produces a FILES row whose\n * `storageProvider` is the vendor storage and whose `storageRef` is that id.\n *\n * One route, two bodies: a multipart `file` part carries bytes, a JSON\n * `remoteReference` carries a reference. The two are distinguished by which is\n * present, never by a header a client can get wrong.\n */\nexport const FILE_REMOTE_REFERENCE_LINK_BODY_KEY = 'remoteReference';\n\nexport const FileRemoteReferenceLinkSchema = z.strictObject({\n  /** The provider whose picker produced the reference — `google-drive` (the connected provider's ref), never the storage value `google_drive`. */\n  providerRef: z.string().min(1),\n  /** The vendor's own id for the file, exactly as the picker returned it. */\n  externalId: z.string().min(1),\n  /**\n   * What the picker showed the person. Advisory: the backend reads the vendor's\n   * own metadata before creating the row and prefers it, because a display\n   * name typed by a client is not evidence about the file.\n   */\n  displayName: z.string().min(1).optional(),\n  mimeType: z.string().min(1).optional(),\n  sizeBytes: z.number().int().min(0).optional(),\n});\nexport type FileRemoteReferenceLink = z.infer<typeof FileRemoteReferenceLinkSchema>;\n\nexport const FileRemoteReferenceLinkRequestSchema = z.object({\n  [FILE_REMOTE_REFERENCE_LINK_BODY_KEY]: FileRemoteReferenceLinkSchema,\n});\nexport type FileRemoteReferenceLinkRequest = z.infer<typeof FileRemoteReferenceLinkRequestSchema>;\n\n/** What a request body says about a remote reference — three answers, all distinct. */\nexport enum FileRemoteReferenceLinkRead {\n  /** The body carries no `remoteReference` at all: this is a byte upload, or nothing. */\n  ABSENT = 'absent',\n  /** A well-formed reference. */\n  PRESENT = 'present',\n  /** The key is there and its value is not a reference — a client defect, never silently an upload. */\n  INVALID = 'invalid',\n}\n\nexport type FileRemoteReferenceLinkReadResult =\n  | { readonly kind: FileRemoteReferenceLinkRead.ABSENT }\n  | { readonly kind: FileRemoteReferenceLinkRead.PRESENT; readonly link: FileRemoteReferenceLink }\n  | { readonly kind: FileRemoteReferenceLinkRead.INVALID; readonly issues: readonly string[] };\n\n/**\n * Reads a remote reference off a parsed request body. A multipart upload\n * arrives with an empty or `fileId`-only body and reads as ABSENT; a JSON body\n * naming the key is either PRESENT or INVALID. Nothing else is inferred.\n */\nexport function readFileRemoteReferenceLinkRequest(body: unknown): FileRemoteReferenceLinkReadResult {\n  if (body === null || typeof body !== 'object' || !(FILE_REMOTE_REFERENCE_LINK_BODY_KEY in body)) {\n    return { kind: FileRemoteReferenceLinkRead.ABSENT };\n  }\n  const parsed = FileRemoteReferenceLinkRequestSchema.safeParse(body);\n  if (!parsed.success) {\n    return {\n      kind: FileRemoteReferenceLinkRead.INVALID,\n      issues: parsed.error.issues.map((issue) => `${issue.path.join('.') || '(root)'}: ${issue.message}`),\n    };\n  }\n  return { kind: FileRemoteReferenceLinkRead.PRESENT, link: parsed.data[FILE_REMOTE_REFERENCE_LINK_BODY_KEY] };\n}\n"]}

package/dist/esm/files/files.shared.resources-config.schemas.d.ts

@@ -7,13 +7,13 @@
  * ## Scope Model
  *
  * Files use a **dynamic scope** that is derived from the parent resource's
- * resourcePrimaryScope when linked. The FILES resource itself is configured
- * with ORGANIZATIONS as default primaryScope, but individual file records
+ * resourcePrimaryScope when linked. The canonical FILES registry relationship gives it
+ * APPLICATION as its repository primaryScope, but individual file records
  * store their actual scope in the `primaryScope` field.
  *
  * This allows files to be correctly scoped to:
  * - APPLICATION: App-level shared files
- * - ORGANIZATIONS: Org-scoped files (default)
+ * - ORGANIZATIONS: Org-scoped files
  * - USER_SELF: User-private files
  *
  */

package/dist/esm/files/files.shared.resources-config.schemas.js

@@ -7,13 +7,13 @@
  * ## Scope Model
  *
  * Files use a **dynamic scope** that is derived from the parent resource's
- * resourcePrimaryScope when linked. The FILES resource itself is configured
- * with ORGANIZATIONS as default primaryScope, but individual file records
+ * resourcePrimaryScope when linked. The canonical FILES registry relationship gives it
+ * APPLICATION as its repository primaryScope, but individual file records
  * store their actual scope in the `primaryScope` field.
  *
  * This allows files to be correctly scoped to:
  * - APPLICATION: App-level shared files
- * - ORGANIZATIONS: Org-scoped files (default)
+ * - ORGANIZATIONS: Org-scoped files
  * - USER_SELF: User-private files
  *
  */

package/dist/esm/files/files.shared.resources-config.schemas.js.map

@@ -1 +1 @@
-{"version":3,"file":"files.shared.resources-config.schemas.js","sourceRoot":"","sources":["../../../../src/files/files.shared.resources-config.schemas.ts"],"names":[],"mappings":"AAAA;;;;;;;;;;;;;;;;;;GAkBG;AAGH,OAAO,EAAE,0CAA0C,EAAE,MAAM,8CAA8C,CAAC;AAC1G,OAAO,EAAE,qBAAqB,EAAE,gBAAgB,EAAE,kCAAkC,EAAE,MAAM,gDAAgD,CAAC;AAC7I,OAAO,EAAE,0BAA0B,EAAE,4BAA4B,EAA8C,MAAM,uCAAuC,CAAC;AAC7J,OAAO,EAAE,cAAc,EAAE,MAAM,iDAAiD,CAAC;AACjF,OAAO,EAAE,UAAU,EAAE,MAAM,wBAAwB,CAAC;AASpD;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;GAiCG;AACH,MAAM,CAAC,MAAM,gDAAgD,GAAG,CAC9D,sBAA8C,EAC9C,EAAE,CAAC,0CAA0C,CAI7C;IACA,UAAU,EAAE,UAAU;IACtB,kBAAkB,EAAE,gBAAgB,CAAC,KAAK;IAC1C,uBAAuB,EAAE,kCAAkC,CAAC,gBAAgB,CAAC,KAAK,CAAC;IACnF,qBAAqB,EAAE,sBAAsB;IAC7C,gBAAgB,EAAE,IAAI;IACtB,cAAc,EAAE;QACd,qBAAqB,CAAC,IAAI;QAC1B,qBAAqB,CAAC,IAAI;QAC1B,qBAAqB,CAAC,MAAM;QAC5B,qBAAqB,CAAC,MAAM;QAC5B,qBAAqB,CAAC,MAAM;KAC7B;IACD,uBAAuB,EAAE;QACvB,CAAC,qBAAqB,CAAC,IAAI,CAAC,EAAE;YAC5B,QAAQ,EAAE;gBACR;oBACE,WAAW,EAAE,4BAA4B,CAAC,eAAe;oBACzD,SAAS,EAAE,IAAI;oBACf,KAAK,EAAE,CAAC,cAAc,CAAC,UAAU,CAAC;oBAClC,SAAS,EAAE,0BAA0B,CAAC,GAAG;iBAC1C;aACF;SACF;QACD,CAAC,qBAAqB,CAAC,IAAI,CAAC,EAAE;YAC5B,QAAQ,EAAE;gBACR;oBACE,WAAW,EAAE,4BAA4B,CAAC,eAAe;oBACzD,SAAS,EAAE,IAAI;oBACf,KAAK,EAAE,CAAC,cAAc,CAAC,UAAU,CAAC;oBAClC,SAAS,EAAE,0BAA0B,CAAC,GAAG;iBAC1C;aACF;SACF;QACD,CAAC,qBAAqB,CAAC,MAAM,CAAC,EAAE;YAC9B,QAAQ,EAAE;gBACR;oBACE,WAAW,EAAE,4BAA4B,CAAC,eAAe;oBACzD,SAAS,EAAE,IAAI;oBACf,KAAK,EAAE,CAAC,cAAc,CAAC,UAAU,CAAC;oBAClC,SAAS,EAAE,0BAA0B,CAAC,GAAG;iBAC1C;aACF;SACF;QACD,CAAC,qBAAqB,CAAC,MAAM,CAAC,EAAE;YAC9B,QAAQ,EAAE;gBACR;oBACE,WAAW,EAAE,4BAA4B,CAAC,eAAe;oBACzD,SAAS,EAAE,IAAI;oBACf,KAAK,EAAE,CAAC,cAAc,CAAC,UAAU,CAAC;oBAClC,SAAS,EAAE,0BAA0B,CAAC,GAAG;iBAC1C;aACF;SACF;QACD,CAAC,qBAAqB,CAAC,MAAM,CAAC,EAAE;YAC9B,QAAQ,EAAE;gBACR;oBACE,WAAW,EAAE,4BAA4B,CAAC,eAAe;oBACzD,SAAS,EAAE,IAAI;oBACf,KAAK,EAAE,CAAC,cAAc,CAAC,UAAU,CAAC;oBAClC,SAAS,EAAE,0BAA0B,CAAC,GAAG;iBAC1C;aACF;SACF;KACF;CACF,CAAC,CAAC","sourcesContent":["/**\n * Files Resource Configuration (Repository-only)\n * \n * Provides repository operations for file metadata management.\n * Files are managed internally by the file upload system.\n * \n * ## Scope Model\n * \n * Files use a **dynamic scope** that is derived from the parent resource's\n * resourcePrimaryScope when linked. The FILES resource itself is configured\n * with ORGANIZATIONS as default primaryScope, but individual file records\n * store their actual scope in the `primaryScope` field.\n * \n * This allows files to be correctly scoped to:\n * - APPLICATION: App-level shared files\n * - ORGANIZATIONS: Org-scoped files (default)\n * - USER_SELF: User-private files\n *\n */\n\nimport { z } from 'zod';\nimport { createResourceConfiguration_Initialization } from '../resources/resources-config.shared.factory';\nimport { CoreResourceOperation, CoreResourceType, coreResourceShared_FieldIdentifier } from '../resources/resources.shared.core.definitions';\nimport { ResourceOperationRiskLevel, ResourceOperationVariantType, ResourceRelationship, ResourcePrimaryScope } from '../resources/resources.shared.schemas';\nimport { CORE_ORG_ROLES } from '../security/authorizations/roles.shared.schemas';\nimport { FileSchema } from './files.shared.schemas';\n\ntype FilesCoreOperations = \n  | CoreResourceOperation.READ\n  | CoreResourceOperation.LIST\n  | CoreResourceOperation.CREATE\n  | CoreResourceOperation.UPDATE\n  | CoreResourceOperation.DELETE;\n\n/**\n * Files Resource Configuration Factory\n * \n * Creates a REPOSITORY_ONLY resource configuration for file metadata.\n * Files are managed internally by the file upload system and not exposed\n * as standard REST API endpoints. Repository operations are used internally\n * by FilesBackendService.\n *\n * ## Persistence\n *\n * There is deliberately NO `persistenceAdapter` here: FILES FOLLOWS the application's default\n * adapter. It used to be pinned to MongoDB, on the grounds that \"file metadata relies on\n * Mongo-backed transactional/link semantics throughout the upload/link/unlink/cleanup pipeline\".\n * Measured rather than trusted, that was substantially true when written and is no longer:\n *\n * - the upload/link transaction opened on `MongoDBService` BY NAME; it now opens on whichever\n *   store FILES resolves to;\n * - the cleanup batch cleared link metadata through a raw-MongoDB `$unset`; it now uses the\n *   adapter-neutral guarded set-and-clear on the repository contract;\n * - the file-id validation was believed to require an ObjectId shape. It never did —\n *   `Resources_SharedUtils.isValidResourceId` has always accepted ObjectId AND UUID, and only the\n *   comment claimed otherwise.\n *\n * Blobs were never the issue: there is no GridFS. They live in object storage, and MongoDB held\n * only this metadata row.\n *\n * **The pin was also what forced file metadata into a SECOND store**, which is why removing it\n * closes more than it opens: a resource and its file metadata on one adapter share ONE native\n * transaction, so generated-document materialization (PDFs) stops being refused as a cross-adapter\n * boundary, and no saga or outbox is needed to make it atomic.\n *\n * An application is expected to be wholly one adapter (plan Wave 4.5). Following the default is\n * what makes that true for FILES instead of quietly exempting it.\n */\nexport const filesResourceConfiguration_InitializationFactory = (\n  resourcesRelationships: ResourceRelationship[]\n) => createResourceConfiguration_Initialization<\n  undefined,\n  FilesCoreOperations,\n  typeof FileSchema\n>({\n  mainSchema: FileSchema,\n  resourceIdentifier: CoreResourceType.FILES,\n  resourceFieldIdentifier: coreResourceShared_FieldIdentifier[CoreResourceType.FILES],\n  resourceRelationships: resourcesRelationships,\n  isSystemResource: true,\n  coreOperations: [\n    CoreResourceOperation.READ,\n    CoreResourceOperation.LIST,\n    CoreResourceOperation.CREATE,\n    CoreResourceOperation.UPDATE,\n    CoreResourceOperation.DELETE,\n  ],\n  operationsConfiguration: {\n    [CoreResourceOperation.READ]: {\n      variants: [\n        {\n          variantType: ResourceOperationVariantType.REPOSITORY_ONLY,\n          isDefault: true,\n          roles: [CORE_ORG_ROLES.ORG_MEMBER],\n          riskLevel: ResourceOperationRiskLevel.LOW,\n        },\n      ],\n    },\n    [CoreResourceOperation.LIST]: {\n      variants: [\n        {\n          variantType: ResourceOperationVariantType.REPOSITORY_ONLY,\n          isDefault: true,\n          roles: [CORE_ORG_ROLES.ORG_MEMBER],\n          riskLevel: ResourceOperationRiskLevel.LOW,\n        },\n      ],\n    },\n    [CoreResourceOperation.CREATE]: {\n      variants: [\n        {\n          variantType: ResourceOperationVariantType.REPOSITORY_ONLY,\n          isDefault: true,\n          roles: [CORE_ORG_ROLES.ORG_MEMBER],\n          riskLevel: ResourceOperationRiskLevel.LOW,\n        },\n      ],\n    },\n    [CoreResourceOperation.UPDATE]: {\n      variants: [\n        {\n          variantType: ResourceOperationVariantType.REPOSITORY_ONLY,\n          isDefault: true,\n          roles: [CORE_ORG_ROLES.ORG_MEMBER],\n          riskLevel: ResourceOperationRiskLevel.LOW,\n        },\n      ],\n    },\n    [CoreResourceOperation.DELETE]: {\n      variants: [\n        {\n          variantType: ResourceOperationVariantType.REPOSITORY_ONLY,\n          isDefault: true,\n          roles: [CORE_ORG_ROLES.ORG_MEMBER],\n          riskLevel: ResourceOperationRiskLevel.LOW,\n        },\n      ],\n    },\n  },\n});\n"]}
+{"version":3,"file":"files.shared.resources-config.schemas.js","sourceRoot":"","sources":["../../../../src/files/files.shared.resources-config.schemas.ts"],"names":[],"mappings":"AAAA;;;;;;;;;;;;;;;;;;GAkBG;AAGH,OAAO,EAAE,0CAA0C,EAAE,MAAM,8CAA8C,CAAC;AAC1G,OAAO,EAAE,qBAAqB,EAAE,gBAAgB,EAAE,kCAAkC,EAAE,MAAM,gDAAgD,CAAC;AAC7I,OAAO,EAAE,0BAA0B,EAAE,4BAA4B,EAA8C,MAAM,uCAAuC,CAAC;AAC7J,OAAO,EAAE,cAAc,EAAE,MAAM,iDAAiD,CAAC;AACjF,OAAO,EAAE,UAAU,EAAE,MAAM,wBAAwB,CAAC;AASpD;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;GAiCG;AACH,MAAM,CAAC,MAAM,gDAAgD,GAAG,CAC9D,sBAA8C,EAC9C,EAAE,CAAC,0CAA0C,CAI7C;IACA,UAAU,EAAE,UAAU;IACtB,kBAAkB,EAAE,gBAAgB,CAAC,KAAK;IAC1C,uBAAuB,EAAE,kCAAkC,CAAC,gBAAgB,CAAC,KAAK,CAAC;IACnF,qBAAqB,EAAE,sBAAsB;IAC7C,gBAAgB,EAAE,IAAI;IACtB,cAAc,EAAE;QACd,qBAAqB,CAAC,IAAI;QAC1B,qBAAqB,CAAC,IAAI;QAC1B,qBAAqB,CAAC,MAAM;QAC5B,qBAAqB,CAAC,MAAM;QAC5B,qBAAqB,CAAC,MAAM;KAC7B;IACD,uBAAuB,EAAE;QACvB,CAAC,qBAAqB,CAAC,IAAI,CAAC,EAAE;YAC5B,QAAQ,EAAE;gBACR;oBACE,WAAW,EAAE,4BAA4B,CAAC,eAAe;oBACzD,SAAS,EAAE,IAAI;oBACf,KAAK,EAAE,CAAC,cAAc,CAAC,UAAU,CAAC;oBAClC,SAAS,EAAE,0BAA0B,CAAC,GAAG;iBAC1C;aACF;SACF;QACD,CAAC,qBAAqB,CAAC,IAAI,CAAC,EAAE;YAC5B,QAAQ,EAAE;gBACR;oBACE,WAAW,EAAE,4BAA4B,CAAC,eAAe;oBACzD,SAAS,EAAE,IAAI;oBACf,KAAK,EAAE,CAAC,cAAc,CAAC,UAAU,CAAC;oBAClC,SAAS,EAAE,0BAA0B,CAAC,GAAG;iBAC1C;aACF;SACF;QACD,CAAC,qBAAqB,CAAC,MAAM,CAAC,EAAE;YAC9B,QAAQ,EAAE;gBACR;oBACE,WAAW,EAAE,4BAA4B,CAAC,eAAe;oBACzD,SAAS,EAAE,IAAI;oBACf,KAAK,EAAE,CAAC,cAAc,CAAC,UAAU,CAAC;oBAClC,SAAS,EAAE,0BAA0B,CAAC,GAAG;iBAC1C;aACF;SACF;QACD,CAAC,qBAAqB,CAAC,MAAM,CAAC,EAAE;YAC9B,QAAQ,EAAE;gBACR;oBACE,WAAW,EAAE,4BAA4B,CAAC,eAAe;oBACzD,SAAS,EAAE,IAAI;oBACf,KAAK,EAAE,CAAC,cAAc,CAAC,UAAU,CAAC;oBAClC,SAAS,EAAE,0BAA0B,CAAC,GAAG;iBAC1C;aACF;SACF;QACD,CAAC,qBAAqB,CAAC,MAAM,CAAC,EAAE;YAC9B,QAAQ,EAAE;gBACR;oBACE,WAAW,EAAE,4BAA4B,CAAC,eAAe;oBACzD,SAAS,EAAE,IAAI;oBACf,KAAK,EAAE,CAAC,cAAc,CAAC,UAAU,CAAC;oBAClC,SAAS,EAAE,0BAA0B,CAAC,GAAG;iBAC1C;aACF;SACF;KACF;CACF,CAAC,CAAC","sourcesContent":["/**\n * Files Resource Configuration (Repository-only)\n * \n * Provides repository operations for file metadata management.\n * Files are managed internally by the file upload system.\n * \n * ## Scope Model\n * \n * Files use a **dynamic scope** that is derived from the parent resource's\n * resourcePrimaryScope when linked. The canonical FILES registry relationship gives it\n * APPLICATION as its repository primaryScope, but individual file records\n * store their actual scope in the `primaryScope` field.\n * \n * This allows files to be correctly scoped to:\n * - APPLICATION: App-level shared files\n * - ORGANIZATIONS: Org-scoped files\n * - USER_SELF: User-private files\n *\n */\n\nimport { z } from 'zod';\nimport { createResourceConfiguration_Initialization } from '../resources/resources-config.shared.factory';\nimport { CoreResourceOperation, CoreResourceType, coreResourceShared_FieldIdentifier } from '../resources/resources.shared.core.definitions';\nimport { ResourceOperationRiskLevel, ResourceOperationVariantType, ResourceRelationship, ResourcePrimaryScope } from '../resources/resources.shared.schemas';\nimport { CORE_ORG_ROLES } from '../security/authorizations/roles.shared.schemas';\nimport { FileSchema } from './files.shared.schemas';\n\ntype FilesCoreOperations = \n  | CoreResourceOperation.READ\n  | CoreResourceOperation.LIST\n  | CoreResourceOperation.CREATE\n  | CoreResourceOperation.UPDATE\n  | CoreResourceOperation.DELETE;\n\n/**\n * Files Resource Configuration Factory\n * \n * Creates a REPOSITORY_ONLY resource configuration for file metadata.\n * Files are managed internally by the file upload system and not exposed\n * as standard REST API endpoints. Repository operations are used internally\n * by FilesBackendService.\n *\n * ## Persistence\n *\n * There is deliberately NO `persistenceAdapter` here: FILES FOLLOWS the application's default\n * adapter. It used to be pinned to MongoDB, on the grounds that \"file metadata relies on\n * Mongo-backed transactional/link semantics throughout the upload/link/unlink/cleanup pipeline\".\n * Measured rather than trusted, that was substantially true when written and is no longer:\n *\n * - the upload/link transaction opened on `MongoDBService` BY NAME; it now opens on whichever\n *   store FILES resolves to;\n * - the cleanup batch cleared link metadata through a raw-MongoDB `$unset`; it now uses the\n *   adapter-neutral guarded set-and-clear on the repository contract;\n * - the file-id validation was believed to require an ObjectId shape. It never did —\n *   `Resources_SharedUtils.isValidResourceId` has always accepted ObjectId AND UUID, and only the\n *   comment claimed otherwise.\n *\n * Blobs were never the issue: there is no GridFS. They live in object storage, and MongoDB held\n * only this metadata row.\n *\n * **The pin was also what forced file metadata into a SECOND store**, which is why removing it\n * closes more than it opens: a resource and its file metadata on one adapter share ONE native\n * transaction, so generated-document materialization (PDFs) stops being refused as a cross-adapter\n * boundary, and no saga or outbox is needed to make it atomic.\n *\n * An application is expected to be wholly one adapter (plan Wave 4.5). Following the default is\n * what makes that true for FILES instead of quietly exempting it.\n */\nexport const filesResourceConfiguration_InitializationFactory = (\n  resourcesRelationships: ResourceRelationship[]\n) => createResourceConfiguration_Initialization<\n  undefined,\n  FilesCoreOperations,\n  typeof FileSchema\n>({\n  mainSchema: FileSchema,\n  resourceIdentifier: CoreResourceType.FILES,\n  resourceFieldIdentifier: coreResourceShared_FieldIdentifier[CoreResourceType.FILES],\n  resourceRelationships: resourcesRelationships,\n  isSystemResource: true,\n  coreOperations: [\n    CoreResourceOperation.READ,\n    CoreResourceOperation.LIST,\n    CoreResourceOperation.CREATE,\n    CoreResourceOperation.UPDATE,\n    CoreResourceOperation.DELETE,\n  ],\n  operationsConfiguration: {\n    [CoreResourceOperation.READ]: {\n      variants: [\n        {\n          variantType: ResourceOperationVariantType.REPOSITORY_ONLY,\n          isDefault: true,\n          roles: [CORE_ORG_ROLES.ORG_MEMBER],\n          riskLevel: ResourceOperationRiskLevel.LOW,\n        },\n      ],\n    },\n    [CoreResourceOperation.LIST]: {\n      variants: [\n        {\n          variantType: ResourceOperationVariantType.REPOSITORY_ONLY,\n          isDefault: true,\n          roles: [CORE_ORG_ROLES.ORG_MEMBER],\n          riskLevel: ResourceOperationRiskLevel.LOW,\n        },\n      ],\n    },\n    [CoreResourceOperation.CREATE]: {\n      variants: [\n        {\n          variantType: ResourceOperationVariantType.REPOSITORY_ONLY,\n          isDefault: true,\n          roles: [CORE_ORG_ROLES.ORG_MEMBER],\n          riskLevel: ResourceOperationRiskLevel.LOW,\n        },\n      ],\n    },\n    [CoreResourceOperation.UPDATE]: {\n      variants: [\n        {\n          variantType: ResourceOperationVariantType.REPOSITORY_ONLY,\n          isDefault: true,\n          roles: [CORE_ORG_ROLES.ORG_MEMBER],\n          riskLevel: ResourceOperationRiskLevel.LOW,\n        },\n      ],\n    },\n    [CoreResourceOperation.DELETE]: {\n      variants: [\n        {\n          variantType: ResourceOperationVariantType.REPOSITORY_ONLY,\n          isDefault: true,\n          roles: [CORE_ORG_ROLES.ORG_MEMBER],\n          riskLevel: ResourceOperationRiskLevel.LOW,\n        },\n      ],\n    },\n  },\n});\n"]}