@mohasinac/appkit 4.53.1 → 4.54.0-next.0

package/dist/_internal/server/features/products/listing-tab-counts.js

@@ -11,9 +11,10 @@
  *       the tab bar renders, so a tenth listing type is counted automatically.
  *
  * EXPORTS:
- *   ListingTabScope   — the surface's scope (category / brand / store)
- *   ListingTabCounts  — tabSlug -> count, `undefined` meaning "query failed"
- *   listingTabCounts  — resolve every tab's count in one parallel batch
+ *   ListingTabScope       — the surface's scope (category / brand / store)
+ *   ListingTabCounts      — tabSlug -> count, `undefined` meaning "unknown"
+ *   ListingTabCountResult — the AVAILABLE and TOTAL maps, see below
+ *   listingTabCounts      — resolve every tab's counts in one parallel batch
  *
  * @tag domain:products,categories,stores
  * @tag layer:server
@@ -25,6 +26,11 @@
 import { categoriesRepository, productRepository } from "../../../../repositories/index.js";
 import { serverLogger } from "../../../../monitoring/index.js";
 import { normalizeError } from "../../../../errors/normalize.js";
+import { sieveAnd, sieveFilter, SIEVE_OP, sortBy } from "../../../../utils/sieve-builder.js";
+import { PRODUCT_FIELDS } from "../../../../constants/field-names.js";
+import { isListingRowAvailable, pluginFor, } from "../../../shared/listing-types/_registry.js";
+import { normalizeListingType } from "../../../../features/products/utils/listing-type.js";
+import { clauseToSieve, PUBLIC_PRODUCT_MAX_PAGE_SIZE } from "./list-public.js";
 const DEFAULT_STATUS = "published";
 /** Bundles a category owns, resolved by the same rule the bundles tab renders. */
 async function countBundles(scope) {
@@ -65,6 +71,154 @@ function bundleMatchesScope(bundle, scope) {
     }
     return true;
 }
+/**
+ * How many rows in scope are NOT available, per listing type.
+ *
+ * ── 🛑 WHY THIS IS NOT AN AGGREGATE COUNT ─────────────────────────────────
+ *
+ * Two independent reasons, either of which alone is disqualifying.
+ *
+ * 1. Unavailability is an OR across DIFFERENT fields (`availableQuantity == 0`
+ *    OR `isSold == true` OR `prizeRevealStatus == closed` …). Firestore cannot
+ *    express that in one query, and counting each clause separately and adding
+ *    them double-counts every row matching two of them.
+ *
+ * 2. A clause selects a SUPERSET, deliberately. `madeToOrder` is pointedly NOT
+ *    a clause (see the note in `availability.ts`), so a print-on-demand sticker
+ *    sitting at `availableQuantity: 0` matches `availableQuantity == 0` and is
+ *    nevertheless AVAILABLE. Only `isListingRowAvailable` knows that, and it is
+ *    a per-row predicate. Measured on the category that prompted this work,
+ *    a clause-count would have badged "Art & Stickers 2" over three available
+ *    rows — trading one wrong number for another.
+ *
+ * So this is Path C of `listPublicProducts` reused in miniature: one bounded
+ * query per DISTINCT clause, in parallel, merged and deduped by id, then every
+ * surviving row confirmed with the real predicate. Nine listing types collapse
+ * to five clauses, so the whole tab bar costs ~5 × 50 documents in one parallel
+ * round — the same fan-out and the same budget that scope already spends.
+ *
+ * 🛑 The queries are NOT narrowed to the tab's listing types. Firestore permits
+ * one array operator per query and the category scope already spends it on
+ * `categorySlugs array-contains-any`, so adding `listingType in (…)` risks an
+ * INVALID_ARGUMENT for no gain: unavailable rows are sparse, and tallying each
+ * row by its own `listingType` afterwards answers every tab from one pass.
+ */
+async function unavailableByType(scope, types, now) {
+    const byType = new Map();
+    const unknown = new Set();
+    /*
+     * One entry per DISTINCT clause, remembering which types depend on it, so a
+     * clause that cannot run takes down only those types' badges.
+     */
+    const distinct = new Map();
+    for (const type of types) {
+        for (const clause of pluginFor(type).unavailableClauses) {
+            const key = clause.field + "|" + clause.op + "|" + String(clause.value);
+            const entry = distinct.get(key) ?? { clause, types: new Set() };
+            entry.types.add(type);
+            distinct.set(key, entry);
+        }
+    }
+    if (distinct.size === 0)
+        return { byType, unknown };
+    const status = scope.status ?? DEFAULT_STATUS;
+    const results = await Promise.all([...distinct.values()].map(async (entry) => {
+        const { clause } = entry;
+        /*
+         * 🛑 NO SORT on an equality clause — load-bearing, not an omission.
+         *
+         * A tally does not care about order, and adding `orderBy createdAt`
+         * turns a query Firestore can merge-join from single-field indexes into
+         * one demanding a composite index PER CLAUSE PER SCOPE: fifteen new
+         * indexes on a collection already carrying 223, every one of them write
+         * amplification on every product write. Measured against the live
+         * project: all four equality clauses run index-free without the sort and
+         * return FAILED_PRECONDITION with it.
+         *
+         * An inequality is the exception Firestore forces — its first `orderBy`
+         * must be its own field (Root Cause #59) — so that one clause does need
+         * an index, which is exactly why `unknown` is tracked per type.
+         *
+         * 🛑 THE AUCTION INDEXES ARE NOT DECLARED, deliberately. Until they are,
+         * the auction clause returns FAILED_PRECONDITION, `unknown` gains
+         * `auction`, and that ONE badge falls back to its total — every other
+         * type stays exact. Adding them to
+         * `appkit/firebase/base/firestore.indexes.json` is only half the change:
+         * an undeployed index file fails `audit-firebase-rules-deployed`, so the
+         * three entries below and `npm run firebase -- deploy --only
+         * firestore:indexes` belong in the same session.
+         *
+         *   products: status ASC, categorySlugs CONTAINS, auctionEndDate DESC
+         *   products: brand  ASC, status ASC,             auctionEndDate DESC
+         *   products: storeId ASC, status ASC,            auctionEndDate DESC
+         *
+         * One per scope the tab bars count in, because `buildScopedQuery` leads
+         * with a different equality for each.
+         */
+        const sorts = clause.op === "lt" && clause.sortField
+            ? sortBy(clause.sortField, "DESC")
+            : undefined;
+        try {
+            const result = await productRepository.list({
+                filters: sieveAnd(sieveFilter(PRODUCT_FIELDS.STATUS, SIEVE_OP.EQ, status), clauseToSieve(clause, now)),
+                ...(sorts ? { sorts } : {}),
+                page: 1,
+                pageSize: PUBLIC_PRODUCT_MAX_PAGE_SIZE,
+            }, {
+                storeId: scope.storeId,
+                categoriesIn: scope.categoriesIn,
+                brandName: scope.brandName,
+            });
+            return { entry, result };
+        }
+        catch (error) {
+            const e = normalizeError(error);
+            // ERROR, not warn: a clause that cannot run is almost always a missing
+            // composite index — a permanent, silent skew of the badges that depend
+            // on it rather than a transient blip. The fields are named so the log
+            // says which index to create.
+            serverLogger.error("listingTabCounts: unavailable clause failed; those badges fall back to totals", {
+                field: clause.field,
+                op: clause.op,
+                types: [...entry.types],
+                error: e.message,
+            });
+            return { entry, result: null };
+        }
+    }));
+    const merged = new Map();
+    for (const { entry, result } of results) {
+        if (!result) {
+            for (const type of entry.types)
+                unknown.add(type);
+            continue;
+        }
+        const rows = result.items;
+        // A saturated window means there are more unavailable rows than were seen,
+        // so the tally is a floor for every type this clause serves.
+        if (rows.length >= PUBLIC_PRODUCT_MAX_PAGE_SIZE) {
+            for (const type of entry.types)
+                unknown.add(type);
+        }
+        for (const row of rows) {
+            const id = typeof row.id === "string" ? row.id : JSON.stringify(row.id);
+            if (!merged.has(id))
+                merged.set(id, row);
+        }
+    }
+    for (const row of merged.values()) {
+        // The clause matched a superset; this is the real answer.
+        if (isListingRowAvailable(row, now))
+            continue;
+        const type = normalizeListingType(row);
+        byType.set(type, (byType.get(type) ?? 0) + 1);
+    }
+    return { byType, unknown };
+}
+/** The listing types one tab spans — `"art|stickers"` is a pipe OR-group. */
+function typesOf(tab) {
+    return String(tab.listingType).split("|").filter(Boolean);
+}
 /**
  * Count every tab in `tabs` within `scope`, in one parallel batch.
  *
@@ -75,10 +229,12 @@ function bundleMatchesScope(bundle, scope) {
  * `stores` is not counted here: only the category page has that tab and it
  * already resolves its store list eagerly to render the tab body.
  */
-export async function listingTabCounts(tabs, scope) {
+export async function listingTabCounts(tabs, scope, opts) {
+    const now = opts?.now ?? new Date();
     const listingTabs = tabs.filter((tab) => Boolean(tab.listingType));
     const wantsBundles = tabs.some((tab) => tab.collection === "bundles");
-    const [typeCounts, bundleCount] = await Promise.all([
+    const allTypes = [...new Set(listingTabs.flatMap(typesOf))];
+    const [typeCounts, bundleCount, unavailable] = await Promise.all([
         productRepository.countByListingTypes(listingTabs.map((tab) => String(tab.listingType)), {
             status: scope.status ?? DEFAULT_STATUS,
             storeId: scope.storeId,
@@ -86,12 +242,30 @@ export async function listingTabCounts(tabs, scope) {
             brandName: scope.brandName,
         }),
         wantsBundles ? countBundles(scope) : Promise.resolve(undefined),
+        unavailableByType(scope, allTypes, now),
     ]);
-    const counts = {};
+    const total = {};
+    const available = {};
     for (const tab of listingTabs) {
-        counts[tab.id] = typeCounts[String(tab.listingType)];
+        const tabTypes = typesOf(tab);
+        const totalForTab = typeCounts[String(tab.listingType)];
+        total[tab.id] = totalForTab;
+        if (totalForTab === undefined ||
+            tabTypes.some((t) => unavailable.unknown.has(t))) {
+            // Falling back to the total reproduces the pre-split badge rather than
+            // inventing a number — and it keeps the hint silent, because the hint
+            // only speaks when both figures are known.
+            available[tab.id] = totalForTab;
+            continue;
+        }
+        const gone = tabTypes.reduce((sum, type) => sum + (unavailable.byType.get(type) ?? 0), 0);
+        available[tab.id] = Math.max(0, totalForTab - gone);
+    }
+    if (wantsBundles) {
+        // A bundle has no availability scope of its own — the bundles tab renders
+        // active bundle ROWS, not products, so the two numbers are one number.
+        total.bundles = bundleCount;
+        available.bundles = bundleCount;
     }
-    if (wantsBundles)
-        counts.bundles = bundleCount;
-    return counts;
+    return { available, total };
 }

package/dist/_internal/server/features/search/index-build/sources.js

@@ -195,7 +195,26 @@ export const PUBLIC_INDEX_SOURCES = [
     {
         typeKey: "part",
         collection: "partGlossary",
-        select: ["name", "code", "classification", "slot"],
+        /*
+         * 🛑 `aliases` IS IN THE SELECT BECAUSE AN ABBREVIATION IS HOW PEOPLE
+         * SEARCH FOR A PART.
+         *
+         * The wiki states a part's short form outright, and it reaches 1,072 of
+         * 2,490 rows: `EWD` is Eternal Wide Defense, `BWD` is Big Wide Defense,
+         * `ES` is Eternal Spike. Those are the names printed on the part and the
+         * names the community uses — but they lived only in Firestore, because
+         * this select carried name/code/classification/slot and nothing else.
+         *
+         * So the data was there, the page was there, and searching `EWD` found
+         * NOTHING. A gap between holding a fact and being able to find it is
+         * invisible from either end.
+         *
+         * 🛑 It must be `aliases`, not `aka`. The generator UNIONS the wiki's
+         * `aka` into the pre-existing `aliases` array rather than replacing it,
+         * so `aliases` is the superset — selecting `aka` would silently drop
+         * every alias the corpus contributed.
+         */
+        select: ["name", "code", "classification", "slot", "aliases"],
         slugOf: (id) => (id.includes("--") ? id.replace("--", "/") : null),
         toRecord: (id, d) => {
             const name = str(d.name);
@@ -214,11 +233,33 @@ export const PUBLIC_INDEX_SOURCES = [
                 return null;
             const code = str(d.code);
             const classification = str(d.classification);
+            /*
+             * The abbreviations, appended to `detail` because that is the only
+             * other field the record carries and the matcher reads both.
+             *
+             * 🛑 Bounded to four and de-duplicated against the name and code. A
+             * part can carry a dozen aliases, and the artifact is a public file
+             * fetched by every visitor — the whole point of it is that it stays
+             * small enough to ship whole. Four covers the abbreviation plus the
+             * other vendor's name, which is what anyone actually types.
+             */
+            const aliases = Array.isArray(d.aliases) ? d.aliases.map(str).filter(Boolean) : [];
+            const seen = new Set([name.toLowerCase(), (code ?? "").toLowerCase()]);
+            const extra = [];
+            for (const a of aliases) {
+                const k = String(a).toLowerCase();
+                if (seen.has(k))
+                    continue;
+                seen.add(k);
+                extra.push(String(a));
+                if (extra.length === 4)
+                    break;
+            }
             return {
                 title: name,
                 // The classification IS the disambiguation — it is why a user
                 // searching "105" can tell three results apart.
-                detail: [classification, code].filter(Boolean).join(" · "),
+                detail: [classification, code, ...extra].filter(Boolean).join(" · "),
             };
         },
     },

package/dist/_internal/server/features/stores/tabs.d.ts

@@ -1,5 +1,5 @@
 import { isListingTypeEnabled } from "../../../shared/listing-types/feature-flags";
-import { type ListingTabCounts } from "../products/listing-tab-counts";
+import { type ListingTabCountResult } from "../products/listing-tab-counts";
 type SiteSettingsSnapshot = Parameters<typeof isListingTypeEnabled>[1];
 export interface StoreTabLink {
     value: string;
@@ -11,7 +11,12 @@ export interface ResolvedStoreTabs {
     dropdownTabs: StoreTabLink[];
     /** Coupons (if any), Reviews (if any), About — always non-empty. */
     tabs: StoreTabLink[];
-    listingCounts: ListingTabCounts;
+    /**
+     * Both numbers, because they answer different questions: `available` is what
+     * each tab badges, `total` is what decides whether the tab exists at all.
+     * See `ListingTabCountResult`.
+     */
+    listingCounts: ListingTabCountResult;
     couponsCount: number;
     reviewsCount: number;
 }

package/dist/_internal/server/features/stores/tabs.js

@@ -73,7 +73,7 @@ export async function resolveStoreTabs(storeSlug, storeId, settings) {
                 .then((r) => r.total)
                 .catch(() => 0),
         ])
-        : [{}, 0, 0];
+        : [{ available: {}, total: {} }, 0, 0];
     const visibleStoreTabs = STORE_PAGE_TABS.filter((tab) => {
         if (tab.id === "bundles") {
             if (!isCategoryTypeEnabled("bundle", settings))
@@ -92,12 +92,14 @@ export async function resolveStoreTabs(storeSlug, storeId, settings) {
         // that leads to an empty page. `undefined` means the count query FAILED,
         // not zero, so the tab stays visible rather than hiding real stock
         // behind a swallowed error (Root Cause #59).
-        const count = listingCounts[tab.id];
+        // TOTAL, not the badge: a tab whose rows have all ended still has an
+        // archive behind the Ended/All scopes, and hiding it would strand that.
+        const count = listingCounts.total[tab.id];
         return count === undefined || count > 0;
     });
     const dropdownTabs = visibleStoreTabs.map((tab) => ({
         value: tab.id,
-        label: tabLabel(tab.label, listingCounts[tab.id]),
+        label: tabLabel(tab.label, listingCounts.available[tab.id]),
         href: STORE_LISTING_HREF[tab.id](storeSlug),
     }));
     const tabs = [

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

@@ -11,9 +11,7 @@
 import { runWeeklyPayoutEligibility } from "./weeklyPayoutEligibility.js";
 import { runHardBanCascade } from "./hardBanCascade.js";
 import { runResetOtpVerification } from "./resetOtpVerification.js";
-import { runWhatsAppNotify } from "./whatsappNotify.js";
 import { runNewsletterExport } from "./newsletterExport.js";
-import { runWhatsAppCatalogImport } from "./whatsappCatalogImport.js";
 import { runStoreNameBackfill } from "./storeNameBackfill.js";
 import { runCategoryTaxonomyBackfill } from "./categoryTaxonomyBackfill.js";
 async function runPayoutsWeeklyJob(_payload, ctx) {
@@ -42,15 +40,9 @@ async function runHardBanCascadeJob(payload, ctx) {
 async function runResetOtpVerificationJob(_payload, ctx) {
     return runResetOtpVerification(ctx);
 }
-async function runWhatsAppNotifyJob(payload, ctx) {
-    return runWhatsAppNotify(payload, ctx);
-}
 async function runNewsletterExportJob(_payload, ctx) {
     return runNewsletterExport(ctx);
 }
-async function runWhatsAppCatalogImportJob(payload, ctx) {
-    return runWhatsAppCatalogImport({ storeSlug: String(payload.storeSlug ?? "") }, ctx);
-}
 async function runStoreNameBackfillJob(payload, ctx) {
     return runStoreNameBackfill({ storeId: String(payload.storeId ?? "") }, ctx);
 }
@@ -68,9 +60,7 @@ export const JOB_RUNNERS = {
     payoutsWeekly: runPayoutsWeeklyJob,
     hardBanCascade: runHardBanCascadeJob,
     resetOtpVerification: runResetOtpVerificationJob,
-    whatsappNotify: runWhatsAppNotifyJob,
     newsletterExport: runNewsletterExportJob,
-    whatsappCatalogImport: runWhatsAppCatalogImportJob,
     storeNameBackfill: runStoreNameBackfillJob,
     categoryTaxonomyBackfill: runCategoryTaxonomyBackfillJob,
 };

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/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
@@ -1042,7 +1101,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",