@mohasinac/appkit 4.42.1 → 4.42.2

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

@@ -13,8 +13,12 @@
  * 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, and nothing on the write side
- * derives that chain yet.
+ * 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
@@ -26,10 +30,10 @@
 export const authored = {
     "checklist-admin-catalog-listings-brands-crud": {
         roles: ["admin", "guest"],
-        startPage: "/admin/categories",
+        startPage: "/admin/brands",
         steps: [
             "Sign in as admin@letitrip.in / TempPass123!.",
-            "Open the admin brands surface and create one named 'QA Brand admin-crud' with a website, a country and a founding year.",
+            "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.",
@@ -64,17 +68,24 @@ export const authored = {
         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 a category, a brand, stock 3 and an image.",
+            "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.",
+            "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 },
-        expectedBehaviour: "An admin create and edit round-trip, and an edit writes back only what changed. The category link count is worth recording: a product is supposed to carry its full ancestor chain so every ancestor page can find it, and nothing on the write side derives that chain — so a product created through a form against a deep category gets ONE slug and is invisible on every ancestor page.",
-        expectedUiState: "After each reload the values hold and only the price differs after the edit. Record how many category links the public page shows — one, where the chosen category has ancestors, is the known gap rather than a surprise. After the delete the public URL no longer resolves.",
-        expectedData: { unintendedFieldChanges: 0 },
+        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": {
@@ -161,14 +172,15 @@ export const authored = {
         startPage: "/admin/products",
         steps: [
             "Sign in as admin@letitrip.in / TempPass123!.",
-            "Open each per-type admin listing in turn — auctions, pre-orders, prize draws, classifieds, digital codes, live items, art and stickers.",
+            "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, an auction's bid range — 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.",
-        expectedUiState: "Every per-type page offers filters including its own, and each visibly changes the rows. A page with no filters, or a filter that leaves the count identical while incrementing the badge, are both findings named by page.",
+        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": {
@@ -196,7 +208,7 @@ export const authored = {
             "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 the admin payment-methods listing.",
+            "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.",
@@ -210,7 +222,7 @@ export const authored = {
             "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 the admin payment-methods listing.",
+            "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.",
@@ -219,10 +231,10 @@ export const authored = {
     },
     "checklist-admin-catalog-listings-sublisting-categories-crud": {
         roles: ["admin", "guest"],
-        startPage: "/admin/categories",
+        startPage: "/admin/sublisting-categories",
         steps: [
             "Sign in as admin@letitrip.in / TempPass123!.",
-            "Open the admin sublisting-categories surface and read the existing rows.",
+            "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.",
@@ -244,20 +256,20 @@ export const authored = {
             "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.",
-            "Count the active carousels and check the cap is respected.",
+            "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 may be active at once, and 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. Attempting a sixth active carousel is refused rather than silently accepted.",
+        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",
+        startPage: "/admin/sections",
         steps: [
             "Sign in as admin@letitrip.in / TempPass123!.",
-            "Open the homepage sections editor and read every section, its type and its order.",
+            "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.",
@@ -276,9 +288,9 @@ export const authored = {
             "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 the admin listing filtered to art and check the listing appears there.",
+            "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 the public art tab and check the listing appears there too.",
+            "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 },
@@ -296,8 +308,8 @@ export const authored = {
             "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 or on-sale flag on, save, reload, and check the public surface that flag drives.",
-            "Turn both flags back off, save, and confirm the product leaves those surfaces.",
+            "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.",

package/dist/features/tester/seed-data/authored/admin__category-brand-authoring.js

@@ -5,12 +5,20 @@
  * 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.
  *
- * 🛑 ONE OF THESE IS A KNOWN OPEN GAP RATHER THAN A REGRESSION. Nothing on the
- * write path derives a product's ancestor chain from the category it was filed
- * under — the convention is maintained by hand in the seed. So a seller picking a
- * tier-3 category through the form today produces a one-element chain and a
- * product invisible on every ancestor page. The case says so and asks for what
- * actually happens, because a case that assumes the answer teaches nothing.
+ * 🛑 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
@@ -79,16 +87,14 @@ export const authored = {
             "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.",
+            "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 only works if the product carries its full ancestor chain — and nothing on the write path derives that chain today. So a product created here is expected to be visible on Burst Parts and NOT on its ancestors. That is a known open gap, not a fresh regression, and the value of the case is the exact answer rather than the verdict.",
-        expectedUiState: "Record exactly which of the three category pages list the product. Visible on all three means the chain is now derived on write and the gap is closed; visible only on Burst Parts is today's expected state.",
-        expectedData: { categoryPagesListingIt: 1 },
+        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.",
-        needsReview: true,
-        reviewNote: "Open gap by design — the write side does not append ancestors. The case exists to measure it, and its answer should change once that lands.",
     },
     "checklist-admin-category-brand-authoring-brand-rename-orphan-check": {
         roles: ["admin"],
@@ -130,29 +136,42 @@ export const authored = {
         steps: [
             "Sign in as admin@letitrip.in / TempPass123!.",
             "Open /admin/categories and start creating a category.",
-            "Find where the row's kind is chosen and read the options offered.",
-            "Check the options match the kinds the site actually renders — a listing category, a brand, a sub-listing group and a bundle.",
-            "Check no option is offered that no page renders.",
-            "Save nothing and open an existing brand row for edit, checking its kind is shown.",
+            "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.",
         ],
-        expectedBehaviour: "Brands, bundles, sub-listing groups and ordinary categories are all rows in one collection distinguished by a kind field, so the author has to be able to see and set it. An option offered that no page renders creates rows nothing will ever display.",
-        expectedUiState: "The kind is an explicit, readable choice on create and visible on edit, and every option corresponds to a kind the site renders.",
-        endResult: "Nothing is saved.",
+        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!.",
-            "Open /admin/categories and attempt to delete Beyblade Burst, which has children and products beneath it.",
-            "Read the confirmation or refusal.",
-            "Check the message names how many children or products depend on it.",
-            "If it refuses, cancel and confirm the category is untouched.",
-            "If it succeeds, open the public categories tree and record what happened to its children.",
+            "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: { categoryId: "category-beyblade-burst" },
-        expectedBehaviour: "A delete that orphans a subtree is unrecoverable, so it is refused with a count of what depends on it. Deletes are the one operation whose bug cannot be undone, which is why the refusal has to be structural rather than a warning the admin can click past.",
-        expectedUiState: "The delete is refused with a message naming the dependent children and products. If it succeeds instead, that is the finding and the state of the orphaned subtree is the evidence.",
-        endResult: "The category still exists. If the delete succeeded, re-seed rather than attempting a manual repair.",
+        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.js

@@ -11,6 +11,45 @@
  * as a rejection that leaves the item live — both look correct from the admin's
  * seat, and only the public view can tell them apart.
  *
+ * 🛑 STATUS IS CHANGED FROM THE LIST, NOT THE EDITOR (corrected 2026-09-29).
+ *
+ * All three cases said "open its detail" and then "change its status and save".
+ * `AdminProductEditorView` has exactly three sections — Listing type, Details,
+ * Inventory — and `status` appears in it only as a default and as read-only
+ * header text. There is no status control to use. The real ones are on
+ * /admin/products' row menu: 'Approve' (writes published), 'Reject', and a
+ * 'Quick edit' drawer whose Status select is the one place an admin picks a
+ * value. So the procedure now names the row menu.
+ *
+ * 🛑 AND THE TYPE TABS IN THAT EDITOR RENDER NOTHING. Every `<TabsContent>` is
+ * self-closing: the strip flips the `listingType` discriminator and shows no
+ * type-specific fields at all. So a moderator opening a live listing sees no
+ * species, no jurisdiction list and no video — which is precisely the
+ * "deciding blind" failure the live case was written to catch, and it is real
+ * today. The case now says where to look and what the finding is, rather than
+ * sending a tester to hunt a panel that does not exist. Recorded in OUTOFSCOPE.
+ *
+ * 🛑 THE CODE POOL IS EDIT-MODE ONLY. `renderDigitalContentPool` is gated on
+ * `mode === "edit" && listingType === "digital-code" && productId`, so a
+ * digital-code listing cannot be created WITH codes in one pass — it is created,
+ * saved, and reopened. "Code Pool Size (optional)" on the create form is a
+ * seller-typed number that the server recounts from the real subcollection; it
+ * is not the pool.
+ *
+ * 🛑 /admin/classified, /admin/digital-codes AND /admin/live ARE BROWSE-ONLY.
+ * All three are thin wrappers over `buildListingTypeListingConfig`, which
+ * supplies a search box, a sort and a `status` filter — and no row actions, no
+ * bulk actions, no Approve/Reject and no Quick edit. The catalogue `href`s
+ * pointed at them, which is a real page where the case's central action cannot
+ * be performed; they now point at /admin/products, and `startPage` says the
+ * same. Both Status and Type on that page are chip groups inside the FILTER
+ * DRAWER, not an always-visible row, and Type is multi-select.
+ *
+ * Field labels used below are the real ones: 'City' / 'Preferred Contact Method'
+ * (section "Meetup Details"), 'Code Pool Size (optional)' /
+ * 'Redemption Instructions (optional)', 'Species / Common Name' /
+ * 'Jurisdictions where sale is permitted'.
+ *
  * @tag domain:tester
  * @tag layer:seed
  * @tag pattern:none
@@ -23,56 +62,104 @@ export const authored = {
         roles: ["admin", "seller", "guest"],
         startPage: "/admin/products",
         steps: [
-            "Sign in as tyson@beybladearena.in / TempPass123! and create a classified titled 'QA Classified admin-moderate' at 900, city Pune.",
-            "Sign out and sign in as admin@letitrip.in / TempPass123!.",
-            "Open the admin listing that holds classifieds and find it.",
-            "Read every status chip offered and select each in turn, noting which returns this listing.",
-            "Change its status to a non-published one and save.",
-            "Open the listing's public URL in a private window and read what is shown.",
-            "Restore it to published, then sign back in as tyson and delete it.",
+            "Sign in as tyson@beybladearena.in / TempPass123!, open /store/classified/new, and create a listing titled 'QA Classified admin-moderate' at 900 with City 'Pune' under Meetup Details. Publish it and note the slug on its public URL.",
+            "Sign in as admin@letitrip.in / TempPass123! and open /admin/products.",
+            "Open the filter drawer, tick Classified in its multi-select Type chip group, apply, and find the listing.",
+            "In that same filter drawer read the Status chip group — All, Pending, Published, Draft, Archived — and select each in turn, noting which one returns this listing.",
+            "Open the row menu, choose 'Quick edit', set Status to Archived, and save.",
+            "Open the listing's public URL and read what is shown.",
+            "Quick-edit it back to Published, then sign in as tyson@beybladearena.in and delete it from /store/classified.",
         ],
-        inputs: { title: "QA Classified admin-moderate", price: 900, city: "Pune" },
+        inputs: { title: "QA Classified admin-moderate", price: 900, city: "Pune", archivedVia: "Quick edit" },
         expectedBehaviour: "An admin status change reaches the public read path. Every status chip must also name a value the documents actually hold — a chip whose id is a display label rather than the stored value matches nothing forever and returns an empty list with no error.",
-        expectedUiState: "The listing is findable under its own status chip. After the status change the public URL no longer renders it as a live listing — a public page still showing it is the failure, and the admin row will look correct either way.",
-        endResult: "The listing is restored to published and then deleted. A chip returning nothing while the unfiltered list holds rows of that status is a separate finding worth naming.",
+        expectedUiState: "While published the listing is returned by the Published chip and by no other. After the archive the public URL no longer renders it as a live listing, and the Archived chip returns it — the admin row will look correct either way, so the public page is the oracle. A chip returning nothing while All holds rows of that status is a separate finding worth naming.",
+        expectedData: { statusAfterArchive: "archived", chipReturningIt: "Archived" },
+        endResult: "The listing is Published again and then deleted. Re-open the public URL after the delete: a page still rendering it is a cache or projection failure.",
     },
     "checklist-admin-classifieds-digitalcodes-live-digitalcode-create-moderate": {
         roles: ["admin", "seller", "guest"],
         startPage: "/admin/products",
         steps: [
-            "Sign in as tyson@beybladearena.in / TempPass123! and create a digital-code listing titled 'QA Digital Code admin-moderate' at 350 with three codes.",
-            "Sign out and sign in as admin@letitrip.in / TempPass123!.",
-            "Find it in the admin listing and open its detail.",
-            "Read whether the actual CODE STRINGS are visible to the admin.",
-            "Change its status to a non-published one and save.",
-            "Open the public URL in a private window and read what is shown.",
-            "Restore it, then sign back in as tyson and delete it.",
+            "Sign in as tyson@beybladearena.in / TempPass123!, open /store/digital-codes/new, and create a listing titled 'QA Digital Code admin-moderate' at 350. Publish it.",
+            "REOPEN it from /store/digital-codes for editing — the code pool is only mounted in edit mode — and add three codes QA-CODE-1, QA-CODE-2, QA-CODE-3. Note the slug on its public URL.",
+            "Sign in as admin@letitrip.in / TempPass123!, open /admin/products, open the filter drawer, tick Digital Code in its Type chip group, apply, and find the listing.",
+            "Read the row and every column: are the actual CODE STRINGS visible anywhere in the list?",
+            "Open the row menu, choose 'Quick edit', set Status to Archived, and save.",
+            "Open the listing's public URL and read what is shown.",
+            "Quick-edit it back to Published, then sign in as tyson@beybladearena.in and delete it from /store/digital-codes.",
         ],
-        inputs: { title: "QA Digital Code admin-moderate", price: 350, codeCount: 3 },
-        expectedBehaviour: "Moderation works the same for this type, and the code pool is the thing worth watching: an unsold code is inventory a buyer will pay for, so it must not be readable from a list view. Availability here reads the nested pool count rather than a stock figure.",
-        expectedUiState: "The listing is findable and its status change takes effect publicly. Unsold code strings are not displayed in the admin list; if the detail view shows them, record exactly where — that is a finding rather than a pass.",
-        endResult: "The listing is restored and deleted. Note whether an admin can read unredeemed codes at all.",
+        inputs: {
+            title: "QA Digital Code admin-moderate",
+            price: 350,
+            codeCount: 3,
+            codes: "QA-CODE-1, QA-CODE-2, QA-CODE-3",
+        },
+        expectedBehaviour: "Moderation works the same for this type, and the code pool is the thing worth watching: an unsold code is inventory a buyer will pay for, so it must not be readable from a list view. Availability for this type reads the nested pool count rather than a stock figure, which is why the pool has to exist before the listing can be judged available at all.",
+        expectedUiState: "The listing is findable under the Digital Code chip and its archive takes effect publicly. NO unredeemed code string appears in the admin list — not in a column, not in a tooltip, not in the quick-edit drawer. If any is visible, quote it and say exactly where; that is a finding, not a pass.",
+        expectedData: { codesVisibleInAdminList: false, statusAfterArchive: "archived" },
+        endResult: "The listing is Published again and then deleted. Record whether an admin can read an unredeemed code anywhere in the product — a 'no' here is a leak of paid inventory.",
     },
     "checklist-admin-classifieds-digitalcodes-live-live-create-moderate": {
         roles: ["admin", "seller", "guest"],
         startPage: "/admin/products",
         steps: [
-            "Sign in as tyson@beybladearena.in / TempPass123! and create a live listing titled 'QA Live Item admin-moderate' at 3000, species Dog, jurisdictions Maharashtra only, with public/test-media/sample-video.mp4 attached.",
-            "Sign out and sign in as admin@letitrip.in / TempPass123!.",
-            "Find it in the admin listing and open its detail.",
-            "Read whether the species, jurisdiction list and video are all shown to the moderator.",
-            "Change its status to a non-published one and save.",
-            "Open the public URL in a private window and read what is shown.",
-            "Restore it, then sign back in as tyson and delete it.",
+            "Sign in as tyson@beybladearena.in / TempPass123!, open /store/live/new, and create a listing titled 'QA Live Item admin-moderate' at 3000 with 'Species / Common Name' set to Dog and 'Jurisdictions where sale is permitted' set to Maharashtra only.",
+            "Attach /test-media/sample-video.mp4 as its video and publish it. Note the slug on its public URL.",
+            "Sign in as admin@letitrip.in / TempPass123!, open /admin/products, open the filter drawer, tick Live Item in its Type chip group, apply, and find the listing.",
+            "Open the row menu and then the editor at /admin/products/{its id}/edit. Read every section and record whether the species, the jurisdiction list and the video appear ANYWHERE.",
+            "Return to /admin/products, open the row menu, choose 'Quick edit', set Status to Archived, and save.",
+            "Open the listing's public URL and read what is shown.",
+            "Quick-edit it back to Published, then sign in as tyson@beybladearena.in and delete it from /store/live.",
         ],
         inputs: {
             title: "QA Live Item admin-moderate",
             price: 3000,
             species: "Dog",
             jurisdictions: "Maharashtra",
+            video: "/test-media/sample-video.mp4",
         },
-        expectedBehaviour: "A live listing is the one type where moderation has a duty beyond commerce — the jurisdiction list decides who may lawfully receive the animal or plant, and the mandatory video is what the moderator judges the listing on. Both must be visible in the admin view or the moderator is deciding blind.",
-        expectedUiState: "The admin detail shows the species line, the jurisdiction list AND the video. The status change takes effect on the public page. A moderation row offering approve and reject without showing the video is the acting-blind failure this page family exists to catch.",
-        endResult: "The listing is restored and deleted. Record specifically whether the video was viewable from the moderation surface.",
+        expectedBehaviour: "A live listing is the one type where moderation has a duty beyond commerce — the jurisdiction list decides who may lawfully receive the animal or plant, and the video is what the moderator judges the listing on. Both must be visible to the admin, or the moderator is approving and rejecting blind.",
+        expectedUiState: "🛑 EXPECT THIS TO FAIL ON THE ADMIN HALF, AND RECORD IT AS A FAILURE. The admin editor has three sections — Listing type, Details, Inventory — and its listing-type tabs render EMPTY content, so no species, no jurisdiction list and no video is shown. Confirm that by reading the sections and say so, naming the three sections you found. The archive half does hold: it takes effect on the public page. Keep the two apart in the comment — the moderation mechanics work and the information the moderator needs is absent.",
+        expectedData: { adminSectionsSeen: 3, speciesShownToAdmin: false, videoShownToAdmin: false },
+        endResult: "The listing is Published again and then deleted. Record specifically whether the video was viewable from any admin surface — that is the finding, not the status change.",
+    },
+    /*
+     * 🛑 ADDED 2026-09-29. The three cases above all archive; none of them used
+     * the 'Reject' action, and it is the one that writes a value the rest of the
+     * product cannot represent.
+     *
+     * `ProductStatus` is draft | published | in_review | archived — four values,
+     * no 'rejected'. `ADMIN_PRODUCT_STATUS_TABS` mirrors those four plus All.
+     * But AdminProductsView's Reject row action writes `{ status: "rejected" }`,
+     * and the PATCH schema types status as a bare `z.string().optional()`, so it
+     * is persisted verbatim with no validation.
+     *
+     * The effect looks right — every public query filters `status == published`,
+     * so the listing does disappear — which is exactly why nobody noticed. The
+     * cost is on the way back: the row now matches no status chip, so an admin
+     * can only reach it under All, and the seller's own status filters cannot
+     * isolate it either. Root Cause #33's shape on the WRITE side.
+     *
+     * Written as a case rather than fixed: choosing between adding 'rejected' to
+     * the union and making Reject write 'archived' is a product decision.
+     */
+    "checklist-admin-classifieds-digitalcodes-live-reject-status-has-no-chip": {
+        roles: ["admin", "seller"],
+        startPage: "/admin/products",
+        steps: [
+            "Sign in as tyson@beybladearena.in / TempPass123!, open /store/classified/new, and create a listing titled 'QA Classified reject-status' at 700 with City 'Pune'. Publish it.",
+            "Sign in as admin@letitrip.in / TempPass123! and open /admin/products.",
+            "Open the filter drawer, tick Classified in its Type chip group, apply, then find the listing, open its row menu and click 'Reject'.",
+            "Read the status shown on the row.",
+            "In the filter drawer select each Status chip in turn — Pending, Published, Draft, Archived — and record whether ANY of them returns the listing.",
+            "Select the All status chip and confirm it is still there.",
+            "Open the listing's public URL and read what is shown.",
+            "Quick-edit it back to Published, then sign in as tyson@beybladearena.in and delete it from /store/classified.",
+        ],
+        inputs: { title: "QA Classified reject-status", price: 700, city: "Pune", action: "Reject" },
+        expectedBehaviour: "A rejected listing must stay reachable by the admin who rejected it. Hiding it from buyers is only half the job — a moderator needs to find it again to explain, reverse or escalate the decision, and the status filters are the only tool for that.",
+        expectedUiState: "🛑 EXPECT THE FILTER HALF TO FAIL. The row reads 'rejected', a value ProductStatus does not have, so none of the four status chips returns it and it is reachable only under All. Record which chips you tried and that each came back without it. The public half should hold — the listing is gone from its public URL, because every public query filters on published.",
+        expectedData: { statusOnRow: "rejected", chipsReturningIt: 0 },
+        endResult: "The listing is Published again and then deleted. Two findings to keep separate: a status no chip matches, and — if the public page still renders it — a far worse one.",
     },
 };