@mohasinac/appkit 4.34.1 → 4.35.1

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

@@ -0,0 +1,344 @@
+/*
+ * WHY: Authored six-part procedures for the buying/wishlist-history page.
+ * WHAT: 20 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 TWO CAPS BEHAVE DIFFERENTLY ON PURPOSE. The wishlist is a HARD cap of 20
+ * — the twenty-first add is refused with an error, because silently dropping an
+ * item the buyer asked to save is worse than telling them the list is full. History
+ * is a SOFT cap of 50 with silent oldest-first eviction, because nobody asked for
+ * a browsing record and an error about it would be noise.
+ *
+ * Both are one document per user, keyed on the user's own id, and every mutation
+ * runs in a transaction — two quick taps must not race into a duplicate.
+ *
+ * @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-wishlist-history-add-wishlist-pdp": {
+        roles: ["buyer"],
+        startPage: "/products/product-beyblade-burst-valkyrie",
+        steps: [
+            "Sign in as rehan.sheikh@gmail.com / TempPass123!.",
+            "Open /products/product-beyblade-burst-valkyrie and read the wishlist control's state.",
+            "Click it and watch the control while the request runs.",
+            "Read its state afterwards.",
+            "Open /wishlist and find the item.",
+            "Return to the product page and reload it, then read the control again.",
+        ],
+        inputs: { productId: "product-beyblade-burst-valkyrie" },
+        expectedBehaviour: "The control adds the item and then reflects that it is saved. It must also reflect the saved state on a fresh load — a control that resets to unsaved on reload is reading nothing and will let the buyer add the same item twice.",
+        expectedUiState: "The control changes to a saved state without a full page load, the item appears on /wishlist, and after the reload the control still reads as saved.",
+        endResult: "The item is on the wishlist. Later cases in this page read it.",
+    },
+    "checklist-buying-wishlist-history-add-wishlist-card": {
+        roles: ["buyer"],
+        startPage: "/products",
+        steps: [
+            "Sign in as rehan.sheikh@gmail.com / TempPass123!.",
+            "Open /products and find a product card with a wishlist control.",
+            "Click the wishlist control on the card WITHOUT opening the product.",
+            "Read the control's state and check the page did not navigate.",
+            "Click the card's body and check it opens that product.",
+            "Go back and check the card's control still reads as saved.",
+        ],
+        expectedBehaviour: "The card's wishlist control acts in place and does not navigate. Clicking the card body still opens the product — merely wiring a control onto a card must not disable its navigation, which is a defect this codebase has had where a selection callback silently removed the link.",
+        expectedUiState: "The control saves without navigating, and the card body still opens the product afterwards. A card that stops opening once it carries a control is the failure.",
+        endResult: "A second item is on the wishlist.",
+    },
+    "checklist-buying-wishlist-history-remove-wishlist": {
+        roles: ["buyer"],
+        startPage: "/wishlist",
+        steps: [
+            "Sign in as rehan.sheikh@gmail.com / TempPass123!.",
+            "Open /wishlist and note how many items it holds.",
+            "Remove one item and read what happens.",
+            "RELOAD and count the items.",
+            "Open that product's page and read its wishlist control.",
+            "Remove an item from the product page instead and check /wishlist reflects it.",
+        ],
+        expectedBehaviour: "Removal persists and both surfaces agree, because both read the same single document. A removal that succeeds on one surface and leaves the other showing the item means one of them is holding its own copy.",
+        expectedUiState: "The count falls by one and stays after the reload. The product page's control reads as unsaved. Removing from the product page removes it from /wishlist too.",
+        endResult: "One item remains on the wishlist.",
+    },
+    "checklist-buying-wishlist-history-wishlist-persists-guest-to-login": {
+        roles: ["guest", "buyer"],
+        startPage: "/products",
+        steps: [
+            "Open /products in a private window with no session.",
+            "Add two products to the wishlist as a guest and note their titles.",
+            "Open /wishlist and confirm both are listed.",
+            "Sign in as karthik.new@gmail.com / TempPass123! from that same window.",
+            "Open /wishlist and read what is listed.",
+            "Check both guest items are present alongside anything the account already had.",
+            "Reload and confirm they persist.",
+        ],
+        expectedBehaviour: "A guest wishlist is merged into the account on sign-in rather than discarded. The buyer saved those items deliberately, so losing them at the moment they create an account is the worst possible time to lose them.",
+        expectedUiState: "After signing in both guest items are on the account's wishlist, together with anything it already held, and they survive a reload. An emptied wishlist after sign-in is the failure.",
+        endResult: "The account's wishlist holds the merged set. Remove the added items afterwards.",
+    },
+    "checklist-buying-wishlist-history-wishlist-idempotent-readd": {
+        roles: ["buyer"],
+        startPage: "/products/product-beyblade-x-wizard-arrow",
+        steps: [
+            "Sign in as rehan.sheikh@gmail.com / TempPass123!.",
+            "Open /products/product-beyblade-x-wizard-arrow and add it to the wishlist.",
+            "Open /wishlist and count how many times it appears.",
+            "Return to the product and click the wishlist control twice in quick succession.",
+            "Open /wishlist and count again.",
+            "Reload and count once more.",
+        ],
+        inputs: { productId: "product-beyblade-x-wizard-arrow" },
+        expectedBehaviour: "Re-adding an item already saved is a no-op rather than a duplicate. Every mutation runs in a transaction precisely so two quick taps cannot race into two entries — a duplicate would also consume one of the twenty slots.",
+        expectedUiState: "The item appears exactly once however many times the control is pressed. Two entries for one product is the failure, and it is easiest to produce with a double tap.",
+        expectedData: { entriesForProduct: 1 },
+        endResult: "The item is on the wishlist once.",
+    },
+    "checklist-buying-wishlist-history-wishlist-cap-enforced": {
+        roles: ["buyer"],
+        startPage: "/products",
+        steps: [
+            "Sign in as karthik.new@gmail.com / TempPass123!, an account with a near-empty wishlist.",
+            "Open /products and add items to the wishlist until twenty are saved, counting as you go.",
+            "Open /wishlist and confirm the count is twenty.",
+            "Add a twenty-first item and read exactly what happens.",
+            "Open /wishlist and count again.",
+            "Remove one item, then add the refused item again and check it is accepted.",
+        ],
+        inputs: { cap: 20 },
+        expectedBehaviour: "The wishlist is a HARD cap: the twenty-first add is refused with a readable error. Silently dropping an item the buyer explicitly asked to save is worse than telling them the list is full — which is the opposite choice from history, where eviction is silent on purpose.",
+        expectedUiState: "The twentieth add succeeds. The twenty-first is refused with a message naming the limit, and the count stays at twenty. Freeing a slot lets the refused item in. A silent failure, or a list that grows to twenty-one, are both failures.",
+        expectedData: { maxItems: 20 },
+        endResult: "The wishlist is at or below twenty. Clear the added items afterwards.",
+    },
+    "checklist-buying-wishlist-history-wishlist-across-listing-types": {
+        roles: ["buyer"],
+        startPage: "/products",
+        steps: [
+            "Sign in as rehan.sheikh@gmail.com / TempPass123!.",
+            "Add a standard product to the wishlist.",
+            "Open an auction and add it.",
+            "Open a pre-order and add it.",
+            "Open a prize draw, a classified, a digital code, a live item and an art print, adding each.",
+            "Open /wishlist and read every entry.",
+            "Check each shows the right type badge and links to the right detail route.",
+        ],
+        expectedBehaviour: "Every listing type can be saved and each entry links to its own detail route. Three types once had their detail route hardcoded to the standard product page, so a saved classified, digital code or live item opened the wrong page from every card and carousel in the app.",
+        expectedUiState: "All eight entries are listed with the correct type badge, and each opens its own detail route rather than a /products URL. An auction entry opening /products is the wrong-route failure.",
+        expectedData: { wrongDetailRoutes: 0 },
+        endResult: "Eight items are saved. Remove them afterwards so the cap cases start clean.",
+    },
+    "checklist-buying-wishlist-history-wishlist-price-drop-accuracy": {
+        roles: ["buyer", "seller"],
+        startPage: "/wishlist",
+        steps: [
+            "Sign in as rehan.sheikh@gmail.com / TempPass123! and add product-beyblade-burst-valkyrie to the wishlist.",
+            "Open /wishlist and read the price shown against it.",
+            "Sign out and sign in as tyson@beybladearena.in / TempPass123!.",
+            "Lower that product's price to 799 and save.",
+            "Sign back in as the buyer and open /wishlist.",
+            "Read the price shown and any price-drop indicator.",
+            "Restore the product's original price.",
+        ],
+        inputs: { productId: "product-beyblade-burst-valkyrie", priceBefore: 999, priceAfter: 799 },
+        expectedBehaviour: "The entry records the price at the time it was saved, so a drop can be computed against it. The CURRENT price must come from the product rather than the snapshot — a list rendering the saved price as if it were live tells the buyer an item costs what it used to.",
+        expectedUiState: "The current price reads ₹799.00 and any drop indicator compares it against the ₹999.00 saved at add time. A list still showing ₹999.00 is reading the snapshot as live.",
+        expectedData: { currentPrice: 799, priceAtAdd: 999 },
+        endResult: "The product's price is restored. The wishlist should then show ₹999.00 again with no drop.",
+    },
+    "checklist-buying-wishlist-history-wishlist-sold-out-item": {
+        roles: ["buyer"],
+        startPage: "/wishlist",
+        steps: [
+            "Sign in as rehan.sheikh@gmail.com / TempPass123!.",
+            "Add product-beyblade-burst-valtryek-v3-sold-out to the wishlist.",
+            "Open /wishlist and read that entry.",
+            "Check it is marked as unavailable rather than looking purchasable.",
+            "Read whether an add-to-cart control is offered on it.",
+            "Click the entry and check the product page also reads as out of stock.",
+        ],
+        inputs: { productId: "product-beyblade-burst-valtryek-v3-sold-out" },
+        expectedBehaviour: "A saved item that has since sold out is marked as such and offers no purchase control. The wishlist is one of the few surfaces where an unavailable item legitimately remains visible — the buyer asked to watch it — so it must say so rather than being filtered away or shown as buyable.",
+        expectedUiState: "The entry is present and marked unavailable, with no add-to-cart control. An entry offering purchase on a sold-out item is the failure; silently removing it from the list is a different one.",
+        endResult: "Remove the entry afterwards.",
+    },
+    "checklist-buying-wishlist-history-wishlist-empty-state": {
+        roles: ["buyer"],
+        startPage: "/wishlist",
+        steps: [
+            "Sign in as karthik.new@gmail.com / TempPass123!.",
+            "Open /wishlist and remove every item until none remain.",
+            "Read what the page shows.",
+            "Check it offers a way onward rather than only stating the list is empty.",
+            "Follow that link and read where it lands.",
+            "Reload /wishlist and confirm the empty state is still shown.",
+        ],
+        expectedBehaviour: "An empty wishlist shows a named empty state with a route back into browsing. A blank area reads as a broken page rather than an empty one, and this page is reachable from the header on every visit.",
+        expectedUiState: "A readable message and a working link to browse. Not a bare white area and not a heading with nothing under it. The link lands on a real listing page.",
+        endResult: "The wishlist is empty.",
+    },
+    "checklist-buying-wishlist-history-wishlist-add-to-cart-from-list": {
+        roles: ["buyer"],
+        startPage: "/wishlist",
+        steps: [
+            "Sign in as rehan.sheikh@gmail.com / TempPass123!.",
+            "Add product-beyblade-burst-valkyrie to the wishlist and open /wishlist.",
+            "Use the add-to-cart control on that entry.",
+            "Watch the control while the request runs and read the cart badge.",
+            "Open /cart and confirm the item is there at the right price.",
+            "Return to /wishlist and read whether the item is still saved.",
+        ],
+        expectedBehaviour: "Adding to the cart from the wishlist does not remove it from the wishlist — those are two different intentions, and a buyer who adds one of several saved items has not stopped watching it. The price charged comes from the product, not from the saved snapshot.",
+        expectedUiState: "The cart badge increases and /cart holds the item at its current price. The wishlist entry is still present afterwards. An entry that vanishes on add-to-cart is the failure.",
+        endResult: "The item is in both the cart and the wishlist. Empty the cart afterwards.",
+    },
+    "checklist-buying-wishlist-history-wishlist-card-clickable": {
+        roles: ["buyer"],
+        startPage: "/wishlist",
+        steps: [
+            "Sign in as rehan.sheikh@gmail.com / TempPass123! with at least two items saved.",
+            "Open /wishlist and click an entry's image.",
+            "Read where it lands and go back.",
+            "Click the entry's title and read where it lands.",
+            "Go back and click an empty part of the entry's body.",
+            "Check every route reached is that item's own detail page.",
+        ],
+        expectedBehaviour: "The whole entry is a link to its item. A card that only responds on its title forces the buyer to aim, and a card that responds nowhere is a dead end — this list exists to get back to saved items.",
+        expectedUiState: "Image, title and body all open the same product's detail page. An inert region on the card is the finding.",
+        endResult: "Read-only; nothing persists.",
+    },
+    "checklist-buying-wishlist-history-wishlist-heart-solid-red": {
+        roles: ["buyer"],
+        startPage: "/products/product-beyblade-burst-valkyrie",
+        steps: [
+            "Sign in as rehan.sheikh@gmail.com / TempPass123!.",
+            "Open a product NOT on the wishlist and look at its wishlist control.",
+            "Note the glyph's shape and fill.",
+            "Add it and look at the control again.",
+            "Compare the saved and unsaved states — check they differ by more than colour alone.",
+            "Switch to dark mode and read both states again.",
+            "Check the glyph is a rendered icon rather than a text character.",
+        ],
+        expectedBehaviour: "Saved and unsaved are visually distinct in both themes, and the glyph is a real icon rather than a text character. A text character cannot be sized by any utility — it renders at the platform font's fallback size, which is exactly why one control in a row can look wrong beside its neighbours.",
+        expectedUiState: "The unsaved state is an outline and the saved state is filled, distinguishable in both themes. The glyph is proportionate to its control. A heart character used as the icon, or a state difference carried by colour alone, are both findings.",
+        endResult: "Remove the item afterwards.",
+    },
+    "checklist-buying-wishlist-history-wishlist-view-remove-buttons": {
+        roles: ["buyer"],
+        startPage: "/wishlist",
+        steps: [
+            "Sign in as rehan.sheikh@gmail.com / TempPass123! with at least two items saved.",
+            "Open /wishlist and read every control offered on an entry.",
+            "Check both a view and a remove control are present.",
+            "Use remove and read whether it asks for confirmation.",
+            "Read the entry count immediately and after a RELOAD.",
+            "Check the remove acted on the entry it was pressed on, not another.",
+        ],
+        expectedBehaviour: "Each entry offers both a way in and a way out. Remove acts on the entry it belongs to — a remove keyed on array position deletes the wrong one once the list has shifted, and both survivors still look like valid entries.",
+        expectedUiState: "View and remove are both present. The removed entry is the one whose control was pressed, and the count is correct after the reload.",
+        endResult: "One fewer item is saved.",
+    },
+    "checklist-buying-wishlist-history-wishlist-sync-item": {
+        roles: ["buyer"],
+        startPage: "/wishlist",
+        steps: [
+            "Sign in as rehan.sheikh@gmail.com / TempPass123! in window A and open /wishlist.",
+            "In window B, sign in as the same account and open a product not yet saved.",
+            "Add it to the wishlist in window B.",
+            "Return to window A and reload /wishlist.",
+            "Read whether the new item is present.",
+            "Remove it in window A, then reload window B's product page and read its control.",
+        ],
+        expectedBehaviour: "Both windows read one document, so a change in either is visible in the other after a reload. Whether it propagates without a reload is worth recording but is not the assertion — the wishlist is not a realtime surface.",
+        expectedUiState: "After the reload each window reflects the other's change. Note whether anything updated without reloading. A change that never appears even after a reload means one window is holding a private copy.",
+        endResult: "Both windows agree on the wishlist's contents.",
+    },
+    "checklist-buying-wishlist-history-wishlist-sync-all": {
+        roles: ["buyer"],
+        startPage: "/wishlist",
+        steps: [
+            "Sign in as rehan.sheikh@gmail.com / TempPass123! and open /wishlist.",
+            "Look for a control that syncs or refreshes the whole list.",
+            "Note the item count and each entry's price and availability.",
+            "Use the sync control if one exists.",
+            "Read whether prices and availability updated.",
+            "Reload the page and compare against what the sync produced.",
+        ],
+        expectedBehaviour: "A sync refreshes each entry's live price and availability from its product rather than from the saved snapshot. If no such control exists, the page must already be reading live values on load — one of the two has to be true, and this case establishes which.",
+        expectedUiState: "Prices and availability match the products' current values, either after the sync or already on load. Record which mechanism is in play. Values matching the saved snapshot rather than the product is the failure either way.",
+        endResult: "Read-only; nothing persists.",
+    },
+    "checklist-buying-wishlist-history-view-history": {
+        roles: ["buyer"],
+        startPage: "/user/history",
+        steps: [
+            "Sign in as rehan.sheikh@gmail.com / TempPass123!.",
+            "Open three different product pages in sequence, noting their titles and the order.",
+            "Open the browsing history page.",
+            "Read the entries and their order.",
+            "Check the most recently viewed is first.",
+            "Check each entry shows a title, an image and a viewed time, and links to its product.",
+        ],
+        expectedBehaviour: "History records each view with a timestamp and shows the most recent first. Each entry carries a snapshot of the product's title and image so the list renders even if the product is later removed — which is why a deleted product leaves a readable entry whose link 404s rather than a blank row.",
+        expectedUiState: "The three products appear newest first with titles, images and times, each linking to its product. An entry with no title or image is reading the live product rather than its snapshot.",
+        endResult: "Three entries are recorded.",
+    },
+    "checklist-buying-wishlist-history-history-revisit-reorders": {
+        roles: ["buyer"],
+        startPage: "/user/history",
+        steps: [
+            "Sign in as rehan.sheikh@gmail.com / TempPass123!.",
+            "Open the history page and note which product is third from the top.",
+            "Open that product's page again.",
+            "Return to the history page and read the order.",
+            "Check that product is now first.",
+            "Count the entries and check the product appears only once.",
+        ],
+        expectedBehaviour: "Revisiting a product moves its entry to the top rather than adding a second one. The existing entry for that product is removed and a fresh one inserted at the front — so the count is unchanged and the order reflects the newest visit.",
+        expectedUiState: "The revisited product is first and appears exactly once. The total entry count is unchanged. Two entries for one product is the failure.",
+        expectedData: { entriesForProduct: 1 },
+        endResult: "History is reordered with no duplicates.",
+    },
+    "checklist-buying-wishlist-history-history-fifo-cap": {
+        roles: ["buyer"],
+        startPage: "/user/history",
+        steps: [
+            "Sign in as karthik.new@gmail.com / TempPass123!, an account with little history.",
+            "Open the history page and note the entry count.",
+            "Browse enough distinct product pages to exceed fifty entries in total, noting the FIRST product viewed.",
+            "Open the history page and count the entries.",
+            "Look for that first product in the list.",
+            "Check no error or warning appeared while browsing.",
+        ],
+        inputs: { cap: 50 },
+        expectedBehaviour: "History is a SOFT cap: at fifty entries the oldest is evicted silently. Nobody asked for a browsing record, so an error about it would be noise — which is the opposite choice from the wishlist, where the buyer explicitly asked to save something and a silent drop would be wrong.",
+        expectedUiState: "The count never exceeds fifty. The earliest product viewed is gone from the list. No error or warning appeared at any point. A count above fifty means the cap is not applied on write and the document grows without bound.",
+        expectedData: { maxEntries: 50 },
+        endResult: "History holds at most fifty entries. The contrast with the wishlist's hard cap is the point.",
+    },
+    "checklist-buying-wishlist-history-history-guest-merge-on-login": {
+        roles: ["guest", "buyer"],
+        startPage: "/products",
+        steps: [
+            "Open a private window with no session and view three product pages, noting their titles.",
+            "Open the history page as a guest and confirm the three are listed.",
+            "Sign in as karthik.new@gmail.com / TempPass123! from that same window.",
+            "Open the history page and read the entries.",
+            "Check the three guest views are present alongside the account's existing history.",
+            "Check no product appears twice and the total does not exceed fifty.",
+            "Check the order is newest-first across both sets.",
+        ],
+        expectedBehaviour: "Guest history is mirrored locally and merged into the account on sign-in, de-duplicated by product with the newer view winning, and trimmed to fifty. All three of those steps matter: a merge without de-duplication produces two entries for a product seen in both states, and one without trimming pushes the document past its cap.",
+        expectedUiState: "All three guest products are present, no product appears twice, the total is at most fifty, and the order is newest-first across the merged set.",
+        expectedData: { maxEntries: 50, duplicateProducts: 0 },
+        endResult: "The account's history holds the merged, de-duplicated set.",
+    },
+};

package/dist/features/tester/seed-data/authored/community-support__public-profile.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/community-support__public-profile.js

@@ -0,0 +1,53 @@
+/*
+ * WHY: Authored six-part procedures for the community-support/public-profile page.
+ * WHAT: 2 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.
+ *
+ * Both cases are run SIGNED OUT on purpose. A public page read while signed in as
+ * the owner proves nothing about what the public sees, and the store page is one
+ * of the surfaces that once passed a raw store document straight into a client
+ * component — publishing a decrypted WhatsApp token into the page HTML.
+ *
+ * @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-community-support-public-profile-view-seller-store": {
+        roles: ["guest"],
+        startPage: "/stores",
+        steps: [
+            "Open /stores in a private window with no session.",
+            "Click the 'Beyblade Arena' card.",
+            "Read the store header — name, logo, banner, verified badge and rating.",
+            "Read the tab bar and open each tab in turn.",
+            "Open the browser's View Source and search the HTML for the words accessToken, adminNotes, suspensionReason and customCommissionRate.",
+        ],
+        inputs: { storeId: "store-beyblade-arena" },
+        expectedBehaviour: "The public store page is built from a projection that names every field it emits, rather than by spreading the store document and deleting a few keys. A deny-list is blind to fields nobody thought to delete — and to fields the TypeScript interface never declared at all.",
+        expectedUiState: "The header shows 'Beyblade Arena' with its logo and banner. The tabs render their listings. None of accessToken, adminNotes, suspensionReason or customCommissionRate appears anywhere in the page source, including inside the React data payload embedded at the bottom of the HTML.",
+        expectedData: { secretFieldsInHtml: 0 },
+        endResult: "Nothing persists — read-only. A hit on any of those four words is a data leak and fails the case outright, regardless of how the page looks.",
+    },
+    "checklist-community-support-public-profile-view-public-profile": {
+        roles: ["guest"],
+        startPage: "/profile/user-tyson-blader",
+        steps: [
+            "Open /profile/user-tyson-blader in a private window with no session.",
+            "Read the display name, avatar and bio.",
+            "Open each tab on the profile.",
+            "Search the page source for an email address and for a phone number.",
+            "Open /profile/user-yugi-muto and read the same things.",
+        ],
+        inputs: { sellerProfile: "user-tyson-blader", buyerProfile: "user-yugi-muto" },
+        expectedBehaviour: "A public profile shows what its owner chose to publish and nothing drawn from their account record. Email and phone are PII-encrypted at rest and have no business on this page in any form, masked or otherwise.",
+        expectedUiState: "Both profiles render a display name, avatar and bio, with their tabs populated. Neither page — nor its source — contains an email address or a phone number. A profile set to Private returns a not-found page for a signed-out visitor rather than rendering with fields blanked out.",
+        endResult: "Nothing persists — read-only. Both profiles are public in the seed, so a not-found here means the visibility default changed.",
+    },
+};

package/dist/features/tester/seed-data/authored/community-support__support-tickets.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/community-support__support-tickets.js

@@ -0,0 +1,76 @@
+/*
+ * WHY: Authored six-part procedures for the community-support/support-tickets page.
+ * WHAT: 3 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-community-support-support-tickets-create-ticket": {
+        roles: ["buyer"],
+        startPage: "/user/support",
+        steps: [
+            "Sign in as rehan.sheikh@gmail.com / TempPass123!.",
+            "Open /user/support.",
+            "Click the control that starts a new ticket.",
+            "Type 'QA Ticket create-ticket' in the subject field.",
+            "Select 'Orders' as the category.",
+            "Type 'Raised by the tester checklist to confirm ticket creation persists.' in the message field.",
+            "Submit the ticket.",
+            "Reload /user/support.",
+        ],
+        inputs: {
+            subject: "QA Ticket create-ticket",
+            category: "Orders",
+            message: "Raised by the tester checklist to confirm ticket creation persists.",
+        },
+        expectedBehaviour: "A ticket document is created against this buyer with a ticket- prefixed id, an open status, and the first message stored as its opening entry rather than as a separate field the reply thread cannot see.",
+        expectedUiState: "The list gains a row reading 'QA Ticket create-ticket' with an open status and the Orders category. Opening it shows the submitted message as the first entry in the thread.",
+        expectedData: { subject: "QA Ticket create-ticket", status: "open" },
+        endResult: "The row is still there after the reload. A ticket that appears once and is gone on refresh was written to component state, not to Firestore.",
+    },
+    "checklist-community-support-support-tickets-reply-ticket": {
+        roles: ["buyer"],
+        startPage: "/user/support",
+        steps: [
+            "Sign in as rehan.sheikh@gmail.com / TempPass123!.",
+            "Open /user/support and open the ticket named 'QA Ticket create-ticket'.",
+            "Read how many messages the thread holds.",
+            "Type 'QA Reply reply-ticket — second message in the thread.' in the reply box.",
+            "Submit the reply.",
+            "Reload the page.",
+        ],
+        inputs: { reply: "QA Reply reply-ticket — second message in the thread." },
+        expectedBehaviour: "The reply is appended to the ticket's own message array in a transaction, so two replies sent quickly cannot overwrite one another. An ordinary reply that carries no status change costs one write and no read — the ticket is only re-read when a status accompanies the message.",
+        expectedUiState: "The thread gains a second entry with the typed text, attributed to the buyer and timestamped. The earlier message is still above it, unchanged. The ticket's status has not silently moved to resolved.",
+        expectedData: { threadMessageCount: 2 },
+        endResult: "Both messages survive the reload in the same order. A reply that replaces the first message rather than appending is the failure this case catches.",
+    },
+    "checklist-community-support-support-tickets-support-tickets-search-box": {
+        roles: ["buyer"],
+        startPage: "/user/support",
+        steps: [
+            "Sign in as rehan.sheikh@gmail.com / TempPass123!.",
+            "Open /user/support and read the total number of rows.",
+            "Type 'QA Ticket' in the search box.",
+            "Read the rows.",
+            "Clear the box and type 'zzzznope'.",
+            "Read the rows.",
+            "Clear the box, then use the status filter to select a status and read the rows.",
+            "Toggle 'Hide resolved/closed' and read the rows.",
+        ],
+        inputs: { matchingQuery: "QA Ticket", nonsenseQuery: "zzzznope" },
+        expectedBehaviour: "This list moved onto the shared listing scaffold, which supplies search over subject, id and category for free. The pre-existing status filter and the hide-resolved toggle have to keep working across that conversion — a migration that adds one affordance and quietly drops two is a net loss.",
+        expectedUiState: "'QA Ticket' narrows the list to matching subjects. 'zzzznope' returns an empty state, not the full list — that is the control which proves the box filters rather than decorates. The status filter changes which rows appear, and the toggle removes resolved and closed rows.",
+        expectedData: { nonsenseResultCount: 0 },
+        endResult: "Nothing persists; search and filter state live in the URL, so reloading reproduces the same narrowed list.",
+    },
+};

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

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

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

@@ -0,0 +1,93 @@
+/*
+ * WHY: Authored six-part procedures for the content-discovery/blog 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.
+ *
+ * Blog posts have no gallery field, so extra images live inline in the content
+ * HTML — a case looking for a separate image array is looking for something the
+ * document has never had.
+ *
+ * @tag domain:tester
+ * @tag layer:seed
+ * @tag pattern:none
+ * @tag access:server-only
+ * @tag consumers:seed-data/authored/index.ts
+ * @tag sideEffects:none
+ */
+export const authored = {
+    "checklist-content-discovery-blog-blog-listing": {
+        roles: ["guest"],
+        startPage: "/blog",
+        steps: [
+            "Open /blog in a private window with no session.",
+            "Read every card — title, excerpt, cover image, category and read time.",
+            "Note whether any card names a draft or archived post.",
+            "Use the category filter, selecting each value in turn, and read the results.",
+            "Page to the end of the list.",
+        ],
+        expectedBehaviour: "The listing shows published posts only. The seed holds 17 published, 2 draft and 1 archived, so a listing showing 20 is not filtering by status at all — and status filtering is the kind of guard that gets dropped when a route stops sending a parameter the query only applied when asked.",
+        expectedUiState: "Every card carries a title, an excerpt, a rendered cover image and a category. No draft or archived post appears. Each category filter value returns rows or a named empty state.",
+        expectedData: { draftPostsVisible: 0 },
+        endResult: "Read-only; nothing persists beyond the URL.",
+    },
+    "checklist-content-discovery-blog-read-post": {
+        roles: ["guest"],
+        startPage: "/blog",
+        steps: [
+            "Open /blog in a private window and click the first post.",
+            "Read the title, author, publish date and read time.",
+            "Read the whole article body, checking the paragraphs and any inline images render.",
+            "Read the address bar and note whether the URL uses the post's slug.",
+            "Reload the page.",
+        ],
+        expectedBehaviour: "A post renders its stored HTML content, including the images embedded inline within it. The route is keyed on slug, so the URL is stable and shareable.",
+        expectedUiState: "Title, author, date and read time are shown. The body renders as formatted prose with its inline images displayed — not as raw HTML tags shown as visible text, and not as a wall of markup. The URL carries the post's slug.",
+        endResult: "Read-only; nothing persists. The reload shows the same article.",
+    },
+    "checklist-content-discovery-blog-blog-cover-image-display": {
+        roles: ["guest"],
+        startPage: "/blog",
+        steps: [
+            "Open /blog in a private window and look at every card's cover image.",
+            "Hard-reload with Ctrl+Shift+R and look again.",
+            "Open one post and look at its cover image at the top of the article.",
+            "Note whether the same image appears on the card and on the post.",
+            "Look for any broken-image glyph or grey placeholder tile.",
+        ],
+        expectedBehaviour: "Cover images are served through the media proxy, which is what applies the watermark and keeps the storage bucket private. An image stored as a raw bucket URL bypasses that entirely and is the pattern to watch for.",
+        expectedUiState: "Every card shows its cover image, on both loads. The post's hero image matches its card's. No broken-image glyph and no grey placeholder square anywhere.",
+        endResult: "Read-only; nothing persists.",
+    },
+    "checklist-content-discovery-blog-blog-youtube-embed": {
+        roles: ["guest"],
+        startPage: "/blog",
+        steps: [
+            "Open /blog in a private window and find a post whose card or body indicates a video.",
+            "Open that post.",
+            "Scroll to the embedded video.",
+            "Click play and watch for a few seconds.",
+            "Read any error text shown in or near the player.",
+        ],
+        expectedBehaviour: "A YouTube id on a post renders as a privacy-preserving embed. The failure worth naming is the one the product-detail pages had: a YouTube URL handed to a native video element, which cannot play a watch-page URL and says so in the player's own words.",
+        expectedUiState: "The embedded player renders and plays on click. What must not appear is 'No video with supported format and MIME type found', an empty black box, or a bare link where a player should be.",
+        endResult: "Read-only; nothing persists.",
+    },
+    "checklist-content-discovery-blog-blog-related-posts-sections": {
+        roles: ["guest"],
+        startPage: "/blog",
+        steps: [
+            "Open /blog in a private window and open any post.",
+            "Scroll below the article body.",
+            "Read the heading of each related section and the cards inside it.",
+            "Check whether the post currently open appears in any of them.",
+            "Click a card in each section and confirm it opens that post.",
+        ],
+        expectedBehaviour: "Three separate signals are rendered below the article — same category, shared tags, and same author — each as its own section. A section with a heading and an empty rail should not render at all; showing the heading anyway advertises content that is not there.",
+        expectedUiState: "Three headed sections appear: Related Posts, 'You might also like', and a same-author section. Each holds at least one card with a real title and image. The current post appears in none of them, and every card opens the post it names.",
+        expectedData: { selfLinkCount: 0 },
+        endResult: "Read-only; nothing persists.",
+    },
+};

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

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