@mohasinac/appkit 4.57.0 → 4.59.0

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

@@ -1,165 +0,0 @@
-/*
- * WHY: Authored six-part procedures for the admin/classifieds-digitalcodes-live page.
- * WHAT: 3 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.
- *
- * 🛑 THESE ARE MODERATION CASES, so each ends on the PUBLIC page. An approval that
- * updates a dashboard row and never reaches the public listing is the same defect
- * 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
- * @tag access:server-only
- * @tag consumers:seed-data/authored/index.ts
- * @tag sideEffects:none
- */
-export const authored = {
-    "checklist-admin-classifieds-digitalcodes-live-classified-create-moderate": {
-        roles: ["admin", "seller", "guest"],
-        startPage: "/admin/products",
-        steps: [
-            "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", 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: "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!, 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,
-            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!, 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 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.",
-    },
-};

package/dist/features/tester/seed-data/authored/admin__content-deletes.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__content-deletes.js

@@ -1,267 +0,0 @@
-/*
- * WHY: Authored six-part procedures for the admin/content-deletes page.
- * WHAT: 14 case(s), keyed by full checklist id.
- *
- * 🛑 A DELETE IS THE ONE OPERATION WHOSE BUG CANNOT BE UNDONE, AND BEFORE THIS PAGE
- * THE WHOLE CATALOGUE HELD THREE CASES THAT TESTED ONE. Creates and edits were
- * covered thoroughly; the operation that destroys data was not, which is exactly
- * backwards.
- *
- * Every case here deletes something it created, or restores what it changed. Where
- * that is not possible — a seeded record with dependents — the case checks the
- * REFUSAL rather than performing the delete.
- *
- * Two distinctions run through the page: disable is not delete, and unpublish is
- * not delete. A screen that blurs either invites an admin to reach for the
- * irreversible one when they wanted the reversible one.
- *
- * @tag domain:tester
- * @tag layer:seed
- * @tag pattern:none
- * @tag access:server-only
- * @tag consumers:seed-data/authored/index.ts
- * @tag sideEffects:none
- */
-const SIGN_IN_ADMIN = "Sign in as admin@letitrip.in / TempPass123!.";
-export const authored = {
-    "checklist-admin-content-deletes-homepage-section-edit-persists": {
-        roles: ["admin"],
-        startPage: "/admin/sections",
-        steps: [
-            SIGN_IN_ADMIN,
-            "Open /admin/sections and open a section for edit.",
-            "Change its heading to 'QA Section Heading Probe' and save.",
-            "Reload the admin page and read the heading.",
-            "Sign out, open /, and find that section on the homepage.",
-            "Read its heading there.",
-            "Restore the original heading.",
-        ],
-        inputs: { heading: "QA Section Heading Probe" },
-        expectedBehaviour: "An edit persists and the public page follows. A handler that validates a body, returns success and never calls a write is the failure this checks for — the response echoes the submission back, so it is indistinguishable from a real save without a reload.",
-        expectedUiState: "The new heading is on the admin page after the reload and on the public homepage. A value that reverts is the finding despite the success message.",
-        endResult: "The original heading is restored.",
-    },
-    "checklist-admin-content-deletes-homepage-section-delete": {
-        roles: ["admin"],
-        startPage: "/admin/sections",
-        steps: [
-            SIGN_IN_ADMIN,
-            "Open /admin/sections and note the full order of sections.",
-            "Create a new section so the delete has a disposable target.",
-            "Note where it sits in the order.",
-            "Delete it and confirm.",
-            "Read the remaining sections and their order.",
-            "Open the public homepage and check the order matches and no gap is left.",
-        ],
-        expectedBehaviour: "Deleting a section removes it and leaves the rest in order. Ordering keyed on array position rather than on a stored order value shifts every later section by one on a delete, so the page silently reorders itself.",
-        expectedUiState: "The section is gone from both the admin list and the homepage, with the remaining sections in their original relative order and no empty band where it was.",
-        endResult: "Only the section this case created is gone.",
-    },
-    "checklist-admin-content-deletes-homepage-section-reorder": {
-        roles: ["admin"],
-        startPage: "/admin/sections",
-        steps: [
-            SIGN_IN_ADMIN,
-            "Open /admin/sections and write down the current order of the first four sections.",
-            "Move the third section above the first.",
-            "Save if a save is required.",
-            "Reload and read the order.",
-            "Open the public homepage and read the order there.",
-            "Restore the original order.",
-        ],
-        expectedBehaviour: "A reorder persists and the public page follows it. A reorder that holds in the admin list and not publicly means the order is being stored somewhere the public read does not consult.",
-        expectedUiState: "The new order survives the reload and matches on the public homepage. Agreement between the two is what makes the reorder real.",
-        endResult: "The original order is restored.",
-    },
-    "checklist-admin-content-deletes-homepage-section-disable-vs-delete": {
-        roles: ["admin"],
-        startPage: "/admin/sections",
-        steps: [
-            SIGN_IN_ADMIN,
-            "Open /admin/sections and disable a section rather than deleting it.",
-            "Sign out, open /, and check the section is gone from the homepage.",
-            "Return to the admin page and check the section is still listed, marked as disabled.",
-            "Re-enable it and check it returns publicly.",
-            "Read the two controls side by side and check which is which is obvious without trying them.",
-            "Check the delete control carries a confirmation and the disable control does not need one.",
-        ],
-        expectedBehaviour: "Disable hides a section reversibly; delete removes it permanently. The two must be visually distinct, because an admin wanting to hide a section for a week and reaching for the wrong one loses its whole configuration.",
-        expectedUiState: "A disabled section is absent publicly and still present, marked, in the admin list. The destructive control is visually distinct and confirms; the reversible one does not.",
-        endResult: "The section is re-enabled.",
-    },
-    "checklist-admin-content-deletes-carousel-slide-edit-persists": {
-        roles: ["admin"],
-        startPage: "/admin/carousel",
-        steps: [
-            SIGN_IN_ADMIN,
-            "Open /admin/carousel and open a slide for edit.",
-            "Change its title to 'QA Slide Title Probe' and change its autoplay delay.",
-            "Save.",
-            "Reload the admin page and read both values.",
-            "Open the public homepage and watch the carousel reach that slide.",
-            "Restore both original values.",
-        ],
-        inputs: { title: "QA Slide Title Probe" },
-        expectedBehaviour: "Both the content and the settings persist and reach the homepage. Settings are the half more likely to be dropped, because nothing on the admin screen shows whether an autoplay delay was actually written.",
-        expectedUiState: "Both values survive the reload and the homepage carousel reflects them. A title that saved while the delay reverted is the finding.",
-        endResult: "The original title and delay are restored.",
-    },
-    "checklist-admin-content-deletes-carousel-slide-delete": {
-        roles: ["admin"],
-        startPage: "/admin/carousel",
-        steps: [
-            SIGN_IN_ADMIN,
-            "Open /admin/carousel and create a slide titled 'QA Disposable Slide' so the delete has a safe target.",
-            "Activate it and check it appears on the homepage rotation.",
-            "Delete it and confirm.",
-            "Reload the admin list and check it is gone.",
-            "Open the public homepage and watch a full rotation.",
-            "Check the remaining slides still advance on their own.",
-        ],
-        inputs: { title: "QA Disposable Slide" },
-        expectedBehaviour: "Deleting a slide removes it from the rotation and the rest keep autoplaying. A rotation driven by an index into the old list stalls or throws on the removed position, and the carousel then simply stops — which reads as a design choice rather than a failure.",
-        expectedUiState: "The slide is gone from the admin list and from the rotation, and the remaining slides advance automatically through a full cycle.",
-        endResult: "Only the disposable slide is gone.",
-    },
-    "checklist-admin-content-deletes-carousel-active-limit-enforced": {
-        roles: ["admin"],
-        startPage: "/admin/carousel",
-        steps: [
-            SIGN_IN_ADMIN,
-            "Open /admin/carousel and write down which slides are active — five of the six seeded slides are, and one is inactive.",
-            "Read whether the page states a maximum anywhere.",
-            "Activate the sixth slide and save.",
-            "Read what happens: a refusal naming the maximum, or a successful save.",
-            "Reload /admin/carousel and count the active slides again.",
-            "Sign out, open /, and count the slides actually in the homepage rotation.",
-            "Sign back in and restore the original active set from step 2.",
-        ],
-        inputs: { maxActiveSlides: 5, seededSlides: 6 },
-        expectedBehaviour: "Exceeding the active-slide maximum should be refused with a reason. Silently accepting the extra slide and then rendering only the first few is worse than refusing — the admin sees their slide saved and never learns it is not being shown.",
-        expectedUiState: "🛑 EXPECT THE SAVE TO SUCCEED, AND RECORD IT AS A FAILURE. The limit is enforced in the appkit handlers mounted at /api/carousel, and the admin editor posts to /api/admin/carousel, whose `active` field is a bare optional boolean with no count check. So expect six active slides in the admin list and FIVE in the homepage rotation — the public read slices to five. Report both numbers; the gap between them is the finding, and it is exactly the saved-but-not-rendered slide this case names.",
-        expectedData: { activeSlidesInAdmin: 6, slidesOnHomepage: 5 },
-        endResult: "The original active set is restored, so the homepage rotates the same five slides as before.",
-    },
-    "checklist-admin-content-deletes-blog-edit-persists": {
-        roles: ["admin"],
-        startPage: "/admin/blog",
-        steps: [
-            SIGN_IN_ADMIN,
-            "Open /admin/blog and open blog-spot-genuine-takara-tomy-beyblade for edit, writing down its Slug.",
-            "Change its title to 'QA Blog Title Probe', edit a sentence of its body, and replace its cover image with /test-media/sample-image.png.",
-            "Save.",
-            "Reload the admin editor and check all three changes are there.",
-            "Sign out, open /blog/blog-spot-genuine-takara-tomy-beyblade, and check all three again.",
-            "Restore the original title, sentence and cover image.",
-        ],
-        inputs: { title: "QA Blog Title Probe", coverImage: "/test-media/sample-image.png" },
-        expectedBehaviour: "All three kinds of change persist together — a scalar field, rich body content and a media reference. Media is the one most often dropped on update: a create path that finalises a newly-uploaded file while the update path does not leaves the image in temporary storage, so it renders once and disappears later.",
-        expectedUiState: "Title, body and cover image all changed on both the editor and the public page. An image that renders immediately and is broken after a reload is the finalise failure.",
-        endResult: "All three original values are restored.",
-    },
-    "checklist-admin-content-deletes-blog-delete-removes-public-page": {
-        roles: ["admin"],
-        startPage: "/admin/blog",
-        steps: [
-            SIGN_IN_ADMIN,
-            "Open /admin/blog and create a post titled 'QA Disposable Post', publish it.",
-            "Open /blog/qa-disposable-post — the slug is the title slugified — and note that it renders.",
-            "Return to /admin/blog and delete it, confirming.",
-            "Reload the public URL with the network panel open.",
-            "Read the response status.",
-            "Open /blog and check the post is gone from the list.",
-        ],
-        inputs: { title: "QA Disposable Post" },
-        expectedBehaviour: "A deleted post's URL returns 404. A 200 carrying an empty article keeps the URL in search indexes indefinitely and shows visitors a page that looks broken rather than gone.",
-        expectedUiState: "The public URL returns 404 with a readable not-found page, and the post is absent from the blog list. A 200 with an empty article is the finding.",
-        expectedData: { statusCode: 404 },
-        endResult: "Only the disposable post is gone.",
-    },
-    "checklist-admin-content-deletes-blog-unpublish-vs-delete": {
-        roles: ["admin"],
-        startPage: "/admin/blog",
-        steps: [
-            SIGN_IN_ADMIN,
-            "Open /admin/blog and unpublish a post rather than deleting it.",
-            "Open /blog publicly and check it is absent from the list.",
-            "Open its public URL directly as a signed-out visitor and read what happens.",
-            "Return to /admin/blog and check the post is still listed and still editable.",
-            "Republish it and check it returns to the public list.",
-            "Read the two controls and check delete is visually distinct from unpublish.",
-        ],
-        expectedBehaviour: "Unpublishing hides a post reversibly and keeps it editable; deleting removes it. The controls have to look different, because the reversible and the irreversible action sit next to each other in the same menu.",
-        expectedUiState: "The unpublished post is absent publicly, still present and editable in admin, and returns on republish. The delete control is visually distinct and confirms.",
-        endResult: "The post is republished.",
-    },
-    "checklist-admin-content-deletes-listing-delete-removes-public-page": {
-        roles: ["admin"],
-        startPage: "/admin/products",
-        steps: [
-            SIGN_IN_ADMIN,
-            "Create a product titled 'QA Disposable Listing' priced at 299 and publish it.",
-            "Open its public detail page and note the URL, and find it in /products.",
-            "Return to /admin/products and delete it, confirming.",
-            "Reload the public URL with the network panel open and read the status.",
-            "Open /products and search for it.",
-            "Open /search and search for it there too.",
-        ],
-        inputs: { title: "QA Disposable Listing", price: 299 },
-        expectedBehaviour: "A deleted listing leaves every grid it appeared in, not only its own page. Search is the one most likely to lag, because its index is written on save — a listing removed from the collection but left in the index renders a result card that 404s when clicked.",
-        expectedUiState: "The detail URL returns 404 and the listing is absent from both the catalogue grid and search results. A search result that leads to a 404 is the finding.",
-        expectedData: { statusCode: 404 },
-        endResult: "Only the disposable listing is gone.",
-    },
-    "checklist-admin-content-deletes-listing-delete-with-orders-refused-or-archived": {
-        roles: ["admin"],
-        startPage: "/admin/products",
-        steps: [
-            SIGN_IN_ADMIN,
-            "Open /admin/orders, open any order, and write down its id and the exact title of one product it contains.",
-            "Open /admin/products, find that product, and delete it.",
-            "Read whether the interface refuses, warns about the order, or simply deletes.",
-            "Reload /admin/products and confirm whether the product is gone.",
-            "Reopen the order from step 2 and read whether its rows still render with that title and price.",
-            "Click the product link on the order's row and read exactly where it lands — a product page, a 404, or nothing.",
-            "Repeat the link check as the BUYER on /user/orders for the same order, since that is where a real person would meet it.",
-        ],
-        inputs: { deleteIsHard: true },
-        expectedBehaviour: "An order's rows denormalise the title, price and image they display, so an existing order survives the product's deletion — but the buyer's link into that product breaks. Either outcome can be defensible; what matters is that it is deliberate and stated rather than discovered by a buyer opening an old order.",
-        expectedUiState: "🛑 EXPECT A HARD DELETE. `adminDeleteProduct` checks only that a prize draw is not locked and then deletes the document; there is no order check anywhere, and no archive path. So expect no refusal and no warning. The order should still render its rows from the denormalised title and price — if it does NOT, that is a far more serious finding than the broken link. Record where the product link lands, on both the admin and the buyer surfaces.",
-        expectedData: { deleteRefused: false, orderRowsStillRender: true },
-        endResult: "A seeded product has been destroyed. `products` is seed-owned and is re-seeded around every run, so this is recoverable — but re-seed rather than attempting a manual repair, and do not run this case against a product another case in the same batch depends on.",
-        needsReview: true,
-        reviewNote: "What the code does is now settled — a hard delete with no order guard. What is NOT settled is whether that is the intended behaviour, so the case records the consequence for a real buyer rather than asserting a verdict on the design.",
-    },
-    "checklist-admin-content-deletes-delete-confirmations-name-the-record": {
-        roles: ["admin"],
-        startPage: "/admin/products",
-        steps: [
-            SIGN_IN_ADMIN,
-            "Open /admin/products and trigger a delete on a specific row.",
-            "Read the confirmation dialog WITHOUT confirming, and note whether it names that record.",
-            "Cancel.",
-            "Repeat on /admin/blog, /admin/carousel and /admin/categories.",
-            "Record any confirmation that says only 'this item' or 'are you sure'.",
-        ],
-        expectedBehaviour: "A delete confirmation names the record it will remove. A generic prompt gives an admin nothing to check against — the most common delete mistake is the right action on the wrong row, and only the name catches it.",
-        expectedUiState: "Each confirmation quotes the record's title or id. A generic prompt is a finding, named by surface.",
-        endResult: "Nothing is deleted.",
-    },
-    "checklist-admin-content-deletes-delete-reflected-immediately": {
-        roles: ["admin"],
-        startPage: "/admin/products",
-        steps: [
-            SIGN_IN_ADMIN,
-            "Create a product titled 'QA Delete Refresh Probe' priced at 199.",
-            "Delete it from the list and confirm.",
-            "WITHOUT reloading, read whether the row has gone.",
-            "Wait ten seconds and read the list again.",
-            "Reload and read it once more.",
-            "Open the list in a second tab and read it there.",
-        ],
-        inputs: { title: "QA Delete Refresh Probe", price: 199 },
-        expectedBehaviour: "The row goes immediately and stays gone. A row that returns after a moment means a cached copy re-hydrated over the deletion — the delete did happen, but the screen contradicts it, which is the worst possible signal to give somebody who just deleted something.",
-        expectedUiState: "The row is gone immediately, still gone after ten seconds, after a reload and in a second tab. A row that reappears at any point is the finding.",
-        endResult: "The probe product is deleted.",
-    },
-};

package/dist/features/tester/seed-data/authored/admin__content-marketing.d.ts

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