sinfactura-types 1.10.652 → 1.10.654

package/dist/cjs/socket.js

@@ -584,7 +584,8 @@ exports.SOCKET_ACTIONS = [
     // ML will still restate; a consumer must not render one as final.
     'mercadolibre_settlement_period',
     // BE → the store's OPERATOR sockets when an avanzado custom domain's provisioning state
-    // moves, or a teardown removes it (`provisioning: null`) (`CustomDomainSocketPayload`). Status only: the row's
+    // moves, a teardown removes it (`provisioning: null`), or a revoke lands (`status: 'REVOKED'`)
+    // (`CustomDomainSocketPayload`). Status only: the row's
     // `verificationToken` is an ownership credential and is never re-sent here.
     'customDomain',
     // BE → all store users on every purchase-order write: create, update, cancel,

package/dist/inventory.d.ts

@@ -326,7 +326,7 @@ declare global {
      * mixture could never be unpicked afterwards.
      *
      * ⚠️ **The same segment is what makes the partition reachable by a tenant
-     * purge.** `sweepTableByStore` selects a row only when the storeId is a
+     * purge.** The tenant-operation coordinator's row sweep selects a row only when the storeId is a
      * `#`-DELIMITED PK segment or the whole SK (`pkBelongsToStore`,
      * `@helpers/tenantPartitions`), so a key carrying no storeId anywhere is
      * invisible to delete-tenant and reset-tenant alike. The delimiters are load

package/dist/platform.d.ts

@@ -125,14 +125,35 @@ export interface ResetCashOpResult {
     /** Present only when `complete` is `false`. */
     cursor?: string;
 }
-/** `POST /platform/operations { mode: 'delete-tenant' | 'reset-tenant' }` — both tenant wipes take the same body. */
+/**
+ * `POST /platform/operations { mode: 'delete-tenant' | 'reset-tenant' }` — both tenant wipes take the same body.
+ * The wipe runs asynchronously; poll `GET /platform/tenant-operations/{operationId}` for its
+ * `TenantOperationStatus`. The body carries no `requestId`: the server DERIVES one from the stage,
+ * the operator, the action, the store and its audit-lifecycle generation, so a repeat replays:
+ *
+ * - a new admission answers `202 { message, data: TenantOperationAdmission }`;
+ * - a repeat while the operation is live answers `200` with that same operation;
+ * - a repeat of an operation that `failed` before its business phase finished requeues it and
+ *   answers `200` (the legacy shape's restart);
+ * - a repeat of a finished delete answers `200` with the completed operation;
+ * - a finished reset rotates the generation, so the next reset is a fresh `202` — also when that
+ *   reset's observation stage later `failed`: the legacy shape cannot restart it, and the fresh
+ *   reset's own archive closure re-cleans the residue. A caller that needs to restart such an
+ *   operation admits through `TenantOperationV2Body` and repeats its own `requestId`.
+ *
+ * `reason` is not part of the replay match — the first admission's is the one recorded. Another
+ * MANAGER's call is a new admission, refused `409 TENANT_OPERATION_IN_PROGRESS` while one is live.
+ */
 export interface TenantWipeOpBody extends PlatformOperatorReason {
     mode: 'delete-tenant' | 'reset-tenant';
     storeId: string;
     /** Must equal `storeId`. */
     confirm: string;
 }
-/** Additive admission contract; route activation follows coordinated rollout. */
+/**
+ * `POST /platform/operations { mode: 'tenant-operation-v2' }` — the replayable admission: the same
+ * `requestId` and payload answer `200` with the same operation, a changed payload `409`; a new one `202`.
+ */
 export interface TenantOperationV2Body extends PlatformOperatorReason {
     mode: 'tenant-operation-v2';
     action: 'delete-tenant' | 'reset-tenant';
@@ -140,6 +161,19 @@ export interface TenantOperationV2Body extends PlatformOperatorReason {
     storeId: string;
     confirm: string;
 }
+/**
+ * - `queued`, `running`, `uncertain` — NOT terminal: the business phase is pending, in progress, or
+ *   its last attempt threw and will be retried; the store stays quiesced.
+ * - `business-completed` — the business data and the entity chain are gone and the store can be
+ *   recreated; the archives and derivatives are still being closed. It lasts at least the
+ *   cold-delivery window (24 h 15 min from admission) and is NOT final — but it may also be where
+ *   the operation stops: when the observation stage gives up on residue it cannot prove, the status
+ *   stays `business-completed` for good, the open classes `pending`/`unresolved`, and never reaches
+ *   `completed`. No field tells the two apart; a poller bounds its wait.
+ * - `completed` — terminal: every class is final (none `pending` or `unresolved`).
+ * - `failed` — terminal until restarted: the stall ceiling was reached. A replay of the admitting
+ *   request requeues it (`queued`, or `business-completed` once the business phase had finished).
+ */
 export type TenantOperationState = 'queued' | 'running' | 'uncertain' | 'business-completed' | 'completed' | 'failed';
 export interface TenantOperationClassReport {
     classId: string;
@@ -153,6 +187,7 @@ export interface TenantOperationAdmission {
     action: 'delete-tenant' | 'reset-tenant';
     targetStoreId: string;
 }
+/** `GET /platform/tenant-operations/{operationId}` → `{ message, data }`; `status` is a `TenantOperationState`. */
 export interface TenantOperationStatus extends TenantOperationAdmission {
     createdAt: number;
     updatedAt: number;

package/dist/socket.d.ts

@@ -43,8 +43,10 @@ export interface CustomDomainSocketPayload {
     /**
      * The attempt as it now stands, or `null` when a teardown (a deprovision, a
      * revoke, the grace-expiry sweep) removed it — whatever state it was in.
-     * Merge the `null` over a cached row: the attempt is gone, and the host can
-     * be provisioned again.
+     * Merge the `null` over a cached row: the attempt is gone. Whether the host
+     * can be provisioned again depends on `status`: absent (a deprovision, the
+     * grace sweep), the row is still VERIFIED and it can; `'REVOKED'`, the host
+     * is gone from the store and must not be offered for publishing.
      */
     provisioning: {
         state: DomainProvisioningState;
@@ -69,6 +71,14 @@ export interface CustomDomainSocketPayload {
      * still type-checks.
      */
     deactivatesAt?: number | null;
+    /**
+     * The row's status, sent only when the frame follows a status change: a
+     * revoke posts ONE frame after its REVOKED write lands —
+     * `{ provisioning: null, deactivatesAt: null, status: 'REVOKED' }` — never the
+     * bare teardown frame before it. Absent means the status did not move; keep
+     * the cached one.
+     */
+    status?: DomainStatus;
 }
 /**
  * `data` of the BULK-IMPORT `customers` frame: "drop your cached customer list

package/dist/socket.js

@@ -581,7 +581,8 @@ export const SOCKET_ACTIONS = [
     // ML will still restate; a consumer must not render one as final.
     'mercadolibre_settlement_period',
     // BE → the store's OPERATOR sockets when an avanzado custom domain's provisioning state
-    // moves, or a teardown removes it (`provisioning: null`) (`CustomDomainSocketPayload`). Status only: the row's
+    // moves, a teardown removes it (`provisioning: null`), or a revoke lands (`status: 'REVOKED'`)
+    // (`CustomDomainSocketPayload`). Status only: the row's
     // `verificationToken` is an ownership credential and is never re-sent here.
     'customDomain',
     // BE → all store users on every purchase-order write: create, update, cancel,

package/package.json

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