platform-types 1.10.761 → 1.10.763

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',
-];