@mohasinac/appkit 4.68.0 → 4.69.0

package/dist/_internal/shared/listing-types/route-gating.js

@@ -17,27 +17,22 @@
  * type-keyed gate could see them — the only thing that identifies them is
  * where they point.
  *
- * ## The rule, and the one case that makes it non-obvious
+ * ## Where the rules are written down
  *
- * A href is disabled when EVERY listing type that claims its route is
- * disabled. Not "any" — `art` and `stickers` share `/art`, so a site that
- * sells art but not stickers must keep `/art` reachable. Treating one disabled
- * claimant as enough would silently delete a working destination.
+ * On `isClosedHref` below — the three axes it reads (listing-type flags ANDed
+ * with measured counts, closed browse sections, hand-disabled routes), what it
+ * deliberately does not match, and the production measurement that forced each
+ * one. Stated there and not restated here deliberately: two comments
+ * disagreeing about what a gate matches is a defect this codebase keeps paying
+ * for, and the only safe number of descriptions is one.
  *
- * ## What it deliberately does NOT match
- *
- * Editorial pages that merely have a type's name in the path — `/help/auctions`,
- * `/how-auctions-work`, `/seller-guide/prize-draws`. None of them starts with
- * `/auctions`, so prefix matching excludes them for free, and that is correct:
- * an explainer about auctions is still honest reading when auctions are off.
- * A substring test would have eaten all three.
- *
- * Store tabs (`/stores/{slug}/auctions`) are also out of scope — those are
- * resolved by `resolveStoreTabs`, which owns its own visibility, and a second
- * owner is how a mirror drifts (Root Cause #42).
+ * Store tabs (`/stores/{slug}/auctions`) are out of scope — those are resolved
+ * by `resolveStoreTabs`, which owns its own visibility, and a second owner is
+ * how a mirror drifts (Root Cause #42).
  */
 import { LISTING_TYPE_REGISTRY } from "./_registry.js";
-import { ALL_LISTING_TYPES, isListingTypeEnabled } from "./feature-flags.js";
+import { ALL_LISTING_TYPES, isListingSurfaceVisible, } from "./feature-flags.js";
+import { closedSurfacePrefixes, isUnderClosedPrefix } from "./hidden-surfaces.js";
 /**
  * browse route → every listing type that browses there.
  *
@@ -88,27 +83,76 @@ function normalisePath(href) {
     // Trailing slash off, but never reduce "/" to "".
     return delocalised.length > 1 ? delocalised.replace(/\/+$/, "") : delocalised;
 }
+export function closedSurfaceContext(settings, counts) {
+    return { settings, counts, prefixes: closedSurfacePrefixes(settings) };
+}
 /**
- * `true` when `href` points at a listing type's browse page (or any page
- * beneath it) and every type that browses there is disabled.
- *
- * Fails OPEN on anything it cannot classify: an unknown path, an external URL
- * or a missing settings document all return `false`. A settings read that
- * errored must not strip working destinations out of the homepage — the same
- * reasoning as the suggestions endpoint's TTL cache and `src/proxy.ts`'s
- * disabled-routes gate.
+ * `true` when `href` leads somewhere this site has closed.
+ *
+ * ## THREE axes, because authored content can point at any of them
+ *
+ * This replaced `isDisabledListingHref`, which read `listings.listingTypes`
+ * and nothing else — and the two axes it could not see were the two doing
+ * visible damage. Measured on the live homepage, 2026-10-27:
+ *
+ *   · **counts.** `art` and `spares` had flag `true` and measured count `0`,
+ *     so they were auto-hidden everywhere — `/art` and `/spares` both answered
+ *     a real **404** at the edge — while the homepage went on shipping 3 links
+ *     to each from the "Shop extras" cards. `isListingTypeEnabled` reads the
+ *     flag only, so it called both of them enabled. `isListingSurfaceVisible`
+ *     ANDs the flag with the count, which is the rule every other surface on
+ *     the site already uses.
+ *   · **browse sections.** All four had been `false` since 2026-10-24, and the
+ *     homepage carried **34** `/categories` links across the welcome hero's
+ *     secondary CTA, the 35-button systems matrix and the 4-banner generation
+ *     promo grid.
+ *
+ * ## Deliberately link-based, never keyword-based
+ *
+ * Unchanged from the original, and still the point: nothing here reads copy.
+ * "Win it at your price" names no type, so a word search would miss it, and it
+ * would also eat the authenticity slide for saying "bid" in passing. A
+ * destination is checkable; prose is not.
+ *
+ * ## What it still does NOT match
+ *
+ * Editorial pages that merely carry a name in the path — `/help/auctions`,
+ * `/how-auctions-work`, `/seller-guide/prize-draws`. None starts with
+ * `/auctions`, so the `/`-delimited boundary excludes them for free, and that
+ * is correct: an explainer about auctions is honest reading when auctions are
+ * off.
+ *
+ * Fails OPEN on anything it cannot classify — an unknown path, an external
+ * URL, a missing settings document. A settings read that errored must not
+ * strip working destinations off the homepage (Root Cause #72).
  */
-export function isDisabledListingHref(href, settings) {
+export function isClosedHref(href, ctx) {
     const path = normalisePath(href);
     if (!path)
         return false;
+    // Closed browse sections and hand-disabled routes, descendants included.
+    if (isUnderClosedPrefix(path, ctx.prefixes))
+        return true;
     for (const [route, types] of TYPES_BY_BROWSE_ROUTE) {
         // The browse page itself, or a detail page under it. `startsWith(route)`
         // alone would match `/live` against `/livestream`, so the boundary is
         // explicit.
         if (path !== route && !path.startsWith(`${route}/`))
             continue;
-        return types.every((type) => !isListingTypeEnabled(type, settings));
+        /*
+         * 🛑 `every`, not `some`, and `isListingSurfaceVisible`, not
+         * `isListingTypeEnabled`.
+         *
+         * `every`: `art` and `stickers` share `/art`, so a site selling art but
+         * not stickers must keep `/art` reachable. One closed claimant is not
+         * enough — treating it as enough silently deletes a working destination.
+         *
+         * `isListingSurfaceVisible`: it ANDs the admin flag with the measured
+         * count, which is what makes the auto-hidden-because-empty case visible
+         * here. Reading the flag alone is exactly how the live homepage kept
+         * advertising `/art` and `/spares` after both began 404ing.
+         */
+        return types.every((type) => !isListingSurfaceVisible(type, ctx.settings, ctx.counts));
     }
     return false;
 }

package/dist/features/about/components/HelpPageView.js

@@ -10,6 +10,9 @@ import { Row, Stack } from "../../../ui/components/Layout.js";
 import { Section } from "../../../ui/components/Semantic.js";
 import { TextLink } from "../../../ui/components/TextLink.js";
 import { BookOpen, MessageCircle, ShoppingBag, Gavel, PackageCheck, UserCheck, Store, ShieldCheck, ChevronRight, } from "lucide-react";
+import { closedSurfaceContext, isClosedHref, } from "../../../_internal/shared/listing-types/route-gating.js";
+import { getSiteSettingsGlobal } from "../../admin/utils/getSiteSettingsGlobal.js";
+import { safeRead } from "../../../errors/safe-read.js";
 const __P = {
     p6: "p-[var(--appkit-space-6)]",
     p8: "p-[var(--appkit-space-8)]",
@@ -19,6 +22,21 @@ export async function HelpPageView({} = {}) {
     const flex = { row: FLEX_ROW };
     const { getTranslations } = await import("next-intl/server");
     const t = await getTranslations("helpPage");
+    /*
+     * 🛑 THE HELP INDEX IS A HARDCODED LINK LIST, which is the same blind spot
+     * the homepage had: nothing here knows that `/help/seller-badges` and
+     * `/seller-guide` are now closed, so two of its seven tiles pointed at a
+     * 404 — on the page a confused buyer goes to when something has already
+     * gone wrong.
+     *
+     * Filtered through the one closed-surface rule rather than by deleting the
+     * entries: a withdrawn surface is a flag, so the tile returns on its own if
+     * the flag is flipped back.
+     */
+    const settings = await safeRead(() => getSiteSettingsGlobal(), {
+        route: "/help", key: "help.siteSettings", fallback: null,
+    });
+    const closedSurfaces = closedSurfaceContext(settings, undefined);
     const TOPICS = [
         {
             icon: ShoppingBag,
@@ -77,7 +95,7 @@ export async function HelpPageView({} = {}) {
             iconColor: "text-rose-600 dark:text-rose-400",
         },
     ];
-    return (_jsxs(Div, { className: "-mx-4 md:-mx-6 lg:-mx-8 -mt-6 sm:-mt-8 lg:-mt-10", children: [_jsx(ProseHero, { title: t("title"), subtitle: t("subtitle") }), _jsxs(Stack, { gap: "14", className: `${page.container.md}`, padding: "content-banner", children: [renderTopicsGrid(t, flex, TOPICS), renderScamAwarenessAlert(t), renderTrackOrderSection(t), renderContactCtaSection(t)] })] }));
+    return (_jsxs(Div, { className: "-mx-4 md:-mx-6 lg:-mx-8 -mt-6 sm:-mt-8 lg:-mt-10", children: [_jsx(ProseHero, { title: t("title"), subtitle: t("subtitle") }), _jsxs(Stack, { gap: "14", className: `${page.container.md}`, padding: "content-banner", children: [renderTopicsGrid(t, flex, TOPICS.filter((x) => !isClosedHref(x.href, closedSurfaces))), renderScamAwarenessAlert(t), renderTrackOrderSection(t), renderContactCtaSection(t)] })] }));
 }
 function renderTopicsGrid(t, flex, topics) {
     return (_jsxs(Section, { children: [_jsx(Heading, { level: 2, className: "mb-6", align: "center", children: t("browseTopics") }), _jsx(Div, { layout: "grid", gap: "4", className: "sm:grid-cols-2 lg:grid-cols-3", children: topics.map(({ icon: Icon, title, desc, href, color, iconColor }) => (_jsxs(TextLink, { rounded: "xl", href: href, shadow: "hover-md", className: `group border p-[1.25rem] transition ${color} no-underline`, children: [_jsx(Row, { align: "center", justify: "center", className: `w-10 h-10 mb-3`, surface: "default", rounded: "lg", children: _jsx(Icon, { className: `w-5 h-5 ${iconColor}` }) }), _jsxs(Div, { layout: "flex", justify: "between", align: "start", className: flex.row, children: [_jsxs(Div, { children: [_jsx(Text, { className: "mb-1", weight: "semibold", children: title }), _jsx(Text, { variant: "secondary", className: "leading-relaxed", size: "sm", children: desc })] }), _jsx(ChevronRight, { className: "w-4 h-4 mt-1 flex-shrink-0 opacity-40 group-hover:opacity-80 transition-opacity" })] })] }, href))) })] }));

package/dist/features/admin/schemas/firestore.d.ts

@@ -780,6 +780,29 @@ export interface SiteSettingsDocument extends BaseDocument {
          * Add a new section THERE, not here.
          */
         browsePages?: Partial<Record<string, boolean>>;
+        /**
+         * Public paths withdrawn wholesale — closed including every descendant.
+         *
+         * 🛑 THE FOURTH AXIS, and it exists because the other three cannot express
+         * "this FEATURE is off". `listingTypes` closes a type's browse page,
+         * `browsePages` closes a taxonomy directory, `categoryTypes` closes
+         * bundles — and none of them reaches `/seller-guide`, `/fees`,
+         * `/how-payouts-work`, `/item-requests` or `/scams`.
+         *
+         * 🛑 NOT the same as `disabledRoutes`, and the difference is the whole
+         * point. That array is DERIVED: `updateNavConfigDomain` rebuilds it from
+         * `navConfig ∩ ALL_PUBLIC_NAV_ITEMS` on every nav toggle, so a path that
+         * is not a nav item CANNOT survive there — append one by hand and the next
+         * admin toggle silently re-opens it (Root Cause #42). Most of what a
+         * single-vendor storefront needs to withdraw is footer-only, so it has no
+         * nav item to hang off and this is the only durable home for it.
+         *
+         * Prefix-matched on a `/`-delimited boundary by `closedSurfacePrefixes`,
+         * so `/scams` takes `/scams/report` and `/scams/faqs` with it. Nothing is
+         * deleted: every route, page and `ROUTES.PUBLIC.*` constant still exists,
+         * and removing an entry re-opens it.
+         */
+        closedPaths?: string[];
     };
     /**
      * Admin-authored HTML overrides for the public policy pages. When a key holds

package/dist/features/admin/schemas/firestore.js

@@ -2,6 +2,10 @@
  * Admin Feature Firestore Document Types & Constants
  * Covers: notifications, chat rooms, site settings
  */
+/* Pure constants module with no firebase-admin in its import chain, so this
+ * stays safe in the client bundle (appkit Export Rules). Same reasoning as
+ * the ROUTES import in `_internal/shared/listing-types/feature-flags.ts`. */
+import { ROUTES } from "../../../next/routing/route-map.js";
 import { DEFAULT_AUCTION_BID_INCREMENT_TIERS } from "../../../_internal/shared/features/auctions/config.js";
 // Flag-key constants. Consumers MUST reference the bypass flag via this
 // constant so audit-checkout-bypass rule 1 (substring scan) only sees a
@@ -285,9 +289,14 @@ export const DEFAULT_SITE_SETTINGS_DATA = {
         whatsappNotifyFeeEnabled: false,
         whatsappNotifyFee: 10,
         whatsappNotifyMonthlyFee: 199,
-        giftWrapFeeEnabled: true,
+        /* Opt-in buyer UPSELLS, off since 2026-10-27 — gift wrap and shipment
+         * protection are marketplace merchandising, not "the basic of the basic
+         * for an ecommerce". Disabling an opt-in extra removes an OPTION, so no
+         * total can go up. `platformFeePercent` is deliberately NOT touched: that
+         * changes what every buyer pays and is a pricing decision. */
+        giftWrapFeeEnabled: false,
         giftWrapFee: 49,
-        shipmentProtectionFeeEnabled: true,
+        shipmentProtectionFeeEnabled: false,
         shipmentProtectionFeePercent: 2,
         shipmentProtectionFeeMin: 30,
         saleProtectionFeeEnabled: true,
@@ -348,13 +357,22 @@ export const DEFAULT_SITE_SETTINGS_DATA = {
      * all-true map, and changing this file does NOT rewrite it — flip those in the
      * admin UI, or re-seed.
      */
+    /*
+     * TWO types, as of 2026-10-27 — buy-it-now and reserve, nothing else.
+     *
+     * 🛑 MUST STAY IDENTICAL to `siteSettingsSeedData.listings`, which says the
+     * same thing about this block. They had already drifted: `bundle` was
+     * `false` here and `true` in the seed, so a freshly seeded site shipped the
+     * featured-bundles rail and a never-configured one did not — the exact
+     * disagreement both comments exist to forbid. Change them together.
+     */
     listings: {
         listingTypes: {
             standard: true,
-            spares: true,
             "pre-order": true,
-            art: true,
-            stickers: true,
+            spares: false,
+            art: false,
+            stickers: false,
             auction: false,
             "prize-draw": false,
             classified: false,
@@ -362,9 +380,11 @@ export const DEFAULT_SITE_SETTINGS_DATA = {
             live: false,
         },
         // `bundle: false` is the admin-side switch for bundles, which are a
-        // CATEGORY type rather than a listing type — it is what hides the
-        // homepage's featured-bundles rail and the bundle tabs on category and
-        // brand pages. Same reasoning as the five listing types above.
+        // CATEGORY type rather than a listing type — it hides the homepage's
+        // featured-bundles rail and the bundle tabs on category and brand pages,
+        // and since 2026-10-27 it is also what closes `/bundles` and
+        // `/bundles/{slug}` at the edge via `closedSurfacePrefixes`. Same
+        // reasoning as the eight listing types above.
         categoryTypes: {
             category: true,
             sublisting: true,
@@ -391,6 +411,41 @@ export const DEFAULT_SITE_SETTINGS_DATA = {
             franchise: false,
             stores: false,
         },
+        /*
+         * Marketplace FEATURES withdrawn — the fourth axis, 2026-10-27.
+         *
+         * Owner: reduce a multi-seller marketplace to a plain single-vendor shop.
+         * These are the surfaces whose whole premise is the marketplace — seller
+         * onboarding, the commission schedule, the payout timetable, the scam
+         * registry, the reference tools. `closedPaths` is prefix-matched, so
+         * `/scams` takes `/scams/report` and `/scams/faqs` with it.
+         *
+         * 🛑 NOT in this list, on purpose: `/help`, `/faqs`, `/track`, `/gst`,
+         * `/credits`. They are merely no longer advertised. Closing means 404, and
+         * 404ing a support page someone has bookmarked is a regression with no
+         * upside — unlinking it from the footer is enough.
+         *
+         * 🛑 `/user/become-seller` cannot go here either: `src/proxy.ts` exempts
+         * the whole `/user` subtree from the route gate because it owns its own
+         * RBAC. Seller recruitment is withdrawn by dropping its LINKS instead —
+         * the footer allow-list and the account sidebar's Selling group.
+         */
+        closedPaths: [
+            String(ROUTES.PUBLIC.DEVELOPER),
+            String(ROUTES.PUBLIC.FEES),
+            String(ROUTES.PUBLIC.HELP_SELLER_BADGES),
+            String(ROUTES.PUBLIC.HOW_AUCTIONS_WORK),
+            String(ROUTES.PUBLIC.HOW_EMI_WORKS),
+            String(ROUTES.PUBLIC.HOW_OFFERS_WORK),
+            String(ROUTES.PUBLIC.HOW_PAYOUTS_WORK),
+            String(ROUTES.PUBLIC.ITEM_REQUESTS),
+            String(ROUTES.PUBLIC.LOTTERIES),
+            String(ROUTES.PUBLIC.PARTS),
+            String(ROUTES.PUBLIC.PROMOTIONS),
+            String(ROUTES.PUBLIC.REPORT_ENTITY),
+            String(ROUTES.PUBLIC.SCAMS),
+            String(ROUTES.PUBLIC.SELLER_GUIDE),
+        ],
     },
     shipping: {
         estimatedDays: 5,

package/dist/features/homepage/components/MarketplaceHomepageView.js

@@ -19,6 +19,9 @@ import { safeRead } from "../../../errors/safe-read.js";
 import { fetchLiveStats } from "../lib/live-stats.js";
 import { renderSection, AnnouncementBar } from "../lib/section-renderer.js";
 import { gateCarouselSlides } from "../lib/slide-gating.js";
+import { gateHomepageSections } from "../lib/section-gating.js";
+import { closedSurfaceContext, isClosedHref } from "../../../_internal/shared/listing-types/route-gating.js";
+import { getSurfaceCounts } from "../../../_internal/server/features/products/surface-counts.js";
 import { SECTION_COPY } from "../constants/section-copy.js";
 import { homepageSectionsRepository } from "../repository/homepage-sections.repository.js";
 import { isListingTypeEnabled, isCategoryTypeEnabled, isBrowsePageEnabled, } from "../../../_internal/shared/listing-types/feature-flags.js";
@@ -111,7 +114,7 @@ export async function MarketplaceHomepageView({ adSlots, newsletterFormSlot, onB
     // promotional copy for a promotion that does not exist.
     const announcementMessage = siteSettings?.announcementBar?.message?.trim() || SECTION_COPY.announcementFallback;
     const showAnnouncement = siteSettings?.announcementBar?.enabled ?? true;
-    const [allSections, rawFaqItems] = await Promise.all([
+    const [allSections, rawFaqItems, surfaceCounts] = await Promise.all([
         safeRead(() => homepageSectionsRepository.getEnabledSections(), {
             route: "/", key: "homepage.enabledSections", fallback: [],
         }),
@@ -119,7 +122,50 @@ export async function MarketplaceHomepageView({ adSlots, newsletterFormSlot, onB
         safeRead(() => getHomepageFaqsCached(), {
             route: "/", key: "homepage.faqs", fallback: [],
         }),
+        /*
+         * 🛑 The homepage did NOT read these until 2026-10-27, and that was the
+         * whole reason it kept advertising `/art` and `/spares` after both began
+         * answering a real 404: the flag for each was still `true` and only the
+         * measured count said empty. Every other surface on the site — nav,
+         * footer, sitemap, the edge gate — already ANDed the two.
+         *
+         * `getSurfaceCounts` swallows its own failures and returns `undefined`,
+         * which `isListingSurfaceVisible` reads as VISIBLE. So an unmeasured or
+         * unreadable count leaves the homepage as authored rather than stripping
+         * it (Root Cause #72) — which is also why it needs no `safeRead` wrapper.
+         */
+        getSurfaceCounts(),
     ]);
+    /*
+     * One context for every link decision on this page — the carousel slides and
+     * the section configs both consult it, so they cannot disagree about which
+     * destinations are open. Built once because the prefix list is derived work
+     * and the callers are loops over dozens of links.
+     */
+    const closedSurfaces = closedSurfaceContext(siteSettings, surfaceCounts);
+    /*
+     * 🛑 THE ANNOUNCEMENT BAR IS AUTHORED CONTENT TOO, and it is the FIRST thing
+     * on the page — so it was the worst remaining place to advertise a closed
+     * surface. Found by screenshotting the built page rather than by reading the
+     * HTML: the live bar read "… — See Events for codes" and linked `/events`,
+     * which `disabledRoutes` now closes.
+     *
+     * It survived the grep that caught everything else because the bar is
+     * CLIENT-rendered through a portal, so `/events` never appears as an `href`
+     * in the server HTML — it arrives as a prop in the RSC payload. The tell was
+     * in the browser console, not the markup: a `next/link` prefetch of
+     * `/events?_rsc=…` answering **404**.
+     *
+     * Dropping only the LINK is deliberate, and the message is left alone: the
+     * copy is the admin's, this code cannot rewrite English, and a bar that
+     * still reads "See Events for codes" with nothing to click is a smaller
+     * wrong than silently editing someone's promotional copy. The honest fix for
+     * the wording is the admin changing it — which `close-remaining-surfaces.mjs`
+     * now does for the live document.
+     */
+    const announcementLink = isClosedHref(siteSettings?.announcementBar?.link, closedSurfaces)
+        ? undefined
+        : siteSettings?.announcementBar?.link;
     // A homepage section must not advertise a listing type the site does not
     // offer. This gate previously read `featureFlags.{auctions,preOrders,events,
     // blog}`; that group was deleted on 2026-08-29, and only the listing-type
@@ -132,7 +178,7 @@ export async function MarketplaceHomepageView({ adSlots, newsletterFormSlot, onB
     // no product control for "we don't run events", and there never was one that
     // anything but this line read. Those are switched off per-document instead
     // (`enabled: false`), which is the only lever they have.
-    const enabledSections = allSections.filter((section) => {
+    const typeGatedSections = allSections.filter((section) => {
         const type = section.type;
         const gatedListing = HOMEPAGE_SECTION_LISTING_TYPE[type];
         if (gatedListing && !isListingTypeEnabled(gatedListing, siteSettings))
@@ -145,6 +191,22 @@ export async function MarketplaceHomepageView({ adSlots, newsletterFormSlot, onB
             return false;
         return true;
     });
+    /*
+     * The FOURTH gate, and the only one that can see authored content.
+     *
+     * 🛑 All three maps above are keyed on `SectionType`, so none of them can
+     * say anything about a `custom-cards` / `promo-grid` / `banner` / `welcome`
+     * section — one generic type whose only tie to a surface is where its
+     * buttons point. Measured on the live homepage 2026-10-27, that blind spot
+     * was shipping **34 links to the closed `/categories` section** and **3 each
+     * to `/art` and `/spares`, both of which already answered a real 404**, from
+     * four sections the gates above had no opinion about.
+     *
+     * Runs AFTER the type gates, not instead of them: a section the type gate
+     * already dropped must not be walked at all, and the type gates remain the
+     * right answer for a section that IS a surface.
+     */
+    const enabledSections = gateHomepageSections(typeGatedSections, closedSurfaces);
     // Collect live metric requests from all enabled stats sections
     const liveStatRequests = [];
     for (const section of enabledSections) {
@@ -278,6 +340,6 @@ export async function MarketplaceHomepageView({ adSlots, newsletterFormSlot, onB
      * type, so a keyword scan would miss the worse of the two offenders while
      * eating innocent ones. See `slide-gating.ts`.
      */
-    const carouselSlides = gateCarouselSlides(toCarouselSlides(slides), siteSettings);
-    return (_jsx(Main, { children: _jsxs(Div, { className: "relative", children: [showAnnouncement ? (_jsx(TopBannerPortal, { children: _jsx(AnnouncementBar, { message: announcementMessage, link: siteSettings?.announcementBar?.link, onDismiss: onBannerDismiss }) })) : null, orderedSections.map((section) => renderSection(section, adSlots, newsletterFormSlot ?? null, faqItems, carouselSlides, liveStats, sectionData, brand))] }) }));
+    const carouselSlides = gateCarouselSlides(toCarouselSlides(slides), closedSurfaces);
+    return (_jsx(Main, { children: _jsxs(Div, { className: "relative", children: [showAnnouncement ? (_jsx(TopBannerPortal, { children: _jsx(AnnouncementBar, { message: announcementMessage, link: announcementLink, onDismiss: onBannerDismiss }) })) : null, orderedSections.map((section) => renderSection(section, adSlots, newsletterFormSlot ?? null, faqItems, carouselSlides, liveStats, sectionData, brand))] }) }));
 }

package/dist/features/homepage/lib/section-gating.d.ts

@@ -0,0 +1,84 @@
+/**
+ * Homepage SECTION-CONFIG gating — strip authored links that point at a closed
+ * surface, and drop whatever is left with nothing to say.
+ *
+ * ## The gap this closes
+ *
+ * `MarketplaceHomepageView` has three section gates and they are all keyed on
+ * `SectionType`: `HOMEPAGE_SECTION_LISTING_TYPE`,
+ * `HOMEPAGE_SECTION_CATEGORY_TYPE`, `HOMEPAGE_SECTION_BROWSE_PAGE`. They work,
+ * and they are enough for a section that IS a surface — the auctions rail, the
+ * categories rail, the stores rail.
+ *
+ * They cannot see a `custom-cards`, `promo-grid`, `banner`, `welcome` or
+ * `collection-cards` section, because those are one generic type holding
+ * admin-authored content whose only tie to a surface is where its buttons
+ * point. `gateCarouselSlides` is the same realisation for the `carousel` type;
+ * this is the rest of the homepage.
+ *
+ * ## 🛑 Measured on the live homepage, 2026-10-27
+ *
+ * With all four browse pages closed since 2026-10-24, and `art`/`spares`
+ * auto-hidden at count 0 (both already answering a real 404 at the edge), a
+ * production fetch of `/` carried:
+ *
+ * | links | to | state |
+ * |---|---|---|
+ * | **34** | `/categories` + `/categories/{slug}` | section closed |
+ * | 3 | `/art` | **404** |
+ * | 3 | `/spares` | **404** |
+ *
+ * Three ungated sections produced all of it: `section-welcome-hero`
+ * (`secondaryCtaLink`), `section-systems-matrix` (35 category buttons across 4
+ * cards) and `section-generation-promos` (4 category banners). Plus
+ * `section-shop-extras`, whose three cards pointed at `/art`, `/spares` and
+ * `/bundles`.
+ *
+ * A rail that advertises a closed door is worse than an absent rail: the
+ * visitor spends a click to find out, and a crawler spends budget.
+ *
+ * ## The three rules, in order
+ *
+ * 1. **A closed link is removed.** Button, banner, CTA — whatever carries it.
+ * 2. **A container whose links were ALL closed is removed.** A card or banner
+ *    with its CTAs stripped is a picture with no destination; it reads as a
+ *    broken tile, not as a tidied one.
+ * 3. **A section left with no linked content is removed.** This is rule 2 one
+ *    level up, and it is what turns the systems matrix (every one of its 35
+ *    buttons closed) from "four empty cards" into "not rendered".
+ *
+ * 🛑 Rule 3 applies ONLY to sections whose content IS the links. A `welcome`
+ * hero that loses its secondary CTA keeps its heading, its copy and its
+ * primary CTA to `/products`, and must still render — dropping it would blank
+ * the top of the homepage because one of its two buttons was withdrawn. That
+ * is why `LINK_BEARING_SECTIONS` is an explicit allow-list keyed on
+ * `SectionType` rather than "any section with no links left".
+ *
+ * ## Fails OPEN throughout
+ *
+ * Every decision runs through `isClosedHref`, which classifies nothing when
+ * the settings document is missing. A transient Firestore error therefore
+ * leaves the homepage exactly as authored rather than stripping it to the
+ * studs — the same direction as every other gate on this page (Root Cause
+ * #72).
+ *
+ * @tag domain:homepage
+ * @tag layer:shared
+ * @tag access:isomorphic
+ * @tag sideEffects:none
+ */
+import { type ClosedSurfaceContext } from "../../../_internal/shared/listing-types/route-gating";
+import type { HomepageSectionDocument } from "../schemas/firestore";
+/**
+ * Strip closed destinations from one section, or return `null` to drop it.
+ *
+ * Exported for the audit and for direct use; `gateHomepageSections` is the
+ * normal entry point.
+ */
+export declare function gateHomepageSection<T extends HomepageSectionDocument>(section: T, ctx: ClosedSurfaceContext): T | null;
+/**
+ * Apply `gateHomepageSection` across an ordered section list.
+ *
+ * Returns a new array; input is not mutated.
+ */
+export declare function gateHomepageSections<T extends HomepageSectionDocument>(sections: readonly T[], ctx: ClosedSurfaceContext): T[];