@mohasinac/appkit 4.34.1 → 4.35.1

package/dist/features/tester/seed-data/authored/buying__user-dashboard-extras.js

@@ -0,0 +1,283 @@
+/*
+ * WHY: Authored six-part procedures for the buying/user-dashboard-extras page.
+ * WHAT: 15 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.
+ *
+ * 🛑 SIX CASES HERE ARE ABOUT THE ORDER TIMELINE, and they turn on two rules that
+ * are easy to get backwards.
+ *
+ * A step with no recorded date renders an em-dash. Not the current time, and not
+ * a proxy field — the record's last-updated value means "last write of any kind"
+ * and an expiry date is a deadline, not an event. A fabricated timestamp cannot be
+ * told from a real one afterwards, which makes it worse than a missing one.
+ *
+ * And money churn is deliberately NOT in the timeline. Only the final coupon and
+ * add-on state is kept, on the order itself. A coupon that lapsed before the order
+ * existed is not that order's history, and pricing noise would exhaust the
+ * fifty-entry cap within days and bury the handful of transitions anyone reads.
+ *
+ * @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-user-dashboard-extras-addresses-crud": {
+        roles: ["buyer"],
+        startPage: "/user/addresses",
+        steps: [
+            "Sign in as rehan.sheikh@gmail.com / TempPass123!.",
+            "Open /user/addresses and read the existing addresses.",
+            "Create one: 'QA Address dashboard-extras', '15 Test Lane', Indore, Madhya Pradesh, 452010, landmark 'Opposite the arena'.",
+            "Save, RELOAD, and read every field including the landmark.",
+            "Edit ONLY the street to '16 Test Lane', save, RELOAD, and read every field again.",
+            "Set it as the default, save, RELOAD, and check exactly one address is default.",
+            "Delete it and RELOAD to confirm.",
+        ],
+        inputs: {
+            name: "QA Address dashboard-extras",
+            streetBefore: "15 Test Lane",
+            streetAfter: "16 Test Lane",
+            landmark: "Opposite the arena",
+        },
+        expectedBehaviour: "Create, edit, default-set and delete all persist, and an edit to one field leaves the rest alone. Setting a default must unset the previous one — two defaults is a state nothing downstream can resolve. The landmark is the field to watch: a form that cannot name it sends undefined, and undefined overwrites.",
+        expectedUiState: "After each reload the address holds exactly what was typed, landmark included, and after the street edit the landmark is still there. Exactly one address is marked default.",
+        expectedData: { defaultAddressCount: 1 },
+        endResult: "The address is deleted by the final step.",
+    },
+    "checklist-buying-user-dashboard-extras-catalogue-crud": {
+        roles: ["buyer"],
+        startPage: "/user",
+        steps: [
+            "Sign in as rehan.sheikh@gmail.com / TempPass123!.",
+            "Open the personal catalogue surface and read the existing items.",
+            "Create one titled 'QA Catalogue dashboard-extras' with a description and public/test-media/sample-image.png attached.",
+            "Save, RELOAD, and read every field including the photo.",
+            "Set it to public, save, and open /profile/user-yugi-muto in a private window.",
+            "Find it under the Catalogue tab and open its own public page.",
+            "Set it back to private and check it disappears from the public profile.",
+            "Delete the item.",
+        ],
+        inputs: {
+            title: "QA Catalogue dashboard-extras",
+            image: "public/test-media/sample-image.png",
+        },
+        expectedBehaviour: "A personal catalogue item is a private photo record of something the buyer owns, optionally published. It is NOT a listing type — it lives in its own feature with its own id prefix, and its public visibility is a per-item choice rather than a consequence of creating it.",
+        expectedUiState: "After the reload every field holds and the photo renders. Set public, the item appears on the owner's public profile Catalogue tab and has its own page. Set private, it disappears from the public profile.",
+        endResult: "The item is deleted by the final step.",
+    },
+    "checklist-buying-user-dashboard-extras-settings-page": {
+        roles: ["buyer"],
+        startPage: "/user/settings",
+        steps: [
+            "Sign in as rehan.sheikh@gmail.com / TempPass123!.",
+            "Open /user/settings and read every tab in the strip.",
+            "Open each tab and check it renders its fields rather than an empty panel.",
+            "Note one distinctive value from each tab.",
+            "Change one field on one tab and save.",
+            "RELOAD and walk every tab, comparing each noted value.",
+            "Restore the changed field.",
+        ],
+        expectedBehaviour: "Every tab renders, and saving one tab leaves the others untouched. A form that submits its whole object from state populated only by the tabs the user opened blanks the rest — and the save reports success either way, so only the reload shows it.",
+        expectedUiState: "All tabs render fields. After the reload only the edited field differs and every other noted value is unchanged. A tab that opens empty, or a value silently reset, are both findings.",
+        expectedData: { unintendedFieldChanges: 0 },
+        endResult: "The changed field is restored.",
+    },
+    "checklist-buying-user-dashboard-extras-my-prize-draws": {
+        roles: ["buyer"],
+        startPage: "/user",
+        steps: [
+            "Sign in as tester@letitrip.in / TempPass123!.",
+            "Open the buyer's prize-draws surface and read every row.",
+            "Check each names the draw, the number of entries bought and the outcome.",
+            "Find an entry in a REVEALED draw and read the prize it names.",
+            "Find an entry in a draw that has not yet been drawn and read what it shows.",
+            "Open one entry and check it reaches the draw or the order behind it.",
+            "Compare a revealed prize against the same prize on the order page.",
+        ],
+        expectedBehaviour: "The list shows what was entered and what came of it. A pending draw and a revealed one are different states and must read differently — a pending entry shown as though it lost, or a revealed one shown as pending, are both wrong and neither errors.",
+        expectedUiState: "Rows name the draw, the entry count and either the assigned prize or a pending state. The prize matches what the order page shows. Rows open something rather than being inert.",
+        endResult: "Read-only; nothing persists.",
+    },
+    "checklist-buying-user-dashboard-extras-my-digital-codes": {
+        roles: ["buyer"],
+        startPage: "/user",
+        steps: [
+            "Sign in as tester@letitrip.in / TempPass123!.",
+            "Open the buyer's digital-codes surface and read every row.",
+            "Check each names the listing it came from and shows its code or its delivery state.",
+            "Find an auto-claim purchase and read whether its code is present.",
+            "Find a manual-delivery purchase and read what it shows instead.",
+            "Use any copy control and paste the result somewhere to compare it against what is displayed.",
+            "Reload and check the codes are still there.",
+        ],
+        expectedBehaviour: "An auto-claim purchase shows its delivered code immediately; a manual-delivery one shows a pending state until the seller sends it. Any copy control must place exactly the displayed string on the clipboard — a truncated or differently-cased copy produces a redemption failure the buyer cannot explain.",
+        expectedUiState: "Auto-claim rows show a real code that survives a reload. Manual rows show a pending state rather than an empty cell. The copied value matches the displayed one character for character.",
+        endResult: "Read-only; nothing persists.",
+    },
+    "checklist-buying-user-dashboard-extras-my-offers": {
+        roles: ["buyer"],
+        startPage: "/user/offers",
+        steps: [
+            "Sign in as vivaan.kapoor@gmail.com / TempPass123!.",
+            "Open /user/offers and read every row — product, offered amount, listed price, status and round.",
+            "Read every status filter offered and select each, noting any that returns nothing.",
+            "For each empty filter, check the unfiltered list for rows of that status.",
+            "Find an offer that was countered and read how its round is shown.",
+            "Open one offer and read its detail.",
+            "Check at least one row action is a view rather than only a mutation.",
+        ],
+        expectedBehaviour: "The list shows the negotiation state with enough context to act — the offered amount against the listed price is the whole point. A counter creates a NEW offer document per round, linked forwards and backwards and denormalised to the chain's root, so a row can say which round it is without extra reads.",
+        expectedUiState: "Rows show product, amounts, status and round. Every status filter returns its own rows or is empty with none unfiltered either — the real statuses include countered and withdrawn, and a chip reading 'Rejected' against a stored 'Declined' matches nothing forever. A view affordance exists.",
+        endResult: "Read-only; nothing persists beyond the URL.",
+    },
+    "checklist-buying-user-dashboard-extras-order-timeline-shows-real-events": {
+        roles: ["buyer"],
+        startPage: "/user/orders",
+        steps: [
+            "Sign in as tester@letitrip.in / TempPass123!.",
+            "Open /user/orders and open an order that has moved through several statuses.",
+            "Open its timeline and read every step in order.",
+            "Read the date and time against each step.",
+            "Check the 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.",
+            "Compare one step's date against when that transition actually happened.",
+        ],
+        expectedBehaviour: "The timeline is built from the order's own recorded per-status dates. A step with no date renders an em-dash — never the current time, and never a proxy such as the record's last-updated value, which means 'last write of any kind' rather than when the step happened.",
+        expectedUiState: "Reached steps carry real dates, unreached steps read as upcoming, and any missing date is an em-dash. Every step carrying a plausible date on a recently-placed order is the fabrication failure, and it is indistinguishable from correct data afterwards.",
+        endResult: "Read-only; nothing persists.",
+    },
+    "checklist-buying-user-dashboard-extras-order-partial-refund-in-timeline": {
+        roles: ["buyer"],
+        startPage: "/user/orders",
+        steps: [
+            "Sign in as tester@letitrip.in / TempPass123!.",
+            "Open /user/orders and find an order that received a partial refund.",
+            "Open its timeline and look for an entry describing the refund.",
+            "Read whether the entry states the amount refunded.",
+            "Check the entry is not phrased as an array or a count changing.",
+            "Compare the refunded amount against the order's own refund total.",
+        ],
+        expectedBehaviour: "A partial refund changes no tracked status field, so a plain field-diff would leave no trace of it at all — the entry is contributed explicitly. Diffing the refunds collection instead was rejected because it renders as 'an array of one became an array of two', which is true and useless.",
+        expectedUiState: "The timeline holds an entry naming the refund and its amount, in readable language. An entry describing a list growing, or no entry at all for a refund that demonstrably happened, are both failures.",
+        endResult: "Read-only. If no partially-refunded order exists, answer null rather than creating one.",
+    },
+    "checklist-buying-user-dashboard-extras-order-auction-won-vs-bought-out": {
+        roles: ["buyer"],
+        startPage: "/user/orders",
+        steps: [
+            "Sign in as tester@letitrip.in / TempPass123!.",
+            "Open /user/orders and switch to the Auction wins tab.",
+            "Open an order that came from a WON auction and read what it says about how it was won.",
+            "Read whether it shows the winning bid and the number of competing bids.",
+            "Open an order that came from a BUY-NOW purchase on an auction and read the same.",
+            "Compare the two — check they are described differently.",
+            "Check the buy-now order's bid count is not assumed to be zero.",
+        ],
+        expectedBehaviour: "A settled win and a buyout are both auction orders but different provenance, and the order records which. A buyout is a REAL bid: it is placed as a bid, leaves the auction live, and the count it records is the competitive bids it beat — so a buyout order asserting zero bids by definition is wrong.",
+        expectedUiState: "The won order names the winning bid and the competing bid count. The buy-now order is described as a buyout rather than as a win, and its bid count reflects the bids that existed rather than being fixed at zero.",
+        endResult: "Read-only; nothing persists.",
+    },
+    "checklist-buying-user-dashboard-extras-order-offer-shows-what-was-saved": {
+        roles: ["buyer"],
+        startPage: "/user/orders",
+        steps: [
+            "Sign in as vivaan.kapoor@gmail.com / TempPass123!.",
+            "Open /user/orders and switch to the Offer wins tab.",
+            "Open an order that came from an accepted offer.",
+            "Read the price charged and the listing's original price.",
+            "Check the order states what was saved rather than only the amount paid.",
+            "Compare the charged price against the offer's agreed amount.",
+        ],
+        expectedBehaviour: "An offer order records the agreed price and the listed price it was negotiated down from. The charged figure must be the AGREED one — the rule that decides a line's price knows about locked prices, and three hand-written copies of that rule elsewhere omitted that branch, so the gateway captured the list price while the cart showed the agreed one.",
+        expectedUiState: "The order shows the agreed price as charged, the original listed price, and the difference. A charged amount equal to the listing price is the copied-rule failure, and the two figures never appear on the same screen anywhere else.",
+        endResult: "Read-only; nothing persists.",
+    },
+    "checklist-buying-user-dashboard-extras-order-history-no-money-churn": {
+        roles: ["buyer"],
+        startPage: "/user/orders",
+        steps: [
+            "Sign in as tester@letitrip.in / TempPass123!.",
+            "Open an order that had coupons applied and add-ons selected.",
+            "Open its timeline and read every entry.",
+            "Look for entries describing coupons being applied or removed, or add-on fees changing.",
+            "Count the entries in total.",
+            "Read the order's own summary and check the final coupon and add-on state is shown there instead.",
+        ],
+        expectedBehaviour: "Pricing churn is deliberately absent from the timeline. Only the FINAL coupon and add-on state is kept, and it lives on the order itself — a coupon that lapsed before the order existed is not that order's history, and pricing noise would exhaust the fifty-entry cap within days and bury the handful of transitions anyone actually reads.",
+        expectedUiState: "The timeline holds status transitions and refunds, and no entries about coupons being applied or removed. The order's summary shows the final applied discounts and add-ons. A timeline full of pricing entries is the failure.",
+        expectedData: { pricingEntriesInTimeline: 0 },
+        endResult: "Read-only; nothing persists.",
+    },
+    "checklist-buying-user-dashboard-extras-order-history-carries-no-personal-data": {
+        roles: ["buyer"],
+        startPage: "/user/orders",
+        steps: [
+            "Sign in as tester@letitrip.in / TempPass123!.",
+            "Open an order and open its timeline.",
+            "Read every entry for a name, an email address or a phone number.",
+            "Read how the actor of each change is identified.",
+            "Open the browser's View Source and search the page for an email address.",
+            "Check any actor shown is an identifier rather than a person's name.",
+        ],
+        expectedBehaviour: "History entries carry no personal data, and this is enforced where the entry is built rather than by convention. The encryption pass is a flat top-level loop that never descends into arrays — so a name or email nested inside a history entry would be stored in PLAINTEXT and never decrypted on the way out, which is why the primitive scrubs those fields itself.",
+        expectedUiState: "No entry contains a name, email or phone. Actors are identifiers. Neither the rendered timeline nor the page source contains an email address.",
+        expectedData: { piiInTimeline: 0 },
+        endResult: "Read-only. A convention saying 'do not put PII in history' is one forgetful writer away from a plaintext leak, which is why this is checked rather than assumed.",
+    },
+    "checklist-buying-user-dashboard-extras-my-returns": {
+        roles: ["buyer"],
+        startPage: "/user",
+        steps: [
+            "Sign in as tester@letitrip.in / TempPass123!.",
+            "Open the buyer's returns surface and read every row.",
+            "Check each names the item, the order and the reason given.",
+            "Read every status filter offered and select each.",
+            "Open one return and read the full reason and any admin response.",
+            "Check the returned order also appears under the ACTIVE scope on /user/orders.",
+        ],
+        expectedBehaviour: "Returns are a view over orders rather than a separate entity — a return is an order status. That is why a return-requested order sits under Active on the orders list: it is an open item awaiting action, and filing it under Closed removes it from the list the buyer checks.",
+        expectedUiState: "Rows name the item, the order and the reason, and open to the full text. The same order appears under Active on /user/orders. A return-requested order under Closed is the finding.",
+        endResult: "Read-only; nothing persists beyond the URL.",
+    },
+    "checklist-buying-user-dashboard-extras-my-reviews": {
+        roles: ["buyer"],
+        startPage: "/user",
+        steps: [
+            "Sign in as rehan.sheikh@gmail.com / TempPass123!.",
+            "Open the buyer's reviews surface and read every row.",
+            "Check each names the product, the rating and the date.",
+            "Check any review photos render rather than showing placeholder icons.",
+            "Open one and check it can be edited.",
+            "Read whether any seller response is shown alongside.",
+            "Click a row and confirm it reaches the product or the review.",
+        ],
+        expectedBehaviour: "The buyer's own reviews are listed with their photos and any seller response. Review images are plain URL strings — a renderer expecting objects reads undefined off every one and falls back to a placeholder, which makes all the photos vanish at once rather than one being broken.",
+        expectedUiState: "Rows name the product, rating and date, photos render, and any seller response is visible. Rows reach the product or the review. Placeholder icons in place of every photo is the string-versus-object failure.",
+        expectedData: { placeholderPhotos: 0 },
+        endResult: "Read-only; nothing persists.",
+    },
+    "checklist-buying-user-dashboard-extras-user-personal-listings-search-sort": {
+        roles: ["buyer"],
+        startPage: "/user",
+        steps: [
+            "Sign in as rehan.sheikh@gmail.com / TempPass123!.",
+            "Open the personal catalogue surface and note the unfiltered item count.",
+            "Type a word from one item's title into the search box and read the results.",
+            "Clear it, type zzzznope, and read the count.",
+            "Read the sort dropdown's options and its default selection.",
+            "Check the default is one of the offered options.",
+            "Select each other option and check the order changes each time.",
+        ],
+        inputs: { nonsenseQuery: "zzzznope" },
+        expectedBehaviour: "Search narrows and every sort option reorders. The nonsense query is the control that separates a filtering search from a decorative one — a real term returns plausible rows either way. A default sort that is not among the offered options opens the dropdown blank, which this listing family has done before.",
+        expectedUiState: "The real term narrows the list; 'zzzznope' returns zero and an empty state rather than everything. The sort dropdown opens with one of its own options selected, and each option visibly reorders the items.",
+        expectedData: { nonsenseResultCount: 0, inertSortOptions: 0 },
+        endResult: "Read-only; nothing persists beyond the URL.",
+    },
+};

package/dist/features/tester/seed-data/authored/buying__user-dashboard-navigation.d.ts

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

package/dist/features/tester/seed-data/authored/buying__user-dashboard-navigation.js

@@ -0,0 +1,167 @@
+/*
+ * WHY: Authored six-part procedures for the buying/user-dashboard-navigation page.
+ * WHAT: 9 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 /user SUBTREE IS DIFFERENT FROM /admin AND /store. Its layout reads no
+ * session server-side — the guard is a client component — so these routes are
+ * PRERENDERED to a signed-out shell and the session hydrates in the browser. That
+ * shell is the same bytes for every visitor, which is what makes it safe, and it
+ * is also why the signed-out case watches for a flash rather than expecting an
+ * immediate server redirect.
+ *
+ * @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-user-dashboard-navigation-sidebar-all-links-work": {
+        roles: ["buyer"],
+        startPage: "/user",
+        steps: [
+            "Sign in as rehan.sheikh@gmail.com / TempPass123!.",
+            "Open /user and expand every group in the sidebar.",
+            "Click each link in turn, reading where it lands and going back each time.",
+            "Write down any link that 404s, renders an empty shell, or lands somewhere unrelated.",
+            "Count the links against the pages that exist under /user.",
+            "Read whether a Testing group is present for this non-tester account.",
+        ],
+        expectedBehaviour: "Every sidebar link opens a real page with content. The inverse — a built page with no sidebar entry — is the same defect from the other side, and it is not mechanically blocked: around seventeen pages across the portals were once reachable only by typing their exact URL. The Testing group is injected at runtime for tester accounts and must be absent entirely for others rather than rendering as an empty heading.",
+        expectedUiState: "Every link resolves to a page with content, not a 404 and not chrome with an empty body. No Testing group appears for this account. Note any page you know exists that has no link — that half has to be spotted by eye.",
+        expectedData: { brokenLinks: 0 },
+        endResult: "Read-only; nothing persists.",
+    },
+    "checklist-buying-user-dashboard-navigation-sidebar-active-highlight": {
+        roles: ["buyer"],
+        startPage: "/user",
+        steps: [
+            "Sign in as rehan.sheikh@gmail.com / TempPass123!.",
+            "Open /user and note which sidebar entry is highlighted.",
+            "Navigate to /user/orders and read which entry is highlighted.",
+            "Open a specific order's detail and read the highlight again.",
+            "Navigate to /user/addresses and read it again.",
+            "Press the browser back button and read the highlight.",
+        ],
+        expectedBehaviour: "The highlight is derived from the current path, so it follows nested routes where the sidebar has no entry of its own — an order detail still highlights Orders — and it follows a back navigation, which a highlight set from the click cannot.",
+        expectedUiState: "Exactly one entry is highlighted at a time and it matches the current section, including on the order detail. After the back navigation it matches wherever the browser landed.",
+        endResult: "Read-only; nothing persists.",
+    },
+    "checklist-buying-user-dashboard-navigation-sidebar-mobile-collapse": {
+        roles: ["buyer"],
+        startPage: "/user",
+        steps: [
+            "Sign in as rehan.sheikh@gmail.com / TempPass123!.",
+            "Resize the browser window to 390 pixels wide and open /user.",
+            "Read how the sidebar is presented.",
+            "Open it, read its entries, and navigate somewhere.",
+            "Check whether it closed on navigation.",
+            "Count the fixed bars at the bottom of the screen.",
+            "Try to scroll the page sideways.",
+        ],
+        inputs: { mobileWidth: 390 },
+        expectedBehaviour: "On a phone the sidebar collapses behind a control and closes after navigating. The dashboard renders its own bottom tab bar and the public one is suppressed on these routes, so exactly one is mounted — two would be two bars on the same pixels with a height nobody owns, and everything above them would be positioned against the wrong one.",
+        expectedUiState: "The sidebar is collapsed by default, opens on demand and closes after navigation. Exactly one bottom bar is present, carrying dashboard destinations rather than the public ones. The page does not scroll sideways.",
+        expectedData: { bottomNavCount: 1 },
+        endResult: "Read-only; restore the window width afterwards.",
+    },
+    "checklist-buying-user-dashboard-navigation-deep-link-direct-load": {
+        roles: ["buyer"],
+        startPage: "/user/orders",
+        steps: [
+            "Sign in as rehan.sheikh@gmail.com / TempPass123!.",
+            "Open /user/orders, apply a filter and a sort, and copy the URL.",
+            "Open a new tab and paste that URL.",
+            "Read whether the same filter and sort are applied on first paint.",
+            "Open a specific order's detail, copy that URL, and open it in a new tab.",
+            "Read whether it opens on the same order.",
+            "Reload that tab and read it again.",
+        ],
+        expectedBehaviour: "Listing state lives in the URL, so a filtered view is shareable and reproduces on first paint. These routes are prerendered and hydrate their session client-side, so a deep link renders its shell immediately and fills in — what must not happen is the filters arriving and then being replaced by the defaults.",
+        expectedUiState: "The pasted listing URL shows the same rows, filter and sort as the tab it came from. The order URL opens that order and survives a reload. A filtered link that lands on the unfiltered default is the failure.",
+        endResult: "Read-only; nothing persists beyond the URL.",
+    },
+    "checklist-buying-user-dashboard-navigation-become-seller-crossnav": {
+        roles: ["buyer"],
+        startPage: "/user",
+        steps: [
+            "Sign in as karthik.new@gmail.com / TempPass123!, a buyer with no store.",
+            "Open /user and find the route into selling.",
+            "Click it and read where it lands.",
+            "Go back and open /sell directly, reading where that lands.",
+            "Sign out and sign in as tyson@beybladearena.in / TempPass123!, who has a store.",
+            "Open /user and read what the same area of the sidebar offers now.",
+            "Follow it and read where it lands.",
+        ],
+        expectedBehaviour: "The cross-navigation resolves by whether the account already has a store: a buyer is routed into the become-seller flow, an existing seller into their store dashboard. Offering a seller the become-seller flow, or a buyer a dashboard they cannot use, are the two ways this reads wrong.",
+        expectedUiState: "The buyer's link opens the become-seller flow with real content. The seller's opens /store. Neither lands on a 404 and neither offers the wrong destination for its account.",
+        endResult: "Read-only; apply for nothing.",
+    },
+    "checklist-buying-user-dashboard-navigation-browser-back-forward": {
+        roles: ["buyer"],
+        startPage: "/user",
+        steps: [
+            "Sign in as rehan.sheikh@gmail.com / TempPass123!.",
+            "Open /user, then /user/orders, then apply a filter, then open an order's detail.",
+            "Press the browser back button once and read where it lands.",
+            "Press back again and read where it lands, including whether the filter is still applied.",
+            "Press back once more.",
+            "Press forward three times, reading each landing.",
+        ],
+        expectedBehaviour: "Each state change that alters the URL is one history entry, so back walks them in reverse one press at a time. A filter change that writes the URL twice — once for the filter and once to reset the page number — produces two entries for one action, and back appears not to work.",
+        expectedUiState: "Back and forward move one step per press, and the filtered listing returns with its filter applied. Two presses needed to undo a single filter change is the double-navigation failure.",
+        endResult: "Read-only; nothing persists beyond the URL.",
+    },
+    "checklist-buying-user-dashboard-navigation-logged-out-redirect": {
+        roles: ["guest"],
+        startPage: "/user",
+        steps: [
+            "Open a private window with no session.",
+            "Open /user and watch the page for 5 seconds.",
+            "Open /user/orders and watch for 5 seconds.",
+            "Open /user/addresses and watch for 5 seconds.",
+            "Read each for any name, email, order or address at any point.",
+            "Open the browser's View Source on one of them and search for an email address and for a uid.",
+            "Read where each navigation ends up.",
+        ],
+        expectedBehaviour: "These routes are prerendered to a signed-out shell and the session hydrates client-side, so the served HTML is identical for every visitor and cannot contain anyone's data. The redirect therefore happens after hydration — a brief flash of chrome is expected and is the tradeoff being evaluated, while a spinner that never resolves is not.",
+        expectedUiState: "Each URL shows chrome and a loading state, then lands on the sign-in page. No name, email, order or address appears at any point, and none is present in the page source. Nothing is still spinning after 5 seconds. Record whether the flash feels acceptable.",
+        expectedData: { userDataInSource: 0 },
+        endResult: "All three end signed out. Any trace of a real account fails the case outright, separately from the flash question.",
+    },
+    "checklist-buying-user-dashboard-navigation-breadcrumbs-accurate": {
+        roles: ["buyer"],
+        startPage: "/user",
+        steps: [
+            "Sign in as rehan.sheikh@gmail.com / TempPass123!.",
+            "Open /user and read any breadcrumb trail shown.",
+            "Navigate to /user/orders and read the trail.",
+            "Open a specific order's detail and read the trail.",
+            "Click each breadcrumb ancestor in turn and check it lands where it says.",
+            "Check the current page is shown as the last crumb and is not itself a link.",
+        ],
+        expectedBehaviour: "The trail reflects the real route hierarchy and every ancestor is a working link. The last crumb is the current page and is not clickable — a self-link reads as a working link and goes nowhere new, the same defect the policy pages' related-links list had.",
+        expectedUiState: "The trail deepens as the route deepens, every ancestor navigates correctly, and the final crumb is plain text rather than a link.",
+        endResult: "Read-only; nothing persists.",
+    },
+    "checklist-buying-user-dashboard-navigation-sidebar-logout-button": {
+        roles: ["buyer"],
+        startPage: "/user",
+        steps: [
+            "Sign in as rehan.sheikh@gmail.com / TempPass123!.",
+            "Open /user and find the log-out control in the sidebar.",
+            "Click it and read where the browser lands.",
+            "Open /user again and read what happens.",
+            "Press the browser back button and read what is shown.",
+            "Open /user/orders directly and read what happens.",
+        ],
+        expectedBehaviour: "Log out clears both the server session cookie and the client auth session. Clearing only one leaves the browser able to re-mint a session on the next request, which is why the second navigation rather than the redirect is the real check — and a dashboard restored from the back-forward cache after log-out is a real exposure on a shared machine.",
+        expectedUiState: "The browser leaves the dashboard. Opening /user or /user/orders afterwards redirects to sign-in rather than rendering, even briefly with real data. The back button does not restore the dashboard from cache.",
+        endResult: "The session is ended.",
+    },
+};

package/dist/features/tester/seed-data/authored/buying__user-uncovered-pages.d.ts

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

package/dist/features/tester/seed-data/authored/buying__user-uncovered-pages.js

@@ -0,0 +1,90 @@
+/*
+ * WHY: Authored six-part procedures for the buying/user-uncovered-pages page.
+ * WHAT: 4 case(s), keyed by full checklist id.
+ *
+ * Four buyer routes the sweep found with no case naming them anywhere. Three are
+ * "editors that are also pages" — opened by URL, they must render with the form
+ * ALREADY open, because a page whose only content is a closed drawer is a blank
+ * screen with a working URL.
+ *
+ * @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-buying-user-uncovered-pages-user-preorders-renders": {
+        roles: ["buyer"],
+        startPage: "/user/pre-orders",
+        steps: [
+            SIGN_IN_BUYER,
+            "Open /user/pre-orders.",
+            "Read the pre-orders listed, or the empty state.",
+            "For each, read its production status and its expected delivery date.",
+            "Open one and check it links back to the listing it was placed against.",
+            "Check the deposit paid is distinguished from the full price.",
+        ],
+        expectedBehaviour: "A buyer's pre-orders are listed with the two things that make them different from an ordinary order — production status and expected delivery. A pre-order is bought at a deposit, so showing only the full price misstates what was charged and what is still owed.",
+        expectedUiState: "Each pre-order shows its production status, its expected delivery date and its deposit against the full price, and links to its listing. An empty state is acceptable only if the account has none.",
+        endResult: "Read-only.",
+    },
+    "checklist-buying-user-uncovered-pages-user-support-new-renders": {
+        roles: ["buyer"],
+        startPage: "/user/support/new",
+        steps: [
+            SIGN_IN_BUYER,
+            "Open /user/support/new directly by URL.",
+            "Read whether the ticket form is already open or whether the page is blank.",
+            "Close or cancel the form.",
+            "Read where the browser lands.",
+            "Check it is the ticket list rather than a dead route.",
+        ],
+        expectedBehaviour: "An editor that is also a page opens with its form already showing, and cancelling lands on the list it belongs to. A page whose content is a closed drawer is blank with a working URL — nothing errors, and there is nothing to click.",
+        expectedUiState: "The form is open on arrival, and cancelling lands on /user/support. A blank page, or a cancel that leaves the browser nowhere, are both findings.",
+        endResult: "No ticket is created.",
+    },
+    "checklist-buying-user-uncovered-pages-user-catalogue-new-renders": {
+        roles: ["buyer"],
+        startPage: "/user/catalogue/new",
+        steps: [
+            SIGN_IN_BUYER,
+            "Open /user/catalogue/new directly by URL.",
+            "Check the form is already open.",
+            "Fill it with the title 'QA Catalogue Probe' and upload /test-media/sample-image.png.",
+            "Save it.",
+            "Read where the browser lands and check the item is in the catalogue list.",
+            "Reload and check it is still there, then delete it.",
+        ],
+        inputs: { title: "QA Catalogue Probe", imagePath: "/test-media/sample-image.png" },
+        expectedBehaviour: "The form opens on arrival, saves, and the saved item appears in the list. Reloading is the whole check — an item that never reached storage looks identical until then, and an image that was never finalised renders once and breaks later.",
+        expectedUiState: "The item is listed with its photo after the save and still after the reload. A broken image on the second load is the finalise failure.",
+        endResult: "The QA catalogue item is deleted.",
+    },
+    "checklist-buying-user-uncovered-pages-user-addresses-add-renders": {
+        roles: ["buyer"],
+        startPage: "/user/addresses/add",
+        steps: [
+            SIGN_IN_BUYER,
+            "Open /user/addresses/add directly by URL.",
+            "Check the form is already open.",
+            "Fill it with the name 'QA Address Probe', phone 9876543210, line 1 '221B Test Street', landmark 'Opposite the QA park', postal code 560001.",
+            "Save it.",
+            "Read the address list and find the new entry.",
+            "Open it for edit and check the landmark survived.",
+            "Delete the address afterwards.",
+        ],
+        inputs: {
+            fullName: "QA Address Probe",
+            phone: "9876543210",
+            addressLine1: "221B Test Street",
+            landmark: "Opposite the QA park",
+            postalCode: "560001",
+        },
+        expectedBehaviour: "Every field the form collects is written and read back — the landmark specifically, because a form missing a field the server accepts sends nothing for it on every edit and quietly drops whatever was there. Reopening the saved address for edit is the only way to see it.",
+        expectedUiState: "The address appears in the list, and reopening it for edit shows all five values including the landmark. A landmark that is blank on reopen is the finding.",
+        endResult: "The QA address is deleted.",
+    },
+};

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

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