@mohasinac/appkit 4.45.0 → 4.46.0

package/dist/seed/carousel-slides-seed-data.js

@@ -194,8 +194,46 @@ const _rawSlides = [
         updatedAt: daysAgo(3),
     },
     {
+        /*
+         * ── G1c — THE AUTHENTICITY SLIDE ────────────────────────────────────────
+         *
+         * 🛑 This slide's id has said `authenticated-originals` since it was
+         * written and its copy said "Turn your collection into income" — a
+         * seller-acquisition message under an authenticity name. So authenticity,
+         * which is this marketplace's actual differentiator, had NO hero surface
+         * at all while the id implied it did.
+         *
+         * It is the one hero message the crawl independently validates three ways:
+         * beybladeartshop runs it as their slide 5 ("100% original Takara Tomy
+         * Beyblades. Don't fall for cheap imitations!"); worldhobbyshop — the SEO
+         * leader of the fifteen — ships a top-level "MidFake Beyblades" category
+         * and an FAQ promising that midfake and reproduction stock is kept
+         * separate with authenticity disclosed; and we already have the feature
+         * (`ProductAuthenticity` is a REQUIRED field with a badge and four FAQ
+         * rows) with nowhere on the homepage that says so.
+         *
+         * 🛑 THE COPY ANSWERS "AFTERMARKET", NOT "FAKE", and that is the finding
+         * that matters. The counterfeit seller measured in section 3.7 makes **zero**
+         * authenticity claims across 1,277 listings — no "original", no "replica",
+         * no "fake" — and sells itself as "a popular brand" offering "custom parts
+         * or upgraded components", "like many other aftermarket brands". So
+         * "aftermarket" and "custom" are the words our buyers will actually be
+         * sold, and a slide that only rebuts the word "fake" rebuts nothing they
+         * will hear.
+         *
+         * It also states the three-tier vocabulary rather than a binary, because
+         * the tiers are the honest part: a reproduction IS sellable when labelled,
+         * and claiming everything is original would be the same unfalsifiable
+         * promise the counterfeiter makes in reverse.
+         *
+         * 🛑 Seller acquisition is NOT lost — it keeps its own `banner` section
+         * ("Have collectibles to sell?" → "Start selling →"), the `features` and
+         * `stats` sections, and two nav entries. Verified before this was changed.
+         * `MAX_ACTIVE_SLIDES` is 5 and all five were taken, so this is a swap
+         * rather than an addition.
+         */
         id: "slide-authenticated-originals",
-        title: "Sell on the marketplace",
+        title: "Original, reproduction, or unverified — every listing says which",
         order: 5,
         active: true,
         background: {
@@ -205,18 +243,53 @@ const _rawSlides = [
         },
         overlay: {
             enabled: true,
-            subtitle: "For sellers",
-            title: "Turn your collection into income",
-            description: "Open a store in minutes, list for free, and get paid on a predictable schedule.",
+            subtitle: "Authenticity, stated",
+            // 🛑 "We make sellers say which" was the same overclaim as the body —
+            // the field is optional, so nobody is MADE to. What is true is that
+            // every listing carries a label, which is the verifiable version.
+            title: "“Aftermarket” is not a brand. Every listing says which.",
+            /*
+             * 🛑 THE CLAIM WAS FALSE WHEN FIRST WRITTEN, and the check is the point.
+             *
+             * It read "the seller has to pick one before it can go live" — and
+             * `authenticity` is `.optional()` in the write schema while being ABSENT
+             * on all 71 live products. A hero promise nobody could keep, on the one
+             * subject where this marketplace's credibility rests.
+             *
+             * Both halves were fixed before the copy was: the root default now makes
+             * 381/381 listing nodes resolve a value, and `withDerivedCategoryFields`
+             * stamps it on every seeded product (measured after loading:
+             * `original=4`, `unverified=67`, zero absent).
+             *
+             * The copy still says what is TRUE rather than what would be strongest.
+             * A seller may still omit the field — the category then decides, and it
+             * decides `unverified`, never `original`. So the promise is "every
+             * listing carries a label and we never silently claim original", which
+             * is both accurate and the more useful thing to say.
+             */
+            description: "Every listing carries one of three labels — original, reproduction or unverified. A seller can say which; if they do not, it reads “unverified”, because we will not claim “original” on your behalf. Reproductions are welcome here when they are labelled; a listing that leaves you guessing is not.",
             button: {
-                id: "slide-sell-cta",
-                text: "Start selling",
-                link: String(ROUTES.PUBLIC.SELLER_GUIDE),
+                id: "slide-authenticity-cta",
+                text: "How to spot a fake",
+                /*
+                 * 🛑 `/faqs/product_information`, the CATEGORY — not a question slug.
+                 * The route is `/faqs/[category]` and it matches on
+                 * `CATEGORY_KEYS.includes(category)`, so `/faqs/faq-how-to-spot-a-fake`
+                 * would silently fall back to "all" and land the reader on the full
+                 * index instead of the answer. Verified against the route before
+                 * writing it, because the FAQ documents DO carry a `seo.slug` of
+                 * exactly that shape, which makes the wrong link the obvious one.
+                 *
+                 * This category holds both authenticity answers — "How do I spot a fake
+                 * Beyblade?" and "What is a reproduction or midfake? Is it a fake?" —
+                 * which is the pair the slide's claim rests on.
+                 */
+                link: "/faqs/product_information",
                 variant: "primary",
                 openInNewTab: false,
             },
         },
-        link: { url: String(ROUTES.PUBLIC.SELLER_GUIDE), openInNewTab: false },
+        link: { url: "/faqs/product_information", openInNewTab: false },
         settings: SLIDE_SETTINGS,
         createdBy: "user-admin-letitrip",
         createdAt: daysAgo(40),

package/dist/seed/categories-seed-data.js

@@ -57,6 +57,7 @@ import { withCategorySearchTxt } from "./_helpers/search-txt-wrappers.js";
 import { CATEGORY_FOREST } from "./_helpers/category-forest.js";
 import { BRAND_ROW_COUNT, buildBrandRows } from "./_helpers/brand-rows.js";
 import { MODEL_LEAF_COUNT } from "./_helpers/category-models.js";
+import { PART_LEAF_COUNT } from "./_helpers/category-parts.js";
 import { MARKET_BAND_LEAF_IDS } from "./_helpers/category-content.js";
 import { productsStandardSeedData } from "./products-standard-seed-data.js";
 const NOW = new Date();
@@ -461,12 +462,49 @@ const allCategoryRows = [
  * (the seed CLI, the tester fixtures, the audits) wants to fail before writing
  * rather than after.
  */
-const modelLeafRows = rawCategories.filter((c) => c.tier === 4).length;
-if (modelLeafRows !== MODEL_LEAF_COUNT) {
-    throw new Error(`category seed: ${modelLeafRows} tier-4 model leaves reached the tree but ` +
-        `category-models.ts generated ${MODEL_LEAF_COUNT}. A line id in the ` +
-        `forest no longer matches a key in MODEL_LEAVES — re-run ` +
-        `node scripts/gen-category-models.mjs and check the line ids.`);
+/*
+ * 🛑 TIER 4 IS NOW TWO GENERATED FAMILIES, not one.
+ *
+ * This assertion compared the tier-4 count against `MODEL_LEAF_COUNT` alone,
+ * and it CAUGHT the part leaves the moment they landed — 968 against an
+ * expected 216 — which is precisely the job it was written for. Widening it to
+ * the sum is the fix; deleting it or loosening it to `>=` would retire the one
+ * check that can see a generated map silently empty.
+ *
+ * Kept as an exact equality for the same reason: a `>=` would pass with
+ * `PART_LEAVES` entirely gone.
+ */
+/*
+ * 🛑 DISTINCT IDS. This assertion did not exist, and its absence is what let 20
+ * part leaves overwrite 20 model leaves in production.
+ *
+ * The whole failure was silent at every layer: the forest walked 1,138 nodes
+ * with only 1,118 distinct ids, `appkit-seed load` is a `set(…, {merge:true})`
+ * so the second row with an id quietly replaced the first, and the CLI reported
+ * `created 1173, errors 0` while Firestore held 1,153 documents. A buyer opening
+ * `/categories/category-galeon` got the attack ring instead of the bey.
+ *
+ * Counting rows is not counting documents, and this is the one check that can
+ * tell the difference BEFORE anything is written.
+ */
+const allIds = allCategoryRows.map((c) => c.id).filter((x) => typeof x === "string");
+const duplicateIds = [...new Set(allIds.filter((id, i) => allIds.indexOf(id) !== i))];
+if (duplicateIds.length > 0) {
+    throw new Error(`category seed: ${duplicateIds.length} duplicate id(s) — a merge write would ` +
+        `silently overwrite, so the load would report success and lose rows. ` +
+        `First few: ${duplicateIds.slice(0, 8).join(", ")}`);
+}
+if (allIds.length !== allCategoryRows.length) {
+    throw new Error(`category seed: ${allCategoryRows.length - allIds.length} row(s) have no string id`);
+}
+const tier4Rows = rawCategories.filter((c) => c.tier === 4).length;
+const expectedTier4 = MODEL_LEAF_COUNT + PART_LEAF_COUNT;
+if (tier4Rows !== expectedTier4) {
+    throw new Error(`category seed: ${tier4Rows} tier-4 leaves reached the tree but the generated ` +
+        `maps declare ${expectedTier4} (${MODEL_LEAF_COUNT} models + ${PART_LEAF_COUNT} parts). ` +
+        `A parent id in the forest no longer matches a key in MODEL_LEAVES or PART_LEAVES — ` +
+        `re-run node scripts/gen-category-models.mjs and node scripts/gen-category-parts.mjs ` +
+        `and check the parent ids.`);
 }
 if (brandRows.length !== BRAND_ROW_COUNT) {
     throw new Error(`category seed: ${brandRows.length} brand rows built, expected ${BRAND_ROW_COUNT}`);

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

@@ -446,20 +446,62 @@ export const homepageSectionsSeedData = [
             title: "Frequently Asked Questions",
             subtitle: "The questions new buyers ask most.",
             showOnHomepage: true,
-            displayCount: 6,
+            /*
+             * B6b — 6 → 10. The FAQ block is the densest single SEO win on the page
+             * (worldhobbyshop's 10-question block is a measured part of why it leads
+             * the fifteen on SEO) and it is an answer-engine surface, so it feeds
+             * `faqJsonLd`. 20 rows are flagged `showOnHomepage`; showing 10 of them
+             * is the intended shape.
+             */
+            displayCount: 10,
             linkToFullPage: true,
             viewMoreLabel: "View all FAQs →",
             showCategoryTabs: true,
-            visibleTabs: ["shipping_delivery", "returns_refunds", "orders_payment"],
+            /*
+             * 🛑 EMPTY ON PURPOSE — the tabs DERIVE from the items actually shown.
+             *
+             * This listed `["shipping_delivery", "returns_refunds",
+             * "orders_payment"]` and measured live on 2026-10-12 **all three
+             * rendered EMPTY PANELS**, while the three categories whose rows were
+             * actually displayed (`general`, `product_information`,
+             * `fees_and_taxes`) had no tab at all.
+             *
+             * The cause is that the two halves answer different questions and
+             * neither knows about the other: the ITEMS come from
+             * `getHomepageFAQs()` — `showOnHomepage` ordered by `priority` DESC,
+             * then sliced to `displayCount` — while the TABS were a hand-written
+             * list. Raise a row's priority, or add a higher-priority row in another
+             * category (B6b's FAQ half added 22, including a whole new
+             * `fees_and_taxes`), and the slice moves out from under the tabs
+             * silently. That is Root Cause #72's shape: a tab you can click with
+             * nothing behind it.
+             *
+             * `FAQSection` already derives tabs from its items when `tabs` is empty
+             * (`if (tabsProp && tabsProp.length > 0) return tabsProp;`), so an empty
+             * array makes an empty tab STRUCTURALLY IMPOSSIBLE rather than something
+             * to re-sync by hand. A hand-maintained enumeration beside a query is
+             * the defect, not the list's contents.
+             *
+             * 🛑 `[]` rather than deleting the key, because `appkit-seed load` is a
+             * MERGE write and cannot remove a field — dropping it from the seed
+             * would leave the three stale values in Firestore forever and the fix
+             * would read as applied while changing nothing.
+             */
+            visibleTabs: [],
             allowMultipleOpen: false,
             defaultOpenCount: 1,
-            categories: [
-                "general",
-                "orders_payment",
-                "shipping_delivery",
-                "returns_refunds",
-                "product_information",
-            ],
+            /*
+             * 🛑 NOT a filter, despite the name. The renderer uses this ONLY as a
+             * fallback tab list when `visibleTabs` is empty
+             * (`cfg?.visibleTabs?.length ? cfg.visibleTabs : cfg?.categories`), and
+             * the items are never filtered by it. So a category absent from here is
+             * still displayed — which is why `fees_and_taxes` rows appear on the
+             * homepage today while being absent from this list.
+             *
+             * Emptied too, or it would simply become the hand-written tab list this
+             * change exists to delete.
+             */
+            categories: [],
         },
         createdAt: daysAgo(90),
         updatedAt: daysAgo(16),
@@ -517,4 +559,123 @@ export const homepageSectionsSeedData = [
      * array does not remove them from Firestore — delete both documents at
      * /admin/sections after seeding, or they keep rendering.
      */
+    /*
+     * ── B6b — THE SYSTEMS MATRIX ─────────────────────────────────────────────
+     *
+     * worldhobbyshop's single biggest SEO asset, and it is TAXONOMY ROUTING
+     * rather than merchandising: 25 internal links telling a crawler which
+     * sub-collections exist. It is most of why they have 79 unique internal
+     * links (BAS has 57) while running the FEWEST products and words on their
+     * homepage of the fifteen crawled — 8 product cards and 1,816 words.
+     *
+     * 🛑 `custom-cards`, NOT `collection-cards`, and the plan had this wrong.
+     * `collection-cards` is capped at `COLLECTION_CARDS_MAX_ENTRIES = 3` and its
+     * entries are LIVE-CONTENT queries (`{type, limit, categorySlug}`), so it
+     * cannot express a link matrix at all. `custom-cards` carries
+     * `cards[].buttons[]` of `{label, href}`, which is exactly a matrix.
+     *
+     * 🛑 Every href is a REAL post-B5 category id, read off `categoriesSeedData`
+     * rather than typed from memory. A dead link here is the Root Cause #33
+     * shape on the routing axis — it 404s, and `audit-nav-page-wiring` does not
+     * reach section configs.
+     *
+     * No prices anywhere, which is what makes this safe where a price-band tile
+     * is not — see the note below the array.
+     */
+    {
+        id: "section-systems-matrix",
+        type: "custom-cards",
+        order: 5,
+        enabled: true,
+        config: {
+            title: "Every system, every part family",
+            layout: "grid",
+            columns: 4,
+            autoScroll: false,
+            loop: false,
+            cards: [
+                {
+                    id: "matrix-original",
+                    eyebrow: "1999–2003",
+                    title: "Beyblade Original",
+                    body: "Four part systems in four years, and they do not interchange. Plastic Generation through Heavy Metal System.",
+                    buttons: [
+                        { label: "Plastic Generation", href: "/categories/category-original-plastic-gen", variant: "ghost" },
+                        { label: "Spin Gear", href: "/categories/category-original-spin-gear", variant: "ghost" },
+                        { label: "Magnacore", href: "/categories/category-original-magnacore", variant: "ghost" },
+                        { label: "Engine Gear", href: "/categories/category-original-engine-gear", variant: "ghost" },
+                        { label: "Heavy Metal System", href: "/categories/category-original-hms", variant: "ghost" },
+                        { label: "Parts", href: "/categories/category-original-parts", variant: "outline" },
+                        { label: "Launchers", href: "/categories/category-original-launchers", variant: "outline" },
+                    ],
+                },
+                {
+                    id: "matrix-metal",
+                    eyebrow: "2008–2013",
+                    title: "Metal Fight",
+                    body: "The tuning era, and the only generation where loose parts outnumber complete tops.",
+                    buttons: [
+                        { label: "Metal System", href: "/categories/category-metal-phws", variant: "ghost" },
+                        { label: "Metal Fusion", href: "/categories/category-metal-fusion", variant: "ghost" },
+                        { label: "Metal Masters", href: "/categories/category-metal-masters", variant: "ghost" },
+                        { label: "Metal Fury (4D)", href: "/categories/category-metal-fury-4d", variant: "ghost" },
+                        { label: "Shogun Steel", href: "/categories/category-metal-shogun-steel", variant: "ghost" },
+                        { label: "Parts", href: "/categories/category-metal-parts", variant: "outline" },
+                        { label: "Launchers", href: "/categories/category-metal-launchers", variant: "outline" },
+                    ],
+                },
+                {
+                    id: "matrix-burst",
+                    eyebrow: "2015–2023",
+                    title: "Beyblade Burst",
+                    body: "Seven waves of the bursting mechanic, from single-layer Classic to Burst Ultimate.",
+                    buttons: [
+                        { label: "Burst Classic", href: "/categories/category-burst-classic", variant: "ghost" },
+                        { label: "Burst God", href: "/categories/category-burst-god", variant: "ghost" },
+                        { label: "Cho-Z", href: "/categories/category-burst-cho-z", variant: "ghost" },
+                        { label: "GT", href: "/categories/category-burst-gt", variant: "ghost" },
+                        { label: "Superking", href: "/categories/category-burst-superking", variant: "ghost" },
+                        { label: "Dynamite Battle", href: "/categories/category-burst-db", variant: "ghost" },
+                        { label: "Burst Ultimate", href: "/categories/category-burst-bu", variant: "ghost" },
+                        { label: "Parts", href: "/categories/category-burst-parts", variant: "outline" },
+                    ],
+                },
+                {
+                    id: "matrix-x",
+                    eyebrow: "2023–",
+                    title: "Beyblade X",
+                    body: "The Xtreme Line rail is the centre of the design — blades, ratchets and bits, and a stadium that is part of the game.",
+                    buttons: [
+                        { label: "Basic Line", href: "/categories/category-x-basic", variant: "ghost" },
+                        { label: "Unique Line (UX)", href: "/categories/category-x-unique-ux", variant: "ghost" },
+                        { label: "Custom Line (CX)", href: "/categories/category-x-custom-cx", variant: "ghost" },
+                        { label: "X-Over Project", href: "/categories/category-x-over", variant: "ghost" },
+                        { label: "Parts", href: "/categories/category-x-parts", variant: "outline" },
+                        { label: "Launchers", href: "/categories/category-x-launchers", variant: "outline" },
+                        { label: "Stadiums", href: "/categories/category-x-stadiums", variant: "outline" },
+                    ],
+                },
+            ],
+        },
+        createdAt: daysAgo(1),
+        updatedAt: daysAgo(1),
+    },
+    /*
+     * 🛑 TCI's five BUDGET TILES ("Under ₹499 / ₹799 / ₹999 / ₹1499") are
+     * DELIBERATELY NOT SEEDED, and this is a decision rather than an omission.
+     *
+     * The plan argued they are safe because "the tiles are LINKS, not prices".
+     * That is true of the tile and false of the mechanism. Prices are hidden from
+     * signed-out visitors, and the price-range facet and every money sort are
+     * withheld specifically because "hiding the number is not hiding the value" —
+     * bracketing a hidden price with a range filter is the one casually reachable
+     * way around the gate. The documented residue is that a HAND-WRITTEN
+     * `?f=price<499` still works, and five tiles on the homepage promote that
+     * residue to the most prominent path on the site: a guest could bucket the
+     * entire catalogue into five price bands in five clicks, without an account.
+     *
+     * The matrix above has no such property — a category link reveals no amount.
+     * Revisit if guest price-gating is ever relaxed; until then this is a tile
+     * that would quietly undo a gate another step built.
+     */
 ];

package/dist/seed/index.d.ts

@@ -90,3 +90,5 @@ export { mergeFirestoreIndices, generateMergedFirestoreIndexFile, } from "./fire
 export { assertPiiRoundTrip, seedForTest } from "./test-utils";
 export type { TestSeedHandles } from "./test-utils";
 export { type SeedPurpose, type SeedPurposeFields, type WithSeedPurpose, SEED_PURPOSE_VALUES, ALL_SEED_PURPOSES, SEED_COLLECTION_PURPOSE, SEED_TEST_TTL_DAYS, isSeedPurpose, resolveSeedPurpose, seedPurposeFields, stampSeedPurpose, asSeedPurpose, } from "./seed-purpose";
+export { partGlossarySeedData } from "./part-glossary-seed-data";
+export { modelCompositionSeedData } from "./model-composition-seed-data";

package/dist/seed/index.js

@@ -35,6 +35,16 @@ export { storesSeedData } from "./stores-seed-data.js";
 export { storeAddressesSeedData } from "./store-addresses-seed-data.js";
 export { categoriesSeedData, categoriesP1SeedData } from "./categories-seed-data.js";
 export { productsStandardSeedData } from "./products-standard-seed-data.js";
+/*
+ * 🛑 `productsCatalogueSeedData` DELETED (I6, 2026-10-13) — 968 generated
+ * listings, one per tier-4 leaf. "I do not need products ... rest is either
+ * standard or test data."
+ *
+ * A merge-write loader CANNOT remove a document, so deleting the file alone
+ * leaves all 968 rows live and `appkit-seed status` reports the collection in
+ * sync either way (it counts ids). The removal is
+ *   npx appkit-seed delete --yes --collections products && npx appkit-seed load
+ */
 export { productsAuctionsSeedData } from "./products-auctions-seed-data.js";
 export { productsPreordersSeedData } from "./products-preorders-seed-data.js";
 export { productsPrizeDrawsSeedData } from "./products-prize-draws-seed-data.js";
@@ -92,3 +102,6 @@ export { assertPiiRoundTrip, seedForTest } from "./test-utils.js";
  * must never be hand-written beside it (`audit-seed-purpose` blocks it).
  */
 export { SEED_PURPOSE_VALUES, ALL_SEED_PURPOSES, SEED_COLLECTION_PURPOSE, SEED_TEST_TTL_DAYS, isSeedPurpose, resolveSeedPurpose, seedPurposeFields, stampSeedPurpose, asSeedPurpose, } from "./seed-purpose.js";
+// E4/D12 — generated from `docs/research/part-composition-2026-10/`.
+export { partGlossarySeedData } from "./part-glossary-seed-data.js";
+export { modelCompositionSeedData } from "./model-composition-seed-data.js";

package/dist/seed/model-composition-seed-data.d.ts

@@ -0,0 +1,15 @@
+/**
+ * GENERATED by `scripts/generate-parts-seed.mjs` — do not hand-edit.
+ * Source: `docs/research/part-composition-2026-10/` (E4a/E4b), itself
+ * extracted from the LOCAL corpus with no network crawl.
+ *
+ * Model composition — which parts each bey is made of — 259 rows.
+ *
+ * 🛑 Facts only. Fandom is CC-BY-SA, so names, codes, weights and slot
+ * structure are taken and the PROSE is not — our own descriptions come from
+ * the category templates. Regenerate rather than edit: a hand-fix here is lost
+ * on the next run and, worse, makes the committed output disagree with the
+ * script that is supposed to produce it.
+ */
+import type { ModelCompositionDocument } from "../features/parts/schemas/firestore";
+export declare const modelCompositionSeedData: Partial<ModelCompositionDocument>[];