@mohasinac/appkit 4.34.1 → 4.35.0

package/dist/features/tester/seed-data/authored/content-discovery__category-brand-relations.js

@@ -0,0 +1,149 @@
+/*
+ * WHY: Authored six-part procedures for the content-discovery/category-brand-relations page.
+ * WHAT: 8 case(s), keyed by full checklist id.
+ *
+ * 🛑 THE TWO SIDES OF THE TREE ARE ASYMMETRIC AND THAT ASYMMETRY IS THE POINT.
+ *
+ * A PRODUCT carries its full ancestor chain, so a category page matches on its own
+ * id alone. A STORE carries a single category with no chain, so the store side
+ * genuinely needs the descendant list. Reversing either is a real defect that
+ * renders as an empty grid: expanding a root into every descendant blows the
+ * query's value cap and the throw is swallowed, while NOT expanding the store side
+ * hides every store filed below the top tier.
+ *
+ * Brands are rows in the same collection as categories, discriminated by a type
+ * field, and they match products by DISPLAY NAME rather than by id — so renaming a
+ * brand silently orphans its catalogue while the page keeps rendering.
+ *
+ * @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-content-discovery-category-brand-relations-tier-depth-reachable": {
+        roles: ["guest"],
+        startPage: "/categories",
+        steps: [
+            "Open /categories and find Spinning Tops.",
+            "Click into it and read the child categories listed.",
+            "Click Beyblade Burst and read its children.",
+            "Click Burst Parts and read its children.",
+            "Click one of those and note there are no further children.",
+            "Count how many clicks it took to reach the leaf.",
+        ],
+        expectedBehaviour: "Every tier is reachable by clicking, with no typed URLs. A tier that renders but offers no way down is unreachable in practice, which is the same as not existing for anyone browsing.",
+        expectedUiState: "Four levels: Spinning Tops, then Beyblade Burst, then Burst Parts, then a leaf such as Layers or Drivers. Each page lists its own children until the leaf, which lists none.",
+        expectedData: { tiersReached: 4 },
+        endResult: "Read-only.",
+    },
+    "checklist-content-discovery-category-brand-relations-second-root-reachable": {
+        roles: ["guest"],
+        startPage: "/categories",
+        steps: [
+            "Open /categories and read every top-level category shown.",
+            "Check both Spinning Tops and Living Collectibles are present.",
+            "Click Living Collectibles and read its children.",
+            "Click down to a leaf under it.",
+            "Check the leaf lists at least one live-item listing.",
+        ],
+        inputs: { rootA: "category-spinning-tops", rootB: "category-living-collectibles" },
+        expectedBehaviour: "Both roots are on the index. The tree had one root and two tiers before it was rebuilt, so the live-item listings carried no category at all and were unreachable from every category and brand page — a whole listing type invisible to browsing while its detail pages worked fine.",
+        expectedUiState: "Two roots on the index, and the Living Collectibles branch walks down to a leaf holding a live listing. One root, or a second root that leads nowhere, is the finding.",
+        endResult: "Read-only.",
+    },
+    "checklist-content-discovery-category-brand-relations-root-page-shows-descendant-products": {
+        roles: ["guest"],
+        startPage: "/categories/category-spinning-tops",
+        steps: [
+            "Open /categories/category-beyblade-burst and note the title of one product listed there.",
+            "Open /categories/category-spinning-tops.",
+            "Search the listing for that same product.",
+            "Read the product count shown on the root page.",
+            "Compare it against the counts on its four generation children.",
+        ],
+        inputs: { rootId: "category-spinning-tops", childId: "category-beyblade-burst" },
+        expectedBehaviour: "A product carries its FULL ancestor chain, so a root page matches on its own id and needs no descendant expansion. A product visible on a leaf but missing from its root means the chain was not written on the product side — and nothing appends ancestors on write today, so a listing created through the seller form has a single-element chain and is invisible on every ancestor page.",
+        expectedUiState: "The product from the child page also appears on the root page, and the root's count is at least the sum of its children's. A root showing only its own directly-tagged products — normally none — is the finding.",
+        endResult: "Read-only.",
+    },
+    "checklist-content-discovery-category-brand-relations-root-page-not-blank-on-large-tree": {
+        roles: ["guest"],
+        startPage: "/categories/category-spinning-tops",
+        steps: [
+            "Open /categories/category-spinning-tops with the browser console open.",
+            "Read whether the product grid renders rows or is empty.",
+            "Read the console for any error.",
+            "Read the network panel for any failed request.",
+            "Change the sort and read the grid again.",
+            "Page forward once and read it again.",
+        ],
+        inputs: { rootId: "category-spinning-tops" },
+        expectedBehaviour: "The root page renders products. Expanding a root into itself plus every descendant on a fifty-node tree exceeds the query's value cap, the query throws, and every caller wraps that fetch so the failure resolves to nothing — a blank grid with no error in the console, no failed request, and nothing to point at.",
+        expectedUiState: "Rows render on the default view and after a sort change and a page forward, with a clean console. A blank grid is the finding precisely BECAUSE nothing else signals it.",
+        expectedData: { consoleErrors: 0 },
+        endResult: "Read-only.",
+    },
+    "checklist-content-discovery-category-brand-relations-mid-tier-scopes-to-own-subtree": {
+        roles: ["guest"],
+        startPage: "/categories/category-beyblade-burst",
+        steps: [
+            "Open /categories/category-spinning-tops and note its product count.",
+            "Open /categories/category-beyblade-burst and note its count.",
+            "Compare the two.",
+            "Open /categories/category-beyblade-metal and note the title of a product listed there.",
+            "Search for it on the Beyblade Burst page.",
+        ],
+        inputs: { parentId: "category-spinning-tops", childId: "category-beyblade-burst" },
+        expectedBehaviour: "A mid-tier category shows its own subtree only. Equal counts on parent and child mean the scoping is not being applied at all — which reads as a working page right up until somebody notices a Metal Fight product on the Burst page.",
+        expectedUiState: "The child's count is strictly smaller than the parent's, and no Metal Fight product appears on the Burst page. Equal counts, or a sibling's product appearing, are both findings.",
+        endResult: "Read-only.",
+    },
+    "checklist-content-discovery-category-brand-relations-store-under-deep-category-visible-at-root": {
+        roles: ["guest"],
+        startPage: "/categories/category-spinning-tops",
+        steps: [
+            "Open /categories/category-spinning-tops and open its Stores tab.",
+            "Read every store listed.",
+            "Open a deeper category under the same root and open its Stores tab.",
+            "Read the stores listed there.",
+            "Check every store from the deeper page also appears on the root's tab.",
+        ],
+        inputs: { rootId: "category-spinning-tops" },
+        expectedBehaviour: "A store carries a SINGLE category with no ancestor chain, so the store side genuinely does need the descendant list — the opposite of the product side. It expanded direct children only, so a store filed three tiers down was invisible on its root while its products were not, which is why the two sides look inconsistent when this breaks.",
+        expectedUiState: "Every store on a descendant category's Stores tab also appears on the root's. A store visible deep and absent at the root is the finding, named.",
+        endResult: "Read-only.",
+    },
+    "checklist-content-discovery-category-brand-relations-brand-page-lists-its-products": {
+        roles: ["guest"],
+        startPage: "/brands/brand-takara-tomy",
+        steps: [
+            "Open /brands/brand-takara-tomy and read the brand name in the hero.",
+            "Read the products listed and count them.",
+            "Open one of those products and read the brand named on its detail page.",
+            "Compare that string against the brand page's name, character for character.",
+            "Repeat on /brands/brand-beyblade.",
+        ],
+        inputs: { brandId: "brand-takara-tomy" },
+        expectedBehaviour: "Products are matched to a brand by its DISPLAY NAME, not its id. The two strings must agree exactly, so renaming a brand orphans its entire catalogue — and the page still renders its hero, its editorial panels and an empty grid, with nothing anywhere reporting that a rename caused it.",
+        expectedUiState: "Both brand pages list products, and each listed product's own detail page names the same brand string as the page's title. An empty grid on a brand with known products is the finding.",
+        endResult: "Read-only.",
+    },
+    "checklist-content-discovery-category-brand-relations-brand-and-category-are-one-collection": {
+        roles: ["guest"],
+        startPage: "/brands/brand-takara-tomy",
+        steps: [
+            "Open /brands/brand-takara-tomy and read every panel on the page.",
+            "Note whether an About-this-brand panel with website, country and founding year is present.",
+            "Open /categories/category-beyblade-burst and read every panel there.",
+            "Check no About-this-brand panel appears on the category page.",
+            "Check both pages render their highlights and questions sections, or neither if both are unset.",
+        ],
+        inputs: { brandId: "brand-takara-tomy", categoryId: "category-beyblade-burst" },
+        expectedBehaviour: "A brand and a category are rows in ONE collection distinguished by a type field, so the only thing keeping their pages apart is that each renders the fields belonging to its own kind. Brand-only fields were seeded and accepted by the interface for a long time while nothing rendered them anywhere.",
+        expectedUiState: "The brand page shows website, country and founding year; the category page shows none of them and shows no empty labelled slots for them either.",
+        endResult: "Read-only.",
+    },
+};

package/dist/features/tester/seed-data/authored/content-discovery__coupons.d.ts

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

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

@@ -0,0 +1,121 @@
+/*
+ * WHY: Authored six-part procedures for the content-discovery/coupons page.
+ * WHAT: 6 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.
+ *
+ * These are the buyer-facing DISCOVERY cases — browsing, claiming, and the
+ * rejection messages. The stacking arithmetic lives on buying/buying-coupons and
+ * is not repeated here; a rule tested in two places drifts in one of them.
+ *
+ * @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-content-discovery-coupons-view-claimed-coupons": {
+        roles: ["buyer"],
+        startPage: "/user/coupons",
+        steps: [
+            "Sign in as vivaan.kapoor@gmail.com / TempPass123!.",
+            "Open /user/coupons and read what is listed.",
+            "Open /promotions, click the 'Coupons' tab, and claim NEWBLADER.",
+            "Open /user/coupons again.",
+            "Read the NEWBLADER row — its code, discount, minimum spend and expiry.",
+            "Reload the page.",
+        ],
+        inputs: { coupon: "NEWBLADER" },
+        expectedBehaviour: "The wallet lists coupons this buyer has claimed, with enough detail to decide whether to use one. An unclaimed coupon has no row here at all, which is why claiming is part of the procedure rather than an assumption.",
+        expectedUiState: "Before claiming, the page either lists previously-claimed coupons or shows a named empty state — not a blank panel. After claiming, a NEWBLADER row appears carrying its code, its discount, any minimum spend and an expiry date. Values reading 'undefined' or 'NaN%' are the shape failure to watch for, since the card reads both a flat and a nested coupon shape.",
+        endResult: "The NEWBLADER row survives the reload.",
+    },
+    "checklist-content-discovery-coupons-coupon-discount-applied": {
+        roles: ["buyer"],
+        startPage: "/promotions",
+        steps: [
+            "Sign in as vivaan.kapoor@gmail.com / TempPass123!.",
+            "Open /promotions, click the 'Coupons' tab, and read the ARENA25 card's stated discount and minimum spend.",
+            "Add product-beyblade-burst-regalia-genesis (₹1,399, Beyblade Arena) to the cart.",
+            "Open /checkout and complete the address and add-ons steps.",
+            "Type ARENA25 in the coupon field and click 'Apply'.",
+            "Read the discount amount applied and compare it with what the card promised.",
+        ],
+        inputs: { coupon: "ARENA25", itemPrice: 1399 },
+        expectedBehaviour: "The discount a public card advertises is the discount checkout applies. A card that states a percentage while checkout applies a cap the card never mentioned is a promise the corpus cannot keep.",
+        expectedUiState: "The applied amount matches the card's stated terms, including any maximum-discount cap the card should also be stating. ARENA25 appears in the applied list with no error.",
+        endResult: "Reloading /checkout shows the same coupon and amount. A discrepancy between the card and the applied amount is a copy bug at minimum and a pricing bug at worst.",
+    },
+    "checklist-content-discovery-coupons-coupon-expired-rejected": {
+        roles: ["buyer"],
+        startPage: "/checkout",
+        steps: [
+            "Sign in as vivaan.kapoor@gmail.com / TempPass123!.",
+            "Add product-beyblade-burst-regalia-genesis (₹1,399) to the cart.",
+            "Open /checkout and complete the address and add-ons steps.",
+            "Type TESTEREXPIRED in the coupon field and click 'Apply'.",
+            "Read the exact wording of the rejection.",
+        ],
+        inputs: { coupon: "TESTEREXPIRED" },
+        expectedBehaviour: "An expired coupon is refused with a reason that names expiry specifically. TESTEREXPIRED is seeded with an end date a day in the past and isActive still true, so this exercises the date check rather than the active flag — the two are separate reasons and a single generic message cannot tell a buyer which applies.",
+        expectedUiState: "The rejection names expiry, in the shape 'This coupon has expired'. It does not read 'Invalid coupon', which would leave the buyer retyping a code that will never work. TESTEREXPIRED does not enter the applied list.",
+        expectedData: { couponApplied: false },
+        endResult: "Reloading /checkout shows TESTEREXPIRED absent.",
+    },
+    "checklist-content-discovery-coupons-coupon-below-min-purchase": {
+        roles: ["buyer"],
+        startPage: "/checkout",
+        steps: [
+            "Sign in as vivaan.kapoor@gmail.com / TempPass123!.",
+            "Add product-tester-standard-3 (₹99) to the cart and nothing else.",
+            "Open /checkout and complete the address and add-ons steps.",
+            "Type ARENA25 in the coupon field and click 'Apply'.",
+            "Read the exact wording of the rejection and whether it names the required amount.",
+        ],
+        inputs: { coupon: "ARENA25", cartSubtotal: 99, minPurchase: 1000 },
+        expectedBehaviour: "A coupon below its minimum spend is refused with a message that names the threshold, so the buyer knows how much more to add. The minimum is measured against the items the coupon could actually discount, not the whole cart.",
+        expectedUiState: "The rejection names a minimum purchase and states the amount. It is not a bare 'Invalid coupon'. ARENA25 does not enter the applied list.",
+        expectedData: { couponApplied: false },
+        endResult: "Reloading /checkout shows ARENA25 absent.",
+    },
+    "checklist-content-discovery-coupons-coupon-not-combinable": {
+        roles: ["buyer"],
+        startPage: "/checkout",
+        steps: [
+            "Sign in as vivaan.kapoor@gmail.com / TempPass123!.",
+            "Add product-beyblade-burst-regalia-genesis (₹1,399, Beyblade Arena) to the cart.",
+            "Open /checkout and complete the address and add-ons steps.",
+            "Type ARENA25 in the coupon field and click 'Apply'.",
+            "Type ARENAVIP in the coupon field and click 'Apply'.",
+            "Read the rejection and check whether it names the coupon already holding the slot.",
+            "Open the 'How coupons work' panel and read whether its rules match what just happened.",
+        ],
+        inputs: { coupon1: "ARENA25", coupon2: "ARENAVIP" },
+        expectedBehaviour: "Both are seller coupons on the same store, and the rule is one per store — so the second is refused. The refusal must name the coupon occupying the slot, otherwise the buyer cannot tell which one to remove.",
+        expectedUiState: "ARENA25 stays applied with its amount unchanged. The rejection names ARENA25 as the blocker. The help panel's stated rules match the behaviour just observed — a panel describing rules the code does not enforce is worse than no panel.",
+        expectedData: { storeCouponCount: 1 },
+        endResult: "Reloading /checkout shows ARENA25 applied and ARENAVIP absent.",
+    },
+    "checklist-content-discovery-coupons-coupon-per-user-limit": {
+        roles: ["buyer"],
+        startPage: "/checkout",
+        steps: [
+            "Sign in as vivaan.kapoor@gmail.com / TempPass123!.",
+            "Add product-beyblade-burst-regalia-genesis (₹1,399) to the cart.",
+            "Open /checkout, complete the address and add-ons steps, apply TESTERLIMITED, and place the order with Cash on Delivery.",
+            "Add product-beyblade-metal-storm-pegasus (₹1,299) to the cart.",
+            "Open /checkout, complete the address and add-ons steps, and type TESTERLIMITED in the coupon field.",
+            "Read the rejection.",
+            "Sign out, sign in as rehan.sheikh@gmail.com / TempPass123!, add the same item, and apply TESTERLIMITED at checkout.",
+        ],
+        inputs: { coupon: "TESTERLIMITED", perUserLimit: 1 },
+        expectedBehaviour: "TESTERLIMITED allows one use per user and has no global limit, so exhausting it for one buyer must leave it fully usable for the next. Enforcing a per-user limit as if it were global would withdraw the coupon from everybody after a single redemption.",
+        expectedUiState: "The second attempt by the same buyer is refused with a limit-reached message. The DIFFERENT buyer's attempt is accepted and the coupon appears in their applied list. A refusal for the second buyer means the limit is being read as global.",
+        expectedData: { perUserLimit: 1 },
+        endResult: "One order carries the discount and a second buyer can still use the code. The cross-account half is the case — the same-account half alone passes under either reading.",
+    },
+};

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

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

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

@@ -0,0 +1,207 @@
+/*
+ * WHY: Authored six-part procedures for the content-discovery/event-participation page.
+ * WHAT: 12 case(s), keyed by full checklist id.
+ *
+ * Events were covered from the ADMIN side — creating them, configuring raffles and
+ * spin wheels, drawing winners. What nobody had written was the participant's own
+ * experience: joining, seeing their own entry, finding themselves on a leaderboard,
+ * and learning that they won.
+ *
+ * That asymmetry is worth naming. An admin surface can look complete while the
+ * participant sees nothing at all, because the two are different pages reading
+ * different projections of the same record — and the admin one is the one that
+ * gets built first and looked at most.
+ *
+ * @tag domain:tester
+ * @tag layer:seed
+ * @tag pattern:none
+ * @tag access:server-only
+ * @tag consumers:seed-data/authored/index.ts
+ * @tag sideEffects:none
+ */
+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",
+        steps: [
+            SIGN_IN_BUYER,
+            "Open /events and pick an event whose status is active.",
+            "Open it and find the control for joining.",
+            "Use it.",
+            "Read the outcome shown.",
+            "Check it states whether the entry was confirmed or waitlisted, and why if waitlisted.",
+        ],
+        expectedBehaviour: "Joining produces an entry with an explicit status. Waitlisted and confirmed are different outcomes with different consequences, so reporting only 'joined' leaves the participant believing they have a place they may not have.",
+        expectedUiState: "The result names the entry's status, and a waitlisted entry says why. A bare success message is the finding.",
+        endResult: "One entry exists for this account.",
+    },
+    "checklist-content-discovery-event-participation-own-entry-visible-after-join": {
+        roles: ["buyer"],
+        startPage: "/events",
+        steps: [
+            SIGN_IN_BUYER,
+            "Join an active event.",
+            "Return to the event page and look for the participant's own entry.",
+            "Read its status there.",
+            "Check the page shows the participant is already in rather than offering to join again.",
+            "Look for the entry anywhere else the buyer's own account lists it.",
+        ],
+        expectedBehaviour: "A participant can see their own entry without asking anyone. An entry that exists only on an admin screen is a record about somebody that they cannot read — and the join control still offering itself is what makes them try again.",
+        expectedUiState: "The event page shows the participant's own entry with its status, and the join control reflects that they are already in.",
+        endResult: "The entry is visible to its owner.",
+    },
+    "checklist-content-discovery-event-participation-entry-survives-reload-and-relogin": {
+        roles: ["buyer"],
+        startPage: "/events",
+        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 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.",
+        expectedUiState: "The entry and its status are present after the reload, after signing back in, and in the second browser.",
+        endResult: "The entry persists.",
+    },
+    "checklist-content-discovery-event-participation-cannot-join-twice": {
+        roles: ["buyer"],
+        startPage: "/events",
+        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.",
+            "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.",
+        expectedUiState: "The second attempt is refused with a message saying the account is already entered, and only one entry exists. Two entries is the finding.",
+        expectedData: { entriesForAccount: 1 },
+        endResult: "Exactly one entry exists.",
+    },
+    "checklist-content-discovery-event-participation-leave-or-cancel-entry": {
+        roles: ["buyer"],
+        startPage: "/events",
+        steps: [
+            SIGN_IN_BUYER,
+            "Join an active event.",
+            "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.",
+            "Check the event's entry count fell.",
+        ],
+        expectedBehaviour: "Withdrawing is possible and is reflected in both the entry and the event's counts. An entry that cannot be withdrawn leaves a participant permanently counted in something they left — and if the counts do not follow, a waitlisted person is never promoted into the freed place.",
+        expectedUiState: "The entry reads as cancelled or is gone, the state survives a reload, and the event's entry count is one lower.",
+        endResult: "The entry is withdrawn.",
+    },
+    "checklist-content-discovery-event-participation-closed-event-cannot-be-joined": {
+        roles: ["buyer"],
+        startPage: "/events",
+        steps: [
+            SIGN_IN_BUYER,
+            "Open /events and find an event whose status is ended.",
+            "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.",
+            "Repeat with one whose status is paused.",
+        ],
+        expectedBehaviour: "An event that cannot be joined says so on the page rather than accepting a click and failing at submit. The status set includes paused and cancelled alongside ended, and each has to be handled — a page that only knows about ended lets the other two through.",
+        expectedUiState: "None of the three offers a working join control, and each states its own status. A control that fails only on submit is the finding, named by status.",
+        endResult: "No entry is created.",
+    },
+    "checklist-content-discovery-event-participation-leaderboard-shows-real-participants": {
+        roles: ["buyer"],
+        startPage: "/events",
+        steps: [
+            SIGN_IN_BUYER,
+            "Open an event that has a leaderboard and open that tab.",
+            "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.",
+            "Cross-check one row against the event's entry list if it is visible.",
+        ],
+        expectedBehaviour: "The leaderboard lists real entrants with real scores, and their names are masked. A masking helper that only copies its input instead of masking is invisible everywhere except to a human who recognises a real name — one shipped in exactly that shape and sat, because the field it should have masked was not being displayed at all.",
+        expectedUiState: "Real participants with real scores, each name partially hidden. A full name is a finding and a leak; all-zero scores is a separate finding.",
+        endResult: "Read-only.",
+    },
+    "checklist-content-discovery-event-participation-leaderboard-own-row-findable": {
+        roles: ["buyer"],
+        startPage: "/events",
+        steps: [
+            SIGN_IN_BUYER,
+            "Join an event that has a leaderboard and take part enough to appear on it.",
+            "Open the leaderboard.",
+            "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.",
+        ],
+        expectedBehaviour: "A participant can find themselves. A leaderboard is read almost entirely to answer one question — where am I — and on a long list without a marker that answer requires scrolling past everyone else.",
+        expectedUiState: "The participant's own row is marked or surfaced, with their position. Having to scroll a long list to find it is the finding.",
+        endResult: "Read-only.",
+    },
+    "checklist-content-discovery-event-participation-leaderboard-ordering-correct": {
+        roles: ["buyer"],
+        startPage: "/events",
+        steps: [
+            SIGN_IN_BUYER,
+            "Open an event leaderboard and write down the first ten rows in order with their scores.",
+            "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.",
+            "Check the order is identical, including the tied pair.",
+        ],
+        expectedBehaviour: "The ordering is by score and is stable across reloads, ties included. An unstable tie break swaps positions between two visits — so a participant sees themselves at rank 6 and then rank 7 with nothing having changed, which reads as the site losing their score.",
+        expectedUiState: "Scores are non-increasing down the list, and the whole order including the tied pair is identical after the reload.",
+        endResult: "Read-only.",
+    },
+    "checklist-content-discovery-event-participation-leaderboard-empty-state": {
+        roles: ["buyer"],
+        startPage: "/events",
+        steps: [
+            SIGN_IN_BUYER,
+            "Open /events and find an event with no entries yet, such as a draft or a newly-started one.",
+            "Open its leaderboard.",
+            "Read what is shown.",
+            "Check it states there are no entries rather than showing a blank panel.",
+            "Check whatever chrome the leaderboard has — headings, columns — either renders sensibly or is omitted.",
+        ],
+        expectedBehaviour: "An empty leaderboard says it is empty. A blank panel is indistinguishable from a leaderboard that failed to load, and the participant's reasonable conclusion is that their entry was lost.",
+        expectedUiState: "An explicit empty state. A blank area, or column headings over nothing, are both findings.",
+        endResult: "Read-only.",
+    },
+    "checklist-content-discovery-event-participation-raffle-winner-announced-to-participants": {
+        roles: ["admin", "buyer"],
+        startPage: "/events",
+        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 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.",
+        ],
+        expectedBehaviour: "A drawn raffle is announced on the event page and the winner is notified. A result that exists only in the admin screen means the winner never learns they won — and the notification's link has to land somewhere real, which for entries means the list rather than a fabricated per-entry page that would 404.",
+        expectedUiState: "The event page names the winner, the winner has a notification, and other participants can see the result. A win visible only to an admin is the finding.",
+        endResult: "One raffle is drawn.",
+    },
+    "checklist-content-discovery-event-participation-spin-wheel-one-use-enforced": {
+        roles: ["buyer"],
+        startPage: "/events",
+        steps: [
+            SIGN_IN_BUYER,
+            "Open /events and find a spin-wheel event that is currently open.",
+            "Take a spin and read the result.",
+            "Attempt to spin again immediately.",
+            "Read what happens.",
+            "Reload the page and attempt 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.",
+    },
+};

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

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