platform-types 1.10.762 → 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.

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/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: {}`;

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.

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.

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

@@ -341,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,
@@ -362,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#`. */

package/dist/order.d.ts

@@ -2722,14 +2722,14 @@ export declare const orderFulfilmentProgress: (order: OrderFulfilmentProgressInp
  *   `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: {}`;

package/dist/order.js

@@ -357,14 +357,14 @@ export const orderFulfilmentProgress = (order) => {
  *   `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: {}`;

package/dist/platform.d.ts

@@ -88,8 +88,8 @@ export interface ReseedConstraintsOpBody extends PlatformOperatorReason {
  */
 export interface RotateWebhookKeyOpBody extends PlatformOperatorReason {
     mode: 'rotate-webhook-key';
-    provider: 'mercadopago' | 'stripe' | 'whatsapp';
-    /** Required for `stripe` and `whatsapp` (provider-issued); optional override for `mercadopago`. Never echoed or audited. */
+    provider: 'mercadopago' | 'stripe';
+    /** Required for `stripe` (provider-issued); optional override for `mercadopago`. Never echoed or audited. */
     newSecret?: string;
     /** Must equal `provider`. Required — absent or wrong is `400 CONFIRMATION_MISMATCH`. */
     confirm: string;
@@ -460,9 +460,6 @@ export interface TenantHealthEnvelope {
             connected: boolean;
             oauthExpiresAt: number | null;
         };
-        whatsapp: {
-            enabled: boolean;
-        };
         sms: {
             enabled: boolean;
         };

package/dist/product.d.ts

@@ -774,7 +774,7 @@ declare global {
         /**
          * Most units of this product ONE sale may carry, summed across every line of
          * the operation. Enforced server-side on every local sale entry point
-         * (order create, storefront and WhatsApp checkout, presupuesto conversion,
+         * (order create, storefront checkout, presupuesto conversion,
          * service delivery, and quantity-increasing edits), which refuse
          * `409 PRODUCT_SALE_LIMIT_EXCEEDED` — see {@link ProductSaleLimitRefusal}.
          *

package/dist/reminder.d.ts

@@ -2,10 +2,11 @@ declare global {
     /**
      * Which dispatcher actually delivered. Only the send helper knows this.
      *
-     * `'whatsapp'` is the scheduled payment reminder's WhatsApp leg
-     * (`Store.config.paymentReminders.channels`): a template message sent from the
-     * store's own connected number. On such a row `to` is the phone number the
-     * message went to, digits only, not an email address.
+     * ⚠️ `'whatsapp'` is HISTORY only. Nothing sends or records it any more, but the
+     * automatic payment reminder once had a WhatsApp leg, and the rows it wrote are
+     * durable and still read back in a customer's reminder history. On such a row
+     * `to` is the phone number the message went to, digits only, not an email
+     * address. Handle the member; never expect a new row to carry it.
      */
     type ReminderChannel = 'gmail' | 'ses' | 'whatsapp';
     /**

package/dist/socket.d.ts

@@ -26,7 +26,7 @@
  * A client must ignore actions it does not own rather than assume it
  * receives all of them.
  */
-export declare const SOCKET_ACTIONS: readonly ["account", "appointments", "appointmentWaitlist", "attendance", "attributes", "automation-rules", "baskets", "cart", "brands", "cash", "catalogOperation", "categories", "campaigns", "customers", "customerNote", "customerAddress", "customerContact", "deliveries", "globals", "inventory", "invoices", "literals", "loyalty", "orders", "presupuestos", "products", "promotions", "segments", "returns", "rma", "templates", "services", "service-templates", "shifts", "stores", "suppliers", "supplier-invoice", "support", "surveys", "users", "warehouses", "zones", "favorites", "webhooks", "account-delete", "baskets-delete", "cart-delete", "log-delete", "notifications", "support-message", "whatsapp-order-draft", "whatsapp-order-confirmation", "payment_received", "mp_payment_status_changed", "payment_linked", "payment_unlinked", "mercadopago", "mercadopago_dynamic_qr_created", "mercadopago_static_qr_created", "mp_hook_log_appended", "mp_ipn_log_appended", "orderPaymentAttempt", "paymentAttemptChanged", "stripe", "subscription", "caea", "print", "print-order", "print-invoice", "print-product", "print-tag", "print_job_failed", "request_printers", "printers_changed", "agent_status_changed", "print_rules_changed", "printers_active", "agent_command", "maintenance", "currency_auto_updated", "drain_progress", "integration_event_appended", "userActivityRecorded", "mercadolibre_settlement_period", "customDomain", "purchaseOrders", "cycleCounts", "stockTransfers", "workItems"];
+export declare const SOCKET_ACTIONS: readonly ["account", "appointments", "appointmentWaitlist", "attendance", "attributes", "automation-rules", "baskets", "cart", "brands", "cash", "catalogOperation", "categories", "campaigns", "customers", "customerNote", "customerAddress", "customerContact", "deliveries", "globals", "inventory", "invoices", "literals", "loyalty", "orders", "presupuestos", "products", "promotions", "segments", "returns", "rma", "templates", "services", "service-templates", "shifts", "stores", "suppliers", "supplier-invoice", "support", "surveys", "users", "warehouses", "zones", "favorites", "webhooks", "account-delete", "baskets-delete", "cart-delete", "log-delete", "notifications", "support-message", "payment_received", "mp_payment_status_changed", "payment_linked", "payment_unlinked", "mercadopago", "mercadopago_dynamic_qr_created", "mercadopago_static_qr_created", "mp_hook_log_appended", "mp_ipn_log_appended", "orderPaymentAttempt", "paymentAttemptChanged", "stripe", "subscription", "caea", "print", "print-order", "print-invoice", "print-product", "print-tag", "print_job_failed", "request_printers", "printers_changed", "agent_status_changed", "print_rules_changed", "printers_active", "agent_command", "maintenance", "currency_auto_updated", "drain_progress", "integration_event_appended", "userActivityRecorded", "mercadolibre_settlement_period", "customDomain", "purchaseOrders", "cycleCounts", "stockTransfers", "workItems"];
 /** Union of every server→client data-frame action. */
 export type SocketAction = (typeof SOCKET_ACTIONS)[number];
 /**

package/dist/socket.js

@@ -498,13 +498,6 @@ export const 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.

package/dist/store.d.ts

@@ -270,16 +270,10 @@ declare global {
      * at send time and failing CLOSED.
      *
      * - `channels` — which legs the chase runs on. ABSENT means `['email']`, so a
-     *   store that never set it behaves exactly as before. `'whatsapp'` adds a
-     *   template message from the store's OWN connected WhatsApp number, carrying
-     *   a MercadoPago payment link for the balance, and needs more than the email
-     *   leg: the `whatsappCommerce` entitlement, headroom on the monthly
-     *   `whatsappMessages` meter, a connected MercadoPago account, a ledger in
-     *   ARS, and per customer a `marketing.consent.whatsapp` stamp with
-     *   `marketing.whatsapp === true` and a phone. Both legs share one cooldown
-     *   (`Customer.lastReminderAt`). On a store with both channels the email leg
-     *   wins the period: a customer it can chase gets the email only, and the
-     *   WhatsApp leg covers the customers email cannot reach (no address).
+     *   store that never set it behaves exactly as before; `'email'` is the only
+     *   leg. ⚠️ A store saved while a `'whatsapp'` leg still existed can carry that
+     *   member until its next save: the chase ignores it, and `PATCH /store` accepts
+     *   it and drops it (a list naming ONLY it saves as `frequency: 'none'`).
      */
     interface PaymentRemindersConfig {
         frequency?: 'none' | 'weekly' | 'monthly';
@@ -288,7 +282,7 @@ declare global {
         channels?: PaymentReminderChannel[];
     }
     /** A leg of the automatic payment reminder — see `PaymentRemindersConfig.channels`. */
-    type PaymentReminderChannel = 'email' | 'whatsapp';
+    type PaymentReminderChannel = 'email';
     /**
      * Cut-offs and window for the periodic ABC (Pareto) classification of the
      * catalogue. Every member is optional and absence falls back to the api's
@@ -879,13 +873,6 @@ declare global {
              * storefront.
              */
             publicContact?: boolean;
-            /**
-             * Draft an order automatically from every inbound WhatsApp text message.
-             * Off unless an admin turns it on. Still needs the `aiFeatures` and
-             * `whatsappCommerce` entitlements, and `aiOptOut` still wins. Drafts are
-             * never placed or sent: staff confirm each one.
-             */
-            whatsappOrderAutoDraft?: boolean;
             /**
              * Per-category × per-channel notification/feedback defaults; absent ⇒
              * FE falls back to all-on. FE-read only — `PATCH /store` validates shape only.
@@ -1251,7 +1238,6 @@ declare global {
     interface StoreIntegrations {
         afip?: Afip;
         mercadopago?: Mercadopago;
-        whatsapp?: WhatsAppConfig;
         sms?: SmsIntegration;
         gmail?: Gmail;
         mercadolibre?: Mercadolibre;

package/dist/subscription.d.ts

@@ -24,7 +24,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.
  */
@@ -100,7 +100,7 @@ declare global {
      * exhausts this union (a `switch`, a `Record<FeatureKey, …>`) still has to
      * handle the new member in the same change.
      */
-    type FeatureKey = 'maxOrdersMonth' | 'maxInvoicesMonth' | 'whatsappMessages' | 'maxProducts' | 'maxUsers' | 'maxCustomers' | 'maxWarehouses' | 'priceListsMax' | 'webhooks' | 'afipInvoicing' | 'suppliers' | 'domesticPayments' | 'stripePayments' | 'cashManagement' | 'importExport' | 'advancedReports' | 'customBranding' | 'prioritySupport' | 'whatsappCommerce' | 'aiFeatures' | 'mobileApp' | 'customDomain' | 'advancedPricing' | 'marketplaceChannels' | 'storefront' | 'loyalty' | 'marketing' | 'mandatory2fa';
+    type FeatureKey = 'maxOrdersMonth' | 'maxInvoicesMonth' | 'maxProducts' | 'maxUsers' | 'maxCustomers' | 'maxWarehouses' | 'priceListsMax' | 'webhooks' | 'afipInvoicing' | 'suppliers' | 'domesticPayments' | 'stripePayments' | 'cashManagement' | 'importExport' | 'advancedReports' | 'customBranding' | 'prioritySupport' | 'aiFeatures' | 'mobileApp' | 'customDomain' | 'advancedPricing' | 'marketplaceChannels' | 'storefront' | 'loyalty' | 'marketing' | 'mandatory2fa';
     /** Resolved entitlements for a specific tenant (matrix + overrides applied). */
     type ResolvedEntitlements = Record<FeatureKey, Entitlement>;
     /**
@@ -1236,7 +1236,7 @@ export declare const isPaidPlanTier: (value: unknown) => value is PaidPlanTier;
  * metered / lifetime cap PASSES THROUGH — a new cap silently unbounded.
  * Checklist: `docs/PLANS_AND_ENTITLEMENTS.md` in the api repo.
  */
-export declare const FEATURE_KEYS: readonly ["afipInvoicing", "suppliers", "advancedReports", "cashManagement", "importExport", "domesticPayments", "stripePayments", "whatsappCommerce", "aiFeatures", "mobileApp", "customBranding", "customDomain", "prioritySupport", "advancedPricing", "marketplaceChannels", "storefront", "loyalty", "marketing", "mandatory2fa", "maxUsers", "maxProducts", "maxCustomers", "maxWarehouses", "priceListsMax", "webhooks", "maxOrdersMonth", "maxInvoicesMonth", "whatsappMessages"];
+export declare const FEATURE_KEYS: readonly ["afipInvoicing", "suppliers", "advancedReports", "cashManagement", "importExport", "domesticPayments", "stripePayments", "aiFeatures", "mobileApp", "customBranding", "customDomain", "prioritySupport", "advancedPricing", "marketplaceChannels", "storefront", "loyalty", "marketing", "mandatory2fa", "maxUsers", "maxProducts", "maxCustomers", "maxWarehouses", "priceListsMax", "webhooks", "maxOrdersMonth", "maxInvoicesMonth"];
 type AssertNoUncoveredFeatureKey<T extends never> = T;
 export type UncoveredFeatureKeys = AssertNoUncoveredFeatureKey<Exclude<FeatureKey, (typeof FEATURE_KEYS)[number]>>;
 export {};

package/dist/subscription.js

@@ -24,7 +24,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.
  */
@@ -109,7 +109,6 @@ export const FEATURE_KEYS = [
     'importExport',
     'domesticPayments',
     'stripePayments',
-    'whatsappCommerce',
     'aiFeatures',
     'mobileApp',
     'customBranding',
@@ -129,5 +128,4 @@ export const FEATURE_KEYS = [
     'webhooks',
     'maxOrdersMonth',
     'maxInvoicesMonth',
-    'whatsappMessages',
 ];

package/dist/wire.d.ts

@@ -43,8 +43,6 @@ export declare const STORE_MP_SECRET_KEYS: readonly ["accessToken", "code", "ref
 export declare const STORE_GMAIL_SECRET_KEYS: readonly ["refreshTokenEncrypted", "accessTokenEncrypted"];
 /** KMS-ciphertext Mercadolibre OAuth credentials + the single-flight refresh marker. */
 export declare const STORE_MERCADOLIBRE_SECRET_KEYS: readonly ["accessTokenEncrypted", "refreshTokenEncrypted", "refreshAttemptAt"];
-/** WhatsApp's only secret field on `Store.integrations.whatsapp`. */
-export declare const STORE_WHATSAPP_SECRET_KEYS: readonly ["accessToken"];
 /**
  * KMS-ciphertext TiendaNube OAuth credential on `Store.integrations.tiendanube`.
  * A single `accessTokenEncrypted` — TiendaNube issues no refresh token, so there
@@ -94,8 +92,6 @@ declare global {
      * because the type has to describe what actually arrives.
      */
     type StoreMercadolibreSecretKey = (typeof STORE_MERCADOLIBRE_SECRET_KEYS)[number];
-    /** The one credential key stripped from `Store.integrations.whatsapp` before it crosses a wire. */
-    type StoreWhatsappSecretKey = (typeof STORE_WHATSAPP_SECRET_KEYS)[number];
     /** The one KMS-ciphertext key stripped from `Store.integrations.tiendanube` before it crosses a wire. */
     type StoreTiendanubeSecretKey = (typeof STORE_TIENDANUBE_SECRET_KEYS)[number];
     /** A TOTP sub-key stripped from `User.totp` before a USER row crosses a wire. */

package/dist/wire.js

@@ -64,8 +64,6 @@ export const STORE_MERCADOLIBRE_SECRET_KEYS = [
     'refreshTokenEncrypted',
     'refreshAttemptAt',
 ];
-/** WhatsApp's only secret field on `Store.integrations.whatsapp`. */
-export const 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/package.json

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

package/dist/cjs/whatsapp.js

@@ -1,70 +0,0 @@
-"use strict";
-/**
- * Published WhatsApp surface — the tenant-facing connection config and the
- * tenant's own template send (`POST /whatsapp/send`).
- *
- * ⚠️ **Meta's inbound webhook payload is NOT here and must not come back.**
- * The twelve shapes Meta POSTs to `/whatsapp` — the entry/change/value
- * envelope, the contact, message, document, audio, image, status, error,
- * conversation and pricing leaves — live in
- * `./internal/whatsappWebhook.ts`, prefixed `WhatsAppWebhook*` and excluded
- * from the published build. They are inbound (the provider answering us), so
- * they fail `./internal/README.md`'s own test for what may be published, and
- * their bare names MERGED with globals in every consumer: a published
- * `interface Document` made `document.filename` compile and type as `string`
- * against `lib.dom`'s `Document`, returning `undefined` at runtime.
- */
-Object.defineProperty(exports, "__esModule", { value: true });
-exports.WHATSAPP_SEND_ERROR_CODES = void 0;
-/**
- * `POST /whatsapp/send` refusals, beyond the cross-cutting `GATING_ERROR_CODES`
- * (notably `PLAN_LIMIT_EXCEEDED` for the `whatsappMessages` monthly cap).
- *
- * - `VALIDATION_FAILED` · 400 — including a body naming both or neither of
- *   `to` / `customerId`.
- * - `IDEMPOTENCY_KEY_REQUIRED` · 400 — no `Idempotency-Key` header. The
- *   idempotency wrapper's own codes (`INVALID_IDEMPOTENCY_KEY`,
- *   `IDEMPOTENCY_KEY_REUSE`, `IDEMPOTENCY_IN_PROGRESS`, `IDEMPOTENCY_KEY_FAILED`,
- *   `IDEMPOTENCY_LOCK_CONTENTION`) apply too. `IDEMPOTENCY_KEY_FAILED` (409)
- *   means an earlier attempt under this key may have reached Meta: check the
- *   recipient's chat before sending again under a NEW key.
- * - `PLATFORM_INTEGRATION_DISABLED` · 503 — WhatsApp is switched off
- *   platform-wide by SINFACTURA.
- * - `WHATSAPP_NOT_CONNECTED` · 409 — the calling store has no connected
- *   WhatsApp, or a connection with no stored token after a disconnect. Disable
- *   the send control. ⚠️ Never falls back to the platform number.
- * - `WHATSAPP_TOKEN_REJECTED` · 409 — connected, but Meta refused the stored
- *   token. Reconnect.
- * - `CUSTOMER_NOT_FOUND` · 404 / `WHATSAPP_RECIPIENT_PHONE_MISSING` · 400 — a bad
- *   id versus a real customer with no usable number.
- * - `WHATSAPP_RECIPIENT_NOT_ALLOWED` · 403 — non-production stages only: the
- *   number is not on that stage's test allowlist. Nothing was sent.
- * - `WHATSAPP_TEMPLATE_NOT_APPROVED` · 422 — not approved, paused, disabled,
- *   wrong language or wrong parameter count (Meta does not tell these apart).
- * - `WHATSAPP_RECIPIENT_OPTED_OUT` · 409 — the recipient cannot receive it.
- * - `WHATSAPP_RATE_LIMITED` · 429 — throughput cap; retry later.
- * - `WHATSAPP_ACCOUNT_SUSPENDED` · 403 — the WhatsApp Business account or the
- *   number itself is restricted.
- * - `WHATSAPP_SEND_FAILED` · 502 — any other Meta 4xx refusal; carries `metaCode`.
- * - `WHATSAPP_SEND_UNCONFIRMED` · 502 — the request reached Meta and its outcome
- *   is unknown: no answer came back, Meta answered 5xx, or Meta accepted it
- *   without a message id.
- *   The message may have been delivered, so the key is sealed:
- *   a retry under it answers `IDEMPOTENCY_KEY_FAILED` rather than re-sending.
- */
-exports.WHATSAPP_SEND_ERROR_CODES = [
-    'VALIDATION_FAILED',
-    'IDEMPOTENCY_KEY_REQUIRED',
-    'PLATFORM_INTEGRATION_DISABLED',
-    'WHATSAPP_NOT_CONNECTED',
-    'WHATSAPP_TOKEN_REJECTED',
-    'CUSTOMER_NOT_FOUND',
-    'WHATSAPP_RECIPIENT_PHONE_MISSING',
-    'WHATSAPP_RECIPIENT_NOT_ALLOWED',
-    'WHATSAPP_TEMPLATE_NOT_APPROVED',
-    'WHATSAPP_RECIPIENT_OPTED_OUT',
-    'WHATSAPP_RATE_LIMITED',
-    'WHATSAPP_ACCOUNT_SUSPENDED',
-    'WHATSAPP_SEND_FAILED',
-    'WHATSAPP_SEND_UNCONFIRMED',
-];

package/dist/whatsapp.d.ts

@@ -1,148 +0,0 @@
-/**
- * Published WhatsApp surface — the tenant-facing connection config and the
- * tenant's own template send (`POST /whatsapp/send`).
- *
- * ⚠️ **Meta's inbound webhook payload is NOT here and must not come back.**
- * The twelve shapes Meta POSTs to `/whatsapp` — the entry/change/value
- * envelope, the contact, message, document, audio, image, status, error,
- * conversation and pricing leaves — live in
- * `./internal/whatsappWebhook.ts`, prefixed `WhatsAppWebhook*` and excluded
- * from the published build. They are inbound (the provider answering us), so
- * they fail `./internal/README.md`'s own test for what may be published, and
- * their bare names MERGED with globals in every consumer: a published
- * `interface Document` made `document.filename` compile and type as `string`
- * against `lib.dom`'s `Document`, returning `undefined` at runtime.
- */
-declare global {
-    /**
-     * Per-tenant WhatsApp Business connection + plan tier.
-     *
-     * ⚠️ **Treat every member as potentially absent on a real row.** Rows
-     * predate the connect flow that populates this block, and writes here are
-     * forward-only — an older tenant keeps its original shape rather than being
-     * backfilled. This is a property of the stored data, not a statement about
-     * which release shipped the writer, so it does not go stale.
-     *
-     * ⚠️ The Meta access token is deliberately absent. It is written by the
-     * per-tenant OAuth callback and stripped by `sanitizeStoreRow` at every
-     * STORE-row wire boundary, so a consumer never receives it;
-     * `WhatsAppConfigRow` (api-internal, unpublished) is what the api's own
-     * senders read. Declaring it here described a field that never arrives.
-     */
-    interface WhatsAppConfig {
-        wabaId: string;
-        phoneNumberId: string;
-        verifiedName: string;
-        /**
-         * Meta's quality signal for the number.
-         *
-         * ⚠️ `'UNKNOWN'` is a real Meta value, not a placeholder — it is what a
-         * number with no traffic yet reports, so every freshly connected tenant
-         * starts here. Render it as "no data", never fold it into `'GREEN'`:
-         * coercing it makes a brand-new number indistinguishable from a
-         * healthy one, and the coercion is invisible at the read site.
-         */
-        qualityRating: 'GREEN' | 'YELLOW' | 'RED' | 'UNKNOWN';
-        status: 'connected' | 'disconnected' | 'suspended';
-        tier: 'free' | 'pro' | 'enterprise';
-        /** ISO timestamp. */
-        connectedAt: string;
-        /** ISO timestamp. */
-        disconnectedAt?: string;
-    }
-    /**
-     * Request body for `POST /whatsapp/send` — the TENANT's own template send,
-     * under `adminToken`, from the calling store's own connected number.
-     *
-     * ⚠️ The request must carry an `Idempotency-Key` header — without one it is
-     * refused `400 IDEMPOTENCY_KEY_REQUIRED`. Meta is called before anything is
-     * written, so a retried request with no key would send the message twice.
-     *
-     * ⚠️ There is no `storeId` member and there must never be one. The sending
-     * store is the authorizer's; a body-supplied one is the shape that would let
-     * a tenant address another tenant's number.
-     *
-     * ⚠️ Template only. Outside Meta's 24-hour customer-service window a free-form
-     * message is refused, and every case this serves (invoice reminder, payment
-     * link, order confirmation) is outside it — so there is no free-text member.
-     *
-     * Exactly one of `to` / `customerId` is required.
-     */
-    interface WhatsAppSendRequest {
-        /** Meta-approved template NAME, as registered against the store's own WhatsApp Business account. */
-        template: string;
-        /**
-         * Language code of the approved translation. Defaults to `'es'`.
-         *
-         * ⚠️ Meta matches a template by (name, language) PAIR — an approved template
-         * requested in the wrong language is refused exactly like one that was never
-         * approved (`WHATSAPP_TEMPLATE_NOT_APPROVED`).
-         */
-        languageCode?: string;
-        /**
-         * BODY placeholders, in `{{1}}`, `{{2}}`, … order.
-         *
-         * ⚠️ ORDER IS THE BINDING — Meta positions them, so an amount where a due
-         * date belongs is accepted, delivered and wrong.
-         */
-        parameters?: string[];
-        /** Recipient, digits with country code (`5491150123456`). Mutually exclusive with `customerId`. */
-        to?: string;
-        /** Recipient by id, resolved against the CALLING store's own customers. */
-        customerId?: string;
-        /** Display name for the message-log row only; never sent to Meta. */
-        name?: string;
-    }
-    /**
-     * `data` of a successful `POST /whatsapp/send`.
-     *
-     * (Named for the template send, not `WhatsAppSendResult`: that name belongs
-     * to the api-internal send seam and has a different shape.)
-     */
-    interface WhatsAppTemplateSendResult {
-        /** Meta's message id — the handle every later delivery-status webhook carries. */
-        messageId: string;
-        template: string;
-        /** ms epoch of the accepted send. */
-        sentAt: number;
-    }
-}
-/**
- * `POST /whatsapp/send` refusals, beyond the cross-cutting `GATING_ERROR_CODES`
- * (notably `PLAN_LIMIT_EXCEEDED` for the `whatsappMessages` monthly cap).
- *
- * - `VALIDATION_FAILED` · 400 — including a body naming both or neither of
- *   `to` / `customerId`.
- * - `IDEMPOTENCY_KEY_REQUIRED` · 400 — no `Idempotency-Key` header. The
- *   idempotency wrapper's own codes (`INVALID_IDEMPOTENCY_KEY`,
- *   `IDEMPOTENCY_KEY_REUSE`, `IDEMPOTENCY_IN_PROGRESS`, `IDEMPOTENCY_KEY_FAILED`,
- *   `IDEMPOTENCY_LOCK_CONTENTION`) apply too. `IDEMPOTENCY_KEY_FAILED` (409)
- *   means an earlier attempt under this key may have reached Meta: check the
- *   recipient's chat before sending again under a NEW key.
- * - `PLATFORM_INTEGRATION_DISABLED` · 503 — WhatsApp is switched off
- *   platform-wide by SINFACTURA.
- * - `WHATSAPP_NOT_CONNECTED` · 409 — the calling store has no connected
- *   WhatsApp, or a connection with no stored token after a disconnect. Disable
- *   the send control. ⚠️ Never falls back to the platform number.
- * - `WHATSAPP_TOKEN_REJECTED` · 409 — connected, but Meta refused the stored
- *   token. Reconnect.
- * - `CUSTOMER_NOT_FOUND` · 404 / `WHATSAPP_RECIPIENT_PHONE_MISSING` · 400 — a bad
- *   id versus a real customer with no usable number.
- * - `WHATSAPP_RECIPIENT_NOT_ALLOWED` · 403 — non-production stages only: the
- *   number is not on that stage's test allowlist. Nothing was sent.
- * - `WHATSAPP_TEMPLATE_NOT_APPROVED` · 422 — not approved, paused, disabled,
- *   wrong language or wrong parameter count (Meta does not tell these apart).
- * - `WHATSAPP_RECIPIENT_OPTED_OUT` · 409 — the recipient cannot receive it.
- * - `WHATSAPP_RATE_LIMITED` · 429 — throughput cap; retry later.
- * - `WHATSAPP_ACCOUNT_SUSPENDED` · 403 — the WhatsApp Business account or the
- *   number itself is restricted.
- * - `WHATSAPP_SEND_FAILED` · 502 — any other Meta 4xx refusal; carries `metaCode`.
- * - `WHATSAPP_SEND_UNCONFIRMED` · 502 — the request reached Meta and its outcome
- *   is unknown: no answer came back, Meta answered 5xx, or Meta accepted it
- *   without a message id.
- *   The message may have been delivered, so the key is sealed:
- *   a retry under it answers `IDEMPOTENCY_KEY_FAILED` rather than re-sending.
- */
-export declare const WHATSAPP_SEND_ERROR_CODES: readonly ["VALIDATION_FAILED", "IDEMPOTENCY_KEY_REQUIRED", "PLATFORM_INTEGRATION_DISABLED", "WHATSAPP_NOT_CONNECTED", "WHATSAPP_TOKEN_REJECTED", "CUSTOMER_NOT_FOUND", "WHATSAPP_RECIPIENT_PHONE_MISSING", "WHATSAPP_RECIPIENT_NOT_ALLOWED", "WHATSAPP_TEMPLATE_NOT_APPROVED", "WHATSAPP_RECIPIENT_OPTED_OUT", "WHATSAPP_RATE_LIMITED", "WHATSAPP_ACCOUNT_SUSPENDED", "WHATSAPP_SEND_FAILED", "WHATSAPP_SEND_UNCONFIRMED"];
-export type WhatsAppSendErrorCode = (typeof WHATSAPP_SEND_ERROR_CODES)[number];
-export {};

package/dist/whatsapp.js

@@ -1,67 +0,0 @@
-/**
- * Published WhatsApp surface — the tenant-facing connection config and the
- * tenant's own template send (`POST /whatsapp/send`).
- *
- * ⚠️ **Meta's inbound webhook payload is NOT here and must not come back.**
- * The twelve shapes Meta POSTs to `/whatsapp` — the entry/change/value
- * envelope, the contact, message, document, audio, image, status, error,
- * conversation and pricing leaves — live in
- * `./internal/whatsappWebhook.ts`, prefixed `WhatsAppWebhook*` and excluded
- * from the published build. They are inbound (the provider answering us), so
- * they fail `./internal/README.md`'s own test for what may be published, and
- * their bare names MERGED with globals in every consumer: a published
- * `interface Document` made `document.filename` compile and type as `string`
- * against `lib.dom`'s `Document`, returning `undefined` at runtime.
- */
-/**
- * `POST /whatsapp/send` refusals, beyond the cross-cutting `GATING_ERROR_CODES`
- * (notably `PLAN_LIMIT_EXCEEDED` for the `whatsappMessages` monthly cap).
- *
- * - `VALIDATION_FAILED` · 400 — including a body naming both or neither of
- *   `to` / `customerId`.
- * - `IDEMPOTENCY_KEY_REQUIRED` · 400 — no `Idempotency-Key` header. The
- *   idempotency wrapper's own codes (`INVALID_IDEMPOTENCY_KEY`,
- *   `IDEMPOTENCY_KEY_REUSE`, `IDEMPOTENCY_IN_PROGRESS`, `IDEMPOTENCY_KEY_FAILED`,
- *   `IDEMPOTENCY_LOCK_CONTENTION`) apply too. `IDEMPOTENCY_KEY_FAILED` (409)
- *   means an earlier attempt under this key may have reached Meta: check the
- *   recipient's chat before sending again under a NEW key.
- * - `PLATFORM_INTEGRATION_DISABLED` · 503 — WhatsApp is switched off
- *   platform-wide by SINFACTURA.
- * - `WHATSAPP_NOT_CONNECTED` · 409 — the calling store has no connected
- *   WhatsApp, or a connection with no stored token after a disconnect. Disable
- *   the send control. ⚠️ Never falls back to the platform number.
- * - `WHATSAPP_TOKEN_REJECTED` · 409 — connected, but Meta refused the stored
- *   token. Reconnect.
- * - `CUSTOMER_NOT_FOUND` · 404 / `WHATSAPP_RECIPIENT_PHONE_MISSING` · 400 — a bad
- *   id versus a real customer with no usable number.
- * - `WHATSAPP_RECIPIENT_NOT_ALLOWED` · 403 — non-production stages only: the
- *   number is not on that stage's test allowlist. Nothing was sent.
- * - `WHATSAPP_TEMPLATE_NOT_APPROVED` · 422 — not approved, paused, disabled,
- *   wrong language or wrong parameter count (Meta does not tell these apart).
- * - `WHATSAPP_RECIPIENT_OPTED_OUT` · 409 — the recipient cannot receive it.
- * - `WHATSAPP_RATE_LIMITED` · 429 — throughput cap; retry later.
- * - `WHATSAPP_ACCOUNT_SUSPENDED` · 403 — the WhatsApp Business account or the
- *   number itself is restricted.
- * - `WHATSAPP_SEND_FAILED` · 502 — any other Meta 4xx refusal; carries `metaCode`.
- * - `WHATSAPP_SEND_UNCONFIRMED` · 502 — the request reached Meta and its outcome
- *   is unknown: no answer came back, Meta answered 5xx, or Meta accepted it
- *   without a message id.
- *   The message may have been delivered, so the key is sealed:
- *   a retry under it answers `IDEMPOTENCY_KEY_FAILED` rather than re-sending.
- */
-export const WHATSAPP_SEND_ERROR_CODES = [
-    'VALIDATION_FAILED',
-    'IDEMPOTENCY_KEY_REQUIRED',
-    'PLATFORM_INTEGRATION_DISABLED',
-    'WHATSAPP_NOT_CONNECTED',
-    'WHATSAPP_TOKEN_REJECTED',
-    'CUSTOMER_NOT_FOUND',
-    'WHATSAPP_RECIPIENT_PHONE_MISSING',
-    'WHATSAPP_RECIPIENT_NOT_ALLOWED',
-    'WHATSAPP_TEMPLATE_NOT_APPROVED',
-    'WHATSAPP_RECIPIENT_OPTED_OUT',
-    'WHATSAPP_RATE_LIMITED',
-    'WHATSAPP_ACCOUNT_SUSPENDED',
-    'WHATSAPP_SEND_FAILED',
-    'WHATSAPP_SEND_UNCONFIRMED',
-];