@mohasinac/appkit 4.53.2 → 4.54.1

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).