@mohasinac/appkit 4.58.0 → 4.60.0

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

@@ -1,16 +0,0 @@
-import type { SupportTicketPlain } from "../features/support/schemas/firestore";
-/**
- * Derive `searchTxt` for every record from its own subject.
- *
- * The seed writes documents raw via `batch.set()` — both `seed/runner.ts` and
- * `seed-cli.mjs` — bypassing the repository, which is the only thing that
- * builds tokens. Without this every seeded ticket would have no `searchTxt` at
- * all and `array-contains` would match zero documents, for every query,
- * forever. That is exactly how FAQ search was found broken.
- *
- * Computed with the SAME `buildSearchTxt` over the SAME field the repository
- * uses, so a seeded ticket and a user-created one are byte-identical. Pure
- * 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<SupportTicketPlain>[];

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

@@ -1,239 +0,0 @@
-/*
- * WHY: Seeds support tickets for the Beyblade marketplace — 8 tickets across all statuses.
- * WHAT: open (2), in_progress (2), waiting_on_user (1), resolved (2), closed (1).
- *
- * EXPORTS:
- *   supportTicketsSeedData — Array of Partial<SupportTicketPlain> for seed runner
- *
- * @tag domain:support
- * @tag layer:seed
- * @tag pattern:none
- * @tag access:server-only
- * @tag consumers:seed/index.ts,seed/runner.ts
- * @tag sideEffects:none
- */
-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 };
-}
-const BASE = Date.now();
-function daysBack(n) {
-    return new Date(BASE - n * 24 * 60 * 60 * 1000);
-}
-/**
- * A timeline entry for the W18 `statusHistory` fixtures.
- *
- * `actorUid` only, never a name — `withHistory` scrubs
- * SUPPORT_TICKET_PII_FIELDS (which includes `assignedToName`) from real
- * writes, so a fixture carrying one would be the single place that is untrue.
- */
-function entry(at, actorRole, trigger, changes, extra) {
-    return { at, actorRole, trigger, changes, ...extra };
-}
-const supportTicketRecords = [
-    // ── 1. Order issue — in progress ─────────────────────────────────────────
-    {
-        id: "ticket-yugi-order-001",
-        userId: "user-yugi-muto",
-        userEmail: "rehan.sheikh@example.com",
-        userDisplayName: "Mock User 3",
-        category: "order_issue",
-        subject: "Order delivered but item is missing from the box",
-        description: "I received order #order-1-20260515-abc123 but the Beyblade Original Dranzer S was not inside — only the outer packaging and bubble wrap were present. Please help.",
-        orderId: "order-1-20260515-abc123",
-        status: SUPPORT_TICKET_FIELDS.STATUS_VALUES.IN_PROGRESS,
-        priority: SUPPORT_TICKET_FIELDS.PRIORITY_VALUES.HIGH,
-        assignedTo: "user-admin-letitrip",
-        assignedToName: "Mock User 1",
-        messages: [
-            msg("msg-yugi-001-u1", "user-yugi-muto", "user", "I received my order but the beyblade was missing! The seal was broken on arrival.", 5),
-            msg("msg-yugi-001-s1", "user-admin-letitrip", "support", "Hi Rehan, we're sorry to hear this. I've raised a claim with the courier. Could you please share a photo of the packaging?", 4),
-            msg("msg-yugi-001-u2", "user-yugi-muto", "user", "Photos attached. The outer tape was clearly cut and resealed.", 3),
-        ],
-        createdAt: daysBack(5),
-        updatedAt: daysBack(3),
-    },
-    // ── 2. Open ticket — refund request ───────────────────────────────────────
-    {
-        id: "ticket-yugi-refund-001",
-        userId: "user-yugi-muto",
-        userEmail: "rehan.sheikh@example.com",
-        userDisplayName: "Mock User 3",
-        category: "refund_request",
-        subject: "Requesting refund for cancelled pre-order",
-        description: "I placed a pre-order for the Beyblade X BX-08 wave 3 months ago. The store has now closed. I would like a full refund of ₹899.",
-        status: SUPPORT_TICKET_FIELDS.STATUS_VALUES.OPEN,
-        priority: SUPPORT_TICKET_FIELDS.PRIORITY_VALUES.NORMAL,
-        messages: [
-            msg("msg-yugi-002-u1", "user-yugi-muto", "user", "The store closed without shipping. I paid via Razorpay. Transaction ID: pay_test_abc123.", 2),
-        ],
-        createdAt: daysBack(2),
-        updatedAt: daysBack(2),
-    },
-    // ── 3. Waiting on user — account recovery ─────────────────────────────────
-    {
-        id: "ticket-kaiba-account-001",
-        userId: "user-seto-kaiba",
-        userEmail: "vivaan.kapoor@example.com",
-        userDisplayName: "Mock User 2",
-        category: "account",
-        subject: "Cannot log in — OTP not arriving on new phone number",
-        description: "I changed my phone number and now OTP for login is going to the old number. I cannot access my account.",
-        status: SUPPORT_TICKET_FIELDS.STATUS_VALUES.WAITING_ON_USER,
-        priority: SUPPORT_TICKET_FIELDS.PRIORITY_VALUES.NORMAL,
-        assignedTo: "user-admin-letitrip",
-        assignedToName: "Mock User 1",
-        messages: [
-            msg("msg-kaiba-001-u1", "user-seto-kaiba", "user", "I'm locked out. My old number is no longer active.", 7),
-            msg("msg-kaiba-001-s1", "user-admin-letitrip", "support", "Hi Vivaan, to verify ownership we need your registered email and last 4 digits of the payment card used on this account. Please reply here.", 6),
-        ],
-        createdAt: daysBack(7),
-        updatedAt: daysBack(6),
-    },
-    // ── 4. Resolved — listing dispute ─────────────────────────────────────────
-    {
-        id: "ticket-yugi-dispute-001",
-        userId: "user-yugi-muto",
-        userEmail: "rehan.sheikh@example.com",
-        userDisplayName: "Mock User 3",
-        category: "listing_dispute",
-        subject: "Product description says mint but tip is heavily worn",
-        description: "The Beyblade Metal Storm Pegasus I received has a rounded, sanded-down tip and scratches on the layer. The listing said mint condition. I want to return it.",
-        status: SUPPORT_TICKET_FIELDS.STATUS_VALUES.RESOLVED,
-        priority: SUPPORT_TICKET_FIELDS.PRIORITY_VALUES.NORMAL,
-        assignedTo: "user-admin-letitrip",
-        assignedToName: "Mock User 1",
-        messages: [
-            msg("msg-yugi-003-u1", "user-yugi-muto", "user", "The tip is clearly not mint. Here are photos showing the wear and scratches.", 12),
-            msg("msg-yugi-003-s1", "user-admin-letitrip", "support", "Thank you for the photos Rehan. We've contacted the seller and initiated a return + full refund.", 11),
-            msg("msg-yugi-003-s2", "user-admin-letitrip", "support", "Refund of ₹2,499 has been processed back to your original payment method. This ticket is now resolved.", 8),
-        ],
-        resolvedAt: daysBack(8),
-        /*
-         * open -> in_progress -> resolved, with the assignment in between.
-         *
-         * `resolvedAt` above was ALREADY in this fixture, and no code path had
-         * ever written it (verified 2026-08-26) — the seed described a shape the
-         * application could not produce. The repository stamps it on the
-         * transition now, so this fixture and reality finally agree.
-         */
-        statusHistory: [
-            entry(daysBack(12), "buyer", "createTicket", {
-                status: { from: null, to: "open" },
-            }, { actorUid: "user-yugi-muto" }),
-            entry(daysBack(11), "admin", "assignTicket", {
-                assignedTo: { from: null, to: "user-admin-letitrip" },
-                status: { from: "open", to: "in_progress" },
-            }, { actorUid: "user-admin-letitrip" }),
-            entry(daysBack(8), "admin", "adminUpdateTicket", {
-                status: { from: "in_progress", to: "resolved" },
-                resolvedAt: { from: null, to: "2026-08-18T00:00:00.000Z" },
-            }, {
-                actorUid: "user-admin-letitrip",
-                reason: "Return accepted and refund processed.",
-            }),
-        ],
-        createdAt: daysBack(12),
-        updatedAt: daysBack(8),
-    },
-    // ── 5. Closed — auction dispute (terminal) ────────────────────────────────
-    {
-        id: "ticket-yugi-auction-001",
-        userId: "user-yugi-muto",
-        userEmail: "rehan.sheikh@example.com",
-        userDisplayName: "Mock User 3",
-        category: "auction_dispute",
-        subject: "Winning bid was removed from Dragoon Storm auction",
-        description: "I won the Beyblade Original Dragoon Storm auction but my winning bid was removed without explanation.",
-        status: SUPPORT_TICKET_FIELDS.STATUS_VALUES.CLOSED,
-        priority: SUPPORT_TICKET_FIELDS.PRIORITY_VALUES.LOW,
-        messages: [
-            msg("msg-yugi-004-u1", "user-yugi-muto", "user", "My winning bid was cancelled. I have a screenshot.", 20),
-            msg("msg-yugi-004-s1", "user-admin-letitrip", "support", "Hi Rehan, after reviewing the auction logs we found a duplicate bid was submitted. The correct winning bid remains active. No action needed.", 18),
-            msg("msg-yugi-004-u2", "user-yugi-muto", "user", "Understood, thanks for clarifying.", 17),
-        ],
-        closedAt: daysBack(17),
-        createdAt: daysBack(20),
-        updatedAt: daysBack(17),
-    },
-    // ── 6. Open — general inquiry ─────────────────────────────────────────────
-    {
-        id: "ticket-kaiba-general-001",
-        userId: "user-seto-kaiba",
-        userEmail: "vivaan.kapoor@example.com",
-        userDisplayName: "Mock User 2",
-        category: "general",
-        subject: "How do I list a sealed limited-edition beyblade?",
-        description: "I want to list my sealed limited-edition Metal Lightning L-Drago with the authenticity certificate visible and verified. What are the steps?",
-        status: SUPPORT_TICKET_FIELDS.STATUS_VALUES.OPEN,
-        priority: SUPPORT_TICKET_FIELDS.PRIORITY_VALUES.LOW,
-        messages: [
-            msg("msg-kaiba-002-u1", "user-seto-kaiba", "user", "I've read the FAQ but couldn't find the exact authenticity verification requirements for sealed pieces.", 1),
-        ],
-        createdAt: daysBack(1),
-        updatedAt: daysBack(1),
-    },
-    // ── 7. Resolved — escalated fraud report (admin handled) ──────────────────
-    {
-        id: "ticket-yugi-fraud-001",
-        userId: "user-yugi-muto",
-        userEmail: "rehan.sheikh@example.com",
-        userDisplayName: "Mock User 3",
-        category: "scam_report",
-        subject: "Seller sent empty box and is now unreachable",
-        description: "I paid ₹2,999 for a Beyblade Burst Regalia Genesis via Razorpay. The seller has not responded in 7 days and the tracking shows the box was 40g — way too light for a sealed spinner.",
-        status: SUPPORT_TICKET_FIELDS.STATUS_VALUES.RESOLVED,
-        priority: SUPPORT_TICKET_FIELDS.PRIORITY_VALUES.HIGH,
-        assignedTo: "user-admin-letitrip",
-        assignedToName: "Mock User 1",
-        messages: [
-            msg("msg-yugi-005-u1", "user-yugi-muto", "user", "I have the weight receipt from Delhivery. 40g is impossible for a sealed beyblade. The seller is not replying on messages or phone.", 10),
-            msg("msg-yugi-005-s1", "user-admin-letitrip", "support", "Hi Rehan, I have escalated this to our admin team for review as it qualifies as a potential fraud case. You will hear back within 24 hours.", 9),
-            msg("msg-yugi-005-a1", "user-admin-letitrip", "support", "Hi Rehan, this is the LetItRip admin. I have reviewed the shipment weight log and the seller communication history. We are initiating a full refund of ₹2,999 under our buyer protection policy. The seller account has been suspended pending investigation.", 8),
-            msg("msg-yugi-005-u2", "user-yugi-muto", "user", "Thank you so much. I really appreciate the quick escalation.", 7),
-        ],
-        resolvedAt: daysBack(7),
-        createdAt: daysBack(10),
-        updatedAt: daysBack(7),
-    },
-    // ── 8. In-progress — seller store suspension appeal (admin handling) ──────
-    {
-        id: "ticket-kaiba-ban-appeal-001",
-        userId: "user-seto-kaiba",
-        userEmail: "vivaan.kapoor@example.com",
-        userDisplayName: "Mock User 2",
-        category: "account",
-        subject: "My account was flagged — I believe it was a mistake",
-        description: "My account was flagged 2 days ago. I received no email explanation. I have never violated any policy. Please review.",
-        status: SUPPORT_TICKET_FIELDS.STATUS_VALUES.IN_PROGRESS,
-        priority: SUPPORT_TICKET_FIELDS.PRIORITY_VALUES.HIGH,
-        assignedTo: "user-admin-letitrip",
-        assignedToName: "Mock User 1",
-        messages: [
-            msg("msg-kaiba-003-u1", "user-seto-kaiba", "user", "I'm a legitimate buyer. I have a clean order history and never had a single complaint. Please explain the flag.", 2),
-            msg("msg-kaiba-003-a1", "user-admin-letitrip", "support", "Hi Vivaan, your account was flagged as part of an automatic fraud check triggered by an unusual login pattern. I am manually reviewing your account history. Please share the last 4 digits of the card used for your most recent Razorpay payment for verification.", 1),
-        ],
-        createdAt: daysBack(2),
-        updatedAt: daysBack(1),
-    },
-];
-/**
- * Derive `searchTxt` for every record from its own subject.
- *
- * The seed writes documents raw via `batch.set()` — both `seed/runner.ts` and
- * `seed-cli.mjs` — bypassing the repository, which is the only thing that
- * builds tokens. Without this every seeded ticket would have no `searchTxt` at
- * all and `array-contains` would match zero documents, for every query,
- * forever. That is exactly how FAQ search was found broken.
- *
- * Computed with the SAME `buildSearchTxt` over the SAME field the repository
- * uses, so a seeded ticket and a user-created one are byte-identical. Pure
- * 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 const supportTicketsSeedData = supportTicketRecords.map((ticket) => ({
-    ...ticket,
-    searchTxt: ticket.subject ? buildSearchTxt([ticket.subject]) : [],
-}));

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

@@ -1,34 +0,0 @@
-/**
- * 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[];

package/dist/seed/tax-codes-seed-data.js

@@ -1,100 +0,0 @@
-/**
- * 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-
- */
-/*
- * A FIXED date, not `Date.now()`. Seed files are re-imported on every
- * `appkit-seed` invocation, so a moving timestamp makes `load` non-idempotent
- * and `status`/`delete` unable to see what a prior run wrote — Root Cause #25.
- */
-const SEEDED_AT = new Date("2026-10-10T00:00:00.000Z");
-export const taxCodesSeedData = [
-    {
-        id: "tax-hsn-95030020",
-        hsnCode: "95030020",
-        label: "Toys, non-electronic incl. spinning tops (HSN 9503 0020) — 5%",
-        description: "The default for this catalogue: every Beyblade, part, launcher and stadium.",
-        gstRate: 5,
-        chapter: "9503",
-        isActive: true,
-        notes: "Verified against the current GST schedule. Spinning tops are named explicitly in this sub-heading, which is why it is the default rather than 9503 0099.",
-        createdAt: SEEDED_AT,
-        updatedAt: SEEDED_AT,
-    },
-    {
-        id: "tax-hsn-95030099",
-        hsnCode: "95030099",
-        label: "Other toys (HSN 9503 0099) — 5%",
-        description: "Toys and collectibles that are not spinning tops and not electronic — figures, model kits, diecast.",
-        gstRate: 5,
-        chapter: "9503",
-        isActive: true,
-        notes: "Verified. The catch-all within chapter 9503 for non-electronic toys.",
-        createdAt: SEEDED_AT,
-        updatedAt: SEEDED_AT,
-    },
-    {
-        id: "tax-hsn-95030010",
-        hsnCode: "95030010",
-        label: "Electronic toys (HSN 9503 0010) — 18%",
-        description: "Toys whose function depends on electronics — anything battery-driven or with a screen.",
-        gstRate: 18,
-        chapter: "9503",
-        isActive: true,
-        notes: "Verified. 🛑 Keep at least one product on this code: it is the only row that proves the 18% branch is applied rather than a 5% rate being hardcoded.",
-        createdAt: SEEDED_AT,
-        updatedAt: SEEDED_AT,
-    },
-    {
-        id: "tax-hsn-95030091",
-        hsnCode: "95030091",
-        label: "Parts of electronic toys (HSN 9503 0091) — 18%",
-        description: "Components and spares for electronic toys.",
-        gstRate: 18,
-        chapter: "9503",
-        isActive: true,
-        notes: "Verified. Follows the parent heading's rate.",
-        createdAt: SEEDED_AT,
-        updatedAt: SEEDED_AT,
-    },
-    {
-        id: "tax-exempt-0",
-        hsnCode: "",
-        label: "Exempt — 0% (no HSN)",
-        description: "Live plants and live animals. An exemption, deliberately recorded rather than left unset.",
-        gstRate: 0,
-        chapter: "exempt",
-        isActive: true,
-        notes: "🛑 Rate 0 is a DECISION; `gstRate: undefined` is 'nobody has said'. Every reader tests `== null` rather than falsiness precisely so this row survives a default being applied elsewhere.",
-        createdAt: SEEDED_AT,
-        updatedAt: SEEDED_AT,
-    },
-];

package/dist/seed/test-data-ttl.d.ts

@@ -1,29 +0,0 @@
-/**
- * The TTL stamp every disposable test fixture must carry.
- *
- * 🛑 `isTestData: true` WITHOUT `testDataExpiresAt` means PERMANENT — nothing
- * ever reclaims it (see `jobs/handlers/_helpers.ts`, which documents the same
- * rule from the sweep's side). That is not a theoretical hazard: until
- * 2026-10-10 the only two `isTestData` rows in the whole seed,
- * `product-tester-crossstore-a` / `-b`, were in exactly that state — live in
- * the public catalogue of 72 products, never purged, and one of them was
- * `store-letitrip-official`'s ONLY buyable standard product, so it was hidden
- * from every real buyer by `hidePublicTestData` while being the only thing
- * that store had to sell. Both are deleted.
- *
- * And the reason they were permanent is that **this module had zero callers**.
- * The helper that enforces the rule existed, was documented as the rule that
- * matters most, and no fixture used it. So: a fixture's three obligations are
- * an id containing `-test-`, `isTestData: true`, and an expiry FROM HERE.
- *
- * Recomputed fresh on every seed run (seed files are re-imported per
- * invocation), so re-seeding naturally refreshes the expiry rather than
- * leaving a fixture that expired between runs.
- *
- * 🛑 Do NOT re-declare the day count elsewhere. It used to be declared twice —
- * here and in `jobs/handlers/messages.ts` — with a comment as the only thing
- * keeping them equal, which is the drift shape Root Cause #42 describes.
- * `messages.ts` now re-exports this one.
- */
-export declare const TEST_DATA_TTL_DAYS = 7;
-export declare function testDataExpiresAt(): Date;

package/dist/seed/test-data-ttl.js

@@ -1,31 +0,0 @@
-/**
- * The TTL stamp every disposable test fixture must carry.
- *
- * 🛑 `isTestData: true` WITHOUT `testDataExpiresAt` means PERMANENT — nothing
- * ever reclaims it (see `jobs/handlers/_helpers.ts`, which documents the same
- * rule from the sweep's side). That is not a theoretical hazard: until
- * 2026-10-10 the only two `isTestData` rows in the whole seed,
- * `product-tester-crossstore-a` / `-b`, were in exactly that state — live in
- * the public catalogue of 72 products, never purged, and one of them was
- * `store-letitrip-official`'s ONLY buyable standard product, so it was hidden
- * from every real buyer by `hidePublicTestData` while being the only thing
- * that store had to sell. Both are deleted.
- *
- * And the reason they were permanent is that **this module had zero callers**.
- * The helper that enforces the rule existed, was documented as the rule that
- * matters most, and no fixture used it. So: a fixture's three obligations are
- * an id containing `-test-`, `isTestData: true`, and an expiry FROM HERE.
- *
- * Recomputed fresh on every seed run (seed files are re-imported per
- * invocation), so re-seeding naturally refreshes the expiry rather than
- * leaving a fixture that expired between runs.
- *
- * 🛑 Do NOT re-declare the day count elsewhere. It used to be declared twice —
- * here and in `jobs/handlers/messages.ts` — with a comment as the only thing
- * keeping them equal, which is the drift shape Root Cause #42 describes.
- * `messages.ts` now re-exports this one.
- */
-export const TEST_DATA_TTL_DAYS = 7;
-export function testDataExpiresAt() {
-    return new Date(Date.now() + TEST_DATA_TTL_DAYS * 24 * 60 * 60 * 1000);
-}

package/dist/seed/test-utils.d.ts

@@ -1,49 +0,0 @@
-import type { JsonValue } from "@mohasinac/appkit";
-import type { SeedBaseUserDocument } from "./factories/user.factory";
-import type { SeedBaseProductDocument } from "./factories/product.factory";
-import type { SeedBaseStoreDocument } from "./factories/store.factory";
-import type { SeedBaseOrderDocument } from "./factories/order.factory";
-import type { SeedCategoryDocument } from "./factories/category.factory";
-import type { SeedFaqDocument } from "./factories/faq.factory";
-/**
- * Assert that every `piiField` in `doc` is encrypted and can be decrypted
- * back to the original plaintext.
- *
- * Throws a descriptive error on any violation — use in tests.
- *
- * @example
- * ```ts
- * const user = makeFullUser({ email: "test@example.com", phone: "+919876543210" });
- * await assertPiiRoundTrip(user, ["email", "phone"]);
- * ```
- */
-export declare function assertPiiRoundTrip<T extends Record<string, JsonValue>>(doc: T, piiFields: Array<keyof T & string>): Promise<void>;
-export interface TestSeedHandles {
-    users: SeedBaseUserDocument[];
-    products: SeedBaseProductDocument[];
-    stores: SeedBaseStoreDocument[];
-    orders: SeedBaseOrderDocument[];
-    categories: SeedCategoryDocument[];
-    faqs: SeedFaqDocument[];
-}
-/**
- * Seed the Firestore emulator with a predictable, minimal dataset.
- *
- * Uses the `FIRESTORE_EMULATOR_PROJECT_ID` env var (default: "demo-test").
- * Requires the emulator to be running before calling this.
- *
- * @example
- * ```ts
- * // jest.setup.ts
- * beforeAll(async () => {
- * const handles = await seedForTest();
- * globalThis.__testUsers = handles.users;
- * });
- * ```
- */
-export declare function seedForTest(overrides?: Partial<{
-    users: SeedBaseUserDocument[];
-    products: SeedBaseProductDocument[];
-    stores: SeedBaseStoreDocument[];
-    orders: SeedBaseOrderDocument[];
-}>): Promise<TestSeedHandles>;

package/dist/seed/test-utils.js

@@ -1,110 +0,0 @@
-import { runSeed } from "./runner.js";
-import { encryptPiiFields, decryptPiiFields, ENC_PREFIX } from "../security/pii-encrypt.js";
-import { hasEncPrefix } from "../security/pii-mask.js";
-import { DEFAULT_CATEGORIES } from "./defaults/categories.js";
-import { DEFAULT_FAQS } from "./defaults/faqs.js";
-import { makeProduct } from "./factories/product.factory.js";
-import { USER_FIXTURES } from "./factories/user.factory.js";
-import { makeStore } from "./factories/store.factory.js";
-// ---------------------------------------------------------------------------
-// PII round-trip assertion
-// ---------------------------------------------------------------------------
-/**
- * Assert that every `piiField` in `doc` is encrypted and can be decrypted
- * back to the original plaintext.
- *
- * Throws a descriptive error on any violation — use in tests.
- *
- * @example
- * ```ts
- * const user = makeFullUser({ email: "test@example.com", phone: "+919876543210" });
- * await assertPiiRoundTrip(user, ["email", "phone"]);
- * ```
- */
-export async function assertPiiRoundTrip(doc, piiFields) {
-    const encrypted = encryptPiiFields(doc, piiFields);
-    for (const field of piiFields) {
-        const val = encrypted[field];
-        // `hasEncPrefix`, not a bare startsWith: the assertion is "this is not
-        // cleartext", which both crypto formats satisfy. And the value NEVER goes
-        // in the message — this helper runs over real fixture PII.
-        if (!hasEncPrefix(val)) {
-            throw new Error(`assertPiiRoundTrip: field "${String(field)}" was NOT encrypted (got ${val.length} chars, no ${ENC_PREFIX} prefix).`);
-        }
-        // Verify blind index was written
-        const indexKey = `${String(field)}Index`;
-        if (!encrypted[indexKey]) {
-            throw new Error(`assertPiiRoundTrip: blind index "${indexKey}" is missing after encryption.`);
-        }
-    }
-    const decrypted = decryptPiiFields(encrypted, piiFields);
-    for (const field of piiFields) {
-        if (decrypted[field] !== doc[field]) {
-            throw new Error(`assertPiiRoundTrip: field "${String(field)}" round-trip mismatch. ` +
-                `Expected "${String(doc[field])}", got "${String(decrypted[field])}"`);
-        }
-    }
-}
-/**
- * Seed the Firestore emulator with a predictable, minimal dataset.
- *
- * Uses the `FIRESTORE_EMULATOR_PROJECT_ID` env var (default: "demo-test").
- * Requires the emulator to be running before calling this.
- *
- * @example
- * ```ts
- * // jest.setup.ts
- * beforeAll(async () => {
- * const handles = await seedForTest();
- * globalThis.__testUsers = handles.users;
- * });
- * ```
- */
-export async function seedForTest(overrides) {
-    const users = overrides?.users ?? Object.values(USER_FIXTURES);
-    const products = overrides?.products ??
-        Array.from({ length: 5 }, (_, i) => makeProduct({ id: `p-${i + 1}` }));
-    const stores = overrides?.stores ?? [makeStore({ id: "store-1" })];
-    const orders = overrides?.orders ?? [];
-    const seedConfig = {
-        projectId: process.env["FIRESTORE_EMULATOR_PROJECT_ID"] ?? "demo-test",
-        collections: [
-            {
-                collection: "users",
-                data: users,
-                idField: "uid",
-                piiFields: ["email"],
-            },
-            {
-                collection: "products",
-                data: products,
-            },
-            {
-                collection: "stores",
-                data: stores,
-                piiFields: ["ownerEmail"],
-            },
-            {
-                collection: "orders",
-                data: orders,
-            },
-            {
-                collection: "categories",
-                data: DEFAULT_CATEGORIES,
-            },
-            {
-                collection: "faqs",
-                data: DEFAULT_FAQS,
-            },
-        ],
-    };
-    await runSeed(seedConfig);
-    return {
-        users,
-        products,
-        stores,
-        orders,
-        categories: DEFAULT_CATEGORIES,
-        faqs: DEFAULT_FAQS,
-    };
-}