platform-types 1.10.761 → 1.10.763

package/dist/ai.d.ts

@@ -621,184 +621,12 @@ declare global {
         /** Email body: trimmed, non-empty, within the send path's body bound. */
         body: string;
     }
-    interface WhatsAppOrderDraftRequest {
-        /** Meta's message id of an INBOUND message this store received. The server re-reads its text. */
-        messageId: string;
-        /** `CUST` + 6–10 digits. Prices the draft at the list a cart prices this customer at (a missing, 0 or deleted list is PUBLICO 1); absent → the store default. */
-        customerId?: string;
-    }
-    /**
-     * One product a parsed item could be. Every field but `score` is read off the
-     * store's own product row and priced by the server — never model output.
-     */
-    interface WhatsAppOrderDraftMatch {
-        productId: string;
-        sku: string;
-        name: string;
-        /** Unit price at the customer's list, in `currency`. Indicative: the order create path re-prices. */
-        amount: number;
-        currency: string;
-        /** Token-overlap similarity of the item phrase and the product name, 0–1. Best first. */
-        score: number;
-    }
-    interface WhatsAppOrderDraftItem {
-        /** The product as the model read it from the message, at most 120 characters. Display it, never parse it. */
-        text: string;
-        /** A whole number of units, 1–999, or `null` when the model's reading was not one — never guessed. */
-        quantity: number | null;
-        /** The model's own confidence in this item, 0–1. */
-        confidence: number;
-        /** At most three, best first. Empty when nothing sellable matched. */
-        matches: WhatsAppOrderDraftMatch[];
-        /** The first match is close enough to stand as the line without a person choosing. */
-        matched: boolean;
-    }
-    /**
-     * Why a person must take the conversation over, in this order:
-     * - `requested` — the customer asked to talk to someone.
-     * - `not_an_order` — the message asks for no products.
-     * - `no_items` — it reads as an order, but no product could be picked out.
-     * - `low_confidence` — the model is below 0.7 on at least one item.
-     * - `invalid_quantity` — at least one item's quantity is `null`.
-     * - `no_match` — nothing sellable matched at least one item.
-     * - `weak_match` — at least one item has matches, none close enough to stand alone.
-     */
-    type WhatsAppOrderDraftHandoffReason = 'requested' | 'not_an_order' | 'no_items' | 'low_confidence' | 'invalid_quantity' | 'no_match' | 'weak_match';
-    /**
-     * `data` payload of the success envelope. ⚠️ A DRAFT: nothing was placed,
-     * reserved or sent. Every draft still needs a staff member to place the
-     * order; `handoff.needed` says one must also talk to the customer.
-     */
-    interface WhatsAppOrderDraftResponse {
-        messageId: string;
-        intent: 'order' | 'human' | 'other';
-        items: WhatsAppOrderDraftItem[];
-        handoff: {
-            needed: boolean;
-            reasons: WhatsAppOrderDraftHandoffReason[];
-        };
-        /** More than 10 items were read; the rest were dropped. */
-        truncated: boolean;
-        /** The model that read the message. */
-        model: string;
-        /** Echoed when sent. */
-        customerId?: string;
-    }
-    /**
-     * The `error` codes this endpoint answers, beyond `GatingErrorCode`
-     * (`PLAN_UPGRADE_REQUIRED` for `aiFeatures` or `whatsappCommerce`,
-     * `IMPERSONATION_READONLY`).
-     *
-     * FREE — no model call was made:
-     * - `VALIDATION_FAILED` · 400.
-     * - `AI_OPT_OUT` · 403 — AI is off for this store, or its state could not be read.
-     * - `WHATSAPP_MESSAGE_NOT_FOUND` · 404 — no INBOUND message of this store has that id.
-     * - `WHATSAPP_MESSAGE_NOT_TEXT` · 422 — the message has no text (a photo, a sticker).
-     * - `WHATSAPP_ORDER_DRAFT_MESSAGE_TOO_LONG` · 422 — over 1000 characters.
-     * - `CUSTOMER_NOT_FOUND` · 404 — `customerId` names no active customer of this store.
-     * - `COST_CEILING_EXCEEDED` · 403 or 503 — see `AiCostCeilingRefusal`.
-     * - `AI_WHATSAPP_ORDER_DRAFT_DISABLED` · 503 — the platform kill-switch for
-     *   this feature is off. Distinct from a ceiling: nothing was spent and no
-     *   budget is exhausted. Like `AI_OPT_OUT`, it is checked AFTER the stored
-     *   draft is read, so a message that already has a `ready` draft is still
-     *   answered with it (200, no spend) while the switch is off. The automatic
-     *   worker checks it before it claims the message and skips it — no draft
-     *   row, no frame — so the message stays undrafted until a staff `POST`.
-     * - `AI_UNAVAILABLE` · 503 — the platform could not make the model call at
-     *   all (a server-side fault, the same code on every AI endpoint). Nothing
-     *   was sent or spent; the message's claim is settled `failed`, so a later
-     *   `POST` drafts it. The automatic worker writes no draft row for it at all
-     *   and retries the message itself.
-     * - `WHATSAPP_ORDER_DRAFT_PENDING` · 409 — the message is being drafted right
-     *   now (by the automatic worker or another request); carries
-     *   `status: 'pending'`. Wait for the `whatsapp-order-draft` frame or retry.
-     *   A `pending` claim older than 60 s is dead (its invocation timed out
-     *   before settling) and the next `POST` takes it over instead.
-     *
-     * A `POST` for a message that already has a `ready` stored draft answers
-     * that draft (200) and spends nothing; only an absent, `failed` or stale one is
-     * drafted again. A `failed` draft whose call was METERED (below) is spent on
-     * a second time when a `POST` retries it — the worker never does.
-     *
-     * METERED — the call ran and its output was refused:
-     * - `WHATSAPP_ORDER_DRAFT_BLOCKED` · 422 — the guardrail refused; carries `reason`
-     *   (filter type names only).
-     * - `WHATSAPP_ORDER_DRAFT_GENERATION_FAILED` · 502 — the output did not parse.
-     */
-    type WhatsAppOrderDraftErrorCode = 'VALIDATION_FAILED' | 'AI_OPT_OUT' | 'WHATSAPP_MESSAGE_NOT_FOUND' | 'WHATSAPP_MESSAGE_NOT_TEXT' | 'WHATSAPP_ORDER_DRAFT_MESSAGE_TOO_LONG' | 'CUSTOMER_NOT_FOUND' | 'COST_CEILING_EXCEEDED' | 'AI_WHATSAPP_ORDER_DRAFT_DISABLED' | 'AI_UNAVAILABLE' | 'WHATSAPP_ORDER_DRAFT_PENDING' | 'WHATSAPP_ORDER_DRAFT_BLOCKED' | 'WHATSAPP_ORDER_DRAFT_GENERATION_FAILED';
-    /**
-     * The one stored draft of a message — built by the automatic worker when
-     * the message arrived (stores with `config.whatsappOrderAutoDraft` on) or
-     * by a staff `POST /whatsapp/order-draft`. Read at `GET
-     * /whatsapp/order-draft?messageId=`. The worker pushes it as the
-     * `whatsapp-order-draft` frame when it settles, through `wsPostStore` with
-     * `audience: 'operator'` — the store's operator sockets, never the
-     * customer's. Kept as long as the message it reads (90 days).
-     *
-     * - `pending` — being drafted; no `draft`, no `error`.
-     * - `ready` — `draft` is set. Still a DRAFT: staff place the order.
-     * - `failed` — `error` is set, one of `WhatsAppOrderDraftErrorCode` or
-     *   `WHATSAPP_ORDER_DRAFT_FAILED` for an unexpected fault. The worker never
-     *   retries it; a staff `POST` does.
-     */
-    interface WhatsAppStoredOrderDraft {
-        messageId: string;
-        status: 'pending' | 'ready' | 'failed';
-        draft?: WhatsAppOrderDraftResponse;
-        error?: string;
-        /** Epoch ms. */
-        createdAt: number;
-        /** Epoch ms. */
-        updatedAt: number;
-    }
-    /** Staff sends a priced quote to the sender of one stored inbound WhatsApp message. No AI spend. */
-    interface WhatsAppOrderConfirmationRequest {
-        messageId: string;
-        presupuestoId: string;
-        paymentMethod?: number;
-        deliveryMethod?: number;
-    }
-    type WhatsAppOrderConfirmationStatus = 'sending' | 'awaiting' | 'confirming' | 'confirmed' | 'cancelled' | 'changes_requested' | 'expired' | 'superseded' | 'failed';
-    /**
-     * Public confirmation returned by POST /whatsapp/order-draft/confirmation and
-     * emitted to operator sockets. The private nonce and sender number never reach
-     * this shape. An accepted staff-authored quote is converted through the existing
-     * atomic order service; an AI parse cannot create an order.
-     */
-    interface WhatsAppOrderConfirmation {
-        messageId: string;
-        presupuestoId: string;
-        status: WhatsAppOrderConfirmationStatus;
-        customerId: string;
-        paymentMethod?: number;
-        deliveryMethod?: number;
-        sentBy: {
-            userId: string;
-            fullName: string;
-        };
-        /** Epoch ms; the earlier of the quote expiry and 24 hours after sending. */
-        expiresAt: number;
-        sentMessageId?: string;
-        orderId?: string;
-        /** A stable refusal code, never a raw provider message or customer text. */
-        error?: string;
-        createdAt: number;
-        updatedAt: number;
-    }
-    /**
-     * Route refusals in addition to the existing entitlement/impersonation codes.
-     * `…_DISABLED` (503) is the `whatsappOrderConfirmationEnabled` platform switch;
-     * `…_RECIPIENT_MISMATCH` (409) is a quote whose customer phone is not the
-     * source message's sender; `…_SETTLED` (409) carries the final confirmation
-     * in `data` (confirmed, cancelled, superseded, or failed after the tap).
-     */
-    type WhatsAppOrderConfirmationErrorCode = 'VALIDATION_FAILED' | 'ADMIN_REQUIRED' | 'WHATSAPP_MESSAGE_NOT_FOUND' | 'PRESUPUESTO_NOT_FOUND' | 'PRESUPUESTO_NOT_MUTABLE' | 'CUSTOMER_NOT_FOUND' | 'PAYMENT_METHOD_NOT_FOUND' | 'DELIVERY_METHOD_NOT_FOUND' | 'WHATSAPP_WINDOW_CLOSED' | 'WHATSAPP_ORDER_CONFIRMATION_DISABLED' | 'WHATSAPP_ORDER_CONFIRMATION_RECIPIENT_MISMATCH' | 'WHATSAPP_ORDER_CONFIRMATION_PENDING' | 'WHATSAPP_ORDER_CONFIRMATION_SETTLED' | 'PLATFORM_INTEGRATION_DISABLED' | 'WHATSAPP_NOT_CONNECTED' | 'WHATSAPP_RECIPIENT_NOT_ALLOWED' | 'WHATSAPP_SEND_UNCONFIRMED' | 'WHATSAPP_SEND_FAILED' | 'WHATSAPP_TEMPLATE_NOT_APPROVED' | 'WHATSAPP_RECIPIENT_OPTED_OUT' | 'WHATSAPP_RATE_LIMITED' | 'WHATSAPP_ACCOUNT_SUSPENDED' | 'WHATSAPP_TOKEN_REJECTED';
     /**
      * The ONE spent-budget refusal every AI spend route answers —
      * `POST /products/enrich`, `/reports/narrative`, `/marketing/copy`,
      * `/reminders/draft`, `/suppliers/doc-extract`,
-     * `/suppliers/price-list-extract`, `/presupuestos/draft` and `/whatsapp/order-draft`, and any AI
-     * route added later. There is no second spelling and no 429 for it.
+     * `/suppliers/price-list-extract` and `/presupuestos/draft`, and any AI route
+     * added later. There is no second spelling and no 429 for it.
      *
      * - 403 — the TENANT's own ceiling. Carries `feature`, `upsell` and `period`.
      *   `upsell` is true only for `monthly`: a daily tenant ceiling is one

package/dist/audit.d.ts

@@ -58,7 +58,8 @@ declare global {
      *
      * - `operator` — a store user acting through the App. Actor is that user.
      * - `platform` — a MANAGER acting through `/platform/*`. Actor is that user.
-     * - `customer` — a web, WhatsApp or storefront customer. Actor is the
+     * - `customer` — a web or storefront customer (older rows also carry ones who
+     *   ordered through the since-removed WhatsApp checkout). Actor is the
      *   `CUST…` id with `fullName: ''` ALWAYS: an `AUDIT#` row has no TTL and is
      *   not reached by erasure, so a stored customer name could never be erased.
      *   Render the name from the live customer row.
@@ -153,6 +154,16 @@ declare global {
      | 'order_shipment_created'
     /** A shipment was voided; when the order was delivered, this un-delivered it. */
      | 'order_shipment_voided' | 'payment_linked' | 'payment_unlinked'
+    /**
+     * An operator closed the order's storefront payment attempt that sat in
+     * `resolution` (`POST /payments/attempts { mode: 'resolve' }`). Records a
+     * decision only — no money moved and the order row is untouched.
+     * `before`: `attemptId`, `state` (`'resolution'`), `resolutionCause`.
+     * `after`: `attemptId`, `state` (`'resolved'`), `outcome` (`'refunded'` |
+     * `'kept'`) and the operator's reason as `'[present]'` — presence only, the
+     * words stay on the attempt row.
+     */
+     | 'payment_attempt_resolved'
     /** HISTORICAL: written only by the removed outbound MercadoPago refund; kept so old timeline rows still parse. */
      | 'payment_refunded'
     /** At least one till tender leg was appended (an absorbed replay writes none). */

package/dist/cjs/index.js

@@ -122,7 +122,6 @@ __exportStar(require("./userActivity.js"), exports);
 __exportStar(require("./valuation.js"), exports);
 __exportStar(require("./webhook.js"), exports);
 __exportStar(require("./wire.js"), exports);
-__exportStar(require("./whatsapp.js"), exports);
 __exportStar(require("./workItem.js"), exports);
 __exportStar(require("./zone.js"), exports);
 __exportStar(require("./provinces.js"), exports);

package/dist/cjs/kitRecipe.js

@@ -28,8 +28,7 @@ const product_ts_1 = require("./product.js");
  *
  * - `counter` — the operator basket and `POST /orders`, which the app's POS and
  *   the mobile app share;
- * - `storefront` — the shopper cart and the web checkout. Its WhatsApp catalogue
- *   and order drafts still leave kits out.
+ * - `storefront` — the shopper cart and the web checkout.
  */
 exports.KIT_SALE_CHANNELS = ['counter', 'storefront'];
 /**

package/dist/cjs/notification.js

@@ -5,8 +5,8 @@ exports.NotificationTypeEnum = void 0;
 // Indexed producers resolve candidates through `getNotificationSubscribers`:
 // legacy opt-ins and explicit channel maps remain source data on USER rows.
 // Addressed ERROR / ML_FACTURADOR_COLLISION / ML_SELLER_SWITCHED /
-// ML_CONNECTION_BROKEN / MENTION / CUSTOMER_PENDING_APPROVAL do not select a
-// producer subscriber audience;
+// ML_CONNECTION_BROKEN / MENTION / CUSTOMER_PENDING_APPROVAL /
+// PAYMENT_ATTEMPT_RESOLUTION do not select a producer subscriber audience;
 // the consumer still reads the live USER row for each delivery channel.
 // AFIP_CERT_EXPIRY is seeded on the founding user and uses the subscriber index.
 // Exported as a real enum consumed by api and app; adding an indexed type
@@ -174,4 +174,29 @@ var NotificationTypeEnum;
      * storefront socket), and never the registrant's email address.
      */
     NotificationTypeEnum["CUSTOMER_PENDING_APPROVAL"] = "CUSTOMER_PENDING_APPROVAL";
+    /**
+     * A storefront online payment attempt entered `resolution`: Mercado Pago
+     * money landed that did not settle its order (a late capture after the hold
+     * ended or the order was cancelled, a second approval, an amount or order
+     * mismatch, an order already paid). Names the order (`orderId`) and the
+     * cause, in the title and description; the app opens the resolution queue
+     * (`GET /payments/attempts?state=resolution`) from it.
+     *
+     * ⚠️ ADMIN-ONLY, and its own preference key. The producer fans out to every
+     * non-disabled ADMIN of the store (`listActiveAdmins`) — the tier that may
+     * read and close the queue — and never to a plain USER, so a client offers
+     * the `PAYMENT_ATTEMPT_RESOLUTION` toggle to ADMINs only. No legacy opt-in
+     * scan, as for `CUSTOMER_PENDING_APPROVAL` (a new key is seeded nowhere): the
+     * consumer enforces explicit type/channel preferences
+     * (`notificationPreferences.PAYMENT_ATTEMPT_RESOLUTION`), default-on when
+     * absent. Additive — no backfill or consumer migration owed.
+     *
+     * Once per new approval: it rings on the committed move INTO the state, and
+     * again on each further APPROVAL recorded on an attempt already there (new
+     * money the operator has not seen — a pending decision is then refused
+     * `409 PAYMENT_ATTEMPT_CHANGED`). A replayed approval moves nothing and rings
+     * nothing. An attempt an operator closed (`resolved`) and a later approval
+     * re-opens rings again.
+     */
+    NotificationTypeEnum["PAYMENT_ATTEMPT_RESOLUTION"] = "PAYMENT_ATTEMPT_RESOLUTION";
 })(NotificationTypeEnum || (exports.NotificationTypeEnum = NotificationTypeEnum = {}));

package/dist/cjs/order.js

@@ -364,14 +364,14 @@ exports.orderFulfilmentProgress = orderFulfilmentProgress;
  *   `data.shiftId`. Logged; reconcile the queued sale by hand.
  * - `ORDER_CURRENCY_NOT_SUBSCRIBED` · 400 — the sale's currency has no
  *   subscription in the store's `currencies`. Logged.
- * - `PAYMENT_METHODS_NOT_CONFIGURED` · 409 — `tenders` sent, or storefront/
- *   WhatsApp checkout attempted, while the store has no payment methods at
+ * - `PAYMENT_METHODS_NOT_CONFIGURED` · 409 — `tenders` sent, or storefront
+ *   checkout attempted, while the store has no payment methods at
  *   all. Storefront checkout carries `data: {}` and refuses before the cart read.
  * - `PAYMENT_METHOD_NOT_FOUND` · 400 — a tender leg's `method`, or storefront
  *   checkout's `paymentMethod`, names none of the store's payment methods.
  *   Storefront checkout carries `data: {}` and refuses before the cart read.
  *
- * Storefront and WhatsApp checkout business refusals. None allocates an order
+ * Storefront checkout business refusals. None allocates an order
  * id, redeems a coupon or writes an order; none is logged as an error:
  * - `DELIVERY_METHOD_NOT_FOUND` · 400 — `deliveryMethod` is not in the store's
  *   delivery catalogue, including an absent/empty catalogue. `data: {}`;
@@ -628,6 +628,13 @@ exports.ORDER_ERROR_CODES = [
     'ORDER_CURRENCY_NOT_SUBSCRIBED',
     'PAYMENT_METHODS_NOT_CONFIGURED',
     'PAYMENT_METHOD_NOT_FOUND',
+    // An online method (`Method.storefront: 'mp-checkout-pro'`) the store cannot
+    // take for this cart: Mercado Pago not connected, or a cart not in pesos.
+    'PAYMENT_METHOD_UNAVAILABLE',
+    // Storefront checkout: the cart re-priced since the shopper saw it (re-read and
+    // confirm), and an allocated order id already taken (retry).
+    'CART_PRICES_CHANGED',
+    'ORDER_ID_COLLISION',
     'DELIVERY_METHOD_NOT_FOUND',
     'ORDER_BELOW_MINIMUM_PURCHASE',
     'ORDER_INVALID_CART',

package/dist/cjs/paymentAttempt.js

@@ -19,7 +19,7 @@
  * no operator write can carry it back onto the order.
  */
 Object.defineProperty(exports, "__esModule", { value: true });
-exports.PAYMENT_HOLD_MINUTES_DEFAULT = exports.PAYMENT_HOLD_MINUTES_MAX = exports.PAYMENT_HOLD_MINUTES_MIN = exports.PAYMENT_ATTEMPT_RESOLUTION_CAUSES = exports.ORDER_NOT_PAYABLE_REASONS = exports.PAYMENT_ATTEMPT_ERROR_CODES = exports.PAYMENT_ATTEMPT_STATES = void 0;
+exports.PAYMENT_HOLD_MINUTES_DEFAULT = exports.PAYMENT_HOLD_MINUTES_MAX = exports.PAYMENT_HOLD_MINUTES_MIN = exports.PAYMENT_ATTEMPT_RESOLUTION_CAUSES = exports.ORDER_NOT_PAYABLE_REASONS = exports.PAYMENT_ATTEMPT_RESOLUTION_REASON_MAX = exports.PAYMENT_ATTEMPT_RESOLUTION_OUTCOMES = exports.PAYMENT_ATTEMPT_ERROR_CODES = exports.PAYMENT_ATTEMPT_STATES = void 0;
 /** Every {@link PaymentAttemptState}, in lifecycle order. */
 exports.PAYMENT_ATTEMPT_STATES = [
     'created',
@@ -31,10 +31,11 @@ exports.PAYMENT_ATTEMPT_STATES = [
     'refunded',
     'charged_back',
     'resolution',
+    'resolved',
 ];
 /**
- * Every refusal code a payment-attempt start, or a checkout choosing an online
- * method, answers:
+ * Every refusal code a payment-attempt start, a checkout choosing an online
+ * method, or an operator closing a resolution answers:
  *
  * - `PAYMENT_PROVIDER_NOT_CONNECTED` · 412 — the store has no Mercado Pago
  *   account connected.
@@ -44,9 +45,20 @@ exports.PAYMENT_ATTEMPT_STATES = [
  *   {@link OrderNotPayableData}.
  * - `PAYMENT_ATTEMPT_EXPIRED` · 410 — the attempt's `expiresAt` passed.
  * - `PAYMENT_METHOD_UNAVAILABLE` · 409 — the checkout chose an online payment
- *   method the store cannot take right now (its provider is not connected).
+ *   method the store cannot take for this cart: its provider is not connected,
+ *   or the cart is not in pesos (Checkout Pro here charges ARS only). `data` is
+ *   `{}`. Also published in `ORDER_ERROR_CODES` — web `POST /orders` answers it.
  * - `MP_PREFERENCE_CREATE_FAILED` · 502 — Mercado Pago refused the checkout or
  *   did not answer in time. No attempt was written, so starting again is safe.
+ * - `PAYMENT_ATTEMPT_NOT_FOUND` · 404 — the resolve named an attempt the store
+ *   does not have, or an `orderId` that is not the attempt's.
+ * - `PAYMENT_ATTEMPT_NOT_IN_RESOLUTION` · 409 — the resolve's attempt is not in
+ *   `resolution` (never was, or another operator closed it first). Nothing
+ *   written; `data.state` is the state it is in.
+ * - `PAYMENT_ATTEMPT_CHANGED` · 409 — the attempt is still in `resolution` but
+ *   is not the one the operator decided on: its `updatedAt` is not the request's
+ *   `expectedUpdatedAt` (a further payment was recorded on it, for one). Nothing
+ *   written; `data` is {@link PaymentAttemptChangedData}.
  */
 exports.PAYMENT_ATTEMPT_ERROR_CODES = [
     'PAYMENT_PROVIDER_NOT_CONNECTED',
@@ -55,7 +67,20 @@ exports.PAYMENT_ATTEMPT_ERROR_CODES = [
     'PAYMENT_ATTEMPT_EXPIRED',
     'PAYMENT_METHOD_UNAVAILABLE',
     'MP_PREFERENCE_CREATE_FAILED',
+    'PAYMENT_ATTEMPT_NOT_FOUND',
+    'PAYMENT_ATTEMPT_NOT_IN_RESOLUTION',
+    'PAYMENT_ATTEMPT_CHANGED',
 ];
+/**
+ * Every `outcome` of {@link ResolvePaymentAttemptRequest}:
+ *
+ * - `refunded` — staff refunded the payment in Mercado Pago's panel.
+ * - `kept` — the money stays with the store (for instance, the order is
+ *   fulfilled by hand on it).
+ */
+exports.PAYMENT_ATTEMPT_RESOLUTION_OUTCOMES = ['refunded', 'kept'];
+/** The longest `reason` a resolve may record, in characters after trimming. */
+exports.PAYMENT_ATTEMPT_RESOLUTION_REASON_MAX = 500;
 /**
  * Every `data.reason` of `409 ORDER_NOT_PAYABLE`:
  *

package/dist/cjs/socket.js

@@ -501,13 +501,6 @@ exports.SOCKET_ACTIONS = [
     // Notifications & messaging.
     'notifications',
     'support-message',
-    /**
-     * An automatic WhatsApp order draft settled (`ready` or `failed`). The
-     * operator sockets of the store only; `data` is a `WhatsAppStoredOrderDraft`.
-     */
-    'whatsapp-order-draft',
-    /** Staff quote confirmation state; operator audience only, data: WhatsAppOrderConfirmation. */
-    'whatsapp-order-confirmation',
     // Payments & providers.
     'payment_received',
     // Operator-only observation invalidation; never a receipt or customer frame.
@@ -528,6 +521,18 @@ exports.SOCKET_ACTIONS = [
      * customer broadcast. Sent once per committed state move of the attempt.
      */
     'orderPaymentAttempt',
+    /**
+     * A storefront payment attempt an operator acts on changed: it entered
+     * `resolution`, took a further NEW approval while in it, or an operator
+     * closed it (`resolved`). `data` is
+     * `PaymentAttemptOperatorView` (`paymentAttempt.ts`) — never the checkout
+     * URL or the Preference id.
+     *
+     * ⚠️ OPERATOR sockets of the store only, and ADMIN tier only (`wsPostStore`
+     * with `lowTierData: null` — the tier `GET /payments/attempts` admits). Never
+     * a customer socket: the shopper's own frame is `orderPaymentAttempt`.
+     */
+    'paymentAttemptChanged',
     'stripe',
     'subscription',
     // Fiscal.

package/dist/cjs/subscription.js

@@ -25,7 +25,7 @@
  * - Feature keys now match the BE wire format directly (renamed afip→afipInvoicing,
  *   cash→cashManagement, reportsAdvanced→advancedReports as of 2026-04-26). The interim
  *   paymentIntegrations key was split into domesticPayments + stripePayments.
- *   New keys whatsappCommerce/aiFeatures/mobileApp/customDomain are
+ *   New keys aiFeatures/mobileApp/customDomain are
  *   declared here even when their epics haven't shipped — the matrix can set
  *   enabled:false until they do.
  */
@@ -113,7 +113,6 @@ exports.FEATURE_KEYS = [
     'importExport',
     'domesticPayments',
     'stripePayments',
-    'whatsappCommerce',
     'aiFeatures',
     'mobileApp',
     'customBranding',
@@ -133,5 +132,4 @@ exports.FEATURE_KEYS = [
     'webhooks',
     'maxOrdersMonth',
     'maxInvoicesMonth',
-    'whatsappMessages',
 ];

package/dist/cjs/wire.js

@@ -18,7 +18,7 @@
  * describes the result in the same edit.
  */
 Object.defineProperty(exports, "__esModule", { value: true });
-exports.ROW_TTL_KEYS = exports.USER_TOTP_INTERNAL_KEYS = exports.STORE_TIENDANUBE_SECRET_KEYS = exports.STORE_WHATSAPP_SECRET_KEYS = exports.STORE_MERCADOLIBRE_SECRET_KEYS = exports.STORE_GMAIL_SECRET_KEYS = exports.STORE_MP_SECRET_KEYS = exports.STORE_AFIP_SECRET_KEYS = exports.RESPONSE_STRIPPED_KEYS = void 0;
+exports.ROW_TTL_KEYS = exports.USER_TOTP_INTERNAL_KEYS = exports.STORE_TIENDANUBE_SECRET_KEYS = exports.STORE_MERCADOLIBRE_SECRET_KEYS = exports.STORE_GMAIL_SECRET_KEYS = exports.STORE_MP_SECRET_KEYS = exports.STORE_AFIP_SECRET_KEYS = exports.RESPONSE_STRIPPED_KEYS = void 0;
 /**
  * The seven keys `response()` deletes from `body.data`.
  *
@@ -67,8 +67,6 @@ exports.STORE_MERCADOLIBRE_SECRET_KEYS = [
     'refreshTokenEncrypted',
     'refreshAttemptAt',
 ];
-/** WhatsApp's only secret field on `Store.integrations.whatsapp`. */
-exports.STORE_WHATSAPP_SECRET_KEYS = ['accessToken'];
 /**
  * KMS-ciphertext TiendaNube OAuth credential on `Store.integrations.tiendanube`.
  * A single `accessTokenEncrypted` — TiendaNube issues no refresh token, so there

package/dist/customer.d.ts

@@ -420,8 +420,8 @@ declare global {
          * already makes on this row.
          *
          * ⚠️ Fed ONLY by a `ReminderRecord` with `kind: 'reminder'` — a delivered
-         * collections chase on ANY channel (the email leg or the scheduled
-         * WhatsApp leg), so both legs share one cooldown. It is absent on a
+         * collections chase on ANY channel (the email leg, or on older rows the
+         * since-removed WhatsApp leg), so every leg shared one cooldown. It is absent on a
          * customer who was never chased, and that is correct rather than missing:
          * populating it from transactional mail would read as "already chased" to
          * a collections operator who would then skip a debtor.
@@ -1593,10 +1593,19 @@ declare global {
      * `register`, `mode: 'social'` with the same provider on `register-social`
      * (that account has no password) — never to register again, which the email
      * uniqueness constraint would now refuse.
+     *
+     * In a store that approves registrations first, the answer is the created
+     * customer with `accessState: 'pending'` and NO session: no token and no
+     * `sessionIssued`. The client tells the shopper the account awaits approval;
+     * signing in is refused until the store approves it.
      */
     type CustomerRegisterResult = AuthCustomer | (Customer & {
         accessToken?: never;
         sessionIssued: false;
+    }) | (Customer & {
+        accessState: 'pending';
+        accessToken?: never;
+        sessionIssued?: never;
     });
 }
 export {};

package/dist/index.d.ts

@@ -98,7 +98,6 @@ export * from './userActivity.ts';
 export * from './valuation.ts';
 export * from './webhook.ts';
 export * from './wire.ts';
-export * from './whatsapp.ts';
 export * from './workItem.ts';
 export * from './zone.ts';
 export * from './provinces.ts';

package/dist/index.js

@@ -106,7 +106,6 @@ export * from "./userActivity.js";
 export * from "./valuation.js";
 export * from "./webhook.js";
 export * from "./wire.js";
-export * from "./whatsapp.js";
 export * from "./workItem.js";
 export * from "./zone.js";
 export * from "./provinces.js";

package/dist/kitRecipe.d.ts

@@ -24,8 +24,7 @@
  *
  * - `counter` — the operator basket and `POST /orders`, which the app's POS and
  *   the mobile app share;
- * - `storefront` — the shopper cart and the web checkout. Its WhatsApp catalogue
- *   and order drafts still leave kits out.
+ * - `storefront` — the shopper cart and the web checkout.
  */
 export declare const KIT_SALE_CHANNELS: readonly ["counter", "storefront"];
 /**

package/dist/kitRecipe.js

@@ -25,8 +25,7 @@ import { MAX_BASE_QUANTITY } from "./product.js";
  *
  * - `counter` — the operator basket and `POST /orders`, which the app's POS and
  *   the mobile app share;
- * - `storefront` — the shopper cart and the web checkout. Its WhatsApp catalogue
- *   and order drafts still leave kits out.
+ * - `storefront` — the shopper cart and the web checkout.
  */
 export const KIT_SALE_CHANNELS = ['counter', 'storefront'];
 /**

package/dist/maintenance.d.ts

@@ -18,15 +18,10 @@ declare global {
     /**
      * A channel a maintenance broadcast can actually leave the platform on.
      *
-     * ⚠️ `'whatsapp'` is deliberately ABSENT, and its absence is the contract
-     * rather than an oversight. The platform's WhatsApp send path
-     * (`POST /tenants/whatsapp`, `mode: 'template'`) is a synchronous HTTP
-     * handler, not a queue producer, and Meta requires a pre-approved template
-     * per message: a fleet-wide fan-out through it would be N inline Graph API
-     * calls inside one request, against a template that does not exist yet.
-     * Declaring the channel here before either is true would let a caller ask
-     * for a send this service cannot make and would have to refuse at runtime.
-     * Adding the member later is purely additive for every consumer.
+     * ⚠️ `'whatsapp'` is deliberately ABSENT: the platform has no WhatsApp send
+     * path, so declaring it would let a caller ask for a send this service cannot
+     * make and would have to refuse at runtime. Adding the member later is purely
+     * additive for every consumer.
      */
     type MaintenanceBroadcastChannel = 'email' | 'sms';
     /**

package/dist/notification.d.ts

@@ -152,7 +152,32 @@ export declare enum NotificationTypeEnum {
      * audience — the operator bell would reach the pending registrant's own
      * storefront socket), and never the registrant's email address.
      */
-    CUSTOMER_PENDING_APPROVAL = "CUSTOMER_PENDING_APPROVAL"
+    CUSTOMER_PENDING_APPROVAL = "CUSTOMER_PENDING_APPROVAL",
+    /**
+     * A storefront online payment attempt entered `resolution`: Mercado Pago
+     * money landed that did not settle its order (a late capture after the hold
+     * ended or the order was cancelled, a second approval, an amount or order
+     * mismatch, an order already paid). Names the order (`orderId`) and the
+     * cause, in the title and description; the app opens the resolution queue
+     * (`GET /payments/attempts?state=resolution`) from it.
+     *
+     * ⚠️ ADMIN-ONLY, and its own preference key. The producer fans out to every
+     * non-disabled ADMIN of the store (`listActiveAdmins`) — the tier that may
+     * read and close the queue — and never to a plain USER, so a client offers
+     * the `PAYMENT_ATTEMPT_RESOLUTION` toggle to ADMINs only. No legacy opt-in
+     * scan, as for `CUSTOMER_PENDING_APPROVAL` (a new key is seeded nowhere): the
+     * consumer enforces explicit type/channel preferences
+     * (`notificationPreferences.PAYMENT_ATTEMPT_RESOLUTION`), default-on when
+     * absent. Additive — no backfill or consumer migration owed.
+     *
+     * Once per new approval: it rings on the committed move INTO the state, and
+     * again on each further APPROVAL recorded on an attempt already there (new
+     * money the operator has not seen — a pending decision is then refused
+     * `409 PAYMENT_ATTEMPT_CHANGED`). A replayed approval moves nothing and rings
+     * nothing. An attempt an operator closed (`resolved`) and a later approval
+     * re-opens rings again.
+     */
+    PAYMENT_ATTEMPT_RESOLUTION = "PAYMENT_ATTEMPT_RESOLUTION"
 }
 declare global {
     type CustomerNotificationPreferences = Partial<Record<'reminder-scheduled' | 'appointment-reminder', {
@@ -316,13 +341,11 @@ declare global {
      * What the outbound seam (`notify()`) knew about one call the moment its
      * transport returned. It is never a delivery receipt: `enqueued` and
      * `handed-off` say a queue or a sender took the message, and `sent` says the
-     * provider accepted it. Later SES events arrive through `EMAILEVENT#`;
-     * WhatsApp status callbacks update the established `WHATSAPP#` history.
+     * provider accepted it. Later SES events arrive through `EMAILEVENT#`.
      */
     type NotifyDeliveryOutcome = 'sent' | 'suppressed' | 'not-sent' | 'enqueued' | 'handed-off' | 'failed';
     /** Why a channel did not deliver, including send-time preference refusals. */
     type NotifyNotSentReason = 'skipped-by-preference' | 'demo' | 'suppressed' | 'refused';
-    type NotifyWhatsAppSuppressionReason = 'allowlist-missing' | 'recipient-malformed' | 'recipient-not-allowlisted';
     /**
      * A recorded transport outcome or send-time preference refusal — the
      * wire half of the `NOTIFY#{storeId}` delivery row. The stored row,
@@ -337,14 +360,14 @@ declare global {
      * `transport`, plus a count.
      */
     interface NotifyDelivery {
-        transport: 'email' | 'queue' | 'ses' | 'ses-marketing' | 'push' | 'whatsapp';
+        transport: 'email' | 'queue' | 'ses' | 'ses-marketing' | 'push';
         /** The closed audience enum `notify()` accepts. */
         audience: 'store-customer' | 'account-holder' | 'store-operator' | 'platform-staff' | 'marketing-recipient';
         /** The producer's event name. Never recipient data. */
         logTag: string;
         outcome: NotifyDeliveryOutcome;
         /** Only when `outcome` is `'not-sent'` or `'suppressed'`. */
-        reason?: NotifyNotSentReason | NotifyWhatsAppSuppressionReason;
+        reason?: NotifyNotSentReason;
         /** Provider channel for sent email; semantic channel for preference skips. */
         channel?: 'gmail' | 'ses' | NotificationPreferenceChannel;
         /** Only when SES returned one. The join key to `EMAILEVENT#`. */