@mohasinac/appkit 4.34.1 → 4.35.0

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

@@ -0,0 +1,263 @@
+/*
+ * 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 'Join the Community' button 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.",
+            "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 has a second smaller paragraph under its heading rather than a heading alone. The link is present and lands on /ethics.",
+        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.",
+            "Read every listing-type chip offered above the grid.",
+            "Read every card title on the first page, looking for anything containing 'Tester' or 'Test'.",
+            "Tick the Auctions chip and read the result count and the sort dropdown.",
+            "Tick Pre-Orders as well and read the sort dropdown again.",
+        ],
+        expectedBehaviour: "/products spans every listing type, so its type chips are a multi-select covering all nine — auctions, pre-orders, prize draws, art and stickers were unreachable from the main catalogue while only four chips were offered. The sort dropdown narrows to the options valid for every selected type, because a sort valid for one type alone would either no-op or fail the query for the others.",
+        expectedUiState: "Nine type chips are offered, ticking more than one is possible, and the Available / Sold & Ended / All tabs are present with Available selected. No card title contains 'Tester' or 'Test' for a signed-out visitor. With Auctions and Pre-Orders both ticked the sort dropdown offers only sorts that apply to both.",
+        expectedData: { listingTypeChipCount: 9 },
+        endResult: "Read-only; nothing persists. Four chips instead of nine is the specific regression this case exists for.",
+    },
+    "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-tester-sandbox 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 and a discount percentage. 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 category forest — two roots across four tiers — and every card links to a page that resolves. Products carry their full ancestor chain, so a category page matches on its own id alone and needs no descendant expansion.",
+        expectedUiState: "Both roots, Spinning Tops and Living Collectibles, are present. 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

@@ -0,0 +1,2 @@
+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

@@ -0,0 +1,102 @@
+/*
+ * 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: [
+            "Open /how-it-works/auctions in a private window and read its content.",
+            "Open /how-it-works/checkout and read its content.",
+            "Open /how-it-works/offers and read its content.",
+            "Open /how-it-works/orders and read its content.",
+            "Open /how-it-works/payouts and read its content.",
+            "Open /how-it-works/pre-orders and read its content.",
+            "Open /how-it-works/reviews 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.",
+            "Sign in as rehan.sheikh@gmail.com / TempPass123! and put live-golden-retriever-puppy in the cart.",
+            "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.",
+    },
+};

package/dist/features/tester/seed-data/authored/public-pages__help-scams-guides-subpages.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/public-pages__help-scams-guides-subpages.js

@@ -0,0 +1,234 @@
+/*
+ * WHY: Authored six-part procedures for the public-pages/help-scams-guides-subpages page.
+ * WHAT: 14 case(s), keyed by full checklist id.
+ *
+ * Eleven public routes the second sweep found with no case naming them anywhere.
+ * They were missed the first time because the first sweep only walked the
+ * dashboard trees — which is the reason to record the method here: the gap was in
+ * the MEASUREMENT, not in the writing, and a narrower sweep than the rule it feeds
+ * reports a smaller backlog than exists.
+ *
+ * 🛑 `/seller-guide` AND `/store/guide` ARE DIFFERENT ROUTE FAMILIES. The first is
+ * public marketing a prospective seller reads before signing up; the second is the
+ * signed-in seller's manual. An existing case covering the dashboard guides looked
+ * like coverage of both and is coverage of neither.
+ *
+ * @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-scams-guides-subpages-help-subpages-load": {
+        roles: ["guest"],
+        startPage: "/help",
+        steps: [
+            "Open /help signed out.",
+            "Open /help/account, /help/auctions, /help/orders and /help/shopping in turn.",
+            "Read each one's status in the network panel and the content it renders.",
+            "Record any that 404s or renders an empty shell.",
+            "Return to /help and check each of the four is linked from it.",
+        ],
+        expectedBehaviour: "All four load with real content and are reachable from the parent. A sub-page that exists but is linked from nowhere is unreachable to anyone who did not type the URL — which is every visitor.",
+        expectedUiState: "Four pages returning 200 with readable content, all four linked from /help. A 404, an empty shell, or a page with no inbound link is a finding, named.",
+        expectedData: { helpSubpagesNotFound: 0 },
+        endResult: "Read-only.",
+    },
+    "checklist-public-pages-help-scams-guides-subpages-help-subpages-linked-both-ways": {
+        roles: ["guest"],
+        startPage: "/help",
+        steps: [
+            "Open /help and note every link into a help sub-page.",
+            "Follow one and look for a way back to /help from it.",
+            "Use it and check the browser lands on /help.",
+            "Repeat on the other three sub-pages.",
+            "Check the site's own navigation or footer also offers a route into help.",
+        ],
+        expectedBehaviour: "Help navigates in both directions. A visitor who arrives on a sub-page from a search result has no context and no route onward unless the page carries one — and help is precisely where somebody arrives already stuck.",
+        expectedUiState: "Every sub-page offers a working route back to /help, and /help links forward to all four. A dead-end sub-page is the finding.",
+        endResult: "Read-only.",
+    },
+    "checklist-public-pages-help-scams-guides-subpages-help-subpage-content-matches-title": {
+        roles: ["guest"],
+        startPage: "/help",
+        steps: [
+            "Open /help/auctions and read its content.",
+            "Open /help/orders and read its content.",
+            "Compare the two.",
+            "Open /help/account and /help/shopping and read those.",
+            "Check none of the four repeats the parent page's text verbatim.",
+            "Check each answers questions about its own topic.",
+        ],
+        expectedBehaviour: "Each sub-page is about its own subject. Four routes rendering one shared body is a page family that was scaffolded and never filled — it loads, it links, and it answers nothing.",
+        expectedUiState: "Four distinct bodies, each on its own topic. Two or more sharing text is the finding, named by which pages.",
+        endResult: "Read-only.",
+    },
+    "checklist-public-pages-help-scams-guides-subpages-scams-types-page-loads": {
+        roles: ["guest"],
+        startPage: "/scams/types",
+        steps: [
+            "Open /scams/types and list every scam category it names.",
+            "Count them.",
+            "Open /scams/report and read the categories its own type field offers.",
+            "Compare the two lists.",
+            "Record any category on one and not the other.",
+        ],
+        expectedBehaviour: "The types page and the report form name the same categories. A page listing fewer teaches a reporter a vocabulary the form will not accept; a form offering more means categories nobody has explained. Either way the reporter picks the wrong one, and the registry's own filters then never surface their report.",
+        expectedUiState: "The two lists match. Any category present on one side only is the finding, named with which side it was missing from.",
+        expectedData: { categoriesOnlyOnOneSide: 0 },
+        endResult: "Read-only.",
+    },
+    "checklist-public-pages-help-scams-guides-subpages-scams-faqs-page-loads": {
+        roles: ["guest"],
+        startPage: "/scams/faqs",
+        steps: [
+            "Open /scams/faqs and count the questions listed.",
+            "Expand three of them and read the answers.",
+            "Check each answer is real prose rather than placeholder text.",
+            "Check the page states how to report a scam and links to the report form.",
+            "Read the console for errors.",
+        ],
+        expectedBehaviour: "The page carries real questions with real answers and routes onward to reporting. Somebody reading a scams FAQ is usually mid-incident, so the route to the report form is the most load-bearing link on the page.",
+        expectedUiState: "Several questions with substantive answers, a working link to /scams/report, and a clean console. An empty accordion is the finding.",
+        endResult: "Read-only.",
+    },
+    "checklist-public-pages-help-scams-guides-subpages-scams-report-form-submits": {
+        roles: ["guest", "buyer"],
+        startPage: "/scams/report",
+        steps: [
+            "Sign in as rehan.sheikh@gmail.com / TempPass123!.",
+            "Open /scams/report and fill every required field, using the description 'QA scam report probe — checklist case, please ignore.'",
+            "Pick a scam type from the list offered.",
+            "Submit the form.",
+            "Read what is shown afterwards.",
+            "Check the reporter is told what happens next rather than only that it was sent.",
+        ],
+        inputs: { description: "QA scam report probe — checklist case, please ignore." },
+        expectedBehaviour: "The form submits and tells the reporter what follows. A bare confirmation leaves somebody who has just been defrauded with no idea whether anyone will look, how long it takes, or what they should do meanwhile.",
+        expectedUiState: "A confirmation naming what happens next — review, timescale, or a reference. A bare 'Submitted' is a finding worth recording even though the submission worked.",
+        endResult: "One QA scam report exists; remove it if the admin surface allows.",
+    },
+    "checklist-public-pages-help-scams-guides-subpages-scams-report-errors-inline": {
+        roles: ["buyer"],
+        startPage: "/scams/report",
+        steps: [
+            "Sign in as rehan.sheikh@gmail.com / TempPass123!.",
+            "Open /scams/report and submit it completely empty.",
+            "Read where the errors appear.",
+            "Check each error is on its own field rather than in a single banner.",
+            "Fill one field and submit again, checking that field's error clears.",
+            "Check no server-side message leaks internal detail such as a file path or a stack.",
+        ],
+        expectedBehaviour: "Errors land on the fields they belong to, and a server-side failure is translated into a human message rather than passed through. A raw server message reaching a form is how a module-load failure with a full stack trace once rendered inside a bidding dialog.",
+        expectedUiState: "One inline error per empty required field, clearing as each is filled. A single banner is a finding; any file path, stack frame or internal identifier in a message is a more serious one.",
+        endResult: "Nothing is submitted.",
+    },
+    "checklist-public-pages-help-scams-guides-subpages-scams-report-reaches-admin": {
+        roles: ["buyer", "admin"],
+        startPage: "/scams/report",
+        steps: [
+            "Sign in as rehan.sheikh@gmail.com / TempPass123! and submit a report with the description 'QA scam report routing probe — checklist case.'",
+            "Sign in as admin@letitrip.in / TempPass123!.",
+            "Find that report in an admin surface.",
+            "Open it and read the description and the reporter.",
+            "Check it can be actioned — accepted, rejected or turned into a registry entry.",
+            "Remove the QA report if the interface allows.",
+        ],
+        inputs: { description: "QA scam report routing probe — checklist case." },
+        expectedBehaviour: "A submitted report reaches an admin who can act on it. A public form with no admin surface behind it is the worst half-built shape available — the reporter is told their report was received, and it goes nowhere.",
+        expectedUiState: "The report is visible to the admin with its description and reporter, and offers an action. A form with nothing behind it is the finding.",
+        endResult: "The QA report is removed if possible.",
+    },
+    "checklist-public-pages-help-scams-guides-subpages-scams-subpages-linked-from-registry": {
+        roles: ["guest"],
+        startPage: "/scams",
+        steps: [
+            "Open /scams signed out.",
+            "Look for links to the types page, the FAQ page and the report form.",
+            "Follow each and check it lands on the right page.",
+            "Return each time.",
+            "Record any of the three that is not linked from /scams.",
+        ],
+        expectedBehaviour: "The registry links to its own sub-pages. A visitor lands on /scams to check a name; if they recognise their own situation there, the report form has to be one click away rather than a URL they would have to guess.",
+        expectedUiState: "All three linked and all three resolving. An unlinked sub-page is a finding, named.",
+        expectedData: { unlinkedScamSubpages: 0 },
+        endResult: "Read-only.",
+    },
+    "checklist-public-pages-help-scams-guides-subpages-public-seller-guide-loads": {
+        roles: ["guest"],
+        startPage: "/seller-guide",
+        steps: [
+            "Open /seller-guide signed out and read its content.",
+            "Note whether it reads as marketing for prospective sellers or as a dashboard manual.",
+            "Sign in as tyson@beybladearena.in / TempPass123! and open /store/guide.",
+            "Read that content.",
+            "Compare the two.",
+            "Check neither is a copy of the other.",
+        ],
+        expectedBehaviour: "These are two different route families with two different audiences — a prospective seller who has not signed up, and a signed-in seller managing a store. An existing case covering the dashboard guides looked like coverage of both and was coverage of neither.",
+        expectedUiState: "Two distinct bodies aimed at two audiences. The public one being a copy of the dashboard manual, or requiring a sign-in, are both findings.",
+        endResult: "Read-only.",
+    },
+    "checklist-public-pages-help-scams-guides-subpages-public-seller-guide-subpages-load": {
+        roles: ["guest"],
+        startPage: "/seller-guide",
+        steps: [
+            "Open /seller-guide and look for links to its bundles and prize-draws pages.",
+            "Open /seller-guide/bundles and read its content and status.",
+            "Open /seller-guide/prize-draws and read the same.",
+            "Check both are linked from the parent.",
+            "Check each has a route back to /seller-guide.",
+        ],
+        expectedBehaviour: "Both sub-pages load and are reachable from the parent in both directions. They explain the two listing types a prospective seller is least likely to already understand, so an unlinked page is a page nobody reads.",
+        expectedUiState: "Both return 200 with real content, are linked from /seller-guide, and link back. A 404 or an unlinked page is a finding.",
+        endResult: "Read-only.",
+    },
+    "checklist-public-pages-help-scams-guides-subpages-public-seller-guide-matches-product": {
+        roles: ["guest", "seller"],
+        startPage: "/seller-guide",
+        steps: [
+            "Open /seller-guide/bundles and write down every claim it makes about how bundles work — pricing, membership, whether a buyer can pick.",
+            "Sign in as tyson@beybladearena.in / TempPass123! and create a bundle, reading what the editor actually offers.",
+            "Compare each claim against what the editor does.",
+            "Open /seller-guide/prize-draws and write down its claims.",
+            "Create a prize draw and compare in the same way.",
+            "Record every claim the product does not keep.",
+        ],
+        expectedBehaviour: "The guide describes the product as it is. A bundle is all-or-nothing and a buyer cannot pick its members — a guide implying otherwise is describing a grouped listing, which is a different feature with a different page. A prospective seller signs up for whichever one the guide described.",
+        expectedUiState: "Every claim on both pages is reproducible in the editor. Each unmet claim is a finding, quoted and paired with what actually happens.",
+        endResult: "Any bundle or prize draw created for this case is deleted.",
+    },
+    "checklist-public-pages-help-scams-guides-subpages-seller-guide-reachable-signed-out": {
+        roles: ["guest"],
+        startPage: "/",
+        steps: [
+            "Open the homepage in a private window with no session.",
+            "Find a route to the public seller guide without typing its URL — a navigation entry, a footer link, or a sell-with-us call to action.",
+            "Follow it and check it lands on /seller-guide.",
+            "Check no sign-in was demanded along the way.",
+            "Check the guide's own call to action leads to the become-a-seller flow.",
+        ],
+        expectedBehaviour: "A signed-out visitor can find and read the guide, then act on it. Gating the pitch behind a sign-in inverts the funnel — the page exists to persuade somebody who has not signed up yet.",
+        expectedUiState: "A discoverable route from the homepage, no sign-in demanded, and a call to action leading to the seller onboarding flow.",
+        endResult: "Read-only.",
+    },
+    "checklist-public-pages-help-scams-guides-subpages-item-requests-new-form-opens": {
+        roles: ["buyer"],
+        startPage: "/item-requests/new",
+        steps: [
+            "Sign in as rehan.sheikh@gmail.com / TempPass123!.",
+            "Open /item-requests/new directly by URL.",
+            "Check the form is already open rather than the page being blank.",
+            "Fill it with the title 'QA Item Request Probe' and a description naming this checklist case.",
+            "Submit it.",
+            "Read where the browser lands and check the request appears in /item-requests.",
+            "Reload and check it is still there, then remove it.",
+        ],
+        inputs: { title: "QA Item Request Probe" },
+        expectedBehaviour: "An editor that is also a page opens with its form showing, and a submitted request appears in the list. Reloading is the check that separates a stored request from one that only ever existed in the browser.",
+        expectedUiState: "The form is open on arrival, the request appears in /item-requests, and is still there after a reload. A blank page on arrival is the finding.",
+        endResult: "The QA item request is removed.",
+    },
+};

package/dist/features/tester/seed-data/authored/public-pages__legal-policy-pages.d.ts

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