@mohasinac/appkit 4.52.4 → 4.53.0

package/dist/seed/bids-seed-data.d.ts

@@ -1,2 +1,2 @@
-import type { BidDocument } from "../features/auctions/schemas/firestore";
-export declare const bidsSeedData: BidDocument[];
+import type { BidPlain } from "../features/auctions/schemas/firestore";
+export declare const bidsSeedData: BidPlain[];

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

@@ -23,6 +23,7 @@
  * @tag consumers:seed/index.ts,seed/runner.ts
  * @tag sideEffects:none
  */
+import { buildBidSearchTxt } from "../utils/search-txt-builders.js";
 const NOW = new Date();
 const daysAgo = (n) => new Date(NOW.getTime() - n * 86400000);
 const BIDDER_EMAILS = {
@@ -36,7 +37,7 @@ const BIDDER_NAMES = {
     "user-ananya-collector": "Mock User 9",
 };
 /*
- * Typed on the document, not `FirestoreDocument`. Once `BidDocument` gained
+ * Typed on the PLAIN shape, not `FirestoreDocument`. Once `BidDocument` gained
  * `statusHistory?: StatusChangeEntry[]`, `Partial<BidDocument>` stopped being
  * assignable to `FirestoreDocument` — an array of objects does not satisfy
  * that index signature. The right fix is to narrow the parameter to what the
@@ -51,6 +52,26 @@ function withBidDefaults(b) {
         currency: "INR",
         isWinning: b.status === "active" || b.status === "won",
         updatedAt: (b.createdAt ?? NOW),
+        /*
+         * 🛑 DERIVED here, from the same builder the repository's write hook uses —
+         * never a hand-written token list.
+         *
+         * A seeded row without this is invisible to search forever:
+         * `array-contains` cannot match a field the document does not have, and it
+         * raises nothing (Root Cause #101's shape). Deriving it from
+         * `buildBidSearchTxt` is also what keeps the seed and every runtime write
+         * agreeing on the normalisation — two token lists built two ways is the
+         * mirror-drift trap (Root Cause #42).
+         *
+         * Applied INSIDE `withBidDefaults` on purpose, after `productTitle` is
+         * defaulted above: a derivation placed before it would index the empty
+         * string for every row that relies on the fallback.
+         */
+        searchTxt: buildBidSearchTxt({
+            productTitle: b.productTitle ??
+                (b.productId ?? "").replace(/^auction-/, "").replace(/-/g, " "),
+            userName: b.userName,
+        }),
     };
 }
 /**
@@ -154,7 +175,7 @@ const _rawBidsSeedData = [
     // auction-beyblade-burst-spriggan-requiem-bought-out — a BUYOUT ended it.
     //
     // Three competitive bids that lost, then the buyout that won. A buyout is a
-    // real BidDocument (`isBuyout: true`) — it is not a bid-free purchase, which
+    // real BidPlain (`isBuyout: true`) — it is not a bid-free purchase, which
     // is why the order's `sourceContext.bidCount` is 3 rather than 0: the buyout
     // itself is excluded from the "against N bidders" figure, the three it beat
     // are not. `standingBidAtBuyout` is read from these bids and NOT from

package/dist/seed/events-seed-data.d.ts

@@ -1,5 +1,5 @@
-import type { EventDocument, EventEntryDocument } from "../features/events/schemas";
-export declare const eventEntriesSeedData: EventEntryDocument[];
+import type { EventDocument, EventEntryPlain } from "../features/events/schemas";
+export declare const eventEntriesSeedData: EventEntryPlain[];
 /**
  * Tokens derived here, not per record — see _helpers/search-txt-wrappers.ts for
  * why the wrapper form is what makes omission impossible.

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

@@ -361,6 +361,11 @@ const _raweventsSeedData = [
     },
 ];
 // ── Event Entries ────────────────────────────────────────────────────────────
+/*
+ * 🛑 `EventEntryPlain`: these fixtures hold REAL plaintext and `seed-cli`
+ * encrypts the PII fields on write. The document type now declares them
+ * `Encrypted<string>`, so the document type would be a false claim.
+ */
 export const eventEntriesSeedData = [
     // Rehan entered the poll
     {

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

@@ -659,7 +659,7 @@ const faqSeedRecords = [
     {
         id: "faq-how-to-verify-authenticity",
         question: "How can I verify if a collectible is authentic?",
-        answer: html(`<p>Look for these trust signals on LetItRip: <strong>Verified Seller</strong> badge (store has passed manual review), <strong>Graded</strong> badge (PSA/BGS/CGC certified with certificate number), <strong>Sealed</strong> badge (factory-sealed product). For ungraded items, check the seller's photo quality and description detail. If in doubt, message the seller before purchasing.</p>`),
+        answer: html(`<p>Look for these trust signals on LetItRip: <strong>Verified Seller</strong> badge (store has passed manual review), <strong>Graded</strong> badge (PSA/BGS/CGC certified with certificate number), <strong>Sealed</strong> badge (factory-sealed product). For ungraded items, check the seller's photo quality and description detail. If in doubt, message the seller before purchasing.</p><p>For <strong>Beyblades specifically</strong>, the <a href="/tools/authenticity">authenticity checker</a> takes a model name, a box code or the brand on the packaging and tells you which checks apply to that generation — and the <a href="/spot-a-fake">spot-a-fake guide</a> walks the same signals by hand, with no account needed.</p>`),
         category: "product_information",
         showOnHomepage: true,
         showInFooter: false,
@@ -667,7 +667,7 @@ const faqSeedRecords = [
         order: 32,
         priority: 8,
         tags: ["authentication", "verification", "trust"],
-        relatedFAQs: ["faq-counterfeit-guarantee", "faq-psa-vs-bgs-vs-cgc"],
+        relatedFAQs: ["faq-counterfeit-guarantee", "faq-psa-vs-bgs-vs-cgc", "faq-check-if-my-beyblade-is-original"],
         stats: makeStats(3800, 190),
         seo: { slug: "faq-how-to-verify-authenticity", metaTitle: "Verify Collectible Authenticity", metaDescription: "How to verify if a collectible is authentic on LetItRip." },
         isActive: true,
@@ -1464,10 +1464,79 @@ const faqSeedRecords = [
         createdAt: daysAgo(30),
         updatedAt: daysAgo(2),
     },
+    {
+        id: "faq-check-if-my-beyblade-is-original",
+        question: "How do I check whether my Beyblade is original?",
+        answer: html("<p>Start with the <a href=\"/tools/authenticity\">authenticity checker</a>. Give it a model name, the code printed on the box, or the brand on the packaging, and it tells you which checks apply to that generation, what the recorded box codes say, and what is still unsettled. The reference half of that page — the generation table, the box-code explanation, the checks that apply regardless — is free and needs no account; only the per-item lookup asks you to sign in.</p><p>🛑 <strong>It grades, it does not rule.</strong> The strongest thing it will say is that something matches a batch collectors record as a reduced-quality run — a statement about a production batch, never an accusation against your seller. Authenticity is settled by physical checks, and the tool lists the conclusive ones first for your generation: a fully die-cast performance tip on a Metal Fight bey, Phillips screws where tri-wing belong on Burst, a Gear Chip missing the <em>Beyblade X</em> logo, or moulded Takara copyright text absent from a plastic-generation part.</p><p>The longer buying guide is at <a href=\"/spot-a-fake\">how to spot a fake</a>. If the problem is a specific seller rather than a specific item, the <a href=\"/scams\">scam registry</a> takes reports.</p>"),
+        category: "product_information",
+        showOnHomepage: true,
+        showInFooter: false,
+        isPinned: false,
+        order: 208,
+        priority: 10,
+        tags: ["authenticity", "fake", "original", "beyblade", "checker", "takara tomy"],
+        relatedFAQs: ["faq-beyblade-box-code-meaning", "faq-what-is-a-reproduction", "faq-is-funskool-beyblade-fake"],
+        stats: makeStats(0, 0),
+        seo: {
+            slug: "faq-check-if-my-beyblade-is-original",
+            metaTitle: "How do I check whether my Beyblade is original?",
+            metaDescription: "Use the authenticity checker: a model name, a box code or the brand on the packaging, and it shows which checks apply to that generation and what is still unsettled.",
+        },
+        isActive: true,
+        createdBy: "user-admin-letitrip",
+        createdAt: daysAgo(1),
+        updatedAt: daysAgo(1),
+    },
+    {
+        id: "faq-beyblade-box-code-meaning",
+        question: "What does the code on the bottom of the box mean?",
+        answer: html("<p>Two different things are both called “the code”, and they answer different questions.</p><p>A <strong>product code</strong> — <code>BB-105</code>, <code>B-174</code>, <code>BX-34</code>, <code>MA-09</code> — identifies the release, and its letter prefix identifies the generation. Read the whole letter group before the digits: <code>BB-</code> is Metal Fight while <code>B-</code> is Burst, so they are easy to confuse. 🛑 <strong>A product code existing proves nothing about authenticity.</strong> One counterfeit catalogue we measured carried more than 900 genuine Takara Tomy codes across 1,277 unlicensed products. What carries information is whether the code and the model name <em>agree</em> — which is what the <a href=\"/tools/authenticity\">authenticity checker</a> compares.</p><p>A <strong>date code</strong> is a letter followed by four digits, like <code>A0813</code>, and it is a production stamp. Collectors have compiled which of these appear on boxes known to be genuine and which belong to reduced-quality batches, and the checker holds both lists for the Metal Fight era. 🛑 <strong>How it decodes is disputed.</strong> One reading takes the letter as the month and the next two digits as the day (8 January 2013); another takes the letter as the factory and the digits as the week of the year. Takara Tomy has published neither, so treat any date as indicative. No decoding has been established at all for Burst or Beyblade X boxes.</p><p>A code that is in neither list means <em>not recorded</em>, not <em>fake</em> — the lists were compiled from boxes collectors personally held, and new genuine codes still surface.</p>"),
+        category: "product_information",
+        showOnHomepage: false,
+        showInFooter: false,
+        isPinned: false,
+        order: 209,
+        priority: 9,
+        tags: ["box code", "date code", "product code", "authenticity", "takara tomy", "midfake"],
+        relatedFAQs: ["faq-check-if-my-beyblade-is-original", "faq-what-is-a-reproduction"],
+        stats: makeStats(0, 0),
+        seo: {
+            slug: "faq-beyblade-box-code-meaning",
+            metaTitle: "What does the code on the bottom of a Beyblade box mean?",
+            metaDescription: "Product codes identify the release and the generation; date codes are production stamps with two disputed readings. Neither proves a bey is genuine on its own.",
+        },
+        isActive: true,
+        createdBy: "user-admin-letitrip",
+        createdAt: daysAgo(1),
+        updatedAt: daysAgo(1),
+    },
+    {
+        id: "faq-is-funskool-beyblade-fake",
+        question: "Is a Funskool Beyblade fake? What about Sonokong?",
+        answer: html("<p><strong>No. Both are legitimate.</strong> Funskool is a licensed Indian importer and Sonokong is the licensed South Korean producer — their names on a box are a <em>positive</em> signal, not a warning. The same goes for the other regional importers: Mani (Hong Kong), Funbox (Taiwan), Sheng Tai (Singapore), NewBoy (Middle East), Bankee (Philippines) and PT Emway (Indonesia). An importer’s holographic sticker or certificate inside the packaging is a sign of a properly imported product.</p><p>🛑 A guide that tells you anything other than “Takara Tomy” or “Hasbro” is a fake is simply wrong, and that mistake is costly in India specifically, where Funskool product is common.</p><p>What <em>should</em> worry you is a box whose most prominent branding is a name nobody licenses — or no manufacturer name at all. Sellers of unlicensed tops here rarely claim to be originals; they sell under their own brand as “aftermarket”, “custom” or “upgraded”. That framing is not a grey area. You can check a brand name against the known lists in the <a href=\"/tools/authenticity\">authenticity checker</a>.</p>"),
+        category: "product_information",
+        showOnHomepage: false,
+        showInFooter: false,
+        isPinned: false,
+        order: 211,
+        priority: 8,
+        tags: ["funskool", "sonokong", "importer", "authenticity", "india", "licensed"],
+        relatedFAQs: ["faq-check-if-my-beyblade-is-original", "faq-what-is-a-reproduction"],
+        stats: makeStats(0, 0),
+        seo: {
+            slug: "faq-is-funskool-beyblade-fake",
+            metaTitle: "Is a Funskool Beyblade fake?",
+            metaDescription: "No — Funskool is a licensed Indian importer and Sonokong the licensed Korean producer. Both marques are a positive signal, not a warning.",
+        },
+        isActive: true,
+        createdBy: "user-admin-letitrip",
+        createdAt: daysAgo(1),
+        updatedAt: daysAgo(1),
+    },
     {
         id: "faq-what-is-a-reproduction",
         question: "What is a \"reproduction\" or \"midfake\"? Is it a fake?",
-        answer: html("<p>A <strong>reproduction</strong> — the community calls them midfakes — is an unbranded 1st-copy of an original design, mostly Chinese-made, carrying no manufacturer's marque. Quality is often genuinely good, and some tournament formats permit certain reproduction parts.</p><p>It is <strong>not</strong> the same as a cheap counterfeit. A counterfeit is poor-quality and can contain lead or cadmium in its metal parts, which is a safety matter — we do not allow those listed at all. A reproduction is a legitimate thing to sell <em>when it is labelled</em>, and every listing on LetItRip states its authenticity as Original, Reproduction, or Unverified.</p><p>🛑 If a seller calls something \"aftermarket\", \"custom\" or \"upgraded\" without naming a manufacturer, they are describing a reproduction. Ask.</p>"),
+        answer: html("<p><strong>“Midfake” is used two ways</strong>, and the difference matters. In the Metal Fight community it means a specific thing: a <em>Takara Tomy</em> batch of reduced quality, built on Takara Tomy blueprints in Taiwan, with different alloys and TT-style box codes — so it may well carry the real marque. Collectors identify those batches by the code on the bottom of the box. Used more loosely — and this is the commoner sense in India — it means any 1st-copy of an original design, mostly Chinese-made, carrying no manufacturer's marque at all. Quality is often genuinely good, and some tournament formats permit certain reproduction parts.</p><p>🛑 There is <strong>no official Takara Tomy statement</strong> acknowledging the reduced-quality batches, so everything known about them comes from collectors comparing boxes.</p><p>It is <strong>not</strong> the same as a cheap counterfeit. A counterfeit is poor-quality and can contain lead or cadmium in its metal parts, which is a safety matter — we do not allow those listed at all. A reproduction is a legitimate thing to sell <em>when it is labelled</em>, and every listing on LetItRip states its authenticity as Original, Reproduction, or Unverified.</p><p>🛑 If a seller calls something \"aftermarket\", \"custom\" or \"upgraded\" without naming a manufacturer, they are describing a reproduction. Ask.</p>"),
         category: "product_information",
         showOnHomepage: true,
         showInFooter: false,
@@ -1475,12 +1544,12 @@ const faqSeedRecords = [
         order: 210,
         priority: 10,
         tags: ["reproduction", "midfake", "authenticity", "fake", "aftermarket"],
-        relatedFAQs: [],
+        relatedFAQs: ["faq-check-if-my-beyblade-is-original", "faq-beyblade-box-code-meaning", "faq-counterfeit-guarantee"],
         stats: makeStats(670, 50),
         seo: {
             slug: "faq-what-is-a-reproduction",
             metaTitle: "What is a \"reproduction\" or \"midfake\"? Is it a fake?",
-            metaDescription: "A reproduction — the community calls them midfakes — is an unbranded 1st-copy of an original design, mostly Chinese-made, carrying no manufacturer's marque",
+            metaDescription: "“Midfake” means two different things — a reduced-quality Takara Tomy batch, or any unbranded 1st-copy. Both differ from a counterfeit.",
         },
         isActive: true,
         createdBy: "user-admin-letitrip",
@@ -1763,6 +1832,107 @@ const faqSeedRecords = [
         createdAt: daysAgo(30),
         updatedAt: daysAgo(2),
     },
+    // ── STICKER SHEETS (3) ──────────────────────────────────────────────────────
+    //
+    // 🛑 FILED UNDER `product_information`, NOT A NEW `stickers` CATEGORY.
+    // The plan called for one, on the premise that the seeded set was
+    // Shipping/Returns/Payments/Auctions/Pre-orders — that list came from a stale
+    // paragraph in CLAUDE.md. The real union already carries `product_information`
+    // (FAQ_CATEGORY_LABELS), which is exactly what these are. Adding a tenth
+    // category for three entries would mean extending a compile-checked union,
+    // the admin option list and every chip derived from it, to say something an
+    // existing value already says.
+    //
+    // 🛑 THREE, NOT SIX. The plan drafted six questions and said plainly that the
+    // answers to half of them need product facts nobody has yet. Those three are
+    // listed below as questions ONLY, and are deliberately NOT seeded — `faqs` is
+    // a public, indexed collection with its own seo.slug, so a placeholder answer
+    // there is a confident lie on a page Google will read.
+    //
+    //   · "What size are the stickers?"           needs: real sheet + part dimensions
+    //   · "Are they weatherproof / dishwasher-safe?" needs: material + laminate spec
+    //   · "Can I buy a single sticker rather than a whole sheet?"
+    //       needs: the per-part listings from Part Two. Today the honest answer is
+    //       "no", and seeding that now would have to be rewritten the week the
+    //       grouped parent+parts listings ship.
+    //
+    // The three below need no product facts — they explain what a kiss cut IS,
+    // which is true of every kiss-cut sticker ever made.
+    {
+        id: "faq-what-is-a-kiss-cut-sticker",
+        question: "What is a kiss-cut sticker?",
+        answer: html(`<p>A <strong>kiss cut</strong> goes through the sticker's vinyl but <em>not</em> through the paper backing behind it. The sheet stays in one piece, and each sticker peels off individually when you want it.</p><p>A <strong>die cut</strong> goes all the way through both layers, so every sticker is already a separate loose piece.</p><p>Kiss-cut sheets are what vintage Beyblade stickers were originally made as: one sheet, many stickers, each outlined along its own shape.</p>`),
+        category: "product_information",
+        showOnHomepage: false,
+        showInFooter: false,
+        isPinned: false,
+        order: 1,
+        priority: 5,
+        tags: ["stickers", "kiss-cut", "die-cut", "sheets"],
+        relatedFAQs: ["faq-sticker-white-border", "faq-how-to-apply-a-sticker"],
+        useSiteSettings: true,
+        variables: {},
+        stats: makeStats(0, 0),
+        seo: {
+            slug: "faq-what-is-a-kiss-cut-sticker",
+            metaTitle: "What is a kiss-cut sticker? | LetItRip",
+            metaDescription: "A kiss cut goes through the vinyl but not the backing, so the sheet stays whole and each sticker peels off on its own.",
+        },
+        isActive: true,
+        createdBy: "user-admin-letitrip",
+        createdAt: daysAgo(1),
+        updatedAt: daysAgo(1),
+    },
+    {
+        id: "faq-sticker-white-border",
+        question: "Why do some stickers have a white border around them?",
+        answer: html(`<p>That border is part of the cut, not a printing mistake. A cutter cannot follow fine detail perfectly, so the cut line is placed slightly <em>outside</em> the artwork — the small margin that leaves is what stops a sliver of artwork being shaved off if the blade drifts by a fraction of a millimetre.</p><p>Where the original sticker was designed with a border, we keep it. Where it was cut tight to the art, we cut tight to the art.</p>`),
+        category: "product_information",
+        showOnHomepage: false,
+        showInFooter: false,
+        isPinned: false,
+        order: 2,
+        priority: 4,
+        tags: ["stickers", "border", "cutting", "bleed"],
+        relatedFAQs: ["faq-what-is-a-kiss-cut-sticker"],
+        useSiteSettings: true,
+        variables: {},
+        stats: makeStats(0, 0),
+        seo: {
+            slug: "faq-sticker-white-border",
+            metaTitle: "Why do stickers have a white border? | LetItRip",
+            metaDescription: "The margin around a sticker is part of the cut — it stops the blade shaving artwork if it drifts a fraction of a millimetre.",
+        },
+        isActive: true,
+        createdBy: "user-admin-letitrip",
+        createdAt: daysAgo(1),
+        updatedAt: daysAgo(1),
+    },
+    {
+        id: "faq-how-to-apply-a-sticker",
+        question: "How do I apply a sticker so it does not lift at the edges?",
+        answer: html(`<p>Clean the surface first and let it dry completely — most lifting is a dusty or slightly greasy surface rather than the adhesive.</p><p>Peel the sticker from one corner rather than lifting it flat, lay that edge down first, then press across the sticker in one direction so the air pushes out ahead of your finger instead of being trapped under it.</p><p>Press firmly for a few seconds once it is down, and leave it a day before getting it wet.</p>`),
+        category: "product_information",
+        showOnHomepage: false,
+        showInFooter: false,
+        isPinned: false,
+        order: 3,
+        priority: 3,
+        tags: ["stickers", "application", "how-to"],
+        relatedFAQs: ["faq-what-is-a-kiss-cut-sticker"],
+        useSiteSettings: true,
+        variables: {},
+        stats: makeStats(0, 0),
+        seo: {
+            slug: "faq-how-to-apply-a-sticker",
+            metaTitle: "How to apply a sticker without lifting edges | LetItRip",
+            metaDescription: "Clean the surface, lay one edge first, and press across in one direction so air pushes out ahead of your finger.",
+        },
+        isActive: true,
+        createdBy: "user-admin-letitrip",
+        createdAt: daysAgo(1),
+        updatedAt: daysAgo(1),
+    },
 ];
 /**
  * Derive `searchTxt` for every record from its own content.

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

@@ -1,12 +1,28 @@
 /*
  * WHY: Seeds the homepage layout — which sections render, in what order, with what copy.
- * WHAT: 22 sections (21 enabled + 1 deliberately disabled), ordered 1..21 contiguously.
+ * WHAT: 23 sections (22 enabled + 1 deliberately disabled), ordered 1..23 contiguously.
+ *
+ * 🛑 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
+ * the file held 23 documents numbered 1..22, and `section-systems-matrix` and
+ * `section-featured-products` BOTH claimed `order: 5`. `MarketplaceHomepageView`
+ * tie-breaks on `updatedAt` (identical for both) and then `id.localeCompare`, so
+ * the live running order of the homepage was decided alphabetically — a silent
+ * accident, not a layout decision.
  *
  * ORDER follows current marketplace-homepage research rather than the previous
- * arbitrary arrangement: hero → trust → orient (categories) → 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).
+ * 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).
+ *
+ * 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
+ * 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.
@@ -145,7 +161,7 @@ export const homepageSectionsSeedData = [
     {
         id: "section-featured-products",
         type: "products",
-        order: 5,
+        order: 6,
         enabled: true,
         config: {
             title: "Featured Products",
@@ -163,7 +179,7 @@ export const homepageSectionsSeedData = [
     {
         id: "section-live-auctions",
         type: "auctions",
-        order: 6,
+        order: 7,
         enabled: true,
         config: {
             title: "Live Auctions",
@@ -181,7 +197,7 @@ export const homepageSectionsSeedData = [
     {
         id: "section-pre-orders",
         type: "pre-orders",
-        order: 7,
+        order: 8,
         enabled: true,
         config: {
             title: "Reserve Before It Ships",
@@ -199,7 +215,7 @@ export const homepageSectionsSeedData = [
     {
         id: "section-featured-bundles",
         type: "featured-bundles",
-        order: 8,
+        order: 9,
         enabled: true,
         config: {
             title: "Curated Bundles",
@@ -215,7 +231,7 @@ export const homepageSectionsSeedData = [
     {
         id: "section-featured-stores",
         type: "stores",
-        order: 9,
+        order: 10,
         enabled: true,
         config: {
             title: "Featured Stores",
@@ -233,7 +249,7 @@ export const homepageSectionsSeedData = [
     {
         id: "section-collector-reviews",
         type: "reviews",
-        order: 10,
+        order: 11,
         enabled: true,
         config: {
             title: "What Buyers Say",
@@ -252,7 +268,7 @@ export const homepageSectionsSeedData = [
     {
         id: "section-upcoming-events",
         type: "events",
-        order: 11,
+        order: 12,
         enabled: true,
         config: {
             title: "Events & Offers",
@@ -269,7 +285,7 @@ export const homepageSectionsSeedData = [
     {
         id: "section-event-raffles",
         type: "event-raffles",
-        order: 12,
+        order: 13,
         enabled: true,
         config: {
             title: "Raffles & Spin Wheels",
@@ -285,7 +301,7 @@ export const homepageSectionsSeedData = [
     {
         id: "section-prize-draws",
         type: "prize-draws",
-        order: 13,
+        order: 14,
         enabled: true,
         config: {
             title: "Prize Draws",
@@ -304,7 +320,7 @@ export const homepageSectionsSeedData = [
     {
         id: "section-collector-blog",
         type: "blog-articles",
-        order: 14,
+        order: 15,
         enabled: true,
         config: {
             title: "From Our Blog",
@@ -324,7 +340,7 @@ export const homepageSectionsSeedData = [
     {
         id: "section-beyblade-banner",
         type: "banner",
-        order: 15,
+        order: 16,
         enabled: true,
         config: {
             height: "md",
@@ -348,7 +364,7 @@ export const homepageSectionsSeedData = [
     {
         id: "section-newsletter",
         type: "newsletter",
-        order: 16,
+        order: 17,
         enabled: true,
         config: {
             title: "Get new listings first",
@@ -366,7 +382,7 @@ export const homepageSectionsSeedData = [
     {
         id: "section-platform-stats",
         type: "stats",
-        order: 17,
+        order: 18,
         enabled: true,
         config: {
             title: "By the numbers",
@@ -383,7 +399,7 @@ export const homepageSectionsSeedData = [
     {
         id: "section-platform-features",
         type: "features",
-        order: 18,
+        order: 19,
         enabled: true,
         config: {
             title: "Security You Can Trust",
@@ -419,7 +435,7 @@ export const homepageSectionsSeedData = [
     {
         id: "section-whatsapp-community",
         type: "whatsapp-community",
-        order: 19,
+        order: 20,
         enabled: true,
         config: {
             title: "Join the community",
@@ -440,7 +456,7 @@ export const homepageSectionsSeedData = [
     {
         id: "section-homepage-faq",
         type: "faq",
-        order: 20,
+        order: 21,
         enabled: true,
         config: {
             title: "Frequently Asked Questions",
@@ -509,7 +525,7 @@ export const homepageSectionsSeedData = [
     {
         id: "section-top-brands",
         type: "brands",
-        order: 21,
+        order: 22,
         enabled: true,
         config: {
             title: "Top Brands",
@@ -530,7 +546,7 @@ export const homepageSectionsSeedData = [
     {
         id: "section-social-feed-instagram",
         type: "social-feed",
-        order: 22,
+        order: 23,
         enabled: false,
         config: {
             title: "Follow along",

package/dist/seed/index.d.ts

@@ -84,6 +84,7 @@ export { scammersSeedData } from "./scammers-seed-data";
 export { supportTicketsSeedData } from "./support-tickets-seed-data";
 export { testerChecklistSeedData, testerResponsesSeedData, } from "../features/tester/seed-data";
 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";

package/dist/seed/index.js

@@ -91,6 +91,7 @@ export { testerChecklistSeedData,
 // continues, which is exactly what happened on the first attempt here.
 testerResponsesSeedData, } from "../features/tester/seed-data/index.js";
 export { productFeaturesSeedData } from "./product-features-seed-data.js";
+export { authenticityKnowledgeSeedData, AUTHENTICITY_KNOWLEDGE_COLLECTION, AUTHENTICITY_KNOWLEDGE_COUNT, } from "./authenticity-knowledge-seed-data.js";
 export { taxCodesSeedData } from "./tax-codes-seed-data.js";
 export { offersSeedData } from "./offers-seed-data.js";
 // S-STORE Extensions (Tier S-STORE) — 11 new collections

package/dist/seed/lottery-entries-seed-data.d.ts

@@ -1,2 +1,2 @@
-import type { LotteryEntryDocument } from "../features/lottery/schemas/firestore";
-export declare const lotteryEntriesSeedData: LotteryEntryDocument[];
+import type { LotteryEntryPlain } from "../features/lottery/schemas/firestore";
+export declare const lotteryEntriesSeedData: LotteryEntryPlain[];

package/dist/seed/offers-seed-data.d.ts

@@ -1,2 +1,2 @@
-import type { OfferDocument } from "../features/seller/schemas/firestore";
-export declare const offersSeedData: Partial<OfferDocument>[];
+import type { OfferPlain } from "../features/seller/schemas/firestore";
+export declare const offersSeedData: Partial<OfferPlain>[];

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

@@ -26,7 +26,7 @@
  * is testable, and it is the exact shape of every offer written before W2.
  *
  * EXPORTS:
- *   offersSeedData — Array of Partial<OfferDocument> for seed runner
+ *   offersSeedData — Array of Partial<OfferPlain> for seed runner
  *
  * @tag domain:offers,seller
  * @tag layer:seed

package/dist/seed/orders-seed-data.d.ts

@@ -1,2 +1,2 @@
-import type { OrderDocument } from "../features/orders/schemas/firestore";
-export declare const ordersSeedData: OrderDocument[];
+import type { OrderPlain } from "../features/orders/schemas/firestore";
+export declare const ordersSeedData: OrderPlain[];

package/dist/seed/payouts-seed-data.d.ts

@@ -1,2 +1,2 @@
-import type { PayoutDocument } from "../features/payments/schemas";
-export declare const payoutsSeedData: Partial<PayoutDocument>[];
+import type { PayoutPlain } from "../features/payments/schemas";
+export declare const payoutsSeedData: Partial<PayoutPlain>[];

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

@@ -3,7 +3,7 @@
  * WHAT: 10 payouts: COMPLETED (5), PROCESSING (1), PENDING (2 — one with refund deduction), FAILED (2).
  *
  * EXPORTS:
- *   payoutsSeedData — Array of Partial<PayoutDocument> for seed runner
+ *   payoutsSeedData — Array of Partial<PayoutPlain> for seed runner
  *
  * @tag domain:payouts,payments
  * @tag layer:seed

package/dist/seed/reviews-seed-data.d.ts

@@ -1,2 +1 @@
-import type { ReviewDocument } from "../features/reviews/schemas/firestore";
-export declare const reviewsSeedData: ReviewDocument[];
+export declare const reviewsSeedData: import("../security/encrypted").Plaintext<import("..").ReviewDocument>[];

package/dist/seed/seed-purpose.js

@@ -136,6 +136,13 @@ export const SEED_COLLECTION_PURPOSE = {
     /* The ~169-term feature vocabulary: condition, authenticity, release, type,
      * spin, grade, chase. Hand-curated from the crawl. */
     productFeatures: "permanent",
+    /*
+     * The box-code tables and generation summaries. `permanent` because they
+     * are reference data compiled from archived primary sources, not exercise
+     * fixtures — a purge that cleared them would leave an admin with no way to
+     * answer "what do we say about this code" short of re-running a generator.
+     */
+    authenticityKnowledge: "permanent",
     /* Branding, fees, commissions, watermark, legal pages, and the AES-encrypted
      * credentials. 🛑 A purge here would destroy live API keys. */
     siteSettings: "permanent",

package/dist/seed/sessions-seed-data.d.ts

@@ -1,3 +1,3 @@
-import { type SessionDocument, SESSION_COLLECTION } from "../features/auth/schemas";
+import { type SessionPlain, SESSION_COLLECTION } from "../features/auth/schemas";
 export { SESSION_COLLECTION };
-export declare const sessionsSeedData: SessionDocument[];
+export declare const sessionsSeedData: SessionPlain[];

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

@@ -20,6 +20,11 @@ const NOW = new Date();
 const daysAgo = (n) => new Date(NOW.getTime() - n * 86400000);
 const daysAhead = (n) => new Date(NOW.getTime() + n * 86400000);
 export { SESSION_COLLECTION };
+/*
+ * 🛑 `SessionPlain`: these fixtures hold real IPs and user-agent strings, and
+ * `seed-cli` encrypts them on write through the repository's own nested
+ * `piiFields` paths. The document type declares them `Encrypted<string>`.
+ */
 export const sessionsSeedData = [
     // Admin — Chrome Desktop (active)
     {

package/dist/seed/site-settings-seed-data.js

@@ -55,7 +55,7 @@ export const siteSettingsSeedData = {
     announcementBar: {
         enabled: true,
         message: "🎉 Up to 25% off select listings + free shipping on orders above ₹999 — See Events for codes",
-        link: "/events",
+        link: ROUTES.PUBLIC.EVENTS,
     },
     watermark: {
         type: "text",

package/dist/seed/support-tickets-seed-data.d.ts

@@ -1,4 +1,4 @@
-import type { SupportTicketDocument } from "../features/support/schemas/firestore";
+import type { SupportTicketPlain } from "../features/support/schemas/firestore";
 /**
  * Derive `searchTxt` for every record from its own subject.
  *
@@ -13,4 +13,4 @@ import type { SupportTicketDocument } from "../features/support/schemas/firestor
  * function of the record's own content, so it stays deterministic and does not
  * reintroduce the `appkit-seed` idempotency problem of Root Cause #25.
  */
-export declare const supportTicketsSeedData: Partial<SupportTicketDocument>[];
+export declare const supportTicketsSeedData: Partial<SupportTicketPlain>[];

package/dist/seed/support-tickets-seed-data.js

@@ -3,7 +3,7 @@
  * WHAT: open (2), in_progress (2), waiting_on_user (1), resolved (2), closed (1).
  *
  * EXPORTS:
- *   supportTicketsSeedData — Array of Partial<SupportTicketDocument> for seed runner
+ *   supportTicketsSeedData — Array of Partial<SupportTicketPlain> for seed runner
  *
  * @tag domain:support
  * @tag layer:seed