@mohasinac/appkit 4.53.2 → 4.54.1

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;

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

@@ -0,0 +1,57 @@
+/**
+ * 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
+ */
+let _identity = {};
+/**
+ * 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 function configurePlatformSupplier(identity) {
+    _identity = { ..._identity, ...identity };
+}
+/**
+ * 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 function getPlatformSupplier() {
+    return _identity;
+}
+/** Reset — for tests and for the seed CLI's isolated runs. */
+export function resetPlatformSupplier() {
+    _identity = {};
+}

package/dist/_internal/shared/fees/calculator.d.ts

@@ -82,14 +82,6 @@ export interface CodHandlingFeeRates {
 }
 /** COD handling fee charged to the buyer: max(fixed floor, subtotal × percent). */
 export declare function computeCodHandlingFee(subtotal: number, rates: CodHandlingFeeRates): number;
-export interface WhatsAppNotifyFeeRates {
-    /** Admin master toggle — the addon isn't charged (even if the buyer selected it) unless this is true. */
-    whatsappNotifyFeeEnabled?: boolean;
-    /** Flat rupee fee charged when the buyer opts in. Falls back to ₹10. */
-    whatsappNotifyFee?: number;
-}
-/** Flat WhatsApp order-updates addon fee — charged only when the buyer opted in AND the admin has the addon enabled. */
-export declare function computeWhatsAppNotifyFee(addonSelected: boolean, rates: WhatsAppNotifyFeeRates): number;
 export interface GiftWrapFeeRates {
     /** Admin master toggle — the addon isn't charged (even if the buyer selected it) unless this is true. */
     giftWrapFeeEnabled?: boolean;

package/dist/_internal/shared/fees/calculator.js

@@ -82,13 +82,6 @@ export function computeCodHandlingFee(subtotal, rates) {
     const percentFee = roundRupees(subtotal * (percent / 100));
     return Math.max(min, percentFee);
 }
-const DEFAULT_WHATSAPP_NOTIFY_FEE = 10;
-/** Flat WhatsApp order-updates addon fee — charged only when the buyer opted in AND the admin has the addon enabled. */
-export function computeWhatsAppNotifyFee(addonSelected, rates) {
-    if (!addonSelected || !rates.whatsappNotifyFeeEnabled)
-        return 0;
-    return rates.whatsappNotifyFee ?? DEFAULT_WHATSAPP_NOTIFY_FEE;
-}
 const DEFAULT_GIFT_WRAP_FEE = 49;
 /** Flat gift-wrap addon fee — charged only when the buyer opted in AND the admin has the addon enabled. */
 export function computeGiftWrapFee(addonSelected, rates) {

package/dist/_internal/shared/listing-types/tiers.d.ts

@@ -0,0 +1,94 @@
+/**
+ * Which listing types a store may create: the basic/advanced split.
+ *
+ * ── The rule ──────────────────────────────────────────────────────────────
+ *
+ * `standard`, `spares` and `auction` are BASIC — every store can use them.
+ * The other seven are ADVANCED and need the `advanced_listing_types`
+ * capability, because each carries an obligation a new seller has not agreed
+ * to yet: a pre-order takes money for stock that does not exist, a prize draw
+ * is a regulated promotion, a classified happens off-platform with no escrow,
+ * a digital code must be delivered from a pool the seller has to keep stocked,
+ * and a live listing is an animal.
+ *
+ * ── Why a Record and not an array ─────────────────────────────────────────
+ *
+ * 🛑 `Record<ListingType, ListingTypeTier>`, so adding a member to the union
+ * is a COMPILE error here rather than a silent omission that defaults to
+ * whichever branch the code happens to fall through to.
+ * `features/products/types/index.ts` warns that adding a union member touches
+ * 21 named sites of which only 11 are compile-checked; this file is written to
+ * be one of the eleven. Root Cause #61.
+ *
+ * ── Why `capabilities` is `readonly string[]` and not `StoreCapability[]` ──
+ *
+ * Two reasons, and the first is the honest one: that is what is actually
+ * STORED. `storeFirestoreSchema` validates the field as `z.array(z.string())`,
+ * so a capability that is not a union member round-trips today and this helper
+ * must not pretend otherwise. The second is that it keeps this module free of
+ * an import from `features/auth/permissions/constants`, which is the kind of
+ * cross-feature edge `audit-import-cycles` exists to watch.
+ *
+ * A `StoreCapability[]` is assignable to it, so a typed caller loses nothing.
+ */
+import type { ListingType } from "../../../features/products/types/index";
+import type { JsonValue } from "../../../schemas/types";
+export type ListingTypeTier = "basic" | "advanced";
+/**
+ * The capability that unlocks every advanced type at once.
+ *
+ * One flag rather than seven, deliberately: the question a seller is actually
+ * answering is "do I want the complicated listing kinds", and seven checkboxes
+ * invite six of them to be wrong. An admin who needs finer control has the
+ * per-type legacy grants below.
+ */
+export declare const ADVANCED_LISTING_TYPE_CAPABILITY = "advanced_listing_types";
+export declare const LISTING_TYPE_TIER: Record<ListingType, ListingTypeTier>;
+export declare function isAdvancedListingType(listingType: ListingType): boolean;
+/**
+ * Does this capability array carry the advanced-types grant?
+ *
+ * Exists so no call site has to spell the capability string, and so none has
+ * to cast: `capabilities` is `StoreCapability[]` in typed code and
+ * `string[]` as stored, and an `.includes()` across that boundary is where an
+ * `as never` gets reached for — which silences every other check on the
+ * expression, not just the one being worked around.
+ */
+export declare function hasAdvancedListingTypes(capabilities: readonly string[] | null | undefined): boolean;
+/** The types every store can use, with no capability at all. */
+export declare const BASIC_LISTING_TYPES: ListingType[];
+export declare const ADVANCED_LISTING_TYPES: ListingType[];
+export interface ListingTypeAccessContext {
+    /** Admins and employees bypass the tier entirely. */
+    isPrivileged?: boolean;
+    /** The store's stored capability array. Absent/empty is treated as none. */
+    capabilities?: readonly string[] | null;
+}
+/**
+ * May this store create or convert to this listing type?
+ *
+ * Pure — takes the capability array the caller already holds rather than
+ * re-reading the store. Every gate site in the codebase has the store document
+ * in scope already, and a helper that fetched would add one Firestore read per
+ * product write against Rule #6's round-trip budget.
+ */
+export declare function isListingTypeAllowedFor(listingType: ListingType, ctx?: ListingTypeAccessContext): boolean;
+/** Every type this store may use, for building a picker or filtering nav. */
+export declare function listingTypesAllowedFor(ctx?: ListingTypeAccessContext): ListingType[];
+/**
+ * Throwing form, for the server-side write paths.
+ *
+ * 🛑 `listingType` being absent is ALLOWED and must stay that way. Both product
+ * schemas declare it optional, and a partial update that touches only `status`
+ * or `stockQuantity` carries no type at all — refusing those would break every
+ * stock decrement and status flip in the app. The gate's job is to refuse a
+ * NAMED advanced type, not to require one.
+ *
+ * 🛑 On an UPDATE, the caller must additionally compare against the STORED
+ * type and skip this when they match — see `sellerUpdateProduct`. Every
+ * per-type edit page re-sends its own type literal, so asserting on the
+ * submitted value alone locks a seller out of editing listings they already
+ * own as soon as the capability is withdrawn. The rule is about creating and
+ * converting, not about touching.
+ */
+export declare function assertListingTypeAllowed(listingType: JsonValue | undefined, ctx?: ListingTypeAccessContext): void;