@mohasinac/appkit 4.46.0 → 4.48.0

package/dist/features/tester/seed-data/authored/community-support__messages.js

@@ -0,0 +1,200 @@
+/*
+ * WHY: Authored six-part procedures for the D9 chat pages (/messages).
+ * WHAT: 10 case(s), keyed by full checklist id.
+ *
+ * 🛑 CHAT IS OFF BY DEFAULT AND `undefined` READS AS OFF.
+ *
+ * `siteSettings.chat.enabled` gates every write path server-side
+ * (`assertChatEnabled`) AND the nav icon AND the Message Seller button. So the
+ * FIRST case here turns it on, and every case after it depends on that having
+ * happened — which is deliberate: the off-state behaviour is itself a case
+ * worth having, because "the feature silently half-works when disabled" is the
+ * shape the original chat feature died of.
+ *
+ * 🛑 AND IT IS A REAL SETTING, NOT A FIXTURE. The seed does not write it, so a
+ * fresh run starts with chat OFF. A case that assumes the icon is present
+ * without having turned it on is testing the wrong state and will answer `no`
+ * for a reason that is not a defect.
+ *
+ * 🛑 THE OLD FEATURE'S TWO BUGS ARE THE TWO MOST VALUABLE CASES HERE, and
+ * neither is visible from the UI alone:
+ *
+ *   1. `useConversation`/`useConversations` never called `signInWithToken`, so
+ *      every RTDB rule evaluated false and the live channel was permission-
+ *      denied — swallowed into `setIsConnected(false)` and a literal
+ *      `// ignore`. The channel LOOKED implemented and was inert. Case
+ *      `live-ping-surfaces-failure` is the control: the error must be VISIBLE.
+ *   2. `listByBuyer`/`listByStore` had no `.limit()`, and every message wrote
+ *      2–3 pings each triggering an unpaginated refetch for both participants.
+ *      Twenty messages ≈ 1,600 reads. Case `inbox-read-is-bounded` is the
+ *      negative control the plan names explicitly.
+ *
+ * 🛑 TWO ACCOUNTS ARE REQUIRED and both are seeded: admin@letitrip.in (admin)
+ * and the owner of store-beyblade-arena, user-tyson-blader. A conversation is
+ * between two DIFFERENT users and the server refuses a self-conversation, so a
+ * single-account run cannot exercise anything past case 2.
+ *
+ * audit-tester-created-id: the conversation id is generated by Firestore and is
+ * therefore not knowable in advance — every case that needs it says to read it
+ * off the URL after the Message Seller button navigates, which is the only
+ * honest instruction. It is not a seed fixture and must not become one: the
+ * point is to exercise the create path.
+ *
+ * @tag domain:tester
+ * @tag layer:seed
+ * @tag pattern:none
+ * @tag access:server-only
+ * @tag consumers:seed-data/authored/index.ts
+ * @tag sideEffects:none
+ */
+export const authored = {
+    "checklist-community-support-messages-chat-off-hides-everything": {
+        roles: ["admin", "buyer", "guest"],
+        startPage: "/admin/site",
+        steps: [
+            "Sign in as admin@letitrip.in / TempPass123!.",
+            "Open /admin/site and confirm the Chat toggle is OFF (its stored value is absent on a fresh seed, which reads as off).",
+            "Open /products/product-beyblade-burst-valkyrie and look at the 'Sold by' card.",
+            "Look at the header icon row, between the notification bell and the wishlist heart.",
+            "Navigate directly to /messages.",
+        ],
+        expectedBehaviour: "With chat off, nothing chat-related renders anywhere: no Message Seller button on the store card, no Messages icon in the header, and no /api/messages/unread-count request fires at all (the hook is gated on the setting, not merely rendered-and-empty). /messages itself still resolves — it is a real route — and shows the signed-out or empty state rather than 404ing.",
+        expectedUiState: "The 'Sold by' card shows ONLY 'Visit Store →'. The header icon row has no speech-bubble icon. /messages renders its own chrome with no conversation rows.",
+        endResult: "Nothing persists; this is the baseline state. Reload and the three absences hold.",
+    },
+    "checklist-community-support-messages-enable-chat-reveals-entry-points": {
+        roles: ["admin", "buyer"],
+        startPage: "/admin/site",
+        steps: [
+            "Sign in as admin@letitrip.in / TempPass123!.",
+            "Open /admin/site, turn the Chat toggle ON, and save.",
+            "Reload /products/product-beyblade-burst-valkyrie.",
+            "Look at the 'Sold by' card and at the header icon row.",
+        ],
+        inputs: { "chat.enabled": true },
+        expectedBehaviour: "Turning it on makes both entry points appear WITHOUT a code change: the gate is a live settings read, not a build-time flag. The Messages icon appears in the header with no badge (zero unread).",
+        expectedUiState: "The 'Sold by' card now shows a 'Message Seller' button beside 'Visit Store →'. A speech-bubble icon appears in the header icon row.",
+        expectedData: { "siteSettings.chat.enabled": true },
+        endResult: "Reload: both still present. The setting is stored, so it survives a sign-out and back in.",
+    },
+    "checklist-community-support-messages-message-seller-creates-thread": {
+        roles: ["buyer", "seller"],
+        startPage: "/products/product-beyblade-burst-valkyrie",
+        steps: [
+            "With chat enabled (previous case), sign in as admin@letitrip.in / TempPass123!.",
+            "Open /products/product-beyblade-burst-valkyrie and click 'Message Seller' on the 'Sold by' card.",
+            "Read the URL you land on and note the conversation id — it is a Firestore-generated id, not a slug.",
+            "Click 'Message Seller' on the SAME product a second time (go back and click again).",
+            "Compare the URL to the one you noted.",
+        ],
+        expectedBehaviour: "The first click resolves store-beyblade-arena's storeId to its owner's uid SERVER-SIDE (a product page knows the store slug, never the owner's Auth UID) and creates one conversation. The second click finds the existing thread and does NOT create a second one — the thread is between two USERS, not per listing, so a buyer with three questions about three items gets one thread.",
+        expectedUiState: "Both clicks land on /messages/{sameId} showing an empty thread with a composer and a 'Block' control in the header.",
+        expectedData: { "conversations: documents between this pair": 1 },
+        endResult: "The conversation persists. /messages now lists it. Clicking Message Seller again forever reuses it.",
+    },
+    "checklist-community-support-messages-send-and-recipient-sees-it": {
+        roles: ["buyer", "seller"],
+        startPage: "/messages",
+        steps: [
+            "Signed in as admin@letitrip.in, open the conversation created in the previous case.",
+            "Type 'Does this come with the original launcher?' and press Enter.",
+            "Watch the bubble while it sends.",
+            "Sign out, sign in as the owner of store-beyblade-arena (user-tyson-blader), and open /messages.",
+            "Open the conversation and read the message.",
+        ],
+        inputs: { body: "Does this come with the original launcher?" },
+        expectedBehaviour: "The message appears immediately as a pending bubble (optimistic), then resolves to a sent one. Server-side the body is PII-stripped and encrypted at rest, a truncated preview is denormalised onto the conversation, the recipient's unread counter is incremented with a real Firestore increment (not a read-modify-write), and a bell-only `message_received` notification is written — no email, because EMAIL_ELIGIBLE_TYPES says false for it.",
+        expectedUiState: "Sender side: the bubble is right-aligned and reads 'Sending…' briefly, then settles. Recipient side: /messages shows the thread with an unread badge of 1 and the preview text; opening it shows the message left-aligned and clears the badge.",
+        expectedData: { "recipient unread before opening": 1, "recipient unread after opening": 0 },
+        endResult: "Reload on both sides: the message is still there, the badge stays cleared for the recipient, and the preview on the inbox row matches the message.",
+    },
+    "checklist-community-support-messages-pii-is-stripped-from-the-body": {
+        roles: ["buyer"],
+        startPage: "/messages",
+        steps: [
+            "Open any conversation you are a participant in.",
+            "Send exactly: 'call me on 9876543210 or pay to tyson@paytm or tyson@okhdfc'",
+            "Read the message as it appears in the thread.",
+            "Reload the page and read it again.",
+        ],
+        inputs: { body: "call me on 9876543210 or pay to tyson@paytm or tyson@okhdfc" },
+        expectedBehaviour: "All three identifiers are replaced BEFORE the write, so the stored body never contains them. The rule order is specific-before-general and that ordering IS the fix: a bare `name@bank` VPA has no TLD dot so it matches neither the email nor the phone rule, and running phone first would mangle '9876543210@upi' into '[number removed]@upi' before the UPI rule ever saw it.",
+        expectedUiState: "The message renders as 'call me on [number removed] or pay to [email removed] or pay to [UPI removed]' — the ten-digit run, the dotted VPA and the bare VPA each replaced, none left through.",
+        expectedData: { "stored body contains '9876543210'": false, "stored body contains 'okhdfc'": false },
+        endResult: "Reload: the redacted form persists. The original text is not recoverable from the UI, which is the point — the redaction happened on the way in, not on the way out.",
+    },
+    "checklist-community-support-messages-retry-does-not-double-post": {
+        roles: ["buyer"],
+        startPage: "/messages",
+        steps: [
+            "Open a conversation and open DevTools → Network, set throttling to Offline.",
+            "Type 'retry test' and press Enter.",
+            "Observe the bubble's state.",
+            "Set throttling back to online and click the failed bubble's retry control.",
+            "Count the messages in the thread.",
+        ],
+        inputs: { body: "retry test" },
+        expectedBehaviour: "The failed send keeps its ORIGINAL clientMessageId — generated once at compose time, not per attempt — so the retry resolves to the same message server-side rather than creating a second one. The server uses the clientMessageId as the message document id and returns the existing document on a replay.",
+        expectedUiState: "Offline: the bubble reads 'Failed — tap to retry' rather than disappearing or silently succeeding. After retry: exactly ONE 'retry test' bubble in the thread, no duplicate.",
+        expectedData: { "messages with body 'retry test'": 1 },
+        endResult: "Reload: one message. A silent failure or a duplicate would both be defects — the first is how the old feature hid, the second is what idempotency exists to prevent.",
+    },
+    "checklist-community-support-messages-soft-ban-blocks-sending": {
+        roles: ["admin", "buyer"],
+        startPage: "/admin/users",
+        steps: [
+            "Sign in as admin@letitrip.in and open /admin/users.",
+            "Find the account you have been testing with as the buyer, open its editor, and apply a soft ban with action 'Send messages' and a reason.",
+            "Sign in as that banned account and open a conversation you are a participant in.",
+            "Type anything and try to send.",
+            "Read the refusal.",
+        ],
+        inputs: { "softBan.action": "send_messages", "softBan.reason": "QA test ban" },
+        expectedBehaviour: "The send is refused server-side with the ban's own reason quoted back. 🛑 This is the case that matters most about this flag: `send_messages` was a live BannedAction with NO READER anywhere in the codebase — an admin could set it and nothing checked it. The check lives in the domain function, so every caller (route, future job) is covered rather than just the one route someone remembered.",
+        expectedUiState: "An error surfaces naming the restriction and the reason — 'You are restricted from sending messages. Reason: QA test ban.' — not a generic failure and not a silently-dropped message.",
+        expectedData: { "messages added to the thread": 0 },
+        endResult: "Reload: no message was added. Remove the ban and the same send succeeds, which is what proves the ban was the cause rather than something else.",
+    },
+    "checklist-community-support-messages-block-stops-the-other-side": {
+        roles: ["buyer", "seller"],
+        startPage: "/messages",
+        steps: [
+            "Sign in as the seller (user-tyson-blader) and open the shared conversation.",
+            "Click 'Block' in the thread header and confirm.",
+            "Sign out, sign back in as the buyer (admin@letitrip.in), open the same conversation.",
+            "Try to send a message.",
+        ],
+        expectedBehaviour: "Blocking records the blocker's uid on the conversation. A send from the blocked party is refused with a clear reason rather than silently vanishing — a blocked sender who thinks their message went through is worse than one who is told.",
+        expectedUiState: "Blocker side: a confirmation, then the block persists. Blocked side: the send fails with 'The other participant is not accepting messages from you.'",
+        expectedData: { "messages added after the block": 0 },
+        endResult: "Reload on both sides: the block holds and the thread's existing history is still readable to both. Blocking stops new messages; it does not delete the past.",
+    },
+    "checklist-community-support-messages-live-ping-surfaces-failure": {
+        roles: ["buyer"],
+        startPage: "/messages",
+        steps: [
+            "Open a conversation and leave it open.",
+            "Open DevTools → Network and block requests to the Firebase Realtime Database host (or set throttling to Offline then back, which drops the subscription).",
+            "Watch the top of the thread for a notice.",
+            "In a second browser profile signed in as the other participant, send a message.",
+            "Reload the first tab.",
+        ],
+        expectedBehaviour: "🛑 THE CONTROL FOR THE BUG THAT KILLED THE OLD FEATURE. When the realtime channel cannot connect, the failure is SURFACED, never swallowed. The old hooks swallowed permission-denied into `setIsConnected(false)` and a literal `// ignore`, so the channel looked implemented and was inert for its entire life. The message is still delivered — it is durably in Firestore the moment the send returns — and the subscription only controls whether the open tab learns about it without a reload.",
+        expectedUiState: "A visible warning strip above the thread reading 'Live updates are unavailable for this conversation. New messages may not appear until you reload.' — NOT a silent nothing. After reload, the other participant's message is present.",
+        endResult: "The message was never lost; only the live notification was. That distinction is what the warning communicates, and a tester seeing no warning at all is the defect.",
+    },
+    "checklist-community-support-messages-inbox-read-is-bounded": {
+        roles: ["buyer"],
+        startPage: "/messages",
+        steps: [
+            "Open DevTools → Network and filter to /api/messages.",
+            "Load /messages and note the request and its response shape.",
+            "Open one conversation and note the thread request's response shape.",
+            "Scroll the thread to its oldest message.",
+        ],
+        expectedBehaviour: "🛑 THE NEGATIVE CONTROL THE PLAN NAMES. Both list reads are bounded and cursor-paginated: the inbox returns at most 50 conversations with a `nextCursor`, the thread at most 50 messages (default 30) with its own `nextCursor`. The absence of a `.limit()` is literally what turned 20 messages into ~1,600 reads the first time this feature existed. The unread badge sums the conversation list the inbox already holds and never issues a list query of its own.",
+        expectedUiState: "Each response carries `{ items: [...], nextCursor }` with `items.length` at or below the limit — never an unbounded array, and never a response whose size grows with total thread count.",
+        expectedData: { "inbox items.length <= 50": true, "thread items.length <= 50": true },
+        endResult: "Reload: the same bounded shape. A response returning every message in a thread is the defect this case exists to catch, and it is invisible from the rendered page — only the network panel shows it.",
+    },
+};

package/dist/features/tester/seed-data/authored/index.js

@@ -71,6 +71,7 @@ import { authored as a_buying__user_dashboard_extras } from "./buying__user-dash
 import { authored as a_buying__offers } from "./buying__offers.js";
 import { authored as a_buying__cart } from "./buying__cart.js";
 import { authored as a_community_support__public_profile } from "./community-support__public-profile.js";
+import { authored as a_community_support__messages } from "./community-support__messages.js";
 import { authored as a_community_support__support_tickets } from "./community-support__support-tickets.js";
 import { authored as a_content_discovery__blog } from "./content-discovery__blog.js";
 import { authored as a_content_discovery__coupons } from "./content-discovery__coupons.js";
@@ -191,6 +192,7 @@ export const AUTHORED_CASES = {
     ...a_buying__offers,
     ...a_buying__cart,
     ...a_community_support__public_profile,
+    ...a_community_support__messages,
     ...a_community_support__support_tickets,
     ...a_content_discovery__blog,
     ...a_content_discovery__coupons,

package/dist/features/tester/seed-data/tester-checklist-seed-data.js

@@ -505,7 +505,7 @@ const rawTesterChecklistItems = [
                 {
                     key: "tester-fixtures-hidden-from-the-public",
                     label: "SIGNED OUT, no product on /products has an id containing \"tester\" — the sandbox is invisible to the public",
-                    description: "Fixed 2026-09-01. BEFORE: the public products endpoint had no viewer concept, so an ANONYMOUS caller got 25 tester fixtures in its first 40 rows — stickers-beyblade-original-classic-sheet, prizedraw-beyblade-metal-closed-revealed, live-golden-retriever-puppy — and they filled the public marketplace. AFTER: open /products in a private window and scan the grid; nothing should be named \"Tester …\". Then sign in AS A TESTER and reload — the sandbox items must come back. Both halves matter: hiding them from everyone would break the tester programme, and a fixture that never reappears is the opposite bug.",
+                    description: "Fixed 2026-09-01. BEFORE: the public products endpoint had no viewer concept, so an ANONYMOUS caller got 25 tester fixtures in its first 40 rows — sticker-beyblade-original-classic-sheet, prizedraw-beyblade-metal-closed-revealed, live-golden-retriever-puppy — and they filled the public marketplace. AFTER: open /products in a private window and scan the grid; nothing should be named \"Tester …\". Then sign in AS A TESTER and reload — the sandbox items must come back. Both halves matter: hiding them from everyone would break the tester programme, and a fixture that never reappears is the opposite bug.",
                     href: "/products",
                 },
                 {
@@ -3519,6 +3519,69 @@ const rawTesterChecklistItems = [
         },
     ]),
     ...group("community-support", "Community & Support", [
+        {
+            /*
+             * D9 chat. 🛑 Chat is OFF by default (`siteSettings.chat.enabled`, and
+             * `undefined` reads as off), so case 1 asserts the off-state and case 2
+             * turns it on — every case after depends on that order. Steps live in
+             * ./authored/community-support__messages.ts.
+             */
+            pageKey: "messages",
+            pageLabel: "Messages (chat)",
+            href: "/messages",
+            cases: [
+                {
+                    key: "chat-off-hides-everything",
+                    label: "With chat disabled, no Message Seller button, no header icon, and no unread-count request — absent, not disabled",
+                    description: "The baseline. `siteSettings.chat.enabled` is undefined on a fresh seed and must read as OFF. A feature that half-renders when disabled is the shape the original chat died of.",
+                },
+                {
+                    key: "enable-chat-reveals-entry-points",
+                    label: "Turning the Chat setting on makes both entry points appear with no code change or redeploy",
+                },
+                {
+                    key: "message-seller-creates-thread",
+                    label: "Message Seller creates ONE conversation, and clicking it again reuses that same thread rather than making a second",
+                    description: "A conversation is between two USERS, not per listing — a buyer with three questions about three items gets one thread. The storeId→ownerId resolution happens server-side because a product page never knows the owner's Auth UID.",
+                },
+                {
+                    key: "send-and-recipient-sees-it",
+                    label: "A sent message reaches the other participant with an unread badge, and opening the thread clears it",
+                    roles: ["buyer", "seller"],
+                },
+                {
+                    key: "pii-is-stripped-from-the-body",
+                    label: "A phone number, a dotted VPA and a bare name@bank VPA are ALL redacted before the message is stored",
+                    description: "The rule order is the fix: specific before general. A bare `name@bank` has no TLD dot so it matches neither the email nor the phone rule, and running phone first mangles `9876543210@upi` before the UPI rule sees it.",
+                },
+                {
+                    key: "retry-does-not-double-post",
+                    label: "Retrying a failed send posts the SAME message once, never a duplicate",
+                    description: "clientMessageId is generated once at compose time, not per attempt, and is the message's document id — so a replay resolves to the existing document.",
+                },
+                {
+                    key: "soft-ban-blocks-sending",
+                    label: "A user soft-banned from 'Send messages' is refused with the ban's own reason",
+                    description: "send_messages was a live BannedAction with NO reader anywhere — an admin could set it and nothing checked it. The check now lives in the domain function so every caller is covered.",
+                    roles: ["admin", "buyer"],
+                },
+                {
+                    key: "block-stops-the-other-side",
+                    label: "Blocking a participant refuses their next message with a clear reason, and leaves existing history readable",
+                    roles: ["buyer", "seller"],
+                },
+                {
+                    key: "live-ping-surfaces-failure",
+                    label: "When the realtime channel cannot connect, a visible warning says so — the failure is never swallowed",
+                    description: "THE control for the bug that killed the old feature: it swallowed permission-denied into setIsConnected(false) and a literal `// ignore`, so the channel looked implemented and was inert for its whole life. The message is still delivered; only the live notification is lost.",
+                },
+                {
+                    key: "inbox-read-is-bounded",
+                    label: "The inbox and thread reads are both cursor-paginated and capped — open 50 threads and the read count does not scale with them",
+                    description: "The negative control. The absence of a .limit() is literally what turned 20 messages into ~1,600 reads the first time this existed. Visible only in the network panel, never on the rendered page.",
+                },
+            ],
+        },
         {
             pageKey: "support-tickets",
             pageLabel: "Support Tickets",

package/dist/index.d.ts

@@ -652,8 +652,8 @@ export { groupedListingsSeedData } from "./seed/index";
 export type { CouponDiscountType } from "./seed/index";
 export type { FirestoreIndexConfig } from "./seed/index";
 export type { HomepageSectionType } from "./seed/index";
-export type { NotificationType } from "./features/admin/schemas/firestore";
-export { NOTIFICATION_TYPE_VALUES } from "./features/admin/schemas/firestore";
+export type { NotificationType, NotificationRelatedType } from "./features/admin/schemas/firestore";
+export { NOTIFICATION_TYPE_VALUES, NOTIFICATION_RELATED_TYPE_VALUES } from "./features/admin/schemas/firestore";
 export type { PayoutStatus } from "./seed/index";
 export type { SeedAddressDocument } from "./seed/index";
 export type { SeedBaseOrderDocument } from "./seed/index";
@@ -3228,3 +3228,9 @@ export { resolveReturnAddress, RTO_ENTRY_CUSTODY, rtoCostBearer, RETURN_ABUSE_SC
 export type { ReturnAddressResolution, ResolveReturnAddressInput, ReturnAbuseSignal, ReturnAbuseCounters, RtoCostBearer, } from "./_internal/shared/features/returns/destination";
 export { COURIER_RATING_MIN_CONFIDENT_SAMPLES, courierRatingDisplay, isValidCourierVote, courierVoteId, rollUpCourierVotes, } from "./_internal/shared/features/shipping/courier-rating";
 export type { CourierRatingPair, CourierRatingDisplay, CourierRatingVote, CourierStats, } from "./_internal/shared/features/shipping/courier-rating";
+/**
+ * D9 — chat. Plain data types, safe for client components that render a
+ * conversation/message prop — the write path (actions) stays server-only, see
+ * server.ts.
+ */
+export type { ConversationDocument, ConversationStatus, ConversationLastMessage, ParticipantRole, MessageDocument, MessageProductRef, } from "./features/messages/schemas/firestore";

package/dist/index.js

@@ -1364,7 +1364,7 @@ export { historySeedData } from "./seed/index.js";
 // SB-UNI-B â€" sublistingCategoriesSeedData merged into categoriesSeedData with categoryType:"sublisting".
 // groupedListingsSeedData - Model for grouped listings seed data.
 export { groupedListingsSeedData } from "./seed/index.js";
-export { NOTIFICATION_TYPE_VALUES } from "./features/admin/schemas/firestore.js";
+export { NOTIFICATION_TYPE_VALUES, NOTIFICATION_RELATED_TYPE_VALUES } from "./features/admin/schemas/firestore.js";
 // [UTIL]-Pure utility â€" no framework or runtime dependency; safe to import from any environment.
 // ErrorCategory - Shared export for error category.
 export { ErrorCategory } from "./monitoring/index.js";

package/dist/next/routing/route-map.d.ts

@@ -86,6 +86,10 @@ export declare const DEFAULT_ROUTE_MAP: {
         readonly HOW_REVIEWS_WORK: "/how-reviews-work";
         readonly HOW_PAYOUTS_WORK: "/how-payouts-work";
         readonly FEES: "/fees";
+        readonly GST: "/gst";
+        readonly SPOT_A_FAKE: "/spot-a-fake";
+        readonly GUIDES: "/guides";
+        readonly CITY_COLLECTIBLES: (city: string) => string;
         readonly EVENTS: "/events";
         readonly EVENT_DETAIL: (id: string) => string;
         readonly EVENT_PARTICIPATE: (id: string) => string;
@@ -175,6 +179,9 @@ export declare const DEFAULT_ROUTE_MAP: {
         readonly CATALOGUE: "/user/catalogue";
         readonly CATALOGUE_NEW: "/user/catalogue/new";
         readonly CATALOGUE_EDIT: (id: string) => string;
+        /** D9 — one universal inbox, same real-top-level-path precedent as WISHLIST/CART. */
+        readonly MESSAGES: "/messages";
+        readonly MESSAGE_THREAD: (conversationId: string) => string;
     };
     readonly STORE: {
         readonly DASHBOARD: "/store";
@@ -493,6 +500,10 @@ export declare const ROUTES: {
         readonly HOW_REVIEWS_WORK: "/how-reviews-work";
         readonly HOW_PAYOUTS_WORK: "/how-payouts-work";
         readonly FEES: "/fees";
+        readonly GST: "/gst";
+        readonly SPOT_A_FAKE: "/spot-a-fake";
+        readonly GUIDES: "/guides";
+        readonly CITY_COLLECTIBLES: (city: string) => string;
         readonly EVENTS: "/events";
         readonly EVENT_DETAIL: (id: string) => string;
         readonly EVENT_PARTICIPATE: (id: string) => string;
@@ -582,6 +593,9 @@ export declare const ROUTES: {
         readonly CATALOGUE: "/user/catalogue";
         readonly CATALOGUE_NEW: "/user/catalogue/new";
         readonly CATALOGUE_EDIT: (id: string) => string;
+        /** D9 — one universal inbox, same real-top-level-path precedent as WISHLIST/CART. */
+        readonly MESSAGES: "/messages";
+        readonly MESSAGE_THREAD: (conversationId: string) => string;
     };
     readonly STORE: {
         readonly DASHBOARD: "/store";

package/dist/next/routing/route-map.js

@@ -79,6 +79,29 @@ export const DEFAULT_ROUTE_MAP = {
         HOW_REVIEWS_WORK: "/how-reviews-work",
         HOW_PAYOUTS_WORK: "/how-payouts-work",
         FEES: "/fees",
+        /*
+         * D6b — the GST explainer. A differentiator rather than table stakes:
+         * exactly ONE of the seventeen crawled Indian collectibles sites states
+         * tax-inclusive pricing to the buyer in words, and sixteen say nothing.
+         */
+        GST: "/gst",
+        /*
+         * D6 — the anti-counterfeit guide. Framed on what the crawl actually
+         * measured: the biggest copy-seller in this market makes no authenticity
+         * claim at all, so the signals are silence + price, then code, then weight.
+         */
+        SPOT_A_FAKE: "/spot-a-fake",
+        /* D6 — the content hub. Fourteen explainers whose only entry point was the
+         * footer; a footer link is reachable but it is not a destination, so it
+         * cannot rank and gives a crawler no page establishing the cluster. */
+        GUIDES: "/guides",
+        /*
+         * D5 — local SEO, one page per city a classified listing actually names.
+         * 🛑 STATIC (`generateStaticParams`): a city page that awaited
+         * `searchParams` would be dynamic, and this is the surface most likely to
+         * be crawled widely (Root Cause #94).
+         */
+        CITY_COLLECTIBLES: (city) => `/collectibles/${city}`,
         EVENTS: "/events",
         EVENT_DETAIL: (id) => `/events/${id}`,
         EVENT_PARTICIPATE: (id) => `/events/${id}/participate`,
@@ -197,6 +220,9 @@ export const DEFAULT_ROUTE_MAP = {
         CATALOGUE: "/user/catalogue",
         CATALOGUE_NEW: "/user/catalogue/new",
         CATALOGUE_EDIT: (id) => `/user/catalogue/${id}/edit`,
+        /** D9 — one universal inbox, same real-top-level-path precedent as WISHLIST/CART. */
+        MESSAGES: "/messages",
+        MESSAGE_THREAD: (conversationId) => `/messages/${conversationId}`,
     },
     STORE: {
         DASHBOARD: "/store",

package/dist/providers/db-firebase/rtdb-paths.d.ts

@@ -26,4 +26,12 @@ export declare const RTDB_PATHS: {
      * `cleanupRtdbEvents` alongside the other three.
      */
     readonly EMAIL_EVENTS: "email_events";
+    /**
+     * D9 — new-message ping per conversation. RTDB-ping-plus-REST: the actual
+     * message content never crosses this channel, only "something changed,
+     * refetch" — `firestore.rules` forbids client Firestore access entirely, so
+     * this plus the bounded REST route is the only option, not a cost choice.
+     * Pruned by `cleanupRtdbEvents`'s sixth block.
+     */
+    readonly CHAT_EVENTS: "chat_events";
 };

package/dist/providers/db-firebase/rtdb-paths.js

@@ -26,4 +26,12 @@ export const RTDB_PATHS = {
      * `cleanupRtdbEvents` alongside the other three.
      */
     EMAIL_EVENTS: "email_events",
+    /**
+     * D9 — new-message ping per conversation. RTDB-ping-plus-REST: the actual
+     * message content never crosses this channel, only "something changed,
+     * refetch" — `firestore.rules` forbids client Firestore access entirely, so
+     * this plus the bounded REST route is the only option, not a cost choice.
+     * Pruned by `cleanupRtdbEvents`'s sixth block.
+     */
+    CHAT_EVENTS: "chat_events",
 };

package/dist/repositories/index.d.ts

@@ -64,3 +64,4 @@ export { MediaAssetsRepository, mediaAssetsRepository, } from "../features/media
 export type { MediaAssetDocument, MediaAssetCreateInput, } from "../features/media/repository/media-assets.repository";
 export { PageViewsRepository, pageViewsRepository, PAGE_VIEW_ENTITY_TYPES, } from "../features/analytics/repository/page-views.repository";
 export type { PageViewDocument, PageViewEntityType, RecordPageViewInput, } from "../features/analytics/repository/page-views.repository";
+export { ConversationsRepository, conversationsRepository, } from "../features/messages/repository/conversations.repository";

package/dist/repositories/index.js

@@ -77,3 +77,7 @@ export { LotteryEntryRepository, lotteryEntryRepository, } from "../features/lot
 // Media assets — short ID → storagePath mapping for SEO-friendly /media/{id} URLs
 export { MediaAssetsRepository, mediaAssetsRepository, } from "../features/media/repository/media-assets.repository.js";
 export { PageViewsRepository, pageViewsRepository, PAGE_VIEW_ENTITY_TYPES, } from "../features/analytics/repository/page-views.repository.js";
+// D9 — chat. Messages themselves are a subcollection (functional module, see
+// features/messages/repository/messages.repository.ts and server.ts), not a
+// BaseRepository class — there is no subcollection form of BaseRepository.
+export { ConversationsRepository, conversationsRepository, } from "../features/messages/repository/conversations.repository.js";

package/dist/schemas/registry.d.ts

@@ -4660,7 +4660,7 @@ export declare const SCHEMAS: {
             youtubeId: import("zod").ZodOptional<import("zod").ZodString>;
             externalVideoUrl: import("zod").ZodOptional<import("zod").ZodString>;
             price: import("zod").ZodOptional<import("zod").ZodNumber>;
-            compareAtPrice: import("zod").ZodOptional<import("zod").ZodNumber>;
+            originalPrice: import("zod").ZodOptional<import("zod").ZodNumber>;
             stockQuantity: import("zod").ZodOptional<import("zod").ZodNumber>;
             featured: import("zod").ZodOptional<import("zod").ZodBoolean>;
             isPromoted: import("zod").ZodOptional<import("zod").ZodBoolean>;
@@ -4750,7 +4750,7 @@ export declare const SCHEMAS: {
             youtubeId: import("zod").ZodOptional<import("zod").ZodString>;
             externalVideoUrl: import("zod").ZodOptional<import("zod").ZodString>;
             price: import("zod").ZodOptional<import("zod").ZodNumber>;
-            compareAtPrice: import("zod").ZodOptional<import("zod").ZodNumber>;
+            originalPrice: import("zod").ZodOptional<import("zod").ZodNumber>;
             stockQuantity: import("zod").ZodOptional<import("zod").ZodNumber>;
             featured: import("zod").ZodOptional<import("zod").ZodBoolean>;
             isPromoted: import("zod").ZodOptional<import("zod").ZodBoolean>;
@@ -4840,7 +4840,7 @@ export declare const SCHEMAS: {
             youtubeId: import("zod").ZodOptional<import("zod").ZodString>;
             externalVideoUrl: import("zod").ZodOptional<import("zod").ZodString>;
             price: import("zod").ZodOptional<import("zod").ZodNumber>;
-            compareAtPrice: import("zod").ZodOptional<import("zod").ZodNumber>;
+            originalPrice: import("zod").ZodOptional<import("zod").ZodNumber>;
             stockQuantity: import("zod").ZodOptional<import("zod").ZodNumber>;
             featured: import("zod").ZodOptional<import("zod").ZodBoolean>;
             isPromoted: import("zod").ZodOptional<import("zod").ZodBoolean>;

package/dist/security/index.d.ts

@@ -6,5 +6,5 @@ export type { UserRole } from "./authorization";
 export { redactPii, safeDisplayName, safeDisplayEmail, maskIp } from "./pii-redact";
 export { encryptValue, decryptValue, hmacBlindIndex, encryptPiiFields, decryptPiiFields, encryptPii, decryptPii, piiBlindIndex, piiIndicesFor, getPiiConfigError, encryptPayoutDetails, decryptPayoutDetails, encryptShippingConfig, decryptShippingConfig, encryptPayoutBankAccount, decryptPayoutBankAccount, } from "./pii-encrypt";
 export { isPiiEncrypted, maskName, maskEmail, maskPublicReview, maskPublicBid, maskPublicEventEntry, maskOfferForSeller, ENC_PREFIX, HMAC_PREFIX, } from "./pii-mask";
-export { USER_PII_FIELDS, USER_PII_INDEX_MAP, ADDRESS_PII_FIELDS, ORDER_PII_FIELDS, PAYOUT_PII_FIELDS, PAYOUT_PII_INDEX_MAP, BID_PII_FIELDS, TOKEN_PII_FIELDS, TOKEN_PII_INDEX_MAP, REVIEW_PII_FIELDS, REVIEW_PII_INDEX_MAP, OFFER_PII_FIELDS, EVENT_ENTRY_PII_FIELDS, LOTTERY_ENTRY_PII_FIELDS, PAYMENT_METHOD_PII_FIELDS, } from "./pii-schemas";
+export { USER_PII_FIELDS, USER_PII_INDEX_MAP, ADDRESS_PII_FIELDS, ORDER_PII_FIELDS, PAYOUT_PII_FIELDS, PAYOUT_PII_INDEX_MAP, BID_PII_FIELDS, TOKEN_PII_FIELDS, TOKEN_PII_INDEX_MAP, REVIEW_PII_FIELDS, REVIEW_PII_INDEX_MAP, OFFER_PII_FIELDS, EVENT_ENTRY_PII_FIELDS, LOTTERY_ENTRY_PII_FIELDS, PAYMENT_METHOD_PII_FIELDS, CONVERSATION_PII_FIELDS, MESSAGE_PII_FIELDS, } from "./pii-schemas";
 export { encryptSecret, decryptSecret, isSecretEncrypted, maskSecret, } from "./settings-encryption";

package/dist/security/index.js

@@ -7,7 +7,7 @@ export { encryptValue, decryptValue, hmacBlindIndex, encryptPiiFields, decryptPi
 // pii-encrypt.ts) so this barrel stays safe to re-export from the
 // universal client+server index.ts. See pii-mask.ts's header comment.
 export { isPiiEncrypted, maskName, maskEmail, maskPublicReview, maskPublicBid, maskPublicEventEntry, maskOfferForSeller, ENC_PREFIX, HMAC_PREFIX, } from "./pii-mask.js";
-export { USER_PII_FIELDS, USER_PII_INDEX_MAP, ADDRESS_PII_FIELDS, ORDER_PII_FIELDS, PAYOUT_PII_FIELDS, PAYOUT_PII_INDEX_MAP, BID_PII_FIELDS, TOKEN_PII_FIELDS, TOKEN_PII_INDEX_MAP, REVIEW_PII_FIELDS, REVIEW_PII_INDEX_MAP, OFFER_PII_FIELDS, EVENT_ENTRY_PII_FIELDS, LOTTERY_ENTRY_PII_FIELDS, PAYMENT_METHOD_PII_FIELDS, } from "./pii-schemas.js";
+export { USER_PII_FIELDS, USER_PII_INDEX_MAP, ADDRESS_PII_FIELDS, ORDER_PII_FIELDS, PAYOUT_PII_FIELDS, PAYOUT_PII_INDEX_MAP, BID_PII_FIELDS, TOKEN_PII_FIELDS, TOKEN_PII_INDEX_MAP, REVIEW_PII_FIELDS, REVIEW_PII_INDEX_MAP, OFFER_PII_FIELDS, EVENT_ENTRY_PII_FIELDS, LOTTERY_ENTRY_PII_FIELDS, PAYMENT_METHOD_PII_FIELDS, CONVERSATION_PII_FIELDS, MESSAGE_PII_FIELDS, } from "./pii-schemas.js";
 export { encryptSecret, decryptSecret, isSecretEncrypted, maskSecret, } from "./settings-encryption.js";
 // RBAC system — DELETED 2026-08-29.
 //

package/dist/security/pii-schemas.d.ts

@@ -56,6 +56,23 @@ export declare const BID_PII_FIELDS: readonly ["userEmail"];
 export declare const TOKEN_PII_FIELDS: readonly ["email"];
 /** Blind-index mapping for token email queries */
 export declare const TOKEN_PII_INDEX_MAP: Record<string, string>;
+/**
+ * D9 — chat. Re-created against the SUBCOLLECTION redesign, not the old
+ * embedded-array one the comment below used to describe.
+ *
+ * `messages/{id}` is a true Firestore subcollection now (one document per
+ * message, not `conversations.messages[]`), so there is no array to walk and
+ * the old `messages[].body` `[]`-syntax path does not apply here — `body` is a
+ * plain top-level field on each message document. Only `lastMessage.body`, a
+ * nested object on the PARENT `conversations` document, needs the dotted-path
+ * form `encryptPiiFields` already supports.
+ *
+ * No blind index on either: nothing queries chat by body content, and a
+ * `searchTxt` over an encrypted body would hand back only what the encryption
+ * withheld — chat search, if it exists, indexes participant names only.
+ */
+export declare const CONVERSATION_PII_FIELDS: readonly ["lastMessage.body"];
+export declare const MESSAGE_PII_FIELDS: readonly ["body"];
 /** PII fields in reviews */
 export declare const REVIEW_PII_FIELDS: readonly ["userName"];
 /** Blind-index mapping for queryable review PII */

package/dist/security/pii-schemas.js

@@ -85,15 +85,23 @@ export const TOKEN_PII_FIELDS = ["email"];
 export const TOKEN_PII_INDEX_MAP = {
     email: "emailIndex",
 };
-/*
- * `CONVERSATION_PII_FIELDS` (`lastMessage`, `messages[].body`) was removed with
- * the conversations feature on 2026-08-31.
+/**
+ * D9 — chat. Re-created against the SUBCOLLECTION redesign, not the old
+ * embedded-array one the comment below used to describe.
+ *
+ * `messages/{id}` is a true Firestore subcollection now (one document per
+ * message, not `conversations.messages[]`), so there is no array to walk and
+ * the old `messages[].body` `[]`-syntax path does not apply here — `body` is a
+ * plain top-level field on each message document. Only `lastMessage.body`, a
+ * nested object on the PARENT `conversations` document, needs the dotted-path
+ * form `encryptPiiFields` already supports.
  *
- * 🛑 Its array-path form was the ONLY user of `encryptPiiFields`' `[]` syntax
- * outside status history. If a future schema needs to encrypt a field inside an
- * array, check that machinery still works before relying on it — a path that no
- * caller exercises is a path nothing proves.
+ * No blind index on either: nothing queries chat by body content, and a
+ * `searchTxt` over an encrypted body would hand back only what the encryption
+ * withheld — chat search, if it exists, indexes participant names only.
  */
+export const CONVERSATION_PII_FIELDS = ["lastMessage.body"];
+export const MESSAGE_PII_FIELDS = ["body"];
 /** PII fields in reviews */
 export const REVIEW_PII_FIELDS = ["userName"];
 /** Blind-index mapping for queryable review PII */

package/dist/seed/_helpers/category-content-generated.d.ts

@@ -0,0 +1,24 @@
+/**
+ * GENERATED by scripts/gen-category-content.mjs — do not edit by hand.
+ *
+ * `contentBody` per category, composed from FACTS ONLY (I7). Every clause
+ * traces to a committed source: canonical-beys.json for a model leaf,
+ * part-glossary.json for a part leaf, the forest's own child lists above them.
+ *
+ * 🛑 A node with nothing factual to say is ABSENT from this map rather than
+ * carrying an empty body — `CategoryHighlightsAndFaqSection` renders nothing
+ * when its inputs are empty, and an empty paragraph reads as a defect.
+ *
+ * 🛑 No price band appears here. `MARKET_BANDS` omits a band rather than
+ * guessing one, and a body that stated an unmeasured "typical price" would be
+ * the same guess with better typography.
+ *
+ * 🛑 No listing COUNT appears here either. Counts live in `categoryCounts` and
+ * move; a sentence saying "48 listings" is wrong the next day and nothing
+ * reports it.
+ *
+ * Model leaves with a body: 217 of 220
+ * Part leaves with a body:  534 of 752
+ */
+export declare const GENERATED_CATEGORY_CONTENT: Record<string, string>;
+export declare const GENERATED_CATEGORY_CONTENT_COUNT = 751;