@mohasinac/appkit 4.42.1 → 4.42.3

package/dist/features/tester/seed-data/authored/admin__users-trust.js

@@ -80,11 +80,11 @@ export const authored = {
     },
     "checklist-admin-users-trust-roles-crud": {
         roles: ["admin"],
-        startPage: "/admin/team",
+        startPage: "/admin/roles",
         steps: [
             "Sign in as admin@letitrip.in / TempPass123!.",
-            "Open the roles or permissions surface and read every role and its permissions.",
-            "Read whether a permissions catalogue page exists and is reachable from the sidebar.",
+            "Open /admin/roles and read every role and its permissions.",
+            "Open /admin/permissions and confirm it redirects to /admin/roles?tab=permissions — it is a redirect-only shim, so the catalogue is a TAB rather than a page of its own. Check that tab is reachable from the sidebar under one name or the other.",
             "Create a role named 'QA Role users-trust' with two permissions and save.",
             "RELOAD and read its permissions.",
             "Edit it to add a third, save, RELOAD, and check the first two are still there.",
@@ -135,7 +135,7 @@ export const authored = {
         startPage: "/admin/addresses",
         steps: [
             "Sign in as admin@letitrip.in / TempPass123!.",
-            "Open the banned-addresses surface and read every column.",
+            "Open /admin/banned-addresses and read every column.",
             "Check each row shows the address, who banned it, when, and why.",
             "Read whether an unban request from the owner is visible on the row.",
             "Open one and read the requester's full note before deciding anything.",
@@ -151,7 +151,7 @@ export const authored = {
         startPage: "/admin/addresses",
         steps: [
             "Sign in as admin@letitrip.in / TempPass123!.",
-            "Open the address clusters surface and read what a cluster row represents.",
+            "Open /admin/address-clusters and read what a cluster row represents.",
             "Check each row states how many accounts share the address and names them.",
             "Open a cluster and read the accounts it groups.",
             "Read whether the shared address itself is shown in full or masked.",
@@ -167,7 +167,7 @@ export const authored = {
         startPage: "/admin/moderation",
         steps: [
             "Sign in as admin@letitrip.in / TempPass123!.",
-            "Open the moderation queue and read every row.",
+            "Open /admin/moderation and read every row.",
             "Check each row identifies what is being moderated and shows enough to judge it.",
             "Open one item and read its full content — text, images, whatever was submitted.",
             "Return to the list and check the same is reachable from the row itself.",
@@ -183,7 +183,7 @@ export const authored = {
         startPage: "/admin/moderation",
         steps: [
             "Sign in as admin@letitrip.in / TempPass123!.",
-            "Open the moderation queue and open an item.",
+            "Open /admin/moderation and open an item.",
             "Read its content, then choose Reject.",
             "Submit with the reason box empty and read what happens.",
             "Type 'Too short' and submit, reading what happens.",
@@ -216,7 +216,7 @@ export const authored = {
         startPage: "/admin/support-tickets",
         steps: [
             "Sign in as admin@letitrip.in / TempPass123!.",
-            "Open the admin support tickets surface and read every column.",
+            "Open /admin/support-tickets and read every column.",
             "Read every status filter and select each, noting any that returns nothing.",
             "Open a ticket and read the full message thread.",
             "Reply to it and change its status in the same action.",
@@ -232,7 +232,7 @@ export const authored = {
         startPage: "/admin/item-requests",
         steps: [
             "Sign in as admin@letitrip.in / TempPass123!.",
-            "Open the item-requests surface and read every row.",
+            "Open /admin/item-requests and read every row.",
             "Check each row shows the requested item's title and description rather than only a requester.",
             "Open one and read the full request before acting.",
             "Read the actions offered and check a view exists alongside them.",
@@ -250,7 +250,7 @@ export const authored = {
         startPage: "/user",
         steps: [
             "Sign in as rehan.sheikh@gmail.com / TempPass123!.",
-            "Open the item-request form from the buyer side.",
+            "Open /item-requests/new as the buyer — the public item-request form, not the admin queue at /admin/item-requests.",
             "Submit it completely empty and read where the errors appear.",
             "Type a title only and submit, reading what happens.",
             "Type a one-word description and submit, reading what happens.",
@@ -267,7 +267,7 @@ export const authored = {
         startPage: "/admin/reports",
         steps: [
             "Sign in as admin@letitrip.in / TempPass123!.",
-            "Open the reports surface and read every row.",
+            "Open /admin/reports and read every row.",
             "Check each row names what was reported and by whom, and shows the reporter's stated detail.",
             "Open one and read the full report before acting.",
             "Read every status filter and select each, noting any that returns nothing.",
@@ -299,7 +299,7 @@ export const authored = {
         startPage: "/admin/reports",
         steps: [
             "Sign in as admin@letitrip.in / TempPass123!.",
-            "Open the reports surface and open the report created by the buyer case.",
+            "Open /admin/reports and open the report created by the buyer case.",
             "Read its full detail, then choose Dismiss.",
             "Submit with the reason empty and read what happens.",
             "Type 'QA Dismissal users-trust — reviewed, no policy breach.' and submit.",
@@ -315,7 +315,7 @@ export const authored = {
         startPage: "/admin/reports",
         steps: [
             "Sign in as admin@letitrip.in / TempPass123!.",
-            "Open the reports surface and open an open report.",
+            "Open /admin/reports and open an open report.",
             "Note the current date and time.",
             "Close the report with a resolution note.",
             "RELOAD and read the closed date shown.",
@@ -331,10 +331,10 @@ export const authored = {
         startPage: "/admin/reports",
         steps: [
             "Sign in as admin@letitrip.in / TempPass123!.",
-            "Open the reports surface and read every status the status control offers.",
+            "Open /admin/reports and read every status the status control offers.",
             "Write the list down.",
             "Select each in turn on a test report and confirm each is accepted.",
-            "Open the reports list and read every status filter chip.",
+            "Open /admin/reports and read every status filter chip.",
             "Compare the chip list against the status list from the editor.",
             "Note any chip naming a status the editor cannot set, or any status the editor sets that has no chip.",
         ],
@@ -347,7 +347,7 @@ export const authored = {
         startPage: "/admin/catalogue-approvals",
         steps: [
             "Sign in as admin@letitrip.in / TempPass123!.",
-            "Open the catalogue approvals surface and read every row.",
+            "Open /admin/catalogue-approvals and read every row.",
             "Check each row shows the submitted item's photos, description and price.",
             "Read every status filter and select each.",
             "Open one submission and read everything the user submitted.",
@@ -362,7 +362,7 @@ export const authored = {
         startPage: "/admin/catalogue-approvals",
         steps: [
             "Sign in as admin@letitrip.in / TempPass123!.",
-            "Open the catalogue approvals surface and find a pending submission.",
+            "Open /admin/catalogue-approvals and find a pending submission.",
             "WITHOUT using Approve or Reject, find a way to open the submission in full.",
             "Read every photo at full size and the complete description.",
             "Read the price the submitter set and any linked marketplace listing.",
@@ -377,7 +377,7 @@ export const authored = {
         startPage: "/admin/payment-methods",
         steps: [
             "Sign in as admin@letitrip.in / TempPass123!.",
-            "Open the payment-methods clusters surface and read what a row represents.",
+            "Open /admin/payment-methods and read what a row represents.",
             "Check each row states how many accounts share the instrument and names them.",
             "Read how the payment identifier itself is displayed.",
             "Search the page source for a full card or UPI identifier.",
@@ -522,7 +522,7 @@ export const authored = {
         startPage: "/admin",
         steps: [
             "Sign in as admin@letitrip.in / TempPass123!.",
-            "Open the homepage sections editor and open the section type picker.",
+            "Open /admin/sections and open the section type picker.",
             "Write down every type offered.",
             "Compare the list against the section types the homepage can render.",
             "Create one of each type not already present, saving after each.",
@@ -538,7 +538,7 @@ export const authored = {
         startPage: "/admin/site",
         steps: [
             "Sign in as admin@letitrip.in / TempPass123!.",
-            "Open the analytics alert settings and find the threshold field.",
+            "Open /admin/analytics and find the threshold field.",
             "Type abc into it and attempt to save.",
             "Read where any error appears.",
             "Type -5 and attempt to save, reading what happens.",

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

@@ -168,8 +168,25 @@ export const authored = {
             "Read the bidder identity, amount and timestamp on every visible row.",
         ],
         expectedBehaviour: "Bidder names are masked on the way out of the server, not hidden in the renderer. The masking helper for bids once returned its input unchanged while being named as though it masked — every bidder's real name was in the public payload and nothing displayed it, so the leak was invisible from the screen. Displaying the masked name is what makes that checkable by eye.",
-        expectedUiState: "Each row reads in the shape '₹3,199.00 · M*** B*** · 4 Sept, 17:06'. The name is genuinely masked — asterisks in the middle — and is not a full readable name, and not a placeholder like 'Bidder'. The timestamp carries both a date and a clock time, not a date alone.",
-        endResult: "The same masked names and timestamps appear after reload. A real full name — 'Meera Bey', 'Rohit Collector' or 'Ananya Collector', the three seeded bidders on this auction — anywhere in these rows is a PII leak and fails the case outright.",
+        /*
+         * 🛑 THE FORBIDDEN NAMES WERE FICTIONAL, SO THE PII CHECK PASSED VACUOUSLY.
+         *
+         * This asserted that 'Meera Bey', 'Rohit Collector' or 'Ananya Collector'
+         * must not appear. Those three strings occur ZERO times in the seed: the
+         * personas' displayName values are "Mock User 11", "Mock User 14" and
+         * "Mock User 9". So the assertion could never fail — it would report a
+         * clean PII check whether masking worked or not, which is the one outcome
+         * worse than no check at all.
+         *
+         * The masked shape was wrong for the same reason: 'M*** B***' is the mask
+         * of "Meera Bey". maskName splits on whitespace and keeps each word's first
+         * character, so "Mock User 11" becomes "M*** U*** 11***".
+         *
+         * Bidder uids are right (meera-bey, rohit-collector, ananya-collector all
+         * bid on this auction) — only the names they resolve to were invented.
+         */
+        expectedUiState: "Each row reads in the shape '₹3,199.00 · M*** U*** 11*** · 4 Sept, 17:06'. The name is genuinely masked — every word reduced to its first character plus asterisks — and is not a full readable name, and not a placeholder like 'Bidder'. The timestamp carries both a date and a clock time, not a date alone.",
+        endResult: "The same masked names and timestamps appear after reload. An unmasked display name — 'Mock User 9', 'Mock User 11' or 'Mock User 14', the three seeded bidders on this auction — anywhere in these rows is a PII leak and fails the case outright.",
     },
     "checklist-buying-bidding-bid-increment-live-tier-change": {
         roles: ["buyer"],

package/dist/features/tester/seed-data/authored/buying__browsing-search.js

@@ -621,14 +621,29 @@ export const authored = {
             "Open /auctions.",
             "Click the 'Ended' tab.",
             "Scan the grid for 'Beyblade Burst B-128 Spriggan Requiem (Ended — Bought Out)' (auction-beyblade-burst-spriggan-requiem-bought-out).",
-            "Click the 'Live' tab.",
+            /*
+             * 🛑 'Available', not 'Live' — and on the next page 'Ended', not 'Closed'.
+             *
+             * `availabilityTabsFor` builds exactly three tabs and only the MIDDLE one
+             * varies: its label comes from HIDE_DEFAULT_NOUN, which maps every
+             * hideDefault onto "Sold" or "Ended" and nothing else. Prize-draw's
+             * `hideDefault: "closed"` maps to "Ended", so /prize-draws reads
+             * Available / Ended / All.
+             *
+             * The first tab is ALWAYS 'Available'. This case named it 'Live' on
+             * /auctions and 'Open' on /prize-draws, and called the prize-draw middle
+             * tab 'Closed' — three controls that render under different names, so the
+             * tester would hunt, fail to find them, and answer "could not test" on a
+             * feature that works.
+             */
+            "Click the 'Available' tab.",
             "Open /prize-draws.",
-            "Click the 'Closed' tab.",
+            "Click the 'Ended' tab.",
             "Scan the grid for 'Metal Fight Mystery Draw — Ended (Revealed)' (prizedraw-beyblade-metal-closed-revealed).",
-            "Click the 'Open' tab.",
+            "Click the 'Available' tab.",
         ],
-        expectedBehaviour: "The 'Available' / 'Live' / 'Open' tab hides sold-out, ended, and closed items by default. The 'Sold & Ended' / 'Ended' / 'Closed' tab reveals them.",
-        expectedUiState: "'Beyblade X BX-34 Dran Buster (Sold Out)' appears on the 'Sold & Ended' tab and is absent on 'Available'. 'Beyblade Burst B-128 Spriggan Requiem (Ended — Bought Out)' appears on 'Ended' and is absent on 'Live'. 'Metal Fight Mystery Draw — Ended (Revealed)' appears on 'Closed' and is absent on 'Open'.",
+        expectedBehaviour: "The 'Available' tab hides sold-out, ended and closed items on every listing page; the middle tab reveals them. Only the middle label varies by listing type — 'Sold & Ended' on /products, 'Ended' on /auctions and on /prize-draws.",
+        expectedUiState: "'Beyblade X BX-34 Dran Buster (Sold Out)' appears on the 'Sold & Ended' tab and is absent on 'Available'. 'Beyblade Burst B-128 Spriggan Requiem (Ended — Bought Out)' appears on /auctions' 'Ended' tab and is absent on 'Available'. 'Metal Fight Mystery Draw — Ended (Revealed)' appears on /prize-draws' 'Ended' tab and is absent on 'Available'. No page offers a tab labelled 'Live', 'Open' or 'Closed'.",
         endResult: "Nothing is persisted. Tab state is URL state only.",
     },
     "checklist-buying-browsing-search-sort-options-per-listing-type": {

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

@@ -337,14 +337,30 @@ export const authored = {
         roles: ["buyer"],
         startPage: "/checkout",
         steps: [
-            "Sign in as admin@letitrip.in / TempPass123! and set Site Settings → Checkout → Out-of-stock policy to 'Cancel whole order'.",
+            /*
+             * 🛑 THE BUYER CHOOSES THIS AT CHECKOUT — it is not an admin setting.
+             *
+             * This step said "Sign in as admin and set Site Settings → Checkout →
+             * Out-of-stock policy". There is no such setting: `outOfStockPolicy` is a
+             * POLICY_SECTIONS field rendered by CheckoutRouteClient and passed
+             * straight into createCheckoutOrder. It appears nowhere in the admin
+             * feature. A tester would have hunted through Site Settings, not found
+             * it, and answered "could not test".
+             *
+             * The option labels were wrong too — 'Cancel whole order' is the app's
+             * "Cancel my whole order", and the sibling case's 'Skip unavailable
+             * items' is actually "Ship what's available and refund the rest", which
+             * shares no words with what the case asked for.
+             */
             "Sign in as rehan.sheikh@gmail.com / TempPass123!.",
-            "Add product-beyblade-burst-valkyrie (₹999, stock 10) and product-beyblade-original-dranzer-s (₹149) to the cart.",
-            "While on the checkout payment step (before submitting), have the admin or another session reduce product-beyblade-burst-valkyrie's stock to 0.",
+            "Add product-beyblade-burst-valkyrie (₹999, stock 10) and product-beyblade-original-dranzer-s (₹1,499) to the cart.",
+            "Open /checkout and advance to the payment step.",
+            "Under 'If an item goes out of stock', select 'Cancel my whole order'.",
+            "Before submitting, have another session reduce product-beyblade-burst-valkyrie's stock to 0.",
             "Submit the checkout.",
         ],
-        inputs: { policy: "Cancel whole order", goesOutOfStock: "product-beyblade-burst-valkyrie" },
-        expectedBehaviour: "With the 'cancel whole order' policy, if any item in the batch goes out of stock mid-checkout, the entire checkout is rejected. No order is created and the buyer receives an error.",
+        inputs: { policy: "Cancel my whole order", goesOutOfStock: "product-beyblade-burst-valkyrie" },
+        expectedBehaviour: "With the cancel-whole-order policy, if any item in the batch goes out of stock mid-checkout, the entire checkout is rejected. No order is created and the buyer receives an error.",
         expectedUiState: "After submitting, an error message is shown indicating that an item went out of stock and the entire order was cancelled. No order confirmation page is shown.",
         expectedData: { ordersCreated: 0 },
         endResult: "After reloading /cart, both items are still present in the cart (or the buyer is able to restart the checkout). No order record exists for this attempt.",
@@ -353,14 +369,16 @@ export const authored = {
         roles: ["buyer"],
         startPage: "/checkout",
         steps: [
-            "Sign in as admin@letitrip.in / TempPass123! and set Site Settings → Checkout → Out-of-stock policy to 'Skip unavailable items'.",
+            /* Buyer-chosen at checkout, not an admin setting — see the sibling case. */
             "Sign in as rehan.sheikh@gmail.com / TempPass123!.",
-            "Add product-beyblade-burst-valkyrie (₹999, stock 10) and product-beyblade-original-dranzer-s (₹149) to the cart.",
-            "While on the checkout payment step (before submitting), have the admin or another session reduce product-beyblade-original-dranzer-s's stock to 0.",
+            "Add product-beyblade-burst-valkyrie (₹999, stock 10) and product-beyblade-original-dranzer-s (₹1,499) to the cart.",
+            "Open /checkout and advance to the payment step.",
+            "Under 'If an item goes out of stock', select 'Ship what's available and refund the rest'.",
+            "Before submitting, have another session reduce product-beyblade-original-dranzer-s's stock to 0.",
             "Submit the checkout.",
         ],
-        inputs: { policy: "Skip unavailable items", goesOutOfStock: "product-beyblade-original-dranzer-s" },
-        expectedBehaviour: "With the 'skip unavailable items' policy, the out-of-stock item is silently dropped and an order is placed for only the still-available item(s). The buyer is informed which item was skipped.",
+        inputs: { policy: "Ship what's available and refund the rest", goesOutOfStock: "product-beyblade-original-dranzer-s" },
+        expectedBehaviour: "With the ship-what's-available policy, the out-of-stock item is dropped and an order is placed for only the still-available item(s). The buyer is informed which item was skipped.",
         expectedUiState: "After submitting, the order confirmation page shows only product-beyblade-burst-valkyrie (₹999). A notice is shown indicating that product-beyblade-original-dranzer-s was unavailable and was removed from the order.",
         expectedData: { orderLineCount: 1 },
         endResult: "After reloading the order detail page, only product-beyblade-burst-valkyrie is listed in the order. product-beyblade-original-dranzer-s is not included.",

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

@@ -601,7 +601,7 @@ export const authored = {
         startPage: "/store/bundles",
         steps: [
             "Sign in as tyson@beybladearena.in / TempPass123!.",
-            "Open the store's bundles surface and start creating one.",
+            "Open /store/bundles and start creating one.",
             "Add a member from this store and one from a different store.",
             "Save and read the message.",
             "Check the message names the offending member or store.",
@@ -729,7 +729,7 @@ export const authored = {
             "Open /cart and read the Won Auctions tab.",
             "Check the line is gone.",
             "Open /user/bids and read that bid's status.",
-            "Open the notification list and read the forfeiture entry.",
+            "Open /user/notifications and read the forfeiture entry.",
             "Check the Cart tab's checkout is now enabled again.",
         ],
         expectedBehaviour: "An unpaid win past its deadline is forfeited, the locked line cleared and the buyer notified. Clearing the line is what unblocks the rest of the cart — a leftover locked line keeps the auction lane non-empty and that lane outranks the others, so the buyer's whole cart stays blocked indefinitely.",
@@ -945,7 +945,14 @@ export const authored = {
         startPage: "/cart",
         steps: [
             "Sign in as rehan.sheikh@gmail.com / TempPass123! with items from TWO sellers.",
-            "Open /cart and tick 'WhatsApp order updates' on ONE seller's card only.",
+            /*
+             * 'WhatsApp updates' — the label StoreAddonsPicker actually renders,
+             * under an 'Add-ons' heading on each seller's card. This said 'WhatsApp
+             * order updates', which appears nowhere; CartPriceBreakdown's matching
+             * FEE LINE reads 'WhatsApp updates' too, so neither surface uses the
+             * longer form.
+             */
+            "Open /cart and tick 'WhatsApp updates' under 'Add-ons' on ONE seller's card only.",
             "Read that seller's fee lines and the aggregate breakdown.",
             "Check the fee is charged once at ₹10.00, not ₹20.00.",
             "Check the other seller's card shows no such fee.",

package/dist/features/tester/seed-data/authored/buying__image-tile-layout.js

@@ -87,22 +87,6 @@ export const authored = {
         expectedUiState: "Every tile shows its image above its caption, all at the same width, at both viewport sizes. An image sitting beside its caption and squeezed narrow is the row-direction failure.",
         endResult: "Read-only; restore the window width afterwards.",
     },
-    "checklist-buying-image-tile-layout-concern-card-icon-above-label": {
-        roles: ["guest"],
-        startPage: "/",
-        steps: [
-            "Open / in a private window at 1280 pixels wide.",
-            "Find the concern or trust cards and look at each one.",
-            "Check each card's icon sits above its label rather than beside it.",
-            "Compare the icon's size against the card's own height.",
-            "Resize to 390 pixels and check the arrangement holds.",
-            "Switch to dark mode and check the icons are still visible.",
-        ],
-        inputs: { desktopWidth: 1280, mobileWidth: 390 },
-        expectedBehaviour: "These cards carry an explicitly-sized icon box, which is what kept them from collapsing entirely when the wrapper defect hit — but an explicit size does not fix the direction, so they still laid the icon out beside the label. Sizing and direction are two separate failures and this card had only one of them.",
-        expectedUiState: "Each card shows its icon above its label at both widths, with the icon proportionate to the card. An icon beside its label, or one at the platform font's fallback size, are different failures and should be reported as such.",
-        endResult: "Read-only; return to light mode and restore the width.",
-    },
     "checklist-buying-image-tile-layout-media-picker-existing-grid": {
         roles: ["seller"],
         startPage: "/store/products/new",

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

@@ -242,11 +242,33 @@ export const authored = {
         roles: ["buyer"],
         startPage: "/user/orders",
         steps: [
-            "Sign in as an account whose inbox you can open and confirm order emails are enabled in its notification settings.",
-            "Place an order and note the time.",
-            "Open the inbox and wait up to five minutes for a confirmation email.",
-            "Read its From name, its subject and its body.",
-            "Have the seller mark the order shipped, then check the inbox again.",
+            /*
+             * 🛑 THE ACCOUNT MUST BE THE HARNESS MAILBOX, AND NO SEEDED PERSONA IS.
+             *
+             * This step used to read "an account whose inbox you can open", which is
+             * not a literal value and quietly hid a real constraint. Two mechanisms
+             * can settle an email case, and BOTH key on TESTER_EMAIL_ID:
+             *
+             *   - check-inbox.mjs reads that mailbox over IMAP
+             *   - the emailEvents recorder writes a row ONLY when the recipient
+             *     equals TESTER_EMAIL_ID (or EMAIL_RECORDER_ALL is set)
+             *
+             * Every seeded persona uses a real-looking address the harness does not
+             * own, so an order placed as rehan produces nothing either instrument can
+             * see. Gmail plus-addressing is the way in: a fresh signup at
+             * <harness-mailbox>+run3@gmail.com is delivered to the same inbox.
+             *
+             * Capture the timestamp BEFORE placing the order. The mailbox is shared
+             * across every case in every run, so "newest matching message" will
+             * happily return one an earlier case left behind — which reads as a pass
+             * for an email this action never sent.
+             */
+            "Register a new account at /auth/register using the harness mailbox with a run-stamped plus-address (the value of TESTER_EMAIL_ID in tester/.env, e.g. name+run3@gmail.com), and confirm order emails are enabled in its notification settings.",
+            "Run `node -e \"console.log(Date.now())\"` and keep that number.",
+            "Place an order as that account.",
+            "Run `node tester/scripts/check-inbox.mjs --since <that number> --subject \"order\"` and read the exit code: 0 the mail arrived, 1 it did not, 2 the mailbox could not be opened.",
+            "Read the message's From name, its subject and its body.",
+            "Have the seller mark the order shipped, capture a fresh timestamp, and run check-inbox.mjs again with --subject \"shipped\".",
             "Click a link inside each email and read where it lands.",
             "Compare each email's figures against the order itself.",
         ],

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

@@ -52,10 +52,10 @@ export const authored = {
             "Read the row — product, offered amount, listed price, status and round.",
             "Open the row action menu and read every action offered.",
             "Use Counter, then cancel out of the form without submitting.",
-            "Use Decline on a DIFFERENT pending offer and read what happens.",
+            "Use Reject on a DIFFERENT pending offer and read what happens.",
             "Reload and read that offer's status.",
         ],
-        expectedBehaviour: "The seller's list shows incoming offers with the context needed to decide, and Accept, Decline and Counter all act. The store keeps sole authority over its own pricing — this is the surface where that authority lives.",
+        expectedBehaviour: "The seller's list shows incoming offers with the context needed to decide, and Accept, Reject and Counter all act. The store keeps sole authority over its own pricing — this is the surface where that authority lives.",
         expectedUiState: "Rows show product, amounts, status and round. All three actions are present and act. The declined offer reads as declined after the reload.",
         endResult: "One offer is declined; QA Offer make-offer is untouched.",
     },
@@ -82,7 +82,7 @@ export const authored = {
         steps: [
             "Sign in as tyson@beybladearena.in / TempPass123!.",
             "Open /store/offers and find a pending offer.",
-            "WITHOUT using Accept, Decline or Counter, find a way to open its details.",
+            "WITHOUT using Accept, Reject or Counter, find a way to open its details.",
             "Read the buyer's note, the listed price, the offered amount and the round.",
             "Read any earlier rounds in the same negotiation.",
             "Return to the list and check the same is reachable from the row.",
@@ -243,12 +243,12 @@ export const authored = {
             "Sign in as admin@letitrip.in / TempPass123!.",
             "Open the admin offers surface and open a pending offer's row menu.",
             "Read every action offered and write the list down.",
-            "Check for Accept, Counter or Decline.",
+            "Check for Accept, Counter or Reject.",
             "Select several rows and read any bulk action bar that appears.",
             "Read whether a bulk cancel is offered.",
         ],
         expectedBehaviour: "Admin is a coordinator, not a participant: only View and Cancel. The store keeps sole authority over its own pricing. There is deliberately no bulk cancel — one shared reason across a heterogeneous selection is worse audit data than none, and a registry-backed control that reads as working while doing nothing is worse than an absent one.",
-        expectedUiState: "The menu offers View and Cancel only. No Accept, Counter or Decline. No bulk cancel appears — and if one does, it must actually act rather than only clearing the selection.",
+        expectedUiState: "The menu offers View and Cancel only. No Accept, Counter or Reject. No bulk cancel appears — and if one does, it must actually act rather than only clearing the selection.",
         expectedData: { adminActions: 2 },
         endResult: "Read-only; act on nothing.",
     },
@@ -259,11 +259,26 @@ export const authored = {
             "Sign in as tyson@beybladearena.in / TempPass123!.",
             "Open /store/offers and open a pending offer's row menu.",
             "Read every action offered.",
-            "Check Accept, Counter and Decline are all present.",
+            "Check Accept, Counter and Reject are all present.",
             "Use Accept on one and reload.",
             "Read the offer's status and check the buyer's cart gains a line for it.",
         ],
-        expectedBehaviour: "Adding an admin surface must not have removed the store's own actions. The seller retains Accept, Counter and Decline — an admin coordinating a dispute is a different capability from the seller deciding their own price.",
+        expectedBehaviour: 
+        /*
+         * 'Reject', not 'Decline'. SellerOffersView renders its row menu from
+         * ACTIONS.STORE["accept-offer" | "counter-offer" | "reject-offer"], whose
+         * labels are Accept / Counter / Reject. Nothing in the menu says Decline.
+         *
+         * The confusion is real and worth naming: the offer STATUS is `declined`,
+         * and this project's own docs describe the seller as able to
+         * "accept / counter / decline". Both are true of the outcome — but a case
+         * tells a tester which BUTTON to click, and that button says Reject.
+         *
+         * Note SELLER_ROW_ACTIONS.offers ([VIEW, APPROVE, REJECT]) is NOT what
+         * this view uses, so reading the action-defs preset would give a third
+         * answer again.
+         */
+        "Adding an admin surface must not have removed the store's own actions. The seller retains Accept, Counter and Reject — an admin coordinating a dispute is a different capability from the seller deciding their own price.",
         expectedUiState: "All three actions are present and Accept works. The accepted offer reads accepted and produces a cart line in the buyer's offer lane.",
         endResult: "One offer is accepted.",
     },

package/dist/features/tester/seed-data/authored/buying__order-detail-actions.js

@@ -33,7 +33,7 @@ export const authored = {
             "Read what the browser does with the response.",
         ],
         expectedBehaviour: "The invoice is generated on demand and streamed by a route that checks the order belongs to the caller. It is not a stored file and has no public URL.",
-        expectedUiState: "A file downloads rather than rendering in the tab, and its name contains the order id. Not a JSON blob and not an error page.",
+        expectedUiState: "The invoice opens as a readable print view with a Print / Save as PDF control — it is not a JSON blob and not an error page. It does NOT download a file, and that is by design. Check the MONEY: every fee in the total must have its own row, so Subtotal + Shipping + each fee equals the stated Total exactly.",
         expectedData: { invoiceDownloaded: true },
         endResult: "The order is unchanged by downloading its invoice; the row still shows the same status after a reload.",
     },
@@ -106,12 +106,12 @@ export const authored = {
         startPage: "/user/orders",
         steps: [
             "Sign in as rehan.sheikh@gmail.com / TempPass123! — this persona owns the seeded SHIPPED order.",
-            "Open /user/orders and open order-1-20251104-aevnlw.",
+            "Open /user/orders and open order-1-20251122-481j4x.",
             "Use the Track action.",
             "Read every step on the timeline and note which carry a date and which do not.",
             "Compare the dates shown against the order's own placed and shipped dates.",
         ],
-        inputs: { orderId: "order-1-20251104-aevnlw" },
+        inputs: { orderId: "order-1-20251122-481j4x" },
         expectedBehaviour: "Each timeline step shows the date actually recorded for it. A step with no recorded date renders an em-dash rather than a guess — an invented or estimated date is worse than a blank, because it cannot be told apart from a real one.",
         expectedUiState: "The placed and shipped steps carry dates matching the order. Steps the order has not reached show no date rather than today's.",
         expectedData: { fabricatedDatesShown: false },

package/dist/features/tester/seed-data/authored/buying__product-detail.js

@@ -126,7 +126,22 @@ export const authored = {
         ],
         inputs: { productId: "digitalcode-beyblade-x-app-starter-pack", price: 199, codesAvailable: 25, paymentMethod: "Cash on Delivery" },
         expectedBehaviour: "This fixture is auto-claim, so the code is allocated and delivered as soon as the order is confirmed, with no seller action in between. The pool's remaining count drops by one. The listing advertises 25 codes on the product document, but the codes themselves live in a subcollection the seed does not write — so the pool must be stocked first from the seller's Digital Content pool manager on /store/products, or the purchase completes and delivers nothing, which is the exact defect this case exists to catch.",
-        expectedUiState: "The order page shows a digital-code panel containing an actual code string that can be selected and copied. It does not read 'Pending delivery' or 'Waiting for seller' — for an auto-claim listing those states mean the delivery never fired.",
+        /*
+         * 🛑 THE FORBIDDEN STATES DID NOT EXIST, SO THE ASSERTION COULD NOT FAIL.
+         *
+         * This forbade 'Pending delivery' and 'Waiting for seller'. Neither string
+         * is anywhere in the source: CodeRevealPanel renders 'Your Digital Code',
+         * 'Your Digital Content', 'Your download', 'Copied!' and one error —
+         * 'Could not retrieve your code. Please try again.'
+         *
+         * That matters more here than on most pages. Root Cause #103 is exactly
+         * this failure: the pool had no writer, so every purchase logged "code pool
+         * exhausted", returned silently, completed the order normally, and left the
+         * reveal answering 404. The real symptom is an ABSENT or ERRORING panel —
+         * and forbidding two states the app never renders meant this case would
+         * have passed straight through it.
+         */
+        expectedUiState: "The order page shows a digital-code panel headed 'Your Digital Code' (or 'Your Digital Content') containing an actual code string that can be selected and copied. The panel is present at all — an absent panel, a 404 from the reveal request, or the text 'Could not retrieve your code. Please try again.' each mean the delivery never fired, which for an auto-claim listing is the defect this case exists to catch.",
         expectedData: { codeDelivered: true },
         endResult: "Reloading the order still shows the same delivered code. A code that appears once and is blank after reload was never persisted against the order.",
     },
@@ -183,7 +198,16 @@ export const authored = {
             "Look at the gallery thumbnail strip.",
         ],
         expectedBehaviour: "A live listing renders its species-specific fields — species, breed, sex, age and the jurisdiction restrictions — which no other listing type carries, and offers a cart path once those restrictions are satisfied.",
-        expectedUiState: "Heading 'Test Live Item — Golden Retriever Puppy'. A species line in the shape 'Dog (Golden Retriever) · male · 6mo'. BEFORE: the price read '₹1,500.00'; AFTER it reads 'Sign in to see price' and the digits 1,500 appear nowhere, and the 'Handling:' fee on the transport line is absent too. Delivery restrictions are stated rather than blank. The thumbnail strip carries a 'View video' entry alongside 'View image 1'. An 'Add to Cart' button is present.",
+        expectedUiState: 
+        /*
+         * Title and price taken from the seed, not from the deleted sandbox.
+         * This read 'Test Live Item — Golden Retriever Puppy' at '₹1,500.00' —
+         * a fixture from the tester-sandbox catalogue that was removed with
+         * testerSandboxRefresh. The real row is live-golden-retriever-puppy at
+         * ₹25,000. The guest-gate half of this expectation was migrated
+         * correctly; only the literals were left pointing at the old catalogue.
+         */
+        "Heading 'Golden Retriever Puppy — 6 Months, Vaccinated'. A species line in the shape 'Dog (Golden Retriever) · male · 6mo'. BEFORE: the price read '₹25,000.00'; AFTER it reads 'Sign in to see price' and the digits 25,000 appear nowhere, and the 'Handling:' fee on the transport line is absent too. Delivery restrictions are stated rather than blank. The thumbnail strip carries a 'View video' entry alongside 'View image 1'. An 'Add to Cart' button is present.",
         endResult: "Nothing persists — read-only for a guest.",
     },
     "checklist-buying-product-detail-live-item-video-mandatory": {
@@ -221,7 +245,14 @@ export const authored = {
             "Read the note beside the 'Reserve Now' button.",
         ],
         expectedBehaviour: "A pre-order shows an estimated delivery date and takes a deposit rather than the full price, which is what distinguishes it from a standard listing that happens to be out of stock.",
-        expectedUiState: "Heading 'Test Pre-order — Reserve Me!'. BEFORE: the price read '₹299.00' with a 'Reserve with ₹74.75' note; AFTER the price reads 'Sign in to see price', the deposit note is absent entirely, and neither 299 nor 74.75 appears anywhere on the page. An 'Estimated delivery:' label with an actual date beside it, not an empty value or the word 'undefined'. A 'Reserve Now' button is still present. Status badge 'In Production'.",
+        expectedUiState: 
+        /*
+         * Same sandbox leftover as the live-item case above. The real row is
+         * preorder-beyblade-x-bx-08-wave: ₹799 at preOrderDepositPercent 25, so
+         * the deposit is ₹199.75 — figures a tester can check against the seed
+         * rather than against a fixture that no longer exists.
+         */
+        "Heading 'Beyblade X BX-08 Booster — Next Wave'. BEFORE: the price read '₹799.00' with a 'Reserve with ₹199.75' note; AFTER the price reads 'Sign in to see price', the deposit note is absent entirely, and neither 799 nor 199.75 appears anywhere on the page. An 'Estimated delivery:' label with an actual date beside it, not an empty value or the word 'undefined'. A 'Reserve Now' button is still present. Status badge 'In Production'.",
         endResult: "Nothing persists — read-only for a guest.",
     },
     "checklist-buying-product-detail-prizedraw-buy-reveal": {
@@ -261,7 +292,7 @@ export const authored = {
             groupTitle: "QA Set valkyrie-lineage",
         },
         expectedBehaviour: "The group panel appears on the parent and on the child, because membership is symmetric — a child knows its groupId and the parent knows its child slugs. A panel that renders only on the parent means the children's side of the link was never written. The group is BUILT by this case rather than read from the seed: no seeded product carries groupId, isGroupParent or groupChildSlugs, so there is no fixture to read.",
-        expectedUiState: "The panel is present on both pages. Its expand control renders as a real triangle or chevron glyph, not a literal character like '▸' rendered at font-fallback size and not a missing box. Expanded, it lists 'Beyblade Burst B-01 Valkyrie' and 'Beyblade Burst B-135 Regalia Genesis' with image tiles. 'View whole group' opens a modal or drawer showing both members.",
+        expectedUiState: "The panel is present on both pages. Its expand control renders as a real triangle or chevron glyph, not a literal character like '▸' rendered at font-fallback size and not a missing box. Expanded, it lists 'Beyblade Burst B-01 Valkyrie' and 'Beyblade Burst B-59 Regalia Genesis' with image tiles. 'View whole group' opens a modal or drawer showing both members.",
         expectedData: { groupMemberCount: 2 },
         endResult: "Clear the group settings on both listings afterwards so the seeded catalogue is left as it was. A panel that survives on the parent but never appeared on the child is the failure.",
     },

package/dist/features/tester/seed-data/authored/buying__return-request.js

@@ -47,14 +47,27 @@ export const authored = {
         startPage: "/user/orders",
         steps: [
             "Sign in as rehan.sheikh@gmail.com / TempPass123!.",
-            "Open /user/orders and find a delivered order whose item was marked final sale.",
+            "Open /user/orders and open any delivered order — every seeded listing is final sale, because ProductDocument.finalSale is ABSENT on all of them and absent means true.",
             "Confirm the order or its item shows the final-sale term.",
             "Open the return control and read every reason it offers.",
-            "Select the not-received reason.",
+            /*
+             * 🛑 THE RENDERED LABEL, NOT THE ENUM VALUE OR A PARAPHRASE.
+             *
+             * These steps said "the not-received reason" and "the change-of-mind
+             * reason". The stored codes really are `not_received` and `changed_mind`
+             * — but RETURN_REASON_LABEL renders them as 'It never arrived' and
+             * 'I changed my mind', and neither paraphrase appears on screen.
+             *
+             * A tester scanning a select for "not received" does not find it. Same
+             * shape as the Decline/Reject button on buying/offers: the code value and
+             * the label are two different registers, and a step names the one the
+             * user clicks.
+             */
+            "Select 'It never arrived'.",
             "Type 'QA Return not-received — the parcel never arrived.' and submit.",
             "RELOAD the order and read its status.",
         ],
-        inputs: { reason: "not received", note: "QA Return not-received — the parcel never arrived." },
+        inputs: { reason: "It never arrived", note: "QA Return not-received — the parcel never arrived." },
         expectedBehaviour: "Final sale does not override non-delivery. It is a statement about changing your mind, not about whether the seller has to deliver — so a not-received claim must be accepted on a final-sale item, and refusing it converts a delivery failure into a term the buyer never agreed to.",
         expectedUiState: "The not-received reason is offered and accepted despite the final-sale term. After the reload the order reads as return-requested. A blanket refusal citing final sale is the failure.",
         expectedData: { accepted: true },
@@ -65,13 +78,13 @@ export const authored = {
         startPage: "/user/orders",
         steps: [
             "Sign in as rehan.sheikh@gmail.com / TempPass123!.",
-            "Open /user/orders and find a different delivered final-sale order.",
+            "Open /user/orders and open a DIFFERENT delivered order — it is final sale too, for the same reason.",
             "Open the return control and read every reason offered.",
-            "Select the change-of-mind reason.",
+            "Select 'I changed my mind'.",
             "Read what happens — whether it is refused, and what the message says.",
             "Read whether the message names FINAL SALE as the reason for the refusal.",
         ],
-        inputs: { reason: "change of mind" },
+        inputs: { reason: "I changed my mind" },
         expectedBehaviour: "Change of mind is refused on a final-sale item and the refusal NAMES final sale. A generic 'returns are not available' leaves the buyer believing the item is broken or the site is; naming the term tells them it was disclosed before purchase and points them at where they agreed to it.",
         expectedUiState: "The refusal names final sale specifically rather than reading as a generic unavailability. The reason is either not offered at all for this item, or offered and refused with that explanation.",
         expectedData: { accepted: false },