@mohasinac/appkit 4.43.0 → 4.45.0

package/dist/seed/seed-purpose.d.ts

@@ -0,0 +1,200 @@
+/**
+ * ── Seed provenance: may a purge delete this row? ───────────────────────────
+ *
+ * Every document written by `appkit-seed` carries a `seedPurpose`, and it is
+ * the ONE declaration of whether a row is real content or clearable test data.
+ * The purge reads it; nothing else decides.
+ *
+ * ## The rule this exists to enforce
+ *
+ * 🛑 **Content comes from a seed FILE, never from a direct database write.**
+ * Not a one-off script, not a console paste, not a `node -e`. A row that exists
+ * only in Firestore cannot be reviewed in a diff, cannot be recreated after a
+ * purge, and cannot be found by anyone who did not watch it being written —
+ * and when it references other rows, nothing updates it when those move.
+ *
+ * `seedPurpose` makes that rule *checkable*: a document with no `seedPurpose`
+ * was not written by the seeder, so the purge will not touch it.
+ *
+ * ## 🛑 THE DEFAULT IS `test`, AND THE OPPOSITE WAS THIS FILE'S FIRST BUG
+ *
+ * The first version of this file defaulted every collection to `permanent`,
+ * reasoning that the dangerous direction is deleting something unrecoverable.
+ * **That reasoning was wrong here, and it made the purge a no-op.**
+ *
+ * This site has never gone live. There are no real customers, no real orders
+ * and no real payouts — every user, store, listing, auction, order, bid and
+ * review in the seed was added TO EXERCISE THE PLATFORM. Classifying them
+ * `permanent` means "cannot be cleared", which is precisely the opposite of
+ * why the field was asked for.
+ *
+ * So the default is `test`, and `permanent` is the **narrow** exception: the
+ * handful of collections that are genuinely content rather than scaffolding.
+ *
+ * ## 🛑 AND `isTestData` IS NOT DERIVED FROM THIS — that was the second bug
+ *
+ * The first version wrote `isTestData: true` for every `test` row. That would
+ * have **hidden the entire demo catalogue from the public**, because
+ * `hidePublicTestData` filters on exactly that field — 70 products, 416
+ * categories and every store would have vanished from every public page while
+ * the summary line read `created 2513, errors 0`.
+ *
+ * The two concerns are orthogonal and must stay separate:
+ *
+ * | Question | Field |
+ * |---|---|
+ * | May a purge delete this row? | **`seedPurpose`** (here) |
+ * | Should the public be able to SEE this row? | **`isTestData`** + `testDataExpiresAt` |
+ *
+ * A demo product is `test` (clearable) **and visible**. A tester-sandbox
+ * cross-store fixture is `test` **and hidden**. Those are different rows with
+ * different needs, and one field cannot answer both.
+ *
+ * `isTestData` therefore stays an explicit per-row opt-in, authored via
+ * `testDataExpiresAt()` in `./test-data-ttl.ts`, and this file never writes it.
+ *
+ * ## What it replaces
+ *
+ * Measured 2026-10-12, before this file existed: **47** seed data files, of
+ * which **one** carried any permanence marker; `isTestData` declared on **5**
+ * schemas; and `TEST_DATA_COLLECTIONS` listing **`offers`**, whose schema does
+ * not declare the field at all, so that entry could only ever match zero rows.
+ * `users`, `orders`, `faqs`, `reviews`, `bids`, `payouts` and `carts` had no
+ * marker and no purge path — and users and orders are the two that were named.
+ */
+/**
+ * Why a seeded row exists — i.e. what a purge is allowed to do with it.
+ *
+ * 🛑 Not a severity scale. Three different answers to one question: never,
+ * on request, and only on an explicit full purge.
+ */
+export type SeedPurpose = 
+/**
+ * Clearable test data. **The default**, and what almost everything is.
+ *
+ * Users, stores, listings, auctions, orders, bids, reviews, offers, carts,
+ * payouts — everything seeded to exercise a path rather than to be read as
+ * content. `appkit-seed purge` removes these and nothing else.
+ *
+ * 🛑 `test` says nothing about PUBLIC VISIBILITY. A demo product is `test`
+ * and fully visible; that is what makes the demo a demo. Hiding a row from
+ * the public is `isTestData`, which is a separate decision (see the header).
+ */
+"test"
+/**
+ * Real content. **A purge must NEVER remove it**, because re-creating it is
+ * not a re-seed, it is authoring.
+ *
+ * The test to apply: *if clearing this means somebody has to WRITE it again
+ * rather than re-run a loader, it is permanent.*
+ *
+ * That is why the **tester checklist cases** are in here and not in some
+ * harness tier — they are the real catalogue of issues the testers test
+ * against and keep updating, which is authored content that happens to be
+ * about testing. Its 1,162 cases are no more disposable than the 85 FAQs.
+ */
+ | "permanent";
+/**
+ * `Record<SeedPurpose, true>`, so a third value is a compile error in every map
+ * keyed on the union rather than a silent gap (Root Cause #61).
+ */
+export declare const SEED_PURPOSE_VALUES: Record<SeedPurpose, true>;
+export declare const ALL_SEED_PURPOSES: SeedPurpose[];
+export declare function isSeedPurpose(value: unknown): value is SeedPurpose;
+/**
+ * 🛑 There is deliberately NO third `fixture` tier.
+ *
+ * An earlier draft had one, meaning "clearable but only by an explicit full
+ * purge", intended for the tester checklist. Once the cases were correctly
+ * classified as permanent content it had **nothing in it** — and a union member
+ * with no members is the dead-enum-value shape this codebase keeps paying for:
+ * a filter chip whose value no row carries returns zero rows forever and reads
+ * as a working control (Root Cause #33), and nine section types that exist in a
+ * dropdown and have never rendered (F1 #20).
+ *
+ * Two values answer the question that was actually asked. If a genuine third
+ * case appears, add it then — with a row that needs it.
+ */
+export declare const PURGEABLE: Record<SeedPurpose, boolean>;
+/**
+ * The per-collection default, keyed on `COLLECTION_MAP`'s keys in
+ * `appkit/scripts/seed-cli.mjs`.
+ *
+ * 🛑 Typed `Record<string, SeedPurpose>` rather than a closed union of
+ * collection names, and that is a deliberate trade: the collection list lives
+ * in a `.mjs` script that cannot be imported for its types, so a closed union
+ * here would be a fifth hand-written copy of it — the thing this file exists to
+ * stop. `audit-seed-purpose` cross-checks the two sets instead, which catches
+ * both a missing entry and a dead one.
+ *
+ * **Anything absent defaults to `test`**, so a collection added later is
+ * clearable rather than quietly permanent. That is the right fail direction on
+ * a site with no real data: the cost of clearing something re-seedable is one
+ * command, and the cost of being unable to clear it is the state this replaced.
+ */
+export declare const SEED_COLLECTION_PURPOSE: Record<string, SeedPurpose>;
+/** A seeded row may override its collection's default inline. */
+export interface WithSeedPurpose {
+    seedPurpose?: SeedPurpose;
+}
+/**
+ * The row's own declaration wins; otherwise the collection default; otherwise
+ * `test`.
+ */
+export declare function resolveSeedPurpose(collection: string, row?: WithSeedPurpose | null): SeedPurpose;
+export interface SeedPurposeFields {
+    seedPurpose: SeedPurpose;
+}
+/**
+ * The fields to write for a purpose — exactly one.
+ *
+ * 🛑 It does **not** touch `isTestData` or `testDataExpiresAt`, and that
+ * restraint is the whole correction described in the header: deriving
+ * `isTestData` from `test` would have hidden every seeded product, category and
+ * store from the public site while reporting a clean load.
+ *
+ * Kept as a function rather than inlined so there is one place to look when
+ * someone asks "what does a purpose actually write?", and so the next field
+ * (if one is ever justified) lands in one place.
+ */
+export declare function seedPurposeFields(purpose: SeedPurpose): SeedPurposeFields;
+/**
+ * Stamp a row for writing. The one function every loader calls, so the CLI and
+ * `runSeed` cannot disagree about what a purpose means — Root Cause #75's shape
+ * on the seed axis (a rule reachable by copy-paste gets copied, and the copy
+ * made before a branch was added never learns about it).
+ *
+ * Returns a NEW object; the seed arrays are module-level constants re-imported
+ * on every CLI invocation and must not be mutated.
+ */
+export declare function stampSeedPurpose<T extends WithSeedPurpose>(collection: string, row: T): T & SeedPurposeFields;
+/**
+ * Mark a whole array as something other than its collection default — the
+ * readable way to say "this file is permanent" (or "this file is fixtures")
+ * without repeating the field on every row.
+ *
+ * Sets the row-level override, so it beats the collection default and is
+ * visible at the call site.
+ */
+export declare function asSeedPurpose<T>(purpose: SeedPurpose, rows: readonly T[]): Array<T & WithSeedPurpose>;
+/**
+ * How long a `test` row survives before a purge may take it.
+ *
+ * 🛑 STOP-GAP, added 2026-10-12 to unbreak the build — NOT a design decision,
+ * and whoever owns `seedPurpose` should replace it with the real declaration.
+ *
+ * This file arrived with `src/seed/index.ts:247` and `src/index.ts:1935` ALREADY
+ * re-exporting `SEED_TEST_TTL_DAYS` from here while nothing declared it, so
+ * `tsc` failed with TS2305 and appkit did not compile at all — the half-finished
+ * public-surface rename of Root Cause #20, where the barrel landed without the
+ * definition. (The same commit also carried `sxdexport const` on line 149,
+ * i.e. stray keystrokes, which is the likelier reading of what happened here.)
+ *
+ * Aliased to the EXISTING value rather than given a fresh number: a retention
+ * window is a product decision and inventing one would have been worse than the
+ * compile error. `TEST_DATA_TTL_DAYS` is 7 and is what `testDataExpiresAt()`
+ * already stamps on every test row, so this is behaviour-preserving by
+ * construction — and when the two names are reconciled, there is exactly one
+ * number to change.
+ */
+export { TEST_DATA_TTL_DAYS as SEED_TEST_TTL_DAYS } from "./test-data-ttl";

package/dist/seed/seed-purpose.js

@@ -0,0 +1,265 @@
+/**
+ * ── Seed provenance: may a purge delete this row? ───────────────────────────
+ *
+ * Every document written by `appkit-seed` carries a `seedPurpose`, and it is
+ * the ONE declaration of whether a row is real content or clearable test data.
+ * The purge reads it; nothing else decides.
+ *
+ * ## The rule this exists to enforce
+ *
+ * 🛑 **Content comes from a seed FILE, never from a direct database write.**
+ * Not a one-off script, not a console paste, not a `node -e`. A row that exists
+ * only in Firestore cannot be reviewed in a diff, cannot be recreated after a
+ * purge, and cannot be found by anyone who did not watch it being written —
+ * and when it references other rows, nothing updates it when those move.
+ *
+ * `seedPurpose` makes that rule *checkable*: a document with no `seedPurpose`
+ * was not written by the seeder, so the purge will not touch it.
+ *
+ * ## 🛑 THE DEFAULT IS `test`, AND THE OPPOSITE WAS THIS FILE'S FIRST BUG
+ *
+ * The first version of this file defaulted every collection to `permanent`,
+ * reasoning that the dangerous direction is deleting something unrecoverable.
+ * **That reasoning was wrong here, and it made the purge a no-op.**
+ *
+ * This site has never gone live. There are no real customers, no real orders
+ * and no real payouts — every user, store, listing, auction, order, bid and
+ * review in the seed was added TO EXERCISE THE PLATFORM. Classifying them
+ * `permanent` means "cannot be cleared", which is precisely the opposite of
+ * why the field was asked for.
+ *
+ * So the default is `test`, and `permanent` is the **narrow** exception: the
+ * handful of collections that are genuinely content rather than scaffolding.
+ *
+ * ## 🛑 AND `isTestData` IS NOT DERIVED FROM THIS — that was the second bug
+ *
+ * The first version wrote `isTestData: true` for every `test` row. That would
+ * have **hidden the entire demo catalogue from the public**, because
+ * `hidePublicTestData` filters on exactly that field — 70 products, 416
+ * categories and every store would have vanished from every public page while
+ * the summary line read `created 2513, errors 0`.
+ *
+ * The two concerns are orthogonal and must stay separate:
+ *
+ * | Question | Field |
+ * |---|---|
+ * | May a purge delete this row? | **`seedPurpose`** (here) |
+ * | Should the public be able to SEE this row? | **`isTestData`** + `testDataExpiresAt` |
+ *
+ * A demo product is `test` (clearable) **and visible**. A tester-sandbox
+ * cross-store fixture is `test` **and hidden**. Those are different rows with
+ * different needs, and one field cannot answer both.
+ *
+ * `isTestData` therefore stays an explicit per-row opt-in, authored via
+ * `testDataExpiresAt()` in `./test-data-ttl.ts`, and this file never writes it.
+ *
+ * ## What it replaces
+ *
+ * Measured 2026-10-12, before this file existed: **47** seed data files, of
+ * which **one** carried any permanence marker; `isTestData` declared on **5**
+ * schemas; and `TEST_DATA_COLLECTIONS` listing **`offers`**, whose schema does
+ * not declare the field at all, so that entry could only ever match zero rows.
+ * `users`, `orders`, `faqs`, `reviews`, `bids`, `payouts` and `carts` had no
+ * marker and no purge path — and users and orders are the two that were named.
+ */
+/**
+ * `Record<SeedPurpose, true>`, so a third value is a compile error in every map
+ * keyed on the union rather than a silent gap (Root Cause #61).
+ */
+export const SEED_PURPOSE_VALUES = {
+    test: true,
+    permanent: true,
+};
+export const ALL_SEED_PURPOSES = Object.keys(SEED_PURPOSE_VALUES);
+export function isSeedPurpose(value) {
+    return typeof value === "string" && value in SEED_PURPOSE_VALUES;
+}
+/**
+ * 🛑 There is deliberately NO third `fixture` tier.
+ *
+ * An earlier draft had one, meaning "clearable but only by an explicit full
+ * purge", intended for the tester checklist. Once the cases were correctly
+ * classified as permanent content it had **nothing in it** — and a union member
+ * with no members is the dead-enum-value shape this codebase keeps paying for:
+ * a filter chip whose value no row carries returns zero rows forever and reads
+ * as a working control (Root Cause #33), and nine section types that exist in a
+ * dropdown and have never rendered (F1 #20).
+ *
+ * Two values answer the question that was actually asked. If a genuine third
+ * case appears, add it then — with a row that needs it.
+ */
+export const PURGEABLE = {
+    test: true,
+    permanent: false,
+};
+/**
+ * The per-collection default, keyed on `COLLECTION_MAP`'s keys in
+ * `appkit/scripts/seed-cli.mjs`.
+ *
+ * 🛑 Typed `Record<string, SeedPurpose>` rather than a closed union of
+ * collection names, and that is a deliberate trade: the collection list lives
+ * in a `.mjs` script that cannot be imported for its types, so a closed union
+ * here would be a fifth hand-written copy of it — the thing this file exists to
+ * stop. `audit-seed-purpose` cross-checks the two sets instead, which catches
+ * both a missing entry and a dead one.
+ *
+ * **Anything absent defaults to `test`**, so a collection added later is
+ * clearable rather than quietly permanent. That is the right fail direction on
+ * a site with no real data: the cost of clearing something re-seedable is one
+ * command, and the cost of being unable to clear it is the state this replaced.
+ */
+export const SEED_COLLECTION_PURPOSE = {
+    /*
+     * ── permanent: content, not scaffolding ─────────────────────────────────
+     *
+     * The test: if clearing it means someone has to WRITE it again rather than
+     * re-run a loader, it is permanent. Five collections pass that test.
+     */
+    /* 85 answers carrying real figures — the ₹10 fee cap, the 5% GST worked
+     * example, the 48-hour damage window. Explicitly asked to be permanent. */
+    faqs: "permanent",
+    /* 416 nodes, 6 roots. Every product's `categorySlugs` chain points into it,
+     * so clearing it orphans the catalogue — which is exactly what happened when
+     * a purge-then-load wrote 0 of 416 and 70 products pointed at nothing. */
+    categories: "permanent",
+    /* Real HSN codes and GST rates. A wrong rate on a real invoice is a
+     * compliance matter, not a fixture. */
+    taxCodes: "permanent",
+    /* The ~169-term feature vocabulary: condition, authenticity, release, type,
+     * spin, grade, chase. Hand-curated from the crawl. */
+    productFeatures: "permanent",
+    /* Branding, fees, commissions, watermark, legal pages, and the AES-encrypted
+     * credentials. 🛑 A purge here would destroy live API keys. */
+    siteSettings: "permanent",
+    /*
+     * 🛑 The tester checklist cases are PERMANENT CONTENT, not scaffolding.
+     *
+     * 1,162 authored cases, each a six-part procedure with an explicit
+     * before → after — the real catalogue of issues the testers test against and
+     * keep updating. Clearing them is not a re-seed, it is losing the authoring,
+     * and this project's primary quality gate is that catalogue.
+     *
+     * Their RESPONSES are the opposite: per-run verdicts, regenerated every
+     * sweep, and the whole point of clearing between runs. So the two halves of
+     * one feature land in different tiers, which is the case the collection-level
+     * default is for.
+     */
+    testerChecklistItems: "permanent",
+    testerChecklistResponses: "test",
+    /*
+     * ── test: everything else ───────────────────────────────────────────────
+     *
+     * Listed explicitly rather than left to the fallback, because an explicit
+     * table is reviewable and `audit-seed-purpose` can then tell a MISSING entry
+     * from a deliberate one.
+     */
+    users: "test",
+    addresses: "test",
+    storeAddresses: "test",
+    sessions: "test",
+    stores: "test",
+    products: "test",
+    orders: "test",
+    reviews: "test",
+    bids: "test",
+    offers: "test",
+    carts: "test",
+    wishlists: "test",
+    history: "test",
+    payouts: "test",
+    coupons: "test",
+    couponUsage: "test",
+    notifications: "test",
+    supportTickets: "test",
+    catalogueItems: "test",
+    blogPosts: "test",
+    events: "test",
+    eventEntries: "test",
+    groupedListings: "test",
+    scammerProfiles: "test",
+    carousels: "test",
+    carouselSlides: "test",
+    homepageSections: "test",
+    procurementShipments: "test",
+    shipmentLots: "test",
+    shipmentItems: "test",
+    payoutMethods: "test",
+    shippingConfigs: "test",
+    analyticsCards: "test",
+    analyticsAlerts: "test",
+    storeCategories: "test",
+    listingTemplates: "test",
+    moderationQueue: "test",
+    reports: "test",
+    itemRequests: "test",
+    storeGoogleConfig: "test",
+};
+/**
+ * The row's own declaration wins; otherwise the collection default; otherwise
+ * `test`.
+ */
+export function resolveSeedPurpose(collection, row) {
+    if (row && isSeedPurpose(row.seedPurpose))
+        return row.seedPurpose;
+    const declared = SEED_COLLECTION_PURPOSE[collection];
+    return isSeedPurpose(declared) ? declared : "test";
+}
+/**
+ * The fields to write for a purpose — exactly one.
+ *
+ * 🛑 It does **not** touch `isTestData` or `testDataExpiresAt`, and that
+ * restraint is the whole correction described in the header: deriving
+ * `isTestData` from `test` would have hidden every seeded product, category and
+ * store from the public site while reporting a clean load.
+ *
+ * Kept as a function rather than inlined so there is one place to look when
+ * someone asks "what does a purpose actually write?", and so the next field
+ * (if one is ever justified) lands in one place.
+ */
+export function seedPurposeFields(purpose) {
+    return { seedPurpose: purpose };
+}
+/**
+ * Stamp a row for writing. The one function every loader calls, so the CLI and
+ * `runSeed` cannot disagree about what a purpose means — Root Cause #75's shape
+ * on the seed axis (a rule reachable by copy-paste gets copied, and the copy
+ * made before a branch was added never learns about it).
+ *
+ * Returns a NEW object; the seed arrays are module-level constants re-imported
+ * on every CLI invocation and must not be mutated.
+ */
+export function stampSeedPurpose(collection, row) {
+    return { ...row, ...seedPurposeFields(resolveSeedPurpose(collection, row)) };
+}
+/**
+ * Mark a whole array as something other than its collection default — the
+ * readable way to say "this file is permanent" (or "this file is fixtures")
+ * without repeating the field on every row.
+ *
+ * Sets the row-level override, so it beats the collection default and is
+ * visible at the call site.
+ */
+export function asSeedPurpose(purpose, rows) {
+    return rows.map((row) => ({ ...row, seedPurpose: purpose }));
+}
+/**
+ * How long a `test` row survives before a purge may take it.
+ *
+ * 🛑 STOP-GAP, added 2026-10-12 to unbreak the build — NOT a design decision,
+ * and whoever owns `seedPurpose` should replace it with the real declaration.
+ *
+ * This file arrived with `src/seed/index.ts:247` and `src/index.ts:1935` ALREADY
+ * re-exporting `SEED_TEST_TTL_DAYS` from here while nothing declared it, so
+ * `tsc` failed with TS2305 and appkit did not compile at all — the half-finished
+ * public-surface rename of Root Cause #20, where the barrel landed without the
+ * definition. (The same commit also carried `sxdexport const` on line 149,
+ * i.e. stray keystrokes, which is the likelier reading of what happened here.)
+ *
+ * Aliased to the EXISTING value rather than given a fresh number: a retention
+ * window is a product decision and inventing one would have been worse than the
+ * compile error. `TEST_DATA_TTL_DAYS` is 7 and is what `testDataExpiresAt()`
+ * already stamps on every test row, so this is behaviour-preserving by
+ * construction — and when the two names are reconciled, there is exactly one
+ * number to change.
+ */
+export { TEST_DATA_TTL_DAYS as SEED_TEST_TTL_DAYS } from "./test-data-ttl.js";

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

@@ -13,9 +13,9 @@
  * @tag consumers:seed/index.ts,seed/runner.ts
  * @tag sideEffects:none
  */
-import { getSeedLocale } from "./seed-market-config";
+import { getSeedLocale } from "./seed-market-config.js";
 const _locale = getSeedLocale();
-import { SESSION_COLLECTION, } from "../features/auth/schemas";
+import { SESSION_COLLECTION, } from "../features/auth/schemas/index.js";
 const NOW = new Date();
 const daysAgo = (n) => new Date(NOW.getTime() - n * 86400000);
 const daysAhead = (n) => new Date(NOW.getTime() + n * 86400000);

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

@@ -15,7 +15,7 @@
  *   shipmentLotsSeedData  — Array of Partial<ShipmentLot>
  *   shipmentItemsSeedData — Array of Partial<ShipmentItem>
  */
-import { allocateShipmentCosts } from "../features/shipments/utils/cost-allocation";
+import { allocateShipmentCosts } from "../features/shipments/utils/cost-allocation.js";
 const NOW = new Date();
 const daysAgo = (n) => new Date(NOW.getTime() - n * 86400000);
 const daysFromNow = (n) => new Date(NOW.getTime() + n * 86400000);

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

@@ -12,9 +12,9 @@
  * @tag consumers:seed/index.ts,seed/runner.ts
  * @tag sideEffects:none
  */
-import { seedExtMedia, seedPhoto } from "./_helpers/media";
-import { ROUTES } from "../next/routing/route-map";
-import { DEFAULT_AUCTION_BID_INCREMENT_TIERS } from "../_internal/shared/features/auctions/config";
+import { seedExtMedia, seedPhoto } from "./_helpers/media.js";
+import { ROUTES } from "../next/routing/route-map.js";
+import { DEFAULT_AUCTION_BID_INCREMENT_TIERS } from "../_internal/shared/features/auctions/config.js";
 const NOW = new Date();
 const daysAgo = (n) => new Date(NOW.getTime() - n * 86400000);
 const adPlacementsSeed = [
@@ -311,6 +311,9 @@ export const siteSettingsSeedData = {
     shipping: {
         estimatedDays: 7,
         minOrderForFree: 999,
+        // C5c — manual until a Shiprocket provider AND credentials exist. A
+        // seeded `shiprocket` would throw at boot by design.
+        provider: "manual",
     },
     returns: {
         windowDays: 7,
@@ -429,6 +432,30 @@ export const siteSettingsSeedData = {
         autoExtendWindowMinutes: 5,
         settlementGracePeriodHours: 24,
     },
+    /*
+     * 🛑 There is deliberately NO `gst` block here, and it must stay that way.
+     *
+     * It looks like the `auctionConfig` defect one block up — a key the schema
+     * default declares and the seed does not, so `appkit-seed load` can never
+     * create it — but the two are opposite cases, and seeding this one would be
+     * destructive rather than corrective.
+     *
+     *   `auctionConfig` was broken BY its absence: every reader resolved
+     *   `?? []` and fell back to a ₹1 bid increment, so the feature was
+     *   measurably wrong until the key existed.
+     *
+     *   `gst` is CORRECT when absent: readers do `settings.gst?.enabled ??
+     *   false`, which is the intended default — product GST off until a real
+     *   registration is entered.
+     *
+     * And the seed writes `set(..., { merge: true })`, so declaring
+     * `gst: { gstin: "", ... }` here would overwrite a live GSTIN with an empty
+     * string on **every** subsequent `appkit-seed load`. A registration number
+     * is admin-entered identity, not platform config; the only writer is the
+     * Site Settings → Gst tab, and `/api/admin/site` now refuses to enable GST
+     * until the GSTIN passes its own check digit and the legal name and address
+     * are present (see `validateGstEnablement`).
+     */
     commissions: {
         platformFeePercent: 5,
         gstPercent: 18,
@@ -446,6 +473,9 @@ export const siteSettingsSeedData = {
         shipmentProtectionFeeEnabled: true,
         shipmentProtectionFeePercent: 2,
         shipmentProtectionFeeMin: 30,
+        saleProtectionFeeEnabled: true,
+        saleProtectionFeePercent: 3,
+        saleProtectionFeeMin: 49,
         sellerShippingFixed: 0,
         platformShippingPercent: 0,
         platformShippingFixedMin: 0,

package/dist/seed/store-addresses-seed-data.js

@@ -13,7 +13,7 @@
  * @tag consumers:seed/index.ts,seed/runner.ts
  * @tag sideEffects:none
  */
-import { getSeedLocale, getDefaultPhonePrefix } from "./seed-market-config";
+import { getSeedLocale, getDefaultPhonePrefix } from "./seed-market-config.js";
 const _locale = getSeedLocale();
 const _phonePrefix = getDefaultPhonePrefix();
 const NOW = new Date();

package/dist/seed/store-extensions-seed-data.js

@@ -16,7 +16,7 @@
  * @tag consumers:seed/index.ts,seed/runner.ts
  * @tag sideEffects:none
  */
-import { seedPhoto } from "./_helpers/media";
+import { seedPhoto } from "./_helpers/media.js";
 const NOW = new Date();
 // ───── payoutMethods (4 records) ──────────────────────────────────────────
 export const payoutMethodsSeedData = [
@@ -125,10 +125,16 @@ export const analyticsCardsSeedData = [
 ];
 // ───── analyticsAlerts (4 records) ────────────────────────────────────────
 export const analyticsAlertsSeedData = [
-    { id: "alert-low-stock-arena", scope: "seller", ownerId: "user-tyson-blader", label: "Low stock", metric: "min-stock", operator: "<", threshold: 5, windowHours: 24, isActive: true, notifyChannels: ["in-app", "email"] },
-    { id: "alert-no-sales-arena", scope: "seller", ownerId: "user-tyson-blader", label: "Zero sales 48h", metric: "orders-window", operator: "==", threshold: 0, windowHours: 48, isActive: true, notifyChannels: ["in-app"] },
-    { id: "alert-platform-error-rate", scope: "admin", ownerId: "user-admin-letitrip", label: "API error rate > 5%", metric: "api-error-rate", operator: ">", threshold: 0.05, windowHours: 1, isActive: true, notifyChannels: ["in-app", "email", "whatsapp"] },
-    { id: "alert-fraud-surge", scope: "admin", ownerId: "user-admin-letitrip", label: "Fraud reports surge", metric: "reports-1h", operator: ">", threshold: 10, windowHours: 1, isActive: true, notifyChannels: ["in-app", "email"] },
+    // 🛑 Re-keyed in C3a. These four carried `min-stock`, `orders-window`,
+    // `api-error-rate` and `reports-1h` — four kebab-case values that shared ZERO
+    // tokens with the seven snake_case ones the seller picker offered, and which
+    // nothing read because no evaluator existed. `api-error-rate` is gone rather
+    // than renamed: a RATE needs a denominator this platform does not record, so
+    // seeding it would be re-promising what the first version could not keep.
+    { id: "alert-low-stock-arena", scope: "seller", ownerId: "user-tyson-blader", label: "Low stock", metric: "low_stock", operator: ">", threshold: 0, windowHours: 24, isActive: true, notifyChannels: ["in-app", "email"] },
+    { id: "alert-no-sales-arena", scope: "seller", ownerId: "user-tyson-blader", label: "Zero sales 48h", metric: "orders_count", operator: "==", threshold: 0, windowHours: 48, isActive: true, notifyChannels: ["in-app"] },
+    { id: "alert-platform-pending-moderation", scope: "admin", ownerId: "user-admin-letitrip", label: "Listings awaiting review", metric: "pending_moderation", operator: ">", threshold: 5, windowHours: 1, isActive: true, notifyChannels: ["in-app", "email"] },
+    { id: "alert-fraud-surge", scope: "admin", ownerId: "user-admin-letitrip", label: "Open reports surge", metric: "open_reports", operator: ">", threshold: 10, windowHours: 1, isActive: true, notifyChannels: ["in-app", "email"] },
 ];
 // ───── storeCategories (4 records) ────────────────────────────────────────
 export const storeCategoriesSeedData = [

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

@@ -16,9 +16,9 @@
  * @tag consumers:seed/runner.ts
  * @tag sideEffects:none
  */
-import { withStoreSearchTxt } from "./_helpers/search-txt-wrappers";
-import { STORE_FIELDS } from "../constants/field-names";
-import { seedPhoto } from "./_helpers/media";
+import { withStoreSearchTxt } from "./_helpers/search-txt-wrappers.js";
+import { STORE_FIELDS } from "../constants/field-names.js";
+import { seedPhoto } from "./_helpers/media.js";
 const NOW = new Date();
 const daysAgo = (n) => new Date(NOW.getTime() - n * 86400000);
 /**

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

@@ -12,8 +12,8 @@
  * @tag consumers:seed/index.ts,seed/runner.ts
  * @tag sideEffects:none
  */
-import { SUPPORT_TICKET_FIELDS } from "../constants/field-names";
-import { buildSearchTxt } from "../utils/search-txt";
+import { SUPPORT_TICKET_FIELDS } from "../constants/field-names.js";
+import { buildSearchTxt } from "../utils/search-txt.js";
 function msg(id, authorId, authorRole, body, daysAgo) {
     const createdAt = new Date(Date.now() - daysAgo * 24 * 60 * 60 * 1000);
     return { id, authorId, authorRole, body, createdAt };

package/dist/seed/tax-codes-seed-data.d.ts

@@ -0,0 +1,34 @@
+/**
+ * Tax Codes Seed Data
+ *
+ * The HSN codes this catalogue actually needs, and nothing speculative.
+ *
+ * ## 🛑 Only chapter 9503 is VERIFIED
+ *
+ * The four 9503 rates below were confirmed against the current schedule. The
+ * chapters for printed matter (4911) and playing cards (9504) are correct
+ * chapters for merchandise we sell, and their RATES ARE NOT CONFIRMED — the
+ * toys rates themselves moved in the 2025 revision. They are deliberately NOT
+ * seeded: a wrong HSN on a real invoice is worse than an absent one, and an
+ * absent code leaves `gstRate` undefined, which every reader already handles.
+ *
+ * Add them as a one-line seed change once someone has checked the schedule.
+ *
+ * ## The 18% row is load-bearing
+ *
+ * `tax-hsn-95030010` exists so the catalogue has at least one rate that is not
+ * 5%. Without it a 5%-only dataset cannot distinguish "the rate is being
+ * applied" from "the rate is hardcoded", and the B6 gate — the Tax row
+ * rendering on a real order for the first time — would pass either way.
+ *
+ * ## The 0% row is an EXEMPTION, not a missing value
+ *
+ * `tax-exempt-0` carries no HSN, which is legal only at rate 0 (enforced in
+ * both the form schema and the repository). It covers the live
+ * plants/animals listings. `gstRate: 0` and `gstRate: undefined` mean
+ * different things throughout — see the field's own comment.
+ *
+ * id === slug, prefix: tax-
+ */
+import type { TaxCodeDocument } from "../features/tax-codes/schemas/firestore";
+export declare const taxCodesSeedData: TaxCodeDocument[];