@mohasinac/appkit 4.64.1 → 4.66.0

package/dist/_internal/server/features/promotions/data.d.ts

@@ -15,13 +15,34 @@ export declare const getCouponByCode: (code: string) => Promise<import("../../..
  * 🛑 EXPIRED AND INACTIVE COUPONS ARE DROPPED HERE, not in the renderer.
  * A blog post from March that still advertises a code which now errors at
  * checkout is worse than one that advertises nothing: the reader does the
- * work of copying it and is refused at the till. `isCouponValid` is the same
- * predicate checkout applies (active + inside its window + under its total
- * limit), so the page cannot promise what the till will decline.
+ * work of copying it and is refused at the till.
+ *
+ * 🛑 BUT A NOT-YET-OPEN CODE IS KEPT — `isCouponDisplayable`, not
+ * `isCouponValid`. This used to be the checkout predicate, which also requires
+ * `startDate <= now`, and that single clause is why the Diwali event rendered
+ * ONE coupon where it carries five: all four attached codes open on Dhanteras.
+ * Publishing a code ahead of time is deliberate ("save it ahead of time," says
+ * the event's own copy); hiding it breaks the page's own promise.
  *
  * It does NOT check `perUserLimit` — that is per-reader and unknowable on a
  * cached public page. A reader who has personally exhausted a still-valid
  * coupon is refused at checkout with a message that can explain why; that is
  * the correct place for it.
  */
+/**
+ * Every live coupon, for the homepage `coupons` rail.
+ *
+ * 🛑 SAME DISPLAY PREDICATE AS `/promotions` AND THE EVENT PAGE, deliberately.
+ * These are the same claim made in three places; a code visible on one and
+ * absent from another reads as a broken link. One `isCouponDisplayable` call
+ * is what keeps them from drifting — this codebase has paid for hand-written
+ * copies of a money predicate before (Root Cause #75), and these three had in
+ * fact already drifted from `/api/coupons`, which never applied the
+ * start-date clause and so rendered codes the server surfaces swore did not
+ * exist.
+ *
+ * `limit` is applied LAST, after filtering, so an expired code can never
+ * occupy one of the rail's slots and silently push a live one off the end.
+ */
+export declare const getHomepageCoupons: (limit: number) => Promise<AttachedCoupon[]>;
 export declare const getAttachedCoupons: (couponIds: readonly string[] | undefined) => Promise<AttachedCoupon[]>;

package/dist/_internal/server/features/promotions/data.js

@@ -1,6 +1,6 @@
 import { cache } from "react";
-import { couponsRepository } from "../../../../repositories/index.js";
-import { isCouponValid } from "../../../../features/promotions/schemas/index.js";
+import { couponsRepository } from "../../../../features/promotions/repository/coupons.repository.js";
+import { isCouponDisplayable } from "../../../../features/promotions/schemas/index.js";
 import { toAttachedCoupon } from "./adapters.js";
 import { safeRead } from "../../../../errors/safe-read.js";
 export const getCouponByCode = cache(async (code) => {
@@ -21,15 +21,50 @@ export const getCouponByCode = cache(async (code) => {
  * 🛑 EXPIRED AND INACTIVE COUPONS ARE DROPPED HERE, not in the renderer.
  * A blog post from March that still advertises a code which now errors at
  * checkout is worse than one that advertises nothing: the reader does the
- * work of copying it and is refused at the till. `isCouponValid` is the same
- * predicate checkout applies (active + inside its window + under its total
- * limit), so the page cannot promise what the till will decline.
+ * work of copying it and is refused at the till.
+ *
+ * 🛑 BUT A NOT-YET-OPEN CODE IS KEPT — `isCouponDisplayable`, not
+ * `isCouponValid`. This used to be the checkout predicate, which also requires
+ * `startDate <= now`, and that single clause is why the Diwali event rendered
+ * ONE coupon where it carries five: all four attached codes open on Dhanteras.
+ * Publishing a code ahead of time is deliberate ("save it ahead of time," says
+ * the event's own copy); hiding it breaks the page's own promise.
  *
  * It does NOT check `perUserLimit` — that is per-reader and unknowable on a
  * cached public page. A reader who has personally exhausted a still-valid
  * coupon is refused at checkout with a message that can explain why; that is
  * the correct place for it.
  */
+/**
+ * Every live coupon, for the homepage `coupons` rail.
+ *
+ * 🛑 SAME DISPLAY PREDICATE AS `/promotions` AND THE EVENT PAGE, deliberately.
+ * These are the same claim made in three places; a code visible on one and
+ * absent from another reads as a broken link. One `isCouponDisplayable` call
+ * is what keeps them from drifting — this codebase has paid for hand-written
+ * copies of a money predicate before (Root Cause #75), and these three had in
+ * fact already drifted from `/api/coupons`, which never applied the
+ * start-date clause and so rendered codes the server surfaces swore did not
+ * exist.
+ *
+ * `limit` is applied LAST, after filtering, so an expired code can never
+ * occupy one of the rail's slots and silently push a live one off the end.
+ */
+export const getHomepageCoupons = cache(async (limit) => {
+    /*
+     * `safeRead`, for the reason given on `getAttachedCoupons` below: the
+     * homepage is prerendered and an unguarded throw during the prerender
+     * ATTEMPT is fatal to the production build. A failed read costs the page
+     * its coupon rail and records a DEGRADED_READ — it does not cost the
+     * homepage.
+     */
+    const docs = await safeRead(() => couponsRepository.getActiveCoupons(), {
+        route: "/",
+        key: "promotions.getActiveCoupons",
+        fallback: [],
+    });
+    return docs.filter(isCouponDisplayable).map(toAttachedCoupon).slice(0, limit);
+});
 export const getAttachedCoupons = cache(async (couponIds) => {
     if (!couponIds || couponIds.length === 0)
         return [];
@@ -46,5 +81,5 @@ export const getAttachedCoupons = cache(async (couponIds) => {
         key: "promotions.findByIds",
         fallback: [],
     });
-    return docs.filter(isCouponValid).map(toAttachedCoupon);
+    return docs.filter(isCouponDisplayable).map(toAttachedCoupon);
 });

package/dist/_internal/server/features/promotions/index.d.ts

@@ -1,4 +1,4 @@
-export { getCouponByCode, getAttachedCoupons } from "./data";
+export { getCouponByCode, getAttachedCoupons, getHomepageCoupons } from "./data";
 export { toAttachedCoupon } from "./adapters";
 export { validateCoupon, computeDiscount } from "./service";
 export { applyCouponAction, createCouponAction, updateCouponAction, deactivateCouponAction } from "./actions";

package/dist/_internal/server/features/promotions/index.js

@@ -1,4 +1,4 @@
-export { getCouponByCode, getAttachedCoupons } from "./data.js";
+export { getCouponByCode, getAttachedCoupons, getHomepageCoupons } from "./data.js";
 export { toAttachedCoupon } from "./adapters.js";
 export { validateCoupon, computeDiscount } from "./service.js";
 export { applyCouponAction, createCouponAction, updateCouponAction, deactivateCouponAction } from "./actions.js";

package/dist/_internal/server/features/promotions/service.js

@@ -1,4 +1,4 @@
-import { couponsRepository } from "../../../../repositories/index.js";
+import { couponsRepository } from "../../../../features/promotions/repository/coupons.repository.js";
 import { roundRupees } from "../../../../utils/number.formatter.js";
 import { CouponNotFoundError, CouponExpiredError, CouponUsageLimitError, CouponPerUserLimitError, CouponMinPurchaseError, CouponScopeError, } from "../../../shared/features/promotions/errors.js";
 export async function validateCoupon(input, userId) {

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

@@ -39,6 +39,7 @@
  * @tag sideEffects:none
  */
 import { pluginFor } from "../../../../shared/listing-types/_registry.js";
+import { ROUTES } from "../../../../../next/routing/route-map.js";
 // Defined here, not in `_registry` — imported from the DEFINING module
 // (Root Cause #18).
 import { ALL_LISTING_TYPES } from "../../../../shared/listing-types/feature-flags.js";
@@ -82,23 +83,37 @@ export const INDEX_TYPES = [
             weight: t === "standard" ? 1.0 : 0.98,
         };
     }),
-    { key: "category", hrefTemplate: "/categories/{s}", moreHref: "/categories", weight: 0.95 },
-    { key: "brand", hrefTemplate: "/brands/{s}", moreHref: "/brands", weight: 0.9 },
-    { key: "part", hrefTemplate: "/parts/{s}", moreHref: "/parts", weight: 0.9 },
-    { key: "model", hrefTemplate: "/categories/{s}", moreHref: "/categories", weight: 0.85 },
-    { key: "store", hrefTemplate: "/stores/{s}", moreHref: "/stores", weight: 0.8 },
-    { key: "blog", hrefTemplate: "/blog/{s}", moreHref: "/blog", weight: 0.7 },
-    { key: "event", hrefTemplate: "/events/{s}", moreHref: "/events", weight: 0.7 },
-    { key: "faq", hrefTemplate: "/faqs/{s}", moreHref: "/faqs", weight: 0.6 },
-    { key: "review", hrefTemplate: "/reviews/{s}", moreHref: "/reviews", weight: 0.5 },
-    { key: "group", hrefTemplate: "/groups/{s}", moreHref: "/products", weight: 0.5 },
-    { key: "scammer", hrefTemplate: "/scams/{s}", moreHref: "/scams", weight: 0.5 },
+    /*
+     * 🛑 Built from ROUTES, exactly as the listing-type entries above are built
+     * from `pluginFor`. These ten were hand-written path literals until
+     * 2026-10-24 — sitting directly beside a block whose own comment says "One
+     * source of truth, no second mapping" and cites Root Cause #48 for the
+     * version of this bug that shipped. A renamed segment would have moved every
+     * real page and left the search index pointing at the old one, with each
+     * result rendering correctly and navigating to a 404.
+     *
+     * `{s}` is the placeholder the template engine substitutes, so the builder
+     * functions are handed it directly — the same trick `detailRoute("{s}")` uses
+     * above rather than re-deriving the shape.
+     */
+    { key: "category", hrefTemplate: ROUTES.PUBLIC.CATEGORY_DETAIL("{s}"), moreHref: String(ROUTES.PUBLIC.CATEGORIES), weight: 0.95 },
+    { key: "brand", hrefTemplate: ROUTES.PUBLIC.BRAND_DETAIL("{s}"), moreHref: String(ROUTES.PUBLIC.BRANDS), weight: 0.9 },
+    { key: "part", hrefTemplate: ROUTES.PUBLIC.PART_CLASSIFICATION("{s}"), moreHref: String(ROUTES.PUBLIC.PARTS), weight: 0.9 },
+    /* A model IS a category row, which is why it shares the category route. */
+    { key: "model", hrefTemplate: ROUTES.PUBLIC.CATEGORY_DETAIL("{s}"), moreHref: String(ROUTES.PUBLIC.CATEGORIES), weight: 0.85 },
+    { key: "store", hrefTemplate: ROUTES.PUBLIC.STORE_DETAIL("{s}"), moreHref: String(ROUTES.PUBLIC.STORES), weight: 0.8 },
+    { key: "blog", hrefTemplate: ROUTES.BLOG.ARTICLE("{s}"), moreHref: String(ROUTES.BLOG.LIST), weight: 0.7 },
+    { key: "event", hrefTemplate: ROUTES.PUBLIC.EVENT_DETAIL("{s}"), moreHref: String(ROUTES.PUBLIC.EVENTS), weight: 0.7 },
+    { key: "faq", hrefTemplate: ROUTES.PUBLIC.FAQ_CATEGORY("{s}"), moreHref: String(ROUTES.PUBLIC.FAQS), weight: 0.6 },
+    { key: "review", hrefTemplate: ROUTES.PUBLIC.REVIEW_DETAIL("{s}"), moreHref: String(ROUTES.PUBLIC.REVIEWS), weight: 0.5 },
+    { key: "group", hrefTemplate: ROUTES.PUBLIC.GROUP_DETAIL("{s}"), moreHref: String(ROUTES.PUBLIC.PRODUCTS), weight: 0.5 },
+    { key: "scammer", hrefTemplate: ROUTES.PUBLIC.SCAM_DETAIL("{s}"), moreHref: String(ROUTES.PUBLIC.SCAMS), weight: 0.5 },
     /* `/promotions` has no per-coupon page, so `{s}` is absent on purpose and
      * `hrefFor`'s replace is a no-op. Eleven rows all landing on one page would
      * be noise in the federated GROUP (which is why `search-sources.ts` omits
      * coupons), but in the index it is the difference between a code being
      * findable and not. */
-    { key: "coupon", hrefTemplate: "/promotions", moreHref: "/promotions", weight: 0.4 },
+    { key: "coupon", hrefTemplate: String(ROUTES.PUBLIC.PROMOTIONS), moreHref: String(ROUTES.PUBLIC.PROMOTIONS), weight: 0.4 },
 ];
 const facet = (pairs) => {
     const parts = pairs

package/dist/_internal/server/features/seo/sitemap.js

@@ -2,7 +2,7 @@ import { normalizeError } from "../../../../errors/normalize.js";
 import { getAdminDb } from "../../../../providers/db-firebase/index.js";
 import { ROUTES } from "../../../../next/routing/route-map.js";
 import { PRODUCT_COLLECTION } from "../../../../features/products/schemas/firestore.js";
-import { EVENTS_COLLECTION, EVENT_FIELDS } from "../../../../features/events/index.js";
+import { EVENTS_COLLECTION, EVENT_FIELDS } from "../../../../features/events/schemas/firestore.js";
 import { BLOG_POSTS_COLLECTION, BLOG_POST_FIELDS } from "../../../../features/blog/schemas/firestore.js";
 import { CATEGORIES_COLLECTION, CATEGORY_FIELDS } from "../../../../features/categories/schemas/firestore.js";
 // Imported from the DEFINING module, not the feature barrel (Root Cause #18).
@@ -14,6 +14,9 @@ import { PART_GLOSSARY_COLLECTION, ALL_PART_SLOTS } from "../../../../features/p
 import { serverLogger } from "../../../../monitoring/server-logger.js";
 import { PRODUCT_FIELDS } from "../../../../constants/field-names.js";
 import { PRODUCT_DETAIL_LISTING_TYPES } from "./product-detail-types.js";
+import { safeRead } from "../../../../errors/safe-read.js";
+import { siteSettingsRepository } from "../../../../features/admin/repository/site-settings.repository.js";
+import { ALL_BROWSE_PAGES, browsePageForPath, isBrowsePageEnabled, } from "../../../shared/listing-types/feature-flags.js";
 // Product field strings — matches consumer field-names.ts
 const PRODUCT_STATUS = "status";
 const PRODUCT_STATUS_PUBLISHED = "published";
@@ -618,17 +621,43 @@ export async function buildSitemap({ baseUrl }) {
         bey: beyUrls.length,
         part: partUrls.length,
     };
-    const empty = Object.entries(sections)
-        .filter(([, n]) => n === 0)
-        .map(([name]) => name);
-    const total = Object.values(sections).reduce((a, b) => a + b, 0);
-    if (empty.length > 0) {
-        serverLogger.warn(`sitemap: ${empty.length} section(s) produced 0 URLs`, { empty, sections, total });
-    }
-    else {
-        serverLogger.info("sitemap: built", { sections, total });
-    }
-    return [
+    /*
+     * Drop every URL belonging to a CLOSED browse section.
+     *
+     * 🛑 A single filter over the assembled list, not a condition threaded
+     * through the eighteen fetchers above. Section URLs are emitted from several
+     * of them plus `staticPages`, so gating from the inside is five edits and
+     * five chances to miss the sixth — and `browsePageForPath` is the same rule
+     * the navbar and the footer use, so the sitemap cannot end up disagreeing
+     * with the chrome about which sections exist.
+     *
+     * Advertising a URL that answers 404 is worse than omitting it: it is Root
+     * Cause #81's host/sitemap disagreement in miniature, and it spends crawl
+     * budget on pages we have deliberately withdrawn.
+     *
+     * 🛑 Applied BEFORE the per-section digest below. The digest is what
+     * `scripts/deploy.mjs` asserts against, so counting pre-filter would log
+     * URLs the response does not carry.
+     */
+    const settings = await safeRead(() => siteSettingsRepository.findById("global"), {
+        route: "sitemap.xml",
+        key: "sitemap.siteSettings",
+        // Fails OPEN: an unreadable settings document is not evidence that a
+        // section was closed, and silently dropping the catalogue from the sitemap
+        // on a transient Firestore error is the expensive direction of this guess.
+        fallback: null,
+    });
+    const closed = new Set(ALL_BROWSE_PAGES.filter((p) => !isBrowsePageEnabled(p, settings)));
+    const keep = (entry) => {
+        if (closed.size === 0)
+            return true;
+        const path = entry.url.startsWith("http")
+            ? new URL(entry.url).pathname
+            : entry.url;
+        const page = browsePageForPath(path);
+        return page === null || !closed.has(page);
+    };
+    const all = [
         ...staticUrls,
         ...categoryUrls,
         ...brandUrls,
@@ -648,5 +677,42 @@ export async function buildSitemap({ baseUrl }) {
         ...scammerUrls,
         ...beyUrls,
         ...partUrls,
-    ];
+    ].filter(keep);
+    /*
+     * Recount AFTER the filter, and exclude a deliberately-closed section from
+     * the "produced 0 URLs" alarm.
+     *
+     * 🛑 Without this the feature would make its own monitoring cry wolf: the
+     * warning exists because `category: 0` once survived unnoticed for months,
+     * and a warning that fires every build for a reason everyone knows about is
+     * how the next real zero gets ignored. "Closed on purpose" and "broken" must
+     * not look the same in the log.
+     */
+    const sectionPage = {
+        category: "categories",
+        brand: "brands",
+        franchise: "franchise",
+        store: "stores",
+    };
+    for (const name of Object.keys(sections)) {
+        const page = sectionPage[name];
+        if (page && closed.has(page))
+            sections[name] = 0;
+    }
+    const empty = Object.entries(sections)
+        .filter(([name, n]) => n === 0 && !closed.has(sectionPage[name]))
+        .map(([name]) => name);
+    const total = all.length;
+    if (closed.size > 0) {
+        serverLogger.info("sitemap: browse section(s) closed, URLs withheld", {
+            closed: [...closed],
+        });
+    }
+    if (empty.length > 0) {
+        serverLogger.warn(`sitemap: ${empty.length} section(s) produced 0 URLs`, { empty, sections, total });
+    }
+    else {
+        serverLogger.info("sitemap: built", { sections, total });
+    }
+    return all;
 }

package/dist/_internal/server/features/shared/listing-data-factory.js

@@ -1,5 +1,5 @@
 import { cache } from "react";
-import { productRepository } from "../../../../repositories/index.js";
+import { productRepository } from "../../../../features/products/repository/products.repository.js";
 import { safeRead } from "../../../../errors/safe-read.js";
 import { loadProductFeaturesForStore } from "../../../../features/products/repository/loadProductFeatures.js";
 import { isPubliclyVisible } from "../../../shared/listing-types/availability.js";

package/dist/_internal/server/features/shipping/courier-block.js

@@ -28,7 +28,7 @@ import { EmailContainer, EmailDoc, EmailRow, } from "../../../../features/email/
 import { paymentCasesRepository } from "../../../../features/payment-cases/repository/payment-cases.repository.js";
 // `adminNotificationsRepository` lives behind the repositories barrel — the
 // same import the two existing staff-signal call sites use.
-import { adminNotificationsRepository } from "../../../../repositories/index.js";
+import { adminNotificationsRepository } from "../../../../features/store-extensions/repository/rbac.repositories.js";
 import { siteSettingsRepository } from "../../../../features/admin/repository/site-settings.repository.js";
 import { normalizeError } from "../../../../errors/normalize.js";
 import { serverLogger } from "../../../../monitoring/server-logger.js";

package/dist/_internal/server/features/site-settings/adapters.d.ts

@@ -39,7 +39,7 @@ import type { PublicSiteSettings } from "../../../shared/features/site-settings/
  */
 export declare const PUBLIC_SITE_SETTINGS_FIELDS: readonly ["contact", "payment", "listings", "notificationChannels", "announcementBar", "support", "navConfig", "actionConfig", "background", "watermark", "disabledRoutes", "chat", "search"];
 /** Everything else, with the reason it stays server-side. */
-export declare const PRIVATE_SITE_SETTINGS_FIELDS: readonly ["rateChanges", "id", "createdAt", "updatedAt", "credentials", "emailSettings", "legalPages", "commissions", "emi", "gst", "laborRate", "adSettings", "integrations", "platformLimits", "auctionConfig", "siteName", "tagline", "motto", "logo", "favicon", "seo", "socialLinks", "features", "shipping", "returns", "faq", "aboutContent", "navbarConfig", "footerConfig", "theme", "featuredResults", "messaging"];
+export declare const PRIVATE_SITE_SETTINGS_FIELDS: readonly ["rateChanges", "id", "createdAt", "updatedAt", "credentials", "emailSettings", "legalPages", "commissions", "emi", "gst", "laborRate", "adSettings", "integrations", "platformLimits", "auctionConfig", "siteName", "tagline", "motto", "logo", "favicon", "seo", "socialLinks", "features", "shipping", "returns", "faq", "aboutContent", "navbarConfig", "footerConfig", "theme", "featuredResults", "messaging", "whatsappFeed"];
 export interface ToPublicSiteSettingsOptions {
     /**
      * The resolved marker → wordmark → text watermark chain. Injected because

package/dist/_internal/server/features/site-settings/adapters.js

@@ -6,7 +6,7 @@
 export const PUBLIC_SITE_SETTINGS_FIELDS = [
     "contact", // user/orders/[id]/payment — contact.whatsappNumber (narrowed: no address/upiVpa)
     "payment", // CheckoutRouteClient — payment.otpCheckoutThreshold (narrowed)
-    "listings", // useListingTypeFlags — narrowed to listings.listingTypes; categoryTypes has no client reader
+    "listings", // useListingTypeFlags + LayoutShellClient nav filter — narrowed to listings.{listingTypes,browsePages}; categoryTypes has no client reader
     "notificationChannels", // NARROWED: only {email,whatsapp,sms}.enabled — see the projection below
     "announcementBar", // the homepage banner (AdminSiteSettingsView edits it)
     /*
@@ -118,6 +118,18 @@ export const PRIVATE_SITE_SETTINGS_FIELDS = [
     // checkbox, which disables itself when email is off — is behind the admin
     // API, which returns the full document.
     "messaging",
+    /*
+     * The WhatsApp catalogue feed kill switch. Read ONLY by
+     * `/whatsapp/{storeSlug}/feed.csv`, which is a server route doing its own
+     * settings read — the same shape as `auctionConfig` above.
+     *
+     * 🛑 Deliberately NOT public, unlike its sibling `search`. That one is public
+     * because its reader is a GUEST's search box, so a server-only flag could not
+     * reach the visitor it governs. This flag's only reader is Meta's crawler
+     * fetching a CSV; no browser consults it, and publishing "catalogue feeds are
+     * currently off platform-wide" is operational detail with no client to serve.
+     */
+    "whatsappFeed",
 ];
 export function toPublicSiteSettings(doc, opts) {
     return {
@@ -137,6 +149,9 @@ export function toPublicSiteSettings(doc, opts) {
         },
         listings: {
             listingTypes: doc.listings?.listingTypes,
+            // Read by LayoutShellClient to drop nav/footer links into a closed
+            // section. `categoryTypes` is still withheld — it has no client reader.
+            browsePages: doc.listings?.browsePages,
         },
         /*
          * 🛑 Narrowed to the three booleans a client reads, not the group by

package/dist/_internal/server/features/sticker-trace/promote-to-listings.js

@@ -34,7 +34,7 @@
 import { ValidationError } from "../../../../errors/validation-error.js";
 import { serverLogger } from "../../../../monitoring/server-logger.js";
 import { normalizeError } from "../../../../errors/normalize.js";
-import { productRepository } from "../../../../repositories/index.js";
+import { productRepository } from "../../../../features/products/repository/products.repository.js";
 import { mediaAssetsRepository } from "../../../../features/media/repository/media-assets.repository.js";
 import { stickerSheetsRepository } from "../../../../features/sticker-trace/repository/sticker-sheets.repository.js";
 /** A part that becomes its own listing: unique, and actually rendered. */

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

@@ -27,7 +27,7 @@ import type { StoreDetail, StoreListItem } from "../../../../features/stores/typ
  */
 export declare const PUBLIC_STORE_FIELDS: readonly ["id", "storeSlug", "ownerId", "storeName", "storeDescription", "storeCategory", "storeLogoURL", "storeBannerURL", "status", "isPublic", "stats", "bio", "location", "website", "socialLinks", "returnPolicy", "shippingPolicy", "isVacationMode", "vacationMessage", "supportsShippingProtection", "supportsSaleProtection", "allowSharedPurchase", "sharedPurchaseHandlingFee", "sharedPurchaseExtraShippingPerDestination", "isVerified", "sellerTier", "standing", "createdAt"];
 /** Everything else, with the reason it stays server-side. */
-export declare const PRIVATE_STORE_FIELDS: readonly ["whatsappNotifySubscribed", "trustedSeller", "acceptsPoints", "searchTxt", "whatsappNotifySubscribed", "updatedAt", "whatsappConfig", "adminNotes", "statusHistory", "statusHistoryTruncated", "tierLockedByAdmin", "suspensionReason", "capabilities", "customCommissionRate", "googleReviews", "shippingConfig", "emiEnabled", "pricesIncludeGst", "shippingPricing", "returnsDirectToSeller", "isFeatured", "vacationReturnDate", "isTestData", "testDataExpiresAt", "gstin", "legalName", "registeredAddress"];
+export declare const PRIVATE_STORE_FIELDS: readonly ["whatsappNotifySubscribed", "whatsappFeedEnabled", "trustedSeller", "acceptsPoints", "searchTxt", "whatsappNotifySubscribed", "updatedAt", "whatsappConfig", "adminNotes", "statusHistory", "statusHistoryTruncated", "tierLockedByAdmin", "suspensionReason", "capabilities", "customCommissionRate", "googleReviews", "shippingConfig", "emiEnabled", "pricesIncludeGst", "shippingPricing", "returnsDirectToSeller", "isFeatured", "vacationReturnDate", "isTestData", "testDataExpiresAt", "gstin", "legalName", "registeredAddress"];
 /**
  * Accepted input: a `StoreDocument` (the common case) or a loosely-typed
  * Firestore row. The legacy top-level counters below predate `stats` and are

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

@@ -104,6 +104,20 @@ export const PRIVATE_STORE_FIELDS = [
      * someone can name the client that reads it.
      */
     "whatsappNotifySubscribed",
+    /*
+     * 🛑 `whatsappFeedEnabled` — a seller's own DISTRIBUTION PLUMBING.
+     *
+     * Whether this store currently publishes `/whatsapp/{slug}/feed.csv` with
+     * rows in it. Absent means enabled, so the field is only ever present when a
+     * seller (or an admin) has switched the feed off.
+     *
+     * No public reader, which is this file's bar on its own. Beyond that, a buyer
+     * learns nothing from it — it says nothing about the goods, the price or the
+     * dispatch record — while publishing it would advertise which stores are
+     * reachable on WhatsApp at all, which is the same disclosure
+     * `whatsappNotifySubscribed` directly above is private to avoid.
+     */
+    "whatsappFeedEnabled",
     /*
      * 🛑 `trustedSeller` — OUR RISK POSTURE, not a badge.
      *

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

@@ -1,6 +1,6 @@
 "use server";
 import { cache } from "react";
-import { storeRepository } from "../../../../repositories/index.js";
+import { storeRepository } from "../../../../features/stores/repository/store.repository.js";
 import { STORES_PRODUCTS_PAGE_SIZE, STORES_SITEMAP_LIMIT, } from "../../../shared/features/stores/config.js";
 import { makeGetStoreListingsInitial } from "../shared/listing-data-factory.js";
 import { safeRead } from "../../../../errors/safe-read.js";

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

@@ -24,22 +24,26 @@ export declare function resolveStoreTabs(storeSlug: string, storeId: string | un
 /**
  * Where the bare `/stores/[slug]` route should land.
  *
- * Order: **About when the store has written one**, else the first
- * listing-type tab holding anything, else Coupons, else Reviews, else About.
- * `about` is always present in `tabs`, so this never falls through to nothing.
+ * Order: the first listing-type tab holding anything, else Coupons, else
+ * Reviews, else About. `about` is always present in `tabs`, so this never
+ * falls through to nothing.
  *
- * 🛑 About was promoted to first on 2026-10-21, deliberately. Previously the
- * richest listing tab always won, so any stocked store sent every visitor
- * straight to a filtered product grid — the storefront read as a search
- * result, and a seller who had written an introduction was the only person who
- * ever saw it.
+ * 🛑 About was promoted to FIRST on 2026-10-21 and REVERTED on 2026-10-24.
+ * The argument for it was that a stocked storefront opening on a filtered
+ * product grid "reads as a search result". What it actually produced is worse
+ * and was reported as a bug: `store-letitrip-official` carries a
+ * `storeDescription`, so every visit to `/stores/store-letitrip-official`
+ * 307'd to `/about` — a page with no merchandise on it — and the shop read as
+ * having **no products at all**. Measured the day of the revert: the store
+ * holds 22 published listings, its `/products` tab renders 12 of them and its
+ * WhatsApp feed emits all 22, while the landing page showed none of it.
  *
- * It is gated on the store ACTUALLY having About content rather than applied
- * unconditionally: landing on an empty About page would be strictly worse than
- * landing on products, so the old behaviour remains the fallback. The caller
- * supplies the flag because this module takes a `storeId`, not the document,
- * and giving it store-shape knowledge it does not otherwise need would make it
- * a second place that decides what "has an About" means.
+ * A storefront's job is to show stock. An introduction is a tab, and the tab
+ * is right there in the nav bar.
+ *
+ * 🛑 Do NOT re-add a `hasAboutContent` parameter to re-litigate this. It was
+ * the mechanism of the regression, not a safeguard against it: having written
+ * a description is not evidence that a shopper wants to read one.
  */
-export declare function getDefaultStoreTabPath(storeSlug: string, storeId: string | undefined, settings: SiteSettingsSnapshot, hasAboutContent?: boolean): Promise<string>;
+export declare function getDefaultStoreTabPath(storeSlug: string, storeId: string | undefined, settings: SiteSettingsSnapshot): Promise<string>;
 export {};

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

@@ -27,7 +27,7 @@ import { ROUTES } from "../../../../next/routing/route-map.js";
 import { STORE_PAGE_TABS } from "../../../../features/products/constants/listing-tabs.js";
 import { isListingTypeEnabled, isCategoryTypeEnabled } from "../../../shared/listing-types/feature-flags.js";
 import { pluginFor } from "../../../shared/listing-types/_registry.js";
-import { listingTabCounts, } from "../products/listing-tab-counts.js";
+import { listingTabCounts } from "../products/listing-tab-counts.js";
 function tabLabel(base, count) {
     if (!count)
         return base;
@@ -116,29 +116,28 @@ export async function resolveStoreTabs(storeSlug, storeId, settings) {
 /**
  * Where the bare `/stores/[slug]` route should land.
  *
- * Order: **About when the store has written one**, else the first
- * listing-type tab holding anything, else Coupons, else Reviews, else About.
- * `about` is always present in `tabs`, so this never falls through to nothing.
+ * Order: the first listing-type tab holding anything, else Coupons, else
+ * Reviews, else About. `about` is always present in `tabs`, so this never
+ * falls through to nothing.
  *
- * 🛑 About was promoted to first on 2026-10-21, deliberately. Previously the
- * richest listing tab always won, so any stocked store sent every visitor
- * straight to a filtered product grid — the storefront read as a search
- * result, and a seller who had written an introduction was the only person who
- * ever saw it.
+ * 🛑 About was promoted to FIRST on 2026-10-21 and REVERTED on 2026-10-24.
+ * The argument for it was that a stocked storefront opening on a filtered
+ * product grid "reads as a search result". What it actually produced is worse
+ * and was reported as a bug: `store-letitrip-official` carries a
+ * `storeDescription`, so every visit to `/stores/store-letitrip-official`
+ * 307'd to `/about` — a page with no merchandise on it — and the shop read as
+ * having **no products at all**. Measured the day of the revert: the store
+ * holds 22 published listings, its `/products` tab renders 12 of them and its
+ * WhatsApp feed emits all 22, while the landing page showed none of it.
  *
- * It is gated on the store ACTUALLY having About content rather than applied
- * unconditionally: landing on an empty About page would be strictly worse than
- * landing on products, so the old behaviour remains the fallback. The caller
- * supplies the flag because this module takes a `storeId`, not the document,
- * and giving it store-shape knowledge it does not otherwise need would make it
- * a second place that decides what "has an About" means.
+ * A storefront's job is to show stock. An introduction is a tab, and the tab
+ * is right there in the nav bar.
+ *
+ * 🛑 Do NOT re-add a `hasAboutContent` parameter to re-litigate this. It was
+ * the mechanism of the regression, not a safeguard against it: having written
+ * a description is not evidence that a shopper wants to read one.
  */
-export async function getDefaultStoreTabPath(storeSlug, storeId, settings, hasAboutContent) {
+export async function getDefaultStoreTabPath(storeSlug, storeId, settings) {
     const { dropdownTabs, tabs } = await resolveStoreTabs(storeSlug, storeId, settings);
-    if (hasAboutContent) {
-        const about = tabs.find((t) => t.value === "about");
-        if (about)
-            return about.href;
-    }
     return (dropdownTabs[0] ?? tabs[0]).href;
 }

package/dist/_internal/server/features/sublisting-categories/data.js

@@ -1,5 +1,5 @@
 import { cache } from "react";
-import { categoriesRepository } from "../../../../repositories/index.js";
+import { categoriesRepository } from "../../../../features/categories/repository/categories.repository.js";
 export const getSublistingCategoryForDetail = cache(async (slug) => {
     return categoriesRepository.findBySlugAndType(slug, "sublisting");
 });

package/dist/_internal/server/features/wishlist/actions.d.ts

@@ -1,5 +1,5 @@
 import { type ActionResult } from "../../../shared/types/action-result";
-import { type WishlistItem } from "../../../../repositories";
+import type { UserWishlistItem as WishlistItem } from "../../../../features/wishlist/repository/user-wishlist.repository";
 export declare function addToWishlistAction(productId: string, extras?: {
     productType?: WishlistItem["productType"];
     priceAtAdd?: number;

package/dist/_internal/server/features/wishlist/actions.js

@@ -13,7 +13,7 @@ import { normalizeError } from "../../../../errors/normalize.js";
  */
 import { wrapAction } from "../../../shared/types/action-result.js";
 import { requireRoleUser } from "../../../../providers/auth-firebase/helpers.js";
-import { wishlistRepository, WishlistFullError, } from "../../../../repositories/index.js";
+import { wishlistRepository, WishlistFullError } from "../../../../features/wishlist/repository/user-wishlist.repository.js";
 import { WISHLIST_MAX } from "../../../shared/features/wishlist/config.js";
 import { WishlistCapError } from "../../../shared/features/wishlist/errors.js";
 export async function addToWishlistAction(productId, extras) {

package/dist/_internal/server/features/wishlist/data.d.ts

@@ -1,4 +1,4 @@
-import { type WishlistItem } from "../../../../repositories";
+import type { UserWishlistItem as WishlistItem } from "../../../../features/wishlist/repository/user-wishlist.repository";
 export declare const getWishlistForUser: (userId: string) => Promise<{
     items: WishlistItem[];
     meta: {

package/dist/_internal/server/features/wishlist/data.js

@@ -1,5 +1,5 @@
 import { cache } from "react";
-import { wishlistRepository } from "../../../../repositories/index.js";
+import { wishlistRepository } from "../../../../features/wishlist/repository/user-wishlist.repository.js";
 export const getWishlistForUser = cache(async (userId) => {
     const items = await wishlistRepository.getWishlistItems(userId).catch(() => []);
     return { items, meta: { total: items.length } };