@mohasinac/appkit 4.42.0 → 4.42.2

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

@@ -23,10 +23,10 @@ const SIGN_IN_BUYER = "Sign in as rehan.sheikh@gmail.com / TempPass123!.";
 export const authored = {
     "checklist-content-discovery-event-participation-join-event-as-participant": {
         roles: ["buyer"],
-        startPage: "/events",
+        startPage: "/events/event-favourite-blader-poll",
         steps: [
             SIGN_IN_BUYER,
-            "Open /events and pick an event whose status is active.",
+            "Open /events/event-favourite-blader-poll — an ACTIVE poll with 3 seeded entries. 🛑 THE NEXT FOUR CASES READ THE ENTRY THIS ONE CREATES, so they must all use this same event; picking a different active event each time breaks the chain and each case then tests a state nobody set up.",
             "Open it and find the control for joining.",
             "Use it.",
             "Read the outcome shown.",
@@ -38,7 +38,7 @@ export const authored = {
     },
     "checklist-content-discovery-event-participation-own-entry-visible-after-join": {
         roles: ["buyer"],
-        startPage: "/events",
+        startPage: "/events/event-favourite-blader-poll",
         steps: [
             SIGN_IN_BUYER,
             "Join an active event.",
@@ -53,13 +53,13 @@ export const authored = {
     },
     "checklist-content-discovery-event-participation-entry-survives-reload-and-relogin": {
         roles: ["buyer"],
-        startPage: "/events",
+        startPage: "/events/event-favourite-blader-poll",
         steps: [
             SIGN_IN_BUYER,
             "Join an active event and note the entry's status.",
             "Reload the event page and read the entry again.",
             "Sign out and sign back in as the same account.",
-            "Open the event page and read the entry.",
+            "Open /events/event-favourite-blader-poll and read the entry this account created.",
             "Open the event in a different browser signed in as the same account.",
         ],
         expectedBehaviour: "The entry is a stored record keyed to the account, so it survives a reload, a sign-out and a different device. An entry held only in the browser disappears the moment the participant switches devices, which is exactly when they check whether they got in.",
@@ -68,13 +68,13 @@ export const authored = {
     },
     "checklist-content-discovery-event-participation-cannot-join-twice": {
         roles: ["buyer"],
-        startPage: "/events",
+        startPage: "/events/event-favourite-blader-poll",
         steps: [
             SIGN_IN_BUYER,
             "Join an active event.",
             "Attempt to join the same event again from the page.",
             "Read what happens.",
-            "Open the event in a second tab and attempt to join from there as well.",
+            "Open /events/event-favourite-blader-poll in a second tab and attempt to join from there as well.",
             "Check the account has exactly one entry.",
         ],
         expectedBehaviour: "A second join is refused rather than creating a duplicate. Two entries for one account inflate the entry count, double the account's odds in any draw, and are indistinguishable from two different people once the names are masked.",
@@ -84,11 +84,11 @@ export const authored = {
     },
     "checklist-content-discovery-event-participation-leave-or-cancel-entry": {
         roles: ["buyer"],
-        startPage: "/events",
+        startPage: "/events/event-favourite-blader-poll",
         steps: [
             SIGN_IN_BUYER,
             "Join an active event.",
-            "Find the control for withdrawing and use it.",
+            "On /events/event-favourite-blader-poll, find the control for withdrawing and use it.",
             "Read the confirmation, if one is shown.",
             "Read the entry's state afterwards.",
             "Reload and read it again.",
@@ -100,10 +100,10 @@ export const authored = {
     },
     "checklist-content-discovery-event-participation-closed-event-cannot-be-joined": {
         roles: ["buyer"],
-        startPage: "/events",
+        startPage: "/events/event-won-original-set-raffle",
         steps: [
             SIGN_IN_BUYER,
-            "Open /events and find an event whose status is ended.",
+            "Open /events/event-won-original-set-raffle — an ENDED raffle, which is the seed's only ended event.",
             "Open it and read whether a join control is offered.",
             "If one is offered, use it and read what happens.",
             "Repeat with an event whose status is cancelled.",
@@ -115,10 +115,10 @@ export const authored = {
     },
     "checklist-content-discovery-event-participation-leaderboard-shows-real-participants": {
         roles: ["buyer"],
-        startPage: "/events",
+        startPage: "/events/event-favourite-blader-poll/leaderboard",
         steps: [
             SIGN_IN_BUYER,
-            "Open an event that has a leaderboard and open that tab.",
+            "Open /events/event-favourite-blader-poll and open its Leaderboard tab — it carries 3 seeded entries, so the board is not empty.",
             "Read the rows — the names and the scores.",
             "Check the names are masked rather than showing full identities.",
             "Check the scores are real numbers rather than zeros or placeholders.",
@@ -130,11 +130,11 @@ export const authored = {
     },
     "checklist-content-discovery-event-participation-leaderboard-own-row-findable": {
         roles: ["buyer"],
-        startPage: "/events",
+        startPage: "/events/event-favourite-blader-poll/leaderboard",
         steps: [
             SIGN_IN_BUYER,
             "Join an event that has a leaderboard and take part enough to appear on it.",
-            "Open the leaderboard.",
+            "Open /events/event-favourite-blader-poll and its Leaderboard tab.",
             "Look for the participant's own row without scrolling the whole list.",
             "Check it is highlighted, pinned, or otherwise findable.",
             "Read the position shown for it.",
@@ -145,10 +145,10 @@ export const authored = {
     },
     "checklist-content-discovery-event-participation-leaderboard-ordering-correct": {
         roles: ["buyer"],
-        startPage: "/events",
+        startPage: "/events/event-favourite-blader-poll/leaderboard",
         steps: [
             SIGN_IN_BUYER,
-            "Open an event leaderboard and write down the first ten rows in order with their scores.",
+            "Open /events/event-favourite-blader-poll and its Leaderboard tab, and write down every row in order with its score — the seed has 3 entries, so read all of them rather than expecting ten.",
             "Check each score is not greater than the one above it.",
             "Find two rows with equal scores and note their order.",
             "Reload the page and read the first ten again.",
@@ -160,10 +160,10 @@ export const authored = {
     },
     "checklist-content-discovery-event-participation-leaderboard-empty-state": {
         roles: ["buyer"],
-        startPage: "/events",
+        startPage: "/events/event-beyblade-slot-raffle-draft",
         steps: [
             SIGN_IN_BUYER,
-            "Open /events and find an event with no entries yet, such as a draft or a newly-started one.",
+            "Open /events/event-beyblade-slot-raffle-draft — a DRAFT raffle with no seeded entries, which is what makes the empty state reachable.",
             "Open its leaderboard.",
             "Read what is shown.",
             "Check it states there are no entries rather than showing a blank panel.",
@@ -175,12 +175,12 @@ export const authored = {
     },
     "checklist-content-discovery-event-participation-raffle-winner-announced-to-participants": {
         roles: ["admin", "buyer"],
-        startPage: "/events",
+        startPage: "/events/event-won-original-set-raffle",
         steps: [
             "Sign in as admin@letitrip.in / TempPass123! and open an event with a raffle configured.",
             "Draw the raffle and note who won.",
             "Sign in as the winning participant.",
-            "Open the event page and read whether the result is announced.",
+            "Open /events/event-won-original-set-raffle — ENDED and carrying a recorded raffleWinnerUserId — and read whether the result is announced.",
             "Open the account's notifications and look for one about the win.",
             "Sign in as a non-winning participant and check the result is visible to them too.",
         ],
@@ -190,18 +190,18 @@ export const authored = {
     },
     "checklist-content-discovery-event-participation-spin-wheel-one-use-enforced": {
         roles: ["buyer"],
-        startPage: "/events",
+        startPage: "/events/event-daily-beyblade-pull-wheel",
         steps: [
             SIGN_IN_BUYER,
-            "Open /events and find a spin-wheel event that is currently open.",
+            "Open /events/event-daily-beyblade-pull-wheel — the seed's only SPIN_WHEEL event, active, with real spinPrizes and spinMaxPerUser of 2. Note the cap is TWO, not one: a case asserting a single use would fail on a correct system.",
             "Take a spin and read the result.",
-            "Attempt to spin again immediately.",
-            "Read what happens.",
-            "Reload the page and attempt once more.",
+            "Spin a SECOND time — this one is allowed, because spinMaxPerUser is 2.",
+            "Attempt a THIRD spin and read what happens.",
+            "Reload the page and attempt a third spin once more.",
             "If a prize was won, follow whatever the interface offers for claiming it.",
         ],
-        expectedBehaviour: "The per-user spin limit is enforced server-side and survives a reload, and a won prize is claimable. A limit held only in the browser is defeated by refreshing — which is the first thing anyone does after a disappointing spin.",
-        expectedUiState: "The second spin is refused before and after the reload, with a message naming the limit, and a won prize can actually be claimed. A spin that works again after a reload is the finding.",
-        endResult: "One spin is used; claim the prize if one was won.",
+        expectedBehaviour: "The per-user spin limit is TWO, enforced server-side, and it survives a reload; a won prize is claimable. A limit held only in the browser is defeated by refreshing — which is the first thing anyone does after a disappointing spin.",
+        expectedUiState: "The first two spins succeed and the THIRD is refused, before and after the reload, with a message naming the limit; a won prize can actually be claimed. A refusal on the second spin is a failure in the other direction — the cap is 2 — and a third spin that works after a reload is the finding.",
+        endResult: "Both spins are used; claim any prize won. The key still reads one-use-enforced and is deliberately unchanged — a case id is the response document id, so renaming it orphans every verdict recorded against it.",
     },
 };

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

@@ -54,7 +54,7 @@ export const authored = {
         steps: [
             "Open /events in a private window and find event-pokemon-number-draw-july-2026.",
             "Look at its card image.",
-            "Open the lottery's detail page.",
+            "Open /lottery/event-pokemon-number-draw-july-2026 — the lottery detail route is /lottery/{id}, not /events/{id}.",
             "Look at the image at the top of that page.",
             "Note whether either shows an emoji instead of a photograph.",
         ],
@@ -229,7 +229,7 @@ export const authored = {
         steps: [
             "Sign in as admin@letitrip.in / TempPass123!.",
             "Open /admin/events, open event-win-burst-regalia-genesis for editing, and write down its current raffle type.",
-            "Set the raffle type to 'Top N participants', set the N to 3, and save.",
+            "Set the raffle type to 'Top N earliest participants' — the dropdown carries the word 'earliest' and the stored value is top_n_participants — set the N to 3, and save.",
             "Sign out and sign in as rehan.sheikh@gmail.com / TempPass123!.",
             "Open /events/event-win-burst-regalia-genesis and read the Overview tab's description of how winners are chosen.",
             "Click the Participate tab and enter.",

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

@@ -35,8 +35,9 @@ export const authored = {
         steps: [
             "Resize the browser window to 390 pixels wide.",
             "Open /faqs in a private window with no session.",
+            "WAIT for the page to settle before reading any number. This page has been measured showing zero questions at 2.5 seconds and 62 at 6 — a count taken early is confidently wrong, and this case is entirely about comparing counts.",
             "Read the count shown against each category.",
-            "Open one category and count the questions it actually holds.",
+            "Open one category and count the questions it actually holds, waiting again before counting.",
             "Compare the two numbers.",
             "Try to scroll the page sideways.",
         ],
@@ -62,4 +63,25 @@ export const authored = {
         expectedUiState: "At 1280 the categories are a tab strip. At 390 they are a dropdown listing every category, and selecting one switches the questions AND updates the control's own label. The page does not scroll sideways at either width.",
         endResult: "Read-only; nothing persists. Restore the window width afterwards.",
     },
+    "checklist-content-discovery-faq-help-faq-search-filters-and-survives-reload": {
+        roles: ["guest"],
+        startPage: "/faqs",
+        steps: [
+            "Open /faqs in a private window with no session.",
+            "WAIT for the questions to appear before counting anything. 🛑 This page hydrates client-side and the difference is not subtle — it has been measured showing zero questions at 2.5 seconds and 62 at 6. A count taken early produces a confident, wrong answer, and that has already happened twice on this exact page.",
+            "Count the questions visible across all categories once the page has settled.",
+            "Type shipping into the search box and commit it.",
+            "Read the count and confirm it is SMALLER than the unfiltered count, and that the remaining questions are about shipping.",
+            "Read the address bar and check the term is in the URL as ?q=shipping.",
+            "RELOAD with that URL and confirm the same filtered set comes back, waiting again before judging.",
+            "Clear the box, type zzzznope, and commit.",
+            "Read the result — a named empty state and zero questions, not the full list.",
+            "Clear the search and confirm the original count returns.",
+        ],
+        inputs: { realQuery: "shipping", nonsenseQuery: "zzzznope" },
+        expectedBehaviour: "The search box filters the questions and the term round-trips through the URL, so a filtered view is shareable and survives a reload. The nonsense control is the whole case: a real term returns plausible questions whether or not the filter ran at all, so only zzzznope separates filtering from returning everything. The seed ships 63 FAQs across seven categories, which is enough for a real term to narrow visibly rather than by one row.",
+        expectedUiState: "'shipping' shows fewer questions than the unfiltered list and they are about shipping. The URL carries ?q=shipping and reloading reproduces that view. 'zzzznope' shows a named empty state with zero questions — a blank panel with no message is a different failure and should be recorded as such. Clearing restores the original count.",
+        expectedData: { nonsenseResultCount: 0 },
+        endResult: "Read-only; nothing persists beyond the URL. A full list under zzzznope is the failure. So is an empty page under a real term, which on this page is far more likely to be a count taken before hydration than a broken filter — wait, then look again, before recording either.",
+    },
 };

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

@@ -99,12 +99,12 @@ export const authored = {
         roles: ["buyer"],
         startPage: "/user/settings",
         steps: [
-            "Sign in as an account whose inbox you can open.",
-            "Open /user/settings, click the 'Notifications' tab, and make sure Email is on for order updates.",
+            "Sign in as the harness mailbox account. 🛑 NO SEEDED PERSONA CAN RECEIVE TESTABLE EMAIL — both instruments key on TESTER_EMAIL_ID, and every seeded persona uses a real-looking address the harness does not own. Register a plus-addressed signup on that mailbox, or run this as whichever account already uses it.",
+            "Open /user/settings, click the 'Notifications' tab, and make sure Email is on for order updates. order_confirmed is one of the 18 email-eligible types, so it should send.",
             "Place an order that will produce an order-confirmed notification.",
             "Open /user/notifications and confirm the in-app entry is there.",
-            "Open the inbox, checking Spam as well, and wait up to five minutes.",
-            "Read the email's From name and address, its subject and its body.",
+            "Capture a timestamp BEFORE the order — node -e \"console.log(Date.now())\" — then ask the mailbox: node tester/scripts/check-inbox.mjs --since <that number> --subject \"order\". --since is the whole correctness argument: the mailbox is shared across every case in every run, so 'newest matching message' happily returns one an earlier case left behind.",
+            "Read the exit code. 0 means it arrived; 1 means it did not (a product defect); 2 means the mailbox could not be opened (a harness problem, answer null). Then read the email's From name and address, its subject and its body.",
             "Click the button or link inside it.",
         ],
         expectedBehaviour: "The dispatcher fans out to in-app first and then email, rendering a per-type template rather than wrapping the one-line message in a paragraph — for a long time not one caller supplied email HTML, so every type shipped the same bare body.",
@@ -115,12 +115,12 @@ export const authored = {
         roles: ["buyer"],
         startPage: "/user/settings",
         steps: [
-            "Sign in as an account whose inbox you can open.",
+            "Sign in as the harness mailbox account — see the arrival case above; no seeded persona can receive testable email.",
             "Open /user/settings, click the 'Notifications' tab, and turn Email OFF for order updates.",
             "Click 'Save preferences' and reload to confirm it stayed off.",
             "Place an order that would produce an order-confirmed notification.",
             "Open /user/notifications and read the entries.",
-            "Open the inbox and wait five minutes, checking Spam as well.",
+            "Prove the SILENCE rather than waiting for it: node tester/scripts/check-inbox.mjs --since <timestamp captured before the order> --subject \"order\" --expect-none. Without --expect-none, 'nothing arrived' is unprovable — you wait and hope, and a slow inbox looks exactly like a working suppression. Exit 0 means the silence held.",
             "Turn Email back on for order updates and save.",
         ],
         expectedBehaviour: "Turning a channel off suppresses that channel and nothing else — the in-app notification still appears. The suppression depends on a complete type-to-preference-key map: a type missing from it leaves the key undefined, the opt-out check never runs, and mail keeps arriving while the toggle reads as honoured.",

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

@@ -312,7 +312,7 @@ export const authored = {
         startPage: "/admin/team",
         steps: [
             "Sign in as admin@letitrip.in / TempPass123!.",
-            "Open several admin listing pages in turn and look at each toolbar.",
+            "Open these four admin listings in turn and look at each toolbar: /admin/products, /admin/orders, /admin/team, /admin/reviews. Naming them matters — two testers picking different pages cannot compare results, and a gap that appears on only one listing is the finding.",
             "Note any toolbar with a visible empty gap where a control would sit.",
             "Resize to 390 pixels wide and look at the same toolbars.",
         ],

package/dist/features/tester/seed-data/authored/content-discovery__store-reviews-aggregate.js

@@ -64,7 +64,7 @@ export const authored = {
             "Search that body for the text enc:v1 and for the field names userNameIndex, searchTxt and userId.",
         ],
         expectedBehaviour: "A reviewer's name is PII, stored encrypted, and shown masked in public. The generic repository returns the document verbatim, so a route that does not go through the reviews repository serves ciphertext — and a payload built by spreading the document also carries the HMAC blind index, which lets a caller confirm a guessed name.",
-        expectedUiState: "Names render masked, for example 'M*** U***'. No card shows a value beginning enc:v1.",
+        expectedUiState: "Names render masked. maskName masks EVERY whitespace-separated word, and every seeded persona is literally 'Mock User N' — so the exact rendering is 'M*** U*** 3***', including the number. A two-word 'M*** U***' would mean the trailing word was dropped. No card shows a value beginning enc:v1.",
         expectedData: { ciphertextInResponse: false, blindIndexInResponse: false },
         endResult: "Nothing is changed; this case only reads.",
     },

package/dist/features/tester/seed-data/authored/cta-layout__checkout-bottom-bar.js

@@ -11,6 +11,27 @@
  * "looks right". 320px is the narrowest viewport worth supporting and is where
  * every squeeze shows up first.
  *
+ * 🛑 THE PAYMENT STEP DOES NOT OFFER PhonePe BY DEFAULT (corrected 2026-09-29).
+ * CheckoutRouteClient defaults are showCashOption = true, showPhonePe = false,
+ * showCod = false, and the payment branch picks the first ENABLED method in
+ * that order — so the primary CTA on a default site reads 'Pay via UPI / Cash'.
+ * The second case asserted 'Pay Online (PhonePe)' is shown complete, which on a
+ * default site means asserting a button that is not there. It now reads whatever
+ * CTA the enabled method produces and lists all four labels so the tester can
+ * recognise which one they got:
+ *
+ *   showCashOption  'Pay via UPI / Cash'      (default ON, and the longest)
+ *   showPhonePe     'Pay Online (PhonePe)'    (default OFF)
+ *   showCod         'Cash on Delivery'        (default OFF)
+ *   emiVisible      'Pay in EMI'
+ *
+ * 🛑 AND THE BUYER HAS NO SAVED ADDRESS. Three addresses are seeded, owned by
+ * user-yugi-muto, user-seto-kaiba and user-admin-letitrip. rehan.sheikh has none,
+ * so 'select the first saved address' cannot be followed on a fresh project. The
+ * addresses collection is PRESERVE tier, so one may exist from an earlier run
+ * — the step now covers both, because a case that assumes either is wrong half
+ * the time.
+ *
  * @tag domain:tester
  * @tag layer:seed
  * @tag pattern:none
@@ -26,7 +47,8 @@ export const authored = {
             "Resize the browser window to 320 pixels wide.",
             "Sign in as rehan.sheikh@gmail.com / TempPass123!.",
             "Open /products/product-beyblade-burst-valkyrie and click 'Add to Cart'.",
-            "Open /checkout, select the first saved address, and continue to the Extras step.",
+            "Open /checkout. Select a saved address if one is offered; if the list is empty, add one, since no address is seeded for this buyer.",
+            "Continue to the Extras step — checkout is Address, then Extras and fees, then Payment.",
             "Read the two buttons in the bottom action bar and compare their widths.",
         ],
         inputs: { viewportWidth: 320 },
@@ -41,13 +63,16 @@ export const authored = {
             "Resize the browser window to 320 pixels wide.",
             "Sign in as rehan.sheikh@gmail.com / TempPass123!.",
             "Open /products/product-beyblade-burst-valkyrie and click 'Add to Cart'.",
-            "Open /checkout and continue through to the payment step.",
-            "Read the primary button's label in full.",
-            "Select each payment method in turn and read the primary label after each.",
+            "Open /checkout, supply an address if none is saved, and continue through Extras to the Payment step.",
+            "Read the primary button's label in full and write down which of the four it is: 'Pay via UPI / Cash', 'Pay Online (PhonePe)', 'Cash on Delivery' or 'Pay in EMI'.",
+            "Select each payment method the page offers in turn and read the primary label after each.",
         ],
-        inputs: { viewportWidth: 320 },
+        inputs: {
+            viewportWidth: 320,
+            defaultPrimaryCta: "Pay via UPI / Cash",
+        },
         expectedBehaviour: "A label too long for one line makes its button taller rather than truncating. Height is cheap in a bottom bar; a clipped verb is not, because the buyer cannot tell what the button will do.",
-        expectedUiState: "'Pay Online (PhonePe)' is shown complete, wrapping onto two lines if it needs to. An ellipsis anywhere in the bar is a failure, on any payment method.",
+        expectedUiState: "Whichever CTA the enabled method produces is shown complete, wrapping onto two lines if it needs to. On a default site that is 'Pay via UPI / Cash' — the longest of the four, and therefore the one most likely to clip. An ellipsis anywhere in the bar is a failure, on any method. Do NOT record the absence of 'Pay Online (PhonePe)' as a defect: PhonePe is off by default and a separate admin case covers switching it on.",
         endResult: "Layout-only; nothing persists. Restore the window width afterwards.",
     },
 };

package/dist/features/tester/seed-data/authored/cta-layout__dialog-footers.js

@@ -10,6 +10,21 @@
  * compact while a mobile bar stretches — and that is exactly why they are one
  * page. A single rule applied to both is what makes one of them wrong.
  *
+ * 🛑 /admin/products HAS NO DELETE ROW ACTION (corrected 2026-09-29). Its row
+ * menu is Approve, Reject and Quick edit; nothing there opens a destructive
+ * dialog, so the first case could not start. It now uses the bundle editor's
+ * delete, which is a real ConfirmDeleteModal and names the record in its title.
+ *
+ * ConfirmDeleteModal's defaults are title 'Delete Item?', confirm 'Delete',
+ * cancel 'Cancel'; the bundle editor overrides the title to 'Delete this
+ * bundle?'. A dialog still reading the generic default IS the finding — a
+ * confirmation that does not say what it will destroy is barely a confirmation.
+ *
+ * The drawer footer's labels are exact and come from FilterDrawer itself:
+ * 'Reset all' (ghost) and 'Apply' (primary), which becomes 'Apply (N)' while
+ * changes are pending. A tester seeing the count variant is looking at correct
+ * behaviour, not a drifted label.
+ *
  * @tag domain:tester
  * @tag layer:seed
  * @tag pattern:none
@@ -20,19 +35,24 @@
 export const authored = {
     "checklist-cta-layout-dialog-footers-modal-footer-stays-compact-on-desktop": {
         roles: ["admin"],
-        startPage: "/admin/products",
+        startPage: "/admin/bundles",
         steps: [
             "Resize the browser window to 1280 pixels wide.",
             "Sign in as admin@letitrip.in / TempPass123!.",
-            "Open /admin/products.",
-            "Open the row action menu on the first product and choose a destructive action such as Delete.",
-            "Read the dialog's footer buttons and where they sit horizontally.",
-            "Dismiss the dialog with Cancel rather than confirming.",
+            "Open /admin/bundles and open any bundle for editing.",
+            "Click its delete control to open the confirmation dialog. Do NOT confirm.",
+            "Read the dialog's title: it should name the record, not read 'Delete Item?'.",
+            "Read the two footer buttons, 'Cancel' and 'Delete', and where they sit horizontally.",
+            "Dismiss with Cancel.",
         ],
-        inputs: { viewportWidth: 1280 },
+        inputs: {
+            viewportWidth: 1280,
+            dialogTitle: "Delete this bundle?",
+            genericDefault: "Delete Item?",
+        },
         expectedBehaviour: "A dialog footer packs its buttons to the right at content width. A destructive dialog also has to HAVE a confirmation to open at all — every danger-kind action carries its confirmation copy in the action registry, and one without it executes immediately with no warning.",
-        expectedUiState: "Cancel and the destructive button are each about as wide as their own label and sit together at the right edge of the dialog. They do not stretch edge to edge like banners. The dialog names what is about to be deleted rather than asking a generic 'Are you sure?'.",
-        endResult: "Cancel closes the dialog and nothing is deleted. The product is still in the list after a reload — dismissing must not be a silent confirm.",
+        expectedUiState: "'Cancel' and 'Delete' are each about as wide as their own label and sit together at the right edge of the dialog. They do not stretch edge to edge like banners. The title names the bundle rather than reading the component default 'Delete Item?' — a confirmation that does not say what it will destroy is barely a confirmation.",
+        endResult: "Cancel closes the dialog and nothing is deleted. The bundle is still in /admin/bundles after a reload — dismissing must not be a silent confirm.",
     },
     "checklist-cta-layout-dialog-footers-filter-drawer-footer-stacks-when-narrow": {
         roles: ["guest"],
@@ -44,9 +64,13 @@ export const authored = {
             "Scroll to the drawer's footer.",
             "Read both buttons and note whether they sit side by side or one per line.",
         ],
-        inputs: { viewportWidth: 320 },
+        inputs: {
+            viewportWidth: 320,
+            resetLabel: "Reset all",
+            applyLabel: "Apply",
+        },
         expectedBehaviour: "Where a dialog footer stays compact, a drawer footer prefers legibility: if two buttons cannot both read at the available width they stack one per line rather than shrinking below their labels.",
-        expectedUiState: "'Reset all' and 'Apply' are both fully readable. If they cannot fit side by side at 320px they are stacked, one per line. Neither is crushed below its label and neither is truncated.",
+        expectedUiState: "'Reset all' and 'Apply' are both fully readable. If they cannot fit side by side at 320px they are stacked, one per line. Neither is crushed below its label and neither is truncated. The primary reads 'Apply (N)' once a facet has been changed but not yet applied, which is correct rather than a drifted label.",
         endResult: "Layout-only; closing the drawer without applying changes nothing. Restore the window width afterwards.",
     },
 };

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

@@ -6,6 +6,27 @@
  * 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
@@ -20,16 +41,22 @@ export const authored = {
         steps: [
             "Resize the browser window to 375 pixels wide.",
             "Sign in as tyson@beybladearena.in / TempPass123!.",
-            "Open /store/products/new.",
-            "Type 'QA Product editor-action-bar' in the title field so the form becomes dirty and Discard appears.",
-            "Read the action bar and count how many buttons are visible.",
+            "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.",
+            "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" },
-        expectedBehaviour: "Four 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.",
-        expectedUiState: "All four of Discard, Preview, Save draft and Publish are 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.",
-        expectedData: { visibleButtonCount: 4 },
+        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.js

@@ -8,6 +8,23 @@
  * 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
@@ -36,7 +53,7 @@ export const authored = {
         roles: ["buyer"],
         startPage: "/",
         steps: [
-            "Sign in as rehan.sheikh@gmail.com / TempPass123! with an empty cart.",
+            "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.",
@@ -114,7 +131,7 @@ export const authored = {
         steps: [
             "Open the homepage and read which navigation entry is marked as current.",
             "Navigate to /products and read which is marked.",
-            "Navigate to a product detail page 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.",
         ],
@@ -127,15 +144,20 @@ export const authored = {
         startPage: "/admin/site",
         steps: [
             "Sign in as admin@letitrip.in / TempPass123! and open Site Settings.",
-            "Find the announcement bar section and set its message to 'QA announcement probe — checklist case.'",
-            "Save.",
-            "Open the public homepage as a signed-out visitor.",
-            "Read whether the announcement appears and whether the text matches.",
-            "Return to Site Settings, clear the announcement, and check it leaves the homepage.",
+            "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." },
+        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 public homepage, and clearing it removes the bar. A successful save with nothing on the homepage is the finding.",
+        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.js

@@ -6,6 +6,26 @@
  * 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
@@ -23,13 +43,19 @@ export const authored = {
             "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" },
+        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. 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 },
+        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.",
     },
 };