@mohasinac/appkit 4.52.4 → 4.53.0

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/design-ux__header-brand-mark-centring.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/design-ux__header-brand-mark-centring.js

@@ -0,0 +1,90 @@
+/*
+ * WHY: Authored six-part procedures for the design-ux/header-brand-mark-centring page.
+ * WHAT: 6 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-design-ux-header-brand-mark-centring-mark-clear-of-icons-across-the-lg-band": {
+        roles: ["guest"],
+        startPage: "/products",
+        steps: [
+            "Open /products signed out.",
+            "Set the window to exactly 1024px wide.",
+            "Widen in roughly 32px steps to 1280px, pausing at each step.",
+            "At each step look at the space between the 'LetItRip' wordmark and the first icon of the right-hand cluster.",
+        ],
+        expectedBehaviour: "The mark is one of three in-flow tracks in the title row, so the row's layout reserves its width and the action cluster cannot be laid out across it at any width. Previously it was absolutely positioned and the cluster simply grew over it between 1024px and ~1150px.",
+        expectedUiState: "At every step the leaf mark sits in clear space with visible gap on both sides. No part of it overlaps the notification bell, the messages icon, the wishlist heart or the cart. Each icon's full 44px square is unobstructed. If an overlap appears, record the exact window width it starts and stops at — the band is the finding, not the single screenshot.",
+        endResult: "Pure layout; nothing persists. Reloading at any width in the band reproduces the same clean header, and the band must not reappear after a reload.",
+    },
+    "checklist-design-ux-header-brand-mark-centring-mark-clear-signed-out-worst-case": {
+        roles: ["guest", "buyer"],
+        startPage: "/products",
+        steps: [
+            "Sign out completely and load /products.",
+            "Set the window to approximately 1100px wide.",
+            "Screenshot the header.",
+            "Sign in as any buyer and, without changing the window width, screenshot the header again.",
+        ],
+        expectedBehaviour: "Signed out the cluster is at its widest, because 'Sign in' and 'Register' (~160px together) replace a single 44px avatar. ~1100px signed out is the exact combination the original bug report was captured at, so it is the case most likely to regress.",
+        expectedUiState: "Both screenshots show the leaf mark clear of every control. Signed out the cluster reads search, Today's Deals, theme and hamburger plus 'Sign in' and 'Register'; signed in it reads bell, messages, heart, cart, avatar and the same four. In neither does the leaf touch an icon. If exactly one of the two fails, say which — signed-out-only failure means the auth buttons' extra width is still unaccounted for.",
+        endResult: "Navigation and session change only. Signing back out at the same width must return to the clean signed-out header, not to an overlapping one.",
+    },
+    "checklist-design-ux-header-brand-mark-centring-mark-shifts-rather-than-overlapping": {
+        roles: ["guest"],
+        startPage: "/products",
+        steps: [
+            "Signed out at /products, start from 1280px.",
+            "Narrow the window slowly toward 1024px.",
+            "Watch the leaf mark's horizontal position as the gap closes.",
+            "Stop at the narrowest point where the cluster still shows all of its icons.",
+        ],
+        expectedBehaviour: "When the cluster needs more than its half of the row, the side track holding the wordmark yields and the mark is pushed off-centre. Shifting is the intended degradation — the alternative designs either hide the mark under the icons (the old bug) or let the cluster shrink below its own content and be clipped, and the app shell is overflow-clipped, so clipped is gone rather than scrollable.",
+        expectedUiState: "As the window narrows the leaf drifts toward the wordmark and stays fully visible the whole way — it never slides beneath an icon and never gets cropped. Every icon keeps its full box, the hamburger stays entirely inside the right edge, and nothing is cut off. Report separately whether the failure was an overlap, a clipped control, or a disappearing leaf; they have different causes.",
+        endResult: "Nothing persists. Widening back to 1280px returns the leaf to the centre, which also confirms the shift is layout-driven and not a one-way state.",
+    },
+    "checklist-design-ux-header-brand-mark-centring-mark-centred-at-wide-widths": {
+        roles: ["guest"],
+        startPage: "/products",
+        steps: [
+            "Load /products and maximise the window (1440px or wider).",
+            "Compare the leaf mark's position against the horizontal centre of the page content.",
+            "Repeat at 1920px if the display allows it.",
+        ],
+        expectedBehaviour: "With room to spare the two side tracks each take an equal share of the free space, which places the middle track on the row's midpoint — the mark is centred by the layout rather than by a `left: 50%` offset.",
+        expectedUiState: "The leaf is centred in the header to the eye, lining up with the centre of the page beneath it. A mark that is visibly nudged to one side at a wide width is a DIFFERENT fault from the collision — the side tracks are no longer balanced — and should be filed as such, with the window width noted.",
+        endResult: "No state. The centring must hold across a reload and across a soft navigation to another page.",
+    },
+    "checklist-design-ux-header-brand-mark-centring-mark-absent-below-md": {
+        roles: ["guest"],
+        startPage: "/products",
+        steps: [
+            "Load /products signed out.",
+            "Set the window to 767px, then 640px, then 320px.",
+            "At each width inspect the whole header row end to end.",
+            "At 320px tap the hamburger.",
+        ],
+        expectedBehaviour: "The centred mark is hidden below md, which removes it as a layout item entirely rather than merely making it invisible — so the mobile header should be identical to how it has always rendered, with the two side tracks splitting the full width.",
+        expectedUiState: "No centred leaf at any of the three widths. A small leaf sits immediately left of the 'LetItRip' wordmark. The action cluster is still flush against the right edge with no unexplained empty gap between it and the edge. At 320px the hamburger is fully visible, not sliced by the edge, and tapping it opens the menu.",
+        endResult: "Nothing is written. Widening back past 768px brings the centred leaf back, confirming the hide is width-driven.",
+    },
+    "checklist-design-ux-header-brand-mark-centring-mark-centred-in-left-hand-mode": {
+        roles: ["guest"],
+        startPage: "/products",
+        steps: [
+            "Load /products and switch the interface to left-hand mode.",
+            "Set the window to 1024px.",
+            "Widen in ~32px steps to 1280px, checking the header at each step.",
+            "Narrow to 320px and check the header once more.",
+        ],
+        expectedBehaviour: "Hand mode reverses the row's main axis, so the two side tracks swap ends. Each side carries its own mirrored alignment, and the middle track is deliberately hand-neutral — a centred brand mark must not move when the hands swap.",
+        expectedUiState: "The wordmark sits flush against the RIGHT edge with no gap between it and the edge; the icon cluster sits flush against the LEFT edge with the hamburger outermost; the leaf stays centred and overlaps nothing at any step. A wordmark floating away from the right edge means a side track lost its mirrored alignment — that is a fix that only works in right-hand mode, and it is the most likely way this regresses.",
+        endResult: "The hand-mode preference persists across a reload; the header must render the same way after it. Switching back to right-hand mode mirrors everything again with the leaf still centred.",
+    },
+};

package/dist/features/tester/seed-data/authored/design-ux__header-controls-and-messages.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/design-ux__header-controls-and-messages.js

@@ -0,0 +1,85 @@
+/*
+ * WHY: Authored six-part procedures for the design-ux/header-controls-and-messages page.
+ * WHAT: 6 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-design-ux-header-controls-and-messages-no-help-or-tour-icon": {
+        roles: ["guest"],
+        startPage: "/products",
+        steps: [
+            "Open /products at a maximised window.",
+            "Read every icon in the top header row, right of the logo.",
+            "Repeat at 1024px, 768px and 320px.",
+        ],
+        expectedBehaviour: "The tour control was removed outright, along with the prop that fed it, so there is no width at which it can reappear.",
+        expectedUiState: "No '?' icon anywhere in the header at any of the four widths. The right-hand cluster is search, Today's Deals (640px and up), theme toggle and hamburger — plus the signed-in icons at 1024px and up. The removed control previously sat between the theme toggle and the hamburger.",
+        endResult: "Nothing persists; this is a pure chrome check. The hamburger must still be present and fully visible at 320px.",
+    },
+    "checklist-design-ux-header-controls-and-messages-tour-does-not-autostart": {
+        roles: ["guest", "buyer"],
+        startPage: "/",
+        steps: [
+            "Signed out, load /, then /products, then a product detail page.",
+            "Wait a few seconds on each without clicking anything.",
+            "Sign in and repeat the same three pages.",
+        ],
+        expectedBehaviour: "Removing the header button removed the only call to `startTour`. Nothing else should be able to begin a tour, on any route or for any role.",
+        expectedUiState: "No tour popover, spotlight, highlight ring or step counter appears at any point, signed in or out. A tour appearing means something still calls startTour and the removal is incomplete — record which page it fired on.",
+        endResult: "No tour state is written. Reloading any of the pages produces no tour either.",
+    },
+    "checklist-design-ux-header-controls-and-messages-messages-icon-visible-when-signed-in": {
+        roles: ["buyer"],
+        startPage: "/messages",
+        steps: [
+            "Sign in as any buyer.",
+            "At a window 1024px or wider, look at the header beside the notification bell.",
+            "Click the messages icon.",
+        ],
+        expectedBehaviour: "The header renders the messages control only when `siteSettings.chat.enabled` is true — and renders nothing at all when it is not, rather than a disabled icon. The flag is now on, so the control should exist and route to the inbox.",
+        expectedUiState: "A messages/inbox icon is present beside the notification bell and carries an unread badge when there are unread messages. Clicking it navigates to /messages, which loads — not a 404 and not /unauthorized.",
+        endResult: "Navigation only; nothing is written. Going back returns to the previous page with the icon still present.",
+    },
+    "checklist-design-ux-header-controls-and-messages-messages-icon-on-mobile-row": {
+        roles: ["buyer"],
+        startPage: "/messages",
+        steps: [
+            "Still signed in, narrow the window to 320px.",
+            "Look at BOTH header rows — the main row and the secondary row beneath it.",
+            "Tap the messages icon.",
+        ],
+        expectedBehaviour: "Several signed-in icons are hidden from the main row below 1024px and carried on a secondary row instead, so the control moves rather than disappearing.",
+        expectedUiState: "The messages icon is present and fully visible in the secondary header row at 320px — not clipped at the edge and not absent. Tapping it opens /messages.",
+        endResult: "Nothing persists. Widening back past 1024px moves the icon to the main row again.",
+    },
+    "checklist-design-ux-header-controls-and-messages-messages-absent-for-guests": {
+        roles: ["guest"],
+        startPage: "/products",
+        steps: [
+            "Sign out completely.",
+            "Reload /products.",
+            "Inspect both header rows at a desktop width and again at 320px.",
+        ],
+        expectedBehaviour: "A message inbox is per-user, so enabling the feature site-wide must not expose the control to visitors who have no inbox.",
+        expectedUiState: "No messages icon in either header row at either width. The guest header shows search, deals, theme, hamburger and the sign-in affordances only.",
+        endResult: "No state. Signing back in brings the icon back, which also confirms the gate is on the session and not on the page.",
+    },
+    "checklist-design-ux-header-controls-and-messages-messages-inbox-loads": {
+        roles: ["buyer"],
+        startPage: "/messages",
+        steps: [
+            "Signed in, navigate directly to /messages.",
+            "Wait for the page to settle.",
+            "Reload once.",
+        ],
+        expectedBehaviour: "The messaging feature has been dormant behind a disabled flag, so this is the first real exercise of the page. It must handle having no conversations as a normal state.",
+        expectedUiState: "The inbox shell renders with either a list of conversations or an explicit empty state saying there are none. It must NOT be a crash, an error boundary, a redirect to /unauthorized, or a spinner that never resolves. Note the exact empty-state wording so a later run can tell 'empty' from 'failed to load'.",
+        endResult: "Reloading shows the same state. Visiting /messages signed out should send you to sign-in rather than rendering an empty inbox.",
+    },
+};

package/dist/features/tester/seed-data/authored/index.js

@@ -77,6 +77,7 @@ import { authored as a_content_discovery__blog } from "./content-discovery__blog
 import { authored as a_content_discovery__coupons } from "./content-discovery__coupons.js";
 import { authored as a_content_discovery__events } from "./content-discovery__events.js";
 import { authored as a_content_discovery__faq_help } from "./content-discovery__faq-help.js";
+import { authored as a_content_discovery__authenticity_checker } from "./content-discovery__authenticity-checker.js";
 import { authored as a_content_discovery__parts_database } from "./content-discovery__parts-database.js";
 import { authored as a_content_discovery__category_tabs_franchise_bundles } from "./content-discovery__category-tabs-franchise-bundles.js";
 import { authored as a_content_discovery__notifications } from "./content-discovery__notifications.js";
@@ -89,6 +90,8 @@ import { authored as a_design_ux__back_to_top_button } from "./design-ux__back-t
 import { authored as a_design_ux__rich_text_readability } from "./design-ux__rich-text-readability.js";
 import { authored as a_design_ux__action_bar_placement } from "./design-ux__action-bar-placement.js";
 import { authored as a_design_ux__nav_reachability } from "./design-ux__nav-reachability.js";
+import { authored as a_design_ux__header_brand_mark_centring } from "./design-ux__header-brand-mark-centring.js";
+import { authored as a_design_ux__header_controls_and_messages } from "./design-ux__header-controls-and-messages.js";
 import { authored as a_design_ux__feature_badge_picker } from "./design-ux__feature-badge-picker.js";
 import { authored as a_design_ux__dashboard_layout } from "./design-ux__dashboard-layout.js";
 import { authored as a_design_ux__footer_theme } from "./design-ux__footer-theme.js";
@@ -113,6 +116,7 @@ import { authored as a_selling__final_sale_authoring } from "./selling__final-sa
 import { authored as a_selling__listing_type_fields_roundtrip } from "./selling__listing-type-fields-roundtrip.js";
 import { authored as a_selling__media_limits } from "./selling__media-limits.js";
 import { authored as a_selling__seller_bids_bundles_filters } from "./selling__seller-bids-bundles-filters.js";
+import { authored as a_tools__sticker_tracer } from "./tools__sticker-tracer.js";
 import { authored as a_selling__seller_catalog_org } from "./selling__seller-catalog-org.js";
 import { authored as a_selling__seller_custom_brands } from "./selling__seller-custom-brands.js";
 import { authored as a_selling__seller_guide } from "./selling__seller-guide.js";
@@ -139,6 +143,7 @@ import { authored as a_selling__listing_edit_roundtrip } from "./selling__listin
 import { authored as a_selling__digital_content_delivery } from "./selling__digital-content-delivery.js";
 import { authored as a_selling__seller_orders_at_scale } from "./selling__seller-orders-at-scale.js";
 import { authored as a_content_discovery__category_counts_and_rollup } from "./content-discovery__category-counts-and-rollup.js";
+import { authored as a_content_discovery__overflowing_pill_rows } from "./content-discovery__overflowing-pill-rows.js";
 import { authored as a_content_discovery__store_reviews_aggregate } from "./content-discovery__store-reviews-aggregate.js";
 import { authored as a_buying__order_detail_actions } from "./buying__order-detail-actions.js";
 import { authored as a_admin__admin_detail_round_trips } from "./admin__admin-detail-round-trips.js";
@@ -203,6 +208,7 @@ export const AUTHORED_CASES = {
     ...a_content_discovery__coupons,
     ...a_content_discovery__events,
     ...a_content_discovery__faq_help,
+    ...a_content_discovery__authenticity_checker,
     ...a_content_discovery__parts_database,
     ...a_content_discovery__category_tabs_franchise_bundles,
     ...a_content_discovery__notifications,
@@ -215,6 +221,8 @@ export const AUTHORED_CASES = {
     ...a_design_ux__rich_text_readability,
     ...a_design_ux__action_bar_placement,
     ...a_design_ux__nav_reachability,
+    ...a_design_ux__header_brand_mark_centring,
+    ...a_design_ux__header_controls_and_messages,
     ...a_design_ux__feature_badge_picker,
     ...a_design_ux__dashboard_layout,
     ...a_design_ux__footer_theme,
@@ -239,6 +247,7 @@ export const AUTHORED_CASES = {
     ...a_selling__listing_type_fields_roundtrip,
     ...a_selling__media_limits,
     ...a_selling__seller_bids_bundles_filters,
+    ...a_tools__sticker_tracer,
     ...a_selling__seller_catalog_org,
     ...a_selling__seller_custom_brands,
     ...a_selling__seller_guide,
@@ -265,6 +274,7 @@ export const AUTHORED_CASES = {
     ...a_selling__digital_content_delivery,
     ...a_selling__seller_orders_at_scale,
     ...a_content_discovery__category_counts_and_rollup,
+    ...a_content_discovery__overflowing_pill_rows,
     ...a_content_discovery__store_reviews_aggregate,
     ...a_buying__order_detail_actions,
     ...a_admin__admin_detail_round_trips,

package/dist/features/tester/seed-data/authored/selling__media-limits.js

@@ -18,6 +18,7 @@
  * @tag consumers:seed-data/authored/index.ts
  * @tag sideEffects:none
  */
+import { PRODUCT_MAX_IMAGES } from "../../../../_internal/shared/media/limits.js";
 export const authored = {
     "checklist-selling-media-limits-media-gallery-accepts-images-and-video": {
         roles: ["seller"],
@@ -41,39 +42,40 @@ export const authored = {
         expectedUiState: "Three image previews and one video poster frame, each showing its own content rather than a generic icon. No error toast on any of the four.",
         endResult: "Leave the editor without saving so no draft product is created.",
     },
-    "checklist-selling-media-limits-media-tenth-image-uploads": {
+    "checklist-selling-media-limits-media-last-allowed-image-uploads": {
         roles: ["seller"],
         startPage: "/store/products/new",
         steps: [
             "Sign in as tyson@beybladearena.in / TempPass123!.",
-            "Open /store/products/new and type 'QA Product media-tenth' as the title.",
+            "Open /store/products/new and type 'QA Product media-boundary' as the title.",
             "Click 'Show all fields (advanced)' before touching any media. 🛑 /store/products/new opens the QUICK form by default for a create of a standard listing, and it has ONE field — 'Product Image' — with no gallery and no video field at all. Every media step below needs the advanced form.",
-            "Upload public/test-media/sample-image.png to the gallery nine times, counting the previews after each.",
-            "Upload it a tenth time.",
-            "Read the preview count and any message about the limit.",
+            `Read the counter under the gallery and note the cap it advertises. It must read ${PRODUCT_MAX_IMAGES}. 🛑 Do NOT assume a number here — the cap is one constant (\`PRODUCT_MAX_IMAGES\`) and this case is written against whatever it currently is.`,
+            "Upload public/test-media/sample-image.png to the gallery repeatedly, one at a time, counting the previews after each, until the control refuses one.",
+            "Record the preview count reached at the moment of the first refusal.",
         ],
-        inputs: { title: "QA Product media-tenth", uploadCount: 10, cap: 10 },
-        expectedBehaviour: "The tenth image is accepted, because the cap is ten and a cap is inclusive of its own number. An off-by-one that refuses the tenth is the most likely error and the least likely to be noticed, since nine images look like plenty.",
-        expectedUiState: "Ten previews are present after the tenth upload. Any limit message reads as 'you have reached the limit' rather than as a rejection of the tenth file.",
-        expectedData: { imageCount: 10 },
+        inputs: { title: "QA Product media-boundary", cap: PRODUCT_MAX_IMAGES },
+        expectedBehaviour: `Every upload up to and including the ${PRODUCT_MAX_IMAGES}th is accepted, because a cap is inclusive of its own number. An off-by-one that refuses the last one is the most likely error and the least likely to be noticed, since one short of the cap still looks like plenty.`,
+        expectedUiState: `The preview count reached before the first refusal is exactly ${PRODUCT_MAX_IMAGES}. The counter's own advertised cap and the count actually reachable must be the SAME number — a form that says ${PRODUCT_MAX_IMAGES} and allows ${PRODUCT_MAX_IMAGES - 1} is the failure, whichever number it says.`,
+        expectedData: { imageCount: PRODUCT_MAX_IMAGES },
         endResult: "Leave the editor without saving.",
     },
-    "checklist-selling-media-limits-media-eleventh-image-refused-client-side": {
+    "checklist-selling-media-limits-media-over-cap-image-refused-client-side": {
         roles: ["seller"],
         startPage: "/store/products/new",
         steps: [
             "Sign in as tyson@beybladearena.in / TempPass123!.",
-            "Open /store/products/new and upload public/test-media/sample-image.png ten times.",
+            "Open /store/products/new.",
             "Click 'Show all fields (advanced)' before touching any media. 🛑 /store/products/new opens the QUICK form by default for a create of a standard listing, and it has ONE field — 'Product Image' — with no gallery and no video field at all. Every media step below needs the advanced form.",
+            `Fill the gallery to its cap with public/test-media/sample-image.png (${PRODUCT_MAX_IMAGES} uploads).`,
             "Open the browser's Network panel.",
-            "Attempt an eleventh upload of the same file.",
+            "Attempt one more upload of the same file.",
             "Read the message shown and count the previews.",
-            "Check the Network panel for any upload request made by that eleventh attempt.",
+            "Check the Network panel for any signed-URL or upload request made by that over-cap attempt.",
         ],
-        inputs: { cap: 10, attemptCount: 11 },
-        expectedBehaviour: "The eleventh is refused in the browser, before any signed URL is requested. Refusing it only after the bytes have reached storage leaves an orphaned object behind and spends the seller's upload time on a file that was never going to be kept.",
-        expectedUiState: "A readable message names the ten-image limit, the preview count stays at ten, and the Network panel shows NO upload request for the eleventh attempt. A refusal that appears only after a round trip is the failure.",
-        expectedData: { imageCount: 10, uploadRequestsForEleventh: 0 },
+        inputs: { cap: PRODUCT_MAX_IMAGES, attemptCount: PRODUCT_MAX_IMAGES + 1 },
+        expectedBehaviour: "The over-cap file is refused in the browser, before any signed URL is requested. Refusing it only after the bytes have reached storage leaves an orphaned object behind and spends the seller's upload time on a file that was never going to be kept.",
+        expectedUiState: `A readable message NAMES the limit as ${PRODUCT_MAX_IMAGES}, the preview count stays at ${PRODUCT_MAX_IMAGES}, and the Network panel shows NO upload request for the over-cap attempt. A refusal that appears only after a round trip is the failure, and so is a refusal that does not say what the limit is.`,
+        expectedData: { imageCount: PRODUCT_MAX_IMAGES, uploadRequestsForOverCap: 0 },
         endResult: "Leave the editor without saving.",
     },
     "checklist-selling-media-limits-media-second-video-refused-first-kept": {