@mohasinac/appkit 4.52.5 → 4.53.1

package/dist/features/tester/seed-data/authored/content-discovery__category-tabs-franchise-bundles.js

@@ -1,7 +1,7 @@
 /*
  * WHY: Authored six-part procedures for the categories-index tabs, the
  *      franchise unit and the bundle collage (2026-10-14).
- * WHAT: 8 cases, keyed by full checklist id.
+ * WHAT: 9 cases, keyed by full checklist id.
  *
  * 🛑 EVERY CASE IS BEFORE → AFTER, because every defect this work produced
  * rendered a page that looked fine:
@@ -9,17 +9,19 @@
  *   1. The index rendered all 1,185 rows flat — six roots buried under 752
  *      part leaves. A case reading "the categories page loads" passes against
  *      that.
- *   2. The Parts tab first returned 772, catching the 20 classification NODES
- *      as well as the leaves, because their own `parentIds` also pass through
- *      a `*-parts` node. A list mixing "Attack Rings" with attack rings is not
- *      visibly wrong.
- *   3. Seven franchises have no stock. Active, each is a card opening an empty
+ *   2. Seven franchises have no stock. Active, each is a card opening an empty
  *      shop; absent, seventeen `CharacterHotspot` links stay 404. Both look
  *      correct from any single page — which is why two cases here check the
  *      index and the detail page SEPARATELY.
- *   4. Every bundle also carries a placeholder cover, so a collage tested
+ *   3. Every bundle also carries a placeholder cover, so a collage tested
  *      after the cover never renders — and one grey tile is not "broken".
  *
+ * 🛑 A fifth PARTS tab was removed 2026-10-20 and its case deleted with it.
+ * Parts live at `/parts/[classification]/[code]` and in the spares listing
+ * type; a flat tab over 752 leaves was the worse half of both. The
+ * product-detail Parts COMPOSITION tab is unrelated and still covered, on the
+ * `parts-database` page.
+ *
  * So each case counts an exact number or compares two surfaces. Several carry
  * a nonsense control, because a filter that returns everything looks identical
  * to a filter that works.
@@ -47,49 +49,36 @@ export const authored = {
         expectedData: { rootCards: 6 },
         endResult: "Nothing is changed; this case only reads.",
     },
-    "checklist-content-discovery-category-tabs-franchise-bundles-five-tabs-no-all": {
+    "checklist-content-discovery-category-tabs-franchise-bundles-four-tabs-no-all-no-parts": {
         roles: ["guest"],
         startPage: "/categories",
         steps: [
             "Open /categories.",
             "Read the tab bar.",
-            "Confirm there are exactly five tabs: Categories, Brands, Franchises, Parts, Bundles.",
+            "Confirm there are exactly four tabs: Categories, Brands, Franchises, Bundles.",
             "Answer no if a tab labelled 'All' is present.",
+            "Answer no if a tab labelled 'Parts' is present.",
+            "Open a product detail page for a named-model Beyblade — for example /categories/category-ace-dragon-sting-charge-zan reached through Spinning Tops, or any complete-top listing — and confirm its own 'Parts' / 'What it is made of' composition section is STILL there. That is a different tab on a different surface and must not have been removed.",
         ],
-        expectedBehaviour: "BEFORE: the tabs were All / Categories / Brands, and 'All' was the DEFAULT — it is what rendered the 1,185 rows. AFTER: five tabs, no 'All'. Every tab answers a question ('which parts do you have?'); 'all' answered none of them, which is why it was removed rather than reordered.",
-        expectedUiState: "Five tabs, named exactly as above, with no 'All'.",
-        expectedData: { tabCount: 5, hasAllTab: false },
-        endResult: "Nothing is changed; this case only reads.",
-    },
-    "checklist-content-discovery-category-tabs-franchise-bundles-parts-tab-is-leaves-only": {
-        roles: ["guest"],
-        startPage: "/categories",
-        steps: [
-            "Open /categories and click the Parts tab.",
-            "Read the total the pager reports.",
-            "Confirm it reads 752 and not 772.",
-            "Scan the first page and confirm every card is an individual PART — '1B', 'Ten Heavy', 'Neo Right SG'.",
-            "Answer no if a classification GROUP appears as a card: 'Attack Rings', 'Weight Disks', 'Performance Tips', 'Bit Chips'.",
-        ],
-        expectedBehaviour: "BEFORE: the tab returned 772, because the predicate matched any row whose ancestry passes a `*-parts` node — which is true of the 20 classification NODES as well as the leaves beneath them. The list mixed groups with their own contents and was not visibly wrong. AFTER: leaves only, 752. A part is a leaf by itself; a classification is a branch you reach by drilling down.",
-        expectedUiState: "752 parts reported. Every card is a single part; no classification group appears.",
-        expectedData: { partsTotal: 752, classificationNodesShown: 0 },
+        expectedBehaviour: "BEFORE the first fix: the tabs were All / Categories / Brands, and 'All' was the DEFAULT — it is what rendered the 1,185 rows. BEFORE this one: a fifth 'Parts' tab listed all 752 part leaves flat, duplicating /parts and the spares listing type with a worse version of both. AFTER: four tabs, no 'All' and no 'Parts'. The part leaves still exist and are still reached by drilling into a `*-parts` node; only the flat shortcut tab is gone. The product-level composition tab is untouched — removing that would have deleted the part database's own reason to exist.",
+        expectedUiState: "Four tabs, named exactly as above. No 'All', no 'Parts'. A model listing still shows its composition section.",
+        expectedData: { tabCount: 4, hasAllTab: false, hasPartsTab: false },
         endResult: "Nothing is changed; this case only reads.",
     },
     "checklist-content-discovery-category-tabs-franchise-bundles-tabs-do-not-overlap": {
         roles: ["guest"],
         startPage: "/categories",
         steps: [
-            "Open /categories and note the total each of the five tabs reports: Categories, Brands, Franchises, Parts, Bundles.",
-            "Expect 6, 28, 8, 752, 5.",
+            "Open /categories and note the total each of the four tabs reports: Categories, Brands, Franchises, Bundles.",
+            "Expect 6, 28, 8, 5.",
             "Pick one brand by name on the Brands tab — for example Takara-Tomy.",
-            "Open each of the other four tabs and search for that same name.",
+            "Open each of the other three tabs and search for that same name.",
             "Answer no if it appears on any tab other than Brands.",
             "Repeat once with a bundle name taken from the Bundles tab.",
         ],
         expectedBehaviour: "Brands, franchises and bundles are all tier-0 rows, so a predicate that tested the tier before the discriminator would list every one of them under Categories as well. The type check has to come first. A row on two tabs double-counts the catalogue and makes the totals unreadable.",
-        expectedUiState: "Tab totals read 6 / 28 / 8 / 752 / 5. The sampled brand and bundle each appear on exactly one tab.",
-        expectedData: { categories: 6, brands: 28, franchises: 8, parts: 752, bundles: 5 },
+        expectedUiState: "Tab totals read 6 / 28 / 8 / 5. The sampled brand and bundle each appear on exactly one tab.",
+        expectedData: { categories: 6, brands: 28, franchises: 8, bundles: 5 },
         endResult: "Nothing is changed; this case only reads.",
     },
     "checklist-content-discovery-category-tabs-franchise-bundles-franchise-index-hides-unstocked": {
@@ -149,4 +138,37 @@ export const authored = {
         expectedData: { bundleCards: 5, cardsWithCollage: 5 },
         endResult: "Nothing is changed; this case only reads.",
     },
+    "checklist-content-discovery-category-tabs-franchise-bundles-tabs-collapse-on-narrow-viewport": {
+        roles: ["guest"],
+        startPage: "/categories",
+        steps: [
+            "Resize the viewport to a phone width, around 390px.",
+            "Open /categories.",
+            "Look at the tab row reading Categories / Brands / Franchises / Bundles.",
+            "BEFORE a fix landed 2026-10-19: this was a plain row of `<Button variant=\"ghost\">`s with a hand-written underline — no `role=\"tablist\"`, no overflow handling, and on a narrow viewport the later tabs ran past the right edge with no scrollbar and no visible way to reach them.",
+            "AFTER: the row is `<OverflowRow>`. Confirm it has collapsed into a single trigger button showing the active tab's name plus a chevron.",
+            "Click the trigger. Confirm a searchable dropdown opens listing all four tabs.",
+            "Pick a different tab from the dropdown and confirm the page re-filters to it.",
+        ],
+        expectedBehaviour: "A row of controls that does not fit its container must become a trigger that opens a searchable list, not a row the visitor has to discover can be scrolled. `<OverflowRow>` is the one primitive this project built for exactly this shape (see CLAUDE.md § Overflowing Pill & Tab Rows) — the old row predates it and was never migrated. 🛑 Four tabs can still overflow 390px: the threshold is MEASURED width, never a count (that is why `TabsList`'s old `items.length > 5` rule was deleted), so dropping the fifth tab does not retire this case.",
+        expectedUiState: "At 390px: one trigger button, not four separate tab buttons. Opening it shows all four tabs in a dropdown, each clickable, with the active one marked.",
+        expectedData: { tabsVisibleAsRowAt390px: false, collapsedTriggerPresent: true },
+        endResult: "Nothing is changed; this case only reads.",
+    },
+    "checklist-content-discovery-category-tabs-franchise-bundles-tabs-hover-changes-ink": {
+        roles: ["guest"],
+        startPage: "/categories",
+        steps: [
+            "Open /categories on a desktop-width viewport (at least 1024px, so the tabs render as a row rather than a collapsed trigger).",
+            "Pick a tab that is NOT currently active.",
+            "BEFORE a fix landed 2026-10-19: this row (and several others — the notification bell, the admin sidebar/nav/header, the mobile bottom-nav item) carried two competing `hover:text-*` classes on one element, one of which resolved to the element's own RESTING colour. Hovering therefore changed nothing, which reads as 'hover is broken' rather than as a styling bug.",
+            "Hover the mouse pointer over the inactive tab's label without clicking.",
+            "Compare its text colour before and during the hover.",
+            "Move the pointer away and confirm the colour returns to the resting shade.",
+        ],
+        expectedBehaviour: "Every hover state must visibly differ from the resting state. A hover ink that equals the resting ink is indistinguishable from no hover handler at all.",
+        expectedUiState: "The inactive tab's text colour visibly changes while hovered, and reverts when the pointer leaves.",
+        expectedData: { hoverChangesTextColor: true },
+        endResult: "Nothing is changed; this case only reads.",
+    },
 };

package/dist/features/tester/seed-data/authored/content-discovery__events.js

@@ -179,17 +179,27 @@ export const authored = {
         startPage: "/events",
         steps: [
             "Sign in as rehan.sheikh@gmail.com / TempPass123!.",
-            "Open event-won-original-set-raffle and click the Participate tab.",
+            "Open event-win-burst-regalia-genesis and click the Participate tab.",
             "Read the entry conditions stated.",
             "Enter the raffle.",
             "Read what the page shows immediately, without reloading.",
-            "Reload and read the tab again.",
+            "RELOAD and read the tab again BEFORE touching the form — note whether it already shows you as entered, or presents an empty form as though you had not.",
             "Try to enter a second time.",
         ],
-        expectedBehaviour: "An open raffle records one entry per user. The entry is what makes the user eligible for the draw, so a second attempt must be refused rather than creating a duplicate that would double their odds.",
-        expectedUiState: "The entry is confirmed in place. After reloading the tab shows the user as already entered. The second attempt is refused with a message.",
-        expectedData: { entriesPerUser: 1 },
-        endResult: "The entry survives the reload.",
+        /*
+         * 🛑 The fixture changed, 2026-10-19 — it pointed at
+         * `event-won-original-set-raffle`, which is seeded `status: ENDED` with a
+         * winner ALREADY DRAWN. `enterEvent` refuses any event that is not active,
+         * so every step after "Enter the raffle" was unreachable: the case could
+         * only ever record the generic closed-entries refusal, which looks like a
+         * correct result and proves nothing about one-entry-per-user.
+         * `event-win-burst-regalia-genesis` is the active open_raffle.
+         */
+        inputs: { eventId: "event-win-burst-regalia-genesis" },
+        expectedBehaviour: "An open raffle records one entry per user, enforced SERVER-side. The entry is what makes the user eligible for the draw, so a duplicate would literally double their odds against everyone else. A limit held in the browser is no limit: the form's counter starts at zero on every page load.",
+        expectedUiState: "The entry is confirmed in place. After reloading — before any interaction — the tab already shows the user as entered, not an inviting empty form. The second attempt is refused with a message naming the existing entry.",
+        expectedData: { entriesPerUser: 1, entriesAfterSecondAttempt: 1 },
+        endResult: "BEFORE: a reload reset the form's counter to zero and presented an empty form, and submitting it was ACCEPTED with the same 'You're entered in the raffle!' toast — two entries for one person, because only surveys and polls had a per-user check and raffle had none. AFTER: the reloaded page shows the entry, and a forced second submit is refused. Exactly one entry exists.",
     },
     /*
      * 🛑 THESE TWO CASES CHANGED SHAPE, 2026-09-15.
@@ -247,16 +257,32 @@ export const authored = {
         startPage: "/events",
         steps: [
             "Sign in as rehan.sheikh@gmail.com / TempPass123!.",
-            "Open event-daily-beyblade-pull-wheel and click the Participate tab.",
+            "Navigate to the wheel BY CLICKING its card from /events — do not type the URL. The link uses the event's slug, which is the path a real visitor takes.",
+            "Click the Participate tab.",
             "Click the spin control ONCE and watch the wheel.",
             "Read the prize shown and how long it took to appear.",
+            "If anything is refused, open the network panel and record the spin request's STATUS CODE and the `code` field in its response body.",
             "Reload the page and read the Participate tab.",
         ],
         inputs: { eventId: "event-daily-beyblade-pull-wheel" },
-        expectedBehaviour: "The very first spin succeeds and the prize is shown immediately over the realtime channel. A first attempt that fails and a second that works is the signature of a subscription established after the result was already written.",
+        expectedBehaviour: "The very first spin succeeds and names a prize. The spin is a plain POST to /api/events/{id}/spin and its response carries the prize — there is no realtime channel involved, so a failure is the request itself failing, not a subscription timing problem.",
         expectedUiState: "The wheel spins and lands on a named prize within a few seconds. No 'Spin failed' error appears on the first attempt. After reloading, the result is still shown rather than the wheel offering another free spin.",
-        expectedData: { spinsUsed: 1 },
-        endResult: "The recorded spin and its prize survive the reload.",
+        expectedData: { spinsUsed: 1, spinHttpStatus: 200 },
+        /*
+         * 🛑 Two recorded production failures, and the SLUG step above is what
+         * reaches the second one.
+         *
+         * The feature was gated on `FEATURE_PRIZE_DRAWS`, an env var belonging to a
+         * mechanism that had already been retired and was therefore set nowhere —
+         * so every spin returned 503 while the button rendered enabled. Underneath
+         * that, the spin core looked the event up by document id only, with no slug
+         * fallback, while every card links by slug. Fixing the gate alone turns the
+         * 503 into a 404.
+         *
+         * So "type the doc-id URL and spin" would have passed against the live bug.
+         * Arriving by click is the test.
+         */
+        endResult: "BEFORE: the spin returned HTTP 503 with code `feature_disabled` on every attempt (and, once that was fixed, HTTP 404 `EVENT_NOT_FOUND` whenever the page was reached by its slug — i.e. from any card). Both rendered as 'Spin failed. Please try again.'. AFTER: the first click returns 200 and names a prize. The recorded spin and its prize survive the reload.",
     },
     "checklist-content-discovery-events-spin-wheel-max-per-user": {
         roles: ["buyer"],

package/dist/features/tester/seed-data/authored/content-discovery__overflowing-pill-rows.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/content-discovery__overflowing-pill-rows.js

@@ -0,0 +1,209 @@
+/*
+ * 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.js

@@ -36,12 +36,13 @@ export const authored = {
         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 database 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. 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: "Exactly 20 tiles, each labelled in sentence case, each a working link.",
+        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.",
     },

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

@@ -0,0 +1,73 @@
+/*
+ * 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__site-wide-index.d.ts

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