sinfactura-types 1.10.511 → 1.10.512

package/dist/account.d.ts

@@ -114,6 +114,16 @@ declare global {
          * cash row written while today's default drawer was unavailable (no mirror was written).
          */
         cashMirrorOutcome?: number;
+        /**
+         * ms epoch at which a customer erasure (or a merge cancel) confirmed this
+         * movement's CAJA mirror carries no customer name: rewritten, already clean,
+         * not the subject's, or gone. Server-owned bookkeeping, published to NO wire:
+         * both projections withhold it and `DELETE /account`'s echo of the deleted
+         * row strips it. Its readers are that walk, which skips a row carrying it (so
+         * a re-issue resumes instead of restarting and a settled mirror is never
+         * rewritten), and the ledger name scrub, which then lets the row's name go.
+         */
+        cashMirrorSettledAt?: number;
         /**
          * @deprecated Unix ms at which `currencyValue` was effective (ADR-0013) —
          * but NO writer stamps it on ACCOUNT rows: only the parallel Cash mirror

package/dist/customer.d.ts

@@ -385,6 +385,10 @@ declare global {
          *
          * ⚠️ Forward-only: nothing backfills it, and a duplicate that was never
          * merged carries nothing.
+         *
+         * It SURVIVES a Ley 25.326 erasure of this row (an id, not personal data):
+         * the erasure walks the survivor's rows that came from here, and a re-issue
+         * needs it to find them again.
          */
         mergedInto?: string;
         /**
@@ -1050,11 +1054,40 @@ declare global {
          */
         ledgerRowsScrubbed: number;
         /**
-         * `false` when the ledger could not be read to the end, so rows carrying the
-         * name may remain. The CUSTOMER row IS anonymised either way; a caller must
-         * surface this rather than implying a clean scrub.
+         * `false` when the ledger could not be read to the end, or the erasure ran
+         * out of time before every row was written, so rows carrying the name may
+         * remain — including a movement whose CAJA mirror the scrub did not reach,
+         * whose ledger name is kept as the proof the next pass needs. The
+         * CUSTOMER row IS anonymised either way; a caller must surface this rather
+         * than implying a clean scrub.
          */
         ledgerScrubComplete: boolean;
+        /**
+         * `CASH#{storeId}` drawer rows — the CAJA mirror `POST /account` writes for a
+         * cash movement — whose `description` this erasure rewrote to the movement's
+         * motivo alone, taking the customer's name off `GET /cash`. Only rows this
+         * call CHANGED are counted. A mirror once settled is marked on its ledger row
+         * and never visited again, so a re-issue counts only the mirrors earlier
+         * passes did not reach, and reads `0` once every mirror is settled. The
+         * amounts are not touched.
+         */
+        cashMirrorsScrubbed?: number;
+        /**
+         * `false` when a mirror may still carry the name: the subject's cash
+         * movements could not be read to the end, a read or write failed, the
+         * erasure ran out of time, or a row at a movement's key could not be proven
+         * to be that movement's mirror and was left untouched. BOTH erasure handlers
+         * write an `ERROR` row (`CUSTOMER_ANONYMIZE_CASH_MIRROR_INCOMPLETE`), deduped
+         * per customer per day, naming the unproven drawer rows by `cashId`;
+         * re-issuing the erasure resumes the scrub where it stopped. An unproven
+         * row stays reported until it is gone or its `description` is empty or the
+         * movement's motivo alone (an operator's `POST /cash` edit). For a
+         * merged-away customer it also covers the mirrors of the movements the
+         * merge moved to the survivor.
+         * Optional only so the field is additive — every erasure from this version
+         * on sets it.
+         */
+        cashMirrorScrubComplete?: boolean;
         /**
          * Operator notes about this customer (`CUSTOMER_NOTE#{storeId}#{customerId}`)
          * DELETED by this erasure. Unlike the ledger, notes are not a fiscal record:
@@ -1115,7 +1148,10 @@ declare global {
          * `cancellationReason`) removed, a MercadoLibre row's `buyerNickname`
          * removed, the `search` name dropped, `recipientAnonymizedAt` stamped. The
          * row itself is kept (it is a sale); the retained fiscal receptor lives on
-         * `INVOICE#`. Survey rows are not counted here.
+         * `INVOICE#`. Survey rows are not counted here. Only rows THIS call wrote
+         * are counted: a re-issue reads only the orders not stamped yet, so it
+         * counts the ones an earlier pass did not reach and reads `0` once every
+         * order is scrubbed.
          */
         orderRowsScrubbed: number;
         /**
@@ -1123,7 +1159,10 @@ declare global {
          * `comment` the same step blanks — could not be read or written to the end,
          * so a row carrying the name or the subject's free text may remain. BOTH
          * erasure handlers write an un-deduped `ERROR` row
-         * (`CUSTOMER_ANONYMIZE_ORDERS_INCOMPLETE`).
+         * (`CUSTOMER_ANONYMIZE_ORDERS_INCOMPLETE`). ALWAYS `false` for a merged-away
+         * customer (`mergedInto`): the merge re-pointed their orders to the survivor
+         * with no provenance to find them by, so only erasing the survivor reaches
+         * those orders' frozen recipient.
          */
         orderScrubComplete: boolean;
     }

package/package.json

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