@mohasinac/appkit 4.53.1 → 4.54.0

package/dist/features/stores/schemas/firestore.d.ts

@@ -254,28 +254,6 @@ export interface StoreDocument extends BaseDocument {
      * than trusting that nobody adds it.
      */
     returnsDirectToSeller?: boolean;
-    whatsappConfig?: {
-        /** Seller's WhatsApp Business phone number, digits-only with country code e.g. "919876543210" */
-        phoneNumber?: string;
-        /** Meta WABA ID for this store */
-        wabaId?: string;
-        /** Meta Commerce Catalog ID linked to this store */
-        catalogId?: string;
-        /** Encrypted access token (AES-256-GCM via encryptPii) — never returned to client */
-        accessToken?: string;
-        /** Whether catalog sync is enabled for this store */
-        catalogSyncEnabled: boolean;
-        /** Timestamp of last successful catalog sync */
-        lastCatalogSyncAt?: Date;
-        /** Number of products synced in last run */
-        lastSyncCount?: number;
-        /** Status of last sync attempt */
-        lastSyncStatus?: "success" | "partial" | "failed";
-        /** True when wabaId + catalogId + accessToken are all set */
-        connected: boolean;
-        /** When the seller first connected their account */
-        connectedAt?: Date;
-    };
     /**
      * Who changed what, when, and why. See § "Status History" in CLAUDE.md.
      *
@@ -300,9 +278,12 @@ export interface StoreDocument extends BaseDocument {
  */
 export declare const STORE_TRACKED_FIELDS: readonly ["status", "isPublic", "isVerified", "isFeatured", "suspensionReason", "capabilities"];
 /**
- * PII on this document, for `withHistory`'s scrub. `whatsappConfig.accessToken`
- * is a live Meta credential; `mapDoc` decrypts it on EVERY read, so it is
- * present in memory whenever a diff runs.
+ * PII on this document, for the `withHistory` scrub.
+ *
+ * `accessToken` stays listed although the WhatsApp integration that produced
+ * one was removed 2026-10-20: a scrub list is cheap, and a future secret
+ * reaching this document under that name should be scrubbed by default
+ * rather than by someone remembering to add it.
  */
 export declare const STORE_HISTORY_PII_FIELDS: readonly ["accessToken", "payoutDetails", "upiVpa", "accountNumber"];
 export type { StoreCapability } from "../../auth/permissions/constants";

package/dist/features/stores/schemas/firestore.js

@@ -33,9 +33,12 @@ export const STORE_TRACKED_FIELDS = [
     "capabilities",
 ];
 /**
- * PII on this document, for `withHistory`'s scrub. `whatsappConfig.accessToken`
- * is a live Meta credential; `mapDoc` decrypts it on EVERY read, so it is
- * present in memory whenever a diff runs.
+ * PII on this document, for the `withHistory` scrub.
+ *
+ * `accessToken` stays listed although the WhatsApp integration that produced
+ * one was removed 2026-10-20: a scrub list is cheap, and a future secret
+ * reaching this document under that name should be scrubbed by default
+ * rather than by someone remembering to add it.
  */
 export const STORE_HISTORY_PII_FIELDS = [
     "accessToken",

package/dist/features/stores/schemas/index.d.ts

@@ -228,7 +228,7 @@ export declare const storeFirestoreSchema: z.ZodObject<{
         totalReviews: number;
         averageRating?: number | undefined;
     }>>;
-    capabilities: z.ZodOptional<z.ZodArray<z.ZodString, "many">>;
+    capabilities: z.ZodOptional<z.ZodArray<z.ZodEnum<[string, ...string[]]>, "many">>;
     customCommissionRate: z.ZodOptional<z.ZodNumber>;
     googleReviews: z.ZodOptional<z.ZodObject<{
         placeId: z.ZodString;
@@ -347,60 +347,6 @@ export declare const storeFirestoreSchema: z.ZodObject<{
         defaultProviderId: string;
     }>>;
     emiEnabled: z.ZodOptional<z.ZodBoolean>;
-    whatsappConfig: z.ZodOptional<z.ZodObject<{
-        phoneNumber: z.ZodOptional<z.ZodString>;
-        wabaId: z.ZodOptional<z.ZodString>;
-        catalogId: z.ZodOptional<z.ZodString>;
-        accessToken: z.ZodOptional<z.ZodString>;
-        catalogSyncEnabled: z.ZodBoolean;
-        lastCatalogSyncAt: z.ZodOptional<z.ZodUnion<[z.ZodDate, z.ZodString, z.ZodObject<{
-            toDate: z.ZodFunction<z.ZodTuple<[], z.ZodUnknown>, z.ZodDate>;
-        }, "passthrough", z.ZodTypeAny, z.objectOutputType<{
-            toDate: z.ZodFunction<z.ZodTuple<[], z.ZodUnknown>, z.ZodDate>;
-        }, z.ZodTypeAny, "passthrough">, z.objectInputType<{
-            toDate: z.ZodFunction<z.ZodTuple<[], z.ZodUnknown>, z.ZodDate>;
-        }, z.ZodTypeAny, "passthrough">>]>>;
-        lastSyncCount: z.ZodOptional<z.ZodNumber>;
-        lastSyncStatus: z.ZodOptional<z.ZodEnum<["success", "partial", "failed"]>>;
-        connected: z.ZodBoolean;
-        connectedAt: z.ZodOptional<z.ZodUnion<[z.ZodDate, z.ZodString, z.ZodObject<{
-            toDate: z.ZodFunction<z.ZodTuple<[], z.ZodUnknown>, z.ZodDate>;
-        }, "passthrough", z.ZodTypeAny, z.objectOutputType<{
-            toDate: z.ZodFunction<z.ZodTuple<[], z.ZodUnknown>, z.ZodDate>;
-        }, z.ZodTypeAny, "passthrough">, z.objectInputType<{
-            toDate: z.ZodFunction<z.ZodTuple<[], z.ZodUnknown>, z.ZodDate>;
-        }, z.ZodTypeAny, "passthrough">>]>>;
-    }, "strip", z.ZodTypeAny, {
-        catalogSyncEnabled: boolean;
-        connected: boolean;
-        phoneNumber?: string | undefined;
-        accessToken?: string | undefined;
-        wabaId?: string | undefined;
-        catalogId?: string | undefined;
-        lastCatalogSyncAt?: string | Date | z.objectOutputType<{
-            toDate: z.ZodFunction<z.ZodTuple<[], z.ZodUnknown>, z.ZodDate>;
-        }, z.ZodTypeAny, "passthrough"> | undefined;
-        lastSyncCount?: number | undefined;
-        lastSyncStatus?: "success" | "failed" | "partial" | undefined;
-        connectedAt?: string | Date | z.objectOutputType<{
-            toDate: z.ZodFunction<z.ZodTuple<[], z.ZodUnknown>, z.ZodDate>;
-        }, z.ZodTypeAny, "passthrough"> | undefined;
-    }, {
-        catalogSyncEnabled: boolean;
-        connected: boolean;
-        phoneNumber?: string | undefined;
-        accessToken?: string | undefined;
-        wabaId?: string | undefined;
-        catalogId?: string | undefined;
-        lastCatalogSyncAt?: string | Date | z.objectInputType<{
-            toDate: z.ZodFunction<z.ZodTuple<[], z.ZodUnknown>, z.ZodDate>;
-        }, z.ZodTypeAny, "passthrough"> | undefined;
-        lastSyncCount?: number | undefined;
-        lastSyncStatus?: "success" | "failed" | "partial" | undefined;
-        connectedAt?: string | Date | z.objectInputType<{
-            toDate: z.ZodFunction<z.ZodTuple<[], z.ZodUnknown>, z.ZodDate>;
-        }, z.ZodTypeAny, "passthrough"> | undefined;
-    }>>;
 }, "strip", z.ZodTypeAny, {
     status: "pending" | "active" | "rejected" | "suspended";
     id: string;
@@ -470,22 +416,6 @@ export declare const storeFirestoreSchema: z.ZodObject<{
         maxReviews?: number | undefined;
         minRating?: number | undefined;
     } | undefined;
-    whatsappConfig?: {
-        catalogSyncEnabled: boolean;
-        connected: boolean;
-        phoneNumber?: string | undefined;
-        accessToken?: string | undefined;
-        wabaId?: string | undefined;
-        catalogId?: string | undefined;
-        lastCatalogSyncAt?: string | Date | z.objectOutputType<{
-            toDate: z.ZodFunction<z.ZodTuple<[], z.ZodUnknown>, z.ZodDate>;
-        }, z.ZodTypeAny, "passthrough"> | undefined;
-        lastSyncCount?: number | undefined;
-        lastSyncStatus?: "success" | "failed" | "partial" | undefined;
-        connectedAt?: string | Date | z.objectOutputType<{
-            toDate: z.ZodFunction<z.ZodTuple<[], z.ZodUnknown>, z.ZodDate>;
-        }, z.ZodTypeAny, "passthrough"> | undefined;
-    } | undefined;
 }, {
     status: "pending" | "active" | "rejected" | "suspended";
     id: string;
@@ -555,22 +485,6 @@ export declare const storeFirestoreSchema: z.ZodObject<{
         maxReviews?: number | undefined;
         minRating?: number | undefined;
     } | undefined;
-    whatsappConfig?: {
-        catalogSyncEnabled: boolean;
-        connected: boolean;
-        phoneNumber?: string | undefined;
-        accessToken?: string | undefined;
-        wabaId?: string | undefined;
-        catalogId?: string | undefined;
-        lastCatalogSyncAt?: string | Date | z.objectInputType<{
-            toDate: z.ZodFunction<z.ZodTuple<[], z.ZodUnknown>, z.ZodDate>;
-        }, z.ZodTypeAny, "passthrough"> | undefined;
-        lastSyncCount?: number | undefined;
-        lastSyncStatus?: "success" | "failed" | "partial" | undefined;
-        connectedAt?: string | Date | z.objectInputType<{
-            toDate: z.ZodFunction<z.ZodTuple<[], z.ZodUnknown>, z.ZodDate>;
-        }, z.ZodTypeAny, "passthrough"> | undefined;
-    } | undefined;
 }>;
 export type StoreFromSchema = z.infer<typeof storeFirestoreSchema>;
 /** Zod schema for store status — use instead of inline `z.enum(["pending",...])`. */

package/dist/features/stores/schemas/index.js

@@ -1,6 +1,7 @@
 export * from "./firestore.js";
 import { z } from "zod";
 import { StoreStatusValues } from "./firestore.js";
+import { ALL_STORE_CAPABILITIES } from "../../auth/permissions/constants.js";
 import { auditTimestampsShape, firestoreDateSchema, rupeesSchema } from "../../../schemas/firestore-helpers.js";
 // ─── Firestore document schema (W2) ───────────────────────────────────────────
 // Mirrors StoreDocument in ./firestore.ts. Registered into SCHEMAS.firestore.stores.
@@ -70,7 +71,15 @@ export const storeFirestoreSchema = z.object({
         averageRating: z.number().optional(),
     })
         .optional(),
-    capabilities: z.array(z.string()).optional(),
+    /*
+     * 🛑 A `z.enum`, not `z.array(z.string())`. Nothing used to check a stored
+     * capability against the union, so a typo saved successfully and the gate it
+     * was meant to open never opened — with no error anywhere, because an
+     * unrecognised capability is indistinguishable from an ungranted one.
+     */
+    capabilities: z
+        .array(z.enum(ALL_STORE_CAPABILITIES))
+        .optional(),
     customCommissionRate: z.number().min(0).max(100).optional(),
     googleReviews: z
         .object({
@@ -83,20 +92,6 @@ export const storeFirestoreSchema = z.object({
         .optional(),
     shippingConfig: storeShippingConfigSchema.optional(),
     emiEnabled: z.boolean().optional(),
-    whatsappConfig: z
-        .object({
-        phoneNumber: z.string().optional(),
-        wabaId: z.string().optional(),
-        catalogId: z.string().optional(),
-        accessToken: z.string().optional(),
-        catalogSyncEnabled: z.boolean(),
-        lastCatalogSyncAt: firestoreDateSchema.optional(),
-        lastSyncCount: z.number().int().optional(),
-        lastSyncStatus: z.enum(["success", "partial", "failed"]).optional(),
-        connected: z.boolean(),
-        connectedAt: firestoreDateSchema.optional(),
-    })
-        .optional(),
     ...auditTimestampsShape,
 });
 /** Zod schema for store status — use instead of inline `z.enum(["pending",...])`. */

package/dist/features/tester/seed-data/authored/admin__site-system.js

@@ -174,54 +174,6 @@ export const authored = {
         expectedUiState: "With the toggle OFF, /checkout offers only whichever of manual UPI/cash and COD are separately enabled — no 'Pay Online (PhonePe)' button. With it back ON, the button reappears.",
         endResult: "The toggle is restored to ON, matching the state before this case started.",
     },
-    "checklist-admin-site-system-whatsapp-credentials-persist": {
-        roles: ["admin"],
-        startPage: "/admin/site",
-        steps: [
-            "Sign in as admin@letitrip.in / TempPass123!.",
-            "Open /admin/site, switch to the Integrations tab, and WRITE DOWN every WhatsApp field and its current masked state before touching anything.",
-            "Type QA-WA-TOKEN-552310 into the access-token field and fill any account identifier fields.",
-            "Save and RELOAD, then read how each field displays.",
-            "Open /api/site-settings in a private window and search for QA-WA-TOKEN-552310.",
-            "Open a public store page's source and search for it too.",
-            "RESTORE every field to exactly what step 3 recorded — clearing is not restoring, and a real Meta token cleared here cannot be recovered from the seed. Save and reload to confirm.",
-        ],
-        inputs: { token: "QA-WA-TOKEN-552310" },
-        expectedBehaviour: "The token is encrypted at rest and masked on read. It is also decrypted on every read of a store document, so any page handing a raw store document to a client component serialises it into public HTML — which is why both the settings response and a public store page are checked rather than the admin form alone.",
-        expectedUiState: "After the reload the token displays masked. Neither the public settings response nor a public store page's source contains it.",
-        expectedData: { tokenInPublicSurfaces: 0 },
-        endResult: "The fields are cleared by the final step.",
-    },
-    "checklist-admin-site-system-whatsapp-channel-toggle-persists": {
-        roles: ["admin"],
-        startPage: "/admin/site",
-        steps: [
-            "Sign in as admin@letitrip.in / TempPass123!.",
-            "Open /admin/site, switch to the Notifications tab, and read every channel toggle and its state. Four are listed: in-app, email, WhatsApp and SMS.",
-            "Turn the WHATSAPP channel off and save. Pick that one specifically — SMS is seeded OFF (and has no sender at all), so toggling it off would be a no-op that proves nothing.",
-            "RELOAD and read every toggle.",
-            "Check only the one changed.",
-            "Turn it back on, save, and reload to confirm.",
-        ],
-        expectedBehaviour: "Off is the direction that proves persistence when the default is on: a toggle that never saves reads back as its default and passes a test that only ever turns it on. Saving one toggle must not rewrite the rest.",
-        expectedUiState: "After the reload the toggled channel is off and every other is unchanged. A toggle that has reverted to on is the failure, and the save reported success.",
-        endResult: "The toggle is restored.",
-    },
-    "checklist-admin-site-system-whatsapp-order-announcement-fires": {
-        roles: ["admin", "buyer"],
-        startPage: "/admin/site",
-        steps: [
-            "Sign in as admin@letitrip.in / TempPass123! and confirm the WhatsApp order channel is enabled.",
-            "Read whether real credentials are configured or whether the fields are empty.",
-            "Sign in as rehan.sheikh@gmail.com / TempPass123! and place an order that would trigger an order announcement.",
-            "Read whether the buyer opted into WhatsApp updates and what fee was charged for it.",
-            "Check the in-app notification for the order arrived.",
-            "If real credentials are configured, check whether a WhatsApp message arrived.",
-        ],
-        expectedBehaviour: "WhatsApp order announcements are a paid per-store add-on, so the charge and the delivery must agree — a buyer charged the add-on fee and sent nothing is the failure that matters. With no credentials configured, the dispatch skips cleanly rather than failing loudly: the Meta secrets are seeded as empty strings rather than placeholders for exactly that reason.",
-        expectedUiState: "The in-app notification arrives regardless. With credentials configured a message arrives; without them nothing is sent and no error surfaces to the buyer. A charged add-on with no delivery is the finding.",
-        endResult: "One order exists. Record whether credentials were configured — the case reads differently either way.",
-    },
     "checklist-admin-site-system-auction-bid-tiers-admin": {
         roles: ["admin", "buyer"],
         startPage: "/admin/site",

package/dist/features/tester/seed-data/authored/buying__buying-checkout.js

@@ -226,46 +226,6 @@ export const authored = {
         expectedData: { otpRequiredAbove: true, otpRequiredBelow: false },
         endResult: "Entering the correct code completes the order. Three items only add to ₹4,597 — the fourth is what actually crosses the threshold, and an earlier draft of this case stopped at three and could never have triggered the prompt it was checking for.",
     },
-    "checklist-buying-buying-checkout-checkout-otp-whatsapp-hidden-without-phone": {
-        roles: ["buyer"],
-        startPage: "/checkout",
-        steps: [
-            "Sign in as admin@letitrip.in / TempPass123! and confirm Site Settings → Notifications → WhatsApp → 'WhatsApp OTP' is enabled.",
-            "Sign in as rehan.sheikh@gmail.com / TempPass123!.",
-            "Open /user/addresses and add an address named 'QA Address otp-whatsapp-hidden', 2 Test Road, Mumbai, Maharashtra 400001, leaving the phone field empty.",
-            "Add product-beyblade-original-dranzer-s (₹1,499), product-beyblade-original-driger-v (₹1,799), product-beyblade-metal-storm-pegasus (₹1,299) and product-beyblade-burst-regalia-genesis (₹1,399) to the cart, making ₹5,996.",
-            "Open /checkout, select 'QA Address otp-whatsapp-hidden' on Step 1, and continue to the payment step.",
-            "Select a non-COD payment method.",
-            "Read every option offered on the OTP prompt.",
-        ],
-        inputs: { addressLabel: "QA Address otp-whatsapp-hidden", phone: "", subtotal: 5996 },
-        expectedBehaviour: "The WhatsApp channel needs three things at once — admin-enabled, real credentials, and a phone number on the SELECTED address. Missing the third hides the option rather than offering it and failing at send time, which would waste the buyer's OTP window on a channel that could never deliver.",
-        expectedUiState: "The prompt offers email only. There is no 'Send via WhatsApp instead' control, disabled or otherwise, even though the same setting shows one for an address that has a phone.",
-        expectedData: { whatsappOptionPresent: false },
-        endResult: "The order still completes by email OTP. Delete the address afterwards so it does not accumulate across runs.",
-    },
-    "checklist-buying-buying-checkout-checkout-otp-whatsapp-option": {
-        roles: ["buyer"],
-        startPage: "/checkout",
-        steps: [
-            "Sign in as admin@letitrip.in / TempPass123! and confirm Site Settings → Notifications → WhatsApp → 'WhatsApp OTP' is enabled with real Meta Cloud API credentials.",
-            "Sign in as rehan.sheikh@gmail.com / TempPass123!.",
-            "Open /user/addresses and add a phone number to the existing address 'Home — 123 Stadium Lane, Vijay Nagar, Indore, Madhya Pradesh 452010' if it does not already have one.",
-            "Add product-beyblade-original-dranzer-s (₹1,499), product-beyblade-original-driger-v (₹1,799), product-beyblade-metal-storm-pegasus (₹1,299) and product-beyblade-burst-regalia-genesis (₹1,399) to the cart, making ₹5,996.",
-            "Open /cart and click 'Proceed to checkout'.",
-            "Select the address with a phone number on Step 1 and click 'Continue'.",
-            "Click 'Continue to payment' on Step 2.",
-            "On Step 3, select a non-COD payment method.",
-            "Read the default send channel shown on the OTP prompt.",
-            "Click 'Send via WhatsApp instead'.",
-            "Type the code received on WhatsApp into the OTP field and submit it.",
-        ],
-        inputs: { subtotal: 5996, defaultChannel: "email", alternateChannel: "WhatsApp" },
-        expectedBehaviour: "Email is the default channel and WhatsApp is opt-in per attempt. The alternate appears only when the feature is enabled, real Meta credentials are configured, and the selected address carries a phone — the seeded Meta secrets are empty strings rather than placeholders precisely so a missing credential skips cleanly instead of making a billed call that fails.",
-        expectedUiState: "The prompt first shows a masked email. After 'Send via WhatsApp instead' it shows a masked phone in the shape '+91 ••••••7890'. The code that arrives on WhatsApp is accepted and payment proceeds.",
-        expectedData: { defaultChannel: "email" },
-        endResult: "The order is placed after the WhatsApp code verifies. With no real Meta credentials configured this case is unreachable — answer null rather than reporting the missing option as a bug.",
-    },
     "checklist-buying-buying-checkout-checkout-phonepe-charge-includes-shipping": {
         roles: ["buyer"],
         startPage: "/checkout",

package/dist/features/tester/seed-data/authored/content-discovery__authenticity-checker.js

@@ -1,6 +1,6 @@
 /*
  * WHY: Authored six-part procedures for content-discovery/authenticity-checker.
- * WHAT: 16 cases, keyed by full checklist id.
+ * WHAT: 22 cases, keyed by full checklist id.
  *
  * 🛑 EVERY CASE IS WRITTEN AS BEFORE → AFTER, because this feature's whole
  * failure mode is a confident, plausible, wrong answer returned with HTTP 200. A
@@ -44,7 +44,7 @@ export const authored = {
         startPage: "/tools/authenticity",
         steps: [
             "Open /tools/authenticity signed out.",
-            "Confirm the LOOKUP FORM itself is there and usable — Model name, Code on the box, Brand, Generation, How it was sold, and a 'Check it' button.",
+            "Confirm the LOOKUP FORM itself is there and usable — 'Which bey is it?', 'Code on the box', a collapsed 'More details' holding the name-as-printed, brand, generation and how-it-was-sold fields, and a 'Check it' button.",
             "Confirm there is no sign-in card and no 'Sign in to run a lookup' text anywhere on the page.",
             "Enter A0813 as the code and submit, still signed out.",
             "Confirm a real assessment comes back rather than an error or a prompt to sign in.",
@@ -475,4 +475,116 @@ export const authoredTypeahead = {
         expectedUiState: "The result renders immediately. The network log shows no fetch to the search artifact or any /api/search* endpoint.",
         endResult: "Read-only; nothing persists.",
     },
+    /* ── The model picker and the per-model code list (2026-10-20) ──────────
+       * 🛑 The reported bug these exist for: typing "l drago" returned
+       * "Inconclusive — Nothing contradicts it, and nothing confirms it either",
+       * while the tool held 33 recorded box codes for Lightning L-Drago, 35 for
+       * Meteo and 27 for Destructor and had no way to reach any of them. Every
+       * table was keyed by CODE, so naming a bey could never surface them.
+       *
+       * So each case compares the answer against data the tool DEMONSTRABLY HAS.
+       * "Check the picker works" passes against the bug; "picking Lightning
+       * L-Drago must list its 33 codes" does not.
+       */
+    "checklist-content-discovery-authenticity-checker-model-picker-finds-l-drago": {
+        roles: ["guest"],
+        startPage: "/tools/authenticity",
+        steps: [
+            "Open /tools/authenticity.",
+            "Confirm the FIRST field is 'Which bey is it?' and is a searchable select, not a plain text box.",
+            "Open it and type: l drago",
+            "Confirm all three L-Drago releases are offered — Lightning L-Drago 100HF, Meteo L-Drago LW105LF and L-Drago Destructor F:S.",
+            "Confirm each offered row states how many box codes are on file for it.",
+            "Clear the search and type: pegasis",
+            "Confirm Storm Pegasus still appears, even though the list spells it Pegasus.",
+            "Answer no if 'l drago' offers nothing, or if the field is a free-text input with no list.",
+        ],
+        inputs: { search: "l drago" },
+        expectedBehaviour: "BEFORE: the first field was a free-text 'Model name'. Typing 'l drago' matched four releases, so the engine refused to pick one and returned an inconclusive verdict — correct, and useless, because the three L-Dragos it declined to choose between have 95 recorded box codes between them and the screen never said so. AFTER: the picker resolves exactly one bey, which is what unlocks the per-model code list. It searches aliases as well as labels, because Takara Tomy romanises the line Pegasis and Hasbro prints Pegasus — a label-only filter would find neither from the other.",
+        expectedUiState: "A searchable select labelled 'Which bey is it?' listing three L-Drago rows, each annotated with a box-code count. Beys with codes on file are offered before beys without.",
+        endResult: "Nothing is written. The picker only reads a bundled list.",
+    },
+    "checklist-content-discovery-authenticity-checker-picked-model-lists-its-box-codes": {
+        roles: ["guest"],
+        startPage: "/tools/authenticity",
+        steps: [
+            "Open /tools/authenticity.",
+            "In 'Which bey is it?', search for and pick: Lightning L-Drago 100HF",
+            "Leave 'Code on the box' EMPTY.",
+            "Press 'Check it'.",
+            "Read the verdict line, then look for a panel headed 'Box codes recorded for Lightning L-Drago 100HF'.",
+            "Count the codes it lists.",
+            "Answer no if the verdict is 'Inconclusive — Nothing contradicts it, and nothing confirms it either', or if no code list appears.",
+        ],
+        inputs: { modelSlug: "lightning-l-drago-100hf" },
+        expectedBehaviour: "BEFORE: naming this bey with no code produced 'Inconclusive — Nothing contradicts it, and nothing confirms it either' and a physical checklist. True, in that nothing had been checked — and it withheld the 33 box codes the tables record for this exact bey, which is the single most useful thing the tool holds and the one thing the user had asked for. AFTER: the verdict is 'I know this one. Now find the code stamped on the box.' — still not a judgement, because nothing has been checked, but with the next step named and the 33 codes listed to check against.",
+        expectedUiState: "Verdict badge 'Need a bit more', headline 'I know this one. Now find the code stamped on the box.', a caveat naming the count, and a panel listing 33 codes as badges. A link reading 'Everything we hold on Lightning L-Drago 100HF' points at the model's own category page.",
+        expectedData: { recordedCodes: 33 },
+        endResult: "Read-only.",
+    },
+    "checklist-content-discovery-authenticity-checker-picked-model-plus-its-own-code": {
+        roles: ["guest"],
+        startPage: "/tools/authenticity",
+        steps: [
+            "Pick 'Lightning L-Drago 100HF' in 'Which bey is it?'.",
+            "Enter A0910 in 'Code on the box' — a code recorded against this exact bey.",
+            "Press 'Check it' and read the verdict.",
+            "Expand 'How I got there' and find the row about the code.",
+            "Press 'Start over'. Pick Lightning L-Drago 100HF again, this time enter A0310 — a real code recorded against a DIFFERENT bey.",
+            "Read the verdict and expand the working-out again.",
+            "Answer no if the second case reads as a mismatch, a discrepancy, or anything implying the item is wrong.",
+        ],
+        inputs: { modelSlug: "lightning-l-drago-100hf", recordedCode: "A0910", otherBeyCode: "A0310" },
+        expectedBehaviour: "A0910 is in this bey's own list, so the check reads as agreement — the strongest thing the tool can say from data, and it still says so is not proof. A0310 is recorded, but on Earth Aquila: that is WEAK SUPPORT, not a mismatch, because a production date covers whatever was boxed that day. The distinction is the whole point. Reporting 'that code belongs to a different bey' as a discrepancy would manufacture suspicion out of how the tables are organised, and the panel highlights the code you entered inside the list so you can see where it sits.",
+        expectedUiState: "First run: 'Consistent with an original', and a row reading that the code is recorded on genuine boxes of this exact bey. Second run: still not adverse — a neutral row saying the code is recorded but not against this bey, with the phrase 'weak support rather than a mismatch'.",
+        endResult: "Read-only.",
+    },
+    "checklist-content-discovery-authenticity-checker-missing-code-is-not-an-accusation": {
+        roles: ["guest"],
+        startPage: "/tools/authenticity",
+        steps: [
+            "Pick 'Lightning L-Drago 100HF' in 'Which bey is it?'.",
+            "Enter Z9999 in 'Code on the box' — well-formed, and in none of the tables.",
+            "Press 'Check it'.",
+            "Read the verdict, the code panel and the working-out.",
+            "Answer no if any sentence implies the item is fake, counterfeit or a reproduction, or if the verdict is more severe than 'Inconclusive'.",
+        ],
+        inputs: { modelSlug: "lightning-l-drago-100hf", code: "Z9999" },
+        expectedBehaviour: "A code absent from a model's list means UNRECORDED, never wrong. These tables are what collectors photographed, not a manufacturing record: 38 of 221 canonical beys have any recorded code at all, new genuine codes turn up regularly, and counterfeiters print real codes anyway. The panel must say so where a user will actually read it, not only inside the collapsed working-out — the reading 'my code is not in the list, so it is fake' is the one this whole feature has to defend against.",
+        expectedUiState: "Verdict 'Inconclusive'. A neutral row reading 'Not among the 33 codes recorded for Lightning L-Drago 100HF' whose text says 'unrecorded, not wrong'. The code panel carries a line beginning 'A code missing from this list means unrecorded, not fake.'",
+        endResult: "Read-only.",
+    },
+    "checklist-content-discovery-authenticity-checker-working-out-is-collapsed-by-default": {
+        roles: ["guest"],
+        startPage: "/tools/authenticity",
+        steps: [
+            "Pick 'Lightning L-Drago 100HF' and enter A0910. Press 'Check it'.",
+            "WITHOUT expanding anything, confirm you can read the verdict badge, the headline, the caveat and the recorded-code list.",
+            "Confirm the reasoning is behind a single collapsed control reading 'How I got there — N checks'.",
+            "Expand it and confirm every individual check is still there, each with its own confidence chip.",
+            "Press 'Start over'. Now enter the code A0813 with no model picked — a code the sources record as a midfake batch.",
+            "Confirm the working-out is ALREADY OPEN this time, without being clicked.",
+            "Answer no if the reasoning is expanded by default on the clean run, or collapsed on the midfake run.",
+        ],
+        inputs: { modelSlug: "lightning-l-drago-100hf", cleanCode: "A0910", midfakeCode: "A0813" },
+        expectedBehaviour: "BEFORE: every check rendered expanded under a 'What I checked' heading — up to eleven rows of reasoning between the buyer and the answer they asked for. AFTER: it is collapsed, not deleted, because 'why should I believe this' has to stay one tap away for a tool whose entire posture is that it hedges and cites. A CONCERN forces it open: the one case where the reasoning IS the answer is the case where something is wrong, and the user who never expands it must not be the user who never finds out.",
+        expectedUiState: "Clean run: verdict block, code panel, a collapsed 'How I got there — N checks', then the physical checks. Midfake run: the same control, already open.",
+        endResult: "Read-only.",
+    },
+    "checklist-content-discovery-authenticity-checker-result-scrolls-into-view": {
+        roles: ["guest"],
+        startPage: "/tools/authenticity",
+        steps: [
+            "Resize the browser to a phone viewport (about 390 x 740) or use device emulation.",
+            "Pick 'Lightning L-Drago 100HF' and enter A0910.",
+            "Scroll so the 'Check it' button is visible, and note what is on screen.",
+            "Press 'Check it'.",
+            "Without scrolling yourself, confirm the verdict badge and headline are now on screen.",
+            "Answer no if the page does not move and the verdict is below the fold.",
+        ],
+        inputs: { viewport: "390x740", modelSlug: "lightning-l-drago-100hf", code: "A0910" },
+        expectedBehaviour: "BEFORE: the form is taller than a phone viewport, so the answer rendered below the fold and pressing 'Check it' looked like it had done nothing — at the one moment this tool must not be ambiguous. AFTER: the result is scrolled into view on every fresh assessment, including the re-run a clarifying question triggers, and anchored at the top of the viewport rather than the middle so the badge and headline land where the eye already is.",
+        expectedUiState: "After submitting, the verdict badge and headline are visible without manual scrolling.",
+        endResult: "Read-only.",
+    },
 };

package/dist/features/tester/seed-data/authored/selling__quick-add-minimum-details.js

@@ -81,22 +81,6 @@ export const authored = {
         expectedData: { published: true },
         endResult: "The listing survives a reload of the public page and appears in /store/products. Delete it afterwards.",
     },
-    "checklist-selling-quick-add-minimum-details-whatsapp-shows-the-same-fields": {
-        roles: ["seller"],
-        startPage: "/store/whatsapp",
-        steps: [
-            SIGN_IN_SELLER,
-            "Publish 'Minimum Details Probe' from /store/products/new as in the previous case, with Price 499.",
-            "Open /store/whatsapp and find the catalog preview.",
-            "Locate the tile for 'Minimum Details Probe'.",
-            "Read every piece of information the tile shows.",
-            "Compare that list against the fields the quick form asked for.",
-        ],
-        inputs: { title: "Minimum Details Probe", price: 499 },
-        expectedBehaviour: "What WhatsApp shows is a subset of what the short form collects — title, price, image, condition and stock. This is the reason the short form is the right shape: a seller who fills only it has already supplied everything a WhatsApp buyer will see, so nothing is missing from the channel most of them arrive through.",
-        expectedUiState: "The tile shows the image, the name and ₹499. Nothing on it is blank or a placeholder, and nothing it shows was absent from the quick form.",
-        endResult: "Read-only against the catalog preview. Delete the probe listing afterwards.",
-    },
     "checklist-selling-quick-add-minimum-details-advanced-flip-keeps-values": {
         roles: ["seller"],
         startPage: "/store/products/new",

package/dist/features/tester/seed-data/authored/selling__seller-guide.js

@@ -23,7 +23,7 @@ export const authored = {
             "Click 'All Guides' to reach /store/guide. It is a hub and it links the same six sub-guides, so each one has two routes in — check both agree.",
             "Open each of the six in turn and read its content: /store/guide/listings, /store/guide/orders, /store/guide/finance, /store/guide/settings, /store/guide/capabilities, /store/guide/whatsapp.",
             "Write down any that renders empty, 404s, or repeats another page's text.",
-            "Check each guide against the feature it describes — open that feature and confirm the guide's instructions match what is on screen. The WhatsApp guide is the one to read hardest: no seeded store carries a whatsappConfig, so a guide describing a configured integration describes a state no tester can reach.",
+            "Check each guide against the feature it describes — open that feature and confirm the guide's instructions match what is on screen.",
             "Follow every link inside the guides and note where each lands.",
         ],
         expectedBehaviour: "Every seller guide renders its own content and every link in it resolves. A guide describing a screen that has since changed is worse than no guide, because the seller trusts it and then cannot find what it names. The sidebar group defaulting closed is deliberate — guides are reference, not daily work — so a tester who does not expand it will wrongly conclude they are missing.",

package/dist/features/tester/seed-data/authored/selling__seller-marketing-extras.js

@@ -67,85 +67,6 @@ export const authored = {
         expectedUiState: "The message names the missing configuration in plain English. It does not surface a provider error code, an API key, or a raw response body. The public store page shows no empty Google reviews section.",
         endResult: "Nothing is synced. If credentials ARE configured on this environment, record that and read what the sync actually imported instead.",
     },
-    "checklist-selling-seller-marketing-extras-seller-whatsapp-catalog": {
-        roles: ["seller"],
-        startPage: "/store/whatsapp",
-        steps: [
-            "Sign in as tyson@beybladearena.in / TempPass123!.",
-            "Open /store/whatsapp and read every control.",
-            "Read what it says about the connection state.",
-            "Read whether it names the business account and catalog it would sync with.",
-            "Trigger a catalog action without a token configured and read the message.",
-        ],
-        expectedBehaviour: "The catalog surface reports its connection state honestly and declines cleanly when unconfigured. It is the reader of the store's WhatsApp configuration, which is stored encrypted and decrypted on every store read — so what this page shows is the one place the configuration is legitimately visible to its owner.",
-        expectedUiState: "The connection state is stated rather than implied. An unconfigured action produces a readable message naming what is missing, not a provider error. The business account and catalog identifiers are shown to the owner but partially masked.",
-        endResult: "Nothing is synced.",
-    },
-    "checklist-selling-seller-marketing-extras-seller-whatsapp-token-save": {
-        roles: ["seller", "guest"],
-        startPage: "/store/whatsapp",
-        steps: [
-            "Sign in as tyson@beybladearena.in / TempPass123!.",
-            "Open /store/whatsapp and type QA-WHATSAPP-TOKEN-118427 into the access-token field.",
-            "Save and RELOAD, then read how the token is displayed — a set token renders as a mask (••••••), never as the value typed.",
-            "Open the browser's View Source on that settings page and search for QA-WHATSAPP-TOKEN-118427.",
-            "Open /stores/store-beyblade-arena in a private window with no session.",
-            "Open View Source there and search for QA-WHATSAPP-TOKEN-118427 and for accessToken.",
-            "Clear the token field, save, and reload to confirm it is gone. Clearing is the correct ending here, unusually: no seeded store carries a whatsappConfig, so there is no prior value to restore and the field started empty.",
-        ],
-        inputs: { token: "QA-WHATSAPP-TOKEN-118427" },
-        expectedBehaviour: "The token is stored double-encrypted and shown masked to its owner. Because it is decrypted on every read of the store document, the real risk is a page that passes that document to a client component — which serialises it into the public page HTML. The PUBLIC page source is therefore the assertion, not the masked field.",
-        expectedUiState: "After the reload the owner sees a masked value rather than the full token. The public store page's source contains neither the token nor the word accessToken anywhere, including inside the embedded data payload.",
-        expectedData: { tokenInPublicSource: 0 },
-        endResult: "The token is cleared by the final step. A hit on the public page is a credential leak and fails the case outright, however the settings page renders.",
-    },
-    "checklist-selling-seller-marketing-extras-seller-whatsapp-import-runs-in-background": {
-        roles: ["seller"],
-        startPage: "/store/whatsapp",
-        steps: [
-            "Sign in as tyson@beybladearena.in / TempPass123!.",
-            "Open /store/whatsapp and start an import.",
-            "Read what the page shows immediately — whether it blocks or returns.",
-            "Navigate to another store page and back.",
-            "Read whether the import's progress is still reported.",
-            "Wait for it to finish and read the summary.",
-        ],
-        expectedBehaviour: "An import of unknown size is enqueued as a job rather than run inside the request — a route that fans out over a whole catalogue is exactly the shape the ten-second function ceiling kills in production while local runs pass. The page subscribes to the job's progress instead of waiting on a response.",
-        expectedUiState: "The page returns immediately with a job accepted rather than freezing. Progress survives navigating away and back. A completion summary states what was imported. A request that hangs and then times out is the failure this case exists for.",
-        endResult: "Whatever was imported persists. With no credentials configured the import will decline instead — record that rather than failing the case.",
-    },
-    "checklist-selling-seller-marketing-extras-seller-whatsapp-import-skips-already-synced": {
-        roles: ["seller"],
-        startPage: "/store/whatsapp",
-        steps: [
-            "Sign in as tyson@beybladearena.in / TempPass123!.",
-            "Open /store/whatsapp and run an import, noting the summary and the store's product count.",
-            "Run the SAME import a second time without changing anything.",
-            "Read the second summary and compare it against the first.",
-            "Open /store/products and read the product count again.",
-            "Search the products list for any duplicated title.",
-        ],
-        expectedBehaviour: "A second import skips what is already synced rather than creating duplicates. This is the same idempotency the seed data needs: an import keyed on a stable external identifier upserts, while one keyed on anything regenerated per run creates a fresh copy every time and reports success.",
-        expectedUiState: "The second summary reports items skipped rather than a second full import. The product count is unchanged and no title appears twice.",
-        expectedData: { duplicateTitles: 0 },
-        endResult: "No duplicates exist. A doubled product count after a repeated import is the failure, and the summary will still have read as successful. NOTE: no seeded store carries a whatsappConfig at all, so with no Meta credentials configured BOTH imports will decline and there is nothing to compare — record that and answer null rather than reading two declines as a pass. Two identical declines are not evidence that duplicates are skipped.",
-    },
-    "checklist-selling-seller-marketing-extras-seller-whatsapp-push-product-link-opens": {
-        roles: ["seller"],
-        startPage: "/store/products",
-        steps: [
-            "Sign in as tyson@beybladearena.in / TempPass123!.",
-            "Open /store/products and use the WhatsApp push or share control on 'Beyblade Burst B-01 Valkyrie'.",
-            "Read the message it composes before sending anything.",
-            "Read the product link inside it and note its host and path.",
-            "Open that link in a private window with no session.",
-            "Read the page it opens.",
-        ],
-        inputs: { productId: "product-beyblade-burst-valkyrie" },
-        expectedBehaviour: "The shared link is a public, canonical URL a stranger can open. There is one definition of the site host and everything derives from it — two owners drifted once and every sitemap URL pointed at a host that redirected, which is what took the site out of search.",
-        expectedUiState: "The message contains a link on the canonical host with an unprefixed path. Opening it signed out renders the product page directly rather than redirecting, and does not 404.",
-        endResult: "Nothing is sent. A link that redirects before landing is worth recording — every redirect is a hop a shared link pays on every open.",
-    },
     "checklist-selling-seller-marketing-extras-seller-reviews-response": {
         roles: ["seller", "guest"],
         startPage: "/store/reviews",

package/dist/features/tester/seed-data/authored/selling__seller-orders.js

@@ -141,7 +141,7 @@ export const authored = {
              * Measured 2026-09-29: SELLER_ROW_ACTIONS.orders is
              * [VIEW, EDIT, TRACK, RESEND] — no share. SellerOrdersView mentions
              * WhatsApp only as the buyer's purchased add-on flag
-             * (whatsappNotifyAddon / whatsappNotifyFee), and every `wa.me` link in
+             * only as `wa.me` links, and every one of those in
              * the codebase is on the contact page, the chat button or the buyer's own
              * payment page. The registry's WhatsApp actions are store SETUP
              * (whatsapp-connect, catalog-sync, catalog-import).