@mohasinac/appkit 4.53.1 → 4.54.0

package/dist/_internal/server/jobs/core/onOrderCreate.js

@@ -1,77 +1,7 @@
 import { normalizeError } from "../../../../errors/normalize.js";
 import { ORDER_PII_FIELDS, revealPii } from "../../../../security/index.js";
-import { adminNotificationsRepository, storeRepository, userRepository } from "../../../../repositories/index.js";
-import { decryptPii } from "../../../../security/index.js";
-import { sendWhatsAppBusinessMessage, buildPurchaseAnnouncementMessage, } from "../../../../features/whatsapp-bot/server.js";
-import { resolveKeys } from "../../../../core/integration-keys.js";
-import { guardSend, logSuppressedSend } from "../../notifications/send-guard.js";
-async function sendAnnouncement(ctx, toPhone, message, phoneNumberId, accessToken, label, orderId) {
-    try {
-        const sent = await sendWhatsAppBusinessMessage({
-            toPhone,
-            message,
-            phoneNumberId,
-            accessToken,
-        });
-        if (sent) {
-            ctx.logger.info(`Announcement sent to ${label}`, {
-                orderId,
-                toPhone: `...${toPhone.slice(-4)}`,
-            });
-        }
-        else {
-            ctx.logger.error(`Announcement delivery failed for ${label} (non-fatal)`, null, { orderId });
-        }
-    }
-    catch (err) {
-        void normalizeError(err);
-        ctx.logger.error(`Announcement send threw for ${label} (non-fatal)`, err, { orderId });
-    }
-}
-async function notifyStoreOwner(ctx, storeId, message, phoneNumberId, accessToken, orderId) {
-    try {
-        const store = await storeRepository.findBySlug(storeId);
-        if (!store?.ownerId)
-            return;
-        const owner = await userRepository.findById(store.ownerId);
-        const encryptedPhone = owner?.phoneNumber;
-        if (!encryptedPhone)
-            return;
-        const ownerPhone = decryptPii(encryptedPhone);
-        if (ownerPhone) {
-            await sendAnnouncement(ctx, ownerPhone, message, phoneNumberId, accessToken, "store-owner", orderId);
-        }
-    }
-    catch (err) {
-        void normalizeError(err);
-        ctx.logger.error("Store owner lookup failed (non-fatal)", err, { orderId, storeId });
-    }
-}
-/**
- * Seeded credentials are `*_PLACEHOLDER` strings rather than empty, so an
- * emptiness test alone would happily send with a fake token. Mirrors the guard
- * in checkout-value-otp-actions.ts.
- */
-function usable(value) {
-    const v = value?.trim() ?? "";
-    return v && !v.includes("PLACEHOLDER") ? v : "";
-}
-async function resolveWhatsAppCredentials(ctx, orderId) {
-    let db = {};
-    try {
-        db = await resolveKeys();
-    }
-    catch (err) {
-        void normalizeError(err);
-        // Firestore unreachable from the Functions runtime — env-only is still a
-        // valid configuration, so this is a warning, not a failure.
-        ctx.logger.warn("Credential lookup failed — falling back to env", { orderId });
-    }
-    return {
-        phoneNumberId: usable(db.whatsappPhoneNumberId) || usable(ctx.env("WHATSAPP_PHONE_NUMBER_ID")),
-        accessToken: usable(db.whatsappCloudApiToken) || usable(ctx.env("WHATSAPP_CLOUD_API_TOKEN")),
-    };
-}
+import { adminNotificationsRepository } from "../../../../repositories/index.js";
+import { buildPurchaseAnnouncementMessage } from "../../../../features/orders/utils/order-announcement-message.js";
 export async function handleOrderCreate(input, ctx) {
     const { orderId, order } = input;
     const items = order.items ?? [];
@@ -140,37 +70,13 @@ export async function handleOrderCreate(input, ctx) {
         ctx.logger.error("Failed to write admin order notification (non-fatal)", err, { orderId });
     }
     /*
-     * Seller side keeps WhatsApp: it is ONE message to ONE person about their
-     * own sale, which is the case the channel is good at. Credentials resolve
-     * DB-first (Admin → Site Settings → WhatsApp) with an env fallback — this
-     * read `ctx.env()` only until 2026-08-22, so credentials saved in Site
-     * Settings never reached the announcement and it silently no-op'd.
+     * The seller is told about their own sale by the `order_placed`
+     * notification `createOrderForGroup` already sends (in-app + email). This
+     * handler used to ALSO push a WhatsApp Cloud API message here — a duplicate
+     * channel for the same event, and the only thing in this file that needed a
+     * Meta token, a registered number and a billing relationship. Removed with
+     * the rest of the WhatsApp integration on 2026-10-20; no signal was lost,
+     * because the notification path is independent and unchanged.
      */
-    const storeId = order.storeId;
-    if (!storeId) {
-        ctx.logger.info("Order has no storeId — nothing to announce to a seller", { orderId });
-        return;
-    }
-    const { phoneNumberId, accessToken } = await resolveWhatsAppCredentials(ctx, orderId);
-    if (!phoneNumberId || !accessToken) {
-        ctx.logger.info("WhatsApp Cloud API not configured — skipping seller announcement", { orderId });
-        return;
-    }
-    // Audience is "user": a seller receiving news of their own sale is a
-    // marketplace participant, not an operator of the site. Staff exemption is
-    // for the digest and the payout summary, and widening it to "anyone we think
-    // ought to see this" would make the kill switch mean nothing.
-    const guard = {
-        channel: "whatsapp",
-        feature: "order_placed_seller",
-        audience: "user",
-    };
-    const decision = await guardSend(guard);
-    if (!decision.allow) {
-        logSuppressedSend(guard, decision);
-        ctx.logger.info("Seller order announcement suppressed by messaging guard", { orderId, storeId });
-        return;
-    }
-    await notifyStoreOwner(ctx, storeId, message, phoneNumberId, accessToken, orderId);
-    ctx.logger.info(`Order announcement complete`, { orderId, storeId });
+    ctx.logger.info("Order announcement complete", { orderId, storeId: order.storeId ?? null });
 }

package/dist/_internal/server/jobs/core/onOrderStatusChange.d.ts

@@ -6,8 +6,6 @@ export type OrderAfter = {
     userEmail: string;
     productTitle: string;
     trackingNumber?: string;
-    /** Buyer opted into the ₹10 WhatsApp order-updates addon at checkout. */
-    whatsappNotifyAddon?: boolean;
 };
 export type OrderBefore = {
     status: OrderStatus;

package/dist/_internal/server/jobs/core/onOrderStatusChange.js

@@ -54,7 +54,6 @@ export async function handleOrderStatusChange(input, ctx) {
             relatedId: orderId,
             relatedType: "order",
             userEmail,
-            orderWhatsappAddonPaid: after.whatsappNotifyAddon === true,
         });
         // The RTDB mirror that used to live here has been removed. `sendNotification`
         // above is the real path (in-app + email + WhatsApp); the extra

package/dist/_internal/server/jobs/core/onScamReportCreate.js

@@ -30,7 +30,6 @@ export async function handleScamReportCreate(input, ctx) {
                 relatedId: scammerId,
                 relatedType: "scammer",
                 userEmail: reporterPlain?.email ?? undefined,
-                userPhone: reporterPlain?.phoneNumber ?? undefined,
             });
         }
         catch (err) {

package/dist/_internal/server/jobs/core/onScamReportRejected.js

@@ -28,7 +28,6 @@ export async function handleScamReportRejected(input, ctx) {
             relatedId: scammerId,
             relatedType: "scammer",
             userEmail: reporterPlain?.email ?? undefined,
-            userPhone: reporterPlain?.phoneNumber ?? undefined,
         });
     }
     catch (err) {

package/dist/_internal/server/jobs/core/onScamReportVerified.js

@@ -28,7 +28,6 @@ export async function handleScamReportVerified(input, ctx) {
             relatedId: scammerId,
             relatedType: "scammer",
             userEmail: reporterPlain?.email ?? undefined,
-            userPhone: reporterPlain?.phoneNumber ?? undefined,
         });
     }
     catch (err) {

package/dist/_internal/server/jobs/core/paymentWindowTimeout.js

@@ -56,7 +56,6 @@ export async function runPaymentWindowTimeout(ctx) {
                 message: ORDER_MESSAGES.CANCELLED_PAYMENT_WINDOW_MESSAGE(entry.data.productTitle),
                 relatedId: entry.id,
                 relatedType: "order",
-                orderWhatsappAddonPaid: entry.data.whatsappNotifyAddon === true,
             });
         }
         catch (err) {

package/dist/_internal/server/jobs/core/pendingOrderTimeout.js

@@ -67,7 +67,6 @@ export async function runPendingOrderTimeout(ctx) {
                 message: ORDER_MESSAGES.CANCELLED_TIMEOUT_MESSAGE(entry.data.productTitle, timeoutHours),
                 relatedId: entry.id,
                 relatedType: "order",
-                orderWhatsappAddonPaid: entry.data.whatsappNotifyAddon === true,
             });
         }
         catch (err) {

package/dist/_internal/server/notifications/channel-health.d.ts

@@ -1,5 +1,5 @@
 /**
- * Circuit breaker for outbound notification channels (email, WhatsApp).
+ * Circuit breaker for outbound notification channels.
  *
  * Persisted as a singleton Firestore doc `system/channelHealth` so the
  * "is this channel currently known-bad" state survives across requests and
@@ -9,7 +9,11 @@
  * provider). After the cooldown, the next attempt is a half-open probe:
  * its own outcome decides whether the circuit re-closes or re-opens.
  */
-export type NotificationChannel = "email" | "whatsapp";
+/**
+ * Email is the only outbound channel with a transport. "whatsapp" was the
+ * other arm until 2026-10-20, when the Cloud API integration was removed.
+ */
+export type NotificationChannel = "email";
 /**
  * Returns false only when the circuit is open and still within its cooldown
  * window. Any other state (closed, or open-but-cooldown-elapsed) is treated
@@ -20,7 +24,7 @@ export declare function recordChannelOutcome(channel: NotificationChannel, succe
 /**
  * Runs `fn` up to 3 times (500ms then 1.5s between attempts) and records the
  * final outcome against the channel's health state. `fn` must throw on
- * failure — for a helper that returns a boolean instead (e.g. the WhatsApp
+ * failure — for a helper that returns a boolean instead (e.g. a sender
  * Cloud API helpers), convert `false` into a thrown error at the call site
  * before passing it in.
  */

package/dist/_internal/server/notifications/channel-health.js

@@ -1,5 +1,5 @@
 /**
- * Circuit breaker for outbound notification channels (email, WhatsApp).
+ * Circuit breaker for outbound notification channels.
  *
  * Persisted as a singleton Firestore doc `system/channelHealth` so the
  * "is this channel currently known-bad" state survives across requests and
@@ -72,7 +72,7 @@ function delay(ms) {
 /**
  * Runs `fn` up to 3 times (500ms then 1.5s between attempts) and records the
  * final outcome against the channel's health state. `fn` must throw on
- * failure — for a helper that returns a boolean instead (e.g. the WhatsApp
+ * failure — for a helper that returns a boolean instead (e.g. a sender
  * Cloud API helpers), convert `false` into a thrown error at the call site
  * before passing it in.
  */

package/dist/_internal/server/notifications/send-guard.d.ts

@@ -15,7 +15,7 @@
  * message.
  *
  * The guarantee that nothing bypasses this is STRUCTURAL instead: the guard
- * argument is REQUIRED on `sendEmail` and on both WhatsApp senders, so an
+ * argument is REQUIRED on `sendEmail`, so an
  * unguarded send does not typecheck, and `scripts/audit-unguarded-send.mjs`
  * fails the build on a raw `createResendProvider().send()`. Make the wrong
  * thing unrepresentable rather than adding a second layer of defence that has

package/dist/_internal/server/notifications/send-guard.js

@@ -15,7 +15,7 @@
  * message.
  *
  * The guarantee that nothing bypasses this is STRUCTURAL instead: the guard
- * argument is REQUIRED on `sendEmail` and on both WhatsApp senders, so an
+ * argument is REQUIRED on `sendEmail`, so an
  * unguarded send does not typecheck, and `scripts/audit-unguarded-send.mjs`
  * fails the build on a raw `createResendProvider().send()`. Make the wrong
  * thing unrepresentable rather than adding a second layer of defence that has
@@ -69,9 +69,7 @@ export async function guardSend(ctx) {
     if (ctx.audience === "user" && !ctx.transactional) {
         const channelEnabled = ctx.channel === "email"
             ? (messaging?.emailEnabled ?? MESSAGE_BUDGET_DEFAULTS.emailEnabled)
-            : ctx.channel === "whatsapp"
-                ? (messaging?.whatsappEnabled ?? MESSAGE_BUDGET_DEFAULTS.whatsappEnabled)
-                : false; // sms has no sender; if one appears it starts disabled.
+            : false; // sms has no sender; if one appears it starts disabled.
         if (!channelEnabled) {
             return {
                 allow: false,

package/dist/_internal/shared/actions/action-registry.d.ts

@@ -29,7 +29,7 @@ import type { IconKey } from "../../../ui/icons/icon-registry";
 /** What KIND of action — drives default UI affordance (link vs button vs danger). */
 export type ActionKind = "primary" | "secondary" | "danger" | "ghost" | "link" | "chip";
 /** Resource bucket — keyed top-level in the ACTIONS tree. */
-export type ActionResource = "PRODUCT" | "AUCTION" | "PRE_ORDER" | "PRIZE_DRAW" | "DIGITAL_CODE" | "BUNDLE" | "GROUP" | "CATEGORY" | "BRAND" | "SUBLISTING" | "STORE" | "BLOG" | "EVENT" | "SHIPMENT" | "CATALOGUE" | "USER" | "SELLER" | "ADMIN" | "CART" | "CHECKOUT" | "NAV" | "MEDIA" | "SUPPORT" | "LOTTERY" | "TESTER";
+export type ActionResource = "PRODUCT" | "AUCTION" | "PRE_ORDER" | "PRIZE_DRAW" | "DIGITAL_CODE" | "BUNDLE" | "GROUP" | "CATEGORY" | "BRAND" | "SUBLISTING" | "STORE" | "BLOG" | "EVENT" | "REVIEW" | "SHIPMENT" | "CATALOGUE" | "USER" | "SELLER" | "ADMIN" | "CART" | "CHECKOUT" | "NAV" | "MEDIA" | "SUPPORT" | "LOTTERY" | "TESTER";
 /** Confirmation modal config — when set, <Button action={...}> opens
  *  a confirm dialog before firing the actual handler. */
 export interface ActionConfirmation {

package/dist/_internal/shared/actions/action-registry.js

@@ -111,6 +111,28 @@ export const ACTIONS = {
                 confirmLabel: "Delete listing",
             },
         },
+        /*
+         * Clone — ADMIN ONLY, and no confirmation.
+         *
+         * `POST /api/store/products/[id]/duplicate` already strips identity,
+         * analytics, auction bid state and group membership, titles the copy
+         * "… (Copy)" and forces `status: "draft"`. So it creates a draft and
+         * destroys nothing: a confirm dialog on a non-destructive action trains
+         * people to dismiss confirm dialogs.
+         *
+         * 🛑 `permissions: ["admin"]` is narrower than `edit`/`delete` above on
+         * purpose. A seller editing or deleting their own listing is ordinary;
+         * duplicating across the catalogue is a staff tool.
+         */
+        duplicate: {
+            iconKey: "duplicate",
+            id: "product.duplicate",
+            label: "Duplicate",
+            ariaLabel: "Duplicate this listing as a draft",
+            description: "Copy this listing into a new draft, without its bids, analytics or group membership.",
+            kind: "secondary",
+            permissions: ["admin"],
+        },
         "add-to-cart": {
             iconKey: "cart",
             id: "product.add-to-cart",
@@ -321,6 +343,43 @@ export const ACTIONS = {
             kind: "primary",
             categoryTypeScope: ["bundle"],
         },
+        /*
+         * Edit and delete lived only in the ADMIN bucket (`delete-bundle`,
+         * `activate-bundle`, …), so a bundle's own surfaces had nothing
+         * resource-scoped to resolve against. Added here beside `buy-now` so the
+         * owner affordance keys on the resource it is acting on, like every other
+         * bucket.
+         *
+         * 🛑 No `duplicate`. A bundle's members, `bundleCategorySlugs` and
+         * `display.mosaicImages` are all resolved at WRITE time, so a copy would
+         * carry another bundle's resolved state.
+         */
+        edit: {
+            iconKey: "edit",
+            id: "bundle.edit",
+            label: "Edit",
+            ariaLabel: "Edit bundle",
+            description: "Edit this bundle.",
+            kind: "secondary",
+            permissions: ["admin", "seller"],
+            categoryTypeScope: ["bundle"],
+        },
+        delete: {
+            iconKey: "delete",
+            id: "bundle.delete",
+            label: "Delete",
+            ariaLabel: "Delete bundle",
+            description: "Permanently delete this bundle.",
+            kind: "danger",
+            permissions: ["admin", "seller"],
+            categoryTypeScope: ["bundle"],
+            confirmation: {
+                title: "Delete this bundle?",
+                body: "This cannot be undone. The products inside it are NOT deleted — only the bundle that groups them and its discounted price.",
+                confirmLabel: "Delete bundle",
+                confirmKind: "danger",
+            },
+        },
     },
     /*
      * These four buckets were literally `{}` for months while their editors
@@ -660,34 +719,6 @@ export const ACTIONS = {
             kind: "ghost",
             permissions: ["seller", "admin"],
         },
-        // ── WhatsApp integration ────────────────────────────────────────────
-        "whatsapp-connect": {
-            iconKey: "link",
-            id: "store.whatsapp-connect",
-            label: "Save & Connect",
-            ariaLabel: "Save WhatsApp credentials and connect",
-            description: "Save WhatsApp Business credentials and establish connection.",
-            kind: "primary",
-            permissions: ["seller", "admin"],
-        },
-        "whatsapp-catalog-sync": {
-            iconKey: "retry",
-            id: "store.whatsapp-catalog-sync",
-            label: "Push to WhatsApp",
-            ariaLabel: "Sync products to WhatsApp catalog",
-            description: "Push published standard products to WhatsApp Business Catalog.",
-            kind: "secondary",
-            permissions: ["seller", "admin"],
-        },
-        "whatsapp-catalog-import": {
-            iconKey: "upload",
-            id: "store.whatsapp-catalog-import",
-            label: "Import from WhatsApp",
-            ariaLabel: "Import products from WhatsApp catalog",
-            description: "Import products from WhatsApp Catalog as drafts.",
-            kind: "secondary",
-            permissions: ["seller", "admin"],
-        },
         // ── Google Reviews integration ──────────────────────────────────────
         "google-reviews-sync": {
             iconKey: "retry",
@@ -1042,7 +1073,76 @@ export const ACTIONS = {
             },
         },
     },
+    /*
+     * There was no REVIEW bucket at all, while review actions sat scattered
+     * across three others — ADMIN (approve / reject / feature), STORE (reply /
+     * contest) and USER (write-review) — and NOTHING anywhere for a reviewer
+     * editing or deleting their own review. That is the gap a buyer hits on a
+     * product page, so it is the one this bucket is for.
+     */
+    REVIEW: {
+        edit: {
+            iconKey: "edit",
+            id: "review.edit",
+            label: "Edit review",
+            ariaLabel: "Edit your review",
+            description: "Edit a review you wrote.",
+            kind: "secondary",
+        },
+        delete: {
+            iconKey: "delete",
+            id: "review.delete",
+            label: "Delete review",
+            ariaLabel: "Delete your review",
+            description: "Permanently delete a review you wrote.",
+            kind: "danger",
+            confirmation: {
+                title: "Delete your review?",
+                body: "This cannot be undone. The seller's reply to it goes too, and the product's rating is recalculated without your score.",
+                confirmLabel: "Delete review",
+                confirmKind: "danger",
+            },
+        },
+        write: {
+            iconKey: "review",
+            id: "review.write",
+            label: "Write a review",
+            ariaLabel: "Write a review for this item",
+            description: "Write a review for an item you bought.",
+            kind: "primary",
+        },
+    },
     EVENT: {
+        /*
+         * This bucket had only register / cancel-registration / draw-raffle-winner
+         * — no edit, no delete — so the owner affordance on an event card or detail
+         * page had no registry entry to resolve its label and confirm copy from,
+         * and Rule #7 forbids inlining them.
+         */
+        edit: {
+            iconKey: "edit",
+            id: "event.edit",
+            label: "Edit",
+            ariaLabel: "Edit event",
+            description: "Edit this event.",
+            kind: "secondary",
+            permissions: ["admin"],
+        },
+        delete: {
+            iconKey: "delete",
+            id: "event.delete",
+            label: "Delete",
+            ariaLabel: "Delete event",
+            description: "Permanently delete this event.",
+            kind: "danger",
+            permissions: ["admin"],
+            confirmation: {
+                title: "Delete this event?",
+                body: "This cannot be undone. Entries already recorded against it are removed with it, so a participant loses their place.",
+                confirmLabel: "Delete event",
+                confirmKind: "danger",
+            },
+        },
         "register": {
             iconKey: "user",
             id: "event.register",

package/dist/_internal/shared/checkout/order-math.d.ts

@@ -170,7 +170,7 @@ export interface PayableOrderLike {
  * money bug in all four payout paths (`autoPayoutEligibility`,
  * `weeklyPayoutEligibility`, and both `seller-actions` entry points). That
  * field is the GRAND TOTAL — `checkout/actions.ts` builds it as
- * `goods − coupon + shipping + codHandling + whatsappNotify + giftWrap +
+ * `goods − coupon + shipping + codHandling + giftWrap +
  * shipmentProtection + platformFee + platformFeeGst + emiSurcharge + gstAmount`
  * — so using it as the payout base did three wrong things at once:
  *

package/dist/_internal/shared/checkout/order-math.js

@@ -264,7 +264,7 @@ export function allocateAcrossMembers(total, weights) {
  * money bug in all four payout paths (`autoPayoutEligibility`,
  * `weeklyPayoutEligibility`, and both `seller-actions` entry points). That
  * field is the GRAND TOTAL — `checkout/actions.ts` builds it as
- * `goods − coupon + shipping + codHandling + whatsappNotify + giftWrap +
+ * `goods − coupon + shipping + codHandling + giftWrap +
  * shipmentProtection + platformFee + platformFeeGst + emiSurcharge + gstAmount`
  * — so using it as the payout base did three wrong things at once:
  *

package/dist/_internal/shared/features/categories/bundle-copy.d.ts

@@ -72,7 +72,7 @@ export declare const BUNDLE_COPY: {
     readonly adminEditor: {
         readonly loading: "Loading bundle…";
         readonly saveButton: (saving: boolean, isEdit: boolean) => "Save changes" | "Saving…" | "Create bundle";
-        readonly deleteButton: (deleting: boolean) => "Deleting…" | "Delete bundle";
+        readonly deleteButton: (deleting: boolean) => "Delete bundle" | "Deleting…";
         readonly deleteConfirm: "Delete this bundle? This action cannot be undone.";
         readonly fields: {
             readonly nameLabel: "Name *";

package/dist/_internal/shared/features/checkout/config.d.ts

@@ -6,8 +6,6 @@ export declare const CHECKOUT_DEFAULT_COMMISSIONS: {
     readonly codDepositPercent: 10;
     readonly codHandlingFeeMin: 200;
     readonly codHandlingFeePercent: 10;
-    readonly whatsappNotifyFeeEnabled: true;
-    readonly whatsappNotifyFee: 10;
     readonly giftWrapFeeEnabled: true;
     readonly giftWrapFee: 49;
     readonly shipmentProtectionFeeEnabled: true;

package/dist/_internal/shared/features/checkout/config.js

@@ -13,8 +13,6 @@ export const CHECKOUT_DEFAULT_COMMISSIONS = {
     // Mirrors the SiteSettingsDocument defaults, which enable every add-on.
     // Consequence of the mirror: if the settings read fails, an add-on already
     // ticked on the cart document is still billed rather than silently dropped.
-    whatsappNotifyFeeEnabled: true,
-    whatsappNotifyFee: 10,
     giftWrapFeeEnabled: true,
     giftWrapFee: 49,
     shipmentProtectionFeeEnabled: true,

package/dist/_internal/shared/features/messaging/config.d.ts

@@ -16,7 +16,12 @@
  * and find the budget already covers them. A channel that is born capped
  * cannot repeat what email did.
  */
-export type MessageChannel = "email" | "whatsapp" | "sms";
+/**
+ * `whatsapp` was removed 2026-10-20 with the Cloud API integration. `sms`
+ * stays declared with no sender — the ceiling exists so one cannot ship
+ * uncapped — and `email` is the only channel with a live transport.
+ */
+export type MessageChannel = "email" | "sms";
 /**
  * Who the message is FOR — which is what the kill switch keys on.
  *
@@ -76,13 +81,12 @@ export type SendDecision = {
 /**
  * Defaults, mirrored into `DEFAULT_SITE_SETTINGS_DATA.messaging`.
  *
- * 🛑 `emailEnabled` and `whatsappEnabled` default to FALSE. An install that
+ * 🛑 `emailEnabled` defaults to FALSE. An install that
  * has not made a decision should be quiet, not loud — the opposite default is
  * how a fresh deploy mails real people from a half-configured site.
  */
 export declare const MESSAGE_BUDGET_DEFAULTS: {
     readonly emailEnabled: false;
-    readonly whatsappEnabled: false;
     readonly dailyCeiling: {
         /**
          * Resend's free tier is 100/day. 80 is not timidity — the counter is
@@ -92,8 +96,6 @@ export declare const MESSAGE_BUDGET_DEFAULTS: {
          * headroom is what stops "at the limit" from becoming "over it".
          */
         readonly email: 80;
-        /** Meta's pricing is per-conversation, not per-message; this is a sanity bound, not a tier limit. */
-        readonly whatsapp: 200;
         /** No sender exists yet. Present so one cannot ship uncapped. */
         readonly sms: 50;
     };

package/dist/_internal/shared/features/messaging/config.js

@@ -9,13 +9,12 @@
 /**
  * Defaults, mirrored into `DEFAULT_SITE_SETTINGS_DATA.messaging`.
  *
- * 🛑 `emailEnabled` and `whatsappEnabled` default to FALSE. An install that
+ * 🛑 `emailEnabled` defaults to FALSE. An install that
  * has not made a decision should be quiet, not loud — the opposite default is
  * how a fresh deploy mails real people from a half-configured site.
  */
 export const MESSAGE_BUDGET_DEFAULTS = {
     emailEnabled: false,
-    whatsappEnabled: false,
     dailyCeiling: {
         /**
          * Resend's free tier is 100/day. 80 is not timidity — the counter is
@@ -25,8 +24,6 @@ export const MESSAGE_BUDGET_DEFAULTS = {
          * headroom is what stops "at the limit" from becoming "over it".
          */
         email: 80,
-        /** Meta's pricing is per-conversation, not per-message; this is a sanity bound, not a tier limit. */
-        whatsapp: 200,
         /** No sender exists yet. Present so one cannot ship uncapped. */
         sms: 50,
     },

package/dist/_internal/shared/features/site-settings/fees.d.ts

@@ -27,8 +27,6 @@ import type { EmiSettings } from "../emi/schedule";
  * and each `compute*Fee` helper carries its own default.
  */
 export interface BuyerFacingFees {
-    whatsappNotifyFeeEnabled?: boolean;
-    whatsappNotifyFee?: number;
     giftWrapFeeEnabled?: boolean;
     giftWrapFee?: number;
     shipmentProtectionFeeEnabled?: boolean;

package/dist/_internal/shared/features/site-settings/fees.js

@@ -13,8 +13,6 @@ export function toBuyerFacingFees(commissions) {
     if (!commissions)
         return null;
     return {
-        whatsappNotifyFeeEnabled: commissions.whatsappNotifyFeeEnabled,
-        whatsappNotifyFee: commissions.whatsappNotifyFee,
         giftWrapFeeEnabled: commissions.giftWrapFeeEnabled,
         giftWrapFee: commissions.giftWrapFee,
         shipmentProtectionFeeEnabled: commissions.shipmentProtectionFeeEnabled,

package/dist/_internal/shared/features/site-settings/supplier-of-record.d.ts

@@ -0,0 +1,56 @@
+/**
+ * The platform's own supplier-of-record identity, injected once at boot.
+ *
+ * ── Why this seam exists ──────────────────────────────────────────────────
+ *
+ * `appkit.config.js → business` is documented as "THE one owner of the
+ * business's statutory identity", and it records what it was created to end:
+ * the legal name, address, GSTIN and support channels had lived in five places
+ * that already disagreed — four different support addresses published, the
+ * registered address saying Solapur while the warehouse said Hyderabad.
+ *
+ * But that file belongs to the CONSUMER, and appkit has no runtime reader for
+ * it. `resolveSupplierIdentity` therefore read `siteSettings.gst.*` instead,
+ * which quietly made the invoice path a SIXTH owner — and the one that decides
+ * what a tax invoice says about who issued it.
+ *
+ * So the consumer injects it at boot, the same way `configureMarketDefaults`
+ * injects currency and locale: one call in `providers.config.ts`, values read
+ * from `src/constants/business.ts`, which reads `appkit.config.js`. One owner,
+ * one hop.
+ *
+ * 🛑 This is NOT a cache of site settings and must not become one. Whether to
+ * charge GST at all stays `siteSettings.gst.enabled` — an operational switch an
+ * admin owns. WHO the supplier is is a fact about the registered entity, is
+ * legally required to be published, and belongs in a committed file.
+ *
+ * @tag domain:site-settings
+ * @tag layer:shared
+ * @tag access:isomorphic
+ * @tag sideEffects:module-state
+ */
+export interface PlatformSupplierIdentity {
+    gstin?: string;
+    legalName?: string;
+    /** One line, as it should appear in an invoice header. */
+    address?: string;
+}
+/**
+ * Register the platform's statutory identity. Call once, at boot.
+ *
+ * Merges rather than replaces, so a partial call cannot blank a field that was
+ * already supplied — the same shape `configureMarketDefaults` uses.
+ */
+export declare function configurePlatformSupplier(identity: PlatformSupplierIdentity): void;
+/**
+ * The registered identity, or an empty object when nothing was injected.
+ *
+ * 🛑 Returns `{}` rather than throwing, and the caller must treat a missing
+ * GSTIN as "not a tax invoice" — which `resolveSupplierIdentity` already does
+ * via `source: "none"`. Throwing here would turn a misconfigured deployment
+ * into a failed CHECKOUT, and an order that cannot be placed is worse than an
+ * invoice that correctly declines to call itself a tax invoice.
+ */
+export declare function getPlatformSupplier(): PlatformSupplierIdentity;
+/** Reset — for tests and for the seed CLI's isolated runs. */
+export declare function resetPlatformSupplier(): void;