sinfactura-types 1.10.621 → 1.10.622

package/dist/customer.d.ts

@@ -643,7 +643,8 @@ declare global {
      * Every refusal `POST /customers { mode: 'data-export' | 'anonymize' }` and
      * its storefront twin `POST /user` can answer, as the bare SCREAMING_SNAKE
      * `error` code on the wire. Thrown by `stacks/services/customerDataRights.ts`
-     * and mapped to one status each by `@helpers/customerDataRightsRefusal`.
+     * (`RETENTION_REQUEST_CONFLICT` by the operator handler, before the service
+     * runs) and mapped to one status each by `@helpers/customerDataRightsRefusal`.
      */
     type CustomerDataRightsErrorCode = 
     /** No such customer in the TOKEN's store — includes every cross-store id. */
@@ -731,7 +732,17 @@ declare global {
      * day, tells staff that the customer asked. The client tells the shopper to
      * contact the shop; retrying cannot succeed.
      */
-     | 'CUSTOMER_ERASURE_REQUIRES_STAFF';
+     | 'CUSTOMER_ERASURE_REQUIRES_STAFF'
+    /**
+     * 409, OPERATOR ONLY (`POST /customers` mode `anonymize`). The request's
+     * `requestId` is already bound to the erasure of ANOTHER customer (or its
+     * receipt names a retention job that no longer exists). Refused BEFORE the
+     * erasure: NOTHING was erased. Send a fresh `requestId`, or none — the
+     * request id is then derived from the customer named. `data` is
+     * `{ customerId }`, the id the request named. The storefront derives its
+     * request id and never answers this code.
+     */
+     | 'RETENTION_REQUEST_CONFLICT';
     /**
      * Why an erasure was refused or its committed completion remains incomplete.
      *
@@ -1225,6 +1236,55 @@ declare global {
      * for the same reason (the rejection reasons are operator-written).
      */
     type WebAnonymizeCustomerResult = Omit<AnonymizeCustomerResult, 'notesErased' | 'notesEraseComplete' | 'rmaReasonsErased' | 'rmaEraseComplete'>;
+    /**
+     * Where a retention job stands. `completed` is terminal and is reached only
+     * when every individually erasable surface is `erased-and-verified`;
+     * `retained-by-policy` is retention, never an erasure.
+     */
+    type CustomerErasureRetentionState = 'retained-by-policy' | 'erased-and-verified' | 'pending-delivery' | 'retryable-failure' | 'identity-unresolved' | 'completed';
+    /**
+     * The retention job an erasure request recorded: what each retention surface
+     * (logs, audit trails, analytics events) owes the erasure, beyond the
+     * customer rows the erasure itself rewrote. The job is opened BEFORE the
+     * erasure, keyed by the request as sent (store and the customer NAMED), and
+     * lists every id the erasure ran as its subjects. Both erasure surfaces record
+     * one; only the operator surface answers it (`StaffAnonymizeCustomerResult`).
+     */
+    interface AnonymizeCustomerRetention {
+        /**
+         * The job's id. The same request (same `requestId`, or none sent twice for
+         * the same customer named) answers the same id — whichever survivor a retry
+         * resolves. Absent when the job could not be opened; re-issuing the erasure
+         * records it.
+         */
+        jobId?: string;
+        /**
+         * The job's folded state. `identity-unresolved` when the erasure could not
+         * rule out a merge survivor (`erasureIncompleteReason:
+         * 'MERGE_LOOKUP_TRUNCATED'`); `retryable-failure` when the job could not be
+         * opened or brought up to date — re-issue the erasure.
+         */
+        state: CustomerErasureRetentionState;
+        /**
+         * `true` until an analytics adapter records the subject's storefront
+         * analytics events erased and verified, which is what folds the job to
+         * `completed`. No analytics adapter records that yet, so today this is
+         * always `true`: those events are NOT erased by this request. A client must
+         * not present the erasure as complete while it is `true`.
+         */
+        analyticsPending: boolean;
+        /**
+         * `true` when a derivative of an erased id (an export, an artifact, a cached
+         * query result) may still be `registered`, or an erased id is not yet fenced
+         * against new registrations: the sweep failed or ran out of time. Re-issue
+         * the erasure; it resumes where the sweep stopped.
+         */
+        derivativesPending: boolean;
+    }
+    /** `data` of the OPERATOR erasure (`POST /customers` mode `anonymize`). The storefront twin answers no `retention`. */
+    type StaffAnonymizeCustomerResult = AnonymizeCustomerResult & {
+        retention: AnonymizeCustomerRetention;
+    };
     /**
      * The outcome of a Ley 25.326 art. 16 erasure (`anonymizeCustomer`). The
      * row is anonymised in place and KEPT — see `Customer.anonymizedAt`.

package/package.json

@@ -1,6 +1,6 @@
 {
 	"name": "sinfactura-types",
-	"version": "1.10.621",
+	"version": "1.10.622",
 	"description": "Shared wire and entity contracts for the SINFACTURA platform.",
 	"type": "module",
 	"main": "dist/index.js",