@mohasinac/appkit 4.57.0 → 4.59.0

package/dist/features/tester/seed-data/authored/cta-layout__editor-action-bar.js

@@ -1,62 +0,0 @@
-/*
- * WHY: Authored six-part procedures for the cta-layout/editor-action-bar page.
- * WHAT: 1 case, 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.
- *
- * 🛑 /store/products/new OPENS THE QUICK FORM, NOT THIS BAR (corrected
- * 2026-09-29). SellerProductShell picks formMode 'quick' whenever mode is
- * create and the listing type is standard, and QuickProductForm's action row
- * has TWO buttons — 'Publish' and 'Save Draft' — plus a ghost
- * 'Show all fields (advanced)' beneath them. No Discard, no Preview, and no
- * four-button bar to overflow. The case has to take the advanced switch first.
- *
- * 🛑 AND THE FULL FORM'S BAR HOLDS THREE, NOT FOUR. FormShell's ActionRow is
- * Discard as the `anchor` (a ghost button, ALWAYS present rather than appearing
- * when the form goes dirty), then Save draft, then Publish. Preview is not in
- * this row at all — it lives in the FormShell TOP bar, and only when a preview
- * slot is supplied. A case counting four buttons in one row is counting a
- * button that is somewhere else.
- *
- * The labels differ between the generic shell and this editor, so the case asks
- * the tester to RECORD what they read rather than asserting one spelling:
- * FORM_ACTION_META says 'Discard' / 'Save Draft' / 'Publish', while
- * SellerProductShell renders 'Save as draft & finish later' and
- * 'Publish {listingTypeLabel}'. Either way the layout question — does anything
- * run off the right edge at 375px — is unchanged, and that is the case.
- *
- * @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-cta-layout-editor-action-bar-four-buttons-wrap-not-overflow": {
-        roles: ["seller"],
-        startPage: "/store/products/new",
-        steps: [
-            "Resize the browser window to 375 pixels wide.",
-            "Sign in as tyson@beybladearena.in / TempPass123!.",
-            "Open /store/products/new and read its action row. This is the QUICK form: expect two buttons, Publish and Save Draft, and a ghost link reading 'Show all fields (advanced)'.",
-            "Click 'Show all fields (advanced)' to reach the full editor.",
-            "Type 'QA Product editor-action-bar' in the Product Name field.",
-            "Read the action bar and write down every button in it, in order, with its exact label.",
-            "Try to scroll the page sideways.",
-            "Read the right edge of the bar for any button that is partly off screen, and the left edge for Discard — it is anchored there rather than sitting beside the other two.",
-        ],
-        inputs: {
-            viewportWidth: 375,
-            title: "QA Product editor-action-bar",
-            quickFormButtons: 2,
-            fullFormButtons: 3,
-        },
-        expectedBehaviour: "Actions that cannot fit one row wrap onto a second. They used to be non-shrinking children of a non-wrapping row, which does not overflow gracefully — it simply runs off the right edge, taking the last button with it. Discard is the row's anchor rather than a third sibling, because a flat justify-between row with three children opened the gap between Save draft and Publish instead of beside Discard.",
-        expectedUiState: "Every button in the bar is fully visible, wrapping onto a second line as needed. Nothing is cut off at the right edge and the page does not scroll sideways at all. Expect THREE in the full editor — a Discard anchored left, a save and a publish — and do not count Preview: it is in the top bar, not this row, and only when a preview slot is supplied. Record the exact labels you read; they differ between the generic shell and this editor.",
-        expectedData: { quickFormButtonCount: 2, fullFormButtonCount: 3, horizontalScroll: false },
-        endResult: "Leave the editor without saving, so no draft product is created. Restore the window width afterwards.",
-    },
-};

package/dist/features/tester/seed-data/authored/cta-layout__navbar-ctas.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/cta-layout__navbar-ctas.js

@@ -1,163 +0,0 @@
-/*
- * WHY: Authored six-part procedures for the cta-layout/navbar-ctas checklist page.
- * WHAT: 8 case(s), keyed by full checklist id.
- *
- * The header is mounted once in a persistent shell and does NOT re-mount on
- * client-side navigation. Everything below follows from that: a badge cannot
- * correct itself by re-mounting, a signed-in state cannot appear by reloading,
- * and an active-section marker has to be derived from the current path rather
- * than set once on first render.
- *
- * 🛑 CLEARING THE ANNOUNCEMENT DOES NOT REMOVE THE BAR (corrected 2026-09-29).
- * MarketplaceHomepageView reads
- *   announcementBar.message?.trim() || SECTION_COPY.announcementFallback
- * and gates on `announcementBar.enabled ?? true`. So an empty message falls back
- * to 'Free shipping on eligible orders — shop the latest arrivals.'
- * and the bar stays. Removing it means turning OFF 'Show announcement bar'. The
- * last case told the tester to clear the message and check the bar left the
- * homepage, which would have reported correct fallback behaviour as a defect.
- *
- * The seed ships enabled:true with a real message, so no setup toggle is needed,
- * and the ONLY surface that renders it is the homepage.
- *
- * Verified fixed before asserting: the editor writes announcementBar.message,
- * which is the key the renderer reads — the historical bug wrote `text`, a key
- * nothing has ever read, so every announcement saved and none appeared. A pass
- * is the expected result here.
- *
- * @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-cta-layout-navbar-ctas-header-ctas-all-navigate": {
-        roles: ["guest"],
-        startPage: "/",
-        steps: [
-            "Open the homepage signed out.",
-            "List every clickable control in the header, including the logo and any icon-only ones.",
-            "Click each in turn, noting where it lands and returning each time.",
-            "Record any that does nothing.",
-            "Record any that 404s.",
-            "Check the logo returns to the homepage.",
-        ],
-        expectedBehaviour: "Every header control goes somewhere real. An inert control is the harder half to notice — it looks like a slow page rather than a broken link, so the visitor waits and then clicks it again.",
-        expectedUiState: "Every control navigates to a real page and the logo returns home. Any control that does nothing, or 404s, is a finding named by its label or icon.",
-        expectedData: { deadHeaderControls: 0 },
-        endResult: "Read-only.",
-    },
-    "checklist-cta-layout-navbar-ctas-header-cart-badge-live": {
-        roles: ["buyer"],
-        startPage: "/",
-        steps: [
-            "Sign in as rehan.sheikh@gmail.com / TempPass123!. No cart is seeded for this buyer, so the badge should start empty — if it does not, empty the cart before continuing.",
-            "Read the header's cart control and its badge.",
-            "Add a product from /products and read the badge without reloading.",
-            "Add a second and read it again.",
-            "Navigate to two other pages and read the badge on each.",
-            "Open /cart, remove an item, and read the badge.",
-        ],
-        expectedBehaviour: "The badge reads the same cart the pages read, so it tracks every change with no reload. The header never re-mounts across navigation, so a badge holding its own count cannot correct itself — it keeps a stale number for the rest of the session.",
-        expectedUiState: "The badge follows every add and removal immediately and stays correct across navigation. A count that lags or freezes is the finding.",
-        endResult: "Empty the cart afterwards.",
-    },
-    "checklist-cta-layout-navbar-ctas-header-signed-out-vs-in": {
-        roles: ["guest", "buyer"],
-        startPage: "/",
-        steps: [
-            "Open the homepage signed out and read the header's account area.",
-            "Check a sign-in affordance is offered.",
-            "Sign in as rehan.sheikh@gmail.com / TempPass123! from that control.",
-            "Read the header immediately after signing in, WITHOUT reloading.",
-            "Check it now shows an account menu.",
-            "Sign out and read the header again without reloading.",
-        ],
-        expectedBehaviour: "The header switches with the session and without a reload. The session resolves asynchronously on a hard load, so the header may briefly not know who the visitor is — but once it does, the change has to reach the persistent header rather than waiting for the next full page load.",
-        expectedUiState: "Signed out shows sign-in; signed in shows an account menu; each switch happens without a reload. A header still offering sign-in after a successful sign-in is the finding.",
-        endResult: "Signed out.",
-    },
-    "checklist-cta-layout-navbar-ctas-account-menu-links-resolve": {
-        roles: ["buyer", "seller", "admin"],
-        startPage: "/",
-        steps: [
-            "Sign in as rehan.sheikh@gmail.com / TempPass123! and open the account menu.",
-            "Click every item in it, noting where each lands and returning each time.",
-            "Record any 404 or unauthorised page.",
-            "Repeat signed in as tyson@beybladearena.in / TempPass123!.",
-            "Repeat signed in as admin@letitrip.in / TempPass123!.",
-        ],
-        expectedBehaviour: "Every account-menu item lands on a page that role can actually open. A menu entry pointing at a route with no page behind it is a dead link, and one pointing at a page the role cannot access bounces them to an unauthorised screen from their own menu.",
-        expectedUiState: "Every item resolves for its role. A 404 or an unauthorised redirect is a finding, named with the role and the item.",
-        expectedData: { deadMenuLinks: 0 },
-        endResult: "Read-only.",
-    },
-    "checklist-cta-layout-navbar-ctas-role-specific-nav-entries": {
-        roles: ["buyer", "seller", "admin"],
-        startPage: "/",
-        steps: [
-            "Sign in as rehan.sheikh@gmail.com / TempPass123! and write down every navigation entry offered.",
-            "Check no store or admin entry is among them.",
-            "Sign in as tyson@beybladearena.in / TempPass123! and write down the entries.",
-            "Check a store entry is present and no admin entry is.",
-            "Sign in as admin@letitrip.in / TempPass123! and check an admin entry is present.",
-            "Compare the three lists.",
-        ],
-        expectedBehaviour: "Navigation reflects the role. A role check written inline against a role string rather than through the shared predicate drifts from every other check in the product — and the visible symptom is a buyer offered a dashboard that will refuse them.",
-        expectedUiState: "The buyer sees neither store nor admin entries, the seller sees store and not admin, the admin sees admin. Any entry offered to a role that cannot use it is the finding.",
-        endResult: "Read-only.",
-    },
-    "checklist-cta-layout-navbar-ctas-mobile-nav-opens-and-closes": {
-        roles: ["guest"],
-        startPage: "/",
-        steps: [
-            "Resize the browser to 390 pixels wide and open the homepage.",
-            "Open the mobile navigation.",
-            "Check it covers the page and its items are readable.",
-            "Close it with its own control and check it closes.",
-            "Open it again and follow a link.",
-            "Check the navigation closed itself on the new page rather than staying over it.",
-        ],
-        inputs: { mobileWidth: 390 },
-        expectedBehaviour: "The mobile navigation closes on its own control AND after a link is followed. It lives in a shell that does not re-mount on navigation, so nothing closes it automatically — a menu left open sits over the page the visitor just asked for.",
-        expectedUiState: "It opens, closes on its control, and is closed on the destination page after a link. A menu still covering the new page is the finding.",
-        endResult: "Restore the window width.",
-    },
-    "checklist-cta-layout-navbar-ctas-nav-active-state-correct": {
-        roles: ["guest"],
-        startPage: "/",
-        steps: [
-            "Open the homepage and read which navigation entry is marked as current.",
-            "Navigate to /products and read which is marked.",
-            "Navigate to /products/product-beyblade-original-dranzer-s and read which is marked.",
-            "Navigate to /events and read which is marked.",
-            "Use the browser's back button twice and read the marker each time.",
-        ],
-        expectedBehaviour: "The marker is derived from the current path, so it follows client-side navigation and the back button. Set once on first render, it would freeze on whichever section the visitor happened to land on first and stay there for the whole session.",
-        expectedUiState: "The correct entry is marked on every page including the detail page, and it follows the back button. A marker stuck on one section is the finding.",
-        endResult: "Read-only.",
-    },
-    "checklist-cta-layout-navbar-ctas-announcement-bar-message-renders": {
-        roles: ["admin", "guest"],
-        startPage: "/admin/site",
-        steps: [
-            "Sign in as admin@letitrip.in / TempPass123! and open Site Settings.",
-            "Open the 'Announcement' tab, write down the current message, and confirm 'Show announcement bar' is already on.",
-            "Set the message to 'QA announcement probe — checklist case.' and save.",
-            "Sign out and open / . Read whether the announcement appears and whether the text matches exactly.",
-            "Sign back in, CLEAR the message and save, then reload / . The bar should still be there, now reading the fallback: 'Free shipping on eligible orders — shop the latest arrivals.'",
-            "Turn 'Show announcement bar' OFF, save, and reload / . NOW the bar should be gone.",
-            "Restore the original message and turn the toggle back on.",
-        ],
-        inputs: {
-            message: "QA announcement probe — checklist case.",
-            fallback: "Free shipping on eligible orders — shop the latest arrivals.",
-            toggle: "Show announcement bar",
-        },
-        expectedBehaviour: "An announcement an admin saves appears. The editor once wrote the copy under a key no renderer has ever read, so every announcement saved successfully and none of them appeared — a save that reports success while writing to a field with no reader is invisible from both ends.",
-        expectedUiState: "The exact text appears in the announcement bar on the homepage. Clearing the message does NOT remove the bar — it falls back to 'Free shipping on eligible orders — shop the latest arrivals.', which is correct and must not be reported as a defect. Only turning the toggle off removes it. A successful save with the OLD text still on the homepage is the finding.",
-        endResult: "The announcement is cleared.",
-    },
-};

package/dist/features/tester/seed-data/authored/cta-layout__product-bottom-bar.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/cta-layout__product-bottom-bar.js

@@ -1,61 +0,0 @@
-/*
- * WHY: Authored six-part procedures for the cta-layout/product-bottom-bar page.
- * WHAT: 1 case, 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.
- *
- * Verified against ProductDetailActions on 2026-09-29. The mobile bar registers
- * three actions with DISTINCT variants, not two secondaries and a primary:
- *
- *   ghost    Wishlist  (reads 'Saved' and is DISABLED once wishlisted)
- *   outline  Add to Cart  (reads 'Adding…' while busy)
- *   primary  Buy Now      (reads 'Out of Stock' when stock is 0)
- *
- * It also publishes an `infoLabel` carrying the price, which doubles as the
- * bar's re-publish key. Signed in that reads the formatted price; signed out it
- * reads 'Sign in to see price' — so the bar is also where the guest price gate
- * is visible on this page, and a buyer who sees that string is looking at a
- * session that did not resolve.
- *
- * 🛑 product-beyblade-original-dranzer-s is stock 4 and not sold, so the
- * labels are Buy Now / Add to Cart rather than Out of Stock, and it is NOT in
- * this buyer's wishlist: the three seeded wishlists belong to user-yugi-muto,
- * user-seto-kaiba and user-admin-letitrip. So Wishlist is enabled and reads
- * 'Wishlist'. If it reads 'Saved' and is disabled, an earlier case added it
- * and that is not a defect.
- *
- * @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-cta-layout-product-bottom-bar-three-actions-wrap-to-second-row": {
-        roles: ["buyer"],
-        startPage: "/products/product-beyblade-original-dranzer-s",
-        steps: [
-            "Resize the browser window to 375 pixels wide.",
-            "Sign in as rehan.sheikh@gmail.com / TempPass123!.",
-            "Open /products/product-beyblade-original-dranzer-s.",
-            "Read the bottom action bar and note which buttons share a row.",
-            "Compare the widths of the two buttons on the upper row.",
-            "Read the price shown on the bar — signed in it should read the formatted price, 1,499 for this product.",
-            "Click 'Add to Cart' and watch the bar while the label changes.",
-            "Count the rows in the bar during and after the change.",
-        ],
-        inputs: {
-            viewportWidth: 375,
-            productId: "product-beyblade-original-dranzer-s",
-            price: 1499,
-            expectedRows: 2,
-        },
-        expectedBehaviour: "Three actions of different weight are laid out as two secondaries sharing a row above one full-width primary. The secondaries share that row proportionally rather than one being pinned to its content width, which is what made the row read lopsided before.",
-        expectedUiState: "'Wishlist' and 'Add to Cart' occupy the upper row and neither is squeezed to a fraction of the other. 'Buy Now' spans the full width beneath them. The bar shows the price, which for a signed-in buyer reads the formatted amount and never 'Sign in to see price'. While the label reads 'Adding…' the bar still has exactly two rows — a bar that reflows to three rows and back makes the whole page jump under the buyer's thumb mid-tap.",
-        expectedData: { barRowCount: 2, priceOnBar: 1499 },
-        endResult: "The item is in the cart. Restore the window width and empty the cart afterwards so later cases start clean.",
-    },
-};

package/dist/features/tester/seed-data/authored/design-ux__action-bar-placement.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__action-bar-placement.js

@@ -1,89 +0,0 @@
-/*
- * WHY: Authored six-part procedures for the design-ux/action-bar-placement 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-action-bar-placement-back-to-top-dismiss-visible": {
-        roles: ["guest"],
-        startPage: "/products",
-        steps: [
-            "Open /products and scroll down more than about 400 pixels.",
-            "Look at the floating controls in the bottom corner of the window.",
-            "Click the smaller of the two controls.",
-            "Navigate to /auctions and scroll past 400 pixels again.",
-        ],
-        expectedBehaviour: "The dismiss control is an icon button sized as a true square, so its glyph has room to render. Dismissal is in-memory and resets on route change, so it never hides the control for the rest of the session.",
-        expectedUiState: "TWO round controls are visible: a larger one showing an upward chevron, and a smaller one showing a clearly visible ✕. The prior symptom was the smaller control rendering as an EMPTY outlined pill — present and clickable, with no ✕ inside it, because its content box computed to zero width. After clicking the ✕, both controls disappear.",
-        endResult: "On /auctions both controls are back after scrolling. Nothing is persisted — a reload also brings them back.",
-    },
-    "checklist-design-ux-action-bar-placement-action-bar-top-on-desktop": {
-        roles: ["guest"],
-        startPage: "/products",
-        steps: [
-            "Maximise the browser window so it is wider than about 1024 pixels.",
-            "Open any product detail page from /products.",
-            "Look immediately below the site header.",
-            "Scroll the page down and watch the bar.",
-        ],
-        expectedBehaviour: "At `lg` and up the chrome tier is pinned under the header rather than to the bottom edge, and its shadow is cast downward onto the page.",
-        expectedUiState: "The full-width action bar sits directly beneath the header with no gap, and stays there while the page scrolls. Its drop shadow falls DOWNWARD. It must NOT be at the bottom of the window — that was the prior behaviour at every width.",
-        endResult: "Nothing persists; this is layout only. The bar stays under the header for the whole visit at this width.",
-    },
-    "checklist-design-ux-action-bar-placement-action-bar-bottom-on-mobile": {
-        roles: ["guest"],
-        startPage: "/products",
-        steps: [
-            "On the same product detail page, narrow the browser window to phone width (under about 1024 pixels), or switch to device emulation.",
-            "Look at the bottom of the window.",
-            "Slowly widen the window back past the 1024-pixel line, then narrow it again.",
-        ],
-        expectedBehaviour: "One component serves both layouts, switching on a media query, so the bar must move between the two positions rather than being duplicated or dropped.",
-        expectedUiState: "At phone width the action bar is at the BOTTOM, stacked immediately above the bottom navigation bar, with its shadow falling UPWARD. While resizing across the breakpoint the bar moves cleanly from one end to the other — it is never visible in BOTH places at once, and never disappears entirely at any width.",
-        endResult: "No state is written. The bar's position always matches the current window width, including after a reload at either width.",
-    },
-    "checklist-design-ux-action-bar-placement-action-bar-no-content-overlap": {
-        roles: ["guest"],
-        startPage: "/products",
-        steps: [
-            "At desktop width, open a product detail page that shows an action bar.",
-            "Read the very first line of page content under the header.",
-            "Now open a page with no action bar at all, such as /about.",
-            "Look at the space immediately under the header.",
-        ],
-        expectedBehaviour: "The bar is fixed, so it is out of flow and would cover content unless space is reserved. `<Main>` reserves exactly the published tier height, which is zero when no bar exists — so the reservation appears and disappears with the bar rather than being a constant allowance.",
-        expectedUiState: "With a bar present, the first heading and first row of content are fully visible and not clipped behind it. On /about, with no bar, there is NO empty band under the header — the content starts where it always did.",
-        endResult: "Nothing persists. Navigating between a page with a bar and one without must not leave a residual gap on the page that has none.",
-    },
-    "checklist-design-ux-action-bar-placement-action-bar-panels-open-into-screen": {
-        roles: ["admin"],
-        startPage: "/admin/products",
-        steps: [
-            "Sign in as admin@letitrip.in / TempPass123! and open /admin/products at desktop width.",
-            "Tick the checkboxes on two rows to enter bulk mode.",
-            "Open the bulk action-type picker on the bar.",
-            "Narrow the window to phone width and open the same picker again.",
-        ],
-        expectedBehaviour: "The panel is positioned against the bar, so its open direction must follow whichever screen edge the bar is attached to. Opening away from the screen would put the panel partly or wholly out of view.",
-        expectedUiState: "At desktop width the picker expands DOWNWARD over the page content, below the bar. At phone width it expands UPWARD from the bar. In both cases the whole panel is on screen and scrollable, and no part of it is cut off by the window edge.",
-        endResult: "Closing the picker leaves the bulk selection intact. Clearing the selection removes the bar and the panel together.",
-    },
-    "checklist-design-ux-action-bar-placement-back-to-top-clears-the-bar": {
-        roles: ["guest"],
-        startPage: "/products",
-        steps: [
-            "At phone width, open a product detail page with an action bar and scroll past 400 pixels.",
-            "Look at the vertical gap between the back-to-top control and the action bar.",
-            "Slowly widen the window past the desktop breakpoint, watching the control.",
-        ],
-        expectedBehaviour: "The back-to-top offset is expressed against the measured tier rather than against any individual bar, so it tracks the bar's height automatically — and when the tier moves to the top on desktop, the bottom measurement collapses to zero and the control settles lower.",
-        expectedUiState: "At phone width the control floats clear ABOVE the action bar, which itself sits above the bottom navigation — none of the three overlap. As the window widens past the breakpoint the control moves DOWN into the space the bar vacated. At no point during the resize do the control and any bar overlap.",
-        endResult: "Position is derived from layout alone and nothing is stored; reloading at either width reproduces the same spacing.",
-    },
-};

package/dist/features/tester/seed-data/authored/design-ux__back-to-top-button.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__back-to-top-button.js

@@ -1,95 +0,0 @@
-/*
- * WHY: Authored six-part procedures for the design-ux/back-to-top-button page.
- * WHAT: 5 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.
- *
- * The bottom edge is three declared tiers with exactly three variables and three
- * writers: the keyboard inset, the mobile tab bar, and one container measuring
- * everything between. This control consumes all three — which is why "does it
- * clear the CTA bar" is a case rather than a detail.
- *
- * @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-back-to-top-button-appears-and-clickable-on-long-page": {
-        roles: ["guest"],
-        startPage: "/products",
-        steps: [
-            "Open /products in a private window at a desktop width of 1280 pixels.",
-            "Look for the back-to-top control before scrolling.",
-            "Scroll down past 400 pixels.",
-            "Look for the control again and read what it shows.",
-            "Click it.",
-        ],
-        inputs: { viewportWidth: 1280, revealScrollPx: 400 },
-        expectedBehaviour: "The control is hidden at the top of the page, where it would do nothing, and appears once there is somewhere to return to. It must be genuinely clickable rather than sitting behind another fixed element.",
-        expectedUiState: "Nothing is shown before scrolling. After 400 pixels the control appears and responds to a click. A control that appears but does not respond means something transparent is on top of it.",
-        endResult: "Read-only; nothing persists.",
-    },
-    "checklist-design-ux-back-to-top-button-above-sticky-buy-bar": {
-        roles: ["guest"],
-        startPage: "/products/product-beyblade-original-dranzer-s",
-        steps: [
-            "Open /products/product-beyblade-original-dranzer-s in a private window at 1280 pixels wide.",
-            "Scroll down past 400 pixels so both the sticky buy bar and the back-to-top control are showing. Both reveal at exactly 400 — BottomActions.DESKTOP_REVEAL_SCROLL_PX and BackToTop's own default threshold are the same number — so on desktop they appear on the SAME scroll tick and any overlap is deterministic rather than a matter of timing. There is no need to hunt for the moment they collide.",
-            "Look at where the back-to-top control sits relative to the buy bar.",
-            "Try to click both the back-to-top control and each button in the buy bar.",
-            "Resize to 390 pixels wide and repeat.",
-        ],
-        inputs: { desktopWidth: 1280, mobileWidth: 390 },
-        expectedBehaviour: "Neither element learns the other's height — both read from the one measured container, so the control clears the bar automatically and a bar added later is covered with no edit. The desktop reveal threshold for the buy bar is the SAME 400 pixels, so the two appear on the same scroll tick and the overlap is guaranteed rather than occasional.",
-        expectedUiState: "The back-to-top control sits fully above the buy bar with a visible gap, at both widths. It does not overlap any buy-bar button, and every button in the bar is clickable.",
-        endResult: "Read-only; nothing persists. Restore the window width afterwards.",
-    },
-    "checklist-design-ux-back-to-top-button-scrolls-to-top": {
-        roles: ["guest"],
-        startPage: "/products",
-        steps: [
-            "Open /products in a private window and scroll to the bottom of the grid.",
-            "Click the back-to-top control.",
-            "Watch the page as it moves.",
-            "Read what is at the top of the viewport when it stops.",
-            "Read the address bar.",
-        ],
-        expectedBehaviour: "The control scrolls the window to the top of the current page. It is not a navigation — the URL, the filters and the page of results are all unchanged.",
-        expectedUiState: "The page ends at the top with the header and toolbar visible. The URL is unchanged, the same filters are still applied, and the same page of results is still loaded — a jump back to page one would be a navigation wearing a scroll control's clothes.",
-        endResult: "Read-only; nothing persists.",
-    },
-    "checklist-design-ux-back-to-top-button-dismiss-returns-on-navigation": {
-        roles: ["guest"],
-        startPage: "/products",
-        steps: [
-            "Open /products in a private window and scroll past 400 pixels so the control appears.",
-            "Click its close or dismiss control.",
-            "Scroll up and down again and check whether it returns.",
-            "Navigate to /auctions WITHOUT reloading — click a link rather than typing the URL.",
-            "Scroll past 400 pixels and look for the control.",
-        ],
-        expectedBehaviour: "Dismissal lasts for the current page and is reset on the next navigation. This control lives in a shell that does NOT remount when the route changes, so a dismissal stored in browser storage reads as permanent: one click hid it until the tab was closed, with no way to bring it back.",
-        expectedUiState: "After dismissing, the control stays hidden on /products however much the page is scrolled. After navigating to /auctions it returns on scroll. A control still hidden after navigation is the failure.",
-        endResult: "Read-only; nothing persists.",
-    },
-    "checklist-design-ux-back-to-top-button-not-covering-toast-or-modal-actions": {
-        roles: ["buyer"],
-        startPage: "/products/product-beyblade-burst-valkyrie",
-        steps: [
-            "Sign in as rehan.sheikh@gmail.com / TempPass123!.",
-            "Open /products/product-beyblade-burst-valkyrie and scroll past 400 pixels so the control appears.",
-            "Click 'Add to Cart' and watch for a toast.",
-            "Look at whether the control overlaps the toast or any control inside it.",
-            "Open any modal on the page and look at its footer buttons.",
-            "Try to click each footer button.",
-        ],
-        expectedBehaviour: "The control yields to transient and modal UI. A toast carries actions and a modal footer carries the decision — a floating control on top of either takes a click the user meant for something else.",
-        expectedUiState: "The toast is fully visible and its controls are clickable. The modal's footer buttons are unobstructed and every one responds. The back-to-top control either sits clear of both or is hidden while they are open.",
-        endResult: "Remove the item from the cart afterwards so later cases start from an empty cart.",
-    },
-};

package/dist/features/tester/seed-data/authored/design-ux__carousel-arrow-bounds.d.ts

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