@mohasinac/appkit 4.34.0 → 4.35.0

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

@@ -0,0 +1,167 @@
+/*
+ * WHY: Authored six-part procedures for the selling/sectionised-forms page.
+ * WHAT: 9 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.
+ *
+ * 🛑 THE FIRST AND LAST CASES ARE THE SAME ASSERTION AT TWO SCALES: saving a form
+ * writes back only what changed. A form that submits its whole object from
+ * partly-populated state overwrites every field it did not load, returns a normal
+ * success, and is invisible without a reload — which is why both end in one.
+ *
+ * @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-sectionised-forms-form-sections-save-unchanged": {
+        roles: ["seller"],
+        startPage: "/store/products",
+        steps: [
+            "Sign in as tyson@beybladearena.in / TempPass123!.",
+            "Open the editor for 'Beyblade Burst B-01 Valkyrie' and expand every section.",
+            "Write down the value of every field in every section.",
+            "Change one field in ONE section — the description — and save.",
+            "RELOAD the editor and expand every section again.",
+            "Compare every field against what was written down.",
+            "Restore the description and save.",
+        ],
+        inputs: { productId: "product-beyblade-burst-valkyrie" },
+        expectedBehaviour: "Editing one section leaves every other section's values untouched. A sectionised form that submits its whole object from state populated only by the sections the user opened silently blanks the rest — and the save reports success either way.",
+        expectedUiState: "After the reload only the description differs. Every other field in every other section holds its original value, including images, category, brand, stock and the type-specific fields.",
+        expectedData: { unintendedFieldChanges: 0 },
+        endResult: "The product is restored. Any field that emptied itself is the failure, and it is invisible without expanding every section after the reload.",
+    },
+    "checklist-selling-sectionised-forms-form-error-summary-jumps": {
+        roles: ["seller"],
+        startPage: "/store/products/new",
+        steps: [
+            "Sign in as tyson@beybladearena.in / TempPass123!.",
+            "Open /store/products/new and read the page before typing — note whether any errors are listed.",
+            "Leave required fields empty in two DIFFERENT sections.",
+            "Collapse both of those sections.",
+            "Attempt to publish.",
+            "Read the error summary and click an error belonging to a collapsed section.",
+        ],
+        expectedBehaviour: "The summary appears only after a submit is attempted, and clicking an entry expands the owning section and moves to the field. An error in a collapsed section is otherwise unreachable — the user is told something is wrong and cannot see what.",
+        expectedUiState: "No summary before the publish attempt. Afterwards it lists errors from both sections, tagged with their section. Clicking one expands that section and scrolls the field into view.",
+        endResult: "Nothing is published. Leave the editor without saving.",
+    },
+    "checklist-selling-sectionised-forms-required-section-has-no-dead-chevron": {
+        roles: ["seller"],
+        startPage: "/store/products/new",
+        steps: [
+            "Sign in as tyson@beybladearena.in / TempPass123!.",
+            "Open /store/products/new and look at every section header.",
+            "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.",
+            "Compare against a collapsible section's chevron.",
+        ],
+        expectedBehaviour: "A section that cannot collapse does not display a collapse control. A chevron that responds to nothing teaches the user the whole form's chevrons are unreliable, which is a worse cost than the one dead control.",
+        expectedUiState: "Always-open sections have no chevron, or their chevron is visibly non-interactive. A chevron that looks identical to a working one and does nothing on click is the failure.",
+        endResult: "Read-only; leave the editor without saving.",
+    },
+    "checklist-selling-sectionised-forms-open-section-does-not-clip-dropdowns": {
+        roles: ["seller"],
+        startPage: "/store/products/new",
+        steps: [
+            "Sign in as tyson@beybladearena.in / TempPass123!.",
+            "Open /store/products/new and expand a section containing a picker.",
+            "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.",
+            "Read whether its list is clipped by the section's own boundary.",
+            "Resize to 390 pixels wide and open the same picker.",
+        ],
+        inputs: { mobileWidth: 390 },
+        expectedBehaviour: "A picker's list escapes its section's bounds. A section with overflow hidden — which is what a collapsing container needs to animate — clips any list that opens inside it, so the options exist and cannot be seen.",
+        expectedUiState: "The full option list is visible in every case, including in the last section and at 390 pixels. A list cut off at the section's edge is the failure, and it is worst at the bottom of the form where there is least room.",
+        endResult: "Read-only; leave the editor without saving.",
+    },
+    "checklist-selling-sectionised-forms-error-jump-lands-on-the-field": {
+        roles: ["seller"],
+        startPage: "/store/products/new",
+        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.",
+            "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.",
+            "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.",
+        expectedUiState: "The offending field is visible, focused, and carries its own error message. Scrolling to the section heading and stopping there is the failure, as is scrolling past the field so it sits under a sticky bar.",
+        endResult: "Nothing is published. Leave the editor without saving.",
+    },
+    "checklist-selling-sectionised-forms-long-form-typing-is-smooth": {
+        roles: ["seller"],
+        startPage: "/store/products/new",
+        steps: [
+            "Sign in as tyson@beybladearena.in / TempPass123!.",
+            "Open /store/products/new and expand every section.",
+            "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.",
+            "Watch again for lag.",
+        ],
+        expectedBehaviour: "Typing stays responsive with every section open and live validation running. Validation runs on every change once a submit has been attempted — that is what keeps the error summary current — so this is the state where a form is most likely to stutter.",
+        expectedUiState: "Characters appear as they are typed, with no visible catch-up. The error summary updates as fields are fixed without the field itself becoming laggy.",
+        endResult: "Nothing is published. Leave the editor without saving.",
+    },
+    "checklist-selling-sectionised-forms-form-mobile-action-bar": {
+        roles: ["seller"],
+        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.",
+            "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.",
+            "Open the error sheet from the bar, close it, then attempt a publish again and check it reopens.",
+            "Count the fixed bars at the bottom.",
+        ],
+        inputs: { mobileWidth: 390 },
+        expectedBehaviour: "The form's save row and its error sheet occupy the same measured bottom tier as everything else. The sheet's label carries the error COUNT, because the panel only republishes when that label changes — a static label would freeze the sheet's contents while the user fixes fields. Reopening on a second failed submit is driven by a counter rather than a flag, so an ordinary re-render does not reopen what the user just closed.",
+        expectedUiState: "Discard, Save draft and Publish are all reachable and none is clipped. The sheet's label states how many issues remain and that number falls as fields are fixed. Closing it and submitting again reopens it. Exactly one bottom tab bar sits below the action bar.",
+        endResult: "Nothing is published. Restore the window width afterwards.",
+    },
+    "checklist-selling-sectionised-forms-form-conditional-fields-drop-values": {
+        roles: ["seller"],
+        startPage: "/store/products/new",
+        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.",
+            "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.",
+            "Read whether the values are still there.",
+            "Publish and then reload the editor, reading those fields again.",
+        ],
+        expectedBehaviour: "A hidden conditional field either keeps its value or is genuinely dropped — but whichever it does, the saved record must match what the form displayed at submit. The dangerous case is a field that looks retained on screen and is dropped on save, or one dropped from view and still written.",
+        expectedUiState: "Toggling the controlling field back and forth leaves the conditional values in a state the form shows honestly. After publishing and reloading, the stored values match what was on screen when Publish was pressed.",
+        endResult: "Delete the created listing afterwards. A field the form showed and did not save is the failure, and so is one it hid and saved anyway.",
+    },
+    "checklist-selling-sectionised-forms-site-settings-save-still-writes-everything": {
+        roles: ["admin"],
+        startPage: "/admin/site",
+        steps: [
+            "Sign in as admin@letitrip.in / TempPass123!.",
+            "Open /admin/site and walk every tab, writing down a distinctive value from each.",
+            "Open one tab — Fees — and change a single field.",
+            "Save.",
+            "RELOAD /admin/site and walk every tab again.",
+            "Compare each noted value against what was written down.",
+            "Restore the changed field and save.",
+        ],
+        expectedBehaviour: "Saving one tab of the settings singleton preserves every other tab. This is the same defect as the first case at the largest possible scale: the whole document is one record, so a form submitting its full object from a partly-populated state can blank branding, fees, integrations and legal copy in one save that reports success.",
+        expectedUiState: "After the reload only the Fees field differs. Every noted value on every other tab is unchanged — branding, announcement copy, integrations, shipping, legal pages. The masked credentials are still shown as masked rather than blank.",
+        expectedData: { unintendedFieldChanges: 0 },
+        endResult: "The changed field is restored. This is the highest-blast-radius save in the application; check every tab rather than sampling two.",
+    },
+};

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

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

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

@@ -0,0 +1,117 @@
+/*
+ * 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!.",
+            "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.",
+        ],
+        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.",
+        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

@@ -0,0 +1,2 @@
+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

@@ -0,0 +1,88 @@
+/*
+ * 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!.",
+            "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.",
+        ],
+        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.",
+    },
+};

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

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

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

@@ -0,0 +1,151 @@
+/*
+ * WHY: Authored six-part procedures for the selling/seller-catalog-org page.
+ * WHAT: 7 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 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.
+ *
+ * @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.",
+            "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.",
+            "Delete it and RELOAD to confirm it is gone.",
+        ],
+        inputs: {
+            name: "QA Category catalog-org",
+            renamed: "QA Category 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.",
+    },
+    "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.",
+            "Delete the product and the category afterwards.",
+        ],
+        inputs: {
+            categoryName: "QA Category inline-create",
+            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.",
+        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.",
+    },
+    "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.",
+            "Open the picker and search that name, counting the matching options.",
+            "Try again with a case variant: beyblade BURST.",
+        ],
+        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.",
+        expectedData: { matchingOptionCount: 1 },
+        endResult: "Leave the editor without saving.",
+    },
+};

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

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