@mohasinac/appkit 4.42.0 → 4.42.2

package/dist/features/tester/seed-data/_money-flows.js

@@ -38,15 +38,24 @@ export const moneyFlowsPages = [
                 steps: [
                     STEP_SIGNIN_BUYER,
                     "Open /products/product-beyblade-burst-valkyrie.",
+                    "Confirm the signed-in account is ash@pokemonpalace.in and NOT rehan.sheikh@gmail.com. The seeded pending 780 on this product belongs to rehan, who is also the harness default buyer, so running this case as rehan trips the guard that allows only one active offer per listing and Make Offer is refused — which reads as a broken control rather than as the wrong identity.",
                     "Click 'Make Offer'.",
-                    "Enter 780 as the offer amount.",
-                    "Enter the note 'QA offer offer-to-purchase-buyer-makes-offer'.",
-                    "Click 'Submit offer'.",
+                    "Enter 815 as the offer amount. NOT 780: the seed already ships offer-yugi-burst-valkyrie-pending, a pending 780 from a different buyer on this same product, and two pending rows at the same amount on the same listing are tellable apart only by buyer name.",
+                    /*
+                     * Named `QA note buyer-makes-offer`, not `QA offer offer-to-purchase-…`.
+                     * R7 reads `offer-…` as a FIXTURE CITATION wherever it appears in a
+                     * step — including inside a name the tester is being told to type — so
+                     * the page-qualified key read as an offer id that does not exist. The
+                     * fixture reference documents this exact trap; renaming the record is
+                     * cheaper than weakening the rule.
+                     */
+                    "Enter the note 'QA note buyer-makes-offer'.",
+                    "Click the primary button. It reads 'Send offer of ₹815.00' — the label carries the amount, so it doubles as a check that what you typed reached the button. The label is interpolated, so it is not a fixed string to search for.",
                     "Open /user/offers.",
                 ],
-                expectedBehaviour: "An offer is created for 780 against product-beyblade-burst-valkyrie, owned by the signed-in buyer, and the owning seller receives an offer-received notification.",
-                expectedUiState: "The offer modal closes and a success confirmation appears. /user/offers lists a row for the product with amount ₹780 and status Pending. The page does NOT read 'No offers yet'.",
-                endResult: "After reloading /user/offers the row is still listed at ₹780 with status Pending.",
+                expectedBehaviour: "An offer is created for 815 against product-beyblade-burst-valkyrie, owned by the signed-in buyer, and the owning seller receives an offer-received notification.",
+                expectedUiState: "The offer modal closes and a success confirmation appears. /user/offers lists a row for the product with amount ₹815 and status Pending. The page does NOT read 'No offers yet'. Only THIS buyer's offers appear here, so the seeded 780 from another buyer must not be listed.",
+                endResult: "After reloading /user/offers the row is still listed at ₹815 with status Pending.",
             },
             {
                 key: "duplicate-offer-refused",
@@ -54,15 +63,15 @@ export const moneyFlowsPages = [
                 roles: ["buyer"],
                 startPage: "/products/product-beyblade-burst-valkyrie",
                 steps: [
-                    "Sign in as the buyer ash@pokemonpalace.in, holding the pending 780 offer from the previous case.",
+                    "Sign in as the buyer ash@pokemonpalace.in, holding the pending 815 offer from the previous case.",
                     "Open /products/product-beyblade-burst-valkyrie.",
                     "Click 'Make Offer'.",
                     "Enter 800 as the offer amount.",
-                    "Click 'Submit offer'.",
+                    "Click the primary button, which now reads 'Send offer of ₹800.00'.",
                 ],
-                expectedBehaviour: "The second offer is rejected. No new offer document is created; the existing 780 offer is untouched.",
+                expectedBehaviour: "The second offer is rejected. No new offer document is created; the existing 815 offer is untouched.",
                 expectedUiState: "An error states that an active offer already exists on this listing. The amount field keeps the entered 800 rather than clearing silently.",
-                endResult: "After reloading /user/offers there is still exactly ONE pending row for this product, at ₹780 — not two, and not one at ₹800.",
+                endResult: "After reloading /user/offers there is still exactly ONE pending row for this product, at ₹815 — not two, and not one at ₹800. The rule is per buyer per listing, so the other buyer's seeded 780 is unaffected and is not visible here anyway.",
             },
             {
                 key: "seller-sees-and-accepts",
@@ -72,7 +81,7 @@ export const moneyFlowsPages = [
                 steps: [
                     "Sign in as tyson@beybladearena.in / TempPass123!, who owns store-beyblade-arena.",
                     "Open /store/offers.",
-                    "Find the row for offer-yugi-burst-valkyrie-pending (product-beyblade-burst-valkyrie, offered ₹780 against a listed ₹999).",
+                    "Find the row for offer-yugi-burst-valkyrie-pending — product-beyblade-burst-valkyrie, offered ₹780 against a listed ₹999, from buyer Mock User 3. If the previous cases ran there is also an ₹815 row from a different buyer on the same product; accept the ₹780 one.",
                     "Open the row actions menu.",
                     "Click 'Accept'.",
                     "Confirm in the dialog.",
@@ -190,6 +199,7 @@ export const moneyFlowsPages = [
                 startPage: "/user/notifications",
                 steps: [
                     "Sign in as the buyer who won auction-money-flows-closing.",
+                    "🛑 WAIT FOR SETTLEMENT FIRST. The auction closes three minutes after the batch starts, but `auctionSettlement` is a scheduled function running every 15 minutes — so the win is not processed the moment the clock runs out. Nothing in this case or the two after it can be judged until it has run; an empty list before then is the schedule, not a defect.",
                     "Open the notifications bell in the header.",
                     "Find the auction-won notification.",
                     "Read its text.",
@@ -204,19 +214,19 @@ export const moneyFlowsPages = [
                 key: "won-auction-is-payable",
                 label: "🛑 A won auction can actually be paid for",
                 roles: ["buyer"],
-                startPage: "/user/orders",
+                startPage: "/cart",
                 steps: [
                     "Sign in as the buyer who won auction-money-flows-closing.",
-                    "Open /user/orders.",
-                    "Locate the won auction.",
-                    "Click its payment call to action.",
+                    "Open /cart, NOT /user/orders. A win does not create an order — settlement adds a LOCKED CART LINE, and the buyer pays through the ordinary checkout in the auction lane. An order only exists after payment.",
+                    "Locate the won auction line and read its price.",
+                    "Click through to checkout from that line.",
                     "Read the amount due.",
                     "Proceed as far as the payment method selection.",
                 ],
                 expectedBehaviour: "A reachable payment path exists and the amount due equals the winning bid of ₹16,000.",
-                expectedUiState: "The order shows ₹16,000.00 due and a payment control. Root Cause #60 is exactly this failing — settlement once wrote an order with no payment route, so 'the record exists' is NOT a pass; a payment step must be reachable.",
-                endResult: "Stop at the payment method step. After reloading /user/orders the order is still listed as awaiting payment.",
-                href: "/user/orders",
+                expectedUiState: "The cart line reads ₹16,000.00 and checkout is reachable from it, arriving at a payment method selection. Root Cause #60 is exactly this failing — settlement once wrote an ORDER with no payment route at all, so 'the record exists' is NOT a pass; a payment step must be reachable. A line that is present but leads nowhere is the same defect wearing a different shape.",
+                endResult: "Stop at the payment method step and place nothing. After reloading /cart the locked line is still there at ₹16,000.00.",
+                href: "/cart",
             },
             {
                 key: "won-auction-line-is-locked",
@@ -365,7 +375,7 @@ export const moneyFlowsPages = [
                 roles: ["buyer"],
                 startPage: "/checkout",
                 steps: [
-                    "Sign in as admin@letitrip.in / TempPass123!, open /admin/site, switch to the Shipping tab, and confirm 'PhonePe (online card/UPI) enabled' is ON.",
+                    "Sign in as admin@letitrip.in / TempPass123!, open /admin/site, switch to the Shipping tab, and confirm the toggle reading 'PhonePe (online card/UPI) enabled — disabled by default, manual payment is the default' is ON. It is OFF on a fresh install, which is what that label is telling you.",
                     STEP_SIGNIN_BUYER,
                     "Open /products/product-beyblade-burst-valkyrie (₹999) and click 'Add to cart'.",
                     "Open /checkout and complete the address step.",
@@ -443,7 +453,8 @@ export const moneyFlowsPages = [
                 roles: ["buyer"],
                 startPage: "/checkout",
                 steps: [
-                    "Sign in as admin@letitrip.in / TempPass123!, confirm PhonePe is enabled, and set Site Settings → Checkout → Out-of-stock policy to 'Skip unavailable items'.",
+                    "Sign in as admin@letitrip.in / TempPass123! and confirm PhonePe is enabled on Site Settings, Shipping tab.",
+                    "🛑 The out-of-stock policy is NOT an admin setting — there is no Checkout tab in Site Settings, and no control by the name this step used to give. It is a BUYER choice made at checkout, under the heading 'If an item goes out of stock', offering \"Ship what's available and refund the rest\" and \"Cancel my whole order\". The first is already the default, so nothing needs changing; just confirm it is selected when you reach checkout.",
                     STEP_SIGNIN_BUYER,
                     "Add product-beyblade-burst-valkyrie (₹999, stock available) and product-beyblade-original-dranzer-s (₹1,499) to the cart.",
                     "Open /checkout, complete the address step, and click 'Pay Online (PhonePe)'.",
@@ -537,13 +548,13 @@ export const moneyFlowsPages = [
                     "Sign in as admin@letitrip.in / TempPass123!.",
                     "Open /admin/bundles and start a new bundle.",
                     "Name it 'QA cross-store bundle'.",
-                    "Add product-beyblade-burst-valkyrie (store-beyblade-arena) as a member.",
-                    "Add prizedraw-beyblade-mystery-box (store-letitrip-official) as a second member — a different store.",
+                    "Add THREE members, because the form refuses fewer: product-beyblade-burst-valkyrie and product-beyblade-x-wizard-arrow (both store-beyblade-arena), plus prizedraw-beyblade-mystery-box (store-letitrip-official) — a different store.",
+                    "🛑 Two members is not enough to reach the cross-store check at all. BUNDLE_MIN_ITEMS is 3, and a two-member save is refused with 'Select at least 3 products (currently 2).' — a refusal for the wrong reason, which reads as a pass if the message is not read.",
                     "Set the bundle price to 1000 and click Save.",
                 ],
                 inputs: { bundleName: "QA cross-store bundle", bundlePrice: 1000 },
                 expectedBehaviour: "The save is refused because an order belongs to exactly one seller, and a bundle spanning two stores would produce an order containing another seller's product — with no notification, no shipping resolution and no payout for that second seller. The refusal is at save time, not at add-to-cart time, so bundles already stored keep working.",
-                expectedUiState: "An error names the two stores, or at least states that a bundle cannot span sellers. The editor stays open with the entered members intact rather than clearing.",
+                expectedUiState: "An error names how many sellers the members span, or at least states that a bundle cannot span sellers. Read the message: a minimum-members error means the cross-store guard never ran. The editor stays open with the entered members intact rather than clearing.",
                 endResult: "After reloading /admin/bundles there is no bundle named 'QA cross-store bundle'.",
                 href: "/admin/bundles",
             },

package/dist/features/tester/seed-data/authored/account-auth__profile-settings.js

@@ -60,7 +60,15 @@ export const authored = {
             bio: "Tester bio update for QA.",
         },
         expectedBehaviour: "The save succeeds and both fields are written to the user document. The header account menu picks up the new display name too, since it reads the same field.",
-        expectedUiState: "After reload, Profile Details shows the display name 'QA Profile account-auth-profile-settings-edit-profile' and the bio 'Tester bio update for QA.'. Neither field has reverted to 'Rehan Sheikh' or to an empty bio.",
+        expectedUiState: 
+        /*
+         * 'Mock User 3', not 'Rehan Sheikh'. Every seeded persona's displayName
+         * is "Mock User N" — the human-looking names live only in the email
+         * addresses — so 'Rehan Sheikh' occurs nowhere in the seed and the
+         * revert half of this assertion could never fail. A save that silently
+         * reverted would still have passed.
+         */
+        "After reload, Profile Details shows the display name 'QA Profile account-auth-profile-settings-edit-profile' and the bio 'Tester bio update for QA.'. Neither field has reverted to 'Mock User 3' (user-yugi-muto's seeded display name) or to an empty bio.",
         expectedData: {
             displayName: "QA Profile account-auth-profile-settings-edit-profile",
             bio: "Tester bio update for QA.",
@@ -112,8 +120,19 @@ export const authored = {
             "Sign in as rehan.sheikh@gmail.com / TempPass123!.",
             "Open /user/settings.",
             "Click the 'Notifications' tab.",
-            "Set the 'Email' switch to off.",
-            "Set the 'Promotions' switch to off.",
+            /*
+             * Both switches named with their SECTION, because the panel renders two
+             * independent lists — 'Notification channels' (Email / WhatsApp / SMS) and
+             * the per-type list (Offers, Promotions, Reviews, …) — and 'the Email
+             * switch' alone does not say which list to look in.
+             *
+             * The channels section is CONDITIONAL: it renders only when an admin has
+             * enabled at least one external channel in Site Settings. Its absence is
+             * therefore a precondition that was not met, not a defect — which is why
+             * the step says to record it rather than to hunt for the control.
+             */
+            "Set the 'Email' switch under 'Notification channels' to off. If that whole section is absent, record it and skip to the next step — an admin has disabled every external channel, which is a precondition, not a bug.",
+            "Set the 'Promotions' switch in the per-type list to off.",
             "Click 'Save preferences'.",
             "Reload the page.",
             "Click the 'Notifications' tab.",

package/dist/features/tester/seed-data/authored/addresses__address-filters.js

@@ -19,18 +19,23 @@ export const authored = {
         startPage: "/user/addresses",
         steps: [
             "Sign in as rehan.sheikh@gmail.com / TempPass123!.",
-            "Open /user/addresses and add a second address named 'QA Address filters-second', '7 Test Lane', Indore, Madhya Pradesh, 452010, if only one exists.",
-            "Make sure exactly one of the addresses is marked as the default.",
-            "Open the filter drawer and read every facet it offers.",
-            "Tick the Default facet and apply.",
-            "Read which addresses are listed.",
-            "Clear the filter, tick the Standing facet and apply.",
-            "Read which addresses are listed.",
+            "Open /user/addresses. No address is seeded for this buyer, so create two — one labelled 'Home' at '7 Test Lane', Indore, Madhya Pradesh, 452010, and one labelled 'Office' at '8 Test Lane', Bengaluru, Karnataka, 560001.",
+            "Back on /user/addresses, read the controls above the list: a Search input and a Label select. There is no filter drawer and no filter badge.",
+            "Type Indore in Search and read which addresses remain.",
+            "Clear Search, type zzzznope, and read the count.",
+            "Clear Search. Choose Office in the Label select and read which addresses remain.",
+            "Set the Label select back to 'All labels' and confirm both return.",
+            "Finally type Office into Search, with the Label select on All labels, and read the result.",
         ],
-        inputs: { secondAddressName: "QA Address filters-second" },
-        expectedBehaviour: "Every facet offered reads a field the address document actually has. Three facets — Address Type, Verified and Active — named fields that have never existed on this document, so each compared against an empty string and could never match a row while still counting toward the filter badge.",
-        expectedUiState: "The drawer offers only Default and Standing. Ticking Default lists only the default address; ticking Standing changes the list too. Address Type, Verified and Active are not offered at all. A facet that changes nothing while incrementing the badge is the exact failure being checked.",
-        expectedData: { facetCount: 2 },
-        endResult: "Nothing persists; filter state lives in the URL. Delete the second address afterwards.",
+        inputs: {
+            firstLabel: "Home",
+            secondLabel: "Office",
+            searchHit: "Indore",
+            searchMiss: "zzzznope",
+        },
+        expectedBehaviour: "Both controls narrow the list they sit above, and both are in-memory over the already-fetched addresses rather than a refetch. Search matches the name, street, city, state and postal code; the Label select matches the label, which Search deliberately does not cover. A control that changes nothing is the failure this case exists for.",
+        expectedUiState: "Searching Indore leaves the Indore address and hides the Bengaluru one. 'zzzznope' leaves NONE — that is the control that separates filtering from returning everything. Choosing Office in the Label select leaves only the Office address, and 'All labels' restores both.\n\n🛑 Typing Office into SEARCH returns nothing, and that is CORRECT: search covers name, street, city, state and postal code, not the label. Do not record it as broken search. The Label select does not appear at all until at least one address has a label.",
+        expectedData: { searchMissCount: 0, labelFilteredCount: 1 },
+        endResult: "Both controls are cleared. Delete the two addresses afterwards — the addresses collection is PRESERVE tier and is never wiped between runs, so anything left here accumulates forever."
     },
 };

package/dist/features/tester/seed-data/authored/addresses__postal-lookup.js

@@ -28,11 +28,12 @@ export const authored = {
             "Leave the City and State fields empty.",
             "Type 560001 in the PIN code field.",
             "Wait one second without typing anything else.",
-            "Read the City and State fields, and read the rest of the form.",
+            "Read the City field and the 'State / region' picker, then read the rest of the form.",
+            "If neither filled, open the network panel and find the api.zippopotam.us request before judging.",
         ],
-        inputs: { country: "India", pincode: "560001" },
+        inputs: { country: "India", pincode: "560001", expectedState: "Karnataka" },
         expectedBehaviour: "A complete PIN code triggers one debounced lookup that fills only City and State. Nothing else on the form moves — a lookup that also rewrites the street or the label is doing more than it was asked and the user has no way to undo it.",
-        expectedUiState: "Within about half a second City and State are filled with the values for 560001. Every other field holds exactly what it held before, including any name or street already typed. No spinner is left running and no error appears.",
+        expectedUiState: "Within about half a second City and 'State / region' are filled for 560001; the state reads Karnataka. Record the city string rather than asserting one — it is whatever Zippopotam returns for that code. Every other field holds exactly what it held before, including any name or street already typed. No spinner is left running and no error appears.",
         expectedData: { pincode: "560001" },
         endResult: "Nothing is saved unless the form is submitted. Two dead modules once carried the shape of a lookup that had been removed, which is why this looked built long before it was.",
     },
@@ -50,7 +51,7 @@ export const authored = {
         ],
         inputs: { country: "India", city: "Whitefield", pincode: "560001" },
         expectedBehaviour: "Autofill only ever lands in an EMPTY field. A lookup that corrects deliberate typing produces a bug the user cannot report — they simply watch their own text disappear and assume they mistyped.",
-        expectedUiState: "City still reads 'Whitefield' after the lookup completes. State, which was empty, has been filled. Nothing flashes the typed value away and back.",
+        expectedUiState: "City still reads 'Whitefield' after the lookup completes. 'State / region', which was empty, has been filled. Nothing flashes the typed value away and back.",
         expectedData: { city: "Whitefield" },
         endResult: "Nothing persists until the form is submitted. 'Whitefield' is chosen because it is a real Bengaluru locality that the 560001 lookup will not return — a city name the lookup agrees with would prove nothing.",
     },
@@ -63,12 +64,12 @@ export const authored = {
             "Select India as the country.",
             "Type 999999 in the PIN code field.",
             "Wait two seconds and read the whole form.",
-            "Type 'QA Address lookup-miss' as the name, '3 Test Lane' as the street, 'Indore' as the city and 'Madhya Pradesh' as the state.",
+            "Type 'QA Address lookup-miss' as the name, '3 Test Lane' as the street and 'Indore' as the city, then SELECT 'Madhya Pradesh' from the 'State / region' picker — for India it is a 36-option list, not a text box.",
             "Save the address.",
         ],
         inputs: { country: "India", pincode: "999999", city: "Indore", state: "Madhya Pradesh" },
         expectedBehaviour: "An unknown but well-formed code resolves to nothing and the form carries on. The code is still valid — six digits — so it must save; only the convenience lookup missed.",
-        expectedUiState: "No error banner, no red PIN code field, no disabled Save. City and State stay empty and editable, and the typed values are accepted. The address saves with PIN code 999999.",
+        expectedUiState: "No error banner, no red PIN code field, no disabled Save. City stays empty and editable and the 'State / region' picker stays on its placeholder, and the typed and selected values are accepted. The address saves with PIN code 999999, which matches the IN postal pattern of six digits not starting with zero.",
         expectedData: { pincode: "999999", saved: true },
         endResult: "The address exists in /user/addresses after a reload. Delete it afterwards. Treating a miss as a validation failure would block every address in the many areas the lookup does not cover.",
     },

package/dist/features/tester/seed-data/authored/addresses__postal-validation.js

@@ -21,7 +21,7 @@ export const authored = {
             "Sign in as rehan.sheikh@gmail.com / TempPass123!.",
             "Open /user/addresses/new.",
             "Select India as the country.",
-            "Type 'QA Address letters-rejected' as the name, '4 Test Lane' as the street, 'Indore' as the city and 'Madhya Pradesh' as the state.",
+            "Type 'QA Address letters-rejected' as the name, '4 Test Lane' as the street and 'Indore' as the city, then SELECT 'Madhya Pradesh' from the 'State / region' picker.",
             "Type abcdef in the PIN code field.",
             "Click Save.",
             "Read where the error appears.",
@@ -40,7 +40,7 @@ export const authored = {
             "Open /user/addresses/new.",
             "Select Canada as the country.",
             "Read the label on the postal code field.",
-            "Type K1A 0B1 in that field and fill the rest of the form with 'QA Address country-rule', '5 Test Lane', 'Ottawa' and 'Ontario'.",
+            "Type K1A 0B1 in that field, then fill the name 'QA Address country-rule', the street '5 Test Lane' and the city 'Ottawa', and SELECT 'Ontario' from the 'State / region' picker — Canada has one too.",
             "Click Save.",
             "Open the address for editing, switch the country to India, and type K1A 0B1 in the PIN code field.",
             "Type 560001 instead and read the field.",
@@ -63,8 +63,14 @@ export const authored = {
             "Click Save.",
             "Open the address for editing, replace the postal code with ABC-1234, and save again.",
         ],
-        inputs: { country: "United Arab Emirates", firstCode: "00000", secondCode: "ABC-1234" },
-        expectedBehaviour: "For a country with no known format any plausible 3-to-12 character code is accepted. A postal rule exists to catch a typo, never to refuse a real address whose pattern we simply do not have.",
+        inputs: {
+            country: "United Arab Emirates",
+            firstCode: "00000",
+            secondCode: "ABC-1234",
+            postalMin: 3,
+            postalMax: 12,
+        },
+        expectedBehaviour: "For a country with no known format any code of 3 to 12 characters is accepted, which is the POSTAL_MIN and POSTAL_MAX fallback in the one shared validator. A postal rule exists to catch a typo, never to refuse a real address whose pattern we simply do not have — and an EMPTY code is still refused, because a blank is not a postal code in any country.",
         expectedUiState: "Both codes save without an error. The field is not marked red and Save is never disabled. What must not happen is India's six-digit rule being applied by default to a country it does not describe.",
         expectedData: { bothCodesAccepted: true },
         endResult: "The address holds ABC-1234 after a reload. Delete it afterwards.",

package/dist/features/tester/seed-data/authored/addresses__state-picker.js

@@ -21,15 +21,15 @@ export const authored = {
             "Sign in as rehan.sheikh@gmail.com / TempPass123!.",
             "Open /user/addresses/new.",
             "Select India as the country.",
-            "Click the State field and try to type free text into it.",
+            "Click the 'State / region' field and try to type free text into it.",
             "Type karn in the picker's search box and read the options offered.",
             "Select Karnataka.",
             "Change the country to United Arab Emirates.",
-            "Click the State field again and try to type free text.",
+            "Click 'State / region' again and try to type free text.",
         ],
         inputs: { country: "India", stateSearch: "karn", state: "Karnataka" },
         expectedBehaviour: "Where a country's regions are enumerated, State is a searchable picker; where they are not, it is a plain text box. The picker is what stops one column holding 'Karnataka', 'karnataka' and 'KA' depending on which screen created the row — which is what happened while this form and the seller drawer wrote free text into the same field the admin editor filled from a 36-option list.",
-        expectedUiState: "With India selected, State cannot be typed into freely and searching 'karn' narrows a list of India's 36 states and union territories to Karnataka. With United Arab Emirates selected, State becomes an ordinary text input that accepts anything.",
+        expectedUiState: "With India selected, 'State / region' cannot be typed into freely and searching 'karn' narrows a list of India's 36 states and union territories to Karnataka. With United Arab Emirates selected the same label becomes an ordinary text input that accepts anything, because the UAE has no subdivisions in the registry.",
         expectedData: { indiaStateOptionCount: 36 },
         endResult: "Nothing persists unless the form is submitted. A picker offering 28 or 29 options is missing the union territories.",
     },
@@ -40,15 +40,20 @@ export const authored = {
             "Sign in as rehan.sheikh@gmail.com / TempPass123!.",
             "Open /user/addresses/new.",
             "Select India as the country.",
-            "Select Karnataka in the State picker.",
+            "Select Karnataka in the 'State / region' picker.",
             "Change the country to Canada.",
-            "Read the State field.",
+            "Read the 'State / region' field, and count the options it now offers.",
             "Change the country back to India and read it again.",
         ],
-        inputs: { firstCountry: "India", state: "Karnataka", secondCountry: "Canada" },
+        inputs: {
+            firstCountry: "India",
+            state: "Karnataka",
+            secondCountry: "Canada",
+            canadaOptionCount: 13,
+        },
         expectedBehaviour: "Changing the country clears the state, because a state only means something inside the country it belongs to. An address carrying Karnataka under Canada is a row nothing can group, rate for shipping, or tax correctly.",
-        expectedUiState: "After switching to Canada the State field is empty and offers Canadian provinces. Switching back to India leaves it empty too — it does not restore 'Karnataka' from before, which would reintroduce the mismatch the clear exists to prevent.",
-        expectedData: { stateAfterCountryChange: "" },
+        expectedUiState: "After switching to Canada 'State / region' is empty and offers 13 Canadian options, its 10 provinces and 3 territories — an emptied field still listing India's 36 would mean the clear ran and the option source did not. Switching back to India leaves it empty too: the clear fires on every country change and does not restore 'Karnataka', which would reintroduce the mismatch it exists to prevent.",
+        expectedData: { stateAfterCountryChange: "", canadaOptionCount: 13 },
         endResult: "Nothing persists unless the form is submitted. A retained 'Karnataka' under Canada is the failure.",
     },
 };

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

@@ -13,27 +13,65 @@
  * @tag consumers:seed-data/authored/index.ts
  * @tag sideEffects:none
  */
+/*
+ * Verified against the drawer on 2026-09-29, and every assertion the case
+ * makes is correct: the trigger reads 'Request Unban' and renders only when
+ * the address is banned; the drawer's field is 'Reason for unban request';
+ * its submit is 'Submit request' and is DELIBERATELY not disabled on an empty
+ * note, with a source comment saying why; and addressUnbanRequestSchema
+ * carries a .min(20) whose message is
+ *
+ *   'Explain what happened — at least 20 characters. This is all the reviewer sees.'
+ *
+ * So the 20 the case names is real, and so is the error text.
+ *
+ * 🛑 WHAT IS MISSING IS THE PRECONDITION. This buyer has no addresses at all,
+ * and no seeded address is banned, so 'find an address showing a banned state'
+ * finds nothing. Worse, there is no UI path to ban one: ban-address is a row
+ * action on the Banned Addresses queue, which is fed only by
+ * GET /api/admin/addresses?banStatus=..., and its chips are banned,
+ * unban_requested and suspicious. The All chip sends no banStatus and the
+ * route then returns an empty list — so that queue can only act on rows
+ * already in it, and nothing in the product puts a clean address there.
+ *
+ * The one real producer is hardBanCascade, which bans every address belonging
+ * to a hard-banned user. But /unban reverses exactly that via
+ * unbanAutoForOwner, so lifting the user's ban clears the address too. The two
+ * states this case needs together — an ACTIVE buyer with a BANNED address —
+ * cannot be reached from the UI at all.
+ *
+ * So the case attempts the setup, RECORDS the gap, and runs the real
+ * assertions only if a banned address does exist. Recorded in OUTOFSCOPE.
+*/
 export const authored = {
     "checklist-addresses-unban-request-empty-note-says-why": {
         roles: ["buyer"],
         startPage: "/user/addresses",
         steps: [
-            "Sign in as rehan.sheikh@gmail.com / TempPass123!.",
-            "Open /user/addresses and find an address showing a banned state.",
-            "Click 'Request Unban'.",
-            "Leave the note box completely empty and click Submit.",
-            "Read where any message appears.",
-            "Type 'Too short' in the note box and click Submit.",
-            "Type 'This address was banned in error; it is my registered home address.' and click Submit.",
+            "Sign in as admin@letitrip.in / TempPass123! and open the Banned Addresses queue.",
+            "Select the All chip and read how many rows are listed, then try the Banned, Unban Requested and Suspicious chips in turn.",
+            "Record whether ANY route in the product lets an admin ban a single address on an otherwise-active account — if none does, this case cannot be set up, and that is the finding.",
+            "If a banned address belonging to rehan.sheikh@gmail.com does exist, continue. Otherwise stop here and answer no, quoting what each chip returned.",
+            "Sign in as rehan.sheikh@gmail.com / TempPass123! and open /user/addresses.",
+            "Find the banned address and click 'Request Unban'.",
+            "Leave 'Reason for unban request' completely empty and click 'Submit request'. The button must be clickable, not greyed out.",
+            "Read where the message appears.",
+            "Type 'Too short' and click 'Submit request' again.",
+            "Type 'This address was banned in error; it is my registered home address.' and submit.",
         ],
         inputs: {
             shortNote: "Too short",
             validNote: "This address was banned in error; it is my registered home address.",
             minimumLength: 20,
+            trigger: "Request Unban",
+            field: "Reason for unban request",
+            submit: "Submit request",
         },
-        expectedBehaviour: "Submitting with an empty or too-short note fails loudly on the field and names the 20-character minimum. The note is the ENTIRE case a reviewer reads, so a request without one is not a request — but a disabled button with a bare return in its handler tells the user nothing about why.",
-        expectedUiState: "The Submit button is enabled even when the box is empty. Pressing it puts an error on the note field naming the minimum length. 'Too short' produces the same error. The full sentence is accepted and a confirmation appears.",
-        expectedData: { minimumNoteLength: 20 },
-        endResult: "One unban request exists, carrying the full note. A silently disabled button that does nothing when pressed is the failure — the user cannot tell it from a broken page.",
+        expectedBehaviour: "Submitting with an empty or too-short note fails loudly ON THE FIELD and names the 20-character minimum. The note is the entire case a reviewer reads, so a request without one is not a request — but a greyed-out button with a bare return in its handler tells the user nothing about why, which is what this replaced.",
+        expectedUiState: "The submit button is enabled even with the box empty. Pressing it puts an error on the note field naming the minimum length; the schema message reads 'Explain what happened — at least 20 characters. This is all the reviewer sees.' 'Too short' produces the same error. The full sentence is accepted and a confirmation appears.\n\n🛑 If no banned address exists, answer NO for the precondition rather than null: there is no UI path to ban one, which is a product gap and not a missing test channel.",
+        expectedData: { minimumNoteLength: 20, submitEnabledWhenEmpty: true },
+        endResult: "If the request was submitted, the address reads as unban-requested and carries the full note. A silently disabled button that does nothing when pressed is the failure — the user cannot tell it from a broken page.",
+        needsReview: true,
+        reviewNote: "The assertions are verified correct against the drawer and its schema. What is unsettled is whether an admin should be able to ban a single address on an otherwise-active account at all; today they cannot, so this case has no reachable setup.",
     },
 };

package/dist/features/tester/seed-data/authored/admin__admin-detail-round-trips.js

@@ -31,6 +31,8 @@ export const authored = {
             "Press Save.",
             "Reload the page and open the same coupon again.",
             "Read the discount value, the usage limits and the validity dates.",
+            "Restore the description by deleting the word you appended, then save again. coupons is SEED_OWNED so a reseed would fix it either way, but a run does not reseed — three earlier runs left this text reading 'roundtrip roundtrip roundtrip', and a later case reading this description would be reading what this one wrote.",
+            "Note the editor keeps Limits and Validity in COLLAPSIBLE sections. After the reload they are closed, so their fields are absent from the page rather than empty — read those four numbers off the coupon card in the list, which renders them directly, or expand the sections again before judging.",
         ],
         inputs: { couponCode: "ARENA25", descriptionSuffix: "roundtrip" },
         expectedBehaviour: "Editing one field writes that field and leaves the rest as they were. A handler that merges a partial validity or restrictions object wholesale wipes whatever the caller did not resend — and a handler that never calls the repository at all returns a 200 that echoes the submission back, which is indistinguishable from a save.",
@@ -48,7 +50,8 @@ export const authored = {
             "Append the sentence: Edited during a round-trip check.",
             "Press Save.",
             "Reload and reopen the same FAQ.",
-            "Open the public /faqs page and find the same question.",
+            "Open the public /faqs page and find the same question. Answers are collapsed accordions — click the question to expand it before reading.",
+            "Remove the sentence you appended and save again. Append it with the KEYBOARD at the caret, never by filling the field: this is a contenteditable holding real HTML, and a fill replaces the whole answer with plain text, destroying five bold runs on a buyer-facing page.",
         ],
         inputs: { faqSlug: "coupons-and-discounts", appended: "Edited during a round-trip check." },
         expectedBehaviour: "The answer is a structured value, not a bare string. A create path that wraps it and an update path that writes it flat produce a document every reader expects to be an object and finds is a string — which renders as nothing, or as raw markup, on the public page.",
@@ -61,12 +64,13 @@ export const authored = {
         startPage: "/admin/categories",
         steps: [
             "Sign in as admin@letitrip.in / TempPass123!.",
-            "Open /categories/x-starters as a visitor in a second tab and write down its product count.",
-            "In the first tab open /admin/categories and find X Starters.",
+            "Open /categories/category-x-starters as a visitor in a second tab and write down its product count. Note the FULL id — /categories/x-starters serves 'Category Not Found'; every category id carries the category- prefix.",
+            "In the first tab open /admin/categories and find Starter Sets — that is the display name of category-x-starters; there is no category called 'X Starters'.",
             "Write down its parent and how many children it has.",
             "Open its Edit action, change ONLY its description, and press Save.",
             "Reload the admin list and reopen it.",
             "Reload the public category page in the second tab.",
+            "Restore the description by removing the word you appended, then save again. Three of the cases on this page append a marker and this one accumulated 'roundtrip' from an earlier run — categories is SEED_OWNED, but a run does not reseed.",
         ],
         inputs: { categorySlug: "x-starters" },
         expectedBehaviour: "A rename or a description edit touches that field alone. The hierarchy fields — parent, children, ancestors, tier — are derived and must never be rewritten from form state, and the product count is derived from a trigger rather than typed.",
@@ -82,11 +86,11 @@ export const authored = {
             "Open /admin/users and find the account rehan.sheikh@gmail.com.",
             "Open its Edit action, turn BOTH tester flags on, and save — no seeded account carries them, so the case has to set up the field it is about.",
             "Reopen the same account and confirm both flags read as on.",
-            "Change ONLY its bio — append the word roundtrip.",
+            "WRITE DOWN the bio exactly as it stands, then change ONLY the bio — append the word roundtrip.",
             "Press Save.",
             "Reload the list and reopen the same account.",
             "Read the tester flags again.",
-            "Turn both tester flags back off and save.",
+            "Turn both tester flags back off AND restore the bio to what you wrote down, then save. users is PRESERVE-tier — never wiped, never reseeded — so an appended word left behind is permanent, and after a few runs the bio reads roundtrip roundtrip roundtrip.",
         ],
         inputs: { account: "rehan.sheikh@gmail.com", bioSuffix: "roundtrip" },
         expectedBehaviour: "An editor seeded from a LIST row can only send back what that row carried. If the list serializer omits a field the update schema accepts, the editor state defaults to false and the save rewrites it — so editing any other field silently strips it. That is why the check is on a field the form did not touch.",
@@ -101,7 +105,7 @@ export const authored = {
             "Sign in as admin@letitrip.in / TempPass123!.",
             "Open /admin/stores and find Beyblade Arena.",
             "Note whether it is marked Verified and whether it is Featured.",
-            "Open its Edit action and change ONLY the admin notes — append the word roundtrip.",
+            "Note the admin notes as they stand, then open its Edit action and change ONLY the admin notes — append the word roundtrip. Restore them before you finish. Unlike the user bio in the sibling case, stores is SEED_OWNED and a reseed would put this back either way — so this is hygiene rather than damage control, and it keeps a later case from reading notes this one wrote.",
             "Press Save.",
             "Reload the list.",
             "Read the Verified and Featured markers again.",