@wildo-ai/saas-models 1.1.4 → 1.1.6

package/dist/esm/resources/utils/dependent-lifecycle-classification.validation.js.map

@@ -0,0 +1 @@
+{"version":3,"file":"dependent-lifecycle-classification.validation.js","sourceRoot":"","sources":["../../../../../src/resources/utils/dependent-lifecycle-classification.validation.ts"],"names":[],"mappings":"AACA,OAAO,EAAE,+BAA+B,EAAE,MAAM,oCAAoC,CAAC;AACrF,OAAO,EACL,iCAAiC,EACjC,mCAAmC,GAEpC,MAAM,yDAAyD,CAAC;AACjE,OAAO,EACL,oBAAoB,GAErB,MAAM,+CAA+C,CAAC;AAyBvD;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;GAiCG;AACH,MAAM,UAAU,0CAA0C,CACxD,sBAAmF;IAEnF,MAAM,KAAK,GAAyC,EAAE,CAAC;IACvD,MAAM,QAAQ,GAAG,IAAI,GAAG,EAAU,CAAC;IAEnC,KAAK,MAAM,KAAK,IAAI,MAAM,CAAC,MAAM,CAAC,sBAAsB,CAAC,EAAE,CAAC;QAC1D,MAAM,mBAAmB,GAAG,+BAA+B,CAAC;YAC1D,mBAAmB,EAAE,KAAK,CAAC,qBAAqB,EAAE,mBAAmB,IAAI,EAAE;YAC3E,iBAAiB,EAAE,KAAK,CAAC,qBAAqB,EAAE,iBAAiB,IAAI,EAAE;YACvE,kBAAkB,EAAE,EAAE;SACvB,CAAC,CAAC;QAEH,KAAK,MAAM,YAAY,IAAI,mBAAmB,EAAE,CAAC;YAC/C,MAAM,MAAM,GAAG,sBAAsB,CAAC,YAAY,CAAC,aAAa,CAAC,CAAC;YAClE,IAAI,CAAC,MAAM,EAAE,CAAC;gBACZ,SAAS,CAAC,qDAAqD;YACjE,CAAC;YACD,IAAI,CAAC,oBAAoB,CAAC,MAAM,CAAC,EAAE,CAAC;gBAClC,SAAS,CAAC,+EAA+E;YAC3F,CAAC;YAED,8FAA8F;YAC9F,6FAA6F;YAC7F,8FAA8F;YAC9F,kDAAkD;YAClD,MAAM,cAAc,GAAG,iCAAiC,CACtD,YAAY,EACZ,CAAC,YAAY,EAAE,EAAE,CAAC,sBAAsB,CAAC,MAAM,CAAC,YAAY,CAAC,CAAC,EAAE,eAAe,CAChF,CAAC;YACF,IAAI,CAAC,mCAAmC,CAAC,cAAc,CAAC,WAAW,CAAC,EAAE,CAAC;gBACrE,SAAS;YACX,CAAC;YAED,gGAAgG;YAChG,MAAM,GAAG,GAAG,GAAG,MAAM,CAAC,YAAY,CAAC,aAAa,CAAC,IAAI,MAAM,CAAC,YAAY,CAAC,aAAa,CAAC,IAAI,MAAM,CAAC,YAAY,CAAC,eAAe,IAAI,EAAE,CAAC,EAAE,CAAC;YACxI,IAAI,QAAQ,CAAC,GAAG,CAAC,GAAG,CAAC;gBAAE,SAAS;YAChC,QAAQ,CAAC,GAAG,CAAC,GAAG,CAAC,CAAC;YAElB,KAAK,CAAC,IAAI,CAAC;gBACT,kBAAkB,EAAE,YAAY,CAAC,aAAa;gBAC9C,iBAAiB,EAAE,YAAY,CAAC,aAAa;gBAC7C,GAAG,CAAC,YAAY,CAAC,eAAe,CAAC,CAAC,CAAC,EAAE,eAAe,EAAE,YAAY,CAAC,eAAe,EAAE,CAAC,CAAC,CAAC,EAAE,CAAC;gBAC1F,WAAW,EAAE,cAAc,CAAC,WAAW;gBACvC,MAAM,EAAE,cAAc,CAAC,MAAM;aAC9B,CAAC,CAAC;QACL,CAAC;IACH,CAAC;IAED,OAAO,KAAK,CAAC;AACf,CAAC","sourcesContent":["import type { ResourceType } from '../resources.shared.core.definitions';\nimport { getParentDirectionRelationships } from '../resources-config.shared.schemas';\nimport {\n  classifySubjectErasureDisposition,\n  isBlockingSubjectErasureDisposition,\n  SubjectErasureDisposition,\n} from '../../compliance/privacy/subject-erasure.shared.schemas';\nimport {\n  canFireDeleteCascade,\n  type CompositionCascadeDeletabilityResourceInput,\n} from './composition-cascade-deletability.validation';\n\n/**\n * One DEPENDENT edge whose lifecycle nobody has classified (#1095).\n *\n * The classification is the erasure runtime's own — `classifySubjectErasureDisposition` — so the\n * report and the runtime cannot disagree about what an edge says. Two dispositions are reported,\n * exactly the ones {@link isBlockingSubjectErasureDisposition} refuses at runtime:\n *\n *  - `UNCLASSIFIED`: a COMPOSITION edge (`lifecycleModelMode: DEPENDENT`) with NO `onParentDelete`\n *    at all. `enabled` defaults to `false`, so deleting the parent leaves the children in place under\n *    a parent that no longer exists. The tenant purge dispatches the ordinary `ORGANIZATIONS | DELETE`\n *    and relies on the same cascade, so an `ORGANIZATIONS → X` edge in this state leaves X's rows\n *    behind after the tenant is destroyed; a subject erasure reaching the edge is REFUSED outright.\n *  - `UNSUPPORTED_DEFERRED`: `mode: LAZY`, which a subject erasure cannot execute.\n */\nexport interface UnclassifiedDependentLifecycleEdge {\n  parentResourceType: ResourceType;\n  childResourceType: ResourceType;\n  foreignKeyField?: string;\n  disposition: SubjectErasureDisposition;\n  /** The classifier's own justification, naming the declaration that would settle the edge. */\n  reason: string;\n}\n\n/**\n * Collect every DEPENDENT edge whose parent-delete lifecycle the author never classified — the\n * boot-time report `isBlockingSubjectErasureDisposition` was exported for (\"the erasure analogue of\n * `validateCompositionCascadeDeletability`\").\n *\n * ## Why a REPORT and not a refusal\n *\n * `validateCompositionCascadeDeletability` guards edges that OPTED IN to the cascade and cannot run\n * it. This guard is its complement: edges that never opted either way. An undeclared edge is a\n * missing declaration, and the honest reading of \"the framework asked nothing, so the author said\n * nothing\" is a gap to derive and surface, total over the registry, rather than a refusal wired\n * into boot (`application-creation-directive.md`: mark, do not block). The two runtimes that meet\n * such an edge already answer for themselves — the erasure refuses at the edge, the plain delete and\n * the tenant purge orphan silently — and the second is the one nothing reported until now.\n *\n * ## Population\n *\n * Total over every relationship of every configuration, read through the SAME helper the delete\n * cascade and the erasure walker read (`resolveRelationshipLifecycleOnParentDeleteConfig`, inside the\n * classifier). A disabled relationship is not part of the live graph and is skipped by the\n * classifier itself (`NOT_OWNED`).\n *\n * ## Parent-reachability skip, shared with the cascade-deletability guard\n *\n * The delete cascade fires only from the parent's DELETE / DELETE_MANY post-op logic. A parent that\n * can reach neither can never orphan anything, so its undeclared edges are dormant and are NOT\n * reported — `canFireDeleteCascade`, the same predicate the sibling guard uses, so the two guards\n * agree on which edges are live. Self-correcting: the day the parent gains a delete path, its dormant\n * edges are reported.\n *\n * @param resourceConfigurations - the registry's `resourceConfigurations` map (`resourceType →\n *   built configuration`). Each entry is the CHILD in its `parentRelationships` and\n *   `selfRelationships`; parents are looked up in the same map for the reachability skip.\n */\nexport function collectUnclassifiedDependentLifecycleEdges(\n  resourceConfigurations: Record<string, CompositionCascadeDeletabilityResourceInput>,\n): UnclassifiedDependentLifecycleEdge[] {\n  const edges: UnclassifiedDependentLifecycleEdge[] = [];\n  const reported = new Set<string>();\n\n  for (const child of Object.values(resourceConfigurations)) {\n    const parentRelationships = getParentDirectionRelationships({\n      parentRelationships: child.resourceRelationships?.parentRelationships ?? [],\n      selfRelationships: child.resourceRelationships?.selfRelationships ?? [],\n      childRelationships: [],\n    });\n\n    for (const relationship of parentRelationships) {\n      const parent = resourceConfigurations[relationship.resourceType1];\n      if (!parent) {\n        continue; // fail-open: parent not in this map, cannot classify\n      }\n      if (!canFireDeleteCascade(parent)) {\n        continue; // structurally unreachable edge — the parent has no delete path to orphan from\n      }\n\n      // #1279: the classifier reads the CHILD's own `retentionPolicy` — the declaration that states\n      // what an erasure does to its rows — so this guard reports exactly what the runtime will do.\n      // The map is keyed by resource type and already carries the resolved policy, so the lookup is\n      // the same one the reachability skip above makes.\n      const classification = classifySubjectErasureDisposition(\n        relationship,\n        (resourceType) => resourceConfigurations[String(resourceType)]?.retentionPolicy,\n      );\n      if (!isBlockingSubjectErasureDisposition(classification.disposition)) {\n        continue;\n      }\n\n      // The same relationship object is registered on both sides of the graph; report each edge once.\n      const key = `${String(relationship.resourceType1)}→${String(relationship.resourceType2)}:${String(relationship.foreignKeyField ?? '')}`;\n      if (reported.has(key)) continue;\n      reported.add(key);\n\n      edges.push({\n        parentResourceType: relationship.resourceType1,\n        childResourceType: relationship.resourceType2,\n        ...(relationship.foreignKeyField ? { foreignKeyField: relationship.foreignKeyField } : {}),\n        disposition: classification.disposition,\n        reason: classification.reason,\n      });\n    }\n  }\n\n  return edges;\n}\n"]}

package/dist/esm/resources/utils/duplicate-relationship-registration.validation.d.ts.map

@@ -1 +1 @@
-{"version":3,"file":"duplicate-relationship-registration.validation.d.ts","sourceRoot":"","sources":["../../../../src/resources/utils/duplicate-relationship-registration.validation.ts"],"names":[],"mappings":"AAAA,OAAO,KAAK,EAAE,oBAAoB,EAAE,YAAY,EAAE,MAAM,6BAA6B,CAAC;AAEtF;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;GAqFG;AAEH,0EAA0E;AAC1E,MAAM,WAAW,iCAAiC;IAChD,kBAAkB,EAAE,YAAY,CAAC;IACjC,iBAAiB,EAAE,YAAY,CAAC;IAChC,4FAA4F;IAC5F,WAAW,EAAE,MAAM,CAAC;IACpB,6FAA6F;IAC7F,YAAY,EAAE,oBAAoB,CAAC;IACnC,OAAO,EAAE,MAAM,CAAC;CACjB;AAqDD;;;;;;;;;;;GAWG;AACH,wBAAgB,sCAAsC,CACpD,aAAa,EAAE,SAAS,oBAAoB,EAAE,GAC7C,iCAAiC,EAAE,CAgErC"}
+{"version":3,"file":"duplicate-relationship-registration.validation.d.ts","sourceRoot":"","sources":["../../../../../src/resources/utils/duplicate-relationship-registration.validation.ts"],"names":[],"mappings":"AAAA,OAAO,KAAK,EAAE,oBAAoB,EAAE,YAAY,EAAE,MAAM,6BAA6B,CAAC;AAEtF;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;GAqFG;AAEH,0EAA0E;AAC1E,MAAM,WAAW,iCAAiC;IAChD,kBAAkB,EAAE,YAAY,CAAC;IACjC,iBAAiB,EAAE,YAAY,CAAC;IAChC,4FAA4F;IAC5F,WAAW,EAAE,MAAM,CAAC;IACpB,6FAA6F;IAC7F,YAAY,EAAE,oBAAoB,CAAC;IACnC,OAAO,EAAE,MAAM,CAAC;CACjB;AAqDD;;;;;;;;;;;GAWG;AACH,wBAAgB,sCAAsC,CACpD,aAAa,EAAE,SAAS,oBAAoB,EAAE,GAC7C,iCAAiC,EAAE,CAgErC"}

package/dist/esm/resources/utils/field-value-disclosure.utils.d.ts.map

@@ -1 +1 @@
-{"version":3,"file":"field-value-disclosure.utils.d.ts","sourceRoot":"","sources":["../../../../src/resources/utils/field-value-disclosure.utils.ts"],"names":[],"mappings":"AAAA,OAAO,KAAK,EAAE,CAAC,EAAE,MAAM,KAAK,CAAC;AAG7B;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;GA+CG;AACH,wBAAgB,0BAA0B,CAAC,WAAW,EAAE,CAAC,CAAC,UAAU,GAAG,OAAO,CAE7E"}
+{"version":3,"file":"field-value-disclosure.utils.d.ts","sourceRoot":"","sources":["../../../../../src/resources/utils/field-value-disclosure.utils.ts"],"names":[],"mappings":"AAAA,OAAO,KAAK,EAAE,CAAC,EAAE,MAAM,KAAK,CAAC;AAG7B;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;GA+CG;AACH,wBAAgB,0BAA0B,CAAC,WAAW,EAAE,CAAC,CAAC,UAAU,GAAG,OAAO,CAE7E"}

package/dist/esm/resources/utils/field-value-disclosure.utils.js.map

@@ -1 +1 @@
-{"version":3,"file":"field-value-disclosure.utils.js","sourceRoot":"","sources":["../../../../src/resources/utils/field-value-disclosure.utils.ts"],"names":[],"mappings":"AACA,OAAO,EAAE,kBAAkB,EAAE,sBAAsB,EAAE,MAAM,0BAA0B,CAAC;AAEtF;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;GA+CG;AACH,MAAM,UAAU,0BAA0B,CAAC,WAAyB;IAClE,OAAO,kBAAkB,CAAC,WAAW,CAAC,IAAI,sBAAsB,CAAC,WAAW,CAAC,CAAC;AAChF,CAAC","sourcesContent":["import type { z } from 'zod';\nimport { isBackendOnlyField, isWriteOnlySecretField } from '@wildo-ai/zod-decorators';\n\n/**\n * THE ONE RULE for \"may this field's VALUE leave the backend?\" — the disclosure seam every\n * outward-facing surface derives from, rather than restating.\n *\n * ## What it answers, and what it deliberately does not\n *\n * A field's value is non-disclosable when it is `.isBackendOnly()` (the response DTO drops it) or\n * `.isWriteOnlySecret()` (the response DTO masks it). Those two decorators ARE the disclosure\n * boundary; nothing else is. In particular:\n *\n *  - `.isHidden()` gates CHART AGGREGATES (`field-access-validator`), which is a question about\n *    which aggregate may expose a value, not about whether the value may be disclosed at all;\n *  - `.isEphemeral()` gates the audit field-access trail and a one-time frontend display. An\n *    ephemeral field is RETURNED — once, deliberately — so withholding it here would withhold\n *    something the response contract promises.\n *\n * Adding either to this predicate would silently narrow surfaces that are working as designed, so\n * they are named here as considered-and-excluded rather than left to the next reader to re-derive.\n *\n * ## Why BOTH decorators are tested, rather than one implying the other\n *\n * They are independent decorators. A future authoring form — or an application — may set one\n * without the other, and a predicate that assumed the implication would open a disclosure path the\n * day that happened. This reasoning is not new: `isFieldWithheldFromSubjectExport` wrote it down\n * for the subject-export surface first, and this module is that rule extracted so the two surfaces\n * cannot drift apart.\n *\n * ## Why it exists as its own module (issue #95)\n *\n * The rule had TWO independent hand-written copies and one surface that carried only half of it:\n *\n * | surface | `.isBackendOnly()` | `.isWriteOnlySecret()` |\n * |---|---|---|\n * | response DTO / `toResponseSafeToolOutput` (REST, MCP `tools/call`, A2A resource tools) | dropped | masked |\n * | subject export (`isFieldWithheldFromSubjectExport`) | withheld | withheld |\n * | RAG retrieval row header (`getSummaryFieldNames`) | excluded | **rendered in full** |\n *\n * The third row is the defect this module closes. A resource may declare a field BOTH\n * `.isSummaryField()` and `.isWriteOnlySecret()` — nothing forbids it — and the retrieval header\n * would then render, verbatim and into a provider payload, the value the response DTO exists to\n * mask. No resource declares that pair today, so the hole was latent; the header is assembled from\n * declarations an application controls, so it stays latent only until one does.\n *\n * assurance-control: WILDO.DATA.CONFIDENTIALITY — material a schema declares non-disclosable does\n * not cross the client boundary. The registered objective names `.isBackendOnly()`; this rule is\n * where its sibling decorator `.isWriteOnlySecret()` is held to the same boundary, since both\n * describe a value the response DTO refuses to emit as authored.\n */\nexport function isNonDisclosableFieldValue(fieldSchema: z.ZodTypeAny): boolean {\n  return isBackendOnlyField(fieldSchema) || isWriteOnlySecretField(fieldSchema);\n}\n"]}
+{"version":3,"file":"field-value-disclosure.utils.js","sourceRoot":"","sources":["../../../../../src/resources/utils/field-value-disclosure.utils.ts"],"names":[],"mappings":"AACA,OAAO,EAAE,kBAAkB,EAAE,sBAAsB,EAAE,MAAM,0BAA0B,CAAC;AAEtF;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;GA+CG;AACH,MAAM,UAAU,0BAA0B,CAAC,WAAyB;IAClE,OAAO,kBAAkB,CAAC,WAAW,CAAC,IAAI,sBAAsB,CAAC,WAAW,CAAC,CAAC;AAChF,CAAC","sourcesContent":["import type { z } from 'zod';\nimport { isBackendOnlyField, isWriteOnlySecretField } from '@wildo-ai/zod-decorators';\n\n/**\n * THE ONE RULE for \"may this field's VALUE leave the backend?\" — the disclosure seam every\n * outward-facing surface derives from, rather than restating.\n *\n * ## What it answers, and what it deliberately does not\n *\n * A field's value is non-disclosable when it is `.isBackendOnly()` (the response DTO drops it) or\n * `.isWriteOnlySecret()` (the response DTO masks it). Those two decorators ARE the disclosure\n * boundary; nothing else is. In particular:\n *\n *  - `.isHidden()` gates CHART AGGREGATES (`field-access-validator`), which is a question about\n *    which aggregate may expose a value, not about whether the value may be disclosed at all;\n *  - `.isEphemeral()` gates the audit field-access trail and a one-time frontend display. An\n *    ephemeral field is RETURNED — once, deliberately — so withholding it here would withhold\n *    something the response contract promises.\n *\n * Adding either to this predicate would silently narrow surfaces that are working as designed, so\n * they are named here as considered-and-excluded rather than left to the next reader to re-derive.\n *\n * ## Why BOTH decorators are tested, rather than one implying the other\n *\n * They are independent decorators. A future authoring form — or an application — may set one\n * without the other, and a predicate that assumed the implication would open a disclosure path the\n * day that happened. This reasoning is not new: `isFieldWithheldFromSubjectExport` wrote it down\n * for the subject-export surface first, and this module is that rule extracted so the two surfaces\n * cannot drift apart.\n *\n * ## Why it exists as its own module (issue #95)\n *\n * The rule had TWO independent hand-written copies and one surface that carried only half of it:\n *\n * | surface | `.isBackendOnly()` | `.isWriteOnlySecret()` |\n * |---|---|---|\n * | response DTO / `toResponseSafeToolOutput` (REST, MCP `tools/call`, A2A resource tools) | dropped | masked |\n * | subject export (`isFieldWithheldFromSubjectExport`) | withheld | withheld |\n * | RAG retrieval row header (`getSummaryFieldNames`) | excluded | **rendered in full** |\n *\n * The third row is the defect this module closes. A resource may declare a field BOTH\n * `.isSummaryField()` and `.isWriteOnlySecret()` — nothing forbids it — and the retrieval header\n * would then render, verbatim and into a provider payload, the value the response DTO exists to\n * mask. No resource declares that pair today, so the hole was latent; the header is assembled from\n * declarations an application controls, so it stays latent only until one does.\n *\n * assurance-control: WILDO.DATA.CONFIDENTIALITY — material a schema declares non-disclosable does\n * not cross the client boundary. The registered objective names `.isBackendOnly()`; this rule is\n * where its sibling decorator `.isWriteOnlySecret()` is held to the same boundary, since both\n * describe a value the response DTO refuses to emit as authored.\n */\nexport function isNonDisclosableFieldValue(fieldSchema: z.ZodTypeAny): boolean {\n  return isBackendOnlyField(fieldSchema) || isWriteOnlySecretField(fieldSchema);\n}\n"]}

package/dist/esm/resources/utils/http-api-write-declaration.shared.utils.d.ts

@@ -0,0 +1,103 @@
+/**
+ * The authoring contract of a WRITABLE read-through resource (#1679) — what a resource must declare
+ * before the engine will send a create, update or delete to a system of record it does not own.
+ *
+ * Checked in the resource FACTORY, at authoring, because every rule here is decidable from the one
+ * file an author is writing: the binding, the operation list and the schema. What is NOT decidable
+ * here — the instance's partition field, whether the dialect implements writes — needs the saas
+ * configuration and the engine's dialect registry, so it is checked at boot registration instead.
+ *
+ * Every refusal names the fix. A write door into somebody else's ERP is the declaration where a
+ * silently-accepted mistake costs the most, because the mistake is made against data the platform
+ * cannot restore.
+ */
+import type { z } from 'zod';
+import { HttpApiWriteVerb, type HttpApiResourceBinding } from '../../http-api-binding/http-api-binding.shared.schemas';
+import { ResourceOperationIdempotencyKeyRequirement } from '../../requests/idempotency-key.shared';
+import { CoreResourceOperation } from '../resources.shared.core.definitions';
+import { ResourceOperation_ServiceRuntimeMode } from '../resources.shared.schemas';
+/**
+ * The core operation each opened verb reaches, and the only three a read-through resource may write
+ * through. Total over {@link HttpApiWriteVerb}, so a fourth verb is a compile error here until
+ * somebody decides which operation it is.
+ */
+export declare const HTTP_API_WRITE_VERB_CORE_OPERATION: Readonly<Record<HttpApiWriteVerb, CoreResourceOperation>>;
+/**
+ * The write verb a core operation IS on a read-through resource, or `undefined` for a read.
+ *
+ * The one mapping both the authoring check and the repository's dispatch read, so the two cannot
+ * disagree about whether an operation is a write.
+ */
+export declare function resolveHttpApiWriteVerb(coreOperation: unknown): HttpApiWriteVerb | undefined;
+/** What the factory knows about ONE declared operation, reduced to what these rules read. */
+interface HttpApiWriteOperationFacts {
+    readonly operationKey: string;
+    /** The core semantics of each variant: the operation itself for a core one, `resourceOperationLike` for a custom one. */
+    readonly effectiveOperations: readonly unknown[];
+    readonly variants: ReadonlyArray<{
+        readonly idempotencyKey?: ResourceOperationIdempotencyKeyRequirement;
+        readonly haveBulkOperation?: boolean;
+    }>;
+    readonly serviceRuntimeMode?: ResourceOperation_ServiceRuntimeMode;
+}
+/**
+ * Reduce the authored operation declarations to {@link HttpApiWriteOperationFacts}.
+ *
+ * Enumerated by EFFECTIVE semantics, the way the pipeline's CLOSED-population rule enumerates
+ * creates: a core operation is its own semantics, a custom one borrows them per variant through
+ * `resourceOperationLike`, and both sources are unioned because neither sees the other's members.
+ * A custom operation that borrows UPDATE is exactly how an author would write a remote "confirm"
+ * without thinking of it as a write — so it is a write here too.
+ */
+export declare function collectHttpApiWriteOperationFacts(coreOperations: readonly unknown[], operationsConfiguration: Readonly<Record<string, unknown>> | undefined): HttpApiWriteOperationFacts[];
+/**
+ * The `Idempotency-Key` requirement a variant of a read-through WRITE carries — always REQUIRED.
+ *
+ * DERIVED rather than demanded from the author, because it has one legal value: a remote write cannot
+ * be rolled back, so a retry after a lost response must replay the first outcome instead of writing a
+ * second time, and only a required key makes every retry replayable. Asking an author to type the one
+ * answer the mechanism already knows is a question nobody should be asked (`derive-before-you-ask`).
+ * `ACCEPTED` is refused by {@link assertHttpApiWriteDeclarationCoherence}, never silently upgraded.
+ *
+ * The AUTHORED value comes first so the factory's forwarding line still reads
+ * `idempotencyKey: resolveHttpApiWriteIdempotencyKeyRequirement(variantParams.idempotencyKey, …)`, the shape
+ * `operation-variant-field-forwarding.guard.test.ts` recognises as forwarding.
+ */
+export declare function resolveHttpApiWriteIdempotencyKeyRequirement(authored: ResourceOperationIdempotencyKeyRequirement | undefined, isReadThroughWrite: boolean): ResourceOperationIdempotencyKeyRequirement | undefined;
+/**
+ * Refuse every write declaration on a read-through resource that the engine could not honour.
+ *
+ * Throws a plain `Error` naming the rule and the fix; the factory wraps it into its own configuration
+ * error with the resource identifier in front.
+ *
+ * The rules, and why each one exists:
+ *
+ *  1. **No bulk write operation**, opened or not — see {@link BULK_WRITE_OPERATIONS}. Nor a
+ *     `haveBulkOperation` twin of a write, which every tier would run as N single-row writes.
+ *  2. **Every write operation's verb is OPENED by the binding**, and **every opened verb has an
+ *     operation**. Both directions: the first is a route that would answer a refusal forever, the
+ *     second a declared door nobody can reach — and an inert declaration that looks like a control is
+ *     worse than none.
+ *  3. **Every write variant runs INLINE.** A queued or background execution cannot carry the
+ *     `Idempotency-Key`, so a retried request could not replay; the service tier refuses a key on a
+ *     non-INLINE operation already, and a key is required here.
+ *  4. **No write variant declares `Idempotency-Key: ACCEPTED`.** See
+ *     {@link resolveHttpApiWriteIdempotencyKeyRequirement}.
+ *  5. *(Moved, #2010.)* The erasure-stance rule this list carried — a binding that WRITES personal-data fields
+ *     may not declare `NO_SUBJECT_DATA` — is now `personalFieldsContradictingNoSubjectDataStance`, which the
+ *     factory applies to EVERY read-through binding and every pipeline copy. Reading those fields out of a
+ *     system that "holds no subject data" is the same contradiction as writing them into it.
+ *  6. **A `VERSION_CHECKED` binding's version field is one the UPDATE can carry and the CREATE cannot** (#1724). The
+ *     field must exist on the schema, be admitted to the update payload (the caller sends the version it read), and be
+ *     excluded from create (a new row has no version yet, and the vendor stamps it). It must be a STRING: the check
+ *     compares the caller's value byte for byte with the vendor's raw one, and a date schema would coerce it on the way
+ *     in and make every update stale. Whether it maps onto the vendor's `rowVersionField` needs the facet, and is
+ *     checked at boot.
+ */
+export declare function assertHttpApiWriteDeclarationCoherence(params: {
+    readonly binding: HttpApiResourceBinding;
+    readonly operations: readonly HttpApiWriteOperationFacts[];
+    readonly mainSchema: z.ZodTypeAny;
+}): void;
+export {};
+//# sourceMappingURL=http-api-write-declaration.shared.utils.d.ts.map

package/dist/esm/resources/utils/http-api-write-declaration.shared.utils.d.ts.map

@@ -0,0 +1 @@
+{"version":3,"file":"http-api-write-declaration.shared.utils.d.ts","sourceRoot":"","sources":["../../../../../src/resources/utils/http-api-write-declaration.shared.utils.ts"],"names":[],"mappings":"AAAA;;;;;;;;;;;;GAYG;AAEH,OAAO,KAAK,EAAE,CAAC,EAAE,MAAM,KAAK,CAAC;AAG7B,OAAO,EAEL,gBAAgB,EAChB,KAAK,sBAAsB,EAC5B,MAAM,wDAAwD,CAAC;AAChE,OAAO,EAAE,0CAA0C,EAAE,MAAM,uCAAuC,CAAC;AACnG,OAAO,EAAE,qBAAqB,EAAE,MAAM,sCAAsC,CAAC;AAC7E,OAAO,EAAE,oCAAoC,EAAE,MAAM,6BAA6B,CAAC;AAEnF;;;;GAIG;AACH,eAAO,MAAM,kCAAkC,EAAE,QAAQ,CAAC,MAAM,CAAC,gBAAgB,EAAE,qBAAqB,CAAC,CAIvG,CAAC;AAEH;;;;;GAKG;AACH,wBAAgB,uBAAuB,CAAC,aAAa,EAAE,OAAO,GAAG,gBAAgB,GAAG,SAAS,CAK5F;AAeD,6FAA6F;AAC7F,UAAU,0BAA0B;IAClC,QAAQ,CAAC,YAAY,EAAE,MAAM,CAAC;IAC9B,yHAAyH;IACzH,QAAQ,CAAC,mBAAmB,EAAE,SAAS,OAAO,EAAE,CAAC;IACjD,QAAQ,CAAC,QAAQ,EAAE,aAAa,CAAC;QAC/B,QAAQ,CAAC,cAAc,CAAC,EAAE,0CAA0C,CAAC;QACrE,QAAQ,CAAC,iBAAiB,CAAC,EAAE,OAAO,CAAC;KACtC,CAAC,CAAC;IACH,QAAQ,CAAC,kBAAkB,CAAC,EAAE,oCAAoC,CAAC;CACpE;AAED;;;;;;;;GAQG;AACH,wBAAgB,iCAAiC,CAC/C,cAAc,EAAE,SAAS,OAAO,EAAE,EAClC,uBAAuB,EAAE,QAAQ,CAAC,MAAM,CAAC,MAAM,EAAE,OAAO,CAAC,CAAC,GAAG,SAAS,GACrE,0BAA0B,EAAE,CAsB9B;AAED;;;;;;;;;;;;GAYG;AACH,wBAAgB,4CAA4C,CAC1D,QAAQ,EAAE,0CAA0C,GAAG,SAAS,EAChE,kBAAkB,EAAE,OAAO,GAC1B,0CAA0C,GAAG,SAAS,CAGxD;AAiFD;;;;;;;;;;;;;;;;;;;;;;;;;;;;;GA6BG;AACH,wBAAgB,sCAAsC,CAAC,MAAM,EAAE;IAC7D,QAAQ,CAAC,OAAO,EAAE,sBAAsB,CAAC;IACzC,QAAQ,CAAC,UAAU,EAAE,SAAS,0BAA0B,EAAE,CAAC;IAC3D,QAAQ,CAAC,UAAU,EAAE,CAAC,CAAC,UAAU,CAAC;CACnC,GAAG,IAAI,CA8GP"}

package/dist/esm/resources/utils/http-api-write-declaration.shared.utils.js

@@ -0,0 +1,275 @@
+/**
+ * The authoring contract of a WRITABLE read-through resource (#1679) — what a resource must declare
+ * before the engine will send a create, update or delete to a system of record it does not own.
+ *
+ * Checked in the resource FACTORY, at authoring, because every rule here is decidable from the one
+ * file an author is writing: the binding, the operation list and the schema. What is NOT decidable
+ * here — the instance's partition field, whether the dialect implements writes — needs the saas
+ * configuration and the engine's dialect registry, so it is checked at boot registration instead.
+ *
+ * Every refusal names the fix. A write door into somebody else's ERP is the declaration where a
+ * silently-accepted mistake costs the most, because the mistake is made against data the platform
+ * cannot restore.
+ */
+import { getZodObjectShape, isExcludedFromCreate, isExcludedFromUpdate, isZodObject, unwrapSchema } from '@wildo-ai/zod-decorators';
+import { HttpApiWriteConcurrencyMode, HttpApiWriteVerb, } from '../../http-api-binding/http-api-binding.shared.schemas.js';
+import { ResourceOperationIdempotencyKeyRequirement } from '../../requests/idempotency-key.shared.js';
+import { CoreResourceOperation } from '../resources.shared.core.definitions.js';
+import { ResourceOperation_ServiceRuntimeMode } from '../resources.shared.schemas.js';
+/**
+ * The core operation each opened verb reaches, and the only three a read-through resource may write
+ * through. Total over {@link HttpApiWriteVerb}, so a fourth verb is a compile error here until
+ * somebody decides which operation it is.
+ */
+export const HTTP_API_WRITE_VERB_CORE_OPERATION = Object.freeze({
+    [HttpApiWriteVerb.CREATE]: CoreResourceOperation.CREATE,
+    [HttpApiWriteVerb.UPDATE]: CoreResourceOperation.UPDATE,
+    [HttpApiWriteVerb.DELETE]: CoreResourceOperation.DELETE,
+});
+/**
+ * The write verb a core operation IS on a read-through resource, or `undefined` for a read.
+ *
+ * The one mapping both the authoring check and the repository's dispatch read, so the two cannot
+ * disagree about whether an operation is a write.
+ */
+export function resolveHttpApiWriteVerb(coreOperation) {
+    for (const [verb, operation] of Object.entries(HTTP_API_WRITE_VERB_CORE_OPERATION)) {
+        if (operation === coreOperation)
+            return verb;
+    }
+    return undefined;
+}
+/**
+ * The BULK write operations, refused on a read-through resource whatever the binding opens.
+ *
+ * A bulk write against a system the platform does not own is N remote calls with no atomicity: any
+ * of them can fail after the earlier ones landed, and there is no transaction to roll back into. The
+ * engine opens single-row writes only, which is what an author can reason about one row at a time.
+ */
+const BULK_WRITE_OPERATIONS = new Set([
+    CoreResourceOperation.CREATE_MANY,
+    CoreResourceOperation.UPDATE_MANY,
+    CoreResourceOperation.DELETE_MANY,
+]);
+/**
+ * Reduce the authored operation declarations to {@link HttpApiWriteOperationFacts}.
+ *
+ * Enumerated by EFFECTIVE semantics, the way the pipeline's CLOSED-population rule enumerates
+ * creates: a core operation is its own semantics, a custom one borrows them per variant through
+ * `resourceOperationLike`, and both sources are unioned because neither sees the other's members.
+ * A custom operation that borrows UPDATE is exactly how an author would write a remote "confirm"
+ * without thinking of it as a write — so it is a write here too.
+ */
+export function collectHttpApiWriteOperationFacts(coreOperations, operationsConfiguration) {
+    const facts = new Map();
+    for (const operation of coreOperations) {
+        facts.set(String(operation), { operationKey: String(operation), effectiveOperations: [operation], variants: [] });
+    }
+    for (const [operationKey, operationConfig] of Object.entries(operationsConfiguration ?? {})) {
+        const config = (operationConfig ?? {});
+        const variants = config.variants ?? [];
+        const isCore = coreOperations.includes(operationKey);
+        facts.set(operationKey, {
+            operationKey,
+            effectiveOperations: variants.length > 0 && !isCore
+                ? variants.map((variant) => variant.resourceOperationLike ?? operationKey)
+                : [operationKey],
+            variants,
+            serviceRuntimeMode: config.serviceRuntimeMode,
+        });
+    }
+    return [...facts.values()];
+}
+/**
+ * The `Idempotency-Key` requirement a variant of a read-through WRITE carries — always REQUIRED.
+ *
+ * DERIVED rather than demanded from the author, because it has one legal value: a remote write cannot
+ * be rolled back, so a retry after a lost response must replay the first outcome instead of writing a
+ * second time, and only a required key makes every retry replayable. Asking an author to type the one
+ * answer the mechanism already knows is a question nobody should be asked (`derive-before-you-ask`).
+ * `ACCEPTED` is refused by {@link assertHttpApiWriteDeclarationCoherence}, never silently upgraded.
+ *
+ * The AUTHORED value comes first so the factory's forwarding line still reads
+ * `idempotencyKey: resolveHttpApiWriteIdempotencyKeyRequirement(variantParams.idempotencyKey, …)`, the shape
+ * `operation-variant-field-forwarding.guard.test.ts` recognises as forwarding.
+ */
+export function resolveHttpApiWriteIdempotencyKeyRequirement(authored, isReadThroughWrite) {
+    if (!isReadThroughWrite)
+        return authored;
+    return ResourceOperationIdempotencyKeyRequirement.REQUIRED;
+}
+/**
+ * The operations the binding's declared actions name as their HTTP doors, keyed by operation.
+ *
+ * One operation runs one action: two actions naming the same door would make the operation's meaning depend on which
+ * one its implementation happens to hand to the executor, so it is refused here rather than decided there.
+ */
+function collectSystemOfRecordActionDoors(binding) {
+    const doors = new Map();
+    for (const [actionName, action] of Object.entries(binding.actions ?? {})) {
+        if (action.operation === undefined)
+            continue;
+        const existing = doors.get(action.operation);
+        if (existing !== undefined) {
+            throw new Error(`operation '${action.operation}' is named as the door of two actions, '${existing.actionName}' and '${actionName}'. `
+                + 'One operation runs one action; declare a second operation for the second action.');
+        }
+        doors.set(action.operation, { actionName, writes: action.writes });
+    }
+    return doors;
+}
+/**
+ * Hold an action's HTTP door to the ACTION's rules instead of the row-write rules (#1678 review, F1).
+ *
+ * A door does not write a row of the bound entity: its implementation hands the request to the system-of-record action
+ * executor, which authorizes, confines, sends and audits the action. So `writableVerbs` does not open it, and it opens
+ * nothing. What it must still be is honest about the effect it has:
+ *
+ * - a WRITING action changes remote state that cannot be rolled back, so every variant borrows a SINGLE-ROW mutation verb
+ *   (never a read: a read-shaped route is a GET and claims its repeat is harmless, and the boot validator refuses a key on
+ *   one), requires the `Idempotency-Key` (the executor refuses a writing action without one, so anything less is a door
+ *   that always refuses), and runs INLINE (a queued execution cannot carry the key);
+ * - a NON-writing action (a vendor computation) is left to the ordinary rules for the verb it borrows.
+ *
+ * Never a bulk borrow: one request is one action on one target.
+ */
+function assertSystemOfRecordActionDoorCoherence(operation, door) {
+    const bulk = operation.effectiveOperations.find((effective) => BULK_WRITE_OPERATIONS.has(effective));
+    if (bulk !== undefined) {
+        throw new Error(`operation '${operation.operationKey}' is the door of action '${door.actionName}' and borrows a bulk verb ('${String(bulk)}'). `
+            + 'One request runs one action on one target; borrow a single-row verb.');
+    }
+    if (!door.writes)
+        return;
+    const readBorrow = operation.effectiveOperations.find((effective) => resolveHttpApiWriteVerb(effective) === undefined);
+    if (readBorrow !== undefined) {
+        throw new Error(`operation '${operation.operationKey}' is the door of action '${door.actionName}', which writes, and borrows '${String(readBorrow)}', `
+            + 'which is not a mutation. A state-changing route must not be read-shaped: it would be a GET, and a required Idempotency-Key '
+            + 'on a read is refused at boot. Borrow update (an action on one record) or create (an action that makes one) in resourceOperationLike.');
+    }
+    const unkeyed = operation.variants.find((variant) => variant.idempotencyKey !== ResourceOperationIdempotencyKeyRequirement.REQUIRED);
+    if (unkeyed !== undefined) {
+        throw new Error(`operation '${operation.operationKey}' is the door of action '${door.actionName}', which writes, and does not require an `
+            + 'Idempotency-Key on every variant. The executor refuses a writing action without one, so the route would refuse every request; '
+            + `declare idempotencyKey: '${ResourceOperationIdempotencyKeyRequirement.REQUIRED}'.`);
+    }
+    if (operation.serviceRuntimeMode !== undefined
+        && operation.serviceRuntimeMode !== ResourceOperation_ServiceRuntimeMode.INLINE) {
+        throw new Error(`operation '${operation.operationKey}' is the door of action '${door.actionName}' and runs '${operation.serviceRuntimeMode}'. `
+            + 'A writing action runs INLINE: a queued or background execution cannot carry its Idempotency-Key. Remove serviceRuntimeMode.');
+    }
+}
+/**
+ * Refuse every write declaration on a read-through resource that the engine could not honour.
+ *
+ * Throws a plain `Error` naming the rule and the fix; the factory wraps it into its own configuration
+ * error with the resource identifier in front.
+ *
+ * The rules, and why each one exists:
+ *
+ *  1. **No bulk write operation**, opened or not — see {@link BULK_WRITE_OPERATIONS}. Nor a
+ *     `haveBulkOperation` twin of a write, which every tier would run as N single-row writes.
+ *  2. **Every write operation's verb is OPENED by the binding**, and **every opened verb has an
+ *     operation**. Both directions: the first is a route that would answer a refusal forever, the
+ *     second a declared door nobody can reach — and an inert declaration that looks like a control is
+ *     worse than none.
+ *  3. **Every write variant runs INLINE.** A queued or background execution cannot carry the
+ *     `Idempotency-Key`, so a retried request could not replay; the service tier refuses a key on a
+ *     non-INLINE operation already, and a key is required here.
+ *  4. **No write variant declares `Idempotency-Key: ACCEPTED`.** See
+ *     {@link resolveHttpApiWriteIdempotencyKeyRequirement}.
+ *  5. *(Moved, #2010.)* The erasure-stance rule this list carried — a binding that WRITES personal-data fields
+ *     may not declare `NO_SUBJECT_DATA` — is now `personalFieldsContradictingNoSubjectDataStance`, which the
+ *     factory applies to EVERY read-through binding and every pipeline copy. Reading those fields out of a
+ *     system that "holds no subject data" is the same contradiction as writing them into it.
+ *  6. **A `VERSION_CHECKED` binding's version field is one the UPDATE can carry and the CREATE cannot** (#1724). The
+ *     field must exist on the schema, be admitted to the update payload (the caller sends the version it read), and be
+ *     excluded from create (a new row has no version yet, and the vendor stamps it). It must be a STRING: the check
+ *     compares the caller's value byte for byte with the vendor's raw one, and a date schema would coerce it on the way
+ *     in and make every update stale. Whether it maps onto the vendor's `rowVersionField` needs the facet, and is
+ *     checked at boot.
+ */
+export function assertHttpApiWriteDeclarationCoherence(params) {
+    const { binding, operations, mainSchema } = params;
+    const opened = new Set(binding.writableVerbs);
+    const reached = new Set();
+    const actionDoors = collectSystemOfRecordActionDoors(binding);
+    // Checked BEFORE the operations: a door named after a missing operation usually means the author mistyped it, and the
+    // operation they meant would otherwise be refused first as an unopened row write — a message about the wrong thing.
+    const declaredOperationKeys = new Set(operations.map((operation) => operation.operationKey));
+    for (const [operationKey, door] of actionDoors) {
+        if (!declaredOperationKeys.has(operationKey)) {
+            throw new Error(`actions.${door.actionName} names '${operationKey}' as its door, and this resource declares no such operation. `
+                + 'Declare the custom operation, or remove the `operation` from the action.');
+        }
+    }
+    for (const operation of operations) {
+        const door = actionDoors.get(operation.operationKey);
+        if (door !== undefined) {
+            assertSystemOfRecordActionDoorCoherence(operation, door);
+            continue;
+        }
+        const bulk = operation.effectiveOperations.find((effective) => BULK_WRITE_OPERATIONS.has(effective));
+        if (bulk !== undefined) {
+            throw new Error(`operation '${operation.operationKey}' is a bulk write ('${String(bulk)}'), which a read-through resource never runs: `
+                + 'N remote writes have no transaction to roll back into when one of them fails after the others landed. '
+                + 'Declare the single-row create/update/delete instead.');
+        }
+        const verbs = operation.effectiveOperations
+            .map((effective) => resolveHttpApiWriteVerb(effective))
+            .filter((verb) => verb !== undefined);
+        if (verbs.length === 0)
+            continue;
+        for (const verb of verbs) {
+            if (!opened.has(verb)) {
+                throw new Error(`operation '${operation.operationKey}' writes ('${verb}'), and httpApiBinding.writableVerbs does not open '${verb}'. `
+                    + `Add '${verb}' to writableVerbs to open the write toward '${binding.system}', or remove the operation.`);
+            }
+            reached.add(verb);
+        }
+        if (operation.variants.some((variant) => variant.haveBulkOperation === true)) {
+            throw new Error(`operation '${operation.operationKey}' declares a bulk twin (haveBulkOperation), which a read-through resource never runs — `
+                + 'one request would become N remote writes with no atomicity. Remove haveBulkOperation.');
+        }
+        if (operation.serviceRuntimeMode !== undefined
+            && operation.serviceRuntimeMode !== ResourceOperation_ServiceRuntimeMode.INLINE) {
+            throw new Error(`operation '${operation.operationKey}' writes to '${binding.system}' with serviceRuntimeMode '${operation.serviceRuntimeMode}'. `
+                + 'A remote write runs INLINE: its Idempotency-Key is required, and a queued or background execution cannot carry one, '
+                + 'so a retried request could not replay its first outcome. Remove serviceRuntimeMode.');
+        }
+        const accepted = operation.variants.find((variant) => variant.idempotencyKey === ResourceOperationIdempotencyKeyRequirement.ACCEPTED);
+        if (accepted !== undefined) {
+            throw new Error(`operation '${operation.operationKey}' declares idempotencyKey 'accepted'. A write to a system of record cannot be rolled back, `
+                + 'so every retry must replay the first outcome: the key is REQUIRED on every write variant, and the engine sets it for you. '
+                + 'Remove the idempotencyKey declaration.');
+        }
+    }
+    for (const verb of opened) {
+        if (!reached.has(verb)) {
+            throw new Error(`httpApiBinding.writableVerbs opens '${verb}', and no operation of this resource performs it. An opened write nobody can `
+                + `reach is a declaration that decides nothing; declare the ${HTTP_API_WRITE_VERB_CORE_OPERATION[verb]} operation, or remove the verb.`);
+        }
+    }
+    if (binding.writeConcurrency?.mode === HttpApiWriteConcurrencyMode.VERSION_CHECKED && isZodObject(mainSchema)) {
+        const versionField = binding.writeConcurrency.versionField;
+        const fieldSchema = getZodObjectShape(mainSchema)[versionField];
+        if (fieldSchema === undefined) {
+            throw new Error(`httpApiBinding.writeConcurrency.versionField names '${versionField}', which this resource's schema does not declare. `
+                + 'Declare the field (mapped to the vendor\'s row version, e.g. Odoo `write_date`) so a caller can read it and send it back.');
+        }
+        const unwrapped = unwrapSchema(fieldSchema);
+        if (unwrapped?._zod?.def?.type !== 'string') {
+            throw new Error(`httpApiBinding.writeConcurrency.versionField '${versionField}' must be a string schema: the version is compared byte for `
+                + 'byte with what the vendor served (Odoo `write_date`, "YYYY-MM-DD HH:MM:SS"), and a date or number schema would re-format it.');
+        }
+        if (isExcludedFromUpdate(fieldSchema)) {
+            throw new Error(`httpApiBinding.writeConcurrency.versionField '${versionField}' is excluded from UPDATE, so no caller could send the version `
+                + 'it read and every update would be refused. Remove .excludeFromUpdate() from it.');
+        }
+        if (opened.has(HttpApiWriteVerb.CREATE) && !isExcludedFromCreate(fieldSchema)) {
+            throw new Error(`httpApiBinding.writeConcurrency.versionField '${versionField}' may be sent on CREATE, and a new row has no version: the `
+                + 'vendor stamps it. Declare it .excludeFromCreate().');
+        }
+    }
+}
+//# sourceMappingURL=http-api-write-declaration.shared.utils.js.map

package/dist/esm/resources/utils/http-api-write-declaration.shared.utils.js.map

@@ -0,0 +1 @@
+{"version":3,"file":"http-api-write-declaration.shared.utils.js","sourceRoot":"","sources":["../../../../../src/resources/utils/http-api-write-declaration.shared.utils.ts"],"names":[],"mappings":"AAAA;;;;;;;;;;;;GAYG;AAGH,OAAO,EAAE,iBAAiB,EAAE,oBAAoB,EAAE,oBAAoB,EAAE,WAAW,EAAE,YAAY,EAAE,MAAM,0BAA0B,CAAC;AAEpI,OAAO,EACL,2BAA2B,EAC3B,gBAAgB,GAEjB,MAAM,wDAAwD,CAAC;AAChE,OAAO,EAAE,0CAA0C,EAAE,MAAM,uCAAuC,CAAC;AACnG,OAAO,EAAE,qBAAqB,EAAE,MAAM,sCAAsC,CAAC;AAC7E,OAAO,EAAE,oCAAoC,EAAE,MAAM,6BAA6B,CAAC;AAEnF;;;;GAIG;AACH,MAAM,CAAC,MAAM,kCAAkC,GAA8D,MAAM,CAAC,MAAM,CAAC;IACzH,CAAC,gBAAgB,CAAC,MAAM,CAAC,EAAE,qBAAqB,CAAC,MAAM;IACvD,CAAC,gBAAgB,CAAC,MAAM,CAAC,EAAE,qBAAqB,CAAC,MAAM;IACvD,CAAC,gBAAgB,CAAC,MAAM,CAAC,EAAE,qBAAqB,CAAC,MAAM;CACxD,CAAC,CAAC;AAEH;;;;;GAKG;AACH,MAAM,UAAU,uBAAuB,CAAC,aAAsB;IAC5D,KAAK,MAAM,CAAC,IAAI,EAAE,SAAS,CAAC,IAAI,MAAM,CAAC,OAAO,CAAC,kCAAkC,CAAqD,EAAE,CAAC;QACvI,IAAI,SAAS,KAAK,aAAa;YAAE,OAAO,IAAI,CAAC;IAC/C,CAAC;IACD,OAAO,SAAS,CAAC;AACnB,CAAC;AAED;;;;;;GAMG;AACH,MAAM,qBAAqB,GAAyB,IAAI,GAAG,CAAU;IACnE,qBAAqB,CAAC,WAAW;IACjC,qBAAqB,CAAC,WAAW;IACjC,qBAAqB,CAAC,WAAW;CAClC,CAAC,CAAC;AAcH;;;;;;;;GAQG;AACH,MAAM,UAAU,iCAAiC,CAC/C,cAAkC,EAClC,uBAAsE;IAEtE,MAAM,KAAK,GAAG,IAAI,GAAG,EAAsC,CAAC;IAC5D,KAAK,MAAM,SAAS,IAAI,cAAc,EAAE,CAAC;QACvC,KAAK,CAAC,GAAG,CAAC,MAAM,CAAC,SAAS,CAAC,EAAE,EAAE,YAAY,EAAE,MAAM,CAAC,SAAS,CAAC,EAAE,mBAAmB,EAAE,CAAC,SAAS,CAAC,EAAE,QAAQ,EAAE,EAAE,EAAE,CAAC,CAAC;IACpH,CAAC;IACD,KAAK,MAAM,CAAC,YAAY,EAAE,eAAe,CAAC,IAAI,MAAM,CAAC,OAAO,CAAC,uBAAuB,IAAI,EAAE,CAAC,EAAE,CAAC;QAC5F,MAAM,MAAM,GAAG,CAAC,eAAe,IAAI,EAAE,CAGpC,CAAC;QACF,MAAM,QAAQ,GAAG,MAAM,CAAC,QAAQ,IAAI,EAAE,CAAC;QACvC,MAAM,MAAM,GAAG,cAAc,CAAC,QAAQ,CAAC,YAAY,CAAC,CAAC;QACrD,KAAK,CAAC,GAAG,CAAC,YAAY,EAAE;YACtB,YAAY;YACZ,mBAAmB,EAAE,QAAQ,CAAC,MAAM,GAAG,CAAC,IAAI,CAAC,MAAM;gBACjD,CAAC,CAAC,QAAQ,CAAC,GAAG,CAAC,CAAC,OAAO,EAAE,EAAE,CAAC,OAAO,CAAC,qBAAqB,IAAI,YAAY,CAAC;gBAC1E,CAAC,CAAC,CAAC,YAAY,CAAC;YAClB,QAAQ;YACR,kBAAkB,EAAE,MAAM,CAAC,kBAAkB;SAC9C,CAAC,CAAC;IACL,CAAC;IACD,OAAO,CAAC,GAAG,KAAK,CAAC,MAAM,EAAE,CAAC,CAAC;AAC7B,CAAC;AAED;;;;;;;;;;;;GAYG;AACH,MAAM,UAAU,4CAA4C,CAC1D,QAAgE,EAChE,kBAA2B;IAE3B,IAAI,CAAC,kBAAkB;QAAE,OAAO,QAAQ,CAAC;IACzC,OAAO,0CAA0C,CAAC,QAAQ,CAAC;AAC7D,CAAC;AAQD;;;;;GAKG;AACH,SAAS,gCAAgC,CAAC,OAA+B;IACvE,MAAM,KAAK,GAAG,IAAI,GAAG,EAAoC,CAAC;IAC1D,KAAK,MAAM,CAAC,UAAU,EAAE,MAAM,CAAC,IAAI,MAAM,CAAC,OAAO,CAAC,OAAO,CAAC,OAAO,IAAI,EAAE,CAAC,EAAE,CAAC;QACzE,IAAI,MAAM,CAAC,SAAS,KAAK,SAAS;YAAE,SAAS;QAC7C,MAAM,QAAQ,GAAG,KAAK,CAAC,GAAG,CAAC,MAAM,CAAC,SAAS,CAAC,CAAC;QAC7C,IAAI,QAAQ,KAAK,SAAS,EAAE,CAAC;YAC3B,MAAM,IAAI,KAAK,CACb,cAAc,MAAM,CAAC,SAAS,2CAA2C,QAAQ,CAAC,UAAU,UAAU,UAAU,KAAK;kBACnH,kFAAkF,CACrF,CAAC;QACJ,CAAC;QACD,KAAK,CAAC,GAAG,CAAC,MAAM,CAAC,SAAS,EAAE,EAAE,UAAU,EAAE,MAAM,EAAE,MAAM,CAAC,MAAM,EAAE,CAAC,CAAC;IACrE,CAAC;IACD,OAAO,KAAK,CAAC;AACf,CAAC;AAED;;;;;;;;;;;;;;GAcG;AACH,SAAS,uCAAuC,CAAC,SAAqC,EAAE,IAA8B;IACpH,MAAM,IAAI,GAAG,SAAS,CAAC,mBAAmB,CAAC,IAAI,CAAC,CAAC,SAAS,EAAE,EAAE,CAAC,qBAAqB,CAAC,GAAG,CAAC,SAAS,CAAC,CAAC,CAAC;IACrG,IAAI,IAAI,KAAK,SAAS,EAAE,CAAC;QACvB,MAAM,IAAI,KAAK,CACb,cAAc,SAAS,CAAC,YAAY,4BAA4B,IAAI,CAAC,UAAU,+BAA+B,MAAM,CAAC,IAAI,CAAC,MAAM;cAC9H,sEAAsE,CACzE,CAAC;IACJ,CAAC;IACD,IAAI,CAAC,IAAI,CAAC,MAAM;QAAE,OAAO;IACzB,MAAM,UAAU,GAAG,SAAS,CAAC,mBAAmB,CAAC,IAAI,CAAC,CAAC,SAAS,EAAE,EAAE,CAAC,uBAAuB,CAAC,SAAS,CAAC,KAAK,SAAS,CAAC,CAAC;IACvH,IAAI,UAAU,KAAK,SAAS,EAAE,CAAC;QAC7B,MAAM,IAAI,KAAK,CACb,cAAc,SAAS,CAAC,YAAY,4BAA4B,IAAI,CAAC,UAAU,iCAAiC,MAAM,CAAC,UAAU,CAAC,KAAK;cACrI,6HAA6H;cAC7H,sIAAsI,CACzI,CAAC;IACJ,CAAC;IACD,MAAM,OAAO,GAAG,SAAS,CAAC,QAAQ,CAAC,IAAI,CAAC,CAAC,OAAO,EAAE,EAAE,CAAC,OAAO,CAAC,cAAc,KAAK,0CAA0C,CAAC,QAAQ,CAAC,CAAC;IACrI,IAAI,OAAO,KAAK,SAAS,EAAE,CAAC;QAC1B,MAAM,IAAI,KAAK,CACb,cAAc,SAAS,CAAC,YAAY,4BAA4B,IAAI,CAAC,UAAU,2CAA2C;cACxH,gIAAgI;cAChI,4BAA4B,0CAA0C,CAAC,QAAQ,IAAI,CACtF,CAAC;IACJ,CAAC;IACD,IACE,SAAS,CAAC,kBAAkB,KAAK,SAAS;WACvC,SAAS,CAAC,kBAAkB,KAAK,oCAAoC,CAAC,MAAM,EAC/E,CAAC;QACD,MAAM,IAAI,KAAK,CACb,cAAc,SAAS,CAAC,YAAY,4BAA4B,IAAI,CAAC,UAAU,eAAe,SAAS,CAAC,kBAAkB,KAAK;cAC7H,6HAA6H,CAChI,CAAC;IACJ,CAAC;AACH,CAAC;AAED;;;;;;;;;;;;;;;;;;;;;;;;;;;;;GA6BG;AACH,MAAM,UAAU,sCAAsC,CAAC,MAItD;IACC,MAAM,EAAE,OAAO,EAAE,UAAU,EAAE,UAAU,EAAE,GAAG,MAAM,CAAC;IACnD,MAAM,MAAM,GAAG,IAAI,GAAG,CAAmB,OAAO,CAAC,aAAa,CAAC,CAAC;IAChE,MAAM,OAAO,GAAG,IAAI,GAAG,EAAoB,CAAC;IAC5C,MAAM,WAAW,GAAG,gCAAgC,CAAC,OAAO,CAAC,CAAC;IAC9D,sHAAsH;IACtH,oHAAoH;IACpH,MAAM,qBAAqB,GAAG,IAAI,GAAG,CAAC,UAAU,CAAC,GAAG,CAAC,CAAC,SAAS,EAAE,EAAE,CAAC,SAAS,CAAC,YAAY,CAAC,CAAC,CAAC;IAC7F,KAAK,MAAM,CAAC,YAAY,EAAE,IAAI,CAAC,IAAI,WAAW,EAAE,CAAC;QAC/C,IAAI,CAAC,qBAAqB,CAAC,GAAG,CAAC,YAAY,CAAC,EAAE,CAAC;YAC7C,MAAM,IAAI,KAAK,CACb,WAAW,IAAI,CAAC,UAAU,WAAW,YAAY,+DAA+D;kBAC9G,0EAA0E,CAC7E,CAAC;QACJ,CAAC;IACH,CAAC;IAED,KAAK,MAAM,SAAS,IAAI,UAAU,EAAE,CAAC;QACnC,MAAM,IAAI,GAAG,WAAW,CAAC,GAAG,CAAC,SAAS,CAAC,YAAY,CAAC,CAAC;QACrD,IAAI,IAAI,KAAK,SAAS,EAAE,CAAC;YACvB,uCAAuC,CAAC,SAAS,EAAE,IAAI,CAAC,CAAC;YACzD,SAAS;QACX,CAAC;QACD,MAAM,IAAI,GAAG,SAAS,CAAC,mBAAmB,CAAC,IAAI,CAAC,CAAC,SAAS,EAAE,EAAE,CAAC,qBAAqB,CAAC,GAAG,CAAC,SAAS,CAAC,CAAC,CAAC;QACrG,IAAI,IAAI,KAAK,SAAS,EAAE,CAAC;YACvB,MAAM,IAAI,KAAK,CACb,cAAc,SAAS,CAAC,YAAY,uBAAuB,MAAM,CAAC,IAAI,CAAC,gDAAgD;kBACrH,wGAAwG;kBACxG,sDAAsD,CACzD,CAAC;QACJ,CAAC;QACD,MAAM,KAAK,GAAG,SAAS,CAAC,mBAAmB;aACxC,GAAG,CAAC,CAAC,SAAS,EAAE,EAAE,CAAC,uBAAuB,CAAC,SAAS,CAAC,CAAC;aACtD,MAAM,CAAC,CAAC,IAAI,EAA4B,EAAE,CAAC,IAAI,KAAK,SAAS,CAAC,CAAC;QAClE,IAAI,KAAK,CAAC,MAAM,KAAK,CAAC;YAAE,SAAS;QAEjC,KAAK,MAAM,IAAI,IAAI,KAAK,EAAE,CAAC;YACzB,IAAI,CAAC,MAAM,CAAC,GAAG,CAAC,IAAI,CAAC,EAAE,CAAC;gBACtB,MAAM,IAAI,KAAK,CACb,cAAc,SAAS,CAAC,YAAY,cAAc,IAAI,uDAAuD,IAAI,KAAK;sBACpH,QAAQ,IAAI,gDAAgD,OAAO,CAAC,MAAM,6BAA6B,CAC1G,CAAC;YACJ,CAAC;YACD,OAAO,CAAC,GAAG,CAAC,IAAI,CAAC,CAAC;QACpB,CAAC;QACD,IAAI,SAAS,CAAC,QAAQ,CAAC,IAAI,CAAC,CAAC,OAAO,EAAE,EAAE,CAAC,OAAO,CAAC,iBAAiB,KAAK,IAAI,CAAC,EAAE,CAAC;YAC7E,MAAM,IAAI,KAAK,CACb,cAAc,SAAS,CAAC,YAAY,yFAAyF;kBAC3H,uFAAuF,CAC1F,CAAC;QACJ,CAAC;QACD,IACE,SAAS,CAAC,kBAAkB,KAAK,SAAS;eACvC,SAAS,CAAC,kBAAkB,KAAK,oCAAoC,CAAC,MAAM,EAC/E,CAAC;YACD,MAAM,IAAI,KAAK,CACb,cAAc,SAAS,CAAC,YAAY,gBAAgB,OAAO,CAAC,MAAM,8BAA8B,SAAS,CAAC,kBAAkB,KAAK;kBAC/H,sHAAsH;kBACtH,qFAAqF,CACxF,CAAC;QACJ,CAAC;QACD,MAAM,QAAQ,GAAG,SAAS,CAAC,QAAQ,CAAC,IAAI,CAAC,CAAC,OAAO,EAAE,EAAE,CAAC,OAAO,CAAC,cAAc,KAAK,0CAA0C,CAAC,QAAQ,CAAC,CAAC;QACtI,IAAI,QAAQ,KAAK,SAAS,EAAE,CAAC;YAC3B,MAAM,IAAI,KAAK,CACb,cAAc,SAAS,CAAC,YAAY,6FAA6F;kBAC/H,4HAA4H;kBAC5H,wCAAwC,CAC3C,CAAC;QACJ,CAAC;IACH,CAAC;IAED,KAAK,MAAM,IAAI,IAAI,MAAM,EAAE,CAAC;QAC1B,IAAI,CAAC,OAAO,CAAC,GAAG,CAAC,IAAI,CAAC,EAAE,CAAC;YACvB,MAAM,IAAI,KAAK,CACb,uCAAuC,IAAI,+EAA+E;kBACxH,4DAA4D,kCAAkC,CAAC,IAAI,CAAC,iCAAiC,CACxI,CAAC;QACJ,CAAC;IACH,CAAC;IAED,IAAI,OAAO,CAAC,gBAAgB,EAAE,IAAI,KAAK,2BAA2B,CAAC,eAAe,IAAI,WAAW,CAAC,UAAU,CAAC,EAAE,CAAC;QAC9G,MAAM,YAAY,GAAG,OAAO,CAAC,gBAAgB,CAAC,YAAY,CAAC;QAC3D,MAAM,WAAW,GAAG,iBAAiB,CAAC,UAAU,CAAC,CAAC,YAAY,CAA6B,CAAC;QAC5F,IAAI,WAAW,KAAK,SAAS,EAAE,CAAC;YAC9B,MAAM,IAAI,KAAK,CACb,uDAAuD,YAAY,oDAAoD;kBACrH,2HAA2H,CAC9H,CAAC;QACJ,CAAC;QACD,MAAM,SAAS,GAAG,YAAY,CAAC,WAAoB,CAA4C,CAAC;QAChG,IAAI,SAAS,EAAE,IAAI,EAAE,GAAG,EAAE,IAAI,KAAK,QAAQ,EAAE,CAAC;YAC5C,MAAM,IAAI,KAAK,CACb,iDAAiD,YAAY,8DAA8D;kBACzH,8HAA8H,CACjI,CAAC;QACJ,CAAC;QACD,IAAI,oBAAoB,CAAC,WAAW,CAAC,EAAE,CAAC;YACtC,MAAM,IAAI,KAAK,CACb,iDAAiD,YAAY,iEAAiE;kBAC5H,iFAAiF,CACpF,CAAC;QACJ,CAAC;QACD,IAAI,MAAM,CAAC,GAAG,CAAC,gBAAgB,CAAC,MAAM,CAAC,IAAI,CAAC,oBAAoB,CAAC,WAAW,CAAC,EAAE,CAAC;YAC9E,MAAM,IAAI,KAAK,CACb,iDAAiD,YAAY,6DAA6D;kBACxH,oDAAoD,CACvD,CAAC;QACJ,CAAC;IACH,CAAC;AAEH,CAAC","sourcesContent":["/**\n * The authoring contract of a WRITABLE read-through resource (#1679) — what a resource must declare\n * before the engine will send a create, update or delete to a system of record it does not own.\n *\n * Checked in the resource FACTORY, at authoring, because every rule here is decidable from the one\n * file an author is writing: the binding, the operation list and the schema. What is NOT decidable\n * here — the instance's partition field, whether the dialect implements writes — needs the saas\n * configuration and the engine's dialect registry, so it is checked at boot registration instead.\n *\n * Every refusal names the fix. A write door into somebody else's ERP is the declaration where a\n * silently-accepted mistake costs the most, because the mistake is made against data the platform\n * cannot restore.\n */\n\nimport type { z } from 'zod';\nimport { getZodObjectShape, isExcludedFromCreate, isExcludedFromUpdate, isZodObject, unwrapSchema } from '@wildo-ai/zod-decorators';\n\nimport {\n  HttpApiWriteConcurrencyMode,\n  HttpApiWriteVerb,\n  type HttpApiResourceBinding,\n} from '../../http-api-binding/http-api-binding.shared.schemas';\nimport { ResourceOperationIdempotencyKeyRequirement } from '../../requests/idempotency-key.shared';\nimport { CoreResourceOperation } from '../resources.shared.core.definitions';\nimport { ResourceOperation_ServiceRuntimeMode } from '../resources.shared.schemas';\n\n/**\n * The core operation each opened verb reaches, and the only three a read-through resource may write\n * through. Total over {@link HttpApiWriteVerb}, so a fourth verb is a compile error here until\n * somebody decides which operation it is.\n */\nexport const HTTP_API_WRITE_VERB_CORE_OPERATION: Readonly<Record<HttpApiWriteVerb, CoreResourceOperation>> = Object.freeze({\n  [HttpApiWriteVerb.CREATE]: CoreResourceOperation.CREATE,\n  [HttpApiWriteVerb.UPDATE]: CoreResourceOperation.UPDATE,\n  [HttpApiWriteVerb.DELETE]: CoreResourceOperation.DELETE,\n});\n\n/**\n * The write verb a core operation IS on a read-through resource, or `undefined` for a read.\n *\n * The one mapping both the authoring check and the repository's dispatch read, so the two cannot\n * disagree about whether an operation is a write.\n */\nexport function resolveHttpApiWriteVerb(coreOperation: unknown): HttpApiWriteVerb | undefined {\n  for (const [verb, operation] of Object.entries(HTTP_API_WRITE_VERB_CORE_OPERATION) as Array<[HttpApiWriteVerb, CoreResourceOperation]>) {\n    if (operation === coreOperation) return verb;\n  }\n  return undefined;\n}\n\n/**\n * The BULK write operations, refused on a read-through resource whatever the binding opens.\n *\n * A bulk write against a system the platform does not own is N remote calls with no atomicity: any\n * of them can fail after the earlier ones landed, and there is no transaction to roll back into. The\n * engine opens single-row writes only, which is what an author can reason about one row at a time.\n */\nconst BULK_WRITE_OPERATIONS: ReadonlySet<unknown> = new Set<unknown>([\n  CoreResourceOperation.CREATE_MANY,\n  CoreResourceOperation.UPDATE_MANY,\n  CoreResourceOperation.DELETE_MANY,\n]);\n\n/** What the factory knows about ONE declared operation, reduced to what these rules read. */\ninterface HttpApiWriteOperationFacts {\n  readonly operationKey: string;\n  /** The core semantics of each variant: the operation itself for a core one, `resourceOperationLike` for a custom one. */\n  readonly effectiveOperations: readonly unknown[];\n  readonly variants: ReadonlyArray<{\n    readonly idempotencyKey?: ResourceOperationIdempotencyKeyRequirement;\n    readonly haveBulkOperation?: boolean;\n  }>;\n  readonly serviceRuntimeMode?: ResourceOperation_ServiceRuntimeMode;\n}\n\n/**\n * Reduce the authored operation declarations to {@link HttpApiWriteOperationFacts}.\n *\n * Enumerated by EFFECTIVE semantics, the way the pipeline's CLOSED-population rule enumerates\n * creates: a core operation is its own semantics, a custom one borrows them per variant through\n * `resourceOperationLike`, and both sources are unioned because neither sees the other's members.\n * A custom operation that borrows UPDATE is exactly how an author would write a remote \"confirm\"\n * without thinking of it as a write — so it is a write here too.\n */\nexport function collectHttpApiWriteOperationFacts(\n  coreOperations: readonly unknown[],\n  operationsConfiguration: Readonly<Record<string, unknown>> | undefined,\n): HttpApiWriteOperationFacts[] {\n  const facts = new Map<string, HttpApiWriteOperationFacts>();\n  for (const operation of coreOperations) {\n    facts.set(String(operation), { operationKey: String(operation), effectiveOperations: [operation], variants: [] });\n  }\n  for (const [operationKey, operationConfig] of Object.entries(operationsConfiguration ?? {})) {\n    const config = (operationConfig ?? {}) as {\n      variants?: Array<{ resourceOperationLike?: unknown; idempotencyKey?: ResourceOperationIdempotencyKeyRequirement; haveBulkOperation?: boolean }>;\n      serviceRuntimeMode?: ResourceOperation_ServiceRuntimeMode;\n    };\n    const variants = config.variants ?? [];\n    const isCore = coreOperations.includes(operationKey);\n    facts.set(operationKey, {\n      operationKey,\n      effectiveOperations: variants.length > 0 && !isCore\n        ? variants.map((variant) => variant.resourceOperationLike ?? operationKey)\n        : [operationKey],\n      variants,\n      serviceRuntimeMode: config.serviceRuntimeMode,\n    });\n  }\n  return [...facts.values()];\n}\n\n/**\n * The `Idempotency-Key` requirement a variant of a read-through WRITE carries — always REQUIRED.\n *\n * DERIVED rather than demanded from the author, because it has one legal value: a remote write cannot\n * be rolled back, so a retry after a lost response must replay the first outcome instead of writing a\n * second time, and only a required key makes every retry replayable. Asking an author to type the one\n * answer the mechanism already knows is a question nobody should be asked (`derive-before-you-ask`).\n * `ACCEPTED` is refused by {@link assertHttpApiWriteDeclarationCoherence}, never silently upgraded.\n *\n * The AUTHORED value comes first so the factory's forwarding line still reads\n * `idempotencyKey: resolveHttpApiWriteIdempotencyKeyRequirement(variantParams.idempotencyKey, …)`, the shape\n * `operation-variant-field-forwarding.guard.test.ts` recognises as forwarding.\n */\nexport function resolveHttpApiWriteIdempotencyKeyRequirement(\n  authored: ResourceOperationIdempotencyKeyRequirement | undefined,\n  isReadThroughWrite: boolean,\n): ResourceOperationIdempotencyKeyRequirement | undefined {\n  if (!isReadThroughWrite) return authored;\n  return ResourceOperationIdempotencyKeyRequirement.REQUIRED;\n}\n\n/** A resource operation a declared system-of-record action names as its HTTP door (`actions.<name>.operation`). */\ninterface SystemOfRecordActionDoor {\n  readonly actionName: string;\n  readonly writes: boolean;\n}\n\n/**\n * The operations the binding's declared actions name as their HTTP doors, keyed by operation.\n *\n * One operation runs one action: two actions naming the same door would make the operation's meaning depend on which\n * one its implementation happens to hand to the executor, so it is refused here rather than decided there.\n */\nfunction collectSystemOfRecordActionDoors(binding: HttpApiResourceBinding): ReadonlyMap<string, SystemOfRecordActionDoor> {\n  const doors = new Map<string, SystemOfRecordActionDoor>();\n  for (const [actionName, action] of Object.entries(binding.actions ?? {})) {\n    if (action.operation === undefined) continue;\n    const existing = doors.get(action.operation);\n    if (existing !== undefined) {\n      throw new Error(\n        `operation '${action.operation}' is named as the door of two actions, '${existing.actionName}' and '${actionName}'. `\n        + 'One operation runs one action; declare a second operation for the second action.',\n      );\n    }\n    doors.set(action.operation, { actionName, writes: action.writes });\n  }\n  return doors;\n}\n\n/**\n * Hold an action's HTTP door to the ACTION's rules instead of the row-write rules (#1678 review, F1).\n *\n * A door does not write a row of the bound entity: its implementation hands the request to the system-of-record action\n * executor, which authorizes, confines, sends and audits the action. So `writableVerbs` does not open it, and it opens\n * nothing. What it must still be is honest about the effect it has:\n *\n * - a WRITING action changes remote state that cannot be rolled back, so every variant borrows a SINGLE-ROW mutation verb\n *   (never a read: a read-shaped route is a GET and claims its repeat is harmless, and the boot validator refuses a key on\n *   one), requires the `Idempotency-Key` (the executor refuses a writing action without one, so anything less is a door\n *   that always refuses), and runs INLINE (a queued execution cannot carry the key);\n * - a NON-writing action (a vendor computation) is left to the ordinary rules for the verb it borrows.\n *\n * Never a bulk borrow: one request is one action on one target.\n */\nfunction assertSystemOfRecordActionDoorCoherence(operation: HttpApiWriteOperationFacts, door: SystemOfRecordActionDoor): void {\n  const bulk = operation.effectiveOperations.find((effective) => BULK_WRITE_OPERATIONS.has(effective));\n  if (bulk !== undefined) {\n    throw new Error(\n      `operation '${operation.operationKey}' is the door of action '${door.actionName}' and borrows a bulk verb ('${String(bulk)}'). `\n      + 'One request runs one action on one target; borrow a single-row verb.',\n    );\n  }\n  if (!door.writes) return;\n  const readBorrow = operation.effectiveOperations.find((effective) => resolveHttpApiWriteVerb(effective) === undefined);\n  if (readBorrow !== undefined) {\n    throw new Error(\n      `operation '${operation.operationKey}' is the door of action '${door.actionName}', which writes, and borrows '${String(readBorrow)}', `\n      + 'which is not a mutation. A state-changing route must not be read-shaped: it would be a GET, and a required Idempotency-Key '\n      + 'on a read is refused at boot. Borrow update (an action on one record) or create (an action that makes one) in resourceOperationLike.',\n    );\n  }\n  const unkeyed = operation.variants.find((variant) => variant.idempotencyKey !== ResourceOperationIdempotencyKeyRequirement.REQUIRED);\n  if (unkeyed !== undefined) {\n    throw new Error(\n      `operation '${operation.operationKey}' is the door of action '${door.actionName}', which writes, and does not require an `\n      + 'Idempotency-Key on every variant. The executor refuses a writing action without one, so the route would refuse every request; '\n      + `declare idempotencyKey: '${ResourceOperationIdempotencyKeyRequirement.REQUIRED}'.`,\n    );\n  }\n  if (\n    operation.serviceRuntimeMode !== undefined\n    && operation.serviceRuntimeMode !== ResourceOperation_ServiceRuntimeMode.INLINE\n  ) {\n    throw new Error(\n      `operation '${operation.operationKey}' is the door of action '${door.actionName}' and runs '${operation.serviceRuntimeMode}'. `\n      + 'A writing action runs INLINE: a queued or background execution cannot carry its Idempotency-Key. Remove serviceRuntimeMode.',\n    );\n  }\n}\n\n/**\n * Refuse every write declaration on a read-through resource that the engine could not honour.\n *\n * Throws a plain `Error` naming the rule and the fix; the factory wraps it into its own configuration\n * error with the resource identifier in front.\n *\n * The rules, and why each one exists:\n *\n *  1. **No bulk write operation**, opened or not — see {@link BULK_WRITE_OPERATIONS}. Nor a\n *     `haveBulkOperation` twin of a write, which every tier would run as N single-row writes.\n *  2. **Every write operation's verb is OPENED by the binding**, and **every opened verb has an\n *     operation**. Both directions: the first is a route that would answer a refusal forever, the\n *     second a declared door nobody can reach — and an inert declaration that looks like a control is\n *     worse than none.\n *  3. **Every write variant runs INLINE.** A queued or background execution cannot carry the\n *     `Idempotency-Key`, so a retried request could not replay; the service tier refuses a key on a\n *     non-INLINE operation already, and a key is required here.\n *  4. **No write variant declares `Idempotency-Key: ACCEPTED`.** See\n *     {@link resolveHttpApiWriteIdempotencyKeyRequirement}.\n *  5. *(Moved, #2010.)* The erasure-stance rule this list carried — a binding that WRITES personal-data fields\n *     may not declare `NO_SUBJECT_DATA` — is now `personalFieldsContradictingNoSubjectDataStance`, which the\n *     factory applies to EVERY read-through binding and every pipeline copy. Reading those fields out of a\n *     system that \"holds no subject data\" is the same contradiction as writing them into it.\n *  6. **A `VERSION_CHECKED` binding's version field is one the UPDATE can carry and the CREATE cannot** (#1724). The\n *     field must exist on the schema, be admitted to the update payload (the caller sends the version it read), and be\n *     excluded from create (a new row has no version yet, and the vendor stamps it). It must be a STRING: the check\n *     compares the caller's value byte for byte with the vendor's raw one, and a date schema would coerce it on the way\n *     in and make every update stale. Whether it maps onto the vendor's `rowVersionField` needs the facet, and is\n *     checked at boot.\n */\nexport function assertHttpApiWriteDeclarationCoherence(params: {\n  readonly binding: HttpApiResourceBinding;\n  readonly operations: readonly HttpApiWriteOperationFacts[];\n  readonly mainSchema: z.ZodTypeAny;\n}): void {\n  const { binding, operations, mainSchema } = params;\n  const opened = new Set<HttpApiWriteVerb>(binding.writableVerbs);\n  const reached = new Set<HttpApiWriteVerb>();\n  const actionDoors = collectSystemOfRecordActionDoors(binding);\n  // Checked BEFORE the operations: a door named after a missing operation usually means the author mistyped it, and the\n  // operation they meant would otherwise be refused first as an unopened row write — a message about the wrong thing.\n  const declaredOperationKeys = new Set(operations.map((operation) => operation.operationKey));\n  for (const [operationKey, door] of actionDoors) {\n    if (!declaredOperationKeys.has(operationKey)) {\n      throw new Error(\n        `actions.${door.actionName} names '${operationKey}' as its door, and this resource declares no such operation. `\n        + 'Declare the custom operation, or remove the `operation` from the action.',\n      );\n    }\n  }\n\n  for (const operation of operations) {\n    const door = actionDoors.get(operation.operationKey);\n    if (door !== undefined) {\n      assertSystemOfRecordActionDoorCoherence(operation, door);\n      continue;\n    }\n    const bulk = operation.effectiveOperations.find((effective) => BULK_WRITE_OPERATIONS.has(effective));\n    if (bulk !== undefined) {\n      throw new Error(\n        `operation '${operation.operationKey}' is a bulk write ('${String(bulk)}'), which a read-through resource never runs: `\n        + 'N remote writes have no transaction to roll back into when one of them fails after the others landed. '\n        + 'Declare the single-row create/update/delete instead.',\n      );\n    }\n    const verbs = operation.effectiveOperations\n      .map((effective) => resolveHttpApiWriteVerb(effective))\n      .filter((verb): verb is HttpApiWriteVerb => verb !== undefined);\n    if (verbs.length === 0) continue;\n\n    for (const verb of verbs) {\n      if (!opened.has(verb)) {\n        throw new Error(\n          `operation '${operation.operationKey}' writes ('${verb}'), and httpApiBinding.writableVerbs does not open '${verb}'. `\n          + `Add '${verb}' to writableVerbs to open the write toward '${binding.system}', or remove the operation.`,\n        );\n      }\n      reached.add(verb);\n    }\n    if (operation.variants.some((variant) => variant.haveBulkOperation === true)) {\n      throw new Error(\n        `operation '${operation.operationKey}' declares a bulk twin (haveBulkOperation), which a read-through resource never runs — `\n        + 'one request would become N remote writes with no atomicity. Remove haveBulkOperation.',\n      );\n    }\n    if (\n      operation.serviceRuntimeMode !== undefined\n      && operation.serviceRuntimeMode !== ResourceOperation_ServiceRuntimeMode.INLINE\n    ) {\n      throw new Error(\n        `operation '${operation.operationKey}' writes to '${binding.system}' with serviceRuntimeMode '${operation.serviceRuntimeMode}'. `\n        + 'A remote write runs INLINE: its Idempotency-Key is required, and a queued or background execution cannot carry one, '\n        + 'so a retried request could not replay its first outcome. Remove serviceRuntimeMode.',\n      );\n    }\n    const accepted = operation.variants.find((variant) => variant.idempotencyKey === ResourceOperationIdempotencyKeyRequirement.ACCEPTED);\n    if (accepted !== undefined) {\n      throw new Error(\n        `operation '${operation.operationKey}' declares idempotencyKey 'accepted'. A write to a system of record cannot be rolled back, `\n        + 'so every retry must replay the first outcome: the key is REQUIRED on every write variant, and the engine sets it for you. '\n        + 'Remove the idempotencyKey declaration.',\n      );\n    }\n  }\n\n  for (const verb of opened) {\n    if (!reached.has(verb)) {\n      throw new Error(\n        `httpApiBinding.writableVerbs opens '${verb}', and no operation of this resource performs it. An opened write nobody can `\n        + `reach is a declaration that decides nothing; declare the ${HTTP_API_WRITE_VERB_CORE_OPERATION[verb]} operation, or remove the verb.`,\n      );\n    }\n  }\n\n  if (binding.writeConcurrency?.mode === HttpApiWriteConcurrencyMode.VERSION_CHECKED && isZodObject(mainSchema)) {\n    const versionField = binding.writeConcurrency.versionField;\n    const fieldSchema = getZodObjectShape(mainSchema)[versionField] as z.ZodTypeAny | undefined;\n    if (fieldSchema === undefined) {\n      throw new Error(\n        `httpApiBinding.writeConcurrency.versionField names '${versionField}', which this resource's schema does not declare. `\n        + 'Declare the field (mapped to the vendor\\'s row version, e.g. Odoo `write_date`) so a caller can read it and send it back.',\n      );\n    }\n    const unwrapped = unwrapSchema(fieldSchema as never) as { _zod?: { def?: { type?: unknown } } };\n    if (unwrapped?._zod?.def?.type !== 'string') {\n      throw new Error(\n        `httpApiBinding.writeConcurrency.versionField '${versionField}' must be a string schema: the version is compared byte for `\n        + 'byte with what the vendor served (Odoo `write_date`, \"YYYY-MM-DD HH:MM:SS\"), and a date or number schema would re-format it.',\n      );\n    }\n    if (isExcludedFromUpdate(fieldSchema)) {\n      throw new Error(\n        `httpApiBinding.writeConcurrency.versionField '${versionField}' is excluded from UPDATE, so no caller could send the version `\n        + 'it read and every update would be refused. Remove .excludeFromUpdate() from it.',\n      );\n    }\n    if (opened.has(HttpApiWriteVerb.CREATE) && !isExcludedFromCreate(fieldSchema)) {\n      throw new Error(\n        `httpApiBinding.writeConcurrency.versionField '${versionField}' may be sent on CREATE, and a new row has no version: the `\n        + 'vendor stamps it. Declare it .excludeFromCreate().',\n      );\n    }\n  }\n\n}\n"]}

package/dist/esm/resources/utils/initiator-stamped-field-satisfiability.validation.d.ts

@@ -0,0 +1,60 @@
+import { z } from 'zod';
+import type { ResourceType } from '../resources.shared.core.definitions';
+/**
+ * Registry-level guard: a field the ENGINE stamps from the initiator's USER must not be REQUIRED.
+ *
+ * ## The shape (#584)
+ *
+ * `createdByUserId` is stripped from the CREATE DTO by name — a client may never author it — and is
+ * stamped by the repository from `executionContext.initiatorIds.userId`, guarded by `if (userId)` in
+ * both adapters (`addUserTracking`, and the PostgreSQL adapter's own copy). `updatedByUserId` /
+ * `lastUpdatedByUserId` are stamped the same way on UPDATE.
+ *
+ * **A machine principal has no `userId`.** An org or application service acting over MCP, A2A,
+ * client credentials, a worker or a batch supplies none, so a REQUIRED one of these fields is
+ * satisfied by nobody: not the client (stripped), not the repository (the guard skips). Nothing said
+ * so at registration or at exposure, and the write failed — or committed and then failed to describe
+ * itself — the first time a machine caller reached the resource. That is how `todos` and `todoLists`
+ * were found (#577), each only after being exposed.
+ *
+ * ## A refusal at boot, and why it was a report first
+ *
+ * The backend refuses to start when this returns anything — the engine's own measurement is that a
+ * declaration gets made if and only if the framework refuses to start without it.
+ *
+ * It shipped as a startup REPORT on the belief that flipping the existing declarations to optional
+ * changes PostgreSQL column nullability and so owes a migration in every surface. It does not: the
+ * schema planner's contract (version 3) records `sqlType`, `hasIndex`, `isPrimaryKey`, `unique` and
+ * `defaultClause` per column and no nullability, so a required-vs-optional change is enforced by the
+ * Zod layer alone and leaves every lockfile in sync. Measured on all three PostgreSQL surfaces
+ * before the promotion, with the existing declarations flipped in the same change.
+ *
+ * ## Scope
+ *
+ * - Only the user-stamped identifiers. The primary-scope foreign keys (`organizationId`, …) are also
+ *   context-populated, but from the SCOPE, which a machine principal does carry — they are required on
+ *   purpose.
+ * - System resources are skipped: the framework owns their write paths and supplies or refuses the
+ *   attribution explicitly (the SCIM token mint refuses a principal with no user).
+ * - Discriminated-union (polymorphic) schemas are checked on every variant that declares the field.
+ */
+export declare const INITIATOR_USER_STAMPED_FIELD_IDENTIFIERS: readonly ["createdByUserId", "updatedByUserId", "lastUpdatedByUserId"];
+export type InitiatorUserStampedFieldIdentifier = typeof INITIATOR_USER_STAMPED_FIELD_IDENTIFIERS[number];
+export interface InitiatorStampedFieldViolation {
+    readonly resourceType: ResourceType;
+    readonly field: InitiatorUserStampedFieldIdentifier;
+    readonly message: string;
+}
+/** Structural subset of a resource configuration this validator needs. */
+export interface InitiatorStampedFieldResourceInput {
+    readonly resourceIdentifier: ResourceType;
+    readonly mainSchema: z.ZodTypeAny;
+    readonly isSystemResource?: boolean;
+}
+/**
+ * Report every non-system resource that declares an initiator-user-stamped field as REQUIRED.
+ * `isOptional` treats `.optional()`, `.default()` and `.nullish()` as optional; a bare `.nullable()`
+ * stays required, which is correct — `null` is not what the stamp's absence produces.
+ */
+export declare function validateInitiatorStampedFieldSatisfiability(resourceConfigurations: Readonly<Record<string, InitiatorStampedFieldResourceInput>>): InitiatorStampedFieldViolation[];
+//# sourceMappingURL=initiator-stamped-field-satisfiability.validation.d.ts.map

package/dist/esm/resources/utils/initiator-stamped-field-satisfiability.validation.d.ts.map

@@ -0,0 +1 @@
+{"version":3,"file":"initiator-stamped-field-satisfiability.validation.d.ts","sourceRoot":"","sources":["../../../../../src/resources/utils/initiator-stamped-field-satisfiability.validation.ts"],"names":[],"mappings":"AAAA,OAAO,EAAE,CAAC,EAAE,MAAM,KAAK,CAAC;AAQxB,OAAO,KAAK,EAAE,YAAY,EAAE,MAAM,sCAAsC,CAAC;AAEzE;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;GAqCG;AACH,eAAO,MAAM,wCAAwC,wEAAyE,CAAC;AAE/H,MAAM,MAAM,mCAAmC,GAAG,OAAO,wCAAwC,CAAC,MAAM,CAAC,CAAC;AAE1G,MAAM,WAAW,8BAA8B;IAC7C,QAAQ,CAAC,YAAY,EAAE,YAAY,CAAC;IACpC,QAAQ,CAAC,KAAK,EAAE,mCAAmC,CAAC;IACpD,QAAQ,CAAC,OAAO,EAAE,MAAM,CAAC;CAC1B;AAED,0EAA0E;AAC1E,MAAM,WAAW,kCAAkC;IACjD,QAAQ,CAAC,kBAAkB,EAAE,YAAY,CAAC;IAC1C,QAAQ,CAAC,UAAU,EAAE,CAAC,CAAC,UAAU,CAAC;IAClC,QAAQ,CAAC,gBAAgB,CAAC,EAAE,OAAO,CAAC;CACrC;AAaD;;;;GAIG;AACH,wBAAgB,2CAA2C,CACzD,sBAAsB,EAAE,QAAQ,CAAC,MAAM,CAAC,MAAM,EAAE,kCAAkC,CAAC,CAAC,GACnF,8BAA8B,EAAE,CAoBlC"}