@mohasinac/appkit 4.42.0 → 4.42.2

package/dist/features/tester/seed-data/authored/design-ux__back-to-top-button.js

@@ -39,7 +39,7 @@ export const authored = {
         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.",
+            "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.",

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

@@ -22,7 +22,7 @@ export const authored = {
         roles: ["guest"],
         startPage: "/",
         steps: [
-            "Open / in a private window at 1280 pixels wide.",
+            "Open / in a private window at 1280 pixels wide. 🛑 EVERY STEP BELOW MEANS THE CARD CAROUSELS — 'Featured Products', 'Live Auctions', 'Shop by Category', 'Reserve Before It Ships' — and NOT the full-bleed hero slider at the top of the page, which is a different component with its own arrows and its own behaviour. Reading the hero instead is the easiest way to record a finding about the wrong thing.",
             "Scroll to a horizontal card carousel.",
             "Look at the left and right arrows and what sits under each.",
             "Read the title and the price row (signed out that row reads 'Sign in to see price') of the first and last visible cards.",
@@ -37,7 +37,7 @@ export const authored = {
         roles: ["guest"],
         startPage: "/",
         steps: [
-            "Open / in a private window at 1280 pixels wide and scroll to a card carousel.",
+            "Open / in a private window at 1280 pixels wide and scroll to the 'Featured Products' carousel.",
             "Click the right arrow once and watch the cards move.",
             "While the cards are still moving, look at where the arrows are.",
             "Let it settle and look again.",
@@ -52,7 +52,7 @@ export const authored = {
         startPage: "/",
         steps: [
             "Resize the browser window to 390 pixels wide and open / in a private window.",
-            "Scroll to a card carousel and look for arrows.",
+            "Scroll to the 'Featured Products' carousel and look for arrows.",
             "Swipe the rail and check it moves.",
             "Resize to 1280 pixels and look for the arrows again.",
         ],
@@ -66,7 +66,7 @@ export const authored = {
         startPage: "/",
         steps: [
             "Resize the browser window to 390 pixels wide and open / in a private window.",
-            "Scroll to a card carousel and look at the first card's left edge.",
+            "Scroll to the 'Featured Products' carousel and look at the first card's left edge.",
             "Look at the last card's right edge after swiping to the end.",
             "Read each visible card's title and price row in full.",
             "Try to scroll the page sideways rather than the rail.",
@@ -81,7 +81,7 @@ export const authored = {
         startPage: "/",
         steps: [
             "Resize the browser window to 390 pixels wide and open / in a private window.",
-            "Scroll to a card carousel and swipe it left with a short flick.",
+            "Scroll to the 'Featured Products' carousel and swipe it left with a short flick.",
             "Watch where it comes to rest.",
             "Swipe again with a long flick and watch where it rests.",
             "Swipe back to the start.",
@@ -95,7 +95,7 @@ export const authored = {
         roles: ["guest"],
         startPage: "/",
         steps: [
-            "Open / in a private window in light mode at 1280 pixels and scroll to a card carousel.",
+            "Open / in a private window in light mode at 1280 pixels and scroll to the 'Featured Products' carousel.",
             "Look at the left and right edges of the rail for a fade or gradient overlay.",
             "Switch to dark mode and look at the same edges.",
             "Scroll the rail to the middle and look again in dark mode.",
@@ -108,7 +108,7 @@ export const authored = {
         roles: ["guest"],
         startPage: "/",
         steps: [
-            "Open / in a private window at 1280 pixels and find a carousel whose cards wrap to two rows, or a taller card variant.",
+            "Open / in a private window at 1280 pixels and find a carousel whose cards are TALLER than the Featured Products row — 'Live Auctions' carries a countdown and bid line, so its cards run taller than a plain product card. If no section on the page wraps to two rows, say so and test the tallest single row instead rather than hunting for a layout that may not exist.",
             "Look at the arrows' vertical position relative to the rail.",
             "Check whether they are centred on the full height or on one row.",
             "Click each and check it scrolls the whole rail.",
@@ -122,7 +122,7 @@ export const authored = {
         startPage: "/",
         steps: [
             "Open / in a private window and switch to dark mode.",
-            "Scroll to a card carousel and look at both arrows.",
+            "Scroll to the 'Featured Products' carousel and look at both arrows.",
             "Hover each and look at it while hovering.",
             "Compare their visibility against light mode.",
         ],
@@ -134,7 +134,7 @@ export const authored = {
         roles: ["guest"],
         startPage: "/",
         steps: [
-            "Open / in a private window at 1280 pixels and scroll to a card carousel.",
+            "Open / in a private window at 1280 pixels and scroll to the 'Featured Products' carousel.",
             "Look at the left arrow while the rail is at its start.",
             "Click right repeatedly to the end of the rail.",
             "Look at the right arrow at the end and at the rail's position.",
@@ -148,7 +148,7 @@ export const authored = {
         roles: ["guest"],
         startPage: "/",
         steps: [
-            "Open / in a private window at 1280 pixels and scroll to a card carousel.",
+            "Open / in a private window at 1280 pixels and scroll to the 'Featured Products' carousel.",
             "Slowly resize the window down through 1024, 768 and 640 to 390 pixels, watching the rail throughout.",
             "Note the width at which the arrows disappear.",
             "Slowly resize back up to 1280, watching the rail.",

package/dist/features/tester/seed-data/authored/design-ux__dashboard-layout.js

@@ -24,7 +24,7 @@ export const authored = {
         startPage: "/admin",
         steps: [
             "Sign in as admin@letitrip.in / TempPass123!.",
-            "Open /admin and read the sidebar's group headings.",
+            "Open /admin — it redirects to the admin dashboard, which is expected — and read the sidebar's group headings. There are TWELVE, and exactly one, 'Guides', ships defaultOpen:false, so a group already closed on arrival is the fixture rather than a collapse you caused.",
             "Collapse one expanded group and read what remains.",
             "Expand a collapsed group and read its contents.",
             "Navigate to another admin page using the sidebar.",
@@ -40,7 +40,7 @@ export const authored = {
         startPage: "/store",
         steps: [
             "Sign in as tyson@beybladearena.in / TempPass123!.",
-            "Open /store and read the sidebar's group headings.",
+            "Open /store and read the sidebar's group headings. There are SIX — Overview, Listings, Orders & Reviews, Finance, Store, Guides — and the last, 'Guides', ships defaultOpen:false.",
             "Collapse one expanded group and read what remains.",
             "Expand a collapsed group and read its contents.",
             "Navigate to another store page using the sidebar and read the state.",
@@ -55,7 +55,7 @@ export const authored = {
         startPage: "/user",
         steps: [
             "Sign in as rehan.sheikh@gmail.com / TempPass123!.",
-            "Open /user and read the sidebar's group headings.",
+            "Open /user and read the sidebar's group headings. There are FIVE, and none ships collapsed — so on this portal every group should be open on arrival, which makes an already-closed one a real finding here rather than the fixture.",
             "Collapse one expanded group and read what remains.",
             "Expand a collapsed group and read its contents.",
             "Navigate to another user page using the sidebar and read the state.",

package/dist/features/tester/seed-data/authored/design-ux__footer-theme.js

@@ -38,8 +38,8 @@ export const authored = {
         startPage: "/",
         steps: [
             "Open / in a private window and scroll to the footer.",
-            "Find the GitHub icon and look at its size relative to the other social icons.",
-            "Hover it and read any tooltip or label.",
+            "Find the GitHub icon and look at its size relative to the other social icon. There are exactly TWO — WhatsApp and GitHub, both inline SVGs at w-4 h-4 in src/constants/footer.tsx — so 'the other social icons' means one neighbour, and any size difference between two identically-classed SVGs is a real finding rather than a judgement call.",
+            "Hover it and read any tooltip or label. Its aria-label reads 'View the developer’s GitHub profile' — with a straight apostrophe in source — so a screen-reader label that differs, or is missing, is the finding.",
             "Click it and read where it lands.",
             "Switch to dark mode and look at the icon again.",
         ],

package/dist/features/tester/seed-data/authored/design-ux__form-validation-errors.js

@@ -59,8 +59,8 @@ export const authored = {
         startPage: "/store/products/new",
         steps: [
             "Sign in as tyson@beybladearena.in / TempPass123!.",
-            "Open /store/products/new, a multi-step wizard.",
-            "Advance past the first step leaving a required field on it empty, and continue to a later step.",
+            "Open /store/products/new and click 'Show all fields (advanced)'. 🛑 IT IS NOT A WIZARD BY DEFAULT: a standard create opens the QUICK form — six flat fields, no steps at all — so there is no step for an error to be tagged with until you switch. The advanced form is the sectionised one this case is about.",
+            "Advance past the first section leaving a required field on it empty, and continue to a later section.",
             "Leave a required field on that later step empty too.",
             "Attempt to publish.",
             "Read the summary and note whether each error names the step it belongs to.",

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

@@ -57,7 +57,7 @@ export const authored = {
         steps: [
             "Open / in a private window and find the theme control.",
             "Switch to dark mode and read the page.",
-            "Navigate to /products, then to a product page, reading each.",
+            "Navigate to /products, then to /products/product-beyblade-burst-valkyrie, reading each.",
             "Reload the page and watch the first moment it paints.",
             "Set the theme control to follow the system setting and change the system theme.",
         ],
@@ -72,7 +72,7 @@ export const authored = {
             "Open browser DevTools and throttle the network to a slow connection.",
             "Open /products in a private window and watch the page while it loads.",
             "Read what occupies the grid area before the cards arrive.",
-            "Navigate to a product page and watch the same.",
+            "Navigate to /products/product-beyblade-burst-valkyrie and watch the same.",
             "Wait and check the loading state resolves rather than persisting.",
             "Remove the throttle.",
         ],
@@ -130,7 +130,7 @@ export const authored = {
         startPage: "/products",
         steps: [
             "Open /products in a private window and look at the watermark on several card images.",
-            "Open a product page and look at the watermark on the main gallery image.",
+            "Open /products/product-beyblade-burst-valkyrie and look at the watermark on the main gallery image.",
             "Open the image lightbox and look at it there.",
             "Judge whether the product itself is still clearly visible under it.",
             "Look at a video's poster frame and check it carries the watermark too.",
@@ -146,7 +146,7 @@ export const authored = {
             "Open /products/product-beyblade-burst-valkyrie in a private window.",
             "Look at the thumbnail strip below the main image and check each tile shows a picture.",
             "Click a thumbnail and check the main image changes.",
-            "Open a product page that has reviews with photos and look at the 'Photos' grid.",
+            "Open /products/product-beyblade-original-dranzer-s and look at the 'Photos' grid on its reviews. That product is the seed's deep-review fixture — 14 reviews, of which every fourth carries images, so FOUR have photos. Picking any other product risks one with no photo grid at all, and an absent grid is indistinguishable from the collapsed one this case is looking for.",
             "Open the review lightbox and look at its thumbnail strip.",
             "Open /bundles/bundle-original-collectors-set and look at its member collage.",
         ],

package/dist/features/tester/seed-data/authored/design-ux__hand-mode-layout.js

@@ -73,7 +73,7 @@ export const authored = {
             "Sign in as rehan.sheikh@gmail.com / TempPass123! and turn on 'Left-hand mode'.",
             "Open /products and scroll past 400 pixels so the back-to-top control appears.",
             "Note which side of the viewport it is on.",
-            "Open a product detail page, scroll until the purchase bar appears, and check the control still clears the bar.",
+            "Open /products/product-beyblade-burst-valkyrie, scroll until the purchase bar appears, and check the control still clears the bar.",
             "Turn 'Left-hand mode' off and check both again.",
         ],
         inputs: { leftHandMode: true },
@@ -227,12 +227,12 @@ export const authored = {
             "Resize the browser window to 390 pixels wide and open /user.",
             "Look at the bottom tab bar and write down its items in order.",
             "Count the bottom bars present.",
+            "Compare the item order against the public bar from the sibling case (checklist-design-ux-hand-mode-layout-bottom-nav-mirror, on /).",
             "Turn 'Left-hand mode' off and check both again.",
-            "Compare the dashboard's bar against the public one from the previous case.",
         ],
         inputs: { leftHandMode: true, mobileWidth: 390 },
-        expectedBehaviour: "The dashboard renders its own bottom bar and the public one is suppressed on those routes, so exactly one is mounted. Two would be two bars on the same pixels with a height nobody owns, and everything above would be positioned against the wrong one.",
-        expectedUiState: "Exactly one bottom bar on /user in both modes, carrying dashboard destinations rather than the public ones. Item order is unchanged between modes, matching the public bar's behaviour.",
+        expectedBehaviour: "BEFORE (fixed 2026-09-28): /user rendered its own dashboard-specific bottom bar, so this case was testing whether a second, separate implementation happened to mirror the same way as the public one. AFTER: /user renders the exact same shared bottom bar component as every public page — there is only one implementation, so hand-mode mirroring is inherited for free rather than needing its own logic. Exactly one bottom bar is mounted.",
+        expectedUiState: "The /user bottom bar's items and order match the public bar's from the sibling case, in both hand-mode states, because it is literally the same bar. Exactly one bottom bar is present throughout.",
         expectedData: { bottomNavCount: 1 },
         endResult: "The mode is off again by the last step; restore the window width.",
     },

package/dist/features/tester/seed-data/authored/design-ux__homepage-carousels.js

@@ -286,10 +286,10 @@ export const authored = {
     },
     "checklist-design-ux-homepage-carousels-section-config-actually-renders": {
         roles: ["admin", "guest"],
-        startPage: "/admin",
+        startPage: "/admin/sections",
         steps: [
             "Sign in as admin@letitrip.in / TempPass123! and open the homepage sections editor.",
-            "Open one section's configuration and write down every field it offers.",
+            "Open /admin/sections — the homepage sections editor; /admin is only a redirect to the dashboard — then open one section's configuration and write down every field it offers.",
             "Change a visible field — a heading or an item limit — and save.",
             "Open / in a private window and read that section.",
             "Check whether the change is reflected.",
@@ -301,10 +301,10 @@ export const authored = {
     },
     "checklist-design-ux-homepage-carousels-section-save-preserves-other-fields": {
         roles: ["admin"],
-        startPage: "/admin",
+        startPage: "/admin/sections",
         steps: [
             "Sign in as admin@letitrip.in / TempPass123! and open the homepage sections editor.",
-            "Open one section and write down the value of EVERY field it holds.",
+            "Open /admin/sections, then one section, and write down the value of EVERY field it holds.",
             "Change exactly one field and save.",
             "RELOAD the editor and read every field again.",
             "Compare against what was written down.",
@@ -316,10 +316,10 @@ export const authored = {
     },
     "checklist-design-ux-homepage-carousels-carousel-toggles-take-effect": {
         roles: ["admin", "guest"],
-        startPage: "/admin",
+        startPage: "/admin/carousel",
         steps: [
             "Sign in as admin@letitrip.in / TempPass123! and open the carousel or homepage section settings.",
-            "Note which carousel-related toggles are offered and their current states.",
+            "Open /admin/carousel — the flat hero-SLIDE editor, singular; /admin/carousels plural is the named-carousel list and is a different feature — and note which carousel-related toggles are offered and their current states.",
             "Turn one off and save.",
             "Open / in a private window and check whether that behaviour has stopped.",
             "Turn it back on, save, and check the behaviour returns.",
@@ -330,10 +330,10 @@ export const authored = {
     },
     "checklist-design-ux-homepage-carousels-banner-buttons-from-config": {
         roles: ["admin", "guest"],
-        startPage: "/admin",
+        startPage: "/admin/carousel",
         steps: [
             "Sign in as admin@letitrip.in / TempPass123! and open the homepage section holding a banner with buttons.",
-            "Change a button's label to 'QA Banner buttons-from-config' and its destination to /about, then save.",
+            "Open /admin/carousel, the flat hero-slide editor, then change a button's label to 'QA Banner buttons-from-config' and its destination to /about, and save.",
             "Open / in a private window and find that banner.",
             "Read the button's label and click it.",
             "Read where it lands.",

package/dist/features/tester/seed-data/authored/design-ux__status-badge-legibility.js

@@ -87,7 +87,7 @@ export const authored = {
             "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.",
-            "Sign out and sign in as karthik.new@gmail.com / TempPass123!.",
+            "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" },
@@ -100,7 +100,7 @@ export const authored = {
         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.",
+            "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.",

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

@@ -79,7 +79,7 @@ export const authored = {
         ],
         inputs: { productId: "product-beyblade-burst-valkyrie", quantity: 1 },
         expectedBehaviour: "The bar's controls are the real controls, not decorative copies — each performs the same action as its counterpart in the page panel and reflects its own loading state.",
-        expectedUiState: "The label changes while the request runs and the cart badge increases. /cart holds 'Test Gadget — Standard Listing #1'. The wishlist control in the bar also acts rather than doing nothing.",
+        expectedUiState: "The label changes while the request runs and the cart badge increases. /cart holds 'Beyblade Burst Valkyrie' at ₹1,899.00. The wishlist control in the bar also acts rather than doing nothing.",
         endResult: "Empty the cart and the wishlist afterwards so later cases start clean.",
     },
     "checklist-design-ux-sticky-cta-bar-desktop-not-covering-footer": {
@@ -123,7 +123,7 @@ export const authored = {
             "Check the bar offers bidding and not 'Add to Cart'.",
         ],
         expectedBehaviour: "An auction's bar carries the live countdown and a bidding action, because auctions are capability-blocked from the cart. A bar offering Add to Cart here means it is publishing the default rather than the type's own.",
-        expectedUiState: "BEFORE: the bar read '₹15,000.00 · 1 bid' to anyone. AFTER, signed out: it reads 'Sign in to see the bid · 1 bid' — the bid COUNT is not an amount and stays. A ticking countdown whose seconds figure is lower after 3 seconds sits beside it. Its action is 'Place a bid' or Buy Now — never 'Add to Cart'. A frozen countdown is a fail even though the number looks right.",
+        expectedUiState: "BEFORE: the bar read '₹15,000.00 · 1 bid' to anyone. AFTER, signed out: it reads exactly 'Sign in to see price' — the whole label, with the bid-count suffix DROPPED. Record that suffix loss: a bid count is not an amount (it is deliberately excluded from the money-sort list for that reason), so hiding it is inconsistent with the rest of the gate, but it is what the one label-building branch does today and is not this case's pass/fail. A ticking countdown whose seconds figure is lower after 3 seconds sits beside it. Its action is 'Place a bid' or Buy Now — never 'Add to Cart'. A frozen countdown is a fail even though the number looks right.",
         endResult: "Read-only; restore the window width afterwards.",
     },
     "checklist-design-ux-sticky-cta-bar-ended-auction-no-bar": {

package/dist/features/tester/seed-data/authored/page-wiring__data-loss.js

@@ -11,6 +11,21 @@
  * nothing, or wrote the wrong thing. The screen after saving looked correct in
  * every one of them; only the reload told the truth.
  *
+ * 🛑 SLOTS 1-5 ARE ALREADY BOOKED IN THE SEED (corrected 2026-09-29), so the
+ * first case could not start: it told the tester to pull slot 3, and slot 3 is
+ * taken by 'Arjun M'. `maxPullsPerUser` is 1 on this lottery, so a pull is also
+ * a once-per-persona-per-run action and a poor fixture for a case about
+ * surviving an edit. The seeded bookings ARE the fixture; no pull is needed.
+ *
+ * 🛑 AND NONE OF THE FIVE BOOKERS IS A REAL ACCOUNT. user-ravi-k,
+ * user-priya-s, user-arjun-m, user-sneha-p and user-vikram-r appear in
+ * events-seed-data.ts (as lotteryConfig.slots[].bookedByUserId) and in
+ * lottery-entries-seed-data.ts, and NONE of them exists in users-seed-data.ts.
+ * So nobody can sign in as the person who booked slot 3, and any step asking
+ * for that is unperformable. The buyer-side check is done from the public page
+ * instead, which needs no account. Recorded in OUTOFSCOPE: dangling seed FKs
+ * are data, and repairing them is not a case edit.
+ *
  * @tag domain:tester
  * @tag layer:seed
  * @tag pattern:none
@@ -20,23 +35,28 @@
  */
 export const authored = {
     "checklist-page-wiring-data-loss-lottery-edit-preserves-bookings": {
-        roles: ["buyer", "admin"],
+        roles: ["admin", "guest"],
         startPage: "/admin/lotteries",
         steps: [
-            "Sign in as rehan.sheikh@gmail.com / TempPass123! and open the lottery event event-pokemon-number-draw-july-2026.",
-            "Pull slot number 3 and complete the purchase.",
-            "Read the slot grid and note that slot 3 now shows as booked, with the buyer name and lottery number against it.",
-            "Sign out and sign in as admin@letitrip.in / TempPass123!.",
+            "Sign in as admin@letitrip.in / TempPass123! and open /lottery/event-pokemon-number-draw-july-2026.",
+            "Read the slot grid and write down slots 1 to 5 — all five are booked in the seed — recording each slot number, the buyer name shown against it and its lottery number.",
             "Open /admin/lotteries and open the editor for that lottery.",
-            "Rename slot number 7 to 'QA Slot lottery-edit-preserves-bookings' — a slot nobody has pulled.",
+            "Rename slot number 7 to 'QA Slot lottery-edit-preserves-bookings'. Slot 7 is 'Alakazam Base Set Holo' and is NOT booked — renaming an unbooked slot is the whole point.",
             "Save.",
-            "Reload the editor and read slot 3.",
-            "Sign out, sign in as rehan.sheikh@gmail.com / TempPass123!, and open the public lottery page to read slot 3.",
+            "Reload the editor and read slots 1 to 5 against what was written down, then read slot 7.",
+            "Read the price on each of slots 1 to 5 as well — slot 1 is 5000, slot 3 is 2500 — and confirm none has become 0.",
+            "Sign out and open /lottery/event-pokemon-number-draw-july-2026 to read the same five slots as a visitor sees them.",
         ],
-        inputs: { bookedSlot: 3, renamedSlot: 7, newName: "QA Slot lottery-edit-preserves-bookings" },
+        inputs: {
+            bookedSlots: "1, 2, 3, 4, 5",
+            renamedSlot: 7,
+            newName: "QA Slot lottery-edit-preserves-bookings",
+            slot1Price: 5000,
+            slot3Price: 2500,
+        },
         expectedBehaviour: "The write shape cannot express booking state at all, so an admin editing prize names cannot touch attendance. Bookings are re-attached from the stored config and matched by slot NUMBER, never by array position — deleting a slot shifts every later index, and an index-wise merge hands slot 7's buyer the prize that was slot 8's.",
-        expectedUiState: "After the save and reload, slot 3 is still booked, still carrying the same buyer name and the same lottery number. Slot 7 carries its new name. The buyer's own view of the lottery still shows their pull.",
-        expectedData: { slot3StillBooked: true },
+        expectedUiState: "After the save and reload, all five booked slots are still booked, carrying the same buyer names and the same lottery numbers. Slot 7 carries its new name. Every price is unchanged — a grid of zeros is the same defect's twin, caused by seeding the editor from the public projection, which strips price and weight. The public page shows the same five slots still taken.",
+        expectedData: { bookedSlotsAfterSave: 5, slotsPricedZero: 0 },
         endResult: "The pull survives the admin edit. The editor once sent isBooked:false for every slot into a passthrough route, so the first save of a live lottery marked every purchased slot available again and erased the buyers — with a success message and no error anywhere.",
     },
     "checklist-page-wiring-data-loss-lottery-booked-slot-cannot-be-deleted": {
@@ -45,7 +65,7 @@ export const authored = {
         steps: [
             "Sign in as admin@letitrip.in / TempPass123!.",
             "Open /admin/lotteries and open the editor for event-pokemon-number-draw-july-2026.",
-            "Find the slot that has already been pulled, slot number 3.",
+            "Find slot number 3, which the seed ships already booked by 'Arjun M' — no earlier case has to run for this to be true.",
             "Remove that slot from the list.",
             "Save.",
             "Read the error message.",
@@ -62,16 +82,19 @@ export const authored = {
         startPage: "/admin/grouped-listings",
         steps: [
             "Sign in as admin@letitrip.in / TempPass123!.",
-            "Open /admin/grouped-listings and note the title of the first group.",
-            "Open its editor at /admin/grouped-listings/{id}/edit.",
+            "Open /admin/grouped-listings, find group-beyblade-original-lineage, and write down its exact title.",
+            "Open /admin/grouped-listings/group-beyblade-original-lineage/edit.",
             "Replace the title with 'QA Group admin-grouped-listing-title-actually-saves'.",
             "Save and read the confirmation.",
             "RELOAD the page.",
             "Read the title.",
             "Set the title back to what it was and save.",
         ],
-        inputs: { newTitle: "QA Group admin-grouped-listing-title-actually-saves" },
-        expectedBehaviour: "The admin PATCH accepts every field the editor can send, not just productIds. A Zod object schema STRIPS unknown keys rather than rejecting them, so a schema listing only productIds turned a title change into a perfectly normal 200 that wrote nothing at all.",
+        inputs: {
+            group: "group-beyblade-original-lineage",
+            newTitle: "QA Group admin-grouped-listing-title-actually-saves",
+        },
+        expectedBehaviour: "The admin PATCH accepts every field the editor can send, not just productIds. A Zod object schema STRIPS unknown keys rather than rejecting them, so a schema listing only productIds turned a title change into a perfectly normal 200 that wrote nothing at all. Verified fixed on 2026-09-29 — the admin route now parses the same strict schema as the seller route, so a pass here is the expected result. It is kept because the failure was invisible without a reload and would return the moment the two schemas diverge again.",
         expectedUiState: "After the reload the title is the new one. A save confirmation followed by the OLD title after reload is the exact failure — and without the reload the screen looks identical either way, because the form is still showing what was typed.",
         expectedData: { titlePersisted: true },
         endResult: "The title is restored to its original value by the final step, so other cases that read this group by name still work.",

package/dist/features/tester/seed-data/authored/page-wiring__detail-pages.js

@@ -1,6 +1,25 @@
 /*
  * WHY: Authored six-part procedures for the page-wiring/detail-pages page.
- * WHAT: 2 case(s), keyed by full checklist id.
+ * WHAT: 3 case(s), keyed by full checklist id.
+ *
+ * 🛑 REHAN NEVER BID (corrected 2026-09-29). The identity case said to find a
+ * bid placed by rehan.sheikh@gmail.com. Only three personas bid anywhere in the
+ * seed: user-rohit-collector, user-ananya-collector and user-meera-bey. So the
+ * step found nothing, and its buyer half would then have been signing in as
+ * someone looking at another person's bid, which is a different test entirely.
+ *
+ * Bid ids are DERIVED and therefore knowable:
+ *   bid-{auctionSuffix}-{userSuffix}-20260601-{NNN}
+ * so the first bid on auction-beyblade-original-dragoon-storm is
+ *   bid-beyblade-original-dragoon-storm-rohit-collector-20260601-000
+ * That auction has three distinct bidders, which is what makes it the right
+ * fixture for a case about seeing other people's identities.
+ *
+ * ONE builder, FOUR viewers. `buildBidDetailFields(bid, viewer)` is called by
+ * AdminBidsView's modal ('admin'), UserBidsView ('buyer'), SellerBidsView
+ * ('seller') and the shared BidDetailPageClient behind all three /view pages.
+ * Its only viewer-dependent row is Bidder, added when viewer !== 'buyer'. The
+ * seller leg had no case at all and now has one.
  *
  * 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
@@ -21,8 +40,8 @@ export const authored = {
             "Sign in as admin@letitrip.in / TempPass123!.",
             "Open /admin/bids and open the first bid row so its modal appears.",
             "Write down every field label the modal shows, in order.",
-            "Copy the bid's id and close the modal.",
-            "Open /admin/bids/{id}/view directly, substituting the copied id.",
+            "Click the modal's 'Open full page' link and note the URL it lands on.",
+            "Confirm that URL is /admin/bids/{that bid id}/view.",
             "Write down every field label that page shows, in order.",
             "Compare the two lists.",
         ],
@@ -35,16 +54,32 @@ export const authored = {
         startPage: "/admin/bids",
         steps: [
             "Sign in as admin@letitrip.in / TempPass123!.",
-            "Open /admin/bids and find a bid placed by rehan.sheikh@gmail.com on an auction that other people have also bid on.",
-            "Copy that bid's id and open /admin/bids/{id}/view.",
+            "Open /admin/bids/bid-beyblade-original-dragoon-storm-rohit-collector-20260601-000/view directly. It is the first of three bids on auction-beyblade-original-dragoon-storm, placed by rohit.collect@gmail.com.",
             "Write down every bidder name and identifier shown anywhere on the page.",
-            "Sign out and sign in as rehan.sheikh@gmail.com / TempPass123!.",
-            "Open /user/bids/{id}/view with the same id.",
+            "Sign out and sign in as rohit.collect@gmail.com / TempPass123!, the buyer who placed it.",
+            "Open /user/bids/bid-beyblade-original-dragoon-storm-rohit-collector-20260601-000/view.",
             "Write down every bidder name and identifier shown anywhere on that page, including in the page source.",
         ],
         expectedBehaviour: "One viewer argument decides what each portal reveals, in one place. The admin view may name other bidders because moderating a dispute requires it; the buyer's own view must not, because a competitor's identity is not the buyer's to see.",
-        expectedUiState: "The admin page may show other bidders' identities. The buyer page shows only their own bid, with any other bidder masked or absent — and that holds in the page source too, not merely in what is rendered. A real name anywhere in the buyer view is a leak.",
+        expectedUiState: "The admin page shows a Bidder row naming who placed it; the buyer page omits that row entirely — it is the one field buildBidDetailFields makes viewer-dependent, added only when the viewer is not the buyer. Check the page source too, not merely what is rendered. A competing bidder's real name anywhere in the buyer view is a leak.",
         expectedData: { otherBidderNamesInBuyerView: 0 },
         endResult: "Read-only; nothing persists. A buyer view that shows nothing at all also fails — the buyer must still see their own bid.",
     },
+    "checklist-page-wiring-detail-pages-detail-page-seller-sees-bidder": {
+        roles: ["seller"],
+        startPage: "/store/bids",
+        steps: [
+            "Sign in as tyson@beybladearena.in / TempPass123!.",
+            "Open /store/bids and open the first bid row so its modal appears.",
+            "Write down every field label the modal shows, in order.",
+            "Open /store/bids/bid-beyblade-original-dragoon-storm-rohit-collector-20260601-000/view directly.",
+            "Write down every field label that page shows, in order, and compare the two lists.",
+            "Read whether a Bidder row is present and what it names.",
+        ],
+        inputs: { bidId: "bid-beyblade-original-dragoon-storm-rohit-collector-20260601-000", viewer: "seller" },
+        expectedBehaviour: "The seller is the third viewer of the same field builder, and the only one with no case until now. A seller running an auction needs to know who bid, so the Bidder row is present for them as it is for an admin; the buyer is the single viewer it is withheld from.",
+        expectedUiState: "The modal and the page show the same labels in the same order. A Bidder row is present and names the bidder. If it is absent, the seller cannot tell who is bidding on their own auction — and if the buyer view gained one, that is the leak the case above tests.",
+        expectedData: { bidderRowShown: true },
+        endResult: "Read-only; nothing persists. Every bid on this auction belongs to store-beyblade-arena, which is tyson's store, so the seller is entitled to see it.",
+    },
 };

package/dist/features/tester/seed-data/authored/page-wiring__drawer-pages.js

@@ -1,6 +1,29 @@
 /*
  * WHY: Authored six-part procedures for the page-wiring/drawer-pages page.
- * WHAT: 2 case(s), keyed by full checklist id.
+ * WHAT: 3 case(s), keyed by full checklist id.
+ *
+ * 🛑 "EDITOR AS A PAGE" IS TWO DIFFERENT SHAPES, and the cases assumed one
+ * (corrected 2026-09-29). Checked route by route:
+ *
+ *   drawer-as-page   /admin/team/new, /admin/navigation/new — the editor hard-
+ *                    renders <SideDrawer> with no headless mode, so the page
+ *                    mounts it permanently open and wires onClose to navigate
+ *                    back to the list. Here "close the panel" is literal.
+ *   full page        /admin/tester-checklist/new (StackedViewShell +
+ *                    SectionForm), /admin/carousels/new (a Section/Container
+ *                    with a back Link), /store/stickers/new (a product shell).
+ *                    There is no panel and nothing to close; the way back is a
+ *                    Cancel button or a link.
+ *
+ * Both are correct. What matters for every case here is the same two things —
+ * the form is usable on arrival, and there is a way back to its list — so the
+ * steps now ask for that rather than for a drawer that two thirds of these
+ * routes do not have. A tester hunting a panel on /store/stickers/new would
+ * otherwise report a defect that is really a second, equally valid shape.
+ *
+ * All 19 routes named in step prose below were verified to exist on
+ * 2026-09-29. Worth repeating rather than trusting: the hrefs audit validates
+ * href and startPage only, so a route named inside a step is checked by nobody.
  *
  * 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
@@ -20,15 +43,18 @@ export const authored = {
         steps: [
             "Sign in as admin@letitrip.in / TempPass123!.",
             "Open /admin/team/new directly in the address bar.",
-            "Read what is on screen without clicking anything.",
+            "Read what is on screen without clicking anything — this one is a drawer mounted permanently open.",
             "Close the panel and read the address bar.",
-            "Open /admin/navigation/new directly and read what is on screen.",
-            "Close it and read the address bar.",
-            "Open /admin/tester-checklist/new directly and read what is on screen.",
-            "Close it and read the address bar.",
+            "Open /admin/navigation/new directly, read what is on screen, close it, and read the address bar. This is the same drawer-as-page shape.",
+            "Open /admin/tester-checklist/new directly and read what is on screen. This one is a FULL PAGE, not a drawer, so look for a Cancel or back control rather than a panel to close.",
+            "Use that control and read the address bar.",
         ],
-        expectedBehaviour: "An editor that exists as both a drawer and a page opens with its panel ALREADY open when reached by URL. Closing it returns to the list the editor belongs to, so the page is a real destination rather than a dead end.",
-        expectedUiState: "Each of the three URLs renders its form immediately — an invite form, a nav-item form, a checklist-case form — with no blank page and nothing to click first. Closing lands on /admin/team, /admin/navigation and /admin/tester-checklist respectively, not on a 404 and not on the dashboard.",
+        inputs: {
+            drawerAsPage: "/admin/team/new, /admin/navigation/new",
+            fullPage: "/admin/tester-checklist/new",
+        },
+        expectedBehaviour: "An editor reached by URL is usable the moment it loads, and offers a way back to the list it belongs to — so the page is a real destination rather than a dead end. Whether that is a drawer mounted open or an ordinary page is an implementation choice and both are correct; what fails is arriving at a blank page, or having no way back.",
+        expectedUiState: "All three URLs render their form immediately, with no blank page and nothing to click first. Leaving each one lands on /admin/team, /admin/navigation and /admin/tester-checklist respectively, not on a 404 and not on the dashboard. 🛑 Only the first two have a panel to close; the third is a full page and its absence of a drawer is not a finding.",
         endResult: "Nothing is created — close each panel rather than saving. A blank page behind a closed drawer is the failure this catches.",
     },
     "checklist-page-wiring-drawer-pages-page-drawer-deep-link-survives-reload": {
@@ -53,14 +79,14 @@ export const authored = {
         steps: [
             "Sign in as admin@letitrip.in / TempPass123!.",
             "Open each of these by URL in turn: /admin/categories/new, /admin/brands/new, /admin/bundles/new, /admin/faqs/new, /admin/ads/new, /admin/shipments/new, /admin/addresses/new, /admin/grouped-listings/new, /admin/sublisting-categories/new, /admin/carousel/new, /admin/carousels/new.",
-            "On each, note whether the form is already open or the page is blank.",
-            "Close or cancel each and note where the browser lands.",
+            "On each, note whether the form is usable on arrival or the page is blank.",
+            "Leave each one — a drawer close, a Cancel button or a back link, whichever it offers — and note where the browser lands.",
             "Sign in as tyson@beybladearena.in / TempPass123! and repeat for /store/addresses/new, /store/sublisting-categories/new, /store/stickers/new, /store/pre-orders/new and /store/listing-templates/new.",
             "Record every route that arrives blank and every cancel that lands nowhere.",
         ],
-        expectedBehaviour: "Every editor-as-a-page route opens with its form showing and cancels back to its own list. Three of these were already covered by name; the other thirteen are the same route shape and were never named anywhere, so a blank one is a working URL with nothing on it and no error to report.",
-        expectedUiState: "All sixteen arrive with the form open and cancel back to the matching list. Each blank arrival is a finding, and so is each cancel that lands on a dead route — both named by route.",
-        expectedData: { blankEditorRoutes: 0 },
-        endResult: "Nothing is saved.",
+        expectedBehaviour: "Every editor-as-a-page route arrives with its form usable and offers a way back to its own list. These sixteen are distinct from the three named in the first case on this page, and none of them is named anywhere else in the catalogue, so a blank one is a working URL with nothing on it and no error to report.",
+        expectedUiState: "All sixteen arrive with a usable form and get back to the matching list. Each blank arrival is a finding, and so is each exit that lands on a dead route, both named by route. 🛑 These are NOT all drawers: /admin/carousels/new is a plain page with a back link and /store/stickers/new is a product shell, so record how each one offers its way back rather than expecting a panel.",
+        expectedData: { blankEditorRoutes: 0, routesChecked: 16 },
+        endResult: "Nothing is saved. Every one of these routes was verified to exist on 2026-09-29, so a 404 here means one was deleted since, which is itself the finding.",
     },
 };