@mohasinac/appkit 4.57.0 → 4.59.0

package/dist/features/tester/seed-data/authored/buying__image-tile-layout.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/buying__image-tile-layout.js

@@ -1,122 +0,0 @@
-/*
- * WHY: Authored six-part procedures for the buying/image-tile-layout page.
- * WHAT: 7 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 ONE DEFECT SEEN FROM A DIFFERENT SURFACE. A fill-style
- * image resolves its percentages against its parent, so a shrink-to-fit wrapper
- * between a button and its image collapses BOTH to nothing — the tile renders as
- * an empty bordered box while the button still looks and clicks correctly. Twelve
- * surfaces broke at once and none of the call sites had changed.
- *
- * Two things void the fix from outside the primitive, and both are checked here:
- * a bare display utility on the button — which un-layered important styles beat,
- * so the button stops being a flex container — and two or more in-flow children
- * without a column direction, which lays the tile out beside its caption at a
- * fraction of its width.
- *
- * @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-buying-image-tile-layout-bundle-member-thumbnails": {
-        roles: ["guest"],
-        startPage: "/bundles/bundle-original-collectors-set",
-        steps: [
-            "Open /bundles/bundle-original-collectors-set in a private window with no session.",
-            "Look at the member collage and count the tiles.",
-            "Check each tile shows its member's photograph rather than an empty bordered box.",
-            "Compare the tiles' widths against one another.",
-            "Hard-reload with Ctrl+Shift+R and look again.",
-        ],
-        inputs: { bundleId: "bundle-original-collectors-set", memberCount: 3 },
-        expectedBehaviour: "Each member tile renders its image at its intended size. This collage is one of the twelve surfaces that collapsed at once when a wrapper element appeared between a button and its fill-style image — and it is the surface that stayed broken longest, because a bare display utility on the button voided the primitive's own fix from the call site.",
-        expectedUiState: "Three tiles — Dranzer S, Driger V and Storm Pegasus — each showing its member's photo, all the same width. An empty bordered box where a photo should be is the collapse; a tile at a fraction of its neighbour's width is the row-direction failure.",
-        expectedData: { blankTiles: 0 },
-        endResult: "Read-only; nothing persists.",
-    },
-    "checklist-buying-image-tile-layout-bundle-badge-position": {
-        roles: ["guest"],
-        startPage: "/bundles",
-        steps: [
-            "Open /bundles in a private window at 1280 pixels wide.",
-            "Look at each bundle card's discount badge and where it sits on the card.",
-            "Check the badge does not cover the bundle's title or price row.",
-            "Read the badge's text against its background.",
-            "Resize to 390 pixels and look at the badges again.",
-            "Switch to dark mode and read them once more.",
-        ],
-        inputs: { desktopWidth: 1280, mobileWidth: 390 },
-        expectedBehaviour: "The badge overlays the card image, so it takes the solid pairing — a fill with its own on-solid ink — rather than a pale tint. A tint over an arbitrary product photograph is unreadable regardless of theme, and a literal white ink against a theme-inverting background is invisible in exactly one of the two.",
-        expectedUiState: "Every badge is readable at both widths and in both themes, and none covers the title or price row. A visible badge shape with unreadable text inside it is the failure.",
-        endResult: "Read-only; return the site to light mode and restore the width.",
-    },
-    "checklist-buying-image-tile-layout-bundle-tile-opens-lightbox": {
-        roles: ["guest"],
-        startPage: "/bundles/bundle-original-collectors-set",
-        steps: [
-            "Open /bundles/bundle-original-collectors-set in a private window with no session and click a member tile in the collage.",
-            "Read what opens.",
-            "If a lightbox opens, use its next and previous controls and read what changes.",
-            "Close it and check the page is unchanged behind it.",
-            "Click a different tile and confirm it opens that member rather than the first.",
-        ],
-        expectedBehaviour: "A tile is a real control with a destination — either the member's own page or a lightbox on that member. A tile bound to stale state opens the first member whichever one is clicked, which looks like a working lightbox until a second tile is tried.",
-        expectedUiState: "Clicking a tile opens something, and clicking a different tile opens that member. An inert tile, or one that always opens the same member, are both failures.",
-        endResult: "Read-only; close without acting.",
-    },
-    "checklist-buying-image-tile-layout-prizedraw-collage-stacked": {
-        roles: ["guest"],
-        startPage: "/prize-draws/prizedraw-beyblade-mystery-box",
-        steps: [
-            "Open /prize-draws/prizedraw-beyblade-mystery-box in a private window.",
-            "Find the prize collage and count its tiles.",
-            "For each tile, check whether its image sits ABOVE its caption or beside it.",
-            "Compare each tile's width against its neighbours.",
-            "Resize to 390 pixels and check the arrangement again.",
-            "Count the tiles against the number of photographed prizes.",
-        ],
-        expectedBehaviour: "A tile stacks its image above its caption. Where a control holds two or more in-flow children and no column direction, the content wrapper inherits a row direction and lays the image out BESIDE the caption at a fraction of its intended width — the tile still renders, which is why it reads as a design choice rather than a bug.",
-        expectedUiState: "Every tile shows its image above its caption, all at the same width, at both viewport sizes. An image sitting beside its caption and squeezed narrow is the row-direction failure.",
-        endResult: "Read-only; restore the window width afterwards.",
-    },
-    "checklist-buying-image-tile-layout-media-picker-existing-grid": {
-        roles: ["seller"],
-        startPage: "/store/products/new",
-        steps: [
-            "Sign in as tyson@beybladearena.in / TempPass123!.",
-            "Open /store/products/new and open the media picker.",
-            "Switch to its existing-files grid.",
-            "Check every tile shows its image rather than an empty bordered box.",
-            "Check each tile's caption sits below its image rather than beside it.",
-            "Compare the tiles' widths against one another.",
-            "Select one and confirm the right file is chosen.",
-        ],
-        expectedBehaviour: "The existing-files grid is the same clickable-image-tile shape as the bundle collage and the prize-draw collage, inside a form rather than on a public page. It carries both failure modes at once: the tiles can collapse to nothing, and their captions can end up beside the image instead of below it.",
-        expectedUiState: "Every tile shows its image with its caption beneath, all at the same width. Selecting a tile chooses the file it shows rather than another.",
-        expectedData: { blankTiles: 0 },
-        endResult: "Leave the editor without saving.",
-    },
-    "checklist-buying-image-tile-layout-icon-button-spacing": {
-        roles: ["guest", "buyer"],
-        startPage: "/products/product-beyblade-original-dranzer-s",
-        steps: [
-            "Sign in as rehan.sheikh@gmail.com / TempPass123!.",
-            "Open /products/product-beyblade-original-dranzer-s.",
-            "Find every button carrying both an icon and a label and check there is a visible gap between them.",
-            "Compare each glyph's size against its own button's height.",
-            "Find an icon-only control and check it is a true square rather than an ellipse.",
-            "Check no control uses a text character in place of an icon.",
-        ],
-        expectedBehaviour: "A button's gap and alignment reach its real children rather than stopping at the wrapper, and a glyph's size derives from the button's size rather than being fixed. An icon-only control belongs in the square-boxed primitive: the ordinary button's small size sets a minimum height that beats a caller's height utility, so a round icon button rendered that way comes out an ellipse.",
-        expectedUiState: "Every icon-and-label button shows a gap. Glyphs scale with their buttons rather than all being one size. Icon-only controls are square. No control uses a heart, star or similar text character as its icon — a text character cannot be sized by any utility and renders at the platform font fallback.",
-        endResult: "Read-only; nothing persists.",
-    },
-};

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

@@ -1,279 +0,0 @@
-/*
- * WHY: Authored six-part procedures for the buying/my-orders checklist page.
- * WHAT: 14 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.
- *
- * 🛑 THE MANUAL-PAYMENT FLOW WAS COMPLETELY DEAD FROM THE BUYER'S SIDE and nothing
- * errored. The order adapter mapped the payment STATUS and no other payment field,
- * so the payment page's own gate — is this a manual payment method — was undefined
- * for every order, and every buyer who reached it was told politely that the order
- * did not require a manual payment. Five cases here exist because of that, and
- * each reads a field that adapter has to carry.
- *
- * 🛑 `orderType` CANNOT BE FILTERED WITH AN EQUALITY ON "standard". Orders written
- * before the field existed carry no value, and a Firestore equality excludes every
- * document missing the field — so the Normal tab must filter in memory or it hides
- * every legacy order.
- *
- * @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-buying-my-orders-orders-item-summary": {
-        roles: ["buyer"],
-        startPage: "/user/orders",
-        steps: [
-            "Sign in as rehan.sheikh@gmail.com / TempPass123!.",
-            "Open /user/orders and read every row's primary label.",
-            "Check each names the ITEM rather than only an order identifier.",
-            "Find a multi-item order and read how its row summarises the contents.",
-            "Check each row shows a thumbnail of the item.",
-            "Read where the order id appears and how prominent it is.",
-        ],
-        expectedBehaviour: "Every order carries its item title and image denormalised onto the document so a list row needs no extra fetch. A row reading 'Order {id}' threw that away — the data was present the whole time, and the buyer is left opening each order to find out what it was.",
-        expectedUiState: "Rows name the product with a thumbnail, a multi-item order shows a '+N more' style suffix, and the order id is present but de-emphasised rather than being the whole label.",
-        endResult: "Read-only; nothing persists.",
-    },
-    "checklist-buying-my-orders-orders-view-details-button": {
-        roles: ["buyer"],
-        startPage: "/user/orders",
-        steps: [
-            "Sign in as rehan.sheikh@gmail.com / TempPass123!.",
-            "Open /user/orders and click a row's body away from any control.",
-            "Read what opens.",
-            "Go back and use the explicit view-details control on the same row.",
-            "Check both reach the same order.",
-            "Read whether the row also offers actions, and whether at least one is a view rather than a mutation.",
-        ],
-        expectedBehaviour: "The row and its view control reach the same order. A row offering only mutations lets a buyer act on an order they were never able to read, which is the dead-end shape this whole listing family exists to close.",
-        expectedUiState: "Both routes open the same order detail. A view affordance exists alongside any actions. An inert row is the failure.",
-        endResult: "Read-only; close without acting.",
-    },
-    "checklist-buying-my-orders-orders-type-tabs-actually-filter": {
-        roles: ["buyer"],
-        startPage: "/user/orders",
-        steps: [
-            "Sign in as rehan.sheikh@gmail.com / TempPass123!.",
-            "Open /user/orders and read every tab offered.",
-            "Note the unfiltered order count on the All tab.",
-            "Open the Auction wins tab and read the count and the rows.",
-            "Open the Offer wins tab and read the count and the rows.",
-            "Open the Normal tab and read the count and the rows.",
-            "Check the three tabs' counts sum to the All count.",
-        ],
-        expectedBehaviour: "Each tab filters by the lane that produced the order — recorded on the order at creation — and together they partition the whole set. A tab returning the full list is not filtering; one returning nothing while orders of that kind exist is filtering on the wrong value.",
-        expectedUiState: "Auction wins holds only auction-won orders, Offer wins only offer-accepted ones, and the three counts sum to the All count. A sum that does not reconcile means orders are falling through every tab.",
-        expectedData: { tabsPartitionAll: true },
-        endResult: "Read-only; nothing persists beyond the URL.",
-    },
-    "checklist-buying-my-orders-orders-normal-tab-includes-legacy": {
-        roles: ["buyer"],
-        startPage: "/user/orders",
-        steps: [
-            "Sign in as rehan.sheikh@gmail.com / TempPass123!.",
-            "Open /user/orders on the All tab and note the total count.",
-            "Note the count on the Auction wins and Offer wins tabs.",
-            "Subtract those two from the total to get the expected Normal count.",
-            "Open the Normal tab and read its actual count.",
-            "Compare the two numbers.",
-            "Look for the OLDEST order in the account and check it appears on the Normal tab.",
-        ],
-        expectedBehaviour: "The Normal tab must filter IN MEMORY rather than with an equality on the standard lane value. Orders written before that field existed carry no value at all, and a Firestore equality excludes every document missing the field — so an equality-filtered Normal tab silently hides every legacy order while looking like it works.",
-        expectedUiState: "The Normal count equals the total minus the two lane tabs, and the account's oldest order is present. A Normal count lower than that arithmetic is the legacy-exclusion failure, and the missing orders are the oldest ones.",
-        expectedData: { normalTabIncludesLegacy: true },
-        endResult: "Read-only. The arithmetic is the assertion — a Normal tab holding plausible rows proves nothing without it.",
-    },
-    "checklist-buying-my-orders-dashboard-recent-orders-linked": {
-        roles: ["buyer"],
-        startPage: "/user",
-        steps: [
-            "Sign in as rehan.sheikh@gmail.com / TempPass123!.",
-            "Open /user and find the recent-orders area on the dashboard.",
-            "Read each entry and check it names the item rather than only an identifier.",
-            "Click one entry and read where it lands.",
-            "Go back and click the heading or see-all control.",
-            "Check it lands on /user/orders rather than nowhere.",
-        ],
-        expectedBehaviour: "Dashboard entries link to their orders and the section links to the full list. A summary section whose rows are inert is a dead end on the page a buyer lands on first.",
-        expectedUiState: "Each entry names its item and opens that order. The see-all control reaches /user/orders. An entry that does nothing on click is the failure.",
-        endResult: "Read-only; nothing persists.",
-    },
-    "checklist-buying-my-orders-order-item-thumbnails-render": {
-        roles: ["buyer"],
-        startPage: "/user/orders",
-        steps: [
-            "Sign in as rehan.sheikh@gmail.com / TempPass123!.",
-            "Open /user/orders and look at every row's thumbnail.",
-            "Check each shows a photograph rather than an empty box or a placeholder icon.",
-            "Hard-reload with Ctrl+Shift+R and look again.",
-            "Open an order's detail and look at each item's thumbnail there.",
-            "Compare a thumbnail against that product's own page image.",
-        ],
-        expectedBehaviour: "Order items carry an image snapshot so the row renders without fetching the product. That field was absent from the order item type for a long time, so real orders carried no per-item image at all — which renders as a placeholder rather than as an error.",
-        expectedUiState: "Every row and every order-detail item shows its own photograph on both loads, and it matches the product. An empty box or a uniform placeholder across all rows is the missing-field failure.",
-        expectedData: { placeholderThumbnails: 0 },
-        endResult: "Read-only; nothing persists.",
-    },
-    "checklist-buying-my-orders-my-orders-search-filter-sort": {
-        roles: ["buyer"],
-        startPage: "/user/orders",
-        steps: [
-            "Sign in as rehan.sheikh@gmail.com / TempPass123!.",
-            "Open /user/orders and note the unfiltered count.",
-            "Read the scope tabs offered and select each, reading the counts.",
-            "Read every status filter and select each, noting any that returns nothing.",
-            "Search for a word from a visible order's item title and read the results.",
-            "Search zzzznope and read the count.",
-            "Change the sort and check the row order changes.",
-        ],
-        inputs: { nonsenseQuery: "zzzznope" },
-        expectedBehaviour: "Search, filters and sort all narrow the list. The scope tabs read Active / Closed / All, and a return-requested order belongs to ACTIVE — it is an action item, not a finished order. The nonsense query is the control that proves the search filters rather than decorating.",
-        expectedUiState: "Scope tabs and status filters each change the rows. The real search term narrows; 'zzzznope' returns zero rather than the full list. The sort visibly reorders. A return-requested order appears under Active.",
-        expectedData: { nonsenseResultCount: 0 },
-        endResult: "Read-only; nothing persists beyond the URL.",
-    },
-    "checklist-buying-my-orders-order-tracking-timeline": {
-        roles: ["buyer"],
-        startPage: "/user/orders",
-        steps: [
-            "Sign in as rehan.sheikh@gmail.com / TempPass123!.",
-            "Open /user/orders and open a SHIPPED order.",
-            "Open its tracking view.",
-            "Read every step in the timeline and the date against each.",
-            "Check steps the order has not reached are shown as upcoming rather than complete.",
-            "Check any step with no recorded date shows an em-dash rather than a date.",
-            "Read the carrier and tracking number and compare them against the order detail.",
-        ],
-        expectedBehaviour: "The timeline is built from the order's own per-status dates. A status with no recorded date renders an em-dash — never the current time and never a proxy field such as the record's last-updated value, which means 'last write of any kind' rather than 'when this happened'. A fabricated date cannot be told from a real one afterwards.",
-        expectedUiState: "Reached steps show real dates, unreached steps show as upcoming, and any missing date is an em-dash. The carrier and tracking number match the order detail. Every step carrying a plausible date on an order that has only just shipped is the fabrication failure.",
-        endResult: "Read-only; nothing persists.",
-    },
-    "checklist-buying-my-orders-manual-payment-panel-on-order-detail": {
-        roles: ["buyer"],
-        startPage: "/user/orders",
-        steps: [
-            "Sign in as rehan.sheikh@gmail.com / TempPass123!.",
-            "Open /user/orders and open an order paid by cash or UPI awaiting payment.",
-            "Read the order detail for a manual-payment panel.",
-            "Check it names the payment method, the amount and the deadline.",
-            "Find the control that opens the payment page.",
-            "Click it and read where it lands.",
-        ],
-        expectedBehaviour: "The panel renders because the order carries its payment method, deadline and review outcome — not just its payment status. The adapter mapped only the status for a long time, so every buyer-facing gate on those fields saw undefined and the whole manual-payment flow was unreachable.",
-        expectedUiState: "The panel is present on a manual-payment order, naming the method, amount and deadline, with a working control into the payment page. A missing panel on a cash or UPI order is the adapter failure.",
-        endResult: "Read-only; upload nothing yet.",
-    },
-    "checklist-buying-my-orders-manual-payment-page-renders-upi-and-countdown": {
-        roles: ["buyer"],
-        startPage: "/user/orders",
-        steps: [
-            "Sign in as rehan.sheikh@gmail.com / TempPass123!.",
-            "Open a manual-payment order and follow the control to its payment page.",
-            "Read whether the page renders the upload form or tells you no manual payment is required.",
-            "Read the UPI identifier displayed and the amount.",
-            "Read the countdown and note the time remaining.",
-            "Wait ten seconds and read the countdown again.",
-            "Reload the page and check the countdown continues rather than resetting.",
-        ],
-        inputs: { paymentWindowMinutes: 15 },
-        expectedBehaviour: "The page gates on the order's payment method, so it must render the form rather than the polite refusal that every buyer saw while that field was undefined. The countdown runs against the stored deadline, so a reload continues it rather than restarting the window.",
-        expectedUiState: "The upload form, the UPI identifier and the amount all render. The countdown decreases over ten seconds and continues from where it was after a reload. A message saying this order does not require manual payment is the exact failure this case exists for.",
-        endResult: "Read-only. A reset countdown after reload would mean the window restarts on every visit.",
-    },
-    "checklist-buying-my-orders-manual-payment-awaiting-review-state": {
-        roles: ["buyer"],
-        startPage: "/user/orders",
-        steps: [
-            "Sign in as rehan.sheikh@gmail.com / TempPass123!.",
-            "Open a manual-payment order's payment page and upload public/test-media/sample-image.png as proof.",
-            "Type QATXN552310 as the payment reference and submit.",
-            "Read what the page shows immediately afterwards.",
-            "RELOAD and read the page again.",
-            "Open the order detail and read its payment state.",
-            "Check the upload form is no longer inviting another submission.",
-        ],
-        inputs: { proof: "public/test-media/sample-image.png", reference: "QATXN552310" },
-        expectedBehaviour: "Once a proof is submitted the order reads as awaiting verification on both the payment page and the order detail — the state is derived from whether a proof exists and whether a decision has been made, so both surfaces compute the same answer.",
-        expectedUiState: "After submitting, the page reports the proof received and stops offering a fresh upload. The order detail reads as awaiting verification. Both agree after the reload.",
-        endResult: "The order is awaiting verification and is the fixture the admin verify case reads.",
-    },
-    "checklist-buying-my-orders-manual-payment-reupload-note-visible-to-buyer": {
-        roles: ["buyer", "admin"],
-        startPage: "/user/orders",
-        steps: [
-            "Sign in as admin@letitrip.in / TempPass123! and request a proof re-upload on that order, with the note 'QA Note reupload — the reference is unreadable.'.",
-            "Sign out and sign in as rehan.sheikh@gmail.com / TempPass123!.",
-            "Open /user/orders and read that order's row and its detail.",
-            "Read whether the admin's note is shown to the buyer.",
-            "Open the payment page and read whether the upload form is active again and what the deadline shows.",
-            "Upload a fresh proof and submit.",
-            "Read the order's state afterwards.",
-        ],
-        inputs: { note: "QA Note reupload — the reference is unreadable." },
-        expectedBehaviour: "The admin's note reaches the buyer — a re-upload request with no visible reason leaves them resubmitting the same thing. The corrected upload must CLEAR the requested state, or the order is invisible to both the auto-approve sweep and the admin queue and stalls indefinitely.",
-        expectedUiState: "The note is readable on the buyer's order. The payment page is active with an extended deadline. After the fresh upload the order reads as awaiting verification rather than staying in the requested state.",
-        expectedData: { stateAfterReupload: "awaiting verification" },
-        endResult: "The order is back in the review queue with the buyer's second proof.",
-    },
-    "checklist-buying-my-orders-manual-payment-rejected-state": {
-        roles: ["buyer"],
-        startPage: "/user/orders",
-        steps: [
-            "Sign in as rehan.sheikh@gmail.com / TempPass123!.",
-            "Open /user/orders and find an order whose payment was rejected.",
-            "Read its row and its detail.",
-            "Check the rejection is stated plainly rather than the order simply reading as cancelled.",
-            "Read whether the reason given is visible to the buyer.",
-            "Check no upload form is offered any more.",
-            "Read whether the items are back in stock on their product pages.",
-        ],
-        expectedBehaviour: "A rejected payment cancels the order and restores its stock, and the buyer is told which happened. It also triggers a temporary ban cascade against the account — so the buyer seeing only 'cancelled' with no explanation is left unable to connect that to the restriction they then hit.",
-        expectedUiState: "The order states that the payment was rejected, with whatever reason was recorded, and offers no further upload. The items read as in stock again on their product pages.",
-        endResult: "Read-only. If no rejected order exists, answer null rather than creating one — rejecting as fraud bans a real account for seven days.",
-    },
-    "checklist-buying-my-orders-order-lifecycle-emails-arrive": {
-        roles: ["buyer"],
-        startPage: "/user/orders",
-        steps: [
-            /*
-             * 🛑 THE ACCOUNT MUST BE THE HARNESS MAILBOX, AND NO SEEDED PERSONA IS.
-             *
-             * This step used to read "an account whose inbox you can open", which is
-             * not a literal value and quietly hid a real constraint. Two mechanisms
-             * can settle an email case, and BOTH key on TESTER_EMAIL_ID:
-             *
-             *   - check-inbox.mjs reads that mailbox over IMAP
-             *   - the emailEvents recorder writes a row ONLY when the recipient
-             *     equals TESTER_EMAIL_ID (or EMAIL_RECORDER_ALL is set)
-             *
-             * Every seeded persona uses a real-looking address the harness does not
-             * own, so an order placed as rehan produces nothing either instrument can
-             * see. Gmail plus-addressing is the way in: a fresh signup at
-             * <harness-mailbox>+run3@gmail.com is delivered to the same inbox.
-             *
-             * Capture the timestamp BEFORE placing the order. The mailbox is shared
-             * across every case in every run, so "newest matching message" will
-             * happily return one an earlier case left behind — which reads as a pass
-             * for an email this action never sent.
-             */
-            "Register a new account at /auth/register using the harness mailbox with a run-stamped plus-address (the value of TESTER_EMAIL_ID in tester/.env, e.g. name+run3@gmail.com), and confirm order emails are enabled in its notification settings.",
-            "Run `node -e \"console.log(Date.now())\"` and keep that number.",
-            "Place an order as that account.",
-            "Run `node tester/scripts/check-inbox.mjs --since <that number> --subject \"order\"` and read the exit code: 0 the mail arrived, 1 it did not, 2 the mailbox could not be opened.",
-            "Read the message's From name, its subject and its body.",
-            "Have the seller mark the order shipped, capture a fresh timestamp, and run check-inbox.mjs again with --subject \"shipped\".",
-            "Click a link inside each email and read where it lands.",
-            "Compare each email's figures against the order itself.",
-        ],
-        expectedBehaviour: "Each lifecycle transition sends its own templated email. The dispatcher fills in the template and the destination from the notification's type and related record rather than requiring each caller to supply them — which is why almost no caller used to, and every type shipped the same bare one-line body.",
-        expectedUiState: "Confirmation and shipped emails both arrive within a few minutes, from a sender whose display name reads 'LetItRip' exactly. Each has a real templated body rather than a single unstyled sentence, its figures match the order, and its links open the live site.",
-        endResult: "Both emails exist. An in-app notification with no email, while email is enabled for that type, is the failure this case separates from a delivery problem.",
-    },
-};

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

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