@mohasinac/appkit 4.71.0 → 4.71.2

package/dist/providers/payment-phonepe/index.d.ts

@@ -36,7 +36,7 @@
  * });
  * ```
  */
-import type { JsonValue } from "@mohasinac/appkit";
+import type { JsonValue } from "../../schemas/types";
 import { IPaymentProvider } from "../../contracts";
 import type { CheckoutIntentMetadata, PaymentOrder, PaymentCapture, Refund, Dispute, GatewayPaymentRecord } from "../../contracts";
 /**

package/dist/providers/payment-phonepe/index.js

@@ -47,7 +47,19 @@ function packMetaInfo(intent) {
         .udf2(intent.addressId ?? "")
         .udf3(intent.outOfStockPolicy ?? "")
         .udf4((intent.notes ?? "").slice(0, 256))
-        .udf5("")
+        /*
+         * Item 1.39 — the buyer-policy consent record id.
+         *
+         * 🛑 PhonePe's metaInfo is FIVE named slots, not an open map, so unlike
+         * Razorpay's generic `notes` flattening a new intent field is invisible
+         * here until it is named. udf5 was the one spare slot and this is what it
+         * is now for. The webhook path has no session, so without this the
+         * consent taken before the capture could not be found after it — and the
+         * placement would have to either refuse a paid order or write one with no
+         * consent record. Both are unacceptable; a 36-byte id in a spare slot is
+         * neither.
+         */
+        .udf5(intent.policyConsentId ?? "")
         .build();
 }
 function unpackMetaInfo(meta) {
@@ -58,6 +70,7 @@ function unpackMetaInfo(meta) {
         addressId: meta.udf2 || undefined,
         outOfStockPolicy: meta.udf3 || undefined,
         notes: meta.udf4 || undefined,
+        policyConsentId: meta.udf5 || undefined,
     };
 }
 /** merchantOrderId / merchantRefundId — ≤63 chars, `_`/`-` only (PhonePe constraint). */

package/dist/providers/payment-razorpay/index.d.ts

@@ -50,7 +50,7 @@
  * });
  * ```
  */
-import type { JsonValue } from "@mohasinac/appkit";
+import type { JsonValue } from "../../schemas/types";
 import { IPaymentProvider } from "../../contracts";
 import type { PaymentOrder, PaymentCapture, Refund, Dispute, GatewayPaymentRecord } from "../../contracts";
 export { verifyPaymentSignature, verifyWebhookSignature, type RazorpayPaymentResult, } from "./signature";

package/dist/providers/shipping-shiprocket/index.d.ts

@@ -54,12 +54,18 @@
  *
  * ── What is deliberately NOT here ────────────────────────────────────────
  *
- * Inbound webhooks. Shiprocket pushes status updates to a URL configured in
+ * The webhook ROUTE. Shiprocket pushes status updates to a URL configured in
  * its dashboard and authenticates them with an `x-api-key` header whose value
- * you set there — a THIRD secret, and an inbound route rather than a provider
- * method. `trackShipment` below polls instead, which is correct for a provider
- * contract and wasteful as a status mechanism; the webhook is the better
- * answer and belongs in its own route with its own verification.
+ * you set there — an inbound route rather than a provider method, so the route
+ * lives at `/api/shipping/webhook` (item 1.38) and not on this class.
+ * `trackShipment` below polls instead, which is correct for a provider contract
+ * and wasteful as a status mechanism.
+ *
+ * What DOES live here is the credential check itself —
+ * `verifyShiprocketWebhookToken` below — for the same reason
+ * `packCashfreeWebhookSignature` lives in the Cashfree adapter: the encoding of
+ * a provider's authentication belongs to that provider, so no route invents its
+ * own comparison.
  *
  * @tag domain:shipping
  * @tag layer:providers
@@ -67,6 +73,35 @@
  */
 import { IShippingProvider } from "../../contracts";
 import type { CreateShipmentInput, Shipment, TrackingInfo, ServiceabilityResult, WalletBalance } from "../../contracts";
+/**
+ * The header Shiprocket echoes its configured webhook token back on.
+ *
+ * Named here rather than inline at the route, so the route cannot drift from
+ * the provider's actual contract — the mistake that makes a webhook endpoint
+ * 401 everything in production while reading as correct.
+ */
+export declare const SHIPROCKET_WEBHOOK_TOKEN_HEADER = "x-api-key";
+/**
+ * Authenticate an inbound Shiprocket delivery.
+ *
+ * 🛑 BE HONEST ABOUT WHAT THIS IS. Shiprocket offers a SHARED SECRET echoed in
+ * a header, not an HMAC over the body — you choose the value in its dashboard
+ * and it sends that same value on every delivery. So unlike Razorpay or
+ * Cashfree, this proves the CALLER knows the secret; it does **not** prove the
+ * body was not altered in transit, and no amount of care here can make it do
+ * so. That is the strongest check the provider offers. It is written down
+ * rather than glossed over because the difference matters for what the route
+ * is allowed to do with the payload: authenticated-but-unsigned data is good
+ * enough to RECORD, which is what the route does with it.
+ *
+ * 🛑 FAILS CLOSED on every path, and `timingSafeEqual` rather than `===`. A
+ * plain comparison on a secret returns after the first differing byte, which
+ * leaks the secret one character at a time to anyone who can measure the
+ * response. The length guard is there because `timingSafeEqual` THROWS on
+ * differing lengths — and the throw would itself be a side channel, besides
+ * turning a rejection into a 500 (the one status a sender retries).
+ */
+export declare function verifyShiprocketWebhookToken(received: string | null | undefined, expected: string | undefined): boolean;
 export interface ShiprocketConfig {
     /** The API user's email. See the header on why this is not a "login id". */
     email: string;

package/dist/providers/shipping-shiprocket/index.js

@@ -54,23 +54,67 @@
  *
  * ── What is deliberately NOT here ────────────────────────────────────────
  *
- * Inbound webhooks. Shiprocket pushes status updates to a URL configured in
+ * The webhook ROUTE. Shiprocket pushes status updates to a URL configured in
  * its dashboard and authenticates them with an `x-api-key` header whose value
- * you set there — a THIRD secret, and an inbound route rather than a provider
- * method. `trackShipment` below polls instead, which is correct for a provider
- * contract and wasteful as a status mechanism; the webhook is the better
- * answer and belongs in its own route with its own verification.
+ * you set there — an inbound route rather than a provider method, so the route
+ * lives at `/api/shipping/webhook` (item 1.38) and not on this class.
+ * `trackShipment` below polls instead, which is correct for a provider contract
+ * and wasteful as a status mechanism.
+ *
+ * What DOES live here is the credential check itself —
+ * `verifyShiprocketWebhookToken` below — for the same reason
+ * `packCashfreeWebhookSignature` lives in the Cashfree adapter: the encoding of
+ * a provider's authentication belongs to that provider, so no route invents its
+ * own comparison.
  *
  * @tag domain:shipping
  * @tag layer:providers
  * @tag access:server-only
  */
+import { timingSafeEqual } from "node:crypto";
 import { z } from "zod";
 import { IShippingProvider } from "../../contracts/index.js";
 import { ApiError } from "../../errors/index.js";
 import { normalizeError } from "../../errors/normalize.js";
 import { serverLogger } from "../../monitoring/server-logger.js";
 const API_BASE = "https://apiv2.shiprocket.in/v1/external";
+/**
+ * The header Shiprocket echoes its configured webhook token back on.
+ *
+ * Named here rather than inline at the route, so the route cannot drift from
+ * the provider's actual contract — the mistake that makes a webhook endpoint
+ * 401 everything in production while reading as correct.
+ */
+export const SHIPROCKET_WEBHOOK_TOKEN_HEADER = "x-api-key";
+/**
+ * Authenticate an inbound Shiprocket delivery.
+ *
+ * 🛑 BE HONEST ABOUT WHAT THIS IS. Shiprocket offers a SHARED SECRET echoed in
+ * a header, not an HMAC over the body — you choose the value in its dashboard
+ * and it sends that same value on every delivery. So unlike Razorpay or
+ * Cashfree, this proves the CALLER knows the secret; it does **not** prove the
+ * body was not altered in transit, and no amount of care here can make it do
+ * so. That is the strongest check the provider offers. It is written down
+ * rather than glossed over because the difference matters for what the route
+ * is allowed to do with the payload: authenticated-but-unsigned data is good
+ * enough to RECORD, which is what the route does with it.
+ *
+ * 🛑 FAILS CLOSED on every path, and `timingSafeEqual` rather than `===`. A
+ * plain comparison on a secret returns after the first differing byte, which
+ * leaks the secret one character at a time to anyone who can measure the
+ * response. The length guard is there because `timingSafeEqual` THROWS on
+ * differing lengths — and the throw would itself be a side channel, besides
+ * turning a rejection into a 500 (the one status a sender retries).
+ */
+export function verifyShiprocketWebhookToken(received, expected) {
+    if (!expected || !received)
+        return false;
+    const a = Buffer.from(received, "utf8");
+    const b = Buffer.from(expected, "utf8");
+    if (a.length !== b.length)
+        return false;
+    return timingSafeEqual(a, b);
+}
 // ── Response contracts ──────────────────────────────────────────────────────
 //
 // Every one of these is a CLAIM about a payload nobody here has seen. Parsing

package/dist/providers.d.ts

@@ -22,6 +22,9 @@ export type { RazorpayConfig } from "./providers/payment-razorpay/index";
 export { verifyPaymentSignature as verifyRazorpayPaymentSignature, verifyWebhookSignature as verifyRazorpayWebhookSignature, type RazorpayPaymentResult, } from "./providers/payment-razorpay/signature";
 export { PhonePeProvider } from "./providers/payment-phonepe/index";
 export type { PhonePeConfig } from "./providers/payment-phonepe/index";
+export { CashfreeProvider } from "./providers/payment-cashfree/index";
+export type { CashfreeConfig } from "./providers/payment-cashfree/index";
+export { packCashfreeWebhookSignature, verifyCashfreeWebhookSignature, CASHFREE_WEBHOOK_SIGNATURE_HEADER, CASHFREE_WEBHOOK_TIMESTAMP_HEADER, CASHFREE_SESSION_METADATA_KEY, } from "./providers/payment-cashfree/index";
 export { rupeesToPaise, paiseToRupees } from "./core/money";
 export { ManualPaymentProvider } from "./providers/payment-manual/index";
 export { ManualShippingProvider } from "./providers/shipping-manual/index";

package/dist/providers.js

@@ -25,6 +25,11 @@ export { RazorpayProvider } from "./providers/payment-razorpay/index.js";
 export { verifyPaymentSignature as verifyRazorpayPaymentSignature, verifyWebhookSignature as verifyRazorpayWebhookSignature, } from "./providers/payment-razorpay/signature.js";
 // Payment (PhonePe) — disabled by default; siteSettings.payment.phonepeEnabled turns it on
 export { PhonePeProvider } from "./providers/payment-phonepe/index.js";
+// Payment (Cashfree) — disabled by default; siteSettings.payment.cashfreeEnabled turns it on.
+// Bare `fetch`, no SDK, no npm dependency. `order_amount` is decimal rupees, so the
+// adapter converts at its own boundary and keeps the contract in the smallest unit.
+export { CashfreeProvider } from "./providers/payment-cashfree/index.js";
+export { packCashfreeWebhookSignature, verifyCashfreeWebhookSignature, CASHFREE_WEBHOOK_SIGNATURE_HEADER, CASHFREE_WEBHOOK_TIMESTAMP_HEADER, CASHFREE_SESSION_METADATA_KEY, } from "./providers/payment-cashfree/index.js";
 export { rupeesToPaise, paiseToRupees } from "./core/money.js";
 // Payment (manual) — the default provider
 export { ManualPaymentProvider } from "./providers/payment-manual/index.js";

package/dist/react/contexts/SessionContext.d.ts

@@ -26,7 +26,23 @@ export interface SessionUser {
      * before slugs existed have none, and `/profile/{uid}` still resolves.
      */
     slug?: string;
+    /**
+     * Legacy scalar — the HIGHEST-RANKED role this user holds, derived by
+     * `UserRepository.mapDoc`.
+     *
+     * 🛑 Do not gate on it. `roles` is the authority; a scalar cannot answer
+     * "is this seller also an employee" and answering it wrong is silent.
+     */
     role: string;
+    /**
+     * THE role authority — every role this account holds (up to
+     * `getMaxRolesPerUser()`, 3 today). Read it through `rolesOf(user)` so the
+     * `moderator` → `employee` fold applies and the legacy scalar is the
+     * fallback for a session hydrated before this field existed.
+     */
+    roles?: string[];
+    /** 🛑 DISPLAY ONLY — a badge or a default tab. Never an authorization input. */
+    primaryRole?: string;
     disabled?: boolean;
     createdAt?: Date;
     updatedAt?: Date;
@@ -42,7 +58,7 @@ export interface SessionUser {
     publicProfile?: FirestoreDocument;
     /**
      * Buyer activity counts, DERIVED by `/api/user/profile` — orders placed,
-     * auctions won, reviews written. Each is optional and `undefined` means the
+     * collector drops won, reviews written. Each is optional and `undefined` means the
      * count could not be taken, which is NOT the same as zero: render nothing.
      *
      * 🛑 Not the `users/{uid}.stats` document field, which has no writer at all
@@ -54,7 +70,7 @@ export interface SessionUser {
      */
     stats?: {
         totalOrders?: number;
-        auctionsWon?: number;
+        collectorDropsWon?: number;
         reviewsCount?: number;
     };
     metadata?: FirestoreDocument;

package/dist/react/contexts/SessionContext.js

@@ -67,7 +67,15 @@ function buildSessionUser(authUser, serverData) {
         displayName: serverData.displayName || authUser.displayName,
         photoURL: serverData.photoURL || authUser.photoURL,
         phoneNumber: serverData.phoneNumber || authUser.phoneNumber,
+        /*
+         * The role SET carried through client hydration (1.43). Forwarding only
+         * `role` here meant every client-side gate fell back to the scalar even
+         * when the server had sent the array — the dual-read reached the API
+         * response and was then dropped one layer short of the consumer.
+         */
         role: serverData.role || "user",
+        roles: serverData.roles,
+        primaryRole: serverData.primaryRole,
         disabled: serverData.disabled,
         createdAt: serverData.createdAt
             ? new Date(serverData.createdAt)
@@ -144,6 +152,8 @@ export function SessionProvider({ children, initialUser, endpoints: endpointOver
                 photoURL: data.photoURL || null,
                 phoneNumber: data.phoneNumber || null,
                 role: data.role || "user",
+                roles: data.roles,
+                primaryRole: data.primaryRole,
                 disabled: data.disabled,
                 createdAt: data.createdAt ? new Date(data.createdAt) : undefined,
                 updatedAt: data.updatedAt ? new Date(data.updatedAt) : undefined,
@@ -210,7 +220,19 @@ export function SessionProvider({ children, initialUser, endpoints: endpointOver
             const fresh = await fetchUserProfileFromServer();
             if (!fresh || fresh.uid !== user.uid)
                 return;
-            const rbacFieldsChanged = fresh.role !== user.role ||
+            /*
+             * 🛑 The role SET is compared, not just the scalar. An admin ADDING a
+             * role to someone (the owner's actual requirement — upgrading is adding,
+             * not replacing) leaves the highest-ranked scalar unchanged in most
+             * cases: granting `seller` to an `admin` does not move `role` at all. So
+             * the scalar comparison alone saw "nothing changed" and the open tab
+             * never picked up the new access — the same class of bug as the
+             * canTestAdmin one this block was written for.
+             */
+            const rolesChanged = (fresh.roles ?? []).length !== (user.roles ?? []).length ||
+                (fresh.roles ?? []).some((r) => !(user.roles ?? []).includes(r));
+            const rbacFieldsChanged = rolesChanged ||
+                fresh.role !== user.role ||
                 fresh.isTester !== user.isTester ||
                 fresh.canTestAdmin !== user.canTestAdmin ||
                 fresh.disabled !== user.disabled ||

package/dist/react/hooks/useBrowsePageFlags.d.ts

@@ -1,4 +1,4 @@
-import { type BrowsePageKey } from "../../_internal/shared/listing-types/feature-flags";
+import { type BrowsePageKey, type FlagValue } from "../../_internal/shared/listing-types/feature-flags";
 /**
  * Which public browse sections are open, as configured in
  * `siteSettings.listings.browsePages`.
@@ -13,7 +13,7 @@ import { type BrowsePageKey } from "../../_internal/shared/listing-types/feature
  * blank the navbar on every cold load until the settings request resolved —
  * visible flicker on every page of the site rather than one empty browse tab.
  */
-export type BrowsePageFlagsShape = Partial<Record<BrowsePageKey, boolean>>;
+export type BrowsePageFlagsShape = Partial<Record<BrowsePageKey, FlagValue>>;
 export type BrowsePageFlags = Record<BrowsePageKey, boolean> & {
     /** True when the section is open (or the setting has not loaded yet). */
     isEnabled: (page: BrowsePageKey) => boolean;

package/dist/react/hooks/useBrowsePageFlags.js

@@ -1,12 +1,18 @@
 "use client";
 import { useSiteSettings } from "../../core/hooks/useSiteSettings.js";
-import { ALL_BROWSE_PAGES, browsePageForPath, } from "../../_internal/shared/listing-types/feature-flags.js";
+import { ALL_BROWSE_PAGES, browsePageForPath, isBrowsePageListed, } from "../../_internal/shared/listing-types/feature-flags.js";
 export function useBrowsePageFlags() {
     const { data } = useSiteSettings();
-    const bp = data?.listings?.browsePages;
-    // Closed only when EXPLICITLY false — a missing flag, or settings that have
-    // not loaded, means open.
-    const flags = Object.fromEntries(ALL_BROWSE_PAGES.map((page) => [page, bp?.[page] !== false]));
+    const settings = { listings: { browsePages: data?.listings?.browsePages } };
+    /*
+     * 🛑 `"unlisted"` also withdraws the nav link, not just `false` — the
+     * section's own page keeps serving at 200 either way (that's the 404 gate
+     * in `closedSurfacePrefixes`, unaffected by this). `isBrowsePageListed`
+     * already encodes "missing or settings-not-loaded-yet means open", so the
+     * permissive-default behaviour this hook's docstring describes is
+     * unchanged.
+     */
+    const flags = Object.fromEntries(ALL_BROWSE_PAGES.map((page) => [page, isBrowsePageListed(page, settings)]));
     return {
         ...flags,
         isEnabled: (page) => flags[page],

package/dist/react/hooks/useCanSeePrices.js

@@ -40,7 +40,7 @@ import { useOptionalSession } from "../contexts/SessionContext.js";
  * than ripped out, because that is what makes this one boolean a real switch
  * instead of a rewrite. Two things outside this file move with it, and must
  * move back if it is ever flipped:
- *   · `gatedPriceWebPageJsonLd()` — dropped from the product and auction
+ *   · `gatedPriceWebPageJsonLd()` — dropped from the product and collector drop
  *     pages. `isAccessibleForFree: false` over a price anyone can read is a
  *     false declaration to a crawler, which is the exact mismatch the node was
  *     added to prevent, pointed the other way.

package/dist/react/hooks/useCountdown.d.ts

@@ -18,7 +18,7 @@ export interface CountdownRemaining {
 /**
  * @example
  * ```tsx
- * const remaining = useCountdown(auction.endsAt);
+ * const remaining = useCountdown(collectorDrop.endsAt);
  * if (!remaining) return <span>Ended</span>;
  * return <span>{remaining.hours}h {remaining.minutes}m {remaining.seconds}s</span>;
  * ```

package/dist/react/hooks/useCountdown.js

@@ -19,7 +19,7 @@ function resolveMs(endDate) {
 /**
  * @example
  * ```tsx
- * const remaining = useCountdown(auction.endsAt);
+ * const remaining = useCountdown(collectorDrop.endsAt);
  * if (!remaining) return <span>Ended</span>;
  * return <span>{remaining.hours}h {remaining.minutes}m {remaining.seconds}s</span>;
  * ```

package/dist/react/hooks/useListingSurfaceVisibility.js

@@ -1,11 +1,21 @@
 "use client";
 import { useSiteSettings } from "../../core/hooks/useSiteSettings.js";
-import { ALL_LISTING_TYPES, isListingSurfaceVisible, isCountedSurfaceVisible, } from "../../_internal/shared/listing-types/feature-flags.js";
+import { ALL_LISTING_TYPES, isListingSurfaceVisible, isListingTypeListed, isCountedSurfaceVisible, } from "../../_internal/shared/listing-types/feature-flags.js";
 export function useListingSurfaceVisibility() {
     const { data } = useSiteSettings();
     const settings = { listings: { listingTypes: data?.listings?.listingTypes } };
     const counts = data?.surfaceCounts;
-    const flags = Object.fromEntries(ALL_LISTING_TYPES.map((t) => [t, isListingSurfaceVisible(t, settings, counts)]));
+    /*
+     * 🛑 `isListingSurfaceVisible` alone is not "should this be linked" — it
+     * answers enabled-and-has-stock, which stays `true` for `"unlisted"` (an
+     * unlisted type's own pages must keep serving at 200). This hook decides
+     * whether a nav/footer LINK renders, so it also requires `isListingTypeListed`
+     * — the one place "unlisted" actually withdraws a link rather than a page.
+     */
+    const flags = Object.fromEntries(ALL_LISTING_TYPES.map((t) => [
+        t,
+        isListingSurfaceVisible(t, settings, counts) && isListingTypeListed(t, settings),
+    ]));
     return {
         ...flags,
         isVisible: (type) => flags[type],

package/dist/react/hooks/useListingTypeFlags.d.ts

@@ -1,25 +1,79 @@
 import type { ListingType } from "../../features/products/types/index";
+import { type FlagChoice, type FlagValue } from "../../_internal/shared/listing-types/feature-flags";
 /**
  * W1-43 — useListingTypeFlags
  *
- * Returns the enabled-state for each listing type as configured in
- * `siteSettings.listings.listingTypes`. Consumers should hide nav items,
- * filter TypeDropdown options, and reject API requests for disabled types.
+ * Reads `siteSettings.listings.listingTypes` and answers, per listing type,
+ * the TWO different questions that flag can be asked.
  *
- * Defaults to all-enabled when settings haven't loaded yet — match the
- * permissive default used by `DEFAULT_SITE_SETTINGS_DATA` so first paint
+ * Defaults to all-enabled/all-listed when settings haven't loaded yet — match
+ * the permissive default used by `DEFAULT_SITE_SETTINGS_DATA` so first paint
  * doesn't briefly hide enabled features.
  *
  * KEYED ON THE UNION, NOT A HAND-WRITTEN LIST (2026-08-21). Both types below
  * used to enumerate seven types by hand and had never been updated for `art`
- * and `stickers` — so `isEnabled("art")` didn't even typecheck, and the seller
+ * and `stickers` (then two separate members) — so `isEnabled("art")` didn't
+ * even typecheck, and the seller
  * TypeDropdown (its main consumer) could not offer either type. Deriving from
  * `ListingType` makes a missing member a compile error, matching the same
  * decision made for `ALL_LISTING_TYPES_MAP` in `feature-flags.ts`.
+ *
+ * ## 🛑 THREE STORED STATES, TWO DIFFERENT ANSWERS — read this before using it
+ *
+ * The flag is `true | "unlisted" | false`, and this hook used to collapse it
+ * with a single `lt?.[type] !== false`. **`"unlisted" !== false` is `true`**,
+ * so every consumer read an unlisted type as fully available and the third
+ * state did nothing at all — a link that had been correctly hidden came back,
+ * and unlisted types stayed in the `/products` type tabs and type filter.
+ * That was a real regression, found by review, and it is why a boolean is no
+ * longer the only thing this hook hands out.
+ *
+ * | stored | `isEnabled` | `isListed` | means |
+ * |---|---|---|---|
+ * | `true` / absent | ✅ | ✅ | sold and advertised |
+ * | `"unlisted"`    | ✅ | ❌ | **still sold and still serves its pages** — withdrawn from nav, footer, sitemap, type tabs and type filters |
+ * | `false`         | ❌ | ❌ | not sold; the surface 404s |
+ *
+ * **Which one do I want?**
+ *
+ * - **AUTHORING / operating on a type** → `isEnabled`. A seller must be able to
+ *   list, edit and filter their own unlisted-type stock, and a form section for
+ *   a type the site still sells must keep rendering. Unlisting withdraws
+ *   DISCOVERY, never the ability to transact.
+ * - **DISCOVERY — any link, tab, chip, filter option or nav entry that offers a
+ *   browsing visitor a way INTO the type** → `isListed`.
+ *
+ * The indexed form (`flags["collector-drop"]`) is `isEnabled`, kept because
+ * that is what the authoring consumers want and what they already read. If you
+ * are gating something a visitor CLICKS, use `isListed` explicitly.
+ *
+ * Audited consumers (2026-11-07, after the regression above):
+ *
+ * | consumer | gates | reads |
+ * |---|---|---|
+ * | `ProductForm` | seller form sections per type | `isEnabled` |
+ * | `SellerProductsView` TypeDropdown | seller's own stock filter | `isEnabled` |
+ * | `AppLayoutShell` | the "collector drops won" profile stat | `isEnabled` |
+ * | `ProductsIndexListing` query span | which types the page queries | `isEnabled` |
+ * | `ProductsIndexListing` tabs + filter chips | discovery | **`isListed`** |
+ * | `UserBidsView` "Browse collector drops" | discovery | **`isListed`** |
+ *
+ * `useListingSurfaceVisibility` is the stricter sibling for nav/footer: listed
+ * AND measured non-empty. Use it when an empty surface should also drop out.
  */
-export type ListingTypeFlagsShape = Partial<Record<ListingType, boolean>>;
+export type ListingTypeFlagsShape = Partial<Record<ListingType, FlagValue>>;
 export type ListingTypeFlags = Record<ListingType, boolean> & {
-    /** True when the listing type is enabled (or the setting hasn't loaded yet). */
+    /**
+     * Does this marketplace SELL the type at all? True for `"unlisted"`.
+     * The right question for authoring and for operating on existing stock.
+     */
     isEnabled: (type: ListingType) => boolean;
+    /**
+     * May a visitor be OFFERED a way into the type — a link, tab, chip or
+     * filter option? False for `"unlisted"` as well as `false`.
+     */
+    isListed: (type: ListingType) => boolean;
+    /** The raw three-state value, for anything that must tell all three apart. */
+    choiceFor: (type: ListingType) => FlagChoice;
 };
 export declare function useListingTypeFlags(): ListingTypeFlags;

package/dist/react/hooks/useListingTypeFlags.js

@@ -1,14 +1,21 @@
 "use client";
 import { useSiteSettings } from "../../core/hooks/useSiteSettings.js";
-import { ALL_LISTING_TYPES } from "../../_internal/shared/listing-types/feature-flags.js";
+import { ALL_LISTING_TYPES, isListingTypeEnabled, isListingTypeListed, flagValueToChoice, } from "../../_internal/shared/listing-types/feature-flags.js";
 export function useListingTypeFlags() {
     const { data } = useSiteSettings();
-    const lt = data?.listings?.listingTypes;
-    // A type is disabled only when EXPLICITLY set to false — a missing flag (or
-    // settings that haven't loaded) means enabled.
-    const flags = Object.fromEntries(ALL_LISTING_TYPES.map((type) => [type, lt?.[type] !== false]));
+    const settings = { listings: { listingTypes: data?.listings?.listingTypes } };
+    /*
+     * 🛑 Both maps go through the SHARED predicates in `feature-flags.ts` rather
+     * than re-deriving a comparison here. The regression this file is annotated
+     * for was a locally re-derived `!== false`; one authority for the three
+     * states is what stops the next copy drifting the same way.
+     */
+    const enabled = Object.fromEntries(ALL_LISTING_TYPES.map((type) => [type, isListingTypeEnabled(type, settings)]));
+    const listed = Object.fromEntries(ALL_LISTING_TYPES.map((type) => [type, isListingTypeListed(type, settings)]));
     return {
-        ...flags,
-        isEnabled: (type) => flags[type],
+        ...enabled,
+        isEnabled: (type) => enabled[type],
+        isListed: (type) => listed[type],
+        choiceFor: (type) => flagValueToChoice(data?.listings?.listingTypes?.[type]),
     };
 }

package/dist/repositories/index.d.ts

@@ -13,15 +13,14 @@ export { AddressesRepository, addressesRepository, } from "../features/addresses
 export { ProductRepository, productRepository, resolveStockResync, } from "../features/products/repository/products.repository";
 export { OrderRepository, orderRepository, } from "../features/orders/repository/orders.repository";
 export { ReviewRepository, reviewRepository, } from "../features/reviews/repository/reviews.repository";
-export { bidRepository } from "../features/auctions/repository/bid.repository";
+export { bidRepository } from "../features/collector-drops/repository/bid.repository";
 export { CartRepository, cartRepository, } from "../features/cart/repository/cart.repository";
 export { StoreRepository, storeRepository, } from "../features/stores/repository/store.repository";
+export { SellerProfileRepository, sellerProfileRepository, } from "../features/seller/repository/seller-profile.repository";
 export { siteSettingsRepository } from "../features/admin/repository/site-settings.repository";
 export { analyticsRollupRepository } from "../features/admin/repository/analytics-rollup.repository";
 export type { AnalyticsRollupDocument } from "../features/admin/repository/analytics-rollup.repository";
 export { notificationRepository } from "../features/admin/repository/notification.repository";
-export { carouselRepository } from "../features/homepage/repository/carousel.repository";
-export { carouselsRepository, CarouselsRepository } from "../features/homepage/repository/carousels.repository";
 export { homepageSectionsRepository } from "../features/homepage/repository/homepage-sections.repository";
 export { CategoriesRepository, categoriesRepository, } from "../features/categories/repository/categories.repository";
 export { couponsRepository } from "../features/promotions/repository/coupons.repository";
@@ -59,7 +58,7 @@ export { ProductFeaturesRepository, productFeaturesRepository, } from "../featur
 export type { ProductFeatureListFilter } from "../features/products/repository/product-features.repository";
 export { loadProductFeaturesForStore } from "../features/products/repository/loadProductFeatures";
 export { TaxCodesRepository, taxCodesRepository, } from "../features/tax-codes/repository/tax-codes.repository";
-export { LotteryEntryRepository, lotteryEntryRepository, } from "../features/lottery/repository/lottery-entry.repository";
+export { GiveawayEntryRepository, giveawayEntryRepository, } from "../features/giveaway/repository/giveaway-entry.repository";
 export { MediaAssetsRepository, mediaAssetsRepository, } from "../features/media/repository/media-assets.repository";
 export type { MediaAssetDocument, MediaAssetCreateInput, } from "../features/media/repository/media-assets.repository";
 export { PageViewsRepository, pageViewsRepository, PAGE_VIEW_ENTITY_TYPES, } from "../features/analytics/repository/page-views.repository";

package/dist/repositories/index.js

@@ -27,16 +27,15 @@ resolveStockResync, } from "../features/products/repository/products.repository.
 export { OrderRepository, orderRepository, } from "../features/orders/repository/orders.repository.js";
 export { ReviewRepository, reviewRepository, } from "../features/reviews/repository/reviews.repository.js";
 // Canonical appkit-owned repositories
-export { bidRepository } from "../features/auctions/repository/bid.repository.js";
+export { bidRepository } from "../features/collector-drops/repository/bid.repository.js";
 export { CartRepository, cartRepository, } from "../features/cart/repository/cart.repository.js";
 export { StoreRepository, storeRepository, } from "../features/stores/repository/store.repository.js";
+export { SellerProfileRepository, sellerProfileRepository, } from "../features/seller/repository/seller-profile.repository.js";
 // SB-UNI-A 2026-05-13 — storeAddressRepository deleted. Use addressesRepository
 // with ownerType:"store" instead.
 export { siteSettingsRepository } from "../features/admin/repository/site-settings.repository.js";
 export { analyticsRollupRepository } from "../features/admin/repository/analytics-rollup.repository.js";
 export { notificationRepository } from "../features/admin/repository/notification.repository.js";
-export { carouselRepository } from "../features/homepage/repository/carousel.repository.js";
-export { carouselsRepository, CarouselsRepository } from "../features/homepage/repository/carousels.repository.js";
 export { homepageSectionsRepository } from "../features/homepage/repository/homepage-sections.repository.js";
 export { CategoriesRepository, categoriesRepository, } from "../features/categories/repository/categories.repository.js";
 export { couponsRepository } from "../features/promotions/repository/coupons.repository.js";
@@ -77,8 +76,8 @@ export { TaxCodesRepository, taxCodesRepository, } from "../features/tax-codes/r
 // SB-UNI-V — BundlesRepository deleted; bundles live on categoriesRepository
 // with categoryType:"bundle". See features/categories/repository for the
 // listByType / findBySlugAndType helpers.
-// Lottery entries repository
-export { LotteryEntryRepository, lotteryEntryRepository, } from "../features/lottery/repository/lottery-entry.repository.js";
+// Giveaway entries repository
+export { GiveawayEntryRepository, giveawayEntryRepository, } from "../features/giveaway/repository/giveaway-entry.repository.js";
 // Media assets — short ID → storagePath mapping for SEO-friendly /media/{id} URLs
 export { MediaAssetsRepository, mediaAssetsRepository, } from "../features/media/repository/media-assets.repository.js";
 export { PageViewsRepository, pageViewsRepository, PAGE_VIEW_ENTITY_TYPES, } from "../features/analytics/repository/page-views.repository.js";