@mohasinac/appkit 4.58.0 → 4.60.0

package/dist/features/tester/seed-data/authored/public-pages__core-listing-pages.js

@@ -1,263 +0,0 @@
-/*
- * WHY: Authored six-part procedures for the public-pages/core-listing-pages page.
- * WHAT: 16 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 the pages a crawler and a first-time visitor hit, so several cases
- * end by reading the page SOURCE rather than the rendered view — a canonical tag,
- * an embedded data payload and a leaked field are all invisible on screen.
- *
- * @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-public-pages-core-listing-pages-homepage-loads": {
-        roles: ["guest"],
-        startPage: "/",
-        steps: [
-            "Open / in a private window at a desktop width of 1280 pixels.",
-            "Scroll to the bottom, reading every section heading and checking each has content beneath it.",
-            "Write down any heading whose section is empty.",
-            "Resize the window to 390 pixels wide and reload /.",
-            "Scroll to the bottom again, reading the same sections.",
-            "Try to scroll the page sideways.",
-        ],
-        inputs: { desktopWidth: 1280, mobileWidth: 390 },
-        expectedBehaviour: "The homepage composes around 26 independently-fetched sections, each wrapped in its own boundary. A section that throws renders as nothing and is reported server-side rather than replacing the whole page — so the page surviving is not by itself proof that every section worked.",
-        expectedUiState: "At both widths the page renders end to end with no 'Something went wrong'. Every heading has content under it — a heading followed by an empty rail means that section's data fetch returned nothing, which is a different failure from the section being absent. Nothing scrolls sideways at 390px.",
-        expectedData: { emptySectionCount: 0 },
-        endResult: "Read-only; nothing persists. Note each empty section by name in the comment — 'the homepage loads' is true even when four sections are silently blank.",
-    },
-    "checklist-public-pages-core-listing-pages-whatsapp-community-link-real": {
-        roles: ["guest"],
-        startPage: "/",
-        steps: [
-            "Open / on a device or emulator with WhatsApp installed.",
-            "Find the WhatsApp community button — its default label is 'Join our WhatsApp community', not 'Join the Community' — and read the URL it points at.",
-            "Tap it and read what WhatsApp shows.",
-            "Open /contact and find its WhatsApp link.",
-            "Read that URL and compare it with the first.",
-        ],
-        expectedBehaviour: "The invite code resolves to a real group. A placeholder that is not a valid invite code still produces a link-shaped URL and a button that responds — WhatsApp simply reports that the group cannot be found, which reads as WhatsApp's problem rather than the site's.",
-        expectedUiState: "WhatsApp offers to join an actual named group rather than showing 'invalid link' or 'group not found'. The Contact page's link carries the same invite code as the homepage button — two different codes means one of them is stale.",
-        endResult: "Do not actually join the group. Read-only; nothing persists.",
-    },
-    "checklist-public-pages-core-listing-pages-about-us-in-main-nav": {
-        roles: ["guest"],
-        startPage: "/",
-        steps: [
-            "Open / in a private window at a desktop width.",
-            "Read every item in the main top navigation.",
-            "Click 'About Us' in that navigation and read where it lands.",
-            "Resize to 390 pixels wide, open the mobile navigation, and read its items.",
-        ],
-        expectedBehaviour: "About Us is a top-level navigation item, not footer-only. A page reachable only from the footer is a page most visitors never find.",
-        expectedUiState: "'About Us' appears in the main top navigation and lands on /about with content. It is present in the mobile navigation too — a desktop-only nav item is missing for most of the traffic.",
-        expectedData: { aboutHref: "/about" },
-        endResult: "Read-only; nothing persists.",
-    },
-    "checklist-public-pages-core-listing-pages-about-team-real-founder": {
-        roles: ["guest"],
-        startPage: "/about",
-        steps: [
-            "Open /about in a private window with no session.",
-            "Scroll to the \"Who's Behind LetItRip\" section.",
-            "Read the founder card's name and role.",
-            "Click the 'GitHub ↗' link on that card.",
-            "Read the profile it opens.",
-        ],
-        expectedBehaviour: "The team section is admin-editable content, and the founder card holds a real person with a working profile link. A fictional placeholder name renders identically to a real one, so only reading it catches this.",
-        expectedUiState: "The founder card shows a real name — not a seeded persona like 'Mock User' or a franchise character — and its 'GitHub ↗' link opens that person's actual GitHub profile rather than a 404 or the GitHub homepage.",
-        endResult: "Read-only; nothing persists.",
-    },
-    "checklist-public-pages-core-listing-pages-about-values-expanded": {
-        roles: ["guest"],
-        startPage: "/about",
-        steps: [
-            "Open /about in a private window with no session.",
-            "Scroll to the 'Our Values' section.",
-            "Count the values listed, and read whether each has a second smaller paragraph under its heading.",
-            "Read each one for a second, smaller paragraph beneath its heading.",
-            "Find the 'How we hold ourselves to this →' link and click it.",
-            "Read the address bar.",
-        ],
-        inputs: { expectedValueCount: 6 },
-        expectedBehaviour: "The section carries six values, each with a subtitle paragraph, and links onward to the Ethics page — where the commitments are actually detailed. Values with no onward link are a statement with nothing behind it.",
-        expectedUiState: "Six values are shown, not three, each with a second smaller paragraph under its heading, and the link lands on /ethics. 🛑 EXPECT THREE WITHOUT SUBTITLES ON A FRESHLY-SEEDED ENVIRONMENT, and record that as a CONTENT gap rather than a UI failure: appkit/src/seed/site-settings-seed-data.ts ships three valueItems and none of them carries a `detail` field, so it predates this expansion. aboutContent lives in siteSettings, which is PRESERVE-tier and never reseeded, so production holds whatever an admin last saved and may well show six. Report the count you actually see and which environment you saw it in — the link and the subtitle rendering are separately testable and the link should work either way.",
-        expectedData: { valueCount: 6, ethicsHref: "/ethics" },
-        endResult: "Read-only; nothing persists.",
-    },
-    "checklist-public-pages-core-listing-pages-developer-page-loads": {
-        roles: ["guest"],
-        startPage: "/developer",
-        steps: [
-            "Open / in a private window and scroll to the footer's Support column.",
-            "Find the Developer link, positioned next to About Us.",
-            "Click it and read the address bar.",
-            "Read the developer's name on the page.",
-            "Click the 'GitHub ↗' link and read the profile it opens.",
-        ],
-        expectedBehaviour: "The page exists, is reachable from the footer beside About Us, and names a real person with a working profile link — the same three requirements as the founder card, on a page of its own.",
-        expectedUiState: "The footer's Support column holds a Developer link next to About Us. It lands on /developer with real content. The name is a real developer's, and 'GitHub ↗' opens their actual profile.",
-        expectedData: { developerHref: "/developer" },
-        endResult: "Read-only; nothing persists.",
-    },
-    "checklist-public-pages-core-listing-pages-products-listing-page": {
-        roles: ["guest"],
-        startPage: "/products",
-        steps: [
-            "Open /products in a private window with no session.",
-            "Read the total result count and the availability tab bar.",
-            "Click 'Filters' and read every checkbox under the 'Listing type' heading.",
-            "Read every card title on the first page, looking for anything containing 'Tester' or 'Test'.",
-            "Read every badge on the first page of cards.",
-            "Tick 'Classifieds' and 'Digital Codes', click Apply, and read the sort dropdown.",
-        ],
-        expectedBehaviour: "/products is the GENERAL catalogue, not an index of everything. It spans the four listing types that have no entry of their own in the main nav — Standard, Classifieds, Digital Codes, Live Items — so each of those is still reachable from somewhere. Auctions, Pre-Orders, Prize Draws, Art and Stickers each own a dedicated page linked from the main nav and no longer appear here, so no item is reachable from two places with two different chromes. The sort dropdown narrows to the options valid for every selected type.",
-        expectedUiState: "BEFORE (the behaviour this replaced): nine type checkboxes, and the grid mixed cards badged 'Auction', 'Pre-Order' and 'Sticker Sheet' in among ordinary products. AFTER: exactly four checkboxes — Standard, Classifieds, Digital Codes, Live Items — and NO card on any page carries an 'Auction', 'Pre-Order', 'Prize Draw', 'Art Print' or 'Sticker Sheet' badge. The Available / Sold & Ended / All tabs are present with Available selected. No card title contains 'Tester' or 'Test' for a signed-out visitor.",
-        expectedData: { listingTypeChipCount: 4 },
-        endResult: "Read-only; nothing persists. An 'Auction' or 'Pre-Order' badge appearing in this grid is the specific regression this case exists for — those types belong on /auctions and /pre-orders.",
-    },
-    "checklist-public-pages-core-listing-pages-auctions-listing-page": {
-        roles: ["guest"],
-        startPage: "/auctions",
-        steps: [
-            "Open /auctions in a private window with no session.",
-            "Read the availability tab bar and note which tab is selected and what the middle one is called.",
-            "Read every card and check whether any shows an ended countdown.",
-            "Read the sort dropdown's default selection.",
-            "Click the middle availability tab and read the cards.",
-        ],
-        expectedBehaviour: "The default view shows auctions that are still live, and the middle tab is labelled for auctions specifically. An auction's end date is an inequality, which is why it is the one availability clause that carries its own sort field — pairing an inequality with an unrelated sort demands a composite index nobody declares, and the query then fails silently into an empty page.",
-        expectedUiState: "The tabs read Available / Ended / All, not 'Sold & Ended' — the label is derived per type. Available is selected and no card on it shows an ended countdown. The Ended tab shows the closed auctions, including the reserve-not-met one.",
-        expectedData: { middleTabLabel: "Ended" },
-        endResult: "Read-only; nothing persists. An empty Available tab with rows under All means the date filter failed rather than that nothing is live.",
-    },
-    "checklist-public-pages-core-listing-pages-preorders-listing-page": {
-        roles: ["guest"],
-        startPage: "/pre-orders",
-        steps: [
-            "Open /pre-orders in a private window with no session.",
-            "Read the sort dropdown's default selection.",
-            "Read the delivery dates on the cards from the top down.",
-            "Read the availability tabs and note the middle tab's label.",
-            "Click the middle tab and read the cards.",
-        ],
-        expectedBehaviour: "Pre-orders open sorted by earliest delivery first, which is the ordering a buyer waiting on stock cares about. Store tabs for the same type once carried a drifted local copy of this sort array and opened newest-first instead, for the same data.",
-        expectedUiState: "The sort dropdown shows earliest-delivery-first as the selection, and the dates on the cards ascend down the page. The middle availability tab reads 'Sold' rather than 'Ended'. The sold-out fixture appears under it, not under Available.",
-        endResult: "Read-only; nothing persists.",
-    },
-    "checklist-public-pages-core-listing-pages-bundles-listing-page": {
-        roles: ["guest"],
-        startPage: "/bundles",
-        steps: [
-            "Open /bundles in a private window with no session.",
-            "Read each bundle card's price and its discount badge.",
-            "Open bundle-original-collectors-set and read its price and its members.",
-            "Add up the members' individual prices and compare with the bundle price.",
-            "Read the page for anything containing 'Tester' or 'Test' while signed out.",
-        ],
-        inputs: { bundlePrice: 199, memberTotal: 348 },
-        expectedBehaviour: "A bundle is a category row with a locked price, deliberately below the sum of its members, and the discount badge is computed from the two. Its members are mirrored onto the bundle for index-friendly reads, and a reader that trusts only the mirror shows an empty bundle whenever a write path forgot to update it.",
-        expectedUiState: "Each card shows a price row and, when signed in, a discount percentage. Signed out the price row reads 'Sign in to see the bundle price' and NO discount percentage is shown — the percentage is derived from the bundle price and discloses it. Signed in, the sandbox bundle shows ₹199 against a members' total of ₹348. Its detail page lists both members with titles and images rather than reading '0 items'. No sandbox bundle is visible to a signed-out visitor.",
-        expectedData: { sandboxBundleVisibleToGuest: false },
-        endResult: "Read-only; nothing persists. A bundle rendering as empty is the mirror-drift failure, not a missing bundle.",
-    },
-    "checklist-public-pages-core-listing-pages-categories-index": {
-        roles: ["guest"],
-        startPage: "/categories",
-        steps: [
-            "Open /categories in a private window with no session.",
-            "Read every category card — its name, image and item count.",
-            "Note whether both root categories are present.",
-            "Click into one root category and read its page.",
-            "Go back and click a tier-3 category and read its page.",
-        ],
-        expectedBehaviour: "The index renders the SIX roots of the category forest — Spinning Tops, Trading Cards, Collectible Figures, Hot Wheels, Model Kits, Living Collectibles — and every card links to a page that resolves. It shows roots ONLY: the forest is 1,185 rows across five tiers (0-4) and the index used to render every one of them flat. Products carry their full ancestor chain, so a category page matches on its own id alone and needs no descendant expansion.",
-        expectedUiState: "All six roots are present, and NO tier-1-or-deeper category appears on the Categories tab. Every card shows a name and a count rather than a bare name. Both the root and the tier-3 page render with products rather than an empty grid.",
-        expectedData: { rootCategoryCount: 2 },
-        endResult: "Read-only; nothing persists. A root category page rendering blank with no error is the specific failure worth watching for — the query that produces it is wrapped in a catch that returns nothing.",
-    },
-    "checklist-public-pages-core-listing-pages-brands-index-detail": {
-        roles: ["guest"],
-        startPage: "/brands",
-        steps: [
-            "Open /brands in a private window with no session and read every brand card.",
-            "Open /brands/brand-beyblade.",
-            "Read the hero banner, the brand name and the 'About this brand' panel.",
-            "Read the panel for a website, a country and a founding year.",
-            "Read the product grid beneath and check the products belong to that brand.",
-        ],
-        inputs: { brandId: "brand-beyblade" },
-        expectedBehaviour: "Brands are category rows discriminated by type, not a separate collection. A brand page matches its products by DISPLAY NAME rather than by slug, so the brand's name and the brand string on every product must agree exactly — renaming a brand silently orphans its whole catalogue.",
-        expectedUiState: "The hero banner renders — it is driven by the cover image, which the admin editor labels 'Cover Image'. The 'About this brand' panel shows website, country and founding year rather than being absent. The grid holds Beyblade products rather than being empty.",
-        endResult: "Read-only; nothing persists. An empty grid on a brand with seeded products means the name and the product brand strings have drifted apart.",
-    },
-    "checklist-public-pages-core-listing-pages-category-item-counts-accurate": {
-        roles: ["guest"],
-        startPage: "/categories",
-        steps: [
-            "Open /categories in a private window with no session.",
-            "Write down the item count shown on three different category cards.",
-            "Open the first of those categories and count the products actually listed, paging to the end.",
-            "Repeat for the second and third.",
-            "Note any card whose count is zero.",
-        ],
-        expectedBehaviour: "A card's count is what the category page actually contains. A count that fails to compute must read as unknown, never as zero — a count map that returns undefined for an option is treated as 'unknown' and shown, while a zero hides the tab or card entirely, so a transient error would hide a category holding real stock.",
-        expectedUiState: "All three counts match the number of products on their pages. No card shows zero while its page holds products. A card showing a count and an empty page is the inverse failure and equally wrong.",
-        expectedData: { mismatchCount: 0 },
-        endResult: "Read-only; nothing persists.",
-    },
-    "checklist-public-pages-core-listing-pages-parent-category-includes-children": {
-        roles: ["guest"],
-        startPage: "/categories/category-beyblade-burst",
-        steps: [
-            "Open /categories/category-beyblade-burst in a private window and read its product count.",
-            "Write down the titles on the first page.",
-            "Open a child category of Burst — category-burst-tops — and write down its titles.",
-            "Go back to the parent and check whether the child's titles appear there too.",
-            "Open the root, /categories/category-spinning-tops, and read its count and titles.",
-        ],
-        inputs: { parentCategory: "category-beyblade-burst", childCategory: "category-burst-tops" },
-        expectedBehaviour: "Every product carries its full ancestor chain, so a parent page matches on its own id and picks up everything filed beneath it. This is why descendant expansion must NOT be reintroduced: the expansion list for a root exceeds the 30-value cap on the query it feeds, the query throws, and the caller's catch turns that into a blank page with no error anywhere.",
-        expectedUiState: "The parent page includes the child category's products, and its count reflects them. The root page includes products from every tier below it and is not empty.",
-        expectedData: { rootPageEmpty: false },
-        endResult: "Read-only; nothing persists. A blank root category page with populated children is exactly the cap-exceeded failure.",
-    },
-    "checklist-public-pages-core-listing-pages-category-brand-related-sections": {
-        roles: ["guest"],
-        startPage: "/categories/category-beyblade-burst",
-        steps: [
-            "Open /categories/category-beyblade-burst in a private window with no session.",
-            "Scroll to the 'Related Categories' section and read the cards.",
-            "Check whether Beyblade Burst itself is among them.",
-            "Open /brands/brand-beyblade and scroll to 'Related Brands'.",
-            "Read those cards and check whether Beyblade itself is among them.",
-        ],
-        expectedBehaviour: "Each page offers siblings sharing its root, with the current page filtered out. A self-link reads as a working suggestion and goes nowhere new, which is the same defect the policy pages' related-links list has.",
-        expectedUiState: "'Related Categories' lists other categories under the same root and does not include Beyblade Burst. 'Related Brands' lists other brands and does not include Beyblade. Each card carries a name and an image rather than an empty tile.",
-        expectedData: { selfLinkCount: 0 },
-        endResult: "Read-only; nothing persists.",
-    },
-    "checklist-public-pages-core-listing-pages-category-brand-highlights-faq-grouped-listings": {
-        roles: ["guest"],
-        startPage: "/categories/category-beyblade-burst",
-        steps: [
-            "Open /categories/category-beyblade-burst in a private window with no session.",
-            "Read the area immediately below the hero for a highlights list and an FAQ accordion.",
-            "Expand one FAQ entry and read its answer.",
-            "Scroll further and look for a grouped-listings carousel.",
-            "Open /brands/brand-beyblade and read the same three areas, plus the 'About this brand' panel.",
-        ],
-        expectedBehaviour: "Highlights and FAQs are editorial fields on the category row, rendered by one shared section on both category and brand pages. The section renders nothing at all when both arrays are empty, which is why a row with no editorial content shows no empty heading. The grouped-listings carousel is fed by its own collection scoped to the category or brand.",
-        expectedUiState: "Highlights appear as short bullets and the FAQ accordion expands to real answers. The grouped-listings carousel shows cards with titles and images. The brand page shows all of that plus website, country and founding year. An empty heading with nothing under it is a fail; the section absent entirely is correct when there is no content.",
-        endResult: "Read-only; nothing persists.",
-    },
-};

package/dist/features/tester/seed-data/authored/public-pages__help-how-it-works.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/public-pages__help-how-it-works.js

@@ -1,229 +0,0 @@
-/*
- * WHY: Authored six-part procedures for the public-pages/help-how-it-works page.
- * WHAT: 4 case(s), keyed by full checklist id.
- *
- * Written by hand, case by case, against the label each one states. There is no
- * generator: the authoring scripts were deleted once it was clear they were
- * scaffolding around work that is simply writing.
- *
- * "Loads correctly" is one honest step and one honest observation — but a page
- * that returns 200 while rendering an empty shell is the failure mode this
- * codebase actually has, so each case names something that must be ON the page
- * rather than asking whether it loaded.
- *
- * @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-public-pages-help-how-it-works-contact-page": {
-        roles: ["guest"],
-        startPage: "/contact",
-        steps: [
-            "Open /contact in a private window with no session.",
-            "Read the page for a form, contact details and any social or WhatsApp links.",
-            "Click Send with every field empty.",
-            "Read where the errors appear.",
-            "Type 'QA Contact contact-page' as the name, 'qa-contact@mailnull.com' as the email, 'Checklist submission' as the subject and 'Submitted by the tester checklist.' as the message.",
-            "Click Send.",
-        ],
-        inputs: {
-            name: "QA Contact contact-page",
-            email: "qa-contact@mailnull.com",
-            subject: "Checklist submission",
-            message: "Submitted by the tester checklist.",
-        },
-        expectedBehaviour: "The form validates in the browser against its schema and reports each problem on the field that caused it, then submits and is delivered. A contact form that 200s and delivers nothing is indistinguishable from a working one on screen, which is why the empty submit is checked first.",
-        expectedUiState: "The empty submit puts inline errors under the specific fields — not one banner and not a browser-native tooltip. The filled submit produces a visible confirmation, and the form clears or becomes read-only rather than sitting there inviting a second send.",
-        endResult: "A confirmation is shown. If a mailbox for the site's contact address is reachable, the message should arrive there; if it is not reachable, note that in the comment rather than assuming delivery.",
-    },
-    "checklist-public-pages-help-how-it-works-help-page": {
-        roles: ["guest"],
-        startPage: "/help",
-        steps: [
-            "Open /help in a private window with no session.",
-            "Read the page headings and the body content.",
-            "Click each link on the page in turn and read where it lands, going back each time.",
-        ],
-        expectedBehaviour: "The help page renders real content and every link on it resolves. It is one of the destinations the footer and sidebar support links point at, so a broken link here is reached from every page on the site.",
-        expectedUiState: "Headings and body text are present — not a bare chrome-and-spinner shell and not an empty container. Every link lands on a real page rather than a 404 or a silent redirect back to /.",
-        endResult: "Read-only; nothing persists.",
-    },
-    "checklist-public-pages-help-how-it-works-how-it-works-pages": {
-        roles: ["guest"],
-        startPage: "/help",
-        steps: [
-            /*
-             * 🛑 CORRECTED 2026-09-14. These seven steps named /how-it-works/<topic>,
-             * a route family that does not exist — every one was a 404, so the case
-             * could only ever be answered "no" for a reason that was not a product
-             * defect. The real routes are flat: /how-<topic>-work(s). That is also why
-             * these seven pages read as zero-coverage in a gap sweep despite having a
-             * case: the case pointed at nothing.
-             *
-             * audit-tester-checklist-hrefs did not catch it because it validates the
-             * `href` and `startPage` FIELDS, and these paths live inside step strings.
-             */
-            "Open /how-auctions-work in a private window and read its content.",
-            "Open /how-checkout-works and read its content.",
-            "Open /how-offers-work and read its content.",
-            "Open /how-orders-work and read its content.",
-            "Open /how-payouts-work and read its content.",
-            "Open /how-pre-orders-work and read its content.",
-            "Open /how-reviews-work and read its content.",
-            "Write down any of the seven that renders empty, 404s, or repeats another page's copy.",
-        ],
-        expectedBehaviour: "All seven guides render their own distinct copy. Sharing one renderer is correct; sharing one body of text is not — two guides with identical content means the page key is not reaching the content lookup.",
-        expectedUiState: "Each of the seven shows a heading and body specific to its topic. None is blank, none 404s, and no two are word-for-word the same.",
-        expectedData: { guidePageCount: 7 },
-        endResult: "Read-only; nothing persists. Name every failing page in the comment, not just the first.",
-    },
-    "checklist-public-pages-help-how-it-works-fees-page": {
-        roles: ["guest"],
-        startPage: "/fees",
-        steps: [
-            "Open /fees in a private window with no session.",
-            "Read every fee and percentage stated on the page.",
-            "Look specifically for a payout hold period, a minimum payout amount, a gateway fee percentage and any seller commission split.",
-        ],
-        expectedBehaviour: "The page explains what a BUYER pays. Seller-side and platform-internal figures — payout hold days, minimum payout, gateway fee, the seller share of an EMI surcharge — are not buyer-facing and have no reason to be on a public page. Those fields were being published by an unauthenticated settings endpoint for a long time, so this page is worth reading with that specifically in mind.",
-        expectedUiState: "Buyer-facing fees are stated: platform fee and its cap, COD handling, the add-on fees, GST. No payout hold period, minimum payout amount, gateway fee percentage or seller surcharge share appears anywhere on the page or in its source.",
-        expectedData: { sellerInternalFiguresShown: 0 },
-        endResult: "Read-only; nothing persists. Any seller-side figure found here is a projection leak, not a copy problem.",
-    },
-    "checklist-public-pages-help-how-it-works-how-emi-works-page": {
-        roles: ["guest"],
-        startPage: "/how-emi-works",
-        steps: [
-            "Open /how-emi-works signed out and read the whole page.",
-            "Write down the eligibility threshold it states and the worked example it gives.",
-            "Switch identity before continuing: this case is roles [guest] and the harness gives a guest batch NO session at all, so copy tester/.tester-runs/session-buyer.json over session.json and CLOSE THE BROWSER first — the MCP reads that file only at context creation. Then sign in as rehan.sheikh@gmail.com / TempPass123! and put live-golden-retriever-puppy in the cart. That fixture is priced at 25,000, comfortably over the seeded EMI minOrderValue of 10,000, so EMI should be offered; a cheaper item would show no EMI for the right reason and read as a failure.",
-            "Reach the payment step and read the instalment figures offered.",
-            "Compare them against the page's worked example.",
-            "Empty the cart, add product-beyblade-burst-valkyrie instead, and check EMI is NOT offered below the threshold.",
-        ],
-        inputs: { eligibleProduct: "live-golden-retriever-puppy", ineligibleProduct: "product-beyblade-burst-valkyrie" },
-        expectedBehaviour: "The page's threshold and worked example match what checkout does. This is the eighth how-it-works page and the only one describing money, so a stale figure here is a misstated charge rather than stale prose — and the aggregate case covering the family enumerates seven, which is why it needed its own.",
-        expectedUiState: "The stated threshold matches the price at which checkout starts offering EMI, and the worked example's instalment figures match the real ones. Either mismatch is a finding, with both numbers.",
-        endResult: "Empty the cart; place no order.",
-    },
-    /* ── Added 2026-09-14 (F3d) ──────────────────────────────────────────────────
-     * The blanket "how-it-works-pages" case above asserts all seven LOAD. These
-     * assert each one is TRUE: read the guide, then open the feature and compare.
-     * A guide is documentation with no compiler behind it, so nothing catches
-     * drift except doing both halves in one sitting — "it loads" passes against
-     * every stale sentence on the page.
-     */
-    "checklist-public-pages-help-how-it-works-how-auctions-work-matches-product": {
-        roles: ["guest"],
-        startPage: "/how-auctions-work",
-        steps: [
-            "Open /how-auctions-work signed out and read it end to end.",
-            "Write down what it says about the minimum bid increment, about bidding in the final minutes, and about what happens when a reserve is not met.",
-            "Open /auctions/auction-beyblade-original-dragoon-storm in a second tab.",
-            "Compare each of those three claims against what the auction page shows and what its bid form states.",
-        ],
-        expectedBehaviour: "Every claim the guide makes is true of the live auction: the increment it names is the increment the bid form enforces, the end-of-auction behaviour it describes is what the page shows, and an anti-snipe extension it promises actually exists.",
-        expectedUiState: "The guide renders its own headings and body text, not a placeholder. Each of the three claims matches. Quote verbatim any sentence that does not, next to what the auction page actually showed.",
-        endResult: "Read-only; nothing persists. Prices are gated signed out, so compare the RULES rather than the amounts. A mismatch is a real defect even though both pages load.",
-    },
-    "checklist-public-pages-help-how-it-works-how-checkout-works-matches-product": {
-        roles: ["buyer"],
-        startPage: "/how-checkout-works",
-        steps: [
-            "Sign in as rehan.sheikh@gmail.com / TempPass123!.",
-            "Open /how-checkout-works and write down the checkout steps it names, in order.",
-            "Add product-beyblade-burst-valkyrie to the cart and open /checkout.",
-            "Write down the steps checkout actually presents, in order.",
-            "Compare the two lists.",
-        ],
-        expectedBehaviour: "The guide names the same steps in the same order as the product: Address, then Add-ons and fees, then Payment. A guide still describing a two-step checkout sends a buyer looking for a screen that is not there; one that omits the add-ons step hides where the fees are chosen.",
-        expectedUiState: "The checkout step indicator shows three steps and the guide's list matches it. Any extra, missing or reordered step is quoted exactly from the guide.",
-        expectedData: { checkoutSteps: 3 },
-        endResult: "A cart line is left behind — remove it afterwards. Place no order. The guide itself is read-only.",
-    },
-    "checklist-public-pages-help-how-it-works-how-offers-work-matches-product": {
-        roles: ["buyer"],
-        startPage: "/how-offers-work",
-        steps: [
-            "Sign in as rehan.sheikh@gmail.com / TempPass123!.",
-            "Open /how-offers-work and write down what it says about how many counter-rounds are allowed and when an offer expires.",
-            "Open /products/product-beyblade-burst-valkyrie and open the Make-an-Offer form.",
-            "Read the limits and expiry the form itself states.",
-            "Compare them against the guide, then close the form without submitting.",
-        ],
-        expectedBehaviour: "The guide does not promise more counter-rounds than the product allows, and names the same expiry the offer actually gets. Over-promising here costs a buyer a negotiation they believed was still open.",
-        expectedUiState: "The offer form states its own limits. Every number in the guide matches a number the product enforces; any that does not is quoted from both places.",
-        endResult: "Do not submit the offer — cancel out of the form. Nothing persists.",
-    },
-    "checklist-public-pages-help-how-it-works-how-orders-work-matches-product": {
-        roles: ["buyer"],
-        startPage: "/how-orders-work",
-        steps: [
-            "Sign in as rehan.sheikh@gmail.com / TempPass123!.",
-            "Open /how-orders-work and list every order status it names.",
-            "Open /user/orders and list every status offered by the Active, Closed and All tabs and by the status filter.",
-            "Compare the two lists in both directions.",
-        ],
-        expectedBehaviour: "Every status the guide names is one an order can actually hold, and the guide omits none a buyer will see. A status that exists only in the guide teaches a vocabulary the product never uses.",
-        expectedUiState: "Both lists are written down and compared. Any status present in one and absent from the other is named explicitly, with which side it came from.",
-        endResult: "Read-only; nothing persists.",
-    },
-    "checklist-public-pages-help-how-it-works-how-payouts-work-matches-product": {
-        roles: ["seller"],
-        startPage: "/how-payouts-work",
-        steps: [
-            "Sign in as tyson@beybladearena.in / TempPass123!.",
-            "Open /how-payouts-work and write down the payout schedule and every deduction it names.",
-            "Open /store/payouts and read the schedule and deductions shown there.",
-            "Open one payout's detail and compare its deduction lines against the guide's list.",
-        ],
-        expectedBehaviour: "The schedule and the deductions match. This page describes money a seller is owed, so a stale figure is a seller expecting the wrong amount on the wrong day — not merely stale prose.",
-        expectedUiState: "Each deduction named in the guide appears on a real payout, and each deduction on the payout is explained by the guide. Mismatches are quoted with both numbers.",
-        endResult: "Read-only; nothing persists.",
-    },
-    "checklist-public-pages-help-how-it-works-how-pre-orders-work-matches-product": {
-        roles: ["guest"],
-        startPage: "/how-pre-orders-work",
-        steps: [
-            "Open /how-pre-orders-work signed out and write down what it says about the deposit and about whether a pre-order can be cancelled.",
-            "Open /pre-orders/preorder-beyblade-x-bx-08-wave.",
-            "Read what that listing states about its deposit terms and cancellability.",
-            "Compare the two.",
-        ],
-        expectedBehaviour: "The deposit wording and the cancellation rule match the listing. These are the two claims that drift, and both commit the buyer's money.",
-        expectedUiState: "The listing states deposit terms and a cancellation stance; the guide describes the same ones. Any difference is quoted from both pages.",
-        endResult: "Read-only; nothing persists. Prices are gated signed out, so compare the TERMS rather than the amounts.",
-    },
-    "checklist-public-pages-help-how-it-works-how-reviews-work-matches-product": {
-        roles: ["buyer"],
-        startPage: "/how-reviews-work",
-        steps: [
-            "Sign in as rehan.sheikh@gmail.com / TempPass123!.",
-            "Open /how-reviews-work and write down who it says may leave a review and when.",
-            "Open /products/product-beyblade-burst-valkyrie and try to leave a review.",
-            "Read what the form allows or refuses, and the reason it gives.",
-        ],
-        expectedBehaviour: "What the form enforces is what the guide describes. If the guide says only verified purchasers may review, the form refuses a non-purchaser and says so; if the form allows it anyway, the guide is wrong.",
-        expectedUiState: "Either the review form opens, or a refusal states its reason. That outcome matches the guide's sentence, which is quoted in the answer.",
-        endResult: "Do not submit a review. Nothing persists.",
-    },
-    "checklist-public-pages-help-how-it-works-track-order-page-works": {
-        roles: ["guest"],
-        startPage: "/track",
-        steps: [
-            "Open the site footer signed out and find the Support group.",
-            "Click the track-order link and note where it lands.",
-            "Type 9ab3f1-not-a-real-order into the tracking field and submit.",
-            "Note exactly what is shown.",
-            "Now submit the field left empty and note exactly what is shown.",
-        ],
-        inputs: { nonsenseOrderId: "9ab3f1-not-a-real-order" },
-        expectedBehaviour: "The footer link resolves to a real page, and a nonsense id produces a clear not-found outcome rather than a blank panel or a spinner that never resolves. The nonsense id is the control: a page answering the same way to everything is not looking anything up, and a tracking page that never fails is indistinguishable from one that never works.",
-        expectedUiState: "The page renders a tracking form. The nonsense id yields an explicit not-found message; the empty submit yields a field-level validation error rather than a silent no-op. Screenshot both outcomes.",
-        endResult: "Read-only; nothing persists. The id above is INVENTED and is expected not to resolve — that is the point of the control.",
-    },
-};

package/dist/features/tester/seed-data/authored/public-pages__help-scams-guides-subpages.d.ts

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