@mohasinac/appkit 4.57.0 → 4.59.0

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

@@ -1,138 +0,0 @@
-/*
- * WHY: Authored six-part procedures for the selling/seller-analytics-payouts page.
- * WHAT: 6 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.
- *
- * 🛑 A PAYOUT IS MONEY LEAVING THE PLATFORM, so several cases here read the FULL
- * deduction breakdown rather than only the net figure. A net amount alone cannot
- * distinguish a correct deduction from a wrong one, and the seller-side deduction
- * is deliberately uncapped where the buyer-facing platform fee is capped — so the
- * two are not expected to agree and a case that assumes they do is wrong.
- *
- * @tag domain:tester
- * @tag layer:seed
- * @tag pattern:none
- * @tag access:server-only
- * @tag consumers:seed-data/authored/index.ts
- * @tag sideEffects:none
- */
-export const authored = {
-    "checklist-selling-seller-analytics-payouts-view-analytics": {
-        roles: ["seller"],
-        startPage: "/store/analytics",
-        steps: [
-            "Sign in as tyson@beybladearena.in / TempPass123!.",
-            "Open the store's analytics page and read every figure and chart on it.",
-            "Write down any figure reading zero, a dash, or 'undefined'.",
-            "Change the date range if one is offered and read the figures again.",
-            "Compare the order count shown against the number of orders in /store/orders.",
-            "Reload the page and check the figures are the same.",
-        ],
-        expectedBehaviour: "Analytics read from pre-computed rollups rather than scanning every order per request — that is the pattern this codebase uses to keep a dashboard load inside its read budget. A figure that fails to compute must read as unknown rather than as zero: zero is a claim, and it is the wrong one.",
-        expectedUiState: "Figures and charts render with real values. The order count is consistent with the orders list. A dash for a genuinely unavailable metric is acceptable; a confident zero beside a list that clearly has rows is not.",
-        endResult: "Read-only; nothing persists. Note any metric reading zero against visible data — that is the failure this case exists for.",
-    },
-    "checklist-selling-seller-analytics-payouts-view-payouts": {
-        roles: ["seller"],
-        startPage: "/store/payouts",
-        steps: [
-            "Sign in as tyson@beybladearena.in / TempPass123!.",
-            "Open /store/payouts and read every row — period, gross, deductions, net and status.",
-            "Read every status filter offered and select each in turn.",
-            "Write down any filter returning zero rows, then check the unfiltered list for rows of that status.",
-            "Read the sort dropdown's default and confirm it is one of the offered options.",
-            "Open one payout row.",
-        ],
-        expectedBehaviour: "The list shows each payout with its own deductions rather than a bare net figure. Status filters use the values payouts actually hold — and a default sort that is not among the offered options opens the dropdown with nothing selected, which is a real defect on this listing family.",
-        expectedUiState: "Rows show period, gross, deductions and net. Every status filter either returns its own rows or is empty with none in the unfiltered list either. The sort default is one of the options. Rows open a detail view.",
-        endResult: "Read-only; nothing persists beyond the URL.",
-    },
-    "checklist-selling-seller-analytics-payouts-payouts-checkbox-select": {
-        roles: ["seller"],
-        startPage: "/store/payouts",
-        steps: [
-            "Sign in as tyson@beybladearena.in / TempPass123!.",
-            "Open /store/payouts and tick the checkbox on one row.",
-            "Read the bulk action bar that appears and the count it states.",
-            "Click the row itself, away from the checkbox, and read what happens.",
-            "Tick a second row and read the count again.",
-            "Use select-all and read the count against the number of rows on the page.",
-            "Clear the selection and check the bar disappears.",
-        ],
-        expectedBehaviour: "Selecting rows and opening a row are separate gestures — merely WIRING selection must not disable navigation. A card or row that stops opening the moment a selection handler exists, regardless of whether anything is selected, is the specific defect this checks.",
-        expectedUiState: "Ticking a checkbox shows a bulk bar with an accurate count. Clicking the row body with nothing selected still opens the payout. Select-all matches the visible row count. Clearing hides the bar without leaving an empty strip behind.",
-        endResult: "Clear the selection; nothing is mutated. A row that will not open while a checkbox exists is the failure.",
-    },
-    "checklist-selling-seller-analytics-payouts-payouts-detail-panel": {
-        roles: ["seller"],
-        startPage: "/store/payouts",
-        steps: [
-            "Sign in as tyson@beybladearena.in / TempPass123!.",
-            "Open /store/payouts and open a payout's detail panel from the list.",
-            "Write down every field label it shows, in order.",
-            "Read the deduction lines and check they add up to gross minus net.",
-            "Read the list of orders included in the payout.",
-            "Close the panel and check the list is unchanged behind it.",
-        ],
-        expectedBehaviour: "The panel shows the full breakdown — gross, each deduction, net — and the orders that make it up. The arithmetic is the check: a net figure alone cannot distinguish a correct deduction from a wrong one, and a payout is money actually leaving.",
-        expectedUiState: "Gross minus the listed deductions equals the net shown, to the paisa. The included orders are listed and identifiable. Any rounding gap is a finding, not a rounding artefact.",
-        expectedData: { deductionsReconcile: true },
-        endResult: "Read-only; close the panel without acting.",
-    },
-    "checklist-selling-seller-analytics-payouts-payouts-reminder-toggle": {
-        roles: ["seller"],
-        startPage: "/store/payouts",
-        steps: [
-            "Sign in as tyson@beybladearena.in / TempPass123!.",
-            /*
-             * 🛑 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 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.",
-    },
-    "checklist-selling-seller-analytics-payouts-seller-payout-detail-full-page": {
-        roles: ["seller"],
-        startPage: "/store/payouts",
-        steps: [
-            "Sign in as tyson@beybladearena.in / TempPass123!.",
-            "Open /store/payouts and open a payout's detail panel from the list.",
-            "Write down every field label it shows.",
-            "Note the payout's id and close the panel.",
-            "Open that payout's standalone detail page directly by URL.",
-            "Write down every field label it shows and compare the two lists.",
-            "Reload the standalone page and confirm it still renders.",
-        ],
-        expectedBehaviour: "The panel and the page render from one shared content component, so their fields are identical by construction. The standalone page exists because a panel cannot be bookmarked, shared with a colleague, or reopened after a crash — and a payout is exactly the record someone needs to send to someone else.",
-        expectedUiState: "Both surfaces show the same fields with the same values. The standalone page survives a reload with the same payout loaded. A field present in one and missing from the other means a second copy of the content component has appeared.",
-        endResult: "Read-only; nothing persists.",
-    },
-};

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

@@ -1,2 +0,0 @@
-import type { AuthoredCase } from "./_types";
-export declare const authored: Record<string, AuthoredCase>;

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

@@ -1,106 +0,0 @@
-/*
- * WHY: Authored six-part procedures for the selling/seller-bids-bundles-filters page.
- * WHAT: 4 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.
- *
- * 🛑 A FILTER CHIP'S id IS PASSED STRAIGHT INTO AN EQUALITY, and the comparison is
- * byte-exact. A chip whose value is a display label, a wrong case, or a status the
- * documents never hold returns zero rows forever with no error anywhere — so every
- * case here reads the chip's ROWS, not merely that the chip responds.
- *
- * @tag domain:tester
- * @tag layer:seed
- * @tag pattern:none
- * @tag access:server-only
- * @tag consumers:seed-data/authored/index.ts
- * @tag sideEffects:none
- */
-export const authored = {
-    "checklist-selling-seller-bids-bundles-filters-seller-bids-status-filter": {
-        roles: ["seller"],
-        startPage: "/store/bids",
-        steps: [
-            "Sign in as tyson@beybladearena.in / TempPass123!.",
-            "Open the store's bids page and note the total row count with no filter applied.",
-            "Read every status chip offered and write the list down.",
-            "Select each chip in turn and read the row count and the statuses shown in the rows.",
-            "Write down any chip that returns zero rows.",
-            "For each such chip, check the unfiltered list for rows carrying that status.",
-        ],
-        expectedBehaviour: "Every chip offered corresponds to a status bids actually hold. The last step is what separates an empty chip from a broken one: a chip returning nothing while the unfiltered list contains rows of that status is a wrong filter value, and it fails silently because a byte-exact equality that matches nothing is not an error.",
-        expectedUiState: "Each chip either returns rows of its own status, or returns none AND the unfiltered list has none either. A chip that is empty while matching rows are visible unfiltered is the failure, named by chip.",
-        expectedData: { chipsEmptyWithMatchingRows: 0 },
-        endResult: "Read-only; nothing persists beyond the URL.",
-    },
-    "checklist-selling-seller-bids-bundles-filters-seller-bids-sort-dropdown": {
-        roles: ["seller"],
-        startPage: "/store/bids",
-        steps: [
-            "Sign in as tyson@beybladearena.in / TempPass123!.",
-            "Open the store's bids page and read the sort dropdown's default selection and the row order.",
-            "Select each other sort option in turn, reading the row order after each.",
-            "Write down any option that does not change the order.",
-            "Check that the dropdown's default is one of the options it offers.",
-            "Reload with a sort applied and read the order on first paint.",
-        ],
-        expectedBehaviour: "Every sort option reorders the rows. An option whose field is not marked sortable is dropped before the query runs, so the dropdown selection changes and nothing moves. A default that is not among the offered options opens the dropdown with nothing selected.",
-        expectedUiState: "Each option produces a visibly different order. The default is one of the listed options. After the reload the rows are in the selected order on first paint, not the default order that then re-sorts.",
-        expectedData: { inertSortOptions: 0 },
-        endResult: "Read-only; nothing persists beyond the URL.",
-    },
-    "checklist-selling-seller-bids-bundles-filters-seller-bids-bidder-search": {
-        roles: ["seller"],
-        startPage: "/store/bids",
-        steps: [
-            "Sign in as tyson@beybladearena.in / TempPass123!.",
-            "Open the store's bids page and read a bidder identifier from any row.",
-            "Read the search box's placeholder or helper text for how it matches.",
-            "Type that identifier exactly and read the results.",
-            "Clear the box, type only the first half of it, and read the results.",
-            "Clear the box, type zzzznope, and read the results.",
-        ],
-        inputs: { nonsenseQuery: "zzzznope" },
-        expectedBehaviour: "Bidder identities are PII-encrypted at rest, so they can only be matched exactly through a blind index — a partial match is impossible by design rather than by omission. The box must SAY so, because otherwise a partial search returning nothing reads as broken.",
-        expectedUiState: "The exact identifier returns its rows. The partial one returns none, and the box states that matching is exact. 'zzzznope' returns none rather than the full list.",
-        expectedData: { nonsenseResultCount: 0 },
-        endResult: "Read-only. Bidder names shown in these rows should be masked — an unmasked full name here is a separate and more serious finding than anything about the search.",
-    },
-    "checklist-selling-seller-bids-bundles-filters-seller-bundles-active-filter": {
-        roles: ["seller"],
-        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: "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.d.ts

@@ -1,2 +0,0 @@
-import type { AuthoredCase } from "./_types";
-export declare const authored: Record<string, AuthoredCase>;

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

@@ -1,192 +0,0 @@
-/*
- * WHY: Authored six-part procedures for the selling/seller-catalog-org page.
- * 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 — 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
- * @tag pattern:none
- * @tag access:server-only
- * @tag consumers:seed-data/authored/index.ts
- * @tag sideEffects:none
- */
-export const authored = {
-    "checklist-selling-seller-catalog-org-seller-categories-crud": {
-        roles: ["seller"],
-        startPage: "/store/categories",
-        steps: [
-            "Sign in as tyson@beybladearena.in / TempPass123!.",
-            "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: {
-            label: "QA Shelf catalog-org",
-            renamed: "QA Shelf catalog-org renamed",
-        },
-        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"],
-        startPage: "/store/sublisting-categories",
-        steps: [
-            "Sign in as tyson@beybladearena.in / TempPass123!.",
-            "Open the store's sublisting-categories page and read the list.",
-            "Create one named 'QA Sublisting catalog-org' with a description and save.",
-            "RELOAD and read every field.",
-            "Rename it to 'QA Sublisting catalog-org renamed', save, and RELOAD.",
-            "Read the page title and description shown for it, and check they reflect the new name.",
-            "Delete it.",
-        ],
-        inputs: {
-            name: "QA Sublisting catalog-org",
-            renamed: "QA Sublisting catalog-org renamed",
-        },
-        expectedBehaviour: "A sublisting category's derived page metadata is recomputed on rename. Deriving it only at creation freezes the title and description at the original name, so the page keeps describing itself as something it is no longer called — a create-time transform the update path does not repeat.",
-        expectedUiState: "After the rename and reload, both the name AND the derived title and description reflect the new name. Metadata still naming the original is the failure.",
-        endResult: "The sublisting category is deleted by the final step.",
-    },
-    "checklist-selling-seller-catalog-org-sublisting-categories-standard-toolbar": {
-        roles: ["seller"],
-        startPage: "/store/sublisting-categories",
-        steps: [
-            "Sign in as tyson@beybladearena.in / TempPass123!.",
-            "Open the store's sublisting-categories page and write down every toolbar control, left to right.",
-            "Open /store/products and write down its toolbar controls the same way.",
-            "Compare the two orderings.",
-            "Type zzzznope into the search box and read the result count.",
-            "Look for any empty gap in the toolbar where a control would sit.",
-        ],
-        inputs: { nonsenseQuery: "zzzznope" },
-        expectedBehaviour: "This listing uses the shared toolbar scaffold, so its controls match every other listing's in kind and order. The nonsense query is the control that proves the search box filters rather than decorates.",
-        expectedUiState: "The two toolbars present the same controls in the same order. 'zzzznope' returns zero rows and an empty state, not the full list. No empty gap where a control was removed.",
-        expectedData: { nonsenseResultCount: 0 },
-        endResult: "Read-only; nothing persists beyond the URL.",
-    },
-    "checklist-selling-seller-catalog-org-seller-listing-templates-crud": {
-        roles: ["seller"],
-        startPage: "/store/listing-templates",
-        steps: [
-            "Sign in as tyson@beybladearena.in / TempPass123!.",
-            "Open /store/listing-templates and read the list.",
-            "Create a template named 'QA Template catalog-org' with a category, a condition and a description filled in, and save.",
-            "RELOAD and read every field of the saved template.",
-            "Open /store/products/new and apply that template.",
-            "Read which fields it populated.",
-            "Delete the template.",
-        ],
-        inputs: { name: "QA Template catalog-org" },
-        expectedBehaviour: "A template stores a reusable set of field values and applying it populates them in a new listing form. There are two template features in this codebase — an older product-template one superseded by this listing-template one — so confirming which page is reachable from the sidebar matters as much as the CRUD itself.",
-        expectedUiState: "The template survives its reload with every field. Applying it in the product form fills those fields rather than only the name. A template that saves but populates nothing is the failure.",
-        endResult: "The template is deleted by the final step; leave the product editor without saving.",
-    },
-    "checklist-selling-seller-catalog-org-seller-category-inline-create": {
-        roles: ["seller"],
-        startPage: "/store/products/new",
-        steps: [
-            "Sign in as tyson@beybladearena.in / TempPass123!.",
-            "Open /store/products/new and find the category picker.",
-            "Type QA Category inline-create into its search box.",
-            "Read what the picker offers when nothing matches.",
-            "Use the create control and complete the form it opens.",
-            "Read the picker's selection afterwards.",
-        ],
-        inputs: { categoryName: "QA Category inline-create" },
-        expectedBehaviour: "The category picker offers inline creation for the same reason the brand picker does — a seller listing something genuinely new should not have to abandon the form. The created option is auto-selected.",
-        expectedUiState: "A create control appears when the search matches nothing, and after saving the picker shows the new category as selected without being re-opened.",
-        endResult: "A category exists. Leave the editor without saving — it is what the next case reads.",
-    },
-    "checklist-selling-seller-catalog-org-seller-category-inline-create-persists": {
-        roles: ["seller", "guest"],
-        startPage: "/store/products/new",
-        steps: [
-            "Sign in as tyson@beybladearena.in / TempPass123!.",
-            "Open /store/products/new, search the category picker for QA Category inline-create, and confirm it is offered.",
-            "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 and confirm the product is listed on the page it opens.",
-            "Delete the product and the category afterwards.",
-        ],
-        inputs: {
-            categoryName: "QA Category inline-create",
-            title: "QA Product inline-category",
-            price: 400,
-        },
-        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. 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"],
-        startPage: "/store/products/new",
-        steps: [
-            "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 shown on the form.",
-            "Open the picker and search that name, counting the matching options.",
-            "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 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.d.ts

@@ -1,2 +0,0 @@
-import type { AuthoredCase } from "./_types";
-export declare const authored: Record<string, AuthoredCase>;

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

@@ -1,109 +0,0 @@
-/*
- * WHY: Authored six-part procedures for the selling/seller-custom-brands page.
- * WHAT: 5 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.
- *
- * 🛑 A BRAND PAGE MATCHES ITS PRODUCTS BY DISPLAY NAME, not by slug. So a brand
- * created here and the brand string written onto the product must agree exactly,
- * and the public brand page is the only place that disagreement becomes visible —
- * the seller's own dashboard shows the product filed correctly either way.
- *
- * @tag domain:tester
- * @tag layer:seed
- * @tag pattern:none
- * @tag access:server-only
- * @tag consumers:seed-data/authored/index.ts
- * @tag sideEffects:none
- */
-export const authored = {
-    "checklist-selling-seller-custom-brands-seller-brand-inline-create": {
-        roles: ["seller"],
-        startPage: "/store/products/new",
-        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.",
-            "Save the new brand and read the picker's selection afterwards.",
-        ],
-        inputs: { brandName: "QA Brand inline-create" },
-        expectedBehaviour: "A picker with more than five options is searchable, and where a seller might legitimately need a value that does not exist it offers inline creation. The newly created option is auto-selected — making the seller find it again in the list is the half-finished version of this feature.",
-        expectedUiState: "Searching a name that does not exist shows a create control rather than only an empty state. After saving, the picker shows 'QA Brand inline-create' as the current selection without the seller re-opening it.",
-        endResult: "A brand exists. Leave the product editor without saving — the brand is what the next cases read.",
-    },
-    "checklist-selling-seller-custom-brands-seller-brand-inline-create-persists": {
-        roles: ["seller"],
-        startPage: "/store/products/new",
-        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 /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.",
-        expectedUiState: "The brand is offered as an existing option in the product form, after a reload, and in the auction form. Being absent from any of the three is the failure.",
-        endResult: "Leave every editor without saving.",
-    },
-    "checklist-selling-seller-custom-brands-seller-brand-inline-create-duplicate-rejected": {
-        roles: ["seller"],
-        startPage: "/store/products/new",
-        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.",
-            "Count how many options match it.",
-            "Try once more with the same name in different case: qa brand INLINE-CREATE.",
-        ],
-        inputs: { brandName: "QA Brand inline-create", caseVariant: "qa brand INLINE-CREATE" },
-        expectedBehaviour: "A duplicate is refused rather than creating a second row. Because a brand page matches products by DISPLAY NAME, two rows with the same name are two brands the read side cannot tell apart — and a case-differing duplicate is the same problem wearing a disguise.",
-        expectedUiState: "The duplicate attempt is refused with a readable message. Exactly one option matches the name in the picker. The case-differing attempt is refused too — accepting it creates the ambiguity this rule exists to prevent.",
-        expectedData: { matchingOptionCount: 1 },
-        endResult: "Leave the editor without saving.",
-    },
-    "checklist-selling-seller-custom-brands-seller-brand-product-saves-with-new-brand": {
-        roles: ["seller"],
-        startPage: "/store/products/new",
-        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 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 },
-        expectedBehaviour: "The product stores both the brand's slug and its display name, and the two stay in lockstep. The public page's brand link resolves to the brand's own page — a link built from one field while the page matches on the other lands somewhere empty.",
-        expectedUiState: "After the reload the editor shows the brand. The public page shows a brand link reading 'QA Brand inline-create' and clicking it opens that brand's page rather than a 404.",
-        endResult: "The product exists and is the fixture the next case reads. Delete it after that case.",
-    },
-    "checklist-selling-seller-custom-brands-seller-brand-appears-on-public-brands-page": {
-        roles: ["guest"],
-        startPage: "/brands",
-        steps: [
-            "Open /brands in a private window with no session.",
-            "Look for QA Brand inline-create in the list.",
-            "Open its brand page.",
-            "Read the product grid and look for 'QA Product custom-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. 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: "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.d.ts

@@ -1,2 +0,0 @@
-import type { AuthoredCase } from "./_types";
-export declare const authored: Record<string, AuthoredCase>;

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

@@ -1,34 +0,0 @@
-/*
- * WHY: Authored six-part procedures for the selling/seller-guide page.
- * WHAT: 1 case, 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.
- *
- * @tag domain:tester
- * @tag layer:seed
- * @tag pattern:none
- * @tag access:server-only
- * @tag consumers:seed-data/authored/index.ts
- * @tag sideEffects:none
- */
-export const authored = {
-    "checklist-selling-seller-guide-seller-guide-pages": {
-        roles: ["seller"],
-        startPage: "/store/guide",
-        steps: [
-            "Sign in as tyson@beybladearena.in / TempPass123!.",
-            "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.",
-            "Follow every link inside the guides and note where each lands.",
-        ],
-        expectedBehaviour: "Every seller guide renders its own content and every link in it resolves. A guide describing a screen that has since changed is worse than no guide, because the seller trusts it and then cannot find what it names. The sidebar group defaulting closed is deliberate — guides are reference, not daily work — so a tester who does not expand it will wrongly conclude they are missing.",
-        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.d.ts

@@ -1,2 +0,0 @@
-import type { AuthoredCase } from "./_types";
-export declare const authored: Record<string, AuthoredCase>;