@mohasinac/appkit 4.57.0 → 4.59.0

package/dist/features/tester/seed-data/authored/content-discovery__overflowing-pill-rows.js

@@ -1,209 +0,0 @@
-/*
- * WHY: Authored six-part procedures for the content-discovery/overflowing-pill-rows page.
- * WHAT: 11 case(s), keyed by full checklist id.
- *
- * 🛑 WIDTH IS THE SUBJECT, SO EVERY CASE STATES ONE.
- *
- * These cases test a MEASUREMENT. A run that does not pin the viewport cannot
- * tell "collapsed because it did not fit" from "collapsed when it had room" —
- * and those are opposite defects with the same screenshot. Each case therefore
- * names an explicit width and the tester must set it before looking.
- *
- * The defect being guarded is silent by construction: an overflowing row
- * renders cleanly, returns 200, and puts its tail past the right edge with no
- * scrollbar and no arrow. Nothing errors, nothing logs. Measured on the report
- * that prompted this: 12 pills on a 1440px viewport, last four unreachable.
- *
- * FIXTURE: `category-original-attack-rings` — **87 direct children**, counted
- * from `_helpers/category-parts.ts`, and the node the reported screenshot came
- * from (Draciel F, Dragoon F, Dragoon Storm, Dranzer F, Dranzer S, Driger F,
- * Galeon, Galman, Galzzly, Griffolyon, Metal Draciel…).
- *
- * 🛑 It is chosen for being FAR past the threshold at every viewport, so these
- * cases cannot silently stop testing anything if the catalogue is regenerated
- * a little smaller. If it ever drops near a dozen, replace the fixture rather
- * than loosen the assertion — a row that fits proves nothing about a row that
- * does not. The first draft of this file invented an id that does not exist,
- * and `audit-tester-plugin-wiring` R7 caught it: a tester following a bad id
- * finds nothing and reports a bug that is really a typo (Root Cause #32).
- *
- * @tag domain:tester
- * @tag layer:seed
- * @tag pattern:none
- * @tag access:server-only
- * @tag consumers:seed-data/authored/index.ts
- * @tag sideEffects:none
- */
-/**
- * 87 direct children — collapses at EVERY viewport. Use for the search,
- * keyboard and reachability cases.
- */
-const CATEGORY = "/categories/category-original-attack-rings";
-/**
- * 5 direct children (the four generations plus Battle Gear) — fits a desktop
- * and overflows a phone, which is the only fixture that can prove the control
- * tracks WIDTH rather than just always collapsing.
- *
- * 🛑 Both fixtures are needed and neither is redundant. A suite that only ever
- * looked at the 87-child row would pass identically against an implementation
- * that collapsed unconditionally — the bug one size larger than the one being
- * fixed.
- */
-const SMALL_CATEGORY = "/categories/category-spinning-tops";
-export const authored = {
-    "checklist-content-discovery-overflowing-pill-rows-wide-row-stays-pills": {
-        roles: ["guest"],
-        startPage: SMALL_CATEGORY,
-        steps: [
-            "Set the browser window to 1440x900.",
-            `Open ${SMALL_CATEGORY}.`,
-            "Find the 'Subcategories' label and look at the row directly beneath it.",
-            "Count the pills and check whether any is cut off at the right edge.",
-        ],
-        expectedBehaviour: "The row is measured against its container, not counted. When the pills fit, they stay pills — collapsing a row that had room would hide items behind an extra click for no reason.",
-        expectedUiState: "A horizontal row of rounded pills under 'Subcategories', each reading a name and a number. Every pill is fully visible: none is clipped by the right edge and there is no horizontal scrollbar. There is NO single dropdown trigger.",
-        endResult: "Nothing persists; this is a read-only page. Reloading at the same width shows the same pill row.",
-    },
-    "checklist-content-discovery-overflowing-pill-rows-narrow-row-collapses": {
-        roles: ["guest"],
-        startPage: SMALL_CATEGORY,
-        steps: [
-            "Set the browser window to 390x844 (a phone width).",
-            `Open ${SMALL_CATEGORY}.`,
-            "Find the 'Subcategories' label and look at the control directly beneath it.",
-            "🛑 This is the SAME page as the previous case at a different width — that is the point. If it renders a dropdown here and pills there, the control is tracking width.",
-        ],
-        expectedBehaviour: "BEFORE: the pills simply ran past the right edge. There was no scrollbar, no arrow and no indication the row continued, so the subcategories beyond the fold were unreachable — the page looked complete while hiding items. AFTER: the row measures wider than the container and collapses to one trigger.",
-        expectedUiState: "A single bordered control reading 'Browse subcategories' followed by the total count and a chevron. The pill row is NOT present. Nothing is clipped at the right edge.",
-        endResult: "Nothing persists. Reloading at 390px wide shows the collapsed trigger again.",
-    },
-    "checklist-content-discovery-overflowing-pill-rows-collapsed-dropdown-is-searchable": {
-        roles: ["guest"],
-        startPage: CATEGORY,
-        steps: [
-            "Set the browser window to 390x844.",
-            `Open ${CATEGORY}.`,
-            "Click the 'Browse subcategories' trigger.",
-            "Read the full list of rows offered.",
-            "Type drag into the search box.",
-            "Read the list again.",
-            "Clear the search box.",
-        ],
-        inputs: { search: "drag" },
-        expectedBehaviour: "BEFORE: the collapsed control was a native <select>, which cannot be typed at — a 12-row picker had to be scrolled. AFTER: the dropdown opens with a focused search box that filters the list on every keystroke, case-insensitively, matching anywhere in the name rather than only the start.",
-        expectedUiState: "A panel containing a search field and a scrollable list. With 'drag' typed, only rows whose name contains 'drag' remain (e.g. 'Dragoon F', 'Dragoon Storm') and non-matching rows such as 'Draciel F' are gone. Clearing the box restores the full list.",
-        endResult: "Nothing persists. Closing and reopening the dropdown shows an empty search box and the full list.",
-    },
-    "checklist-content-discovery-overflowing-pill-rows-collapsed-dropdown-keyboard": {
-        roles: ["guest"],
-        startPage: CATEGORY,
-        steps: [
-            "Set the browser window to 390x844.",
-            `Open ${CATEGORY}.`,
-            "Click the 'Browse subcategories' trigger.",
-            "Press ArrowDown three times without touching the mouse.",
-            "Note which row is highlighted.",
-            "Press Enter.",
-        ],
-        expectedBehaviour: "The search box keeps focus and the arrow keys move a highlight through the filtered list, wrapping at the ends. Enter opens the highlighted subcategory. Escape closes the panel and returns focus to the trigger. The highlight is the same one the mouse sets, so there are never two cursors in the list.",
-        expectedUiState: "After three ArrowDowns the third row is visibly highlighted and no other row is. After Enter the browser is on that subcategory's own page, whose heading matches the row that was highlighted.",
-        endResult: "The navigation is real: the URL is the chosen subcategory's and reloading stays there.",
-    },
-    "checklist-content-discovery-overflowing-pill-rows-every-item-reachable-when-collapsed": {
-        roles: ["guest"],
-        startPage: SMALL_CATEGORY,
-        steps: [
-            "Set the browser window to 1440x900.",
-            `Open ${SMALL_CATEGORY}.`,
-            "Write down the name of the LAST pill visible in the Subcategories row.",
-            "Resize the window to 390x844.",
-            "Click 'Browse subcategories' and scroll the list to the bottom.",
-            "Compare the list against the names seen at the wide width.",
-        ],
-        expectedBehaviour: "BEFORE: items past the right edge existed in the DOM but had no affordance — no scrollbar, no arrow — so they could not be reached at all at a narrow width. AFTER: the collapsed list contains EVERY direct child, including the ones that used to be cut off.",
-        expectedUiState: "The dropdown list is scrollable and its row count equals the number shown on the trigger. Every pill name seen at 1440px appears as a row, and so do the ones that were clipped.",
-        endResult: "Nothing persists. The list contents are the same on every open.",
-    },
-    "checklist-content-discovery-overflowing-pill-rows-pills-carry-a-leading-image": {
-        roles: ["guest"],
-        startPage: SMALL_CATEGORY,
-        steps: [
-            "Set the browser window to 1440x900.",
-            `Open ${SMALL_CATEGORY}.`,
-            "Look at the left-hand side of each pill in the Subcategories row.",
-            "Resize to 390x844 and open 'Browse subcategories'.",
-            "Look at the left-hand side of each row in the list.",
-        ],
-        expectedBehaviour: "A subcategory's cover image is shown as a small leading thumbnail so the row can be scanned by sight rather than by reading every label. The SAME visual appears in both states — a pill and its dropdown row are the same item and must not look like different things.",
-        expectedUiState: "Each pill shows a small square image immediately left of its name, at roughly text height, without making the pill taller than it was. The dropdown rows show the same images. No image is stretched or letterboxed.",
-        endResult: "Nothing persists. The same images appear on reload.",
-    },
-    "checklist-content-discovery-overflowing-pill-rows-missing-image-falls-back-to-initial": {
-        roles: ["guest"],
-        startPage: "/categories/category-spinning-tops",
-        steps: [
-            "Set the browser window to 1440x900.",
-            "Open /categories/category-spinning-tops.",
-            "Look at the Subcategories row for any entry whose category has no cover image.",
-            "Check what is drawn where the thumbnail would be.",
-        ],
-        expectedBehaviour: "Roughly 650 of the intermediate branch categories have neither an icon nor a cover image, so the fallback is the common case rather than an edge case. It must be a drawn initial, never an empty reserved box and never a broken-image glyph — a blank square reads as a failed load and invites a bug report against working code.",
-        expectedUiState: "A pill with no cover shows a small circle containing the first letter of its name. There is no broken-image icon anywhere in the row, and the pills all sit on the same baseline with equal height whether or not they have an image.",
-        endResult: "Nothing persists.",
-    },
-    "checklist-content-discovery-overflowing-pill-rows-widening-restores-the-pills": {
-        roles: ["guest"],
-        startPage: CATEGORY,
-        steps: [
-            "Set the browser window to 390x844.",
-            `Open ${SMALL_CATEGORY} and confirm the Subcategories control is a single dropdown trigger.`,
-            "Without reloading, resize the window back to 1440x900.",
-            "Look at the Subcategories area again.",
-            "Resize back down to 390 and up to 1440 twice more, watching for flicker.",
-        ],
-        expectedBehaviour: "🛑 This is the case most likely to fail. Collapsing REMOVES the row, so there is nothing left to measure and a naive implementation can never expand again — a one-way door that looks correct until someone widens the window. The row's natural width is cached while it is still rendered, and expanding requires a clear margin above that width rather than an exact fit, so the two states cannot oscillate at the boundary.",
-        expectedUiState: "At 1440px the pill row is back and the dropdown trigger is gone. During the resize the control does not flicker, alternate, or rapidly toggle between the two states at any intermediate width.",
-        endResult: "Nothing persists. The state always matches the current width, not the width the page loaded at.",
-    },
-    "checklist-content-discovery-overflowing-pill-rows-subcategory-click-is-client-side": {
-        roles: ["guest"],
-        startPage: SMALL_CATEGORY,
-        steps: [
-            "Set the browser window to 1440x900.",
-            `Open ${SMALL_CATEGORY}.`,
-            "Open the browser devtools Network tab and clear it.",
-            "Click any subcategory pill.",
-            "Look at whether the page performed a full document navigation.",
-        ],
-        expectedBehaviour: "Subcategory pills are client-side links, not plain anchors. A plain <a> would make every click re-download the whole document — a silent performance regression that looks identical to working navigation apart from the flash.",
-        expectedUiState: "The destination category page renders. The page does not white-flash, and the Network tab shows an RSC payload fetch rather than a full document request for the destination HTML.",
-        endResult: "The URL is the clicked subcategory's; going Back returns to the previous category with its row intact.",
-    },
-    "checklist-content-discovery-overflowing-pill-rows-tabs-collapse-by-width-not-count": {
-        roles: ["guest"],
-        startPage: SMALL_CATEGORY,
-        steps: [
-            "Set the browser window to 1440x900.",
-            `Open ${SMALL_CATEGORY} and scroll to the Products / Auctions / Pre-Orders tab bar.`,
-            "Count the tabs and check whether they render as a row or a dropdown.",
-            "Resize to 390x844 and look at the same tab bar.",
-        ],
-        expectedBehaviour: "BEFORE: the tab bar collapsed whenever it had more than five tabs, regardless of width — so six short tabs became a dropdown on a 1440px desktop with room to spare, while four long ones stayed a row on a phone and overflowed. AFTER: the decision is the measured width of the rendered row against its container, so the same bar can be a row on desktop and a dropdown on a phone.",
-        expectedUiState: "At 1440px the tabs render as a horizontal row with the underline rail on the active one, even when there are six or more. At 390px the same bar is a single dropdown trigger. The resting appearance of the expanded row is unchanged from before — still an underline rail, not pills.",
-        endResult: "Nothing persists. The tab bar's form follows the current width on every render.",
-    },
-    "checklist-content-discovery-overflowing-pill-rows-event-tabs-do-not-jump-to-top": {
-        roles: ["guest"],
-        startPage: "/events",
-        steps: [
-            "Set the browser window to 1440x900.",
-            "Open /events and click into any event with an Overview / Participate / Leaderboard tab bar.",
-            "Scroll down until the tab bar is near the top of the viewport.",
-            "Click a different tab.",
-            "Note the scroll position immediately after the panel swaps.",
-        ],
-        expectedBehaviour: "The app mounts a global ScrollToTop keyed on pathname, so a tab that navigates must opt out explicitly or every switch yanks the page to the top. The tab bar passes that opt-out through to its links.",
-        expectedUiState: "After clicking, the newly selected tab is active and its panel is shown, while the page stays at roughly the scroll position it was at — the tab bar does not leap back down the screen.",
-        endResult: "The URL is the new tab's; reloading lands on that tab.",
-    },
-};

package/dist/features/tester/seed-data/authored/content-discovery__parts-database.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/content-discovery__parts-database.js

@@ -1,167 +0,0 @@
-/*
- * WHY: Authored six-part procedures for content-discovery/parts-database.
- * WHAT: 9 cases, keyed by full checklist id.
- *
- * 🛑 EVERY CASE HERE IS WRITTEN AS BEFORE → AFTER, because every defect this
- * feature has already produced returned HTTP 200 with plausible content. A case
- * reading "check the parts page works" passes against all four of them:
- *
- *   1. `getCompositionsForCategory` first queried a `searchTxt` field that
- *      `modelComposition` does not have. Zero rows, no error, an empty panel
- *      that reads as "no composition recorded".
- *   2. The composition `name` was a FILE PATH for all 259 rows, so the
- *      category join matched 0 of 259 — and a model page with no panel is
- *      indistinguishable from a model we have no data for.
- *   3. Without the paren-stripped fallback the join reached only 150 of 259,
- *      and HMS models in particular silently had no panel.
- *   4. 🛑 The one live listing whose leaf has a composition is an ART POSTER,
- *      so before `LISTING_TYPE_HAS_COMPOSITION` the only Parts tab in the
- *      catalogue offered a poster an attack ring and a blade base — a correct
- *      part list for the wrong kind of object.
- *
- * So each case below names what the WRONG answer looked like, and several
- * compare two surfaces that must agree rather than checking that something
- * rendered.
- *
- * @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-content-discovery-parts-database-index-lists-every-classification": {
-        roles: ["guest"],
-        startPage: "/parts",
-        steps: [
-            "Open /parts.",
-            "Confirm the page heading reads 'Beyblade parts gallery'.",
-            "Count the classification tiles.",
-            "Confirm every tile reads as a part NAME in sentence case — 'Performance Tip', 'Fusion Wheel', 'Bit Chip' — and not as a URL slug like 'performance-tip' or 'bit-chip'.",
-            "Open any one tile and confirm it loads a page rather than 404ing.",
-        ],
-        expectedBehaviour: "BEFORE: there was no parts reference at all, so a buyer reading '105RF' on a listing had nowhere to learn that 105 is a spin-track height and RF is a rubber flat tip. AFTER: 20 classifications, each a real page, under the heading 'Beyblade parts gallery'. The labels come from a compile-checked map rather than being title-cased from the slug, because 'Bit Chip' is not 'bit-chip' title-cased and 'Armour' is not 'armour'.",
-        expectedUiState: "The heading reads 'Beyblade parts gallery'. Exactly 20 tiles, each labelled in sentence case, each a working link.",
-        expectedData: { classificationTiles: 20 },
-        endResult: "Nothing is changed; this case only reads.",
-    },
-    "checklist-content-discovery-parts-database-index-shows-no-fabricated-counts": {
-        roles: ["guest"],
-        startPage: "/parts",
-        steps: [
-            "Open /parts.",
-            "Look at each classification tile and confirm NO tile shows a number of parts.",
-            "Answer no if any tile shows a count, including a zero.",
-        ],
-        expectedBehaviour: "A per-classification count on this page would be 20 queries or a 753-document scan on a page that exists only to route — against a ~3-round-trip budget per render. The honest version of 'we are not going to pay for that number' is to not show a number, rather than to show a stale or a zero one.",
-        expectedUiState: "Tiles carry a label and a link, and no count.",
-        expectedData: { tileShowsCount: false },
-        endResult: "Nothing is changed; this case only reads.",
-    },
-    "checklist-content-discovery-parts-database-classification-page-lists-its-parts": {
-        roles: ["guest"],
-        startPage: "/parts",
-        steps: [
-            "Open /parts, then open the Performance Tip tile.",
-            "Read the count in the line under the heading.",
-            "Count the rows listed.",
-            "Confirm the rows are in alphabetical order by part name.",
-            "Confirm a part that has a recorded weight shows it as '(N g)' and a part with no recorded weight shows nothing in its place — not '0 g' and not an em-dash.",
-        ],
-        expectedBehaviour: "The count is a promise about the list directly beneath it, so the two must agree exactly. Only 98 of 753 parts carry a weight and only 23 carry a code; both are facts about our sources rather than missing data, so an absent one renders as nothing at all. A '0 g' would be a measurement we never took.",
-        expectedUiState: "The stated count equals the number of rows. Rows are alphabetical. Weights appear only where recorded.",
-        expectedData: { statedCountEqualsRowCount: true },
-        endResult: "Nothing is changed; this case only reads.",
-    },
-    "checklist-content-discovery-parts-database-unknown-classification-404s": {
-        roles: ["guest"],
-        startPage: "/parts",
-        steps: [
-            "Open /parts, then edit the address bar to /parts/zzzznope and load it.",
-            "Confirm you get a 404 page.",
-            "Then go back to /parts and open the Performance Tip tile as a positive control, and confirm it loads with rows.",
-            "Answer no if /parts/zzzznope renders an EMPTY classification page instead of 404ing.",
-        ],
-        expectedBehaviour: "BEFORE the guard existed, casting a URL segment to a slot type would have made this a perfectly successful query for a classification no document has: zero rows, HTTP 200, and a page reading 'No parts recorded in this classification yet' — which is a lie about our data rather than a statement about the URL. The positive control is what distinguishes a working 404 from a page that 404s on everything.",
-        expectedUiState: "/parts/zzzznope is a 404. /parts/performance-tip loads and lists parts.",
-        expectedData: { unknownSegment404s: true, knownSegmentLoads: true },
-        endResult: "Nothing is changed; this case only reads.",
-    },
-    "checklist-content-discovery-parts-database-part-page-shows-which-models-use-it": {
-        roles: ["guest"],
-        startPage: "/parts",
-        steps: [
-            "Open /parts, then open Disc, then open the part named Sting.",
-            "Read the 'Used by N models' heading.",
-            "Count the model rows beneath it.",
-            "Click one model row and confirm it opens that model's category page.",
-            "Confirm any model row that is NOT a link is still readable as plain text rather than rendering as a broken link.",
-        ],
-        expectedBehaviour: "'Which beys use this part' is the single most useful thing a part page says and the reason the glossary is a collection rather than a lookup table. 210 of 259 compositions joined to a category, so a model that did not join renders as plain text — a link to a page that does not exist is worse than no link.",
-        expectedUiState: "The heading count equals the number of rows. Linked models open their category page; unlinked models render as text.",
-        expectedData: { headingCountEqualsRowCount: true },
-        endResult: "Nothing is changed; this case only reads.",
-    },
-    "checklist-content-discovery-parts-database-part-page-shows-no-prices": {
-        roles: ["guest"],
-        startPage: "/parts",
-        steps: [
-            "Open /parts, then Disc, then Sting.",
-            "Read the Listings section.",
-            "Confirm NO row shows a rupee amount.",
-            "Confirm no row shows 'Sign in to see price' either.",
-            "Click 'Search the catalogue' or 'See all listings' and confirm it lands on /products with a search term.",
-        ],
-        expectedBehaviour: "Prices are withheld from signed-out visitors, so an amount here would need the price gate and would make this a client-rendered page. A row carrying a title, a condition and a link has nothing to gate and therefore nothing to leak — which is why there is no 'Sign in to see price' placeholder either. The price lives one click away on the listing, where the gate already is.",
-        expectedUiState: "Listing rows show a title and optionally a condition. No rupee amounts, no sign-in-to-see-price text.",
-        expectedData: { pricesOnPartPage: false },
-        endResult: "Nothing is changed; this case only reads.",
-    },
-    "checklist-content-discovery-parts-database-model-page-shows-its-composition": {
-        roles: ["guest"],
-        startPage: "/categories/category-ace-dragon-sting-charge-zan",
-        steps: [
-            "Open /categories/category-ace-dragon-sting-charge-zan — a tier-4 named-model leaf. Every category id carries the `category-` prefix and a URL without it does not resolve.",
-            "Find the 'What it is made of' section.",
-            "Confirm it lists at least one slot row, each reading as a part classification on the left and a part name on the right.",
-            "Click a part name and confirm it opens that part's page under /parts/.",
-            "Then open /categories/category-burst-gt — the generation LINE one level up — and confirm it has NO 'What it is made of' section at all.",
-        ],
-        expectedBehaviour: "BEFORE: the panel showed nothing on every model, twice over — the read queried a field the collection does not have, and separately every composition's name was a file path so none of them joined to a category. Both failures rendered as an absent section, which is indistinguishable from a model we have no data for. AFTER: the leaf shows its parts and each one links out. The LINE shows nothing deliberately — 'Burst GT' is not made of parts, the beys under it are.",
-        expectedUiState: "The model leaf shows a composition with linked part names. The line above it shows no composition section.",
-        expectedData: { leafHasPanel: true, lineHasPanel: false },
-        endResult: "Nothing is changed; this case only reads.",
-    },
-    "checklist-content-discovery-parts-database-art-listing-has-no-parts-tab": {
-        roles: ["guest"],
-        startPage: "/products/art-dranzer-phoenix-poster",
-        steps: [
-            "Open /products/art-dranzer-phoenix-poster — an art print filed under the Dranzer F model leaf.",
-            "Read the tab strip above the description.",
-            "Confirm there is NO 'Parts' tab.",
-            "Answer no if a Parts tab appears listing an attack ring, a weight disk or a blade base.",
-        ],
-        expectedBehaviour: "BEFORE: this was the ONLY listing in the catalogue that satisfied every other condition, so the one Parts tab in the whole product catalogue offered a poster an attack ring and a blade base. It rendered a correct part list for the wrong kind of object, with no error anywhere. AFTER: a print, a sticker sheet and a redemption code are excluded by type. They file under the model's leaf on purpose — a sticker sheet belongs beside the bey it is for — and none of them is made of its parts.",
-        expectedUiState: "No Parts tab on an art listing.",
-        expectedData: { partsTabOnArtListing: false },
-        endResult: "Nothing is changed; this case only reads.",
-    },
-    "checklist-content-discovery-parts-database-seller-description-lists-parts": {
-        roles: ["seller"],
-        startPage: "/store/products/new",
-        steps: [
-            "Open /store/products/new and enter any title.",
-            "Pick the category category-ace-dragon-sting-charge-zan, a Burst GT named-model leaf.",
-            "Set the condition to Used.",
-            "Wait for the template picker to fill the Description field.",
-            "Read the filled description and confirm it contains a 'Parts:' line naming at least one real part.",
-            "Now change the category to category-pokemon-set-151 — a real trading-card expansion-set leaf, which has no parts — and confirm the refilled description contains NO 'Parts:' line at all.",
-            "Answer no if the second description shows an EMPTY 'Parts:' line.",
-        ],
-        expectedBehaviour: "A listing filed under a named model can state what the bey is made of, from the same data the model page renders. The second half is the half that matters: an unfilled slot resolves to an empty string, so a shared template would render an empty 'Parts:' bullet on every listing in the catalogue that is not a Beyblade. The line is REMOVED rather than emptied — absent data must read as absent, not as blank.",
-        expectedUiState: "The Beyblade description carries a Parts line naming real parts. The trading-card description has no Parts line and no empty bullet.",
-        expectedData: { partsLineOnModelLeaf: true, emptyPartsLineElsewhere: false },
-        endResult: "Nothing is saved — the draft is abandoned without publishing, so no listing is created.",
-    },
-};

package/dist/features/tester/seed-data/authored/content-discovery__price-index-and-compare.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/content-discovery__price-index-and-compare.js

@@ -1,73 +0,0 @@
-/*
- * WHY: Authored six-part procedures for the two Wave-11 adoptions —
- *      price-index local resolution and the compare overlay's new
- *      "add another" typeahead.
- * WHAT: 4 case(s), keyed by full checklist id.
- *
- * @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-content-discovery-price-index-tool-price-index-resolves-locally": {
-        roles: ["guest"],
-        startPage: "/tools/price-index",
-        steps: [
-            "Open /tools/price-index in a private window and open DevTools → Network.",
-            "Clear the network log.",
-            "Type a real model name into the search box and submit.",
-            "Read the network log for what fired.",
-            "Read the results on the page.",
-        ],
-        inputs: { query: "Dragoon G" },
-        expectedBehaviour: "The query-to-leaf resolution step runs in the browser against the local search artifact, at zero Firestore reads — before this, it was a searchTxt push-down query on every submit. The server is now asked only for the sale bands of the already-resolved id(s).",
-        expectedUiState: "The network log shows the one-time artifact fetch (a .json, if not already cached from an earlier visit) plus exactly one request to a bands endpoint carrying resolved id(s) — not a raw free-text query parameter. The page shows real min/median/mean/max figures for a model with recorded sales.",
-        endResult: "Read-only; nothing persists.",
-    },
-    "checklist-content-discovery-price-index-tool-price-index-falls-back-when-index-off": {
-        roles: ["admin"],
-        startPage: "/tools/price-index",
-        steps: [
-            "Sign in as admin and flip siteSettings.search.indexEnabled to false (via Firestore console or an admin settings surface, if one exists for it).",
-            "Open /tools/price-index in a private window.",
-            "Search a real model name and submit.",
-            "Read the results.",
-            "Restore the flag to true afterwards.",
-        ],
-        needsReview: true,
-        reviewNote: "Needs the kill switch flipped off to observe the fallback path, which an ordinary run never exercises — flagged for a human or an admin-tooling pass.",
-        expectedBehaviour: "With the index unavailable, the tool must fall back to the original query-based endpoint rather than going blank. The fallback pays a real Firestore query, which is the accepted cost of the flag being off.",
-        expectedUiState: "The same real sale figures appear as when the index is on — slower, possibly, but not absent.",
-        endResult: "Restore siteSettings.search.indexEnabled to true before ending the session.",
-    },
-    "checklist-content-discovery-compare-overlay-add-item-compare-add-another-via-typeahead": {
-        roles: ["guest"],
-        startPage: "/products",
-        steps: [
-            "Open /products and select one item for comparison (checkbox).",
-            "Open the compare overlay.",
-            "Find the 'Add another to compare' box inside the overlay.",
-            "Type a different product's name and read the suggestions.",
-            "Click one.",
-            "Read the overlay's columns.",
-        ],
-        expectedBehaviour: "Before this, the only way to add an item was selecting it via a listing-page checkbox BEFORE opening the overlay — there was no way to add a further item once inside it. The typeahead resolves a slug locally and the overlay fetches that product the same way it already fetches checkbox-selected ones.",
-        expectedUiState: "A new column appears for the picked item — its image, price and specs — without closing the overlay or returning to the grid. The originally-selected item's column is still there.",
-        endResult: "Close the overlay; nothing persists.",
-    },
-    "checklist-content-discovery-compare-overlay-add-item-compare-add-hidden-at-column-limit": {
-        roles: ["guest"],
-        startPage: "/products",
-        steps: [
-            "Open /products and select items for comparison until the compare overlay's maximum column count is reached (checkboxes, then the typeahead if room remains).",
-            "Open or stay in the overlay once full.",
-            "Look for the 'Add another to compare' box.",
-        ],
-        expectedBehaviour: "A picker that cannot actually add anything because the overlay is full is worse than an absent one — it invites a click that does nothing.",
-        expectedUiState: "The 'Add another' box is completely ABSENT once the column limit is reached, not merely disabled or greyed out.",
-        endResult: "Close the overlay; nothing persists.",
-    },
-};

package/dist/features/tester/seed-data/authored/content-discovery__search.d.ts

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