@mohasinac/appkit 4.42.1 → 4.42.3

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

@@ -6,7 +6,7 @@
  * what makes this one page rather than two.
  *
  * `/store/products/new` does NOT open the sectioned form. SellerProductShell.tsx
- * :1339 picks `formMode = "quick"` whenever mode is create and listingType is
+ * :1379 picks `formMode = "quick"` whenever mode is create and listingType is
  * standard, so the default is QuickProductForm — six fields: title*, category*,
  * price*, mainImage*, description, stockQuantity. The sectioned form is behind
  * "Show all fields (advanced)".
@@ -67,7 +67,7 @@ export const authored = {
             "Upload public/test-media/sample-image.png as the Product Image.",
             "Enter Description 'A short-form listing created with only the required fields present.'",
             "Click Publish and read what happens.",
-            "Open the product's public page and read the title, price and image.",
+            "Open the product's public page at /products/{its slug} and read the title, price and image.",
         ],
         inputs: {
             title: "Minimum Details Probe",
@@ -122,7 +122,7 @@ export const authored = {
             SIGN_IN_SELLER,
             "Open /store/products/new and click 'Show all fields (advanced)'.",
             "Open the Basic section and read every option in the Condition dropdown, writing them all down.",
-            "Fill Title 'Condition Probe', Description 'Checking that every condition the form offers can actually be saved.', Category 'Beyblade Burst', Price 499 and a Main Image.",
+            "Fill Product Name 'Condition Probe', Description 'Checking that every condition the form offers can actually be saved.', Category 'Beyblade Burst', Price 499 and a Product Image. The six labels are exactly: Product Name, Category, Price (₹), Stock Quantity, Description, Product Image — there is no field labelled Title or Main Image.",
             "Select Condition 'Like New' and click Publish.",
             "Read the result — inline error, toast, or success.",
             "Repeat with 'Good', then with 'Fair', then with 'New', reading the result each time.",

package/dist/features/tester/seed-data/authored/selling__sectionised-forms.js

@@ -43,6 +43,7 @@ export const authored = {
         steps: [
             "Sign in as tyson@beybladearena.in / TempPass123!.",
             "Open /store/products/new and read the page before typing — note whether any errors are listed.",
+            "Click 'Show all fields (advanced)' first. 🛑 /store/products/new opens the QUICK form for a standard create — six flat fields, NO sections at all — so every section, chevron and error-summary step below needs the advanced form, which is the sectionised one this page is about.",
             "Leave required fields empty in two DIFFERENT sections.",
             "Collapse both of those sections.",
             "Attempt to publish.",
@@ -58,6 +59,7 @@ export const authored = {
         steps: [
             "Sign in as tyson@beybladearena.in / TempPass123!.",
             "Open /store/products/new and look at every section header.",
+            "Click 'Show all fields (advanced)' first. 🛑 /store/products/new opens the QUICK form for a standard create — six flat fields, NO sections at all — so every section, chevron and error-summary step below needs the advanced form, which is the sectionised one this page is about.",
             "Find any section that is always open because it is required.",
             "Look at whether it still shows an expand chevron.",
             "Click that chevron and read what happens.",
@@ -73,6 +75,7 @@ export const authored = {
         steps: [
             "Sign in as tyson@beybladearena.in / TempPass123!.",
             "Open /store/products/new and expand a section containing a picker.",
+            "Click 'Show all fields (advanced)' first. 🛑 /store/products/new opens the QUICK form for a standard create — six flat fields, NO sections at all — so every section, chevron and error-summary step below needs the advanced form, which is the sectionised one this page is about.",
             "Open that picker and read whether its full option list is visible.",
             "Scroll while it is open and check it stays anchored to its field.",
             "Open a picker in the LAST section of the form, near the bottom of the page.",
@@ -90,9 +93,28 @@ export const authored = {
         steps: [
             "Sign in as tyson@beybladearena.in / TempPass123!.",
             "Open /store/products/new and leave a required field empty in a section far down the form.",
+            "Click 'Show all fields (advanced)' first. 🛑 /store/products/new opens the QUICK form for a standard create — six flat fields, NO sections at all — so every section, chevron and error-summary step below needs the advanced form, which is the sectionised one this page is about.",
             "Collapse that section and attempt to publish.",
             "Click the error for that field in the summary.",
             "Read where the page has scrolled to and whether the field is visible.",
+            /*
+             * 🛑 EXPECT THIS TO FAIL TODAY, AND RECORD IT AS A FAILURE.
+             *
+             * Measured 2026-09-29: FormErrorList's entire click handler is
+             * `onClick={() => ctx.goToStep(stepIndex!)}`. There is no focus() call,
+             * no scrollIntoView, and no element lookup — so it opens the owning
+             * section and stops, which is exactly what this case calls the failure.
+             *
+             * Kept as written rather than softened to match. The rationale holds: a
+             * section can carry a dozen fields, and an error summary that drops the
+             * user at the heading has told them something is wrong without showing
+             * them what. Softening it to "lands on the section" would convert a real
+             * UX gap into a passing case.
+             *
+             * So a tester who lands on the heading records a FAILURE with a
+             * screenshot — not "could not test", and not a lenient pass because the
+             * section did open.
+             */
             "Check whether the field is focused and marked, not merely on screen.",
         ],
         expectedBehaviour: "Clicking an error lands ON the field — section expanded, field scrolled into view, focused and marked. Landing on the section heading leaves the user hunting through a section that may hold a dozen fields.",
@@ -105,6 +127,7 @@ export const authored = {
         steps: [
             "Sign in as tyson@beybladearena.in / TempPass123!.",
             "Open /store/products/new and expand every section.",
+            "Click 'Show all fields (advanced)' first. 🛑 /store/products/new opens the QUICK form for a standard create — six flat fields, NO sections at all — so every section, chevron and error-summary step below needs the advanced form, which is the sectionised one this page is about.",
             "Type a long paragraph into the description field at normal speed.",
             "Watch for characters lagging behind the keystrokes.",
             "Attempt a publish so validation is running live, then keep typing into another field.",
@@ -119,7 +142,7 @@ export const authored = {
         startPage: "/store/products/new",
         steps: [
             "Sign in as tyson@beybladearena.in / TempPass123!.",
-            "Resize the browser window to 390 pixels wide and open /store/products/new.",
+            "Resize the browser window to 390 pixels wide, open /store/products/new, and click 'Show all fields (advanced)' — the quick form has no sections and therefore no section-scoped error sheet, which is what this case reads.",
             "Read the action bar at the bottom and every control in it.",
             "Type into a field so the form becomes dirty and read the bar again.",
             "Attempt a publish with fields missing and read what the bar shows.",
@@ -137,6 +160,7 @@ export const authored = {
         steps: [
             "Sign in as tyson@beybladearena.in / TempPass123!.",
             "Open /store/products/new and find a control that reveals conditional fields — a listing type or a shipping choice.",
+            "Click 'Show all fields (advanced)' first. 🛑 /store/products/new opens the QUICK form for a standard create — six flat fields, NO sections at all — so every section, chevron and error-summary step below needs the advanced form, which is the sectionised one this page is about.",
             "Set it so the conditional fields appear and fill them in, noting each value.",
             "Change the controlling field so those conditionals are hidden.",
             "Change it back so they reappear.",

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

@@ -87,14 +87,35 @@ export const authored = {
         startPage: "/store/payouts",
         steps: [
             "Sign in as tyson@beybladearena.in / TempPass123!.",
-            "Open /store/payouts and find the payout reminder toggle.",
-            "Read its current state.",
-            "Turn it OFF and save if a save is required.",
-            "RELOAD the page and read the toggle's state.",
-            "Turn it back on, save, and reload to confirm.",
+            /*
+             * 🛑 THE TOGGLE IS PER-PAYOUT, LABELLED 'Remind me', AND SAVES ITSELF.
+             *
+             * This said "open /store/payouts and find the payout reminder toggle",
+             * then "turn it OFF and save if a save is required", then back on. Three
+             * things were wrong and each one alone would strand a tester:
+             *
+             *  - it is not on the page. It lives inside a SELECTED payout's detail
+             *    panel, so a payout has to be opened first.
+             *  - it is labelled 'Remind me', with the helper text "Flag this payout
+             *    for a personal follow-up". Nothing reads "reminder".
+             *  - there is no save. handleToggleReminder PATCHes immediately and
+             *    toasts 'Reminder set.' or 'Reminder cleared.', so waiting for a save
+             *    button means never completing the step.
+             *
+             * And the direction was backwards: no seeded payout sets
+             * `sellerReminderFlag`, and the control reads
+             * `checked={Boolean(payout.sellerReminderFlag)}` — so it starts OFF.
+             * "Turn it OFF" first was a no-op that would have made the reload check
+             * pass trivially.
+             */
+            "Open /store/payouts and open any payout to show its detail panel.",
+            "Find the 'Remind me' toggle in that panel and read its current state — it starts OFF, because no seeded payout carries the flag.",
+            "Turn it ON. It saves immediately; look for the toast reading 'Reminder set.' rather than a save button.",
+            "RELOAD the page, reopen the SAME payout, and read the toggle's state.",
+            "Turn it back off, confirming the toast reads 'Reminder cleared.', and reload once more to confirm.",
         ],
         expectedBehaviour: "The preference persists server-side. Off is the direction worth testing when the default is on: a toggle that never saves reads back as its default and passes a test that only ever turns it on.",
-        expectedUiState: "After the reload the toggle is still off. A toggle that has reverted to on is the failure, and the save will have reported success.",
+        expectedUiState: "After the reload the reopened payout's 'Remind me' toggle is still ON. A toggle that has reverted to off is the failure — and the PATCH will have reported success and toasted 'Reminder set.', which is exactly what makes it invisible without the reload.",
         expectedData: { reminderEnabled: false },
         endResult: "The toggle is back on by the final step, so payout reminders are not left suppressed.",
     },

package/dist/features/tester/seed-data/authored/selling__seller-bids-bundles-filters.js

@@ -73,16 +73,34 @@ export const authored = {
         startPage: "/store/bundles",
         steps: [
             "Sign in as tyson@beybladearena.in / TempPass123!.",
+            /*
+             * 🛑 THE SELLER OWNS NO SEEDED BUNDLE, SO THE CASE HAS TO MAKE ONE.
+             *
+             * /store/bundles filters on `b.createdByStoreId === store.id`, and
+             * `createdByStoreId` appears ZERO times across every seed file — all 11
+             * seeded bundles are `createdByType: "admin"`, authored by
+             * user-admin-letitrip. They are platform bundles and correctly invisible
+             * here.
+             *
+             * So the page is empty for every seller, and a case that opens it and
+             * "notes the total row count" could only ever be answered "could not
+             * test". Creating one first makes the case self-sufficient, and the
+             * created row is disposable: `categories` is SEED_OWNED, so the next
+             * lifecycle wipe removes it.
+             */
+            "Open /store/bundles/new and create a bundle named 'QA Bundle active-filter' with at least two of this store's products as members, leaving it Active.",
+            "Create a second one named 'QA Bundle inactive-probe' and set it Inactive.",
             "Open the store's bundles page and note the total row count.",
             "Read the active filter's options.",
             "Select active and read the rows and their states.",
             "Select inactive and read the rows and their states.",
             "Confirm the two counts add up to the unfiltered total.",
             "Open one bundle and check its member list is populated rather than reading zero items.",
+            "Delete both QA bundles afterwards.",
         ],
         expectedBehaviour: "The two filter states partition the list, so their counts sum to the total. The member check matters separately: a bundle's members are mirrored onto the bundle for index-friendly reads, and a reader trusting only that mirror shows an empty bundle whenever a write path forgot to update it.",
         expectedUiState: "Active and inactive each return their own rows and the counts sum to the unfiltered total. The opened bundle lists its members with titles and images rather than reading '0 items'.",
         expectedData: { partitionSumsToTotal: true },
-        endResult: "Read-only; nothing persists beyond the URL.",
+        endResult: "Both QA bundles are deleted, leaving the store's bundle list as it was — empty, since no seeded bundle belongs to a store. If the delete fails, say so: `categories` is SEED_OWNED and the next lifecycle wipe clears them anyway, so a leftover is untidy rather than harmful.",
     },
 };

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

@@ -1,16 +1,34 @@
 /*
  * WHY: Authored six-part procedures for the selling/seller-catalog-org page.
- * WHAT: 7 case(s), keyed by full checklist id.
+ * WHAT: 8 case(s), keyed by full checklist id.
  *
  * Written by hand, case by case, against the label each one states. There is no
  * generator: the authoring scripts were deleted once it was clear they were
  * scaffolding around work that is simply writing.
  *
+ * 🛑 THREE DIFFERENT THINGS HERE ARE ALL CALLED "CATEGORY", and conflating them is
+ * how the first version of this file described the wrong object twice:
+ *
+ *   /store/categories            STOREFRONT shelves. Own collection
+ *                                (`storeCategoriesRepository`), scoped to one
+ *                                store, and the field is **Label**, not Name.
+ *   /store/sublisting-categories the seller's sub-groupings, with DERIVED page
+ *                                metadata that must be recomputed on rename.
+ *   the product form's picker    the GLOBAL taxonomy. Its inline-create posts to
+ *                                the admin categories endpoint — which admits
+ *                                sellers deliberately (ROLES_STORE_WRITE, with a
+ *                                comment saying it is for this picker).
+ *
  * 🛑 A PRODUCT CARRIES ITS FULL ANCESTOR CHAIN so a parent category page can match
- * on its own id alone. Nothing on the WRITE side derives that chain yet — the
- * convention is maintained by hand in the seed — so a product filed through a form
- * against a deep category gets a single-slug array and is invisible on every
- * ancestor page. The first category case checks exactly that.
+ * on its own id alone — and since 2026-09-14 that chain IS derived on write, by
+ * `ProductRepository.deriveTaxonomy()`, from both `create` and `update`. This file
+ * used to say the opposite and instruct the tester to REPORT a one-element chain as
+ * a known gap; that is now a false bug report. `deep-category-chain-derived` is the
+ * case that can actually fail if the derivation regresses.
+ *
+ * The inline-create form sends only name/slug/description/isActive — there is **no
+ * parent field** — so a category created that way is always a root and correctly
+ * shows exactly one link. One link there is arithmetic, not a defect.
  *
  * @tag domain:tester
  * @tag layer:seed
@@ -25,19 +43,19 @@ export const authored = {
         startPage: "/store/categories",
         steps: [
             "Sign in as tyson@beybladearena.in / TempPass123!.",
-            "Open the store's categories page and read the list.",
-            "Create one named 'QA Category catalog-org' and save.",
-            "RELOAD and confirm it is listed.",
-            "Rename it to 'QA Category catalog-org renamed' and save, then RELOAD and read the name.",
+            "Open the store's categories page and read the list. These are STOREFRONT shelves scoped to this store — not the global taxonomy the product form's category picker offers.",
+            "Create one and save. The field is labelled 'Label', not 'Name' — type 'QA Shelf catalog-org' into it. Leave the slug blank, it is optional on create.",
+            "RELOAD and confirm it is listed under that label.",
+            "Change the Label to 'QA Shelf catalog-org renamed' WITHOUT touching the slug field, save, then RELOAD and read both the label and the slug.",
             "Delete it and RELOAD to confirm it is gone.",
         ],
         inputs: {
-            name: "QA Category catalog-org",
-            renamed: "QA Category catalog-org renamed",
+            label: "QA Shelf catalog-org",
+            renamed: "QA Shelf catalog-org renamed",
         },
-        expectedBehaviour: "Create, rename and delete all persist. The rename is the one worth watching: a create handler that derives a slug from the name while the update handler leaves the slug alone is the deliberate convention here, so the NAME must change while the URL stays stable.",
-        expectedUiState: "Each operation survives its reload. After the rename the new name is shown; the category's own URL is unchanged, which is correct rather than a bug — an auto-recomputed slug would break every existing link.",
-        endResult: "The category is deleted by the final step.",
+        expectedBehaviour: "Create, rename and delete all persist against this store. The rename is the one worth watching: slug is its own editable field here rather than something derived from the label, so editing the label alone must leave the slug exactly as it was — a slug that silently re-derives would break every link to the shelf.",
+        expectedUiState: "Each operation survives its reload. After the rename the new label is shown and the slug is byte-identical to what it was before. A validation error naming a field the form does not show is also a failure — the create schema requires only the label.",
+        endResult: "The shelf is deleted by the final step. Nothing in the global category taxonomy is touched by this case.",
     },
     "checklist-selling-seller-catalog-org-seller-sublisting-categories-crud": {
         roles: ["seller"],
@@ -118,7 +136,7 @@ export const authored = {
             "Type 'QA Product inline-category' as the title, select that category, type 400 as the price, and publish.",
             "Open the product's public page and read its category links below the title.",
             "Count how many category links are shown.",
-            "Click the one naming QA Category inline-create.",
+            "Click the one naming QA Category inline-create and confirm the product is listed on the page it opens.",
             "Delete the product and the category afterwards.",
         ],
         inputs: {
@@ -126,10 +144,33 @@ export const authored = {
             title: "QA Product inline-category",
             price: 400,
         },
-        expectedBehaviour: "The category persists and the product is filed under it. The product's category list is supposed to be the full ancestor chain, and nothing on the write side derives that chain today — so a product created through this form gets a single slug and is unreachable from every ancestor page.",
-        expectedUiState: "The category is offered after a reload and the product's public page links it. Record how many category links the product shows: ONE, where the chosen category has ancestors, is the known gap this case is here to make visible rather than a surprise.",
+        expectedBehaviour: "The category persists across a reload and the product is genuinely filed under it — reachable from the category's own page, not merely named on the product.",
+        expectedUiState: "The category is offered after a reload and the product's public page links it. EXACTLY ONE link is correct here and is not a defect: the inline-create form sends only name, slug, description and active — it has no parent field — so the category it makes is a root with no ancestors to list. A product under a DEEP category is a different assertion and has its own case.",
         expectedData: { categoryLinksShown: 1 },
-        endResult: "The product and the category are deleted by the final step. If only one link appears, report it — the ancestor chain being seed-only is a documented outstanding follow-up.",
+        endResult: "The product and the category are deleted by the final step. Do not report the single link as a missing ancestor chain — that was this case's own stale claim and it is wrong.",
+    },
+    "checklist-selling-seller-catalog-org-deep-category-chain-derived": {
+        roles: ["seller", "guest"],
+        startPage: "/store/products/new",
+        steps: [
+            "Sign in as tyson@beybladearena.in / TempPass123!.",
+            "Open /store/products/new and search the category picker for 'Heavy Metal System' — a seeded tier-3 category whose ancestors are Original Tops, Beyblade Original and Spinning Tops.",
+            "Select it, type 'QA Product deep-chain' as the title and 500 as the price, and publish.",
+            "Open the product's public page and count the category links below the title.",
+            "Read the names in order and compare them against the four expected.",
+            "Open /categories/category-spinning-tops — the ROOT, three levels above the category chosen — and look for this product.",
+            "Delete the product afterwards.",
+        ],
+        inputs: {
+            categoryName: "Heavy Metal System",
+            categoryId: "category-original-hms",
+            title: "QA Product deep-chain",
+            price: 500,
+        },
+        expectedBehaviour: "A product filed against a deep category is written with its FULL ancestor chain, so every ancestor page matches on its own id alone. The repository derives this on create and update; a form payload cannot supply it, because the create schema strips any categorySlugs it is sent. This is the assertion that fails if that derivation regresses — and the failure is silent, because the product's own page looks completely normal with one link.",
+        expectedUiState: "FOUR category links: Heavy Metal System, Original Tops, Beyblade Original, Spinning Tops. The product appears on the root Spinning Tops page. One link, or a root page that does not list it, is the failure — and note that every SEEDED product shows four, so a new listing showing one is a write-path defect rather than a display one.",
+        expectedData: { categoryLinksShown: 4, foundOnRootCategoryPage: true },
+        endResult: "The product is deleted by the final step. Check the root page before deleting — that is the half a tester is most likely to skip, and it is the half that proves the chain is queryable rather than merely printed.",
     },
     "checklist-selling-seller-catalog-org-seller-category-inline-create-duplicate-rejected": {
         roles: ["seller"],
@@ -138,13 +179,13 @@ export const authored = {
             "Sign in as tyson@beybladearena.in / TempPass123!.",
             "Open /store/products/new and open the category picker.",
             "Use the create control and type the name of a category that already exists — Beyblade Burst.",
-            "Save and read the message.",
+            "Save and read the message shown on the form.",
             "Open the picker and search that name, counting the matching options.",
-            "Try again with a case variant: beyblade BURST.",
+            "Try again with a case variant: beyblade BURST. The form derives the slug by lowercasing and hyphenating, so this collides on the SAME slug and must be refused for the same reason.",
         ],
         inputs: { existingCategory: "Beyblade Burst", caseVariant: "beyblade BURST" },
-        expectedBehaviour: "A duplicate category is refused. Categories are matched by id on the read side rather than by name, so a duplicate is less immediately destructive than a duplicate brand — but it splits a seller's own catalogue across two near-identical entries with no way to merge them.",
-        expectedUiState: "Both attempts are refused with a readable message, and exactly one option matches the name in the picker.",
+        expectedBehaviour: "A duplicate category is refused on its SLUG, which is what makes the case variant collide too. Categories are matched by id on the read side rather than by name, so a duplicate is less immediately destructive than a duplicate brand — but it splits a seller's own catalogue across two near-identical entries with no way to merge them.",
+        expectedUiState: "Both attempts are refused with a readable message — the server answers 409 'A category with this slug already exists' — and exactly one option matches the name in the picker. A refusal that surfaces only as a silent no-op, or as a raw 409 with no message on the form, is a failure even though nothing was created.",
         expectedData: { matchingOptionCount: 1 },
         endResult: "Leave the editor without saving.",
     },

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

@@ -25,6 +25,7 @@ export const authored = {
         steps: [
             "Sign in as tyson@beybladearena.in / TempPass123!.",
             "Open /store/products/new and find the brand picker.",
+            "Click 'Show all fields (advanced)' first. 🛑 /store/products/new opens the QUICK form for a standard create, and its six fields are Product Name, Category, Price (₹), Stock Quantity, Description and Product Image — there is NO brand field on it at all. The brand picker exists only on the advanced form.",
             "Type QA Brand inline-create into its search box.",
             "Read what the picker offers when nothing matches.",
             "Use the create control the picker offers and fill the form it opens.",
@@ -41,10 +42,11 @@ export const authored = {
         steps: [
             "Sign in as tyson@beybladearena.in / TempPass123!.",
             "Open /store/products/new and open the brand picker.",
+            "Click 'Show all fields (advanced)' first. 🛑 /store/products/new opens the QUICK form for a standard create, and its six fields are Product Name, Category, Price (₹), Stock Quantity, Description and Product Image — there is NO brand field on it at all. The brand picker exists only on the advanced form.",
             "Search for QA Brand inline-create.",
             "Read whether it is offered as an existing option.",
             "Reload the page and search for it again.",
-            "Open a different creation form — the auction one — and search for it there.",
+            "Open /store/auctions/new — a different creation form — and search for it there. Note that route exists even though /store/auctions itself is a redirect-only shim to the products list.",
         ],
         inputs: { brandName: "QA Brand inline-create" },
         expectedBehaviour: "The brand was written to the shared categories collection as a brand-typed row, so it is available to every form that reads brands, not only the one that created it. A value that exists only in the creating form's local state disappears on reload.",
@@ -57,6 +59,7 @@ export const authored = {
         steps: [
             "Sign in as tyson@beybladearena.in / TempPass123!.",
             "Open /store/products/new and open the brand picker.",
+            "Click 'Show all fields (advanced)' first. 🛑 /store/products/new opens the QUICK form for a standard create, and its six fields are Product Name, Category, Price (₹), Stock Quantity, Description and Product Image — there is NO brand field on it at all. The brand picker exists only on the advanced form.",
             "Use the create control and type QA Brand inline-create — the name that already exists.",
             "Save and read the message.",
             "Open the picker again and search that name.",
@@ -75,10 +78,11 @@ export const authored = {
         steps: [
             "Sign in as tyson@beybladearena.in / TempPass123!.",
             "Open /store/products/new and type 'QA Product custom-brand' as the title.",
+            "Click 'Show all fields (advanced)' first. 🛑 /store/products/new opens the QUICK form for a standard create, and its six fields are Product Name, Category, Price (₹), Stock Quantity, Description and Product Image — there is NO brand field on it at all. The brand picker exists only on the advanced form.",
             "Select QA Brand inline-create in the brand picker.",
             "Type 500 as the price, fill every other required field, and publish.",
             "RELOAD the product's editor and read the brand.",
-            "Open the product's public page and read the brand link below the title.",
+            "Open the product's public page at /products/{its slug} and read the brand link below the title.",
             "Click that link.",
         ],
         inputs: { title: "QA Product custom-brand", brandName: "QA Brand inline-create", price: 500 },
@@ -94,12 +98,12 @@ export const authored = {
             "Look for QA Brand inline-create in the list.",
             "Open its brand page.",
             "Read the product grid and look for 'QA Product custom-brand'.",
-            "Sign in as tyson@beybladearena.in / TempPass123! and delete the QA product, then the QA brand.",
+            "Open the sort control and choose 'Most Products'. ALL brands should be listed, seeded ones included — Takara-Tomy, Beyblade, Hasbro and Independent Keepers. The seed file writes no `metrics` on brand rows, but `onProductWrite` is a documentWritten trigger on products/{productId}: it fires on seed writes too and increments `metrics.productCount` on the brand as well as the category, creating the field. A brand MISSING from this sort means the trigger did not run for its products.",
         ],
         inputs: { brandName: "QA Brand inline-create", productTitle: "QA Product custom-brand" },
         expectedBehaviour: "A seller-created brand becomes a real public brand page listing its products. The match is on display name, so this page is where a name-versus-slug mismatch finally shows — the brand page renders and its grid is empty, which reads as a brand with no stock rather than as a broken link.",
-        expectedUiState: "The brand is listed on /brands and its page shows 'QA Product custom-brand' in the grid. An empty grid on a brand that demonstrably has a product is the failure this whole page builds toward.",
+        expectedUiState: "The brand is listed on /brands and its page shows 'QA Product custom-brand' in the grid. An empty grid on a brand that demonstrably has a product is the failure this whole page builds toward. Under 'Most Products' every brand with products is listed, seeded ones included. An orderBy does silently exclude a document lacking the ordering field, so a brand absent HERE is real evidence that onProductWrite never ran for its products — which is why this sort is worth opening at all.",
         expectedData: { productsOnBrandPage: 1 },
-        endResult: "Both the product and the brand are deleted by the final step, so nothing accumulates across runs.",
+        endResult: "NOTHING is cleaned up here and that is deliberate: this case is signed out, and the harness gives a guest batch no session at all, so a 'sign in and delete' step could never be performed. The QA product and brand are removed by the seller-side case that created them; if this case runs alone, say so and leave them.",
     },
 };

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

@@ -16,17 +16,18 @@
 export const authored = {
     "checklist-selling-seller-guide-seller-guide-pages": {
         roles: ["seller"],
-        startPage: "/store",
+        startPage: "/store/guide",
         steps: [
             "Sign in as tyson@beybladearena.in / TempPass123!.",
-            "Open /store and find the guide or help entries in the sidebar.",
-            "Open each guide page in turn and read its content.",
+            "Open /store and find the 'Guides' group in the sidebar. It is the LAST group and it defaults CLOSED (defaultOpen: false), so expand it — seven entries: All Guides, Listings Guide, Orders Guide, Finance Guide, Settings, Capabilities, WhatsApp Catalog Sync.",
+            "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.",
+            "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.",
             "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. The fifth step is the one that matters most: 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.",
-        expectedUiState: "Each guide shows a heading and body specific to its topic, with no two identical. Every internal link lands on a real page. Instructions match the current screens — a guide naming a control that no longer exists is the finding, quoted exactly.",
+        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.",
+        expectedUiState: "All six guides show a heading and body specific to their topic, with no two identical, and both the sidebar group and the hub reach all of them. Every internal link lands on a real page. Instructions match the current screens — a guide naming a control that no longer exists is the finding, quoted exactly.",
         expectedData: { brokenGuideLinks: 0 },
         endResult: "Read-only; nothing persists. Report stale instructions with the guide's name and the sentence that is wrong, not just that the page loads.",
     },

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

@@ -88,7 +88,8 @@ export const authored = {
         startPage: "/store/auctions",
         steps: [
             "Sign in as tyson@beybladearena.in / TempPass123!.",
-            "Open the store's auctions listing and read each row.",
+            "Open /store/auctions — it redirects to /store/products?listingType=auction, which is the auctions listing; landing there is correct, not a wrong turn.",
+            "Read each row.",
             "Check each shows the current bid, the bid count and time remaining.",
             "Compare one row's figures against that auction's public page.",
             "Find an ended auction and read what its row shows in place of time remaining.",
@@ -310,7 +311,7 @@ export const authored = {
         startPage: "/store/prize-draws",
         steps: [
             "Sign in as tyson@beybladearena.in / TempPass123!.",
-            "Open the store's prize-draws page and create one titled 'QA Prize Draw seller-crud' at 75 per entry, 20 entries, instant-reveal mode.",
+            "Open /store/prize-draws — it redirects to /store/products?listingType=prize-draw, which is the prize-draws listing. Create one titled 'QA Prize Draw seller-crud' at 75 per entry, 20 entries, instant-reveal mode.",
             "Save, RELOAD, and read the mode, the per-entry price and the entry count.",
             "Open the public page and read the purchase panel's wording.",
             "Check the panel describes buying an ENTRY rather than buying the prize.",

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

@@ -25,7 +25,7 @@ export const authored = {
         startPage: "/store/offers",
         steps: [
             "Sign in as tyson@beybladearena.in / TempPass123!.",
-            "Open the store's offers list and read every row — product, offered amount, listed price, status and round.",
+            "Open /store/offers and read every row — product, offered amount, listed price, status and round.",
             "Read every status filter offered and select each in turn, noting any that returns nothing.",
             "For each empty filter, check the unfiltered list for rows carrying that status.",
             "Open one offer and read its detail, including any earlier rounds.",
@@ -40,11 +40,11 @@ export const authored = {
         startPage: "/store/features",
         steps: [
             "Sign in as tyson@beybladearena.in / TempPass123!.",
-            "Open the store's product-features page and read the existing features.",
+            "Open /store/features and read the existing features.",
             "Create one named 'QA Feature marketing-extras' with an icon and a description, and save.",
             "RELOAD and read every field.",
-            "Open a product editor and attach that feature to 'Beyblade Burst B-01 Valkyrie', then save.",
-            "Open the product's public page and read whether the feature is shown.",
+            "Open /store/products, find 'Beyblade Burst B-01 Valkyrie', open its editor, attach that feature and save.",
+            "Open the product's public page at /products/{its slug} and read whether the feature is shown.",
             "Detach it, then delete the feature.",
         ],
         inputs: { name: "QA Feature marketing-extras", productId: "product-beyblade-burst-valkyrie" },
@@ -54,10 +54,10 @@ export const authored = {
     },
     "checklist-selling-seller-marketing-extras-seller-google-reviews-sync": {
         roles: ["seller"],
-        startPage: "/store",
+        startPage: "/store/google-reviews",
         steps: [
             "Sign in as tyson@beybladearena.in / TempPass123!.",
-            "Open the store's Google reviews sync surface and read what it asks for.",
+            "Open /store/google-reviews and read what it asks for.",
             "Read whether it states that credentials are required and which ones.",
             "Trigger a sync without credentials configured and read the message.",
             "Read whether any error mentions a provider, a key, or a raw response.",
@@ -69,10 +69,10 @@ export const authored = {
     },
     "checklist-selling-seller-marketing-extras-seller-whatsapp-catalog": {
         roles: ["seller"],
-        startPage: "/store",
+        startPage: "/store/whatsapp",
         steps: [
             "Sign in as tyson@beybladearena.in / TempPass123!.",
-            "Open the store's WhatsApp catalog surface and read every control.",
+            "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.",
@@ -83,15 +83,15 @@ export const authored = {
     },
     "checklist-selling-seller-marketing-extras-seller-whatsapp-token-save": {
         roles: ["seller", "guest"],
-        startPage: "/store",
+        startPage: "/store/whatsapp",
         steps: [
             "Sign in as tyson@beybladearena.in / TempPass123!.",
-            "Open the store's WhatsApp settings and type QA-WHATSAPP-TOKEN-118427 into the access-token field.",
-            "Save and RELOAD, then read how the token is displayed.",
+            "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.",
+            "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.",
@@ -101,10 +101,10 @@ export const authored = {
     },
     "checklist-selling-seller-marketing-extras-seller-whatsapp-import-runs-in-background": {
         roles: ["seller"],
-        startPage: "/store",
+        startPage: "/store/whatsapp",
         steps: [
             "Sign in as tyson@beybladearena.in / TempPass123!.",
-            "Open the store's WhatsApp catalog surface and start an import.",
+            "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.",
@@ -116,10 +116,10 @@ export const authored = {
     },
     "checklist-selling-seller-marketing-extras-seller-whatsapp-import-skips-already-synced": {
         roles: ["seller"],
-        startPage: "/store",
+        startPage: "/store/whatsapp",
         steps: [
             "Sign in as tyson@beybladearena.in / TempPass123!.",
-            "Open the store's WhatsApp catalog surface and run an import, noting the summary and the store's product count.",
+            "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.",
@@ -128,7 +128,7 @@ export const authored = {
         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.",
+        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"],
@@ -151,7 +151,7 @@ export const authored = {
         startPage: "/store/reviews",
         steps: [
             "Sign in as tyson@beybladearena.in / TempPass123!.",
-            "Open the store's reviews list and open a review with no seller response.",
+            "Open /store/reviews and open a review with no seller response.",
             "Type 'QA Response seller-reviews-response — thanks for the feedback.' as the response and save.",
             "RELOAD and read the response.",
             "Open that review on the product's public page in a private window.",