@mohasinac/appkit 4.47.0 → 4.48.1

package/dist/features/scams/repository/scammer.repository.js

@@ -6,7 +6,7 @@ import { increment } from "../../../contracts/field-ops.js";
 import { withHistory } from "../../../_internal/shared/history/index.js";
 import { SCAMMER_TRACKED_FIELDS, SCAMMER_HISTORY_PII_FIELDS } from "../schemas/firestore.js";
 import { buildScammerSearchTxt } from "../../../utils/search-txt-builders.js";
-import { planSearchTxt, refineSearchTxt, emptySearchResult, } from "../../../utils/search-txt-query.js";
+import { planSearchTxt, beginSearchWindow, emptySearchResult, } from "../../../utils/search-txt-query.js";
 import { SCAMMER_COLLECTION, SCAMMER_FIELDS, SCAMMER_INCIDENTS_SUBCOLLECTION, SCAMMER_COMMENTS_SUBCOLLECTION, DEFAULT_SCAMMER_DATA, } from "../schemas/firestore.js";
 class ScammerRepository extends BaseRepository {
     constructor() {
@@ -35,12 +35,19 @@ class ScammerRepository extends BaseRepository {
         if (plan.head) {
             baseQuery = baseQuery.where(SCAMMER_FIELDS.SEARCH_TXT, "array-contains", plan.head);
         }
-        const result = await this.sieveQuery(model, ScammerRepository.SIEVE_FIELDS, {
+        /*
+         * One bounded window, one raised `maxPageSize`, one page slice — see
+         * `beginSearchWindow`. Hand-writing the three is how the other ten
+         * repositories each ended up with two of them, which reads as a working
+         * multi-word search and silently cannot reach page 2.
+         */
+        const win = beginSearchWindow(model, plan);
+        const result = await this.sieveQuery(win.model, ScammerRepository.SIEVE_FIELDS, {
             baseQuery,
             defaultPageSize: 20,
-            maxPageSize: 50,
+            maxPageSize: win.maxPageSize(50),
         });
-        return refineSearchTxt(result, plan.rest);
+        return win.finish(result);
     }
     /** Derived on every write path via `applyWriteHooks`. */
     buildSearchTxtFor(data) {
@@ -56,12 +63,19 @@ class ScammerRepository extends BaseRepository {
         if (plan.head) {
             baseQuery = baseQuery.where(SCAMMER_FIELDS.SEARCH_TXT, "array-contains", plan.head);
         }
-        const result = await this.sieveQuery(model, ScammerRepository.SIEVE_FIELDS, {
+        /*
+         * One bounded window, one raised `maxPageSize`, one page slice — see
+         * `beginSearchWindow`. Hand-writing the three is how the other ten
+         * repositories each ended up with two of them, which reads as a working
+         * multi-word search and silently cannot reach page 2.
+         */
+        const win = beginSearchWindow(model, plan);
+        const result = await this.sieveQuery(win.model, ScammerRepository.SIEVE_FIELDS, {
             baseQuery,
             defaultPageSize: 50,
-            maxPageSize: 200,
+            maxPageSize: win.maxPageSize(200),
         });
-        return refineSearchTxt(result, plan.rest);
+        return win.finish(result);
     }
     async findBySeoSlug(seoSlug) {
         try {

package/dist/features/seller/components/SellerProductShell.d.ts

@@ -53,7 +53,7 @@ export interface SellerProductDraft {
     video?: MediaField;
     youtubeId?: string;
     price?: number;
-    compareAtPrice?: number;
+    originalPrice?: number;
     stockQuantity?: number;
     featured?: boolean;
     isPromoted?: boolean;

package/dist/features/seller/components/SellerProductShell.js

@@ -388,7 +388,7 @@ const TYPE_SPECIFIC_SECTIONS = {
 function StepPricing({ values, onChange, listingType, }) {
     const listingPlugin = pluginForMode(listingType);
     const priceLabel = listingPlugin.priceLabel;
-    return (_jsxs(Stack, { gap: "md", children: [_jsx(Alert, { variant: "info", children: "All prices in Indian Rupees (\u20B9)." }), _jsxs(FormGroup, { columns: 2, children: [_jsx(FormField, { name: "price", label: priceLabel, type: "number", value: toRupeesString(values.price), onChange: (v) => onChange({ price: fromRupeesString(v) }), placeholder: "999" }), _jsx(FormField, { name: "compareAtPrice", label: "Compare-at Price (\u20B9, optional)", type: "number", value: toRupeesString(values.compareAtPrice), onChange: (v) => onChange({ compareAtPrice: v ? fromRupeesString(v) : undefined }), placeholder: "1299", helpText: "Original price shown as strikethrough" })] }), listingPlugin.showsStockQuantity && (_jsx(FormField, { name: "stockQuantity", label: "Stock Quantity", type: "number", value: String(values.stockQuantity ?? ""), onChange: (v) => onChange({ stockQuantity: Number(v) }), placeholder: "1" })), _jsxs(FormGroup, { columns: 2, children: [_jsx(Toggle, { checked: !!values.featured, onChange: (checked) => onChange({ featured: checked }), label: "Mark as Featured" }), _jsx(Toggle, { checked: !!values.isNew, onChange: (checked) => onChange({ isNew: checked }), label: "Mark as New Arrival" })] }), _jsx(Toggle, { checked: !!values.allowOffers, onChange: (checked) => onChange({
+    return (_jsxs(Stack, { gap: "md", children: [_jsx(Alert, { variant: "info", children: "All prices in Indian Rupees (\u20B9)." }), _jsxs(FormGroup, { columns: 2, children: [_jsx(FormField, { name: "price", label: priceLabel, type: "number", value: toRupeesString(values.price), onChange: (v) => onChange({ price: fromRupeesString(v) }), placeholder: "999" }), _jsx(FormField, { name: "originalPrice", label: "Compare-at Price (\u20B9, optional)", type: "number", value: toRupeesString(values.originalPrice), onChange: (v) => onChange({ originalPrice: v ? fromRupeesString(v) : undefined }), placeholder: "1299", helpText: "Original price shown as strikethrough" })] }), listingPlugin.showsStockQuantity && (_jsx(FormField, { name: "stockQuantity", label: "Stock Quantity", type: "number", value: String(values.stockQuantity ?? ""), onChange: (v) => onChange({ stockQuantity: Number(v) }), placeholder: "1" })), _jsxs(FormGroup, { columns: 2, children: [_jsx(Toggle, { checked: !!values.featured, onChange: (checked) => onChange({ featured: checked }), label: "Mark as Featured" }), _jsx(Toggle, { checked: !!values.isNew, onChange: (checked) => onChange({ isNew: checked }), label: "Mark as New Arrival" })] }), _jsx(Toggle, { checked: !!values.allowOffers, onChange: (checked) => onChange({
                     allowOffers: checked,
                     minOfferPercent: checked
                         ? values.minOfferPercent ?? DEFAULT_MIN_OFFER_PERCENT
@@ -643,7 +643,7 @@ productId, onSave, onPublish, onDiscard, isLoading = false, storeSlug, renderCat
             required: true,
             quick: true,
             // `gstRate` / `hsnCode` deliberately absent — admin-only, see StepPricing.
-            fields: ["price", "compareAtPrice", "stockQuantity", "allowOffers", "minOfferPercent"],
+            fields: ["price", "originalPrice", "stockQuantity", "allowOffers", "minOfferPercent"],
             render: ({ values, onChange }) => (_jsx(StepPricing, { values: values, onChange: onChange, listingType: listingType })),
             // Built per render because whether stock is required depends on the
             // listing type's own plugin — a digital code has no stock to speak of.

package/dist/features/seller/repository/offer.repository.js

@@ -4,7 +4,7 @@
  * Data access layer for the `offers` Firestore collection.
  * Handles buyer make-an-offer, seller counter/accept/decline lifecycle.
  */
-import { planSearchTxt, refineSearchTxt, emptySearchResult, } from "../../../utils/search-txt-query.js";
+import { planSearchTxt, beginSearchWindow, emptySearchResult, } from "../../../utils/search-txt-query.js";
 import { buildOfferSearchTxt } from "../../../utils/search-txt-builders.js";
 import { BaseRepository, prepareForFirestore, parseSieveDateValue, } from "../../../providers/db-firebase/index.js";
 import { OFFER_COLLECTION, OFFER_FIELDS, OFFER_TRACKED_FIELDS, createOfferId } from "../schemas/index.js";
@@ -43,12 +43,19 @@ class OfferRepository extends BaseRepository {
         if (plan.head) {
             baseQuery = baseQuery.where("searchTxt", "array-contains", plan.head);
         }
-        const result = await this.sieveQuery(model, OfferRepository.SIEVE_FIELDS, {
+        /*
+         * One bounded window, one raised `maxPageSize`, one page slice — see
+         * `beginSearchWindow`. Hand-writing the three is how the other ten
+         * repositories each ended up with two of them, which reads as a working
+         * multi-word search and silently cannot reach page 2.
+         */
+        const win = beginSearchWindow(model, plan);
+        const result = await this.sieveQuery(win.model, OfferRepository.SIEVE_FIELDS, {
             baseQuery,
             defaultPageSize: 50,
-            maxPageSize: 200,
+            maxPageSize: win.maxPageSize(200),
         });
-        return refineSearchTxt(result, plan.rest);
+        return win.finish(result);
     }
     // --- Create --------------------------------------------------------------
     async create(input) {
@@ -113,10 +120,18 @@ class OfferRepository extends BaseRepository {
             if (plan.head) {
                 baseQuery = baseQuery.where(OFFER_FIELDS.SEARCH_TXT, "array-contains", plan.head);
             }
-            const result = await this.sieveQuery(model, OfferRepository.SIEVE_FIELDS, {
+            /*
+             * One bounded window, one raised `maxPageSize`, one page slice — see
+             * `beginSearchWindow`. Hand-writing the three is how the other ten
+             * repositories each ended up with two of them, which reads as a working
+             * multi-word search and silently cannot reach page 2.
+             */
+            const win = beginSearchWindow(model, plan);
+            const result = await this.sieveQuery(win.model, OfferRepository.SIEVE_FIELDS, {
                 baseQuery,
+                maxPageSize: win.maxPageSize(100),
             });
-            return refineSearchTxt(result, plan.rest);
+            return win.finish(result);
         }
         const snap = await this.getCollection()
             .where(OFFER_FIELDS.STORE_ID, "==", storeId)

package/dist/features/seller/schemas/product-form.d.ts

@@ -65,7 +65,7 @@ export declare const productDraftSchema: z.ZodObject<{
     youtubeId: z.ZodOptional<z.ZodString>;
     externalVideoUrl: z.ZodOptional<z.ZodString>;
     price: z.ZodOptional<z.ZodNumber>;
-    compareAtPrice: z.ZodOptional<z.ZodNumber>;
+    originalPrice: z.ZodOptional<z.ZodNumber>;
     stockQuantity: z.ZodOptional<z.ZodNumber>;
     featured: z.ZodOptional<z.ZodBoolean>;
     isPromoted: z.ZodOptional<z.ZodBoolean>;
@@ -155,7 +155,7 @@ export declare const productDraftSchema: z.ZodObject<{
     youtubeId: z.ZodOptional<z.ZodString>;
     externalVideoUrl: z.ZodOptional<z.ZodString>;
     price: z.ZodOptional<z.ZodNumber>;
-    compareAtPrice: z.ZodOptional<z.ZodNumber>;
+    originalPrice: z.ZodOptional<z.ZodNumber>;
     stockQuantity: z.ZodOptional<z.ZodNumber>;
     featured: z.ZodOptional<z.ZodBoolean>;
     isPromoted: z.ZodOptional<z.ZodBoolean>;
@@ -245,7 +245,7 @@ export declare const productDraftSchema: z.ZodObject<{
     youtubeId: z.ZodOptional<z.ZodString>;
     externalVideoUrl: z.ZodOptional<z.ZodString>;
     price: z.ZodOptional<z.ZodNumber>;
-    compareAtPrice: z.ZodOptional<z.ZodNumber>;
+    originalPrice: z.ZodOptional<z.ZodNumber>;
     stockQuantity: z.ZodOptional<z.ZodNumber>;
     featured: z.ZodOptional<z.ZodBoolean>;
     isPromoted: z.ZodOptional<z.ZodBoolean>;

package/dist/features/seller/schemas/product-form.js

@@ -64,7 +64,7 @@ export const productDraftSchema = z
     externalVideoUrl: z.string().optional(),
     // Pricing
     price: z.number().optional(),
-    compareAtPrice: z.number().optional(),
+    originalPrice: z.number().optional(),
     stockQuantity: z.number().optional(),
     featured: z.boolean().optional(),
     isPromoted: z.boolean().optional(),

package/dist/features/server-errors/repository/server-errors.repository.js

@@ -39,6 +39,17 @@ export class ServerErrorsRepository extends BaseRepository {
                 requestId: input.requestId,
                 ...(input.userAgent ? { userAgent: input.userAgent } : {}),
                 ...(input.bodyDigest ? { bodyDigest: input.bodyDigest } : {}),
+                /*
+                 * 🛑 D10, and the G2 sweep is what found it: this hand-picked
+                 * field list is exactly Root Cause #38's shape. `entityType` and
+                 * `entityId` were on `ServerErrorDocument` AND accepted by this
+                 * method's own `Omit<…>` input type — so a caller passing them
+                 * type-checked clean and the fields died right here, on the one
+                 * line nobody re-reads. A write that succeeds is not a field that
+                 * persists.
+                 */
+                ...(input.entityType ? { entityType: input.entityType } : {}),
+                ...(input.entityId ? { entityId: input.entityId } : {}),
             };
             await ref.set(doc);
         }

package/dist/features/server-errors/schemas/firestore.d.ts

@@ -31,6 +31,21 @@ export type ServerErrorDocument = {
     userAgent?: string;
     /** sha256(requestBody) — for diagnosis without leaking PII. */
     bodyDigest?: string;
+    /**
+     * D10 — WHAT the failure was about, when that is narrower than `route`.
+     *
+     * 🛑 Absent means UNKNOWN, never "not a page". Every row written before this
+     * field existed has no value, so any filter over it must treat a missing
+     * `entityType` as INCLUDED — a default-exclusive filter would hide every
+     * pre-existing row and manufacture a backfill nobody budgeted for.
+     *
+     * `"page"` is the one value a user-submitted report can produce (see
+     * `ReportEntityType`), which is what lets an operator line a visitor's
+     * "this page is broken" up against the server-side rows for the same route.
+     */
+    entityType?: "page" | "product" | "store" | "order" | "listing";
+    /** The entity the failure was about — a path for `entityType: "page"`. */
+    entityId?: string;
 };
 export declare const SERVER_ERROR_FIELDS: {
     readonly ID: "id";
@@ -46,6 +61,8 @@ export declare const SERVER_ERROR_FIELDS: {
     readonly REQUEST_ID: "requestId";
     readonly USER_AGENT: "userAgent";
     readonly BODY_DIGEST: "bodyDigest";
+    readonly ENTITY_TYPE: "entityType";
+    readonly ENTITY_ID: "entityId";
 };
 export declare const SERVER_ERROR_STACK_MAX_BYTES = 4096;
 export declare const SERVER_ERROR_RETENTION_DAYS = 30;

package/dist/features/server-errors/schemas/firestore.js

@@ -13,6 +13,8 @@ export const SERVER_ERROR_FIELDS = {
     REQUEST_ID: "requestId",
     USER_AGENT: "userAgent",
     BODY_DIGEST: "bodyDigest",
+    ENTITY_TYPE: "entityType",
+    ENTITY_ID: "entityId",
 };
 export const SERVER_ERROR_STACK_MAX_BYTES = 4096;
 export const SERVER_ERROR_RETENTION_DAYS = 30;

package/dist/features/store-extensions/repository/store-extensions.repositories.d.ts

@@ -14,7 +14,7 @@
  */
 import { BaseRepository } from "../../../providers/db-firebase";
 import type { DocumentSnapshot } from "firebase-admin/firestore";
-import { type AnalyticsAlertDocument, type AnalyticsCardDocument, type ItemRequestDocument, type ListingTemplateDocument, type ModerationQueueDocument, type PayoutMethodDocument, type ReportDocument, type ShippingConfigDocument, type StoreCategoryDocument, type StoreGoogleConfigDocument, type StoreWhatsAppConfigDocument } from "../schemas/firestore";
+import { type AnalyticsAlertDocument, type AnalyticsCardDocument, type ItemRequestDocument, type ItemRequestReply, type ListingTemplateDocument, type ModerationQueueDocument, type PayoutMethodDocument, type ReportDocument, type ShippingConfigDocument, type StoreCategoryDocument, type StoreGoogleConfigDocument, type StoreWhatsAppConfigDocument } from "../schemas/firestore";
 export declare class PayoutMethodsRepository extends BaseRepository<PayoutMethodDocument> {
     /**
      * Bank/UPI details, encrypted at rest by BaseRepository's write hooks.
@@ -86,6 +86,22 @@ export declare class ItemRequestsRepository extends BaseRepository<ItemRequestDo
     listByOwner(opUserId: string): Promise<{
         items: ItemRequestDocument[];
     }>;
+    /**
+     * Append one reply atomically.
+     *
+     * 🛑 F1 #9 — the route did `replies: [...doc.replies, entry]` plus
+     * `replyCount: doc.replyCount + 1`. That is a read-modify-write on both
+     * fields: two people replying within the same second each read N replies and
+     * each wrote N+1, so the second write silently DISCARDED the first reply and
+     * the count agreed with it. Nothing errored, and the losing reply simply
+     * never existed.
+     *
+     * `arrayUnion` + `increment` are server-side operations, so the two writes
+     * compose instead of racing. `arrayUnion` de-duplicates by deep equality,
+     * which is harmless here and faintly useful: the entry carries a unique
+     * `id`, so a retried request appends once rather than twice.
+     */
+    appendReply(id: string, reply: ItemRequestReply): Promise<void>;
 }
 export declare class StoreWhatsAppConfigRepository extends BaseRepository<StoreWhatsAppConfigDocument> {
     constructor();

package/dist/features/store-extensions/repository/store-extensions.repositories.js

@@ -13,6 +13,7 @@
  * The other ten hold no PII and use the BaseRepository public API only.
  */
 import { BaseRepository } from "../../../providers/db-firebase/index.js";
+import { arrayUnion, increment } from "../../../contracts/field-ops.js";
 import { decryptPiiFields } from "../../../security/pii-encrypt.js";
 import { ANALYTICS_ALERTS_COLLECTION, ANALYTICS_CARDS_COLLECTION, ITEM_REQUESTS_COLLECTION, LISTING_TEMPLATES_COLLECTION, MODERATION_QUEUE_COLLECTION, PAYOUT_METHODS_COLLECTION, REPORTS_COLLECTION, SHIPPING_CONFIGS_COLLECTION, STORE_CATEGORIES_COLLECTION, STORE_GOOGLE_CONFIG_COLLECTION, STORE_WHATSAPP_CONFIG_COLLECTION, } from "../schemas/firestore.js";
 export class PayoutMethodsRepository extends BaseRepository {
@@ -117,6 +118,36 @@ export class ItemRequestsRepository extends BaseRepository {
         const items = await this.findBy("opUserId", opUserId);
         return { items };
     }
+    /**
+     * Append one reply atomically.
+     *
+     * 🛑 F1 #9 — the route did `replies: [...doc.replies, entry]` plus
+     * `replyCount: doc.replyCount + 1`. That is a read-modify-write on both
+     * fields: two people replying within the same second each read N replies and
+     * each wrote N+1, so the second write silently DISCARDED the first reply and
+     * the count agreed with it. Nothing errored, and the losing reply simply
+     * never existed.
+     *
+     * `arrayUnion` + `increment` are server-side operations, so the two writes
+     * compose instead of racing. `arrayUnion` de-duplicates by deep equality,
+     * which is harmless here and faintly useful: the entry carries a unique
+     * `id`, so a retried request appends once rather than twice.
+     */
+    async appendReply(id, reply) {
+        /*
+         * Written through the collection directly rather than `update()`, because
+         * `prepareForFirestore` would walk the sentinels as if they were plain
+         * values. Same shape `categories.repository` uses for its own
+         * `arrayUnion` writes.
+         */
+        await this.getCollection()
+            .doc(id)
+            .update({
+            replies: arrayUnion(reply),
+            replyCount: increment(1),
+            updatedAt: new Date(),
+        });
+    }
 }
 export class StoreWhatsAppConfigRepository extends BaseRepository {
     constructor() {

package/dist/features/store-extensions/schemas/firestore.d.ts

@@ -171,7 +171,7 @@ export interface ModerationQueueDocument extends BaseDocument {
 export declare const MODERATION_QUEUE_COLLECTION: "moderationQueue";
 export declare const MODERATION_QUEUE_INDEXED_FIELDS: readonly ["status", "mediaType", "entityType", "entityId", "storeId", "ownerId", "submittedAt", "createdAt"];
 export declare const DEFAULT_MODERATION_QUEUE_DATA: Partial<ModerationQueueDocument>;
-export type ReportEntityType = "product" | "store" | "review" | "event" | "user" | "blog" | "comment";
+export type ReportEntityType = "product" | "store" | "review" | "event" | "user" | "blog" | "comment" | "page" | "message";
 export type ReportStatus = "pending" | "under-review" | "actioned" | "dismissed";
 export type ReportReason = "scam" | "counterfeit" | "prohibited" | "inappropriate" | "harassment" | "spam" | "ip-violation" | "other";
 export interface ReportDocument extends BaseDocument {

package/dist/features/store-extensions/schemas/firestore.js

@@ -139,6 +139,10 @@ const REPORT_ENTITY_TYPE_MAP = {
     user: true,
     blog: true,
     comment: true,
+    // D10 — a broken PAGE. `entityId` carries the path.
+    page: true,
+    // D9 — a chat message.
+    message: true,
 };
 export const REPORT_ENTITY_TYPES = Object.keys(REPORT_ENTITY_TYPE_MAP);
 const REPORT_REASON_MAP = {

package/dist/features/stores/repository/store.repository.js

@@ -12,7 +12,7 @@ import { normalizeError } from "../../../errors/normalize.js";
 import { encryptSecret, decryptSecret, } from "../../../security/settings-encryption.js";
 import { withHistory } from "../../../_internal/shared/history/index.js";
 import { buildStoreSearchTxt } from "../../../utils/search-txt-builders.js";
-import { planSearchTxt, refineSearchTxt, emptySearchResult, } from "../../../utils/search-txt-query.js";
+import { planSearchTxt, beginSearchWindow, emptySearchResult, } from "../../../utils/search-txt-query.js";
 export class StoreRepository extends BaseRepository {
     constructor() {
         super(STORE_COLLECTION);
@@ -220,9 +220,17 @@ export class StoreRepository extends BaseRepository {
         if (plan.head) {
             baseQuery = baseQuery.where(STORE_FIELDS.SEARCH_TXT, "array-contains", plan.head);
         }
+        /*
+         * One bounded window, one raised `maxPageSize`, one page slice — see
+         * `beginSearchWindow`. Hand-writing the three is how the other ten
+         * repositories each ended up with two of them, which reads as a working
+         * multi-word search and silently cannot reach page 2.
+         */
+        const win = beginSearchWindow(model, plan);
         const result = await applySieveToFirestore({
             baseQuery,
-            model,
+            model: win.model,
+            options: { maxPageSize: win.maxPageSize(100) },
             fields: sieveFields,
             // Called DIRECTLY, not through `sieveQuery`, so the mapper has to be
             // passed by hand — and it is the list mapper, never `mapDoc`. With
@@ -230,7 +238,7 @@ export class StoreRepository extends BaseRepository {
             // WhatsApp bearer token and a list has no use for it.
             mapDoc: (snap) => this.mapDocForList(snap),
         });
-        const searched = refineSearchTxt(result, plan.rest);
+        const searched = win.finish(result);
         /*
          * 🛑 The rating threshold is applied IN MEMORY, deliberately.
          *

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

@@ -0,0 +1,2 @@
+import type { AuthoredCase } from "./_types";
+export declare const authored: Record<string, AuthoredCase>;

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,