@mohasinac/appkit 4.34.0 → 4.35.0

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

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

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

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

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

@@ -0,0 +1,78 @@
+/*
+ * 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.
+ *
+ * @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! 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.",
+        ],
+        inputs: { title: "QA Classified admin-moderate", price: 900, city: "Pune" },
+        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.",
+    },
+    "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.",
+        ],
+        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.",
+    },
+    "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.",
+        ],
+        inputs: {
+            title: "QA Live Item admin-moderate",
+            price: 3000,
+            species: "Dog",
+            jurisdictions: "Maharashtra",
+        },
+        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.",
+    },
+};

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

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

package/dist/features/tester/seed-data/authored/admin__content-deletes.js

@@ -0,0 +1,261 @@
+/*
+ * 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.",
+            "Open the public homepage and find that section.",
+            "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.",
+            "Open the public homepage and check the section is gone from it.",
+            "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 count how many slides are currently active.",
+            "Read whether the page states a maximum.",
+            "Activate slides until you exceed that maximum.",
+            "Read what happens on the attempt that would exceed it.",
+            "Open the homepage and count the slides in the rotation.",
+            "Restore the original active set.",
+        ],
+        expectedBehaviour: "Exceeding the active-slide maximum is 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: "The attempt is refused with a message naming the maximum, and the homepage's rotation count matches the active count. A saved-but-not-rendered slide is the finding.",
+        endResult: "The original active set is restored.",
+    },
+    "checklist-admin-content-deletes-blog-edit-persists": {
+        roles: ["admin"],
+        startPage: "/admin/blog",
+        steps: [
+            SIGN_IN_ADMIN,
+            "Open /admin/blog and open a published post for edit.",
+            "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.",
+            "Open the post's public page 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 its public page and note the URL.",
+            "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 the search page 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 and find an order, noting one product it contains.",
+            "Open /admin/products and attempt to delete that product.",
+            "Read whether the interface refuses, warns, or deletes.",
+            "If it deletes, open that order and read whether its rows still render.",
+            "Click the product link on the order's row and read where it lands.",
+            "Record which of the three behaviours occurred.",
+        ],
+        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: "Record exactly what happened: a refusal naming the orders, an archive instead of a delete, or a hard delete. If it deleted, record whether the order still renders and where its product link goes.",
+        endResult: "If a product was hard-deleted, re-seed rather than attempting a manual repair.",
+        needsReview: true,
+        reviewNote: "The intended behaviour is not settled. The case exists to record which of refuse / archive / hard-delete actually happens, and what it does to an existing order.",
+    },
+    "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

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