@mohasinac/appkit 4.58.0 → 4.59.0

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

@@ -1,125 +0,0 @@
-/*
- * WHY: Authored six-part procedures for the page-wiring/data-loss page.
- * WHAT: 4 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.
- *
- * 🛑 EVERY CASE HERE ENDS IN A RELOAD, and that is not padding. All four bugs
- * these cases exist for returned HTTP 200 with a success message and wrote
- * nothing, or wrote the wrong thing. The screen after saving looked correct in
- * every one of them; only the reload told the truth.
- *
- * 🛑 SLOTS 1-5 ARE ALREADY BOOKED IN THE SEED (corrected 2026-09-29), so the
- * first case could not start: it told the tester to pull slot 3, and slot 3 is
- * taken by 'Arjun M'. `maxPullsPerUser` is 1 on this lottery, so a pull is also
- * a once-per-persona-per-run action and a poor fixture for a case about
- * surviving an edit. The seeded bookings ARE the fixture; no pull is needed.
- *
- * 🛑 AND NONE OF THE FIVE BOOKERS IS A REAL ACCOUNT. user-ravi-k,
- * user-priya-s, user-arjun-m, user-sneha-p and user-vikram-r appear in
- * events-seed-data.ts (as lotteryConfig.slots[].bookedByUserId) and in
- * lottery-entries-seed-data.ts, and NONE of them exists in users-seed-data.ts.
- * So nobody can sign in as the person who booked slot 3, and any step asking
- * for that is unperformable. The buyer-side check is done from the public page
- * instead, which needs no account. Recorded in OUTOFSCOPE: dangling seed FKs
- * are data, and repairing them is not a case edit.
- *
- * @tag domain:tester
- * @tag layer:seed
- * @tag pattern:none
- * @tag access:server-only
- * @tag consumers:seed-data/authored/index.ts
- * @tag sideEffects:none
- */
-export const authored = {
-    "checklist-page-wiring-data-loss-lottery-edit-preserves-bookings": {
-        roles: ["admin", "guest"],
-        startPage: "/admin/lotteries",
-        steps: [
-            "Sign in as admin@letitrip.in / TempPass123! and open /lottery/event-pokemon-number-draw-july-2026.",
-            "Read the slot grid and write down slots 1 to 5 — all five are booked in the seed — recording each slot number, the buyer name shown against it and its lottery number.",
-            "Open /admin/lotteries and open the editor for that lottery.",
-            "Rename slot number 7 to 'QA Slot lottery-edit-preserves-bookings'. Slot 7 is 'Alakazam Base Set Holo' and is NOT booked — renaming an unbooked slot is the whole point.",
-            "Save.",
-            "Reload the editor and read slots 1 to 5 against what was written down, then read slot 7.",
-            "Read the price on each of slots 1 to 5 as well — slot 1 is 5000, slot 3 is 2500 — and confirm none has become 0.",
-            "Sign out and open /lottery/event-pokemon-number-draw-july-2026 to read the same five slots as a visitor sees them.",
-        ],
-        inputs: {
-            bookedSlots: "1, 2, 3, 4, 5",
-            renamedSlot: 7,
-            newName: "QA Slot lottery-edit-preserves-bookings",
-            slot1Price: 5000,
-            slot3Price: 2500,
-        },
-        expectedBehaviour: "The write shape cannot express booking state at all, so an admin editing prize names cannot touch attendance. Bookings are re-attached from the stored config and matched by slot NUMBER, never by array position — deleting a slot shifts every later index, and an index-wise merge hands slot 7's buyer the prize that was slot 8's.",
-        expectedUiState: "After the save and reload, all five booked slots are still booked, carrying the same buyer names and the same lottery numbers. Slot 7 carries its new name. Every price is unchanged — a grid of zeros is the same defect's twin, caused by seeding the editor from the public projection, which strips price and weight. The public page shows the same five slots still taken.",
-        expectedData: { bookedSlotsAfterSave: 5, slotsPricedZero: 0 },
-        endResult: "The pull survives the admin edit. The editor once sent isBooked:false for every slot into a passthrough route, so the first save of a live lottery marked every purchased slot available again and erased the buyers — with a success message and no error anywhere.",
-    },
-    "checklist-page-wiring-data-loss-lottery-booked-slot-cannot-be-deleted": {
-        roles: ["admin"],
-        startPage: "/admin/lotteries",
-        steps: [
-            "Sign in as admin@letitrip.in / TempPass123!.",
-            "Open /admin/lotteries and open the editor for event-pokemon-number-draw-july-2026.",
-            "Find slot number 3, which the seed ships already booked by 'Arjun M' — no earlier case has to run for this to be true.",
-            "Remove that slot from the list.",
-            "Save.",
-            "Read the error message.",
-            "Reload the editor and read slot 3.",
-        ],
-        inputs: { bookedSlot: 3 },
-        expectedBehaviour: "Removing a slot somebody has pulled is refused as a CONFLICT, not as a validation error. The request is well formed and the admin is not confused — the world changed under them, and the correct next action is to reopen the pull rather than fix a field.",
-        expectedUiState: "The save fails and the message names the slot number that blocked it, so the admin knows which one to deal with. It does not read as a form error attached to a field, and it is not a generic 'Something went wrong'.",
-        expectedData: { slot3StillPresent: true },
-        endResult: "Slot 3 is still there and still booked after the reload. A save that succeeds and quietly drops the slot is the failure.",
-    },
-    "checklist-page-wiring-data-loss-admin-grouped-listing-title-actually-saves": {
-        roles: ["admin"],
-        startPage: "/admin/grouped-listings",
-        steps: [
-            "Sign in as admin@letitrip.in / TempPass123!.",
-            "Open /admin/grouped-listings, find group-beyblade-original-lineage, and write down its exact title.",
-            "Open /admin/grouped-listings/group-beyblade-original-lineage/edit.",
-            "Replace the title with 'QA Group admin-grouped-listing-title-actually-saves'.",
-            "Save and read the confirmation.",
-            "RELOAD the page.",
-            "Read the title.",
-            "Set the title back to what it was and save.",
-        ],
-        inputs: {
-            group: "group-beyblade-original-lineage",
-            newTitle: "QA Group admin-grouped-listing-title-actually-saves",
-        },
-        expectedBehaviour: "The admin PATCH accepts every field the editor can send, not just productIds. A Zod object schema STRIPS unknown keys rather than rejecting them, so a schema listing only productIds turned a title change into a perfectly normal 200 that wrote nothing at all. Verified fixed on 2026-09-29 — the admin route now parses the same strict schema as the seller route, so a pass here is the expected result. It is kept because the failure was invisible without a reload and would return the moment the two schemas diverge again.",
-        expectedUiState: "After the reload the title is the new one. A save confirmation followed by the OLD title after reload is the exact failure — and without the reload the screen looks identical either way, because the form is still showing what was typed.",
-        expectedData: { titlePersisted: true },
-        endResult: "The title is restored to its original value by the final step, so other cases that read this group by name still work.",
-    },
-    "checklist-page-wiring-data-loss-store-address-landmark-survives-edit": {
-        roles: ["seller"],
-        startPage: "/store/addresses",
-        steps: [
-            "Sign in as tyson@beybladearena.in / TempPass123!.",
-            "Open /store/addresses and create a pickup address from the drawer: name 'QA Address landmark-survives', street '8 Test Lane', city 'Indore', state 'Madhya Pradesh', pincode 452010, landmark 'Opposite the stadium gate'.",
-            "Save and reload the page, then read the address's landmark.",
-            "Open /store/addresses/{id}/edit for that address.",
-            "Change the street to '9 Test Lane' and leave everything else alone.",
-            "Save.",
-            "RELOAD the page and read the landmark.",
-        ],
-        inputs: {
-            name: "QA Address landmark-survives",
-            landmark: "Opposite the stadium gate",
-            streetBefore: "8 Test Lane",
-            streetAfter: "9 Test Lane",
-        },
-        expectedBehaviour: "The edit form carries every field the route accepts. A form missing one field does not leave it alone — it sends undefined, and undefined overwrites. The landmark was dropped on every single edit for exactly that reason.",
-        expectedUiState: "After the reload the street reads '9 Test Lane' AND the landmark still reads 'Opposite the stadium gate'. A blank landmark after an unrelated edit is the failure, and it is invisible until the reload.",
-        expectedData: { landmark: "Opposite the stadium gate" },
-        endResult: "Delete the address afterwards. What this case really asks of any authoring form is: what does the stored record hold that the form cannot name?",
-    },
-};

package/dist/features/tester/seed-data/authored/page-wiring__detail-pages.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/page-wiring__detail-pages.js

@@ -1,85 +0,0 @@
-/*
- * WHY: Authored six-part procedures for the page-wiring/detail-pages page.
- * WHAT: 3 case(s), keyed by full checklist id.
- *
- * 🛑 REHAN NEVER BID (corrected 2026-09-29). The identity case said to find a
- * bid placed by rehan.sheikh@gmail.com. Only three personas bid anywhere in the
- * seed: user-rohit-collector, user-ananya-collector and user-meera-bey. So the
- * step found nothing, and its buyer half would then have been signing in as
- * someone looking at another person's bid, which is a different test entirely.
- *
- * Bid ids are DERIVED and therefore knowable:
- *   bid-{auctionSuffix}-{userSuffix}-20260601-{NNN}
- * so the first bid on auction-beyblade-original-dragoon-storm is
- *   bid-beyblade-original-dragoon-storm-rohit-collector-20260601-000
- * That auction has three distinct bidders, which is what makes it the right
- * fixture for a case about seeing other people's identities.
- *
- * ONE builder, FOUR viewers. `buildBidDetailFields(bid, viewer)` is called by
- * AdminBidsView's modal ('admin'), UserBidsView ('buyer'), SellerBidsView
- * ('seller') and the shared BidDetailPageClient behind all three /view pages.
- * Its only viewer-dependent row is Bidder, added when viewer !== 'buyer'. The
- * seller leg had no case at all and now has one.
- *
- * Written by hand, case by case, against the label each one states. There is no
- * generator: the authoring scripts were deleted once it was clear they were
- * scaffolding around work that is simply writing.
- *
- * @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-page-wiring-detail-pages-detail-page-matches-list-modal": {
-        roles: ["admin"],
-        startPage: "/admin/bids",
-        steps: [
-            "Sign in as admin@letitrip.in / TempPass123!.",
-            "Open /admin/bids and open the first bid row so its modal appears.",
-            "Write down every field label the modal shows, in order.",
-            "Click the modal's 'Open full page' link and note the URL it lands on.",
-            "Confirm that URL is /admin/bids/{that bid id}/view.",
-            "Write down every field label that page shows, in order.",
-            "Compare the two lists.",
-        ],
-        expectedBehaviour: "The modal and the page are two renderings of ONE field builder, so their field sets are identical by construction. Any difference means a second copy of the builder has appeared, and two copies of a field list drift the first time one is edited.",
-        expectedUiState: "Both surfaces show the same labels, in the same order, with the same values. A field present in one and missing from the other is the failure — including a field the page adds that the modal does not have.",
-        endResult: "Read-only; nothing persists. Comparing labels rather than layout is deliberate: the two are allowed to look different, they are not allowed to say different things.",
-    },
-    "checklist-page-wiring-detail-pages-detail-page-hides-identity-per-portal": {
-        roles: ["admin", "buyer"],
-        startPage: "/admin/bids",
-        steps: [
-            "Sign in as admin@letitrip.in / TempPass123!.",
-            "Open /admin/bids/bid-beyblade-original-dragoon-storm-rohit-collector-20260601-000/view directly. It is the first of three bids on auction-beyblade-original-dragoon-storm, placed by rohit.collect@gmail.com.",
-            "Write down every bidder name and identifier shown anywhere on the page.",
-            "Sign out and sign in as rohit.collect@gmail.com / TempPass123!, the buyer who placed it.",
-            "Open /user/bids/bid-beyblade-original-dragoon-storm-rohit-collector-20260601-000/view.",
-            "Write down every bidder name and identifier shown anywhere on that page, including in the page source.",
-        ],
-        expectedBehaviour: "One viewer argument decides what each portal reveals, in one place. The admin view may name other bidders because moderating a dispute requires it; the buyer's own view must not, because a competitor's identity is not the buyer's to see.",
-        expectedUiState: "The admin page shows a Bidder row naming who placed it; the buyer page omits that row entirely — it is the one field buildBidDetailFields makes viewer-dependent, added only when the viewer is not the buyer. Check the page source too, not merely what is rendered. A competing bidder's real name anywhere in the buyer view is a leak.",
-        expectedData: { otherBidderNamesInBuyerView: 0 },
-        endResult: "Read-only; nothing persists. A buyer view that shows nothing at all also fails — the buyer must still see their own bid.",
-    },
-    "checklist-page-wiring-detail-pages-detail-page-seller-sees-bidder": {
-        roles: ["seller"],
-        startPage: "/store/bids",
-        steps: [
-            "Sign in as tyson@beybladearena.in / TempPass123!.",
-            "Open /store/bids and open the first bid row so its modal appears.",
-            "Write down every field label the modal shows, in order.",
-            "Open /store/bids/bid-beyblade-original-dragoon-storm-rohit-collector-20260601-000/view directly.",
-            "Write down every field label that page shows, in order, and compare the two lists.",
-            "Read whether a Bidder row is present and what it names.",
-        ],
-        inputs: { bidId: "bid-beyblade-original-dragoon-storm-rohit-collector-20260601-000", viewer: "seller" },
-        expectedBehaviour: "The seller is the third viewer of the same field builder, and the only one with no case until now. A seller running an auction needs to know who bid, so the Bidder row is present for them as it is for an admin; the buyer is the single viewer it is withheld from.",
-        expectedUiState: "The modal and the page show the same labels in the same order. A Bidder row is present and names the bidder. If it is absent, the seller cannot tell who is bidding on their own auction — and if the buyer view gained one, that is the leak the case above tests.",
-        expectedData: { bidderRowShown: true },
-        endResult: "Read-only; nothing persists. Every bid on this auction belongs to store-beyblade-arena, which is tyson's store, so the seller is entitled to see it.",
-    },
-};

package/dist/features/tester/seed-data/authored/page-wiring__drawer-pages.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/page-wiring__drawer-pages.js

@@ -1,92 +0,0 @@
-/*
- * WHY: Authored six-part procedures for the page-wiring/drawer-pages page.
- * WHAT: 3 case(s), keyed by full checklist id.
- *
- * 🛑 "EDITOR AS A PAGE" IS TWO DIFFERENT SHAPES, and the cases assumed one
- * (corrected 2026-09-29). Checked route by route:
- *
- *   drawer-as-page   /admin/team/new, /admin/navigation/new — the editor hard-
- *                    renders <SideDrawer> with no headless mode, so the page
- *                    mounts it permanently open and wires onClose to navigate
- *                    back to the list. Here "close the panel" is literal.
- *   full page        /admin/tester-checklist/new (StackedViewShell +
- *                    SectionForm), /admin/carousels/new (a Section/Container
- *                    with a back Link), /store/stickers/new (a product shell).
- *                    There is no panel and nothing to close; the way back is a
- *                    Cancel button or a link.
- *
- * Both are correct. What matters for every case here is the same two things —
- * the form is usable on arrival, and there is a way back to its list — so the
- * steps now ask for that rather than for a drawer that two thirds of these
- * routes do not have. A tester hunting a panel on /store/stickers/new would
- * otherwise report a defect that is really a second, equally valid shape.
- *
- * All 19 routes named in step prose below were verified to exist on
- * 2026-09-29. Worth repeating rather than trusting: the hrefs audit validates
- * href and startPage only, so a route named inside a step is checked by nobody.
- *
- * Written by hand, case by case, against the label each one states. There is no
- * generator: the authoring scripts were deleted once it was clear they were
- * scaffolding around work that is simply writing.
- *
- * @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-page-wiring-drawer-pages-page-drawer-opens-already-open": {
-        roles: ["admin"],
-        startPage: "/admin/team/new",
-        steps: [
-            "Sign in as admin@letitrip.in / TempPass123!.",
-            "Open /admin/team/new directly in the address bar.",
-            "Read what is on screen without clicking anything — this one is a drawer mounted permanently open.",
-            "Close the panel and read the address bar.",
-            "Open /admin/navigation/new directly, read what is on screen, close it, and read the address bar. This is the same drawer-as-page shape.",
-            "Open /admin/tester-checklist/new directly and read what is on screen. This one is a FULL PAGE, not a drawer, so look for a Cancel or back control rather than a panel to close.",
-            "Use that control and read the address bar.",
-        ],
-        inputs: {
-            drawerAsPage: "/admin/team/new, /admin/navigation/new",
-            fullPage: "/admin/tester-checklist/new",
-        },
-        expectedBehaviour: "An editor reached by URL is usable the moment it loads, and offers a way back to the list it belongs to — so the page is a real destination rather than a dead end. Whether that is a drawer mounted open or an ordinary page is an implementation choice and both are correct; what fails is arriving at a blank page, or having no way back.",
-        expectedUiState: "All three URLs render their form immediately, with no blank page and nothing to click first. Leaving each one lands on /admin/team, /admin/navigation and /admin/tester-checklist respectively, not on a 404 and not on the dashboard. 🛑 Only the first two have a panel to close; the third is a full page and its absence of a drawer is not a finding.",
-        endResult: "Nothing is created — close each panel rather than saving. A blank page behind a closed drawer is the failure this catches.",
-    },
-    "checklist-page-wiring-drawer-pages-page-drawer-deep-link-survives-reload": {
-        roles: ["admin"],
-        startPage: "/admin/team",
-        steps: [
-            "Sign in as admin@letitrip.in / TempPass123!.",
-            "Open /admin/team and open the editor for employee-blog@letitrip.in.",
-            "Copy the URL from the address bar.",
-            "Reload the page.",
-            "Read whether the panel is open and which record it holds.",
-            "Open the copied URL in a new tab and read the same two things.",
-        ],
-        inputs: { record: "employee-blog@letitrip.in" },
-        expectedBehaviour: "The record's identity is in the URL, so a reload and a fresh tab both restore the same open editor. This is the entire reason these pages exist alongside the drawers — a drawer alone cannot be bookmarked, shared with a colleague, or reopened after a crash.",
-        expectedUiState: "After the reload the panel is still open on employee-blog@letitrip.in with its fields populated. The new tab shows the same. A panel that closes on reload, or reopens empty, both fail.",
-        endResult: "Read-only; close without saving. Nothing persists.",
-    },
-    "checklist-page-wiring-drawer-pages-every-new-editor-route-opens": {
-        roles: ["admin", "seller"],
-        startPage: "/admin/categories/new",
-        steps: [
-            "Sign in as admin@letitrip.in / TempPass123!.",
-            "Open each of these by URL in turn: /admin/categories/new, /admin/brands/new, /admin/bundles/new, /admin/faqs/new, /admin/ads/new, /admin/shipments/new, /admin/addresses/new, /admin/grouped-listings/new, /admin/sublisting-categories/new, /admin/carousel/new, /admin/carousels/new.",
-            "On each, note whether the form is usable on arrival or the page is blank.",
-            "Leave each one — a drawer close, a Cancel button or a back link, whichever it offers — and note where the browser lands.",
-            "Sign in as tyson@beybladearena.in / TempPass123! and repeat for /store/addresses/new, /store/sublisting-categories/new, /store/stickers/new, /store/pre-orders/new and /store/listing-templates/new.",
-            "Record every route that arrives blank and every cancel that lands nowhere.",
-        ],
-        expectedBehaviour: "Every editor-as-a-page route arrives with its form usable and offers a way back to its own list. These sixteen are distinct from the three named in the first case on this page, and none of them is named anywhere else in the catalogue, so a blank one is a working URL with nothing on it and no error to report.",
-        expectedUiState: "All sixteen arrive with a usable form and get back to the matching list. Each blank arrival is a finding, and so is each exit that lands on a dead route, both named by route. 🛑 These are NOT all drawers: /admin/carousels/new is a plain page with a back link and /store/stickers/new is a product shell, so record how each one offers its way back rather than expecting a panel.",
-        expectedData: { blankEditorRoutes: 0, routesChecked: 16 },
-        endResult: "Nothing is saved. Every one of these routes was verified to exist on 2026-09-29, so a 404 here means one was deleted since, which is itself the finding.",
-    },
-};

package/dist/features/tester/seed-data/authored/page-wiring__reachability.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/page-wiring__reachability.js

@@ -1,115 +0,0 @@
-/*
- * WHY: Authored six-part procedures for the page-wiring/reachability page.
- * WHAT: 5 case(s), keyed by full checklist id.
- *
- * Written by hand, case by case, against the label each one states. There is no
- * generator: the authoring scripts were deleted once it was clear they were
- * scaffolding around work that is simply writing.
- *
- * Every case here is the same shape: something was fully built and had no way in.
- * A page with no nav entry and a nav entry with no page are the two halves of one
- * defect, and both ship as "half done" without anything failing.
- *
- * 🛑 Two fixtures pinned on 2026-09-29. Exactly ONE named carousel is seeded
- * — carousel-hero-default, 'Homepage Hero', status active — so 'the first
- * carousel' is that one, and its status toggles between exactly two values,
- * active and draft. The 'Edit carousel' control lives on the DETAIL page
- * /admin/carousels/{id}, not on the list, which only links to each row.
- *
- * Verified before asserting: /admin/events/new really does derive its type list
- * from ALL_EVENT_TYPES now, so Lottery is in the picker and the first case
- * should pass. Its own file still carries the note about the local copy that
- * omitted it, which is why lottery events could once only come from the seeder.
- *
- * @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-page-wiring-reachability-lottery-can-be-created-without-seeding": {
-        roles: ["admin", "buyer"],
-        startPage: "/admin/events/new",
-        steps: [
-            "Sign in as admin@letitrip.in / TempPass123!.",
-            "Open /admin/events/new and read every option in the event type picker.",
-            "Select Lottery as the type.",
-            "Type 'QA Event lottery-created-without-seeding' as the title, set a start date of today and an end date one week out, and save.",
-            "Open /admin/lotteries and open the new event's slot editor.",
-            "Add three slots numbered 1, 2 and 3, give each a name, and save.",
-            "Sign out and sign in as rehan.sheikh@gmail.com / TempPass123!.",
-            "Open /lottery/{the new event id} and pull slot 1.",
-        ],
-        inputs: { eventTitle: "QA Event lottery-created-without-seeding", slotCount: 3, pulledSlot: 1 },
-        expectedBehaviour: "A lottery can be built entirely through the UI. The event and its slots are edited in different places on purpose — the slot editor has no fields for title, dates, status or media, so a lottery created there alone would have no dates, and the draw window is measured from them.",
-        expectedUiState: "Lottery appears in the event type picker, which is where it was missing entirely. The event saves, its slot editor accepts three slots, and the public page renders them as a pullable grid. Slot 1 becomes booked after the pull.",
-        expectedData: { lotteryInTypePicker: true },
-        endResult: "A working lottery exists that no seed script created. Delete the event afterwards. Until this was fixed, lottery events could only come from the seeder.",
-    },
-    "checklist-page-wiring-reachability-carousel-can-be-renamed": {
-        roles: ["admin"],
-        startPage: "/admin/carousels",
-        steps: [
-            "Sign in as admin@letitrip.in / TempPass123!.",
-            "Open /admin/carousels and read the list — one carousel is seeded, 'Homepage Hero', with status active.",
-            "Open /admin/carousels/carousel-hero-default and find its 'Edit carousel' control. It is on this detail page, not on the list.",
-            "Change the name to 'QA Carousel can-be-renamed' and the status from active to draft.",
-            "Save.",
-            "RELOAD /admin/carousels and read the name and status in the row.",
-            "Set the name back to 'Homepage Hero' and the status back to active, then reload once more to confirm.",
-        ],
-        inputs: {
-            carousel: "carousel-hero-default",
-            originalName: "Homepage Hero",
-            newName: "QA Carousel can-be-renamed",
-            statusBefore: "active",
-            statusAfter: "draft",
-        },
-        expectedBehaviour: "A named carousel can be edited after creation. The group editor was create-only, so a carousel's name was fixed for its entire life with no path to change it — and /admin/carousels rendered the flat slide editor rather than a list of named carousels at all.",
-        expectedUiState: "The list page shows named carousels, not a bare slide editor. 'Edit carousel' exists on the detail page, opens with the current values, and after saving and reloading the list row reads 'QA Carousel can-be-renamed' with status draft. Status has exactly two values here — active and draft — so a picker offering more is itself worth noting.",
-        expectedData: { editControlPresent: true },
-        endResult: "The name reads 'Homepage Hero' and the status is active again. Other cases read this carousel by that seeded name, and it is the only one there is.",
-    },
-    "checklist-page-wiring-reachability-grouped-listing-members-editable-from-its-own-page": {
-        roles: ["seller"],
-        startPage: "/store/grouped-listings/new",
-        steps: [
-            "Sign in as tyson@beybladearena.in / TempPass123!.",
-            "Open /store/grouped-listings/new.",
-            "Read the form and look for a product picker, a minimum-active-members field and a cover-image field.",
-            "Type 'QA Group members-editable' as the title.",
-            "Add product-beyblade-burst-valkyrie and product-beyblade-x-wizard-arrow as members.",
-            "Set minimum active members to 2 and attach public/test-media/sample-image.png as the cover image.",
-            "Save.",
-            "RELOAD the group's page and read its members, minimum and cover image.",
-        ],
-        inputs: {
-            title: "QA Group members-editable",
-            member1: "product-beyblade-burst-valkyrie",
-            member2: "product-beyblade-x-wizard-arrow",
-            minActiveMembers: 2,
-            coverImage: "/test-media/sample-image.png",
-        },
-        expectedBehaviour: "Members are chosen while the group is being created, in the same form. productIds was hardcoded to an empty array, so a group could only ever be created empty and populated from somewhere else — and neither the minimum-active-members nor the cover-image field had an input anywhere in the app.",
-        expectedUiState: "All three controls are present on the create form. After saving and reloading, the group holds both products, a minimum of 2, and the uploaded cover image. A group that saves with zero members is the failure.",
-        expectedData: { memberCount: 2, minActiveMembers: 2 },
-        endResult: "Delete the group afterwards so it does not accumulate across runs.",
-    },
-    "checklist-page-wiring-reachability-public-nav-and-footer-resolve": {
-        roles: ["guest"],
-        startPage: "/",
-        steps: [
-            "Signed out, open /.",
-            "Click every link in the public header navigation in turn, reading each destination and going back.",
-            "Open the sidebar support links and click each one, reading each destination.",
-            "Scroll to the footer and click every link in every column, reading each destination.",
-            "Write down any link that lands on a not-found page, an empty shell, or back on the homepage.",
-        ],
-        expectedBehaviour: "Every public-facing link resolves to a real page with content. The nav audit only ever checked the three portal sidebars, so not one of these 62 hrefs was covered by anything — a rename anywhere in the public surface rotted silently.",
-        expectedUiState: "All 62 destinations render real content. None shows a 404, none renders chrome with an empty body, and none silently redirects back to / — a redirect to the homepage looks like a working link and is not one.",
-        expectedData: { brokenLinkCount: 0, linksChecked: 62 },
-        endResult: "Read-only; nothing persists. Record every broken href in the comment, not just the first — one report naming all of them is worth more than a verdict.",
-    },
-};

package/dist/features/tester/seed-data/authored/public-pages__auth-error-pages.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/public-pages__auth-error-pages.js

@@ -1,137 +0,0 @@
-/*
- * WHY: Authored six-part procedures for the public-pages/auth-error-pages 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.
- *
- * @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-public-pages-auth-error-pages-register-page": {
-        roles: ["guest"],
-        startPage: "/auth/register",
-        steps: [
-            "Open /auth/register in a private window with no session.",
-            "Click 'Create account' with every field empty and read where the errors appear.",
-            "Type 'QA Register register-page' as the full name and 'not-an-email' as the email, then click 'Create account'.",
-            "Type qa-register-1@mailnull.com as the email — if that address already has an account from a previous run, increment the number.",
-            "Type TestPass123! in the password field and Different123! in the confirm field, then click 'Create account'.",
-            "Correct the confirm field to TestPass123!, tick the terms checkbox, and click 'Create account'.",
-        ],
-        inputs: {
-            fullName: "QA Register register-page",
-            email: "qa-register-1@mailnull.com",
-            password: "TestPass123!",
-            mismatchedConfirm: "Different123!",
-        },
-        expectedBehaviour: "Each rule reports on the field that broke it — required, email format, password match, terms accepted — before any request is sent, and the account is created only once all four pass.",
-        expectedUiState: "The empty submit marks the individual fields rather than showing one banner. 'not-an-email' is rejected on the email field. The mismatched confirm is rejected on the confirm field, not the password field. The final submit signs the browser in and leaves /auth/register.",
-        endResult: "The account exists and persists. This case creates a real row that teardown does not remove, which is why the address is numbered rather than fixed.",
-    },
-    "checklist-public-pages-auth-error-pages-forgot-reset-password-pages": {
-        roles: ["guest"],
-        startPage: "/auth/forgot-password",
-        steps: [
-            "Open /auth/forgot-password in a private window with no session.",
-            "Click 'Send reset link' with the field empty and read where the error appears.",
-            "Type not-an-email and click 'Send reset link'.",
-            "Type divya.funko@gmail.com and click 'Send reset link'. Read only the CONFIRMATION here — the generic 'if an account exists' message is the whole point of this step and needs no inbox.",
-            "🛑 DO NOT COMPLETE A RESET FOR A SEEDED PERSONA. The harness cannot open divya's inbox — both check-inbox.mjs and the emailEvents recorder key on TESTER_EMAIL_ID — and a reset that half-completes leaves a PRESERVE-tier login changed with nothing to restore it from, breaking every other case that signs in as her. For the link half, register a throwaway account on the harness mailbox using a plus-address and request the reset for THAT.",
-            "Capture a timestamp, request the link for the throwaway address, then run: node tester/scripts/check-inbox.mjs --since <that number> --subject \"reset\". Open the link it reports and read the page it lands on.",
-            "Submit the reset form with two different passwords typed into its two fields.",
-            "Set both fields to QaAuthPages654! and submit.",
-            "No restore is needed: the password changed belongs to a throwaway account, not to a seeded persona. Note in your comment that the account remains — the purge script matches only qa-signup+…@letitrip-qa.test, so a Gmail plus-address is not swept automatically.",
-        ],
-        inputs: {
-            email: "divya.funko@gmail.com",
-            newPassword: "QaAuthPages654!",
-            restoredPassword: "TempPass123!",
-        },
-        expectedBehaviour: "Both pages validate on the field before submitting, and the reset page enforces that the two password entries match. The link's action code is what authorises the change — reaching the inbox is the proof of identity.",
-        expectedUiState: "Empty and malformed emails are marked on the field. A real address produces the generic 'if an account exists' message. The reset page rejects mismatched passwords on the confirm field and accepts matching ones with a confirmation.",
-        endResult: "The password is back at TempPass123! by the final step. This case shares divya.funko@gmail.com with the single-use-link case in signup-login and with nothing else, deliberately — the seeder never resets an existing password, so a changed one outlives every future re-seed.",
-    },
-    "checklist-public-pages-auth-error-pages-verify-email-page": {
-        roles: ["guest"],
-        startPage: "/auth/register",
-        steps: [
-            "Open /auth/register in a private window and create an account on the HARNESS mailbox using a plus-address — no seeded persona can receive testable email, since both instruments key on TESTER_EMAIL_ID — with TestPass123! as the password.",
-            "Capture a timestamp before registering, then find the verification email: node tester/scripts/check-inbox.mjs --since <that number> --subject \"verify\". Read the exit code — 0 arrived, 1 did not (a defect), 2 could not open the mailbox (a harness problem, answer null).",
-            "Open the verification link and read the page it lands on.",
-            "Open /user and look for an unverified-email warning.",
-            "Open the same verification link a second time and read the page.",
-        ],
-        inputs: { password: "TestPass123!" },
-        expectedBehaviour: "The verify-email page consumes the action code, reports the outcome, and offers a way onward. A second visit finds the code spent and says so rather than reporting a second success.",
-        expectedUiState: "The first visit shows a clear confirmation and a link into the site. /user then carries no unverified-email warning. The second visit shows a readable already-used or expired message — not a blank page, not a raw Firebase error code, and not another success.",
-        expectedData: { emailVerified: true },
-        endResult: "The account is verified and stays verified across a sign-out and sign-in.",
-    },
-    "checklist-public-pages-auth-error-pages-oauth-loading-redirect": {
-        roles: ["guest"],
-        startPage: "/auth/login",
-        steps: [
-            "Open /auth/login in a private window with no session.",
-            "Click 'Sign in with Google'.",
-            "Complete the Google popup and watch what the site shows while it finishes.",
-            "Wait up to 30 seconds without clicking anything.",
-            "Read where the browser ends up.",
-        ],
-        expectedBehaviour: "The interstitial waits for the sign-in signal and then moves on by itself. It must not be a terminal state: a page that shows a spinner and never navigates is the same to a user as a crash, and it is the state a dropped realtime signal produces.",
-        expectedUiState: "A loading state appears briefly and then the browser navigates to / or /user with the header showing a signed-in avatar. It does not sit on the loading page indefinitely and it does not land back on /auth/login as though nothing happened.",
-        endResult: "The session is established and survives a reload. Needs a Google account — answer null with that reason if none is available.",
-    },
-    "checklist-public-pages-auth-error-pages-checkout-success-page": {
-        roles: ["buyer"],
-        startPage: "/checkout",
-        steps: [
-            "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, continue through the add-ons step, choose Cash on Delivery and place the order.",
-            "Read the success page for an order number, the item, the address and the total.",
-            "Copy the URL and reload it.",
-            "Open the same URL in a private window with no session.",
-        ],
-        inputs: { productId: "product-beyblade-burst-valkyrie", price: 199, paymentMethod: "Cash on Delivery" },
-        expectedBehaviour: "The success page reads the real order rather than whatever the checkout had in memory, so it survives a reload. It is also order-scoped data, so a signed-out visitor with the URL must not be shown someone's delivery address.",
-        expectedUiState: "The page names an order number, 'Beyblade Burst Valkyrie' at ₹1,899.00 — the product the steps actually add, the delivery address and a total. After the reload it shows the same. In the private window it does not render the order details — it asks for sign-in or reports not-found.",
-        expectedData: { orderTotal: 199 },
-        endResult: "The order exists in /user/orders. A success page that goes blank on reload was rendering from checkout state and not from the order.",
-    },
-    "checklist-public-pages-auth-error-pages-unauthorized-404-pages": {
-        roles: ["guest", "buyer"],
-        startPage: "/",
-        steps: [
-            "Open /this-page-does-not-exist-qa in a private window and read the page.",
-            "Click whatever the page offers as a way back and read where it lands.",
-            "Sign in as rehan.sheikh@gmail.com / TempPass123!.",
-            "Open /admin/site and read the page.",
-            "Open /unauthorized directly and read the page.",
-        ],
-        expectedBehaviour: "Both error pages render as real pages inside the site chrome and offer a way out. A buyer reaching an admin route gets the unauthorized page rather than a crash or a raw framework error, and neither page leaks anything about what it was protecting.",
-        expectedUiState: "The 404 shows a readable message and at least one working link back into the site. The unauthorized page does the same. Neither shows a stack trace, a file path, or an error digest presented as the whole page, and neither renders as an unstyled white page outside the site's own layout.",
-        endResult: "Read-only; nothing persists. A blank white page for either is the failure — it reads as the site being down rather than as one route being unavailable.",
-    },
-    "checklist-public-pages-auth-error-pages-auth-close-terminates-popup": {
-        roles: ["guest"],
-        startPage: "/auth/login",
-        steps: [
-            "Open /auth/login in a private window with no session.",
-            "Start a Google sign-in so the popup opens.",
-            "Complete it and watch the popup window rather than the page behind it.",
-            "Check the popup closes itself rather than sitting on a page.",
-            "Read the original page and check it is now signed in.",
-            "If the popup stays open, read what it shows and whether the opener ever updates.",
-        ],
-        expectedBehaviour: "The popup terminator closes its own window and hands the result back to the opener. A popup that renders and stays open leaves the opener waiting forever — the sign-in genuinely succeeded, and the site never learns it, which is indistinguishable to the visitor from a failed login.",
-        expectedUiState: "The popup closes on its own and the original page becomes signed in without a manual reload. A popup left open is the finding, with whatever it displays.",
-        endResult: "Signed out.",
-    },
-};

package/dist/features/tester/seed-data/authored/public-pages__core-listing-pages.d.ts

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