@mohasinac/appkit 4.58.0 → 4.60.0

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

@@ -1,169 +0,0 @@
-/*
- * 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 — it redirects to /promotions/deals, which is expected — then click the 'Coupons' tab, landing on /promotions/coupons, 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 — it redirects to /promotions/deals — then 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.",
-    },
-    /*
-     * 🛑 THE EXPIRY IS NOW AUTHORED, 2026-09-15.
-     *
-     * This used to use a coupon seeded past its end date while still flagged
-     * active — the one shape that exercises the DATE check rather than the flag.
-     * That fixture is gone and every permanent coupon has a future end date, so
-     * the admin sets one back by hand. Leaving Active ON is the whole point: a
-     * validator that reads only the flag accepts this coupon, and that is the bug.
-     */
-    "checklist-content-discovery-coupons-coupon-expired-rejected": {
-        roles: ["admin", "buyer"],
-        startPage: "/admin/coupons",
-        steps: [
-            "Sign in as admin@letitrip.in / TempPass123!.",
-            "Open /admin/coupons, open SEALED20 for editing, and write down its end date.",
-            "Set its end date to yesterday and LEAVE the Active toggle ON, then save.",
-            "Sign out and 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 SEALED20 in the coupon field and click 'Apply'.",
-            /*
-             * 🛑 EXPECT THIS TO FAIL TODAY, AND RECORD IT AS A FAILURE.
-             *
-             * Measured 2026-09-29: the only rejection this path can produce is
-             * "Coupon is not currently valid" (coupons.repository.ts:241). It is
-             * returned by one branch gated on isCouponValid(), which folds THREE
-             * separate reasons into one string — isActive false, the date window,
-             * and the total usage limit being exhausted.
-             *
-             * So the buyer is told the same thing whether the coupon expired
-             * yesterday, was switched off, or was claimed by someone else thirty
-             * seconds ago. Only the first is permanent; the third may well work on a
-             * retry. The message cannot tell them which, and there is no second
-             * message to fall back to.
-             *
-             * Kept as written rather than softened to match. This case previously
-             * demanded the string 'This coupon has expired', which exists NOWHERE in
-             * the codebase — so the assertion could never be satisfied and never
-             * fail informatively either. Naming the real string is what makes the
-             * failure actionable.
-             */
-            "Read the exact wording of the rejection.",
-            "Sign back in as admin@letitrip.in and restore the end date written down in step 2.",
-        ],
-        inputs: { coupon: "SEALED20" },
-        expectedBehaviour: "An expired coupon is refused with a reason that names expiry specifically. With the end date in the past and isActive still true, 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. Today it reads 'Coupon is not currently valid', which names nothing — record that as the failure, quoting it. SEALED20 must still be kept out of the applied list; a coupon that is refused and applied anyway would be a far worse finding than the wording.",
-        expectedData: { couponApplied: false },
-        endResult: "Reloading /checkout shows SEALED20 absent. The end date is restored by the final step — leaving it in the past silently breaks every later coupon case.",
-    },
-    "checklist-content-discovery-coupons-coupon-below-min-purchase": {
-        roles: ["buyer"],
-        startPage: "/checkout",
-        steps: [
-            "Sign in as vivaan.kapoor@gmail.com / TempPass123!.",
-            "Add product-beyblade-x-wizard-arrow (₹899 — the cheapest in-stock listing in the catalogue, and below ARENA25's ₹1,000 minimum) 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'.",
-            /*
-             * 🛑 THE SECOND HALF OF THIS EXPECTS TO FAIL TODAY.
-             *
-             * Measured 2026-09-29: the message is "Minimum purchase requirement not
-             * met" — the same literal from both producing branches, and no UI
-             * composes the threshold into it (zero .tsx read `minPurchase` outside
-             * the admin editor). So the buyer is told they are short without being
-             * told of what, on a cart they can see is ₹99 against a threshold they
-             * cannot see at all.
-             *
-             * The first half — that it names the minimum-purchase REASON rather than
-             * being a bare "Invalid coupon" — does hold, and is worth keeping
-             * separate: reason and amount are two assertions and only one fails.
-             */
-            "Read the exact wording of the rejection and whether it names the required amount.",
-        ],
-        inputs: { coupon: "ARENA25", cartSubtotal: 899, 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 the minimum-purchase reason — today 'Minimum purchase requirement not met', which satisfies that half — and states the AMOUNT, which it does not. Record the missing amount as the failure, quoting the message. 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 2 × product-beyblade-original-dranzer-s (₹1,499 each, ₹2,998 total — above ARENAVIP's ₹2,000 minimum and in an eligible category) to the cart.",
-            "Open /checkout, complete the address and add-ons steps, apply ARENAVIP, and place the order with Cash on Delivery.",
-            "Add 2 × product-beyblade-original-dranzer-s to the cart again.",
-            "Open /checkout, complete the address and add-ons steps, and type ARENAVIP in the coupon field.",
-            "Read the rejection.",
-            "Sign out, sign in as rehan.sheikh@gmail.com / TempPass123!, add the same two items, and apply ARENAVIP at checkout.",
-        ],
-        inputs: { coupon: "ARENAVIP", perUserLimit: 1 },
-        expectedBehaviour: "ARENAVIP allows one use per user, and its total limit of 50 has 38 uses left — so exhausting it for one buyer must leave it usable by 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-detail-subroutes.d.ts

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

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

@@ -1,209 +0,0 @@
-/*
- * WHY: Authored six-part procedures for content-discovery/event-detail-subroutes.
- * WHAT: 8 cases, keyed by full checklist id.
- *
- * 🛑 ALL 29 EXISTING EVENT CASES STOP AT THE INDEX. `/events/[id]/` has four
- * subroutes — participate, leaderboard, winner, spin-results — and none of them
- * had a single case. Several real defects were found on exactly these pages by
- * hand during the 2026-09 run, which is the ordinary consequence of a surface
- * nobody has a procedure for.
- *
- * Fixtures are named by id because event behaviour is type- and status-specific:
- * a poll and a raffle share a route and share almost nothing else, and "open an
- * event" is a different test every run.
- *
- * @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-event-detail-subroutes-detail-tabs-match-event-type": {
-        roles: ["guest"],
-        startPage: "/events/event-favourite-blader-poll",
-        steps: [
-            "Open /events/event-favourite-blader-poll — a poll.",
-            "Write down every tab shown.",
-            "Open /events/event-original-series-clearance — a sale.",
-            "Write down its tabs.",
-            "Open /events/event-win-burst-regalia-genesis — a raffle.",
-            "Write down its tabs.",
-        ],
-        inputs: {
-            pollEvent: "event-favourite-blader-poll",
-            saleEvent: "event-original-series-clearance",
-            raffleEvent: "event-win-burst-regalia-genesis",
-        },
-        expectedBehaviour: "The tab bar is derived from the event's type. A tab offered for a type that cannot have it leads to a page with nothing to render — and a blank panel reads as a loading failure rather than as a tab that should not exist.",
-        expectedUiState: "The poll shows no Spin Results and no Winner tab. The sale shows no Leaderboard. The raffle shows a Winner tab.",
-        expectedData: { tabWithNoContentShown: false },
-        endResult: "Nothing is changed; this case only reads.",
-    },
-    "checklist-content-discovery-event-detail-subroutes-participate-records-an-entry": {
-        roles: ["buyer"],
-        startPage: "/events/event-favourite-blader-poll",
-        steps: [
-            "Sign in as the buyer rehan.sheikh@gmail.com / TempPass123!.",
-            "Open /events/event-favourite-blader-poll.",
-            "Open its Participate tab.",
-            "Submit the first available option.",
-            "Reload the page.",
-            "Read what the Participate tab shows now.",
-        ],
-        inputs: { eventId: "event-favourite-blader-poll" },
-        expectedBehaviour: "Participation writes an entry and the page reflects it afterwards. A write that succeeds while the screen keeps offering the form is the classic split between behaviour and UI state — and it leads a user to submit repeatedly.",
-        expectedUiState: "After the reload the tab shows the submitted answer or a 'you have taken part' state, not the blank form again.",
-        expectedData: { entryPersisted: true },
-        endResult: "The entry is still recorded after a second reload.",
-    },
-    "checklist-content-discovery-event-detail-subroutes-participate-twice-is-refused": {
-        roles: ["buyer"],
-        startPage: "/events/event-favourite-blader-poll",
-        steps: [
-            "Sign in as the buyer rehan.sheikh@gmail.com / TempPass123! and open /events/event-favourite-blader-poll.",
-            "Participate once if you have not already.",
-            "Reload, and try to participate a second time with a different option.",
-            "Read what happens.",
-            "Open /events/event-favourite-blader-poll, then its Leaderboard tab, and read the total entry count. This case reads the state the previous one left behind, so run them in order — but it still has to start somewhere, and the index is not it.",
-        ],
-        inputs: { eventId: "event-favourite-blader-poll" },
-        expectedBehaviour: "A second entry from the same account is refused with a reason. Silently accepting it doubles that account's weight in the result, which is invisible until somebody reconciles the entry count against the participant count.",
-        expectedUiState: "A clear refusal naming the reason. The entry total does not rise by a second entry from this account.",
-        expectedData: { duplicateEntryAccepted: false },
-        endResult: "Exactly one entry for this account survives a reload.",
-    },
-    "checklist-content-discovery-event-detail-subroutes-leaderboard-ranks-by-a-real-number": {
-        roles: ["guest"],
-        startPage: "/events/event-favourite-blader-poll/leaderboard",
-        steps: [
-            "Open /events/event-favourite-blader-poll and open its Leaderboard tab.",
-            "Read the number beside each of the first five rows — the vote or score the row is ranked on.",
-            "Check that those numbers are in descending order.",
-            "Read the total entry count the event reports.",
-            "Count the rows the leaderboard lists, paging if needed.",
-        ],
-        inputs: { eventId: "event-favourite-blader-poll" },
-        expectedBehaviour: "The leaderboard orders by a stored number and covers the same entries the event counts. A ranking that is merely insertion order looks correct whenever the data happens to arrive sorted, so the descending check has to be explicit.",
-        expectedUiState: "The numbers descend down the list, and the number of entries listed matches the count the event reports. A leaderboard showing no number at all beside each row is the failure — there is then nothing it can be ranking by.",
-        expectedData: { scoresDescending: true },
-        endResult: "Nothing is changed; this case only reads.",
-    },
-    "checklist-content-discovery-event-detail-subroutes-winner-page-before-draw": {
-        roles: ["guest"],
-        startPage: "/events/event-win-burst-regalia-genesis/winner",
-        steps: [
-            "Open /events/event-win-burst-regalia-genesis — an ACTIVE raffle that has not been drawn.",
-            "Open its Winner tab.",
-            "Read the page.",
-        ],
-        inputs: { eventId: "event-win-burst-regalia-genesis" },
-        expectedBehaviour: "An undrawn raffle has no winner, and the page must say so. A blank panel is indistinguishable from a failed load, and any name shown here before a draw is fabricated — which on a prize event is the worst possible thing to render.",
-        expectedUiState: "A clear statement that the draw has not happened yet, ideally with when it will. No name, no masked name, no empty winner card.",
-        expectedData: { winnerNameShown: false },
-        endResult: "Nothing is changed; this case only reads.",
-    },
-    "checklist-content-discovery-event-detail-subroutes-winner-page-after-draw": {
-        roles: ["guest"],
-        startPage: "/events/event-won-original-set-raffle/winner",
-        steps: [
-            "Open /events/event-won-original-set-raffle — an ENDED raffle with a recorded winner.",
-            "Open its Winner tab.",
-            "Read the winner shown and the prize named.",
-            "Open the event's Overview and compare the prize named there.",
-        ],
-        inputs: { eventId: "event-won-original-set-raffle" },
-        expectedBehaviour: "The winner page reads the winner recorded on the event. The displayed name is masked, as every other public surface masks a user's name.",
-        expectedUiState: "A winner is named in masked form and the prize matches what the Overview describes.",
-        expectedData: { winnerShown: true },
-        endResult: "Nothing is changed; this case only reads.",
-    },
-    "checklist-content-discovery-event-detail-subroutes-cancelled-event-refuses-participation": {
-        roles: ["buyer"],
-        startPage: "/events/event-x-launch-raffle-cancelled",
-        steps: [
-            "Sign in as the buyer rehan.sheikh@gmail.com / TempPass123!.",
-            "Open /events/event-x-launch-raffle-cancelled — a CANCELLED raffle.",
-            "Read the event header for its status.",
-            "Open the Participate tab.",
-            "Try to take part.",
-        ],
-        inputs: { eventId: "event-x-launch-raffle-cancelled" },
-        expectedBehaviour: "A cancelled event accepts nothing. The status is checked server-side as well as hidden in the UI: a Participate tab that merely hides its button still has an endpoint behind it.",
-        expectedUiState: "The header says Cancelled, and the Participate tab explains that the event is closed rather than offering a form.",
-        expectedData: { participationAccepted: false },
-        endResult: "No entry is recorded; the entry count is unchanged after a reload.",
-    },
-    "checklist-content-discovery-event-detail-subroutes-guest-sees-event-but-is-prompted": {
-        roles: ["guest"],
-        startPage: "/events",
-        steps: [
-            "Open a private window with no session.",
-            "Open /events/event-favourite-blader-poll.",
-            "Read the Overview — the title, the description and the dates.",
-            "Open the Participate tab.",
-            "Read what it offers.",
-        ],
-        inputs: { eventId: "event-favourite-blader-poll" },
-        expectedBehaviour: "An event is public reading and gated taking-part. Being prompted to sign in IS the expected result — the failure to look for is a hard redirect off the page, which loses the visitor the content they came for, or a form that submits and fails.",
-        expectedUiState: "The event's own content is readable. Participate shows a sign-in prompt rather than a form, and nothing 404s or bounces to /unauthorized.",
-        expectedData: { eventContentReadableByGuest: true },
-        endResult: "No entry is recorded and no session is created.",
-    },
-    /*
-     * 🛑 SPLIT IN TWO, 2026-09-29, after this case failed for a reason that was
-     * not a bug in the code it was testing.
-     *
-     * It asserted that /events/{id}/spin-results lists "this account's own spins".
-     * The route was a PUBLIC feed — `getSpinResultsCached(id)` took only the event
-     * id and returned the ten most recent spins across all users — so read by a
-     * buyer who had never spun it listed three strangers' prizes and showed no
-     * empty state, because from the feed's point of view nothing was empty.
-     *
-     * Both readings turned out to be wanted, so the page now has two sections and
-     * there are two cases. Rewriting the single case to assert whatever the code
-     * already did would have made it a tautology; deleting the account-scoped
-     * claim would have thrown away the one a human actually cared about.
-     */
-    "checklist-content-discovery-event-detail-subroutes-spin-results-subroute": {
-        roles: ["buyer"],
-        startPage: "/events/event-daily-beyblade-pull-wheel/spin-results",
-        steps: [
-            "Sign in as the buyer rehan.sheikh@gmail.com / TempPass123!.",
-            "Open /events/event-daily-beyblade-pull-wheel — a SPIN_WHEEL event, active, with real spinPrizes and spinMaxPerUser of 2.",
-            "Read which tabs the detail page offers and check a results tab is among them.",
-            "Open /events/event-daily-beyblade-pull-wheel/spin-results directly by URL.",
-            "Find the 'Last 10 Spin Results' section — the PUBLIC feed of everyone's recent spins, which is a different section from 'Your Spins'.",
-            "Read the participant name on each row.",
-        ],
-        inputs: {
-            eventId: "event-daily-beyblade-pull-wheel",
-        },
-        expectedBehaviour: "The public feed lists recent spins by ANY participant, and every display name is masked. This is a public page on a public event, so a real winner's full name must not be published beside the prize they won — the same rule that applies to bidder names on public bid history.",
-        expectedUiState: "A 'Last 10 Spin Results' heading over rows of participant, prize and relative time. Every signed-in participant's name is masked to initials in the 'R*** K***' shape; a guest row reads 'Guest'. No row shows a full first and last name.",
-        expectedData: { fullNamesVisibleInPublicFeed: 0 },
-        endResult: "Read-only. Nothing is spun and nothing is written.",
-    },
-    "checklist-content-discovery-event-detail-subroutes-my-spins-scoped-to-viewer": {
-        roles: ["buyer"],
-        startPage: "/events/event-daily-beyblade-pull-wheel/spin-results",
-        steps: [
-            "Sign in as the buyer rehan.sheikh@gmail.com / TempPass123!.",
-            "Open /events/event-daily-beyblade-pull-wheel/spin-results.",
-            "Find the 'Your Spins' section — it sits ABOVE the public 'Last 10 Spin Results' feed.",
-            "Before spinning, read what it shows. It must name YOUR state, not the event's: 'You have not spun on this event yet.' Reading 'No spins yet' here would be the bug this case exists for, because the public feed below is not empty.",
-            "Go back to the event, spin once, and read the prize awarded.",
-            "Return to spin-results and check 'Your Spins' lists exactly that one spin with that prize.",
-            "Confirm no other participant's row appears inside 'Your Spins' — the strangers visible in the feed below must not be in your own section.",
-        ],
-        inputs: {
-            eventId: "event-daily-beyblade-pull-wheel",
-            spinMaxPerUser: 2,
-        },
-        expectedBehaviour: "'Your Spins' is scoped to the signed-in caller and answers what did I win. Its empty state is about the viewer, so someone who has never spun is told so plainly rather than being shown other people's prizes with nothing to distinguish them.",
-        expectedUiState: "Before spinning: a 'Your Spins' heading over the text 'You have not spun on this event yet.' After one spin: exactly one row naming the prize just awarded and its relative time, and no participant names at all — every row in this section is yours by construction.",
-        expectedData: { mySpinRowsBeforeSpinning: 0, mySpinRowsAfterOneSpin: 1 },
-        endResult: "One spin is recorded against this account and 'Your Spins' still shows it after a reload. Signed out, the section reads 'Sign in to see your own spins and the prizes you have won.' rather than showing anyone else's.",
-    },
-};

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

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

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

@@ -1,207 +0,0 @@
-/*
- * 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/event-favourite-blader-poll",
-        steps: [
-            SIGN_IN_BUYER,
-            "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.",
-            "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/event-favourite-blader-poll",
-        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/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 /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.",
-        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/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 /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.",
-        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/event-favourite-blader-poll",
-        steps: [
-            SIGN_IN_BUYER,
-            "Join an active event.",
-            "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.",
-            "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/event-won-original-set-raffle",
-        steps: [
-            SIGN_IN_BUYER,
-            "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.",
-            "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/event-favourite-blader-poll/leaderboard",
-        steps: [
-            SIGN_IN_BUYER,
-            "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.",
-            "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/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 /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.",
-        ],
-        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/event-favourite-blader-poll/leaderboard",
-        steps: [
-            SIGN_IN_BUYER,
-            "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.",
-            "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/event-beyblade-slot-raffle-draft",
-        steps: [
-            SIGN_IN_BUYER,
-            "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.",
-            "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/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 /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.",
-        ],
-        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/event-daily-beyblade-pull-wheel",
-        steps: [
-            SIGN_IN_BUYER,
-            "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.",
-            "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 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.d.ts

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