@mohasinac/appkit 4.53.2 → 4.54.1

package/dist/seed/homepage-sections-seed-data.js

@@ -1,14 +1,22 @@
 /*
  * WHY: Seeds the homepage layout — which sections render, in what order, with what copy.
- * WHAT: 24 sections (23 enabled + 1 deliberately disabled), ordered 1..24 contiguously.
+ * WHAT: 26 sections (21 enabled + 5 deliberately disabled), ordered 1..26 contiguously.
+ *
+ * 🛑 Four of those five were disabled on 2026-10-20 — auctions (3),
+ * featured-bundles (9), event-raffles (13) and prize-draws (14) — each with its
+ * own note on the switch that did it. A disabled row KEEPS its order slot, so
+ * the range stays contiguous and re-enabling one puts it back where it was
+ * rather than at the end.
  * `google-reviews` is a REGISTERED type with no document — see the note
- * beside the deliberate budget-tile omission below for why. Three more joined
- * it 2026-10-19 (`how-it-works`/`testimonials`/`promo-grid`, promoted out of
- * the orphan-component set into real `SectionType`s + `SECTION_REGISTRY`
- * entries) — deliberately left unseeded too: each is now available in the
- * admin section builder's create picker, so an admin can add one when there is
- * real copy to put in it, rather than this file inventing placeholder "How It
- * Works" steps or testimonials nobody actually said.
+ * beside the deliberate budget-tile omission below for why.
+ *
+ * `how-it-works` (25) and `promo-grid` (26) were in that same unseeded set and
+ * were SEEDED 2026-10-20, on the terms the rule always allowed: there is now
+ * real copy for them. How-it-works quotes the three-tier authenticity policy
+ * the carousel already leads with; promo-grid routes to the four generation
+ * categories using the same `/media/` covers those categories use. Neither
+ * invents a claim. `testimonials` stays unseeded — the site has never had a
+ * customer, so every quote would be fabricated.
  *
  * 🛑 That count and range are ASSERTED, not described — `order` must stay unique
  * and contiguous. Until 2026-10-19 this header read "22 sections … 1..21" while
@@ -21,24 +29,33 @@
  * section type with a renderer and zero seeded rows is the same class of gap,
  * just silent rather than colliding.
  *
- * ORDER follows current marketplace-homepage research rather than the previous
- * arbitrary arrangement: hero → trust → orient (categories, systems matrix) →
- * shop (products, auctions, pre-orders, bundles) → supply (stores) → social
- * proof (reviews) → engage (events, raffles, prize draws) → editorial (blog) →
- * convert (seller banner, newsletter) → reassure (stats, security, community,
- * FAQ, brands).
+ * ORDER: hero → SHOP (products, auctions, pre-orders) → carousel → trust →
+ * orient (categories, systems matrix) → shop cont. (bundles) → supply
+ * (stores) → social proof (reviews) → engage (events, raffles, prize draws) →
+ * editorial (blog) → convert (seller banner, newsletter) → reassure (stats,
+ * security, community, FAQ, brands).
+ *
+ * 🛑 Products (2), auctions (3) and pre-orders (4) were lifted above the
+ * carousel on 2026-10-20 at the owner's request — real merchandise directly
+ * under the hero, promotions below it. That OVERRIDES the research arrangement
+ * this header used to describe (trust → orient → shop), so do not "restore"
+ * the old order on the strength of the paragraphs below; they explain the
+ * reasoning for the sections that are still in a research-driven position,
+ * not a mandate for the three that were deliberately moved. Pre-orders came
+ * up from 8 in a second pass, which is why the carousel/trust/categories/
+ * matrix block reads 5 → 8 rather than 4 → 7.
  *
- * The systems matrix sits at 5, between the generation tiles and the first
- * product rail, because that is where the measured leader puts it: on
- * worldhobbyshop "Browse Beyblade Systems & Series" (25 text links) follows
- * "Shop Beyblades by Generation" (6 image tiles) and precedes the one product
- * rail — taxonomy routing before merchandising. See
+ * The systems matrix still sits immediately after the generation tiles (7 → 8)
+ * because that is where the measured leader puts it: on worldhobbyshop
+ * "Browse Beyblade Systems & Series" (25 text links) follows "Shop Beyblades
+ * by Generation" (6 image tiles) — taxonomy routing stays together. See
  * docs/research/competitor-crawl-2026-10/layout.md.
  *
- * Baymard's finding drives the top: a static hero outperforms a carousel, and
- * the one documented carousel win came from demoting it BELOW a static hero.
- * So `welcome` is first and owns the page's single <h1>; `carousel` sits under
- * it and its slide titles render as <h2>.
+ * Baymard's finding still drives the hero: a static hero outperforms a
+ * carousel, and the one documented carousel win came from demoting it BELOW a
+ * static hero. So `welcome` is first and owns the page's single <h1>; the
+ * `carousel` is now demoted further still, under the first three product
+ * rails, and its slide titles render as <h2>.
  *
  * COPY IS CATALOGUE-NEUTRAL on purpose. "Shop by Category" stays correct
  * however the catalogue changes; "Burst & X Series" goes stale the moment it
@@ -62,7 +79,6 @@
  * @tag consumers:seed/index.ts,seed/runner.ts
  * @tag sideEffects:none
  */
-import { seedPhoto } from "./_helpers/media.js";
 import { ROUTES } from "../next/routing/route-map.js";
 const NOW = new Date();
 const daysAgo = (n) => new Date(NOW.getTime() - n * 86400000);
@@ -76,26 +92,43 @@ export const homepageSectionsSeedData = [
         order: 1,
         enabled: true,
         config: {
-            h1: "Buy, Sell & Auction Collectibles",
+            /*
+             * 🛑 NO AUCTIONS IN THE HERO, and nothing else that the site does not
+             * currently do.
+             *
+             * The h1 read "Buy, Sell & Auction Collectibles" and the second CTA sent
+             * visitors to /auctions — which `listings.listingTypes.auction: false`
+             * now switches off (2026-10-20). The first screen of the site is the
+             * worst place to advertise a type whose browse page returns nothing.
+             *
+             * The description lost "bid in live auctions" for the same reason, and
+             * "escrow-backed payments" because that claim was withdrawn from the
+             * seller guide and the Become-a-Seller copy on the same day.
+             *
+             * ⚠️ This is SEED data. The live hero is a `homepageSections` document and
+             * is NOT rewritten by editing this file — change it in the admin
+             * homepage-sections editor, or re-seed.
+             */
+            h1: "Buy & Sell Collectibles",
             subtitle: "Verified sellers, secure payments, and authenticity checks on every listing.",
-            description: "A marketplace built for collectors — browse thousands of listings, bid in live auctions, reserve upcoming releases, and buy with escrow-backed payments.",
+            description: "A marketplace built for collectors — browse thousands of listings, reserve upcoming releases, and buy with secure, verified payments.",
             showCTA: true,
             pillLabel: "Buy, sell & collect",
             ctaText: "Start Shopping",
             ctaLink: String(ROUTES.PUBLIC.PRODUCTS),
-            secondaryCtaText: "Browse Auctions",
-            secondaryCtaLink: String(ROUTES.PUBLIC.AUCTIONS),
+            secondaryCtaText: "Explore Categories",
+            secondaryCtaLink: String(ROUTES.PUBLIC.CATEGORIES),
         },
         createdAt: daysAgo(90),
         updatedAt: daysAgo(2),
     },
-    // ---- 2. Promo carousel ---------------------------------------------------
+    // ---- 5. Promo carousel ---------------------------------------------------
     // "medium" rather than "tall": it now sits UNDER a full hero, so a
     // viewport-height band would push everything else below the fold.
     {
         id: "section-hero-carousel",
         type: "carousel",
-        order: 2,
+        order: 5,
         enabled: true,
         config: {
             title: "Featured promotions",
@@ -108,13 +141,13 @@ export const homepageSectionsSeedData = [
         createdAt: daysAgo(90),
         updatedAt: daysAgo(5),
     },
-    // ---- 3. Trust bar --------------------------------------------------------
-    // Moved up from 4. Research: ~80% of attention is above the fold and the
-    // first 3–4 trust elements carry nearly all of the lift.
+    // ---- 6. Trust bar --------------------------------------------------------
+    // Research: ~80% of attention is above the fold and the first 3–4 trust
+    // elements carry nearly all of the lift.
     {
         id: "section-trust-indicators",
         type: "trust-indicators",
-        order: 3,
+        order: 6,
         enabled: true,
         config: {
             title: "Why buyers trust us",
@@ -126,10 +159,16 @@ export const homepageSectionsSeedData = [
                     description: "Every seller is verified before their first listing goes live.",
                 },
                 {
+                    // Was "Escrow-backed payments". The escrow claim was withdrawn from
+                    // the seller guide, the Become-a-Seller copy and the hero description
+                    // on 2026-10-20; a trust badge is the last place it should have
+                    // survived, because it is the claim a buyer is most likely to rely
+                    // on. The `id` is deliberately unchanged — it is this seed document's
+                    // identity, not its copy.
                     id: "trust-escrow",
                     icon: "lock",
-                    title: "Escrow-backed payments",
-                    description: "Your money is held until the item is delivered and accepted.",
+                    title: "Secure payments",
+                    description: "Your money reaches the seller after the item is delivered and accepted.",
                 },
                 {
                     id: "trust-returns",
@@ -148,12 +187,12 @@ export const homepageSectionsSeedData = [
         createdAt: daysAgo(90),
         updatedAt: daysAgo(20),
     },
-    // ---- 4. Orient: categories ----------------------------------------------
+    // ---- 7. Orient: categories ----------------------------------------------
     // Baymard's top homepage guideline, and the main internal-linking surface.
     {
         id: "section-collectibles-categories",
         type: "categories",
-        order: 4,
+        order: 7,
         enabled: true,
         config: {
             title: "Shop by Category",
@@ -173,13 +212,17 @@ export const homepageSectionsSeedData = [
         createdAt: daysAgo(90),
         updatedAt: daysAgo(10),
     },
-    // ---- 5–8. Shop -----------------------------------------------------------
+    // ---- 2–4, 9. Shop --------------------------------------------------------
+    // Products (2), auctions (3) and pre-orders (4) sit directly under the hero,
+    // ABOVE the carousel — a merchandising-first top of page, asked for
+    // 2026-10-20. Bundles (9) stay below the orientation band.
+    //
     // maxItems stays <= 12 everywhere: SSR supplies exactly 12 via
     // getFeatured*(12), so a larger cap would promise rows that cannot fill.
     {
         id: "section-featured-products",
         type: "products",
-        order: 6,
+        order: 2,
         enabled: true,
         config: {
             title: "Featured Products",
@@ -207,11 +250,24 @@ export const homepageSectionsSeedData = [
         createdAt: daysAgo(90),
         updatedAt: daysAgo(1),
     },
+    /*
+     * 🛑 DISABLED, NOT DELETED — and the `order: 3` slot is held.
+     *
+     * `listings.listingTypes.auction: false` already stops this rail rendering
+     * (HOMEPAGE_SECTION_LISTING_TYPE in MarketplaceHomepageView), so `enabled:
+     * false` is the second of two locks, not the only one. It is worth having
+     * because it is the one an ADMIN sees: a section listed as enabled in the
+     * homepage builder, silently filtered out at render, reads as a bug in the
+     * builder. Both switches say the same thing now.
+     *
+     * The copy and the "⚡ LIVE AUCTIONS" pill stay exactly as they were, so
+     * re-enabling the type and this flag restores the rail intact.
+     */
     {
         id: "section-live-auctions",
         type: "auctions",
-        order: 7,
-        enabled: true,
+        order: 3,
+        enabled: false,
         config: {
             title: "Live Auctions",
             subtitle: "Bidding open now — place yours before the timer runs out.",
@@ -228,7 +284,7 @@ export const homepageSectionsSeedData = [
     {
         id: "section-pre-orders",
         type: "pre-orders",
-        order: 8,
+        order: 4,
         enabled: true,
         config: {
             title: "Reserve Before It Ships",
@@ -243,11 +299,13 @@ export const homepageSectionsSeedData = [
         createdAt: daysAgo(90),
         updatedAt: daysAgo(3),
     },
+    // Disabled 2026-10-20 with `listings.categoryTypes.bundle: false`. Same
+    // two-lock arrangement as the auctions rail above — see that note.
     {
         id: "section-featured-bundles",
         type: "featured-bundles",
         order: 9,
-        enabled: true,
+        enabled: false,
         config: {
             title: "Curated Bundles",
             subtitle: "Multiple items, one discounted price.",
@@ -316,8 +374,18 @@ export const homepageSectionsSeedData = [
     {
         id: "section-event-raffles",
         type: "event-raffles",
+        /*
+         * 🛑 DISABLED, and here `enabled: false` is the ONLY lock there is.
+         *
+         * Raffles and spin wheels are EVENT types, not listing types and not
+         * category types, so no Site Settings toggle reaches them and
+         * `HOMEPAGE_SECTION_LISTING_TYPE` has nothing to map them to. The same gap
+         * put Lotteries, Bundles and Promotions in the footer's hand-written hidden
+         * block (src/constants/navigation.tsx) — a per-document flag is the whole
+         * mechanism for this one, which is exactly why it is spelled out.
+         */
         order: 13,
-        enabled: true,
+        enabled: false,
         config: {
             title: "Raffles & Spin Wheels",
             subtitle: "Enter for free and see if the odds are with you.",
@@ -332,8 +400,10 @@ export const homepageSectionsSeedData = [
     {
         id: "section-prize-draws",
         type: "prize-draws",
+        // Disabled 2026-10-20 with `listings.listingTypes.prize-draw: false` — the
+        // same two-lock arrangement as the auctions rail.
         order: 14,
-        enabled: true,
+        enabled: false,
         config: {
             title: "Prize Draws",
             subtitle: "Buy an entry for a shot at something rare.",
@@ -378,7 +448,13 @@ export const homepageSectionsSeedData = [
         enabled: true,
         config: {
             height: "md",
-            backgroundImage: seedPhoto("marketplace-seller-banner", 1600, 500),
+            /* Real imagery instead of a `seedPhoto()` grey tile — see the MEDIA block
+               in carousel-slides-seed-data.ts for why that helper produces one of six
+               flat SVG rectangles and why a third-party host is not the alternative.
+               🛑 A seller pitch wants a HUMAN packing an order, which the wiki corpus
+               does not contain; this generation cover is a stand-in until a real photo
+               exists for the slot. */
+            backgroundImage: "/media/category-beyblade-x-image",
             content: {
                 title: "Have collectibles to sell?",
                 subtitle: "Open a store in minutes.",
@@ -419,12 +495,40 @@ export const homepageSectionsSeedData = [
         order: 18,
         enabled: true,
         config: {
+            /*
+             * 🛑 VERIFIABLE FACTS, not volume claims.
+             *
+             * This read "200+ Listings · 8+ Verified Sellers · 35+ Buyer Reviews ·
+             * 50+ Orders Completed". Those were `source: "live"` FALLBACKS, shown
+             * whenever the metric fetch fails — and all four were falsifiable in the
+             * same breath as the page that showed them: `realListingsOnly()` in
+             * seed-cli.mjs loads on the order of a dozen products, and the site has
+             * never taken a real order, so "50+ Orders Completed" was a number about
+             * nothing. A visitor who reads it and then browses the catalogue
+             * concludes the whole page is decoration.
+             *
+             * The replacements are things a visitor can CHECK by clicking through,
+             * and each was counted from source in the change that wrote it:
+             *   - parts       `PART_LEAF_COUNT` (_helpers/category-parts.ts:17528) = 2490.
+             *                 🛑 CLAUDE.md says 752; that is stale, the corpus grew.
+             *   - generations 4 tier-1 rows under `category-spinning-tops`.
+             *   - brands      28 `BRAND_SEED_INPUTS` entries (`BRAND_ROW_COUNT`).
+             * Re-count before editing any of them rather than trusting this comment.
+             *
+             * `total_listings` stays LIVE and keeps a `"0"` fallback: a live number is
+             * verifiable by definition, and a zero fallback can only ever understate.
+             * `total_orders` and `total_reviews` are dropped rather than zeroed — a
+             * giant "0" in 48pt type is worse than not raising the subject.
+             *
+             * `iconName` is required on a static stat; a live one derives its glyph
+             * from `metric` via STAT_PRESET_ICON.
+             */
             title: "By the numbers",
             stats: [
-                { key: "products", label: "Listings", value: "200", source: "live", metric: "total_listings", suffix: "+" },
-                { key: "sellers", label: "Verified Sellers", value: "8", source: "live", metric: "verified_sellers", suffix: "+" },
-                { key: "reviews", label: "Buyer Reviews", value: "35", source: "live", metric: "total_reviews", suffix: "+" },
-                { key: "orders", label: "Orders Completed", value: "50", source: "live", metric: "total_orders", suffix: "+" },
+                { key: "products", label: "Listings", value: "0", source: "live", metric: "total_listings", suffix: "+" },
+                { key: "parts", label: "Parts catalogued", value: "2,490", source: "static", iconName: "spares" },
+                { key: "generations", label: "Generations covered", value: "4", source: "static", iconName: "archive" },
+                { key: "brands", label: "Brands", value: "28", source: "static", iconName: "deals" },
             ],
         },
         createdAt: daysAgo(90),
@@ -474,8 +578,17 @@ export const homepageSectionsSeedData = [
         config: {
             title: "Join the community",
             description: "Deal alerts, auction reminders, and early access to drops.",
-            // Keep this link verbatim — a tester-checklist case asserts it.
-            groupLink: "https://chat.whatsapp.com/",
+            /* 🛑 The line that used to sit here — "Keep this link verbatim — a
+               tester-checklist case asserts it" — was FALSE and is deleted. Verified:
+               zero hits for `chat.whatsapp.com` anywhere under
+               `appkit/src/features/tester/seed-data/`. It had also outlived its
+               subject: the value it was protecting (a bare `https://chat.whatsapp.com/`
+               with no invite code) is gone, so the comment defended a string that no
+               longer existed while discouraging anyone from touching the field. */
+            // Left unset: a bare chat.whatsapp.com URL is not a valid invite code and
+            // opens a page that resolves to no group. The real link is env-owned
+            // (WHATSAPP_GROUP_INVITE) and reaches the card through appkit.config.
+            groupLink: undefined,
             benefits: [
                 "Deal alerts before they hit the homepage",
                 "Reminders when auctions you watch are closing",
@@ -635,7 +748,7 @@ export const homepageSectionsSeedData = [
     {
         id: "section-systems-matrix",
         type: "custom-cards",
-        order: 5,
+        order: 8,
         enabled: true,
         config: {
             title: "Every system, every part family",
@@ -746,6 +859,125 @@ export const homepageSectionsSeedData = [
         createdAt: daysAgo(1),
         updatedAt: daysAgo(1),
     },
+    /*
+     * ---- 25. How it works ----------------------------------------------------
+     *
+     * `how-it-works` and `promo-grid` (26) were registered types with renderers,
+     * admin create-picker entries and ZERO seeded rows — so both returned `null`
+     * and the page was missing the two blocks a 2026 marketplace homepage most
+     * obviously has. They were left unseeded on the principle that this file must
+     * not invent placeholder content, which was the right call: the reason they
+     * can be seeded NOW is that there is real, checkable copy to put in them.
+     *
+     * 🛑 Every step below is a claim the site actually honours. No "ships in 24
+     * hours", no "100% buyer protection" — the authenticity labelling in step 2
+     * is the one genuine differentiator the carousel already leads with, quoted
+     * from the same policy.
+     *
+     * 🛑 NO BIDDING STEP. `listings.listingTypes.auction` is false, so a step
+     * telling visitors to place a bid would route them to a browse page with
+     * nothing in it.
+     *
+     * 🛑 PLACEMENT IS PROVISIONAL. Appended at 25/26 rather than inserted mid-page
+     * (how-it-works belongs nearer the top, after the trust bar) because the
+     * section order is being tuned with the owner in a parallel change and
+     * renumbering 24 rows underneath that would collide. Reposition from
+     * /admin/sections, which is cheaper than a reseed.
+     */
+    {
+        id: "section-how-it-works",
+        type: "how-it-works",
+        order: 25,
+        enabled: true,
+        config: {
+            title: "How buying here works",
+            subtitle: "Three steps, and the second one is the part other marketplaces skip.",
+            pillLabel: "New here?",
+            ctaLabel: "Browse the catalogue →",
+            ctaLink: String(ROUTES.PUBLIC.PRODUCTS),
+            steps: [
+                {
+                    number: 1,
+                    iconKey: "search",
+                    title: "Find the piece",
+                    desc: "Filter by generation, part family, condition and price across every seller on the marketplace.",
+                },
+                {
+                    number: 2,
+                    iconKey: "verify",
+                    title: "Read the authenticity label",
+                    desc: "Every listing carries one of three labels — original, reproduction or unverified. If a seller does not say which, it reads “unverified”; we will not claim “original” on their behalf.",
+                },
+                {
+                    number: 3,
+                    iconKey: "lock",
+                    title: "Buy with the seller verified",
+                    desc: "Identity and payout details are checked before a store can publish, and your address and phone number are encrypted at rest.",
+                },
+            ],
+        },
+        createdAt: daysAgo(1),
+        updatedAt: daysAgo(1),
+    },
+    /*
+     * ---- 26. Promo grid ------------------------------------------------------
+     *
+     * The always-dark 4-tile editorial mosaic: one large slot plus three, each a
+     * full-bleed image under a bottom-up scrim. Routes to the four generations,
+     * which is the one set of destinations guaranteed to be populated however the
+     * product catalogue changes — a promo tile pointing at an empty page is worse
+     * than no tile.
+     *
+     * 🛑 `image` is a `/media/<shortId>` slug backed by a real `mediaAssets` row,
+     * never `seedPhoto()` (six flat grey tiles) and never a third-party host
+     * (Root Cause #104). These four covers are the same ones the generation
+     * categories use, so they are known-present.
+     *
+     * 🛑 The component caps at `PROMO_GRID_MAX_BANNERS` (4) and silently drops a
+     * fifth — the layout has exactly one hero slot and three regular ones.
+     */
+    {
+        id: "section-generation-promos",
+        type: "promo-grid",
+        order: 26,
+        enabled: true,
+        config: {
+            eyebrow: "FOUR GENERATIONS",
+            heading: "Pick your era",
+            banners: [
+                {
+                    id: "promo-beyblade-x",
+                    title: "Beyblade X",
+                    ctaLabel: "Shop Beyblade X",
+                    ctaUrl: "/categories/category-beyblade-x",
+                    image: "/media/category-beyblade-x-image",
+                },
+                {
+                    id: "promo-beyblade-burst",
+                    title: "Burst",
+                    ctaLabel: "Shop Burst",
+                    ctaUrl: "/categories/category-beyblade-burst",
+                    image: "/media/category-beyblade-burst-image",
+                },
+                {
+                    id: "promo-beyblade-metal",
+                    title: "Metal Fight",
+                    ctaLabel: "Shop Metal Fight",
+                    ctaUrl: "/categories/category-beyblade-metal",
+                    image: "/media/category-beyblade-metal-image",
+                },
+                {
+                    id: "promo-beyblade-original",
+                    title: "The Originals",
+                    ctaLabel: "Shop the originals",
+                    ctaUrl: "/categories/category-beyblade-original",
+                    image: "/media/category-beyblade-original-image",
+                },
+            ],
+        },
+        createdAt: daysAgo(1),
+        updatedAt: daysAgo(1),
+    },
     /*
      * 🛑 `google-reviews` stays DELIBERATELY UNSEEDED — not an oversight, the
      * same decision already made for `googleMapsApiKey`/`googlePlaceId` in

package/dist/seed/index.d.ts

@@ -86,7 +86,7 @@ export { productFeaturesSeedData } from "./product-features-seed-data";
 export { authenticityKnowledgeSeedData, AUTHENTICITY_KNOWLEDGE_COLLECTION, AUTHENTICITY_KNOWLEDGE_COUNT, } from "./authenticity-knowledge-seed-data";
 export { taxCodesSeedData } from "./tax-codes-seed-data";
 export { offersSeedData } from "./offers-seed-data";
-export { payoutMethodsSeedData, shippingConfigsSeedData, analyticsCardsSeedData, analyticsAlertsSeedData, storeCategoriesSeedData, listingTemplatesSeedData, moderationQueueSeedData, reportsSeedData, itemRequestsSeedData, storeWhatsAppConfigSeedData, storeGoogleConfigSeedData, } from "./store-extensions-seed-data";
+export { payoutMethodsSeedData, shippingConfigsSeedData, analyticsCardsSeedData, analyticsAlertsSeedData, storeCategoriesSeedData, listingTemplatesSeedData, moderationQueueSeedData, reportsSeedData, itemRequestsSeedData, storeGoogleConfigSeedData, } from "./store-extensions-seed-data";
 export type { SeedManifest, SeedManifestEntry, SeedCollectionName } from "./manifest";
 export { SEED_MANIFEST } from "./manifest";
 export type { FirestoreIndexConfig } from "./firestore-indexes";

package/dist/seed/index.js

@@ -95,7 +95,7 @@ export { authenticityKnowledgeSeedData, AUTHENTICITY_KNOWLEDGE_COLLECTION, AUTHE
 export { taxCodesSeedData } from "./tax-codes-seed-data.js";
 export { offersSeedData } from "./offers-seed-data.js";
 // S-STORE Extensions (Tier S-STORE) — 11 new collections
-export { payoutMethodsSeedData, shippingConfigsSeedData, analyticsCardsSeedData, analyticsAlertsSeedData, storeCategoriesSeedData, listingTemplatesSeedData, moderationQueueSeedData, reportsSeedData, itemRequestsSeedData, storeWhatsAppConfigSeedData, storeGoogleConfigSeedData, } from "./store-extensions-seed-data.js";
+export { payoutMethodsSeedData, shippingConfigsSeedData, analyticsCardsSeedData, analyticsAlertsSeedData, storeCategoriesSeedData, listingTemplatesSeedData, moderationQueueSeedData, reportsSeedData, itemRequestsSeedData, storeGoogleConfigSeedData, } from "./store-extensions-seed-data.js";
 export { SEED_MANIFEST } from "./manifest.js";
 export { mergeFirestoreIndices, generateMergedFirestoreIndexFile, } from "./firestore-indexes.js";
 // Test utilities (Firestore emulator + PII assertion)

package/dist/seed/manifest.d.ts

@@ -11,6 +11,6 @@ export interface SeedManifestEntry {
     type?: string;
 }
 /** Every collection name the CLI seeder (appkit/scripts/seed-cli.mjs) and this manifest cover. */
-export type SeedCollectionName = "users" | "addresses" | "categories" | "stores" | "products" | "orders" | "reviews" | "bids" | "coupons" | "carousels" | "carouselSlides" | "homepageSections" | "siteSettings" | "faqs" | "notifications" | "payouts" | "blogPosts" | "events" | "eventEntries" | "sessions" | "carts" | "wishlists" | "history" | "groupedListings" | "scammerProfiles" | "supportTickets" | "productFeatures" | "taxCodes" | "offers" | "couponUsage" | "claimedCoupons" | "payoutMethods" | "shippingConfigs" | "analyticsCards" | "analyticsAlerts" | "storeCategories" | "listingTemplates" | "moderationQueue" | "reports" | "itemRequests" | "storeWhatsAppConfig" | "storeGoogleConfig" | "roleOverrides" | "customRoles" | "adminNotifications" | "lotteryEntries" | "shipments" | "shipmentLots" | "shipmentItems" | "catalogueItems" | "testerChecklistItems";
+export type SeedCollectionName = "users" | "addresses" | "categories" | "stores" | "products" | "orders" | "reviews" | "bids" | "coupons" | "carousels" | "carouselSlides" | "homepageSections" | "siteSettings" | "faqs" | "notifications" | "payouts" | "blogPosts" | "events" | "eventEntries" | "sessions" | "carts" | "wishlists" | "history" | "groupedListings" | "scammerProfiles" | "supportTickets" | "productFeatures" | "taxCodes" | "offers" | "couponUsage" | "claimedCoupons" | "payoutMethods" | "shippingConfigs" | "analyticsCards" | "analyticsAlerts" | "storeCategories" | "listingTemplates" | "moderationQueue" | "reports" | "itemRequests" | "storeGoogleConfig" | "roleOverrides" | "customRoles" | "adminNotifications" | "lotteryEntries" | "shipments" | "shipmentLots" | "shipmentItems" | "catalogueItems" | "testerChecklistItems";
 export type SeedManifest = Record<SeedCollectionName, SeedManifestEntry[]>;
 export declare const SEED_MANIFEST: SeedManifest;

package/dist/seed/manifest.js

@@ -5,7 +5,7 @@
  * name/id pairs without loading the full seed data payload.
  * Auto-derived from the live seed data files — stays in sync automatically.
  */
-import { payoutMethodsSeedData, shippingConfigsSeedData, analyticsCardsSeedData, analyticsAlertsSeedData, storeCategoriesSeedData, listingTemplatesSeedData, moderationQueueSeedData, reportsSeedData, itemRequestsSeedData, storeWhatsAppConfigSeedData, storeGoogleConfigSeedData, } from "./store-extensions-seed-data.js";
+import { payoutMethodsSeedData, shippingConfigsSeedData, analyticsCardsSeedData, analyticsAlertsSeedData, storeCategoriesSeedData, listingTemplatesSeedData, moderationQueueSeedData, reportsSeedData, itemRequestsSeedData, storeGoogleConfigSeedData, } from "./store-extensions-seed-data.js";
 // SB-UNI-C — brandsSeedData merged into categoriesSeedData.
 import { categoriesSeedData } from "./categories-seed-data.js";
 import { usersSeedData } from "./users-seed-data.js";
@@ -223,7 +223,6 @@ export const SEED_MANIFEST = {
     moderationQueue: pick(asArr(moderationQueueSeedData)),
     reports: pick(asArr(reportsSeedData)),
     itemRequests: pick(asArr(itemRequestsSeedData).map((r) => ({ ...r, name: r.title ?? r.id }))),
-    storeWhatsAppConfig: pick(asArr(storeWhatsAppConfigSeedData)),
     storeGoogleConfig: pick(asArr(storeGoogleConfigSeedData)),
     // RBAC + admin notifications — no seed docs yet; manifest stays empty until populated.
     roleOverrides: [],

package/dist/seed/model-composition-seed-data.js

@@ -2493,7 +2493,7 @@ export const modelCompositionSeedData = [
                 "slotKey": "blade-base",
                 "slotLabel": "BLADE BASE (BB)",
                 "partName": "Metal Sharp Base",
-                "partId": "blade-base--metal-sharp-base"
+                "partId": "blade-base--blade-base"
             }
         ],
         "source": "gen1/plastic/flash-leopard-2.md",
@@ -6587,14 +6587,12 @@ export const modelCompositionSeedData = [
             {
                 "slotKey": "disc",
                 "slotLabel": "FORGE DISC",
-                "partName": "variable per combo",
-                "partId": "disc--variable-per-combo"
+                "partName": "variable per combo"
             },
             {
                 "slotKey": "performance-tip",
                 "slotLabel": "PERFORMANCE TIP",
-                "partName": "variable per combo",
-                "partId": "performance-tip--variable-per-combo"
+                "partName": "variable per combo"
             }
         ],
         "source": "gen3/bu/draciel-fortress.md",
@@ -7415,7 +7413,7 @@ export const modelCompositionSeedData = [
                 "slotKey": "driver",
                 "slotLabel": "DRIVER",
                 "partName": "Destroy'",
-                "partId": "driver--destroy-dash"
+                "partId": "driver--destroy"
             }
         ],
         "source": "gen3/db/rage-longinus-s5.md"
@@ -7925,7 +7923,7 @@ export const modelCompositionSeedData = [
                 "slotKey": "driver",
                 "slotLabel": "PERFORMANCE DRIVER",
                 "partName": "Evolution'",
-                "partId": "driver--evolution-dash"
+                "partId": "driver--evolution"
             }
         ],
         "source": "gen3/superking/brave-valtryek.md"
@@ -7972,7 +7970,7 @@ export const modelCompositionSeedData = [
                 "slotKey": "driver",
                 "slotLabel": "DRIVER",
                 "partName": "Destroy'",
-                "partId": "driver--destroy-dash"
+                "partId": "driver--destroy"
             }
         ],
         "source": "gen3/superking/rage-longinus-d3a.md"

package/dist/seed/part-glossary/chunk0.d.ts

@@ -0,0 +1,9 @@
+/**
+ * GENERATED by `scripts/generate-parts-seed.mjs` — do not hand-edit.
+ *
+ * Chunk 0 of the part glossary. See `../part-glossary-seed-data.ts` for
+ * provenance and for why the chunks are separate FILES rather than separate
+ * consts in one file.
+ */
+import type { PartGlossaryDocument } from "../../features/parts/schemas/firestore";
+export declare const glossaryChunk0: Partial<PartGlossaryDocument>[];