@mohasinac/appkit 4.53.2 → 4.54.0

package/dist/ui/components/HorizontalScroller.js

@@ -2,6 +2,7 @@
 import { jsx as _jsx, jsxs as _jsxs } from "react/jsx-runtime";
 import { useRef, useState, useEffect, useCallback, } from "react";
 import { ChevronLeft, ChevronRight } from "lucide-react";
+import { CarouselNav } from "./CarouselNav.js";
 const BREAKPOINTS = [
     ["2xl", 1536],
     ["xl", 1280],
@@ -21,12 +22,23 @@ function resolvePerView(perView, containerWidth) {
     }
     return 1;
 }
-export function HorizontalScroller({ children, className = "", gap = 16, snapToItems, showArrows, arrowSize = "md", arrowStyle = "circle", showScrollbar, scrollContainerRef: externalRef, onScroll, items, renderItem, keyExtractor, perView, rows = 1, autoScroll, autoScrollInterval = 3500, minItemWidth, pauseOnHover = false, itemClassName = "", loop = false, }) {
+export function HorizontalScroller({ children, className = "", gap = 16, snapToItems, showArrows, arrowSize = "md", arrowStyle = "circle", showScrollbar, scrollContainerRef: externalRef, onScroll, items, renderItem, keyExtractor, perView, rows = 1, autoScroll, autoScrollInterval = 3500, minItemWidth, pauseOnHover = false, itemClassName = "", loop = false, showNav = false, navAriaLabel, }) {
     const [itemWidth, setItemWidth] = useState(undefined);
     const [colCount, setColCount] = useState(typeof perView === "number" ? perView : 3);
     const [isPaused, setIsPaused] = useState(false);
     const [atStart, setAtStart] = useState(true);
     const [atEnd, setAtEnd] = useState(true);
+    /*
+     * Page position, for the optional `showNav` indicator.
+     *
+     * 🛑 Derived from scroll geometry, never stored as the source of truth: the
+     * rail is a native scroller and a user can drag it to any offset, so an index
+     * this component *decided* would disagree with where the content actually is
+     * the first time someone swipes. One page = one viewport width, matching what
+     * `scrollBy` already moves.
+     */
+    const [pageIndex, setPageIndex] = useState(0);
+    const [pageCount, setPageCount] = useState(1);
     const internalRef = useRef(null);
     const containerRef = (externalRef ??
         internalRef);
@@ -91,6 +103,11 @@ export function HorizontalScroller({ children, className = "", gap = 16, snapToI
             return;
         // 1px tolerance for sub-pixel rounding
         const maxScroll = el.scrollWidth - el.clientWidth;
+        const width = el.clientWidth;
+        if (width > 0) {
+            setPageCount(Math.max(1, Math.ceil(el.scrollWidth / width)));
+            setPageIndex(Math.round(el.scrollLeft / width));
+        }
         if (maxScroll <= 1) {
             setAtStart(true);
             setAtEnd(true);
@@ -99,6 +116,12 @@ export function HorizontalScroller({ children, className = "", gap = 16, snapToI
         setAtStart(el.scrollLeft <= 1);
         setAtEnd(el.scrollLeft >= maxScroll - 1);
     }, [containerRef]);
+    const goToPage = useCallback((page) => {
+        const el = containerRef.current;
+        if (!el)
+            return;
+        el.scrollTo({ left: page * el.clientWidth, behavior: "smooth" });
+    }, [containerRef]);
     const handleKeyDown = useCallback((e) => {
         if (e.key === "ArrowRight") {
             e.preventDefault();
@@ -196,6 +219,23 @@ export function HorizontalScroller({ children, className = "", gap = 16, snapToI
         updateExtents();
         onScroll?.();
     };
+    /*
+     * The in-flow position indicator.
+     *
+     * 🛑 This is the fix for "no affordance on a phone", and it deliberately does
+     * NOT un-hide the absolute arrows below 640px. Those are `display:none` there
+     * for a documented reason — a 44px circle has nowhere to go over a
+     * single-column card, and `--with-arrows` reserves 2 × 44px of wrapper gutter
+     * to seat them, which on a narrow screen is width taken from the card itself.
+     * An in-flow control needs no gutter and no breakpoint, so the affordance
+     * exists at every width instead of appearing at one.
+     *
+     * No `progressMs`: a rail's autoScroll advances by 0.8 of a viewport rather
+     * than one page, so a fill timed to the interval would not line up with the
+     * segment it sits in. A position cue that is right beats a progress cue that
+     * is approximately right.
+     */
+    const navNode = showNav && pageCount > 1 ? (_jsx(CarouselNav, { count: pageCount, index: pageIndex, onSelect: goToPage, onPrev: () => scrollBy(-1), onNext: () => scrollBy(1), tone: "on-surface", atStart: atStart, atEnd: atEnd, loop: loop, paused: isPaused, ariaLabel: navAriaLabel ?? "Scroll position", className: "appkit-hscroller__nav" })) : null;
     if (showArrows) {
         const prevDisabled = !loop && atStart;
         const nextDisabled = !loop && atEnd;
@@ -206,9 +246,9 @@ export function HorizontalScroller({ children, className = "", gap = 16, snapToI
                 className,
             ]
                 .filter(Boolean)
-                .join(" "), tabIndex: 0, onKeyDown: handleKeyDown, ...interactionHandlers, "data-section": "horizontalscroller-div-511", children: [!arrowsHidden && (_jsx("button", { type: "button", onClick: () => scrollBy(-1), "aria-label": "Previous", "aria-disabled": prevDisabled || undefined, disabled: prevDisabled, className: `appkit-hscroller__arrow appkit-hscroller__arrow--prev appkit-hscroller__arrow--${arrowSize} ${arrowStyle === "full-height" ? "appkit-hscroller__arrow--full-height" : ""}`, children: _jsx(ChevronLeft, { className: "w-4 h-4" }) })), _jsx("div", { ref: containerRef, onScroll: combinedOnScroll, className: scrollerCls(snapToItems, showScrollbar), style: { gap: `${gap}px` }, "data-section": "horizontalscroller-div-512", children: content }), !arrowsHidden && (_jsx("button", { type: "button", onClick: () => scrollBy(1), "aria-label": "Next", "aria-disabled": nextDisabled || undefined, disabled: nextDisabled, className: `appkit-hscroller__arrow appkit-hscroller__arrow--next appkit-hscroller__arrow--${arrowSize} ${arrowStyle === "full-height" ? "appkit-hscroller__arrow--full-height" : ""}`, children: _jsx(ChevronRight, { className: "w-4 h-4" }) }))] }));
+                .join(" "), tabIndex: 0, onKeyDown: handleKeyDown, ...interactionHandlers, "data-section": "horizontalscroller-div-511", children: [!arrowsHidden && (_jsx("button", { type: "button", onClick: () => scrollBy(-1), "aria-label": "Previous", "aria-disabled": prevDisabled || undefined, disabled: prevDisabled, className: `appkit-hscroller__arrow appkit-hscroller__arrow--prev appkit-hscroller__arrow--${arrowSize} ${arrowStyle === "full-height" ? "appkit-hscroller__arrow--full-height" : ""}`, children: _jsx(ChevronLeft, { className: "w-4 h-4" }) })), _jsx("div", { ref: containerRef, onScroll: combinedOnScroll, className: scrollerCls(snapToItems, showScrollbar), style: { gap: `${gap}px` }, "data-section": "horizontalscroller-div-512", children: content }), !arrowsHidden && (_jsx("button", { type: "button", onClick: () => scrollBy(1), "aria-label": "Next", "aria-disabled": nextDisabled || undefined, disabled: nextDisabled, className: `appkit-hscroller__arrow appkit-hscroller__arrow--next appkit-hscroller__arrow--${arrowSize} ${arrowStyle === "full-height" ? "appkit-hscroller__arrow--full-height" : ""}`, children: _jsx(ChevronRight, { className: "w-4 h-4" }) })), navNode] }));
     }
-    return (_jsx("div", { className: ["appkit-hscroller", className].filter(Boolean).join(" "), tabIndex: 0, onKeyDown: handleKeyDown, ...interactionHandlers, "data-section": "horizontalscroller-div-513", children: _jsx("div", { ref: containerRef, onScroll: combinedOnScroll, className: scrollerCls(snapToItems, showScrollbar), style: { gap: `${gap}px` }, "data-section": "horizontalscroller-div-514", children: content }) }));
+    return (_jsxs("div", { className: ["appkit-hscroller", className].filter(Boolean).join(" "), tabIndex: 0, onKeyDown: handleKeyDown, ...interactionHandlers, "data-section": "horizontalscroller-div-513", children: [_jsx("div", { ref: containerRef, onScroll: combinedOnScroll, className: scrollerCls(snapToItems, showScrollbar), style: { gap: `${gap}px` }, "data-section": "horizontalscroller-div-514", children: content }), navNode] }));
 }
 function scrollerCls(snapToItems, showScrollbar) {
     return [

package/dist/ui/components/ImageMosaic.d.ts

@@ -1,11 +1,18 @@
 import React from "react";
 /** Below this there is nothing to arrange, so the caller should render nothing. */
 export declare const MOSAIC_MIN = 3;
+/**
+ * `band` — the category-hero strip this was built for (180/260px).
+ * `hero`  — the homepage hero's right column, roughly double height.
+ */
+export type ImageMosaicSize = "band" | "hero";
 export interface ImageMosaicProps {
     /** Image URLs, most important first. Fewer than `MOSAIC_MIN` renders null. */
     images: readonly string[];
     /** Describes the SUBJECT, not the images — one alt for a decorative group. */
     alt: string;
+    /** Height preset. Defaults to `"band"`, the original behaviour. */
+    size?: ImageMosaicSize;
     className?: string;
 }
 /**
@@ -40,4 +47,4 @@ export interface ImageMosaicProps {
  * breaks SSR/hydration agreement and makes the page feel unstable — and it is
  * the shape Root Cause #25 is about on the seed side.
  */
-export declare function ImageMosaic({ images, alt, className }: ImageMosaicProps): React.JSX.Element | null;
+export declare function ImageMosaic({ images, alt, size, className }: ImageMosaicProps): React.JSX.Element | null;

package/dist/ui/components/ImageMosaic.js

@@ -37,10 +37,11 @@ export const MOSAIC_MIN = 3;
  * breaks SSR/hydration agreement and makes the page feel unstable — and it is
  * the shape Root Cause #25 is about on the seed side.
  */
-export function ImageMosaic({ images, alt, className }) {
+export function ImageMosaic({ images, alt, size = "band", className }) {
     const tiles = images.filter(Boolean).slice(0, MOSAIC_MAX);
     if (tiles.length < MOSAIC_MIN)
         return null;
     const [lead, ...rest] = tiles;
-    return (_jsxs(Div, { className: `appkit-image-mosaic ${className ?? ""}`, role: "img", "aria-label": alt, children: [_jsx(Div, { className: "appkit-image-mosaic__lead", children: _jsx(MediaImage, { src: lead, alt: "", size: "card" }) }), _jsx(Div, { className: "appkit-image-mosaic__rest", children: rest.map((src, i) => (_jsx(Div, { className: "appkit-image-mosaic__tile", children: _jsx(MediaImage, { src: src, alt: "", size: "thumbnail" }) }, `${src}-${i}`))) })] }));
+    const sizeClass = size === "hero" ? "appkit-image-mosaic--hero" : "";
+    return (_jsxs(Div, { className: `appkit-image-mosaic ${sizeClass} ${className ?? ""}`, role: "img", "aria-label": alt, children: [_jsx(Div, { className: "appkit-image-mosaic__lead", children: _jsx(MediaImage, { src: lead, alt: "", size: "card" }) }), _jsx(Div, { className: "appkit-image-mosaic__rest", children: rest.map((src, i) => (_jsx(Div, { className: "appkit-image-mosaic__tile", children: _jsx(MediaImage, { src: src, alt: "", size: "thumbnail" }) }, `${src}-${i}`))) })] }));
 }

package/dist/ui/components/ImageMosaic.style.css

@@ -27,6 +27,28 @@
   }
 }
 
+/*
+ * `size="hero"` — the homepage hero's right column.
+ *
+ * 🛑 A separate modifier rather than a caller `className` height, because the
+ * fixed-height rule above is this primitive's OWN decision (see the header) and
+ * a consumer utility would simply fight it — with `important: true` in both
+ * Tailwind configs, which of the two wins is decided by emission order, not by
+ * the author. The band height is tuned for a category title; a hero column
+ * standing beside a `size="7xl"` headline needs roughly double or the mosaic
+ * reads as a letterboxed strip next to the copy.
+ */
+.appkit-image-mosaic--hero {
+  height: clamp(320px, 34vw, 460px);
+  border-radius: var(--appkit-radius-2xl);
+}
+
+@media (min-width: 768px) {
+  .appkit-image-mosaic--hero {
+    height: clamp(360px, 34vw, 480px);
+  }
+}
+
 .appkit-image-mosaic__lead,
 .appkit-image-mosaic__tile {
   position: relative;

package/dist/ui/components/Layout.style.css

@@ -324,6 +324,12 @@
 .appkit-section--tone-page-header { background-image: var(--appkit-gradient-page-header); }
 .appkit-section--tone-hero        { background-image: var(--appkit-gradient-section-mesh); }
 .appkit-section--tone-accent-banner { background-image: var(--appkit-gradient-accent-banner); }
+/* The variant layer finally exposing --appkit-gradient-whatsapp-card, which
+   had existed in the token layer with that exact name and NO consumer. The
+   community card used `accent-banner` instead — the same primary→secondary
+   gradient as CTABannerSection two sections below it, which is a real part of
+   why the homepage read monotonous. */
+.appkit-section--tone-whatsapp    { background-image: var(--appkit-gradient-whatsapp-card); }
 
 /* Semantic — Ul/Ol marker presets */
 .appkit-list--marker-disc    { list-style: disc; padding-left: 1.25rem; }

package/dist/ui/components/Semantic.d.ts

@@ -41,7 +41,7 @@ import type { SurfaceProps, RoundedKey, PaddingKey, BorderKey, SurfaceKey } from
  * `--appkit-gradient-*` CSS variable so admin custom themes restyle the
  * section without consumer changes.
  */
-export type SectionTone = "plain" | "page-header" | "hero" | "accent-banner";
+export type SectionTone = "plain" | "page-header" | "hero" | "accent-banner" | "whatsapp";
 type SemanticColor = "default" | "primary" | "muted" | "faint" | "inverse" | "success" | "warning" | "error" | "info";
 type SectionLayout = "default" | "flex" | "flex-col" | "flex-sm-row" | "flex-sm-row-between";
 type SectionGap = "none" | "xs" | "sm" | "md" | "lg";
@@ -62,7 +62,8 @@ export interface SectionProps extends React.HTMLAttributes<HTMLElement>, Surface
     /**
      * Themed background tone. Defaults to `"plain"`. Use `"page-header"` for
      * subtle gradient page-headers, `"hero"` for radial mesh hero backgrounds,
-     * `"accent-banner"` for primary→secondary brand banners.
+     * `"accent-banner"` for primary→secondary brand banners, `"whatsapp"` for
+     * the WhatsApp-brand green→teal community card.
      */
     tone?: SectionTone;
     /** Scoped color/gradient/image background — an alternative to `tone` for admin/CMS-configured section backgrounds. Renders behind `children`, absolutely positioned within the section. */

package/dist/ui/components/Semantic.js

@@ -6,6 +6,7 @@ const SECTION_TONE_MAP = {
     "page-header": "appkit-section--tone-page-header",
     hero: "appkit-section--tone-hero",
     "accent-banner": "appkit-section--tone-accent-banner",
+    whatsapp: "appkit-section--tone-whatsapp",
 };
 const SEMANTIC_COLOR_MAP = {
     default: "",

package/dist/ui/components/Typography.d.ts

@@ -44,6 +44,8 @@ declare const TYPOGRAPHY: {
         readonly inherit: "";
         readonly accent: "appkit-color--accent";
         readonly inverse: "appkit-color--inverse";
+        /** Second tier on a dark/branded surface. See Typography.style.css. */
+        readonly "inverse-muted": "appkit-color--inverse-muted";
     };
 };
 export type ColorVariant = keyof typeof TYPOGRAPHY.colorVariant;

package/dist/ui/components/Typography.js

@@ -46,6 +46,8 @@ const TYPOGRAPHY = {
         inherit: "",
         accent: "appkit-color--accent",
         inverse: "appkit-color--inverse",
+        /** Second tier on a dark/branded surface. See Typography.style.css. */
+        "inverse-muted": "appkit-color--inverse-muted",
     },
 };
 const DROP_SHADOW_MAP = {

package/dist/ui/components/Typography.style.css

@@ -165,6 +165,25 @@
   color: var(--appkit-color-text-on-primary, #ffffff);
 }
 
+/* Secondary text on a surface that stays dark/branded in EVERY theme.
+ *
+ * WHY: eight live sites hand-rolled a second tier on a branded surface and
+ * none of them worked the same way. Three in WhatsAppCommunitySection were
+ * `className="/80"` / `"/90"` / `"/75"` — codemod residue from a sweep that
+ * stripped `text-white` off `text-white/80` and left the modifier. Tailwind
+ * cannot generate a class named `/80`, so all three were silent no-ops and
+ * the intended hierarchy rendered flat. Five more in HeroCarousel used raw
+ * `opacity-70`/`-80`/`-90`, which fades the whole element, not just its ink.
+ *
+ * Reads --appkit-color-text-on-primary rather than literal white, so a theme
+ * whose on-primary ink is not #fff still gets a correct second tier. Three
+ * different alphas for one idea is the drift that produced this; there is one
+ * tier here on purpose.
+ */
+.appkit-color--inverse-muted {
+  color: color-mix(in srgb, var(--appkit-color-text-on-primary, #ffffff) 78%, transparent);
+}
+
 .dark .appkit-color--primary {
   color: var(--appkit-color-text);
 }

package/dist/ui/components/index.style.css

@@ -40,6 +40,7 @@
 @import "./DescriptionField.style.css";
 @import "./FormGrid.style.css";
 @import "./HorizontalScroller.style.css";
+@import "./CarouselNav.style.css";
 @import "./NavigationLoader.style.css";
 @import "./ImageLightbox.style.css";
 @import "./SideModal.style.css";

package/dist/ui/index.d.ts

@@ -106,7 +106,7 @@ export { StarRating } from "./components/StarRating";
 export type { BreadcrumbProps, BreadcrumbItem } from "./components/Breadcrumb";
 export { Breadcrumb } from "./components/Breadcrumb";
 export { ImageMosaic, MOSAIC_MIN } from "./components/ImageMosaic";
-export type { ImageMosaicProps } from "./components/ImageMosaic";
+export type { ImageMosaicProps, ImageMosaicSize } from "./components/ImageMosaic";
 export { SplitTile } from "./components/SplitTile";
 export type { SplitTileProps, SplitTilePane } from "./components/SplitTile";
 export type { ImageLightboxProps, LightboxImage, } from "./components/ImageLightbox";
@@ -133,6 +133,8 @@ export type { ItemRowProps } from "./components/ItemRow";
 export { ItemRow } from "./components/ItemRow";
 export type { HorizontalScrollerProps, PerViewConfig, } from "./components/HorizontalScroller";
 export { HorizontalScroller } from "./components/HorizontalScroller";
+export { CarouselNav, CAROUSEL_RAIL_MAX } from "./components/CarouselNav";
+export type { CarouselNavProps, CarouselNavTone } from "./components/CarouselNav";
 export type { FormGridProps, FormFieldProps } from "./components/FormGrid";
 export { FormGrid, FormField as FormGridField } from "./components/FormGrid";
 export type { SettingsSectionProps, ToggleRowProps } from "./components/SettingsSection";

package/dist/ui/index.js

@@ -98,6 +98,10 @@ export { SummaryCard } from "./components/SummaryCard.js";
 export { CountdownDisplay } from "./components/CountdownDisplay.js";
 export { ItemRow } from "./components/ItemRow.js";
 export { HorizontalScroller } from "./components/HorizontalScroller.js";
+/* The ONE carousel position/navigation control — replaces the hero's bespoke
+   pill dots, the rail arrows that vanished below 640px, and the testimonial
+   rail's complete absence of an indicator. */
+export { CarouselNav, CAROUSEL_RAIL_MAX } from "./components/CarouselNav.js";
 export { FormGrid, FormField as FormGridField } from "./components/FormGrid.js";
 export { SettingsSection, ToggleRow } from "./components/SettingsSection.js";
 export { DetailPageHero } from "./components/DetailPageHero.js";

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@mohasinac/appkit",
-  "version": "4.53.2",
+  "version": "4.54.0",
   "license": "MIT",
   "publishConfig": {
     "access": "public"
@@ -254,7 +254,8 @@
     "driver.js": "^1.8.0",
     "jsbarcode": "^3.12.3",
     "motion": "^13.1.1",
-    "phonepe-pg-sdk-node": "^2.0.2",
+    "phonepe-pg-sdk-node": ">=2.0.2",
+    "razorpay": "^2.9.8",
     "react-advanced-cropper": "^0.20.1",
     "tailwind-merge": "^3.3.0",
     "zod": "^3.24.0",

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

@@ -1,27 +0,0 @@
-/**
- * Core: async WhatsApp Business Catalog import (`whatsappCatalogImport` job).
- *
- * `POST /api/store/whatsapp-settings/catalog-import` used to do this inline:
- * one Meta fetch capped at `limit=250`, then a sequential per-item loop doing
- * up to 2 `findBySlug` reads plus 1 `create` write EACH — a real 10s-timeout
- * risk on Vercel Hobby (CLAUDE.md Rule #6) well before the cap was reached.
- * It also declared `paging.next` in its response type and never followed it,
- * so a catalog larger than 250 items silently imported only the first page.
- *
- * Running here instead buys the Function's 300s budget, which is what makes
- * following `paging.next` safe rather than making the timeout worse.
- *
- * Two efficiency changes vs. the old route:
- *  - Existing-slug detection is ONE `findByStore` read into a Set, not 2 reads
- *    per item. A seller's WA catalog is populated by pushing their own store's
- *    products, so store-scoped lookup is equivalent to the old global
- *    `findBySlug` here while costing a single query.
- *  - That Set is updated as we create, so duplicate rows within one Meta
- *    response can't produce two products.
- */
-import type { JobContext } from "../runtime/types";
-import type { JobRunResult } from "./jobRunners";
-export interface WhatsAppCatalogImportPayload {
-    storeSlug: string;
-}
-export declare function runWhatsAppCatalogImport(payload: WhatsAppCatalogImportPayload, ctx: JobContext): Promise<JobRunResult>;

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

@@ -1,172 +0,0 @@
-/**
- * Core: async WhatsApp Business Catalog import (`whatsappCatalogImport` job).
- *
- * `POST /api/store/whatsapp-settings/catalog-import` used to do this inline:
- * one Meta fetch capped at `limit=250`, then a sequential per-item loop doing
- * up to 2 `findBySlug` reads plus 1 `create` write EACH — a real 10s-timeout
- * risk on Vercel Hobby (CLAUDE.md Rule #6) well before the cap was reached.
- * It also declared `paging.next` in its response type and never followed it,
- * so a catalog larger than 250 items silently imported only the first page.
- *
- * Running here instead buys the Function's 300s budget, which is what makes
- * following `paging.next` safe rather than making the timeout worse.
- *
- * Two efficiency changes vs. the old route:
- *  - Existing-slug detection is ONE `findByStore` read into a Set, not 2 reads
- *    per item. A seller's WA catalog is populated by pushing their own store's
- *    products, so store-scoped lookup is equivalent to the old global
- *    `findBySlug` here while costing a single query.
- *  - That Set is updated as we create, so duplicate rows within one Meta
- *    response can't produce two products.
- */
-import { normalizeError } from "../../../../errors/normalize.js";
-import { storeRepository, productRepository } from "../../../../repositories/index.js";
-import { decryptPii } from "../../../../security/index.js";
-const META_GRAPH_BASE = "https://graph.facebook.com/v20.0";
-const SLUG_PREFIX = "product-";
-const PAGE_SIZE = 250;
-/**
- * Defensive stop. 40 pages x 250 = 10,000 items, far beyond any realistic
- * seller catalog — this exists so a malformed/looping `paging.next` from Meta
- * can't spin until the Function's 300s ceiling kills the job mid-write.
- */
-const MAX_PAGES = 40;
-/** Meta returns "<amount> <currency>", e.g. "450.00 INR". */
-function parseMetaPrice(raw) {
-    if (!raw)
-        return 0;
-    const digits = raw.replace(/[^0-9.]/g, "");
-    return Math.round((parseFloat(digits) || 0) * 100) / 100;
-}
-/**
- * The LetItRip slug a Meta item claims to correspond to, if any. Items we
- * pushed carry it in `description` (see catalog-sync's field mapping) and/or
- * `retailer_id`; items authored natively in Meta carry neither.
- */
-function claimedSlug(item) {
-    const description = (item.description ?? "").trim();
-    if (description.startsWith(SLUG_PREFIX))
-        return description;
-    const retailerId = (item.retailer_id ?? "").trim();
-    if (retailerId.startsWith(SLUG_PREFIX))
-        return retailerId;
-    return null;
-}
-export async function runWhatsAppCatalogImport(payload, ctx) {
-    const { storeSlug } = payload;
-    const empty = { total: 0, succeeded: 0, skipped: 0, failed: 0 };
-    const store = await storeRepository.findBySlug(storeSlug);
-    if (!store) {
-        return {
-            summary: empty,
-            succeeded: [],
-            skipped: [],
-            failed: [{ id: storeSlug, reason: "Store not found" }],
-        };
-    }
-    const cfg = store.whatsappConfig;
-    const token = cfg?.accessToken ? decryptPii(cfg.accessToken) : null;
-    // Re-checked here even though the route gates on the same conditions — the
-    // job doc outlives the request, and the seller could disconnect in between.
-    if (!cfg?.connected || !cfg.catalogId || !token) {
-        return {
-            summary: empty,
-            succeeded: [],
-            skipped: [],
-            failed: [{ id: storeSlug, reason: "WhatsApp is not connected for this store" }],
-        };
-    }
-    const existing = await productRepository.findByStore(store.storeSlug);
-    const knownSlugs = new Set(existing.map((p) => p.slug).filter((s) => Boolean(s)));
-    const imported = [];
-    const skipped = [];
-    const failed = [];
-    let url = `${META_GRAPH_BASE}/${cfg.catalogId}/products` +
-        `?fields=name,price,currency,image_url,description,retailer_id&limit=${PAGE_SIZE}`;
-    let page = 0;
-    let truncated = false;
-    while (url) {
-        if (page >= MAX_PAGES) {
-            truncated = true;
-            ctx.logger.warn("whatsappCatalogImport: page cap reached — catalog truncated", {
-                storeSlug,
-                maxPages: MAX_PAGES,
-                importedSoFar: imported.length,
-            });
-            break;
-        }
-        page++;
-        const res = await fetch(url, { headers: { Authorization: `Bearer ${token}` } });
-        if (!res.ok) {
-            const body = (await res.json().catch(() => ({})));
-            const reason = body.error?.message ?? res.statusText;
-            ctx.logger.error("whatsappCatalogImport: Meta fetch failed", null, { storeSlug, page, reason });
-            failed.push({ id: `page-${page}`, reason: `Meta fetch failed: ${reason}` });
-            break;
-        }
-        const body = (await res.json());
-        const items = body.data ?? [];
-        for (const item of items) {
-            const slug = claimedSlug(item);
-            if (slug && knownSlugs.has(slug)) {
-                skipped.push(item.id);
-                continue;
-            }
-            const input = {
-                title: item.name ?? `WhatsApp Import ${item.id}`,
-                description: "",
-                slug: "",
-                listingType: "standard",
-                status: "draft",
-                price: parseMetaPrice(item.price),
-                currency: "INR",
-                mainImage: item.image_url ?? "",
-                images: [],
-                stockQuantity: 1,
-                condition: "new",
-                storeId: store.id,
-                storeName: store.storeName,
-                tags: ["whatsapp-import"],
-                categorySlugs: [],
-                featured: false,
-            };
-            try {
-                const created = await productRepository.create(input);
-                // Guard against the same item appearing twice in one Meta response.
-                if (slug)
-                    knownSlugs.add(slug);
-                if (created.slug)
-                    knownSlugs.add(created.slug);
-                imported.push(created.id);
-            }
-            catch (err) {
-                void normalizeError(err);
-                failed.push({
-                    id: item.id,
-                    reason: err instanceof Error ? err.message : "Product create failed",
-                });
-            }
-        }
-        url = body.paging?.next;
-    }
-    ctx.logger.info("whatsappCatalogImport: complete", {
-        storeSlug,
-        pages: page,
-        imported: imported.length,
-        skipped: skipped.length,
-        failed: failed.length,
-        truncated,
-    });
-    return {
-        summary: {
-            total: imported.length + skipped.length + failed.length,
-            succeeded: imported.length,
-            skipped: skipped.length,
-            failed: failed.length,
-        },
-        succeeded: imported,
-        skipped,
-        failed,
-        data: { imported: imported.length, skipped: skipped.length, pages: page, truncated },
-    };
-}

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

@@ -1,35 +0,0 @@
-/**
- * Core: async WhatsApp notification dispatch (`whatsappNotify` job).
- *
- * `sendNotification()` (appkit/src/features/admin/actions/notification-actions.ts)
- * no longer calls the Meta Cloud API synchronously in-request — it enqueues
- * this job instead (CLAUDE.md Rule #6 async job primitive) and returns
- * immediately. This runner does the actual send, with a bounded retry, and
- * writes the outcome back onto `notifications/{notificationId}` so admins
- * have visibility beyond the `jobs/{jobId}` doc itself.
- *
- * Retry note: `sendWhatsAppTemplateMessage`/`sendWhatsAppBusinessMessage`
- * return a plain boolean (not a status code), so this runner cannot cleanly
- * distinguish a transient 5xx from a terminal 4xx (bad token, unknown
- * template) the way a status-code-aware client could. It retries any
- * failure up to MAX_ATTEMPTS with a short backoff — an acceptable
- * simplification since this runs off the critical path, well inside the
- * Firebase Function's 300s budget, and a terminal error just burns two
- * extra fast failures before giving up.
- */
-import type { JobContext } from "../runtime/types";
-import type { JobRunResult } from "./jobRunners";
-export interface WhatsAppNotifyPayload {
-    toPhone: string;
-    title: string;
-    message: string;
-    type: string;
-    /** Approved Meta template name for this notification type, if configured. */
-    templateName?: string;
-    /** BCP-47 language code the template was approved in. Defaults to "en". */
-    templateLanguage?: string;
-    notificationId: string;
-    phoneNumberId: string;
-    accessToken: string;
-}
-export declare function runWhatsAppNotify(payload: WhatsAppNotifyPayload, ctx: JobContext): Promise<JobRunResult>;