@mohasinac/appkit 4.58.0 → 4.59.0

package/dist/features/tester/seed-data/authored/admin__catalog-listings.js

@@ -1,318 +0,0 @@
-/*
- * WHY: Authored six-part procedures for the admin/catalog-listings page.
- * WHAT: 17 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 ADMIN TYPE CHIPS ONCE USED DISPLAY LABELS AS FILTER VALUES, translated
- * through an indirection map that hid two entirely missing types. A filter value
- * is compared byte-exactly, so a chip reading "Pre-orders" against a stored
- * "pre-order" matches nothing forever with no error. Four cases here read the
- * chips against the real union rather than trusting the labels.
- *
- * Categories are the other theme: a product carries its FULL ancestor chain so a
- * parent page can match on its own id alone. That chain IS derived on write, by
- * `ProductRepository.deriveTaxonomy()`, from create and update alike — this header
- * said the opposite until 2026-09-29 and told the tester a one-element chain was
- * expected. A form cannot supply the chain itself (the create schema strips it), so
- * if the derivation stops running there is no fallback and the product silently
- * reaches only its leaf page.
- *
- * @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-admin-catalog-listings-brands-crud": {
-        roles: ["admin", "guest"],
-        startPage: "/admin/brands",
-        steps: [
-            "Sign in as admin@letitrip.in / TempPass123!.",
-            "Open /admin/brands and create one named 'QA Brand admin-crud' with a website, a country and a founding year.",
-            "Upload public/test-media/sample-image.png to the field labelled for the hero or cover image.",
-            "Save, RELOAD, and read every field.",
-            "Open /brands/{slug} in a private window and read the hero banner and the 'About this brand' panel.",
-            "Check the uploaded image is what renders as the hero.",
-            "Rename the brand, save, reload, and check its URL slug is unchanged.",
-            "Delete the brand and confirm it disappears from /brands.",
-        ],
-        inputs: { name: "QA Brand admin-crud", image: "public/test-media/sample-image.png" },
-        expectedBehaviour: "Brands are category rows discriminated by type, not a separate collection. The image field that actually drives the public hero is the COVER image — a form once offered a 'Logo' input that fed the hero and a 'Banner' input that fed a field with no readers anywhere, so every uploaded banner was silently discarded. Website, country and founding year must render publicly rather than being accepted and never shown.",
-        expectedUiState: "After the reload every field holds. The public page's hero is the uploaded image, and the 'About this brand' panel shows the website, country and year. The slug is unchanged after the rename.",
-        endResult: "The brand is deleted. Record any field the form accepts that never appears publicly — that is a field with no reader.",
-    },
-    "checklist-admin-catalog-listings-categories-crud": {
-        roles: ["admin", "guest"],
-        startPage: "/admin/categories",
-        steps: [
-            "Sign in as admin@letitrip.in / TempPass123!.",
-            "Open /admin/categories and read the tree, noting the six roots and how depth is shown.",
-            "Create a child category named 'QA Category admin-crud' under category-beyblade-burst.",
-            "Save, RELOAD, and read its parent, its tier and its position in the tree.",
-            "Open /categories in a private window and find it beneath its parent.",
-            "Rename it, save, reload, and check its slug is unchanged.",
-            "Delete it and confirm it disappears from the tree and from /categories.",
-        ],
-        inputs: { name: "QA Category admin-crud", parent: "category-beyblade-burst" },
-        expectedBehaviour: "Creating a child places it in the tree with its full ancestor chain derived rather than hand-written — the chain, tier, path and position are all computed, and hand-writing any of them is how a tree goes inconsistent. The slug is immutable after creation, as everywhere else.",
-        expectedUiState: "After the reload the category sits under Beyblade Burst at the right depth, and it appears there publicly. Its slug survives the rename. After the delete it is gone from both surfaces.",
-        endResult: "The category is deleted by the final step.",
-    },
-    "checklist-admin-catalog-listings-products-crud": {
-        roles: ["admin", "guest"],
-        startPage: "/admin/products",
-        steps: [
-            "Sign in as admin@letitrip.in / TempPass123!.",
-            "Open /admin/products and create a product titled 'QA Product admin-crud' at 600 with stock 3, an image, the brand Beyblade, and the category Burst Parts — which sits two levels below the root.",
-            "Save, RELOAD, and read every field.",
-            "Open its public page and read the title, price, stock badge, category links and brand link.",
-            "Count the category links shown and read their names.",
-            "Edit ONLY the price to 700, save, RELOAD, and compare every other field.",
-            "Delete the product and confirm the public page no longer resolves.",
-        ],
-        inputs: {
-            title: "QA Product admin-crud",
-            priceBefore: 600,
-            priceAfter: 700,
-            stock: 3,
-            categoryId: "category-burst-parts",
-            brand: "Beyblade",
-        },
-        expectedBehaviour: "An admin create and edit round-trip, and an edit writes back only what changed. The category links are the second assertion: the repository derives the full ancestor chain on write, so a product filed under Burst Parts carries Beyblade Burst and Spinning Tops with it. The brand link is the same shape — products are matched to a brand by DISPLAY NAME while the picker's value is the brand row's id, so that too is resolved on write rather than stored as picked.",
-        expectedUiState: "After each reload the values hold and only the price differs after the edit. THREE category links: Burst Parts, Beyblade Burst, Spinning Tops. The brand link resolves to a page that lists this product rather than an empty one. One category link, or a brand page that does not list it, are both write-path failures and both look entirely normal on the product's own page. After the delete the public URL no longer resolves.",
-        expectedData: { unintendedFieldChanges: 0, categoryLinksShown: 3 },
-        endResult: "The product is deleted. Report the category link count either way.",
-    },
-    "checklist-admin-catalog-listings-products-default-listing-not-empty": {
-        roles: ["admin"],
-        startPage: "/admin/products",
-        steps: [
-            "Sign in as admin@letitrip.in / TempPass123!.",
-            "Open /admin/products with NO query parameters at all.",
-            "Read the result count and the rows.",
-            "Read which availability scope and which status filter are applied by default.",
-            "Switch to the All scope and compare the count.",
-            "Clear every filter and compare again.",
-        ],
-        expectedBehaviour: "The admin listing opens showing rows. This page shares one query implementation with the public browse path, reached through a sentinel that lets any status through — so an admin listing that opens empty usually means a filter default meant for the public path is being applied here, where an admin needs to see drafts and archived rows too.",
-        expectedUiState: "The default view holds rows rather than an empty state. The All scope returns at least as many. An empty default listing with rows appearing only after clearing filters is the failure.",
-        endResult: "Read-only; nothing persists beyond the URL.",
-    },
-    "checklist-admin-catalog-listings-categories-toggle-filters": {
-        roles: ["admin"],
-        startPage: "/admin/categories",
-        steps: [
-            "Sign in as admin@letitrip.in / TempPass123!.",
-            "Open /admin/categories and note the total row count.",
-            "Read every toggle and filter offered above the list.",
-            "Use each in turn and read the resulting count and rows.",
-            "Write down any toggle that leaves the count unchanged.",
-            "Clear everything and confirm the original count returns.",
-        ],
-        expectedBehaviour: "Every toggle changes the list. A toggle that renders, counts toward the filter badge and matches nothing is inert — that happens when it reads a field the document does not have, and nothing raises. Category rows carry a type discriminator, so filters separating categories from brands, bundles and sublistings are the ones most likely to be reading the wrong field.",
-        expectedUiState: "Each toggle visibly changes the rows. A toggle leaving the count identical while incrementing the filter badge is the failure, named specifically.",
-        expectedData: { inertToggles: 0 },
-        endResult: "Read-only; nothing persists beyond the URL.",
-    },
-    "checklist-admin-catalog-listings-admin-products-type-chips-all-types": {
-        roles: ["admin"],
-        startPage: "/admin/products",
-        steps: [
-            "Sign in as admin@letitrip.in / TempPass123!.",
-            "Open /admin/products and read every listing-type chip offered.",
-            "Write the list down and compare it against the nine types the catalogue supports.",
-            "Select each chip in turn and read the result count and the rows.",
-            "Write down any chip returning zero rows, and any returning the full unfiltered list.",
-            "Check whether a chip for `bundle` is offered.",
-        ],
-        expectedBehaviour: "Nine chips, each filtering to its own type. The chips once used display LABELS as filter values through an indirection map that hid two missing types entirely — and a filter value is compared byte-exactly, so a chip reading 'Pre-orders' against a stored 'pre-order' matches nothing forever. A chip for `bundle` must NOT exist: it stopped being a listing type and would match zero rows permanently.",
-        expectedUiState: "Nine chips are offered and each returns only its own type. No `bundle` chip. A chip returning zero while that type demonstrably exists is the byte-exactness failure; one returning everything is the dropped-filter failure.",
-        expectedData: { typeChipCount: 9 },
-        endResult: "Read-only; nothing persists beyond the URL.",
-    },
-    "checklist-admin-catalog-listings-admin-products-type-chips-multi-select": {
-        roles: ["admin"],
-        startPage: "/admin/products",
-        steps: [
-            "Sign in as admin@letitrip.in / TempPass123!.",
-            "Open /admin/products and tick the Auctions chip, reading the count.",
-            "Tick Pre-orders as well and read the count.",
-            "Check the count is the sum of the two rather than either alone.",
-            "Read the URL and check it encodes both types.",
-            "Open the sort dropdown and read which options are offered with two types selected.",
-            "Untick both and confirm the unfiltered count returns.",
-        ],
-        expectedBehaviour: "Multiple type chips form an OR, so selecting two returns both sets. The alias layer has to split a joined value before looking each part up — testing the whole joined string as one token returns an empty value that is then dropped, so the filter vanishes and the page shows everything. The sort dropdown narrows to options valid for every selected type, since a sort valid for one alone would fail the others.",
-        expectedUiState: "Two chips ticked returns the sum of their individual counts, and the URL carries both. The sort dropdown offers only sorts common to both. A combined selection returning the FULL unfiltered list is the dropped-filter failure.",
-        endResult: "Read-only; nothing persists beyond the URL.",
-    },
-    "checklist-admin-catalog-listings-admin-products-featured-promoted-sorts": {
-        roles: ["admin"],
-        startPage: "/admin/products",
-        steps: [
-            "Sign in as admin@letitrip.in / TempPass123!.",
-            "Open /admin/products and read the sort dropdown's options.",
-            "Select 'Featured first' and read the row order.",
-            "Select 'Promoted first' and read the row order.",
-            "Compare both against the default order.",
-            "Reload with one applied and read the order on first paint.",
-        ],
-        expectedBehaviour: "Both sorts reorder the rows. A sort whose field is not marked sortable is dropped before the query runs, so the dropdown changes and nothing moves — these two shipped exactly that way and went unreported, because a sort that does nothing looks like a list already in that order.",
-        expectedUiState: "Featured rows rise under the first and promoted under the second, and both differ from the default. After a reload the chosen order holds on first paint rather than re-sorting a moment later.",
-        expectedData: { inertSortOptions: 0 },
-        endResult: "Read-only; nothing persists beyond the URL.",
-    },
-    "checklist-admin-catalog-listings-admin-per-type-pages-have-filters": {
-        roles: ["admin"],
-        startPage: "/admin/products",
-        steps: [
-            "Sign in as admin@letitrip.in / TempPass123!.",
-            "Open each per-type admin listing in turn, BY URL — there are exactly six and only /admin/classified is linked from the sidebar: /admin/prize-draws, /admin/classified, /admin/digital-codes, /admin/live, /admin/art, /admin/stickers.",
-            "On each, read the filters offered and note whether any are specific to that type.",
-            "Use each type-specific filter and confirm it changes the rows.",
-            "Write down any page offering no filters at all.",
-            "Write down any filter that changes nothing.",
-            "Now confirm auctions and pre-orders have NO page of their own: /admin/auctions and /admin/pre-orders should not resolve, and both types must instead be reachable as chips on /admin/products.",
-        ],
-        expectedBehaviour: "Each type's page offers the facets that type actually has — a classified's city, a live item's species — on top of the shared ones. A facet that renders and matches nothing is inert, which happens when it emits a field the query allowlist does not carry, and nothing raises. Auctions and pre-orders deliberately have no dedicated admin page; the chips on /admin/products are their only admin surface, and that is why those chips must cover all nine types.",
-        expectedUiState: "All six per-type pages resolve and offer filters including their own, each visibly changing the rows. /admin/auctions and /admin/pre-orders do not resolve, and both types filter correctly from the chips instead — a 404 there is the expected result, not a finding. A page with no filters, or a filter leaving the count identical while incrementing the badge, are findings named by page.",
-        endResult: "Read-only; nothing persists beyond the URL.",
-    },
-    "checklist-admin-catalog-listings-admin-listing-reset-restores-defaults": {
-        roles: ["admin"],
-        startPage: "/admin/products",
-        steps: [
-            "Sign in as admin@letitrip.in / TempPass123!.",
-            "Open /admin/products and note the default count, scope and sort.",
-            "Apply a search term, two type chips, a status filter and a different sort.",
-            "Read the URL and the count.",
-            "Use the reset control.",
-            "Read the URL, the count, the scope, the sort and every filter control.",
-            "Reload and read them again.",
-        ],
-        expectedBehaviour: "Reset returns every control AND the URL to the defaults, not just the visible chips. A reset that clears the drawer while leaving the search term or the sort in the URL produces a list the controls no longer describe.",
-        expectedUiState: "After reset the count, scope and sort match the untouched defaults and the URL carries no leftover parameters. The search box is empty. Reloading reproduces the default view.",
-        endResult: "Read-only; nothing persists beyond the URL.",
-    },
-    "checklist-admin-catalog-listings-admin-address-payment-status-chips-in-url": {
-        roles: ["admin"],
-        startPage: "/admin/addresses",
-        steps: [
-            "Sign in as admin@letitrip.in / TempPass123!.",
-            "Open /admin/addresses and select a status chip.",
-            "Read the URL and check it encodes the selection.",
-            "Copy the URL, open it in a new tab, and read which chip is active on arrival.",
-            "Press the browser back button and read which chip is active.",
-            "Repeat all of this on /admin/payment-methods, which has the same chip row.",
-        ],
-        expectedBehaviour: "Chip state lives in the URL on both listings, so a filtered view is shareable and the back button walks the selections. A chip held in component state alone makes the URL describe a different page from the one on screen.",
-        expectedUiState: "Both listings encode the chip in the URL, the copied URL arrives with the same chip active, and back returns to the previous selection. One press per selection — two presses to undo one chip is the double-navigation failure.",
-        endResult: "Read-only; nothing persists beyond the URL.",
-    },
-    "checklist-admin-catalog-listings-admin-listing-sort-dropdown-preselected": {
-        roles: ["admin"],
-        startPage: "/admin/products",
-        steps: [
-            "Sign in as admin@letitrip.in / TempPass123!.",
-            "Open /admin/products with no query parameters and read the sort dropdown's selection.",
-            "Check something is selected rather than the control being blank.",
-            "Confirm the selected option is one of the options the dropdown offers.",
-            "Repeat on /admin/orders, /admin/addresses and /admin/payment-methods.",
-            "Write down any listing whose dropdown opens with nothing selected.",
-        ],
-        expectedBehaviour: "A listing's default sort is one of the options it offers. Where the default names a field the dropdown does not list, the control opens blank — the list IS sorted, but nothing on screen says how, and two of these listings shipped exactly that way.",
-        expectedUiState: "Every listing opens with a sort visibly selected and that selection is among its own options. A blank dropdown is the failure, named by listing.",
-        endResult: "Read-only; nothing persists.",
-    },
-    "checklist-admin-catalog-listings-sublisting-categories-crud": {
-        roles: ["admin", "guest"],
-        startPage: "/admin/sublisting-categories",
-        steps: [
-            "Sign in as admin@letitrip.in / TempPass123!.",
-            "Open /admin/sublisting-categories and read the existing rows.",
-            "Create one named 'QA Sublisting admin-crud' with a description and save.",
-            "RELOAD and read every field.",
-            "Rename it, save, RELOAD, and read the derived page title and description.",
-            "Check they reflect the NEW name rather than the original.",
-            "Delete it and confirm it is gone.",
-        ],
-        inputs: { name: "QA Sublisting admin-crud" },
-        expectedBehaviour: "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-admin-catalog-listings-carousel-crud": {
-        roles: ["admin", "guest"],
-        startPage: "/admin/carousels",
-        steps: [
-            "Sign in as admin@letitrip.in / TempPass123!.",
-            "Open /admin/carousels and read what the page lists.",
-            "Check it lists NAMED carousels rather than rendering a flat slide editor.",
-            "Create a carousel named 'QA Carousel admin-crud' and add a slide with a title, an image and a link.",
-            "Save, RELOAD, and read the carousel's name, status and its slide.",
-            "Set it active and open / in a private window to find it.",
-            "Add slides to it until a sixth ACTIVE slide is refused. The cap of five is on active SLIDES, not on carousels, and the seed already ships five active ones — so the refusal may arrive on the very first slide you activate.",
-            "Delete the carousel.",
-        ],
-        inputs: { name: "QA Carousel admin-crud", maxActive: 5 },
-        expectedBehaviour: "The list page lists named carousels — it once rendered the flat slide editor instead, so there was no list at all. At most five SLIDES may be active at once — refused at write with a 409 naming the limit, not silently truncated, and there is deliberately no cap on the number of named carousels. A slide's background may be an image, a video, a colour or a gradient; a video background renders through a real video element, so its URL must be directly playable rather than routed through the image proxy, which rejects video outright.",
-        expectedUiState: "The page lists named carousels. After the reload the carousel holds its name, status and slide. Activating it shows it publicly. A sixth active SLIDE is refused with a readable message rather than silently accepted or silently dropped from the public carousel. Refusing to create a sixth CAROUSEL would be the opposite failure — there is no such cap.",
-        endResult: "The carousel is deleted by the final step.",
-    },
-    "checklist-admin-catalog-listings-sections-crud": {
-        roles: ["admin", "guest"],
-        startPage: "/admin/sections",
-        steps: [
-            "Sign in as admin@letitrip.in / TempPass123!.",
-            "Open /admin/sections and read every section, its type and its order. It is the homepage sections editor; /admin is only a redirect to the dashboard.",
-            "Create a section, choosing a type, and configure every field it offers.",
-            "Save, RELOAD, and read every field back.",
-            "Open / in a private window and find the new section in the right position.",
-            "Change ONE field, save, RELOAD, and check every other field is unchanged.",
-            "Delete the section and confirm it disappears from the public homepage.",
-        ],
-        expectedBehaviour: "A section round-trips every field its type offers, and the public homepage reflects its configuration and position. Saving one field must not rewrite the others — a form submitting its whole object from partly-populated state blanks every field it did not load, and the save reports success.",
-        expectedUiState: "After each reload every field holds and only the edited one differs. The public homepage shows the section in its configured position and with its configured content. After the delete it is gone publicly.",
-        expectedData: { unintendedFieldChanges: 0 },
-        endResult: "The section is deleted by the final step.",
-    },
-    "checklist-admin-catalog-listings-art-stickers-crud": {
-        roles: ["admin", "guest"],
-        startPage: "/admin/products",
-        steps: [
-            "Sign in as admin@letitrip.in / TempPass123!.",
-            "Create an art listing titled 'QA Art Print admin-crud' at 700 with a size, material, finish and edition size.",
-            "Save, RELOAD, and read all four print fields.",
-            "Open /admin/art and check the listing appears there.",
-            "Read every other row in that filtered view and check none is an ordinary product.",
-            "Open /art publicly and check the listing appears there too. Art and stickers share that one browse route — there is no /stickers page.",
-            "Delete the listing.",
-        ],
-        inputs: { title: "QA Art Print admin-crud", price: 700 },
-        expectedBehaviour: "Art and stickers are real listing types with their own fields and their own filter value. They were added to the type union and the plugin registry without being added to the repository's alias map, so their queries ran with NO type filter — the filtered view rendered and returned the whole catalogue, which looks like a working page.",
-        expectedUiState: "The print fields round-trip. The art-filtered admin view holds only art listings — an ordinary Beyblade product among them is the dropped-filter failure. The public art tab shows it too.",
-        expectedData: { ordinaryProductsInFilteredView: 0 },
-        endResult: "The listing is deleted by the final step.",
-    },
-    "checklist-admin-catalog-listings-deals-featured-crud": {
-        roles: ["admin", "guest"],
-        startPage: "/admin/products",
-        steps: [
-            "Sign in as admin@letitrip.in / TempPass123!.",
-            "Open /admin/products and open a product's editor.",
-            "Set its featured flag on and save.",
-            "RELOAD and confirm the flag is still on.",
-            "Open / in a private window and find the product in a featured section.",
-            "Set the promoted flag on, save, reload, and open /admin/featured and /admin/deals — both are real listings of flagged products and the product must appear in the matching one.",
-            "Turn both flags back off, save, and confirm the product leaves the homepage section AND leaves /admin/featured and /admin/deals.",
-        ],
-        expectedBehaviour: "Featured, promoted and on-sale flags reach the public surfaces they drive, in both directions. Turning a flag off must remove the product from its section — a flag that only ever adds is half a flag, and the homepage sections that read them filter by availability too, so a sold-out featured product should not appear.",
-        expectedUiState: "Each flag survives its reload and its public surface follows it on and off. The product appears in the featured section when flagged and leaves when unflagged.",
-        endResult: "Both flags are off by the final step, so the seeded product is left as it was.",
-    },
-};

package/dist/features/tester/seed-data/authored/admin__category-brand-authoring.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/admin__category-brand-authoring.js

@@ -1,177 +0,0 @@
-/*
- * WHY: Authored six-part procedures for the admin/category-brand-authoring page.
- * WHAT: 8 case(s), keyed by full checklist id.
- *
- * The WRITE side of the tree. Its read side is content-discovery/category-brand-relations;
- * these are the operations that can corrupt what that page then renders.
- *
- * 🛑 THE ANCESTOR-CHAIN CASE WAS INVERTED AND IS NOW CORRECTED. This header used to
- * say "nothing on the write path derives a product's ancestor chain", and the case
- * encoded that as `categoryPagesListingIt: 1` — so once the gap was actually closed,
- * the case DEMANDED the bug: correct behaviour scored a fail and a tester following
- * it would have filed the fix as a regression.
- *
- * `ProductRepository.deriveTaxonomy()` has derived the chain from both `create` and
- * `update` since 2026-09-14. It reads the leaf's `parentIds`, reverses them onto the
- * front, and writes `categorySlugs = [leaf, ...ancestors]` — byte-identical to what
- * the seed hand-writes. The expected answer is now ALL THREE pages.
- *
- * It stays a valuable case for a reason worth keeping: every SEEDED product already
- * carries a correct chain, so a regression here is invisible to any check that reads
- * existing data. Only a product created through a form can catch it.
- *
- * @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-admin-category-brand-authoring-create-child-under-parent": {
-        roles: ["admin"],
-        startPage: "/admin/categories",
-        steps: [
-            "Sign in as admin@letitrip.in / TempPass123!.",
-            "Open /admin/categories and create a category named 'QA Child Burst Layers'.",
-            "Pick Burst Parts as its parent.",
-            "Save it.",
-            "Open /categories/category-burst-parts on the public site and read its children.",
-            "Click down into the new category and read the path shown.",
-            "Delete the category afterwards.",
-        ],
-        inputs: { name: "QA Child Burst Layers", parentId: "category-burst-parts" },
-        expectedBehaviour: "Picking a parent files the category at that parent's depth plus one and makes it appear beneath it publicly. Depth and lineage are computed from the parent — there is nothing else for the author to get right.",
-        expectedUiState: "The new category is listed as a child of Burst Parts on the public tree and its breadcrumb reads Spinning Tops, Beyblade Burst, Burst Parts, then itself.",
-        endResult: "The QA category is deleted.",
-    },
-    "checklist-admin-category-brand-authoring-structural-fields-derived-not-typed": {
-        roles: ["admin"],
-        startPage: "/admin/categories",
-        steps: [
-            "Sign in as admin@letitrip.in / TempPass123!.",
-            "Open /admin/categories and start creating a category.",
-            "Read every field the form offers.",
-            "Check there is no input for tier, path, ancestors, children, position or subtree size.",
-            "Check the only structural input is the parent picker.",
-            "Open an existing deep category for edit and read the same.",
-        ],
-        expectedBehaviour: "Every structural field is derived from the parent. Exposing one lets an author write a tier that disagrees with the parent they picked, and the tree is then internally inconsistent in a way no page reports — a category can appear at one depth in the breadcrumb and a different one in the listing.",
-        expectedUiState: "The create and edit forms both offer a parent picker and no structural field. Any such input is the finding, named.",
-        endResult: "Nothing is saved.",
-    },
-    "checklist-admin-category-brand-authoring-reparent-moves-whole-subtree": {
-        roles: ["admin"],
-        startPage: "/admin/categories",
-        steps: [
-            "Sign in as admin@letitrip.in / TempPass123!.",
-            "Note that Burst Parts sits under Beyblade Burst and note its own children.",
-            "Edit Burst Parts and change its parent to Beyblade X.",
-            "Save and open /categories/category-beyblade-x publicly.",
-            "Check Burst Parts is listed there and click into it.",
-            "Check its children are still present and still reachable.",
-            "Restore its parent to Beyblade Burst.",
-        ],
-        inputs: { categoryId: "category-burst-parts", newParentId: "category-beyblade-x" },
-        expectedBehaviour: "Re-parenting carries the whole subtree. A move that updates only the moved row leaves its descendants pointing at a lineage that no longer describes them — they are still in the collection and reachable by direct URL, and absent from every page that walks the tree.",
-        expectedUiState: "Burst Parts appears under Beyblade X with all its children intact and clickable. A child that 404s or vanishes from the tree is the finding.",
-        endResult: "The original parent is restored.",
-    },
-    "checklist-admin-category-brand-authoring-product-created-with-deep-category-visible-at-root": {
-        roles: ["admin"],
-        startPage: "/admin/products",
-        steps: [
-            "Sign in as admin@letitrip.in / TempPass123!.",
-            "Create a product named 'QA Ancestor Chain Probe' priced at 499 and file it under Burst Parts.",
-            "Publish it.",
-            "Open /categories/category-burst-parts publicly and check the product is listed.",
-            "Open /categories/category-beyblade-burst and search for it.",
-            "Open /categories/category-spinning-tops and search for it.",
-            "Record on which of the three pages it appears — Burst Parts sits two levels below the root, so all three are expected.",
-            "Delete the product afterwards.",
-        ],
-        inputs: { title: "QA Ancestor Chain Probe", price: 499, categoryId: "category-burst-parts" },
-        expectedBehaviour: "A category page matches on its own id alone, which works only if the product carries its full ancestor chain — and the repository derives that chain on write, from create and update alike. A form cannot supply it: the create schema strips any categorySlugs it is sent, so if the derivation stops running there is no fallback and the product silently reaches its leaf page only.",
-        expectedUiState: "All THREE pages list it: Burst Parts, Beyblade Burst and Spinning Tops. Visible only on Burst Parts is the failure — and it is a silent one, because the product's own page looks entirely normal and every seeded product around it still shows a correct chain.",
-        expectedData: { categoryPagesListingIt: 3 },
-        endResult: "The QA product is deleted.",
-    },
-    "checklist-admin-category-brand-authoring-brand-rename-orphan-check": {
-        roles: ["admin"],
-        startPage: "/admin/brands",
-        steps: [
-            "Sign in as admin@letitrip.in / TempPass123!.",
-            "Open /brands/brand-takara-tomy publicly and count the products listed.",
-            "Open /admin/brands, edit Takara-Tomy, and change its name to 'Takara Tomy QA'.",
-            "Save it.",
-            "Reload /brands/brand-takara-tomy and count the products again.",
-            "Read whether any warning was shown at save time about products that would be affected.",
-            "Restore the name to 'Takara-Tomy' and reload once more.",
-        ],
-        inputs: { brandId: "brand-takara-tomy", renamedTo: "Takara Tomy QA" },
-        expectedBehaviour: "Products are matched to a brand by its display name, so a rename either carries the products with it or warns that it will not. Neither happening is the failure this case is for: the page renders its hero and its editorial panels perfectly over an empty grid, and nothing anywhere connects that to the rename.",
-        expectedUiState: "After the rename the brand page lists the same products, or the save warned first. An empty grid with no warning is the finding, with the before and after counts.",
-        endResult: "The brand name is restored and the products are listed again.",
-    },
-    "checklist-admin-category-brand-authoring-brand-cover-image-is-the-hero": {
-        roles: ["admin"],
-        startPage: "/admin/brands",
-        steps: [
-            "Sign in as admin@letitrip.in / TempPass123!.",
-            "Open /admin/brands and edit Hasbro.",
-            "Read every image field the form offers and note each one's label.",
-            "Upload /test-media/sample-image.png into the field labelled as the cover image.",
-            "Save and open /brands/brand-hasbro publicly.",
-            "Check the uploaded image is what renders as the page's hero banner.",
-            "If the form offers a second image field, upload a distinguishable image there and check whether anything renders it.",
-        ],
-        inputs: { brandId: "brand-hasbro", imagePath: "/test-media/sample-image.png" },
-        expectedBehaviour: "The field labelled as the cover image is the one the hero renders. A form once had a Logo input and a Banner input side by side where Logo wrote the hero's field and Banner wrote a field with no readers at all — so the labels described the reverse of reality and every uploaded banner was discarded silently.",
-        expectedUiState: "The image uploaded into the cover field is the hero on the public page. A second image field whose upload appears nowhere is a finding — that field has no reader.",
-        endResult: "The brand carries the uploaded cover image.",
-    },
-    "checklist-admin-category-brand-authoring-category-type-not-guessable": {
-        roles: ["admin"],
-        startPage: "/admin/categories",
-        steps: [
-            "Sign in as admin@letitrip.in / TempPass123!.",
-            "Open /admin/categories and start creating a category.",
-            "Read every field the create form offers and confirm there is NO dropdown for the row's kind or type — the fields are name, slug, description, parent, order, active and show-in-menu.",
-            "Create one named 'QA Kind Probe' with no parent and save it.",
-            "Open /admin/brands and confirm 'QA Kind Probe' is NOT listed there.",
-            "Create a brand named 'QA Brand Probe' on /admin/brands and save it.",
-            "Return to /admin/categories and confirm 'QA Brand Probe' is NOT listed among the categories.",
-            "Open /brands publicly and confirm QA Brand Probe appears; open /categories and confirm QA Kind Probe appears and QA Brand Probe does not.",
-            "Delete both QA rows.",
-        ],
-        inputs: { categoryName: "QA Kind Probe", brandName: "QA Brand Probe" },
-        expectedBehaviour: "Brands, bundles, sub-listing groups and ordinary categories are all rows in ONE collection distinguished by a kind field — but the author never picks it. The surface determines it: /admin/brands lists and writes kind=brand, /admin/categories writes an ordinary category. That is deliberate, so a missing kind dropdown is correct rather than a gap. What must hold is that the two surfaces stay disjoint.",
-        expectedUiState: "No kind dropdown on either form. Each row appears on exactly ONE admin surface and exactly one public surface. A brand leaking into the category tree — or a category into the brand list — means the kind was not set from the surface, and that row will render in a place built for a different shape.",
-        endResult: "Both QA rows are deleted. If a row appeared on both surfaces, record which, and delete it — a mistyped row is worse left in place than removed.",
-    },
-    "checklist-admin-category-brand-authoring-delete-category-with-children-refused": {
-        roles: ["admin"],
-        startPage: "/admin/categories",
-        steps: [
-            "Sign in as admin@letitrip.in / TempPass123!.",
-            "Create a category 'QA Doomed Parent' under Beyblade Burst, then a category 'QA Orphan Child' under QA Doomed Parent.",
-            "Create a product 'QA Cascade Probe' priced at 499 filed directly under QA Doomed Parent, and publish it.",
-            "Open /admin/categories and delete QA Doomed Parent.",
-            "Open /categories/category-beyblade-burst publicly and look for QA Orphan Child — it should now sit directly under Beyblade Burst.",
-            "Open the QA Cascade Probe product's public page and read its category links.",
-            "Open /categories/category-beyblade-burst and confirm the product is listed there.",
-            "Delete QA Orphan Child and the product afterwards.",
-        ],
-        inputs: {
-            doomedParent: "QA Doomed Parent",
-            orphanChild: "QA Orphan Child",
-            productTitle: "QA Cascade Probe",
-            price: 499,
-            grandparentId: "category-beyblade-burst",
-        },
-        expectedBehaviour: "Deleting a category CASCADES TO ITS PARENT rather than refusing: the children re-parent to the grandparent and the products are re-filed there, through the repository so each product's ancestor chain is rebuilt from its new leaf. This replaced an older flat refusal. The order is load-bearing — products must move while the document still exists — so the failure mode to watch for is a product left pointing at a category that is gone.",
-        expectedUiState: "QA Orphan Child now sits directly under Beyblade Burst. QA Cascade Probe is filed under Beyblade Burst and its category links show the rebuilt chain, with no link naming the deleted QA Doomed Parent. A product with a dead category link, a one-element chain, or one missing from Beyblade Burst entirely is the failure.",
-        expectedData: { childReparentedToGrandparent: true, deadCategoryLinks: 0 },
-        endResult: "Only the two QA rows and the QA product were touched; the seeded tree is unchanged. Do NOT test this by deleting a seeded category — the whole Burst subtree would re-parent and every other case reading it in this run would then be testing a different tree.",
-    },
-};

package/dist/features/tester/seed-data/authored/admin__classifieds-digitalcodes-live.d.ts

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