@mohasinac/appkit 4.58.0 → 4.60.0

package/dist/features/tester/seed-data/authored/design-ux__nav-reachability.js

@@ -1,88 +0,0 @@
-/*
- * WHY: Authored six-part procedures for the design-ux/nav-reachability 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-nav-reachability-main-nav-first-items-reachable": {
-        roles: ["guest"],
-        startPage: "/products",
-        steps: [
-            "Set the browser window to roughly 1024 pixels wide.",
-            "Open /products and look at the horizontal navigation strip under the header.",
-            "Read the FIRST item at the left edge of the strip.",
-            "Scroll the strip to the right as far as it goes and read the LAST item.",
-        ],
-        expectedBehaviour: "The strip centres its items while they fit and falls back to starting at the left edge as soon as they would overflow, so nothing is ever pushed past the leading edge where scrolling cannot reach it.",
-        expectedUiState: "'Home' is the first item visible at the left edge of the strip, followed by 'Products'. Scrolling right reaches 'About Us' at the far end. The prior symptom was the strip opening mid-list with 'Home' and 'Products' already cut off past the left edge and no way to bring them back.",
-        endResult: "Nothing persists. Reloading at the same width shows 'Home' first again — the strip is not remembering a scroll position, it genuinely starts at the beginning.",
-    },
-    "checklist-design-ux-nav-reachability-main-nav-left-chevron-works": {
-        roles: ["guest"],
-        startPage: "/products",
-        steps: [
-            "At roughly 1024 pixels wide, scroll the navigation strip to the right (drag it, or use the right chevron).",
-            "Look at the left end of the strip for a left-pointing chevron.",
-            "Click the left chevron.",
-        ],
-        expectedBehaviour: "The left chevron is shown when the strip has been scrolled away from its start. That condition could never be true while the centring pinned the scroll position at 0, so the control existed and never appeared.",
-        expectedUiState: "After scrolling right, a left chevron is visible at the left end of the strip. Clicking it scrolls the strip back towards the start, and continuing to click eventually brings 'Home' into view and the chevron disappears again.",
-        endResult: "The strip can be scrolled to either end and back as many times as wanted. No state is saved.",
-    },
-    "checklist-design-ux-nav-reachability-header-hamburger-reachable-at-320": {
-        roles: ["guest"],
-        startPage: "/products",
-        steps: [
-            "Set the browser window to 320 pixels wide, or choose an iPhone SE device profile.",
-            "Look at the right-hand end of the top header row.",
-            "Tap the hamburger (menu) control.",
-        ],
-        expectedBehaviour: "The header row must fit inside the viewport at the narrowest supported width. The app shell clips horizontal overflow rather than scrolling it, so anything past the edge is unreachable — not merely out of sight.",
-        expectedUiState: "The hamburger is FULLY visible at the end of the header row, not half-cut and not missing, and tapping it opens the menu. The theme toggle immediately before it is also whole. The prior symptom was the hamburger sitting entirely beyond the right edge and the theme toggle sliced in half.",
-        endResult: "The menu opens and closes normally. Nothing persists.",
-    },
-    "checklist-design-ux-nav-reachability-header-demotes-optional-controls": {
-        roles: ["guest"],
-        startPage: "/products",
-        steps: [
-            "At 320 pixels wide, read every icon in the top header row.",
-            "Widen the window past about 640 pixels.",
-            "Read the header row again.",
-            "At 320 pixels again, open the hamburger menu and look for the deals and tour entries.",
-        ],
-        expectedBehaviour: "Room for the hamburger is made by demoting the two most discretionary controls at the narrowest width, rather than by letting the most important one fall off the end. Neither is removed from the product — only from the header row at that width.",
-        expectedUiState: "At 320px the 'Today's Deals' and product-tour icons are NOT in the header. Above ~640px both are back. At 320px their destinations are still reachable from the menu, so nothing has become unavailable.",
-        endResult: "Purely responsive; no state is written. Resizing back and forth shows them disappear and reappear at the same point each time.",
-    },
-    "checklist-design-ux-nav-reachability-no-horizontal-page-scroll": {
-        roles: ["guest"],
-        startPage: "/",
-        steps: [
-            "Set the browser window to 320 pixels wide.",
-            "Visit each of: /, /products, any product detail page, /categories, /cart.",
-            "On each page, try to drag the page sideways and look for a horizontal scrollbar at the bottom of the window.",
-        ],
-        expectedBehaviour: "No layout should be wider than the viewport at the narrowest supported width. A sideways-scrolling page is the clearest single symptom of a broken responsive layout.",
-        expectedUiState: "On all five pages the content does not move horizontally and no horizontal scrollbar appears. Report the page and the element if any one of them scrolls — this case is per-page, so a single failure is still a finding even if the other four pass.",
-        endResult: "Nothing persists. This is a pure layout check at one width.",
-    },
-    "checklist-design-ux-nav-reachability-lightbox-thumbnails-reachable": {
-        roles: ["guest"],
-        startPage: "/products",
-        steps: [
-            "Open a product that has several images — the Beyblade X UX-03 WizardRod and the video-demo fixtures all carry multiple.",
-            "Click the main product image to open the lightbox.",
-            "Look at the thumbnail strip below the enlarged image.",
-            "Scroll the strip to both ends.",
-        ],
-        expectedBehaviour: "The thumbnail strip is a horizontal scroller and had the same centring defect as the navbar, so with enough images its first thumbnails were off the leading edge with no scroll position that could reach them.",
-        expectedUiState: "The strip begins at the FIRST image, and every thumbnail can be reached by scrolling. No thumbnail is stranded past the left edge. Clicking any thumbnail switches the enlarged image to it.",
-        endResult: "Closing the lightbox returns to the product page with no change. Reopening starts the strip at the first image again.",
-    },
-};

package/dist/features/tester/seed-data/authored/design-ux__rich-text-readability.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/design-ux__rich-text-readability.js

@@ -1,84 +0,0 @@
-/*
- * WHY: Authored six-part procedures for the design-ux/rich-text-readability page.
- * WHAT: 5 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-rich-text-readability-prose-body-readable-dark": {
-        roles: ["guest"],
-        startPage: "/categories/category-spinning-tops",
-        steps: [
-            "Set the site to DARK mode using the theme toggle in the header.",
-            "Open /categories/category-spinning-tops.",
-            "Scroll to the multi-paragraph write-up directly below the hero banner (it begins 'Four generations of Beyblade').",
-            "Read the full write-up at normal viewing distance without leaning in or changing zoom.",
-        ],
-        expectedBehaviour: "The rich-text block takes its body colour from the active theme's own text token rather than from the Tailwind typography plugin's light-theme default. No element in the block should be rendering a colour that was chosen for a white page.",
-        expectedUiState: "Every sentence of the write-up is comfortably readable against the dark page. The body copy is a light grey, clearly brighter than the page background. It is NOT the dim, low-contrast grey that appears to recede into the background — the specific prior symptom was body text at gray-700 on a dark surface.",
-        endResult: "Nothing is written and nothing persists. Reloading the page in dark mode shows the same readable text; this is a pure rendering check.",
-    },
-    "checklist-design-ux-rich-text-readability-prose-links-visible-dark": {
-        roles: ["guest"],
-        startPage: "/categories/category-spinning-tops",
-        steps: [
-            "Stay in DARK mode on /categories/category-spinning-tops.",
-            "Without moving the mouse over them, locate the five inline links in the write-up: 'Beyblade Original', 'Metal Fight', 'Burst', 'Beyblade X' and 'Accessories'.",
-            "Compare each link's text colour against the paragraph text immediately surrounding it.",
-        ],
-        expectedBehaviour: "Link colour resolves to the theme's secondary accent in dark mode, not to the typography plugin's default link colour. Identifying a link must not require hovering, because hover is unavailable on touch devices.",
-        expectedUiState: "All five links are a visibly different colour from the body copy around them and are obviously clickable at a glance. The prior symptom was links rendering at gray-900 — near-black on a dark page, effectively invisible, findable only by sweeping the cursor and watching for the pointer to change. An underline alone does NOT satisfy this case: the text colour itself must differ.",
-        endResult: "No state changes. Clicking any of the five navigates to that category, which also confirms they were real links and not styled text.",
-    },
-    "checklist-design-ux-rich-text-readability-prose-readable-light-regression": {
-        roles: ["guest"],
-        startPage: "/categories/category-spinning-tops",
-        steps: [
-            "On /categories/category-spinning-tops, switch the theme toggle to LIGHT mode.",
-            "Read the same write-up and locate the same five inline links.",
-            "Toggle between light and dark three times, pausing on each to re-read one paragraph and one link.",
-        ],
-        expectedBehaviour: "Both themes resolve their colours from the same rebound token set, so a regression in one is a plausible consequence of a change to the other. Headings, body copy and links must each stay distinct from one another in both themes.",
-        expectedUiState: "In LIGHT mode the body copy is dark on the white surface and the links are the primary brand colour. Headings remain visibly darker/stronger than body copy. Nothing is washed out, and no text becomes near-invisible at either end of the toggle.",
-        endResult: "The theme choice persists across a reload (it is stored client-side), and the write-up renders correctly in whichever mode was last selected.",
-    },
-    "checklist-design-ux-rich-text-readability-prose-readable-across-surfaces": {
-        roles: ["guest"],
-        startPage: "/blog",
-        steps: [
-            "Set the site to DARK mode.",
-            "Open any published post from /blog and read its body copy and any inline links.",
-            "Open /terms (or /privacy) and read the policy body copy.",
-            "Open /faqs and expand any answer.",
-            "Open any product from /products and read its Description tab.",
-        ],
-        expectedBehaviour: "All four surfaces render through the same shared rich-text renderer, so one shared fix must reach all of them. A surface that is still unreadable means the fix did not apply there and the renderer is being bypassed.",
-        expectedUiState: "On each of the four pages the body copy is readable light-grey-on-dark and any inline links are a visibly distinct colour. No page shows the dim gray-700 body or the near-black links described in the dark-mode cases above.",
-        endResult: "Nothing persists. If any ONE of the four fails while the others pass, record which one — that narrows the cause to that surface's own markup rather than the shared renderer.",
-    },
-    "checklist-design-ux-rich-text-readability-prose-follows-custom-theme": {
-        roles: ["admin"],
-        startPage: "/admin/site",
-        steps: [
-            "Sign in as admin@letitrip.in / TempPass123!.",
-            "Open /admin/site and go to the Themes tab.",
-            "Note which theme is currently the default, then set a visibly different one as the active default (for example Cobalt Night, or Sunset).",
-            "Open /categories/category-spinning-tops in a new tab and read the write-up's body copy and links.",
-            "Return to /admin/site → Themes and restore the original default theme.",
-        ],
-        inputs: {
-            "Themes tab — active default": "a theme other than the current default",
-        },
-        expectedBehaviour: "Rich-text colours are bound to `--appkit-color-*` theme tokens, so switching the active theme must restyle admin-authored prose along with the rest of the site. This is only possible since the 2026-10-15 fix: the typography plugin's palette is hardcoded Tailwind greys that no theme record could ever reach.",
-        expectedUiState: "After the theme change, the write-up's paragraph colour and link colour both shift to match the new theme — they do not stay the same grey the previous theme used. Body copy remains readable against whatever surface the new theme sets.",
-        expectedData: {
-            "siteSettings.theme.defaultDarkThemeId": "restored to its original value at the end",
-        },
-        endResult: "The original default theme is restored, so no other tester inherits a changed site theme. Reloading the category page shows prose in the original theme's colours again.",
-    },
-};

package/dist/features/tester/seed-data/authored/design-ux__status-badge-legibility.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/design-ux__status-badge-legibility.js

@@ -1,214 +0,0 @@
-/*
- * WHY: Authored six-part procedures for the design-ux/status-badge-legibility page.
- * WHAT: 13 case(s), keyed by full checklist id.
- *
- * Written by hand, case by case, against the label each one states. There is no
- * generator: the authoring scripts were deleted once it was clear they were
- * scaffolding around work that is simply writing.
- *
- * 🛑 TWO PAIRINGS, NEVER MIXED. An inline chip is a status TINT with matching
- * status ink; a badge overlaying a photo is a status SOLID with on-solid ink.
- * Both halves of each pair invert together. A literal white ink against either
- * background is invisible in exactly one theme, which is why every case here is
- * read in both — and why several of them name the dark theme specifically.
- *
- * A third failure mode is worse than a wrong pairing: a class the build never
- * generates. Tailwind drops an unknown utility silently, so the element renders
- * with no background at all and looks like a styling choice.
- *
- * @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-status-badge-legibility-listing-type-tags-readable-light": {
-        roles: ["guest"],
-        startPage: "/products",
-        steps: [
-            "Open /products in a private window in LIGHT mode and read the badges on the grid: Classified, Digital Code, Live Item.",
-            "Open /auctions and read the Auction badge; /pre-orders for Pre-Order; /prize-draws for Prize Draw; /art for Art Print and Sticker Sheet.",
-            "Read each badge's text against its own background.",
-            "Write down any badge whose text cannot be read.",
-        ],
-        expectedBehaviour: "Each type badge pairs a background and an ink that belong together. A tint paired with a literal white ink is white on near-white in a light theme — and the same badge is perfectly readable in dark, which is why a light-mode pass is its own case.",
-        expectedUiState: "All eight badges are readable in light mode. The specific failure is a badge whose text is invisible against a pale fill while the badge shape is clearly there.",
-        expectedData: { unreadableBadgesLight: 0 },
-        endResult: "Read-only; nothing persists.",
-    },
-    "checklist-design-ux-status-badge-legibility-listing-type-tags-readable-dark": {
-        roles: ["guest"],
-        startPage: "/products",
-        steps: [
-            "Open /products in a private window and switch to DARK mode.",
-            "Read the Classified, Digital Code and Live Item badges on the grid, then visit /auctions, /pre-orders, /prize-draws and /art for the remaining five badges.",
-            "Compare each against how it read in light mode.",
-            "Write down any badge readable in one theme and not the other.",
-        ],
-        expectedBehaviour: "The same eight badges hold in dark mode, because both halves of the pairing invert. A badge that is fine in one theme and unreadable in the other is the signature of a pairing where only one half is a token.",
-        expectedUiState: "All eight badges are readable in dark mode. A badge that passed the light-mode case and fails here is the finding, and it is the same bug from the other side.",
-        expectedData: { unreadableBadgesDark: 0 },
-        endResult: "Read-only; return the site to light mode afterwards.",
-    },
-    "checklist-design-ux-status-badge-legibility-live-item-tag-has-background": {
-        roles: ["guest"],
-        startPage: "/products",
-        steps: [
-            "Open /products in a private window and find a Live Item card.",
-            "Look at its badge and check whether it has a filled background at all.",
-            "Compare it against the Classified and Digital Code badges beside it, then against the Auction badge on /auctions.",
-            "Switch to dark mode and look again.",
-            "Open /live/live-golden-retriever-puppy and look at the badge on the detail page too.",
-        ],
-        expectedBehaviour: "The Live Item badge names a colour the build can actually generate. Its background once used a flat alias that has no tint variant and is absent from the app's own palette entirely, so the class compiled to nothing and the badge rendered with no fill — which reads as a deliberate outline style rather than a dropped class.",
-        expectedUiState: "The Live Item badge has a visible filled background in both themes, like every other type badge. A badge that is text-only while its neighbours are filled is the failure.",
-        expectedData: { hasBackground: true },
-        endResult: "Read-only; return the site to light mode afterwards.",
-    },
-    "checklist-design-ux-status-badge-legibility-promo-badges-readable": {
-        roles: ["guest"],
-        startPage: "/products",
-        steps: [
-            "Open /products in a private window in light mode.",
-            "Find cards showing NEW, SALE and LIMITED badges and read each.",
-            "Note whether these badges sit over the card's photo or beside its title.",
-            "Switch to dark mode and read them again.",
-        ],
-        expectedBehaviour: "These badges overlay a photograph, so they take the solid pairing rather than the tint one — a pale tint over an arbitrary product image is unreadable regardless of theme. A past sweep converted solid fills to tints and left the white ink behind, which broke these three specifically.",
-        expectedUiState: "NEW, SALE and LIMITED are readable over their photos in both themes, with a solid enough fill to separate them from the image behind. A pale badge floating over a light product photo is the failure.",
-        endResult: "Read-only; return the site to light mode afterwards.",
-    },
-    "checklist-design-ux-status-badge-legibility-soft-ban-lift-notification-has-a-body": {
-        roles: ["admin", "buyer"],
-        startPage: "/admin/users",
-        steps: [
-            "Sign in as admin@letitrip.in / TempPass123!.",
-            "Open /admin/users, find karthik.new@gmail.com, and apply a soft ban with a reason.",
-            "Lift the ban again.",
-            "Swap identity: this case lists roles [admin, buyer] and the harness resolves that to ADMIN, so it opens signed in as the admin. Copy tester/.tester-runs/session-buyer.json over session.json, CLOSE THE BROWSER, then sign in as karthik.new@gmail.com / TempPass123!.",
-            "Open /user/notifications and read the ban-lift notification's title AND its body.",
-        ],
-        inputs: { targetUser: "karthik.new@gmail.com" },
-        expectedBehaviour: "The ban-lift notification carries a body, not only a title. Every notification type renders from a per-type template; a type with no template falls back to something generic, which shows as an empty body or a repeat of the title.",
-        expectedUiState: "The notification has a readable title and a distinct body explaining that access is restored. An empty body, or a body that simply restates the title, means this type has no template.",
-        endResult: "The account is unbanned. Confirm karthik.new@gmail.com can sign in normally afterwards — it is used by other cases.",
-    },
-    "checklist-design-ux-status-badge-legibility-review-feedback-notification-delivers": {
-        roles: ["buyer", "seller"],
-        startPage: "/products/product-beyblade-burst-valkyrie",
-        steps: [
-            "Sign in as rehan.sheikh@gmail.com / TempPass123!.",
-            "Open a product this account has bought and leave a review. 🛑 EXPECT NO CONTROL FOR THIS and record that as the finding rather than as a failure to look properly: createReviewAction, useCreateReview and the UI_TEXT.WRITE_REVIEW string all exist, but no .tsx consumes any of them — the only review modal is read-only. If there is genuinely no way to write a review, answer null for this case and report the missing control; do not improvise through an API, which would test a path no buyer can reach.",
-            "Sign out and sign in as tyson@beybladearena.in / TempPass123!, the store owner.",
-            "Open /store and check for a notification about the new review.",
-            "Read its title, its body and where its link goes.",
-            "Click the link.",
-        ],
-        expectedBehaviour: "The seller is notified when a review lands, with a body and a destination. Reviews have no per-record page in any role, so the link correctly resolves to the reviews LIST — fabricating a per-review URL would 404, which is worse than a list.",
-        expectedUiState: "A notification exists for the store owner with a readable title and body. Its link opens the reviews list rather than a 404. No notification at all means the hook did not fire.",
-        endResult: "Delete the review afterwards so review counts on that product stay as seeded.",
-    },
-    "checklist-design-ux-status-badge-legibility-analytics-tags-absent-until-configured": {
-        roles: ["guest"],
-        startPage: "/",
-        steps: [
-            "Open / in a private window with no session.",
-            "Open the browser's View Source and search for gtag, googletagmanager, fbq and connect.facebook.net.",
-            "Open DevTools' Network tab, reload, and look for any request to a Google or Facebook analytics host.",
-            "Note whether any such tag is present.",
-        ],
-        expectedBehaviour: "Analytics tags are injected only when their ids are configured. Those ids live in a settings group that is separate from the encrypted credentials — and that group was written by the admin form while being undeclared on the settings type, which is precisely how a field escapes every type-driven review.",
-        expectedUiState: "With no analytics ids configured, no tag script is present in the source and no request is made to an analytics host. A tag firing with an empty or placeholder id is the failure — it loads the third-party script for every visitor and sends nothing useful.",
-        expectedData: { analyticsRequests: 0 },
-        endResult: "Read-only; nothing persists. If ids ARE configured on this environment, note that instead of failing the case.",
-    },
-    "checklist-design-ux-status-badge-legibility-notification-count-bubbles-readable": {
-        roles: ["buyer"],
-        startPage: "/user",
-        steps: [
-            "Sign in as rehan.sheikh@gmail.com / TempPass123! with at least one unread notification.",
-            "Open /user and read the number inside the header bell's count bubble.",
-            "Read the same bubble in the sidebar if one appears there.",
-            "Switch to dark mode and read both again.",
-            "Resize to 390 pixels wide and read them again.",
-        ],
-        inputs: { mobileWidth: 390 },
-        expectedBehaviour: "A count bubble overlays other chrome, so it takes the solid pairing. These bubbles were among the surfaces a past sweep converted to a tint while leaving the white ink, which makes the number invisible while the bubble itself is clearly there.",
-        expectedUiState: "The number is legible in both themes and at both widths. A visible coloured dot with no readable number in it is the failure.",
-        endResult: "Read-only; return the site to light mode and restore the width.",
-    },
-    "checklist-design-ux-status-badge-legibility-admin-status-chips-colored": {
-        roles: ["admin"],
-        startPage: "/admin/orders",
-        steps: [
-            "Sign in as admin@letitrip.in / TempPass123!.",
-            "Open /admin/orders and read every status chip in the list.",
-            "Check that different statuses use different colours and that each chip's text is readable.",
-            "Open /admin/stores and read its status chips.",
-            "Open /admin/payouts and read its status chips.",
-            "Switch to dark mode and read all three again.",
-        ],
-        expectedBehaviour: "Status chips are inline, so they take the tint pairing with matching ink. Distinct statuses must be distinguishable by colour — a table where every chip is the same grey is a table where status has to be read word by word.",
-        expectedUiState: "Each status renders in its own colour and every chip's text is readable, on all three pages and in both themes. Chips that are all one colour, or whose text is invisible, are both failures.",
-        endResult: "Read-only; return the site to light mode afterwards.",
-    },
-    "checklist-design-ux-status-badge-legibility-faq-helpful-buttons-readable": {
-        roles: ["guest"],
-        startPage: "/faqs",
-        steps: [
-            "Open /faqs in a private window in light mode and expand a question.",
-            "Find the helpful / not-helpful controls and read their labels.",
-            "Hover each and read it while hovering.",
-            "Click one and read its label in the selected state.",
-            "Switch to dark mode and repeat all four readings.",
-        ],
-        expectedBehaviour: "These controls have three states — resting, hover and selected — and each needs its own readable pairing in both themes. They were among the surfaces broken by a tint-with-white-ink conversion, and the selected state is the one most easily missed.",
-        expectedUiState: "Labels are readable in all three states, in both themes. The most likely failure is the selected state, since it is the only one requiring a click to see at all.",
-        endResult: "Read-only apart from the vote; return the site to light mode afterwards.",
-    },
-    "checklist-design-ux-status-badge-legibility-detail-page-tags-readable": {
-        roles: ["guest"],
-        startPage: "/auctions/auction-beyblade-x-shark-edge",
-        steps: [
-            "Open /auctions/auction-beyblade-x-shark-edge in a private window in light mode.",
-            "Read every tag and badge on the page — listing type, condition, stock, any promo tag.",
-            "Open /pre-orders/preorder-beyblade-x-bx-08-wave and read its badges, including the production status.",
-            "Open /prize-draws/prizedraw-beyblade-mystery-box and read its badges.",
-            "Switch to dark mode and read all three pages again.",
-        ],
-        expectedBehaviour: "Detail-page badges follow the same two pairings as card badges. They are worth checking separately because a detail page renders badges the grid never shows — production status, reserve state, code-pool state — and those are the ones a card-only sweep misses.",
-        expectedUiState: "Every badge on all three pages is readable in both themes. Detail-only badges such as 'In Production' are included in the reading.",
-        expectedData: { unreadableBadges: 0 },
-        endResult: "Read-only; return the site to light mode afterwards.",
-    },
-    "checklist-design-ux-status-badge-legibility-whatsapp-community-member-pill": {
-        roles: ["guest"],
-        startPage: "/",
-        steps: [
-            "Open / in a private window in light mode and scroll to the WhatsApp community card.",
-            "Read the member-count pill on it.",
-            "Look at the pill's background against the card's own branded background.",
-            "Switch to dark mode and read the pill again.",
-        ],
-        expectedBehaviour: "A pill sitting on a branded backdrop needs the translucent-white surface, not the page surface. The page surface is a LIGHT background in every light theme, so pairing it with inverse ink is white-on-white — the same defect as the badge cases, expressed through primitive props rather than utility classes.",
-        expectedUiState: "The member-count pill is readable against the branded card in both themes. A pill whose number is invisible while the pill shape is visible is the failure.",
-        endResult: "Read-only; return the site to light mode afterwards.",
-    },
-    "checklist-design-ux-status-badge-legibility-image-lightbox-close-hover": {
-        roles: ["guest"],
-        startPage: "/products/product-beyblade-burst-valkyrie",
-        steps: [
-            "Open /products/product-beyblade-burst-valkyrie in a private window.",
-            "Click the main image to open the lightbox.",
-            "Find the close control and read it at rest.",
-            "Hover it and read it while hovering.",
-            "Hover each of the other toolbar controls — zoom, rotate, expand — and read each.",
-            "Switch to dark mode and repeat.",
-        ],
-        expectedBehaviour: "The lightbox toolbar sits on a fixed dark scrim, which is one of the few places a fixed light hover fill is correct — expressed as white with an alpha rather than as a named palette tint. A named tint is the same near-white in both themes and swallows the icon on hover.",
-        expectedUiState: "The close control and every toolbar control stay visible while hovered, in both themes. An icon that disappears under its own hover fill is the failure, and it only shows with the pointer actually over it.",
-        endResult: "Read-only; return the site to light mode afterwards.",
-    },
-};

package/dist/features/tester/seed-data/authored/design-ux__sticky-cta-bar.d.ts

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