@mohasinac/appkit 4.11.3 → 4.12.1

package/dist/features/tester/seed-data/tester-checklist-seed-data.js

@@ -99,6 +99,18 @@ const rawTesterChecklistItems = [
                     description: "Changed 2026-08-21 — this flow now calls Firebase directly from the browser instead of going through a server route, so the client must swallow Firebase's auth/user-not-found error. Submit a made-up address like nobody-here-12345@example.com and confirm you see \"If an account exists for that email, a reset link is on its way.\" — the same wording a real address produces, with no error toast and nothing in the UI distinguishing the two cases.",
                     href: "/auth/forgot-password",
                 },
+                {
+                    key: "auth-emails-sender-identity-and-inbox",
+                    label: "Signup-verification and password-reset emails arrive in the real inbox, from the site's own sender identity — not spam, not a stranger's domain",
+                    description: "Added 2026-08-21. Register with an address you can actually open, and separately request a password reset. For BOTH emails confirm: (a) it arrives within a few minutes; (b) the From name and address are the site's configured sender, and the display name is spelled \"LetItRip\" exactly — not \"Letitrip\" or \"LetiTrip\"; (c) it landed in the inbox rather than spam or promotions; (d) the button/link inside opens the live site and completes the flow. Try it once with a Gmail address and once with a non-Gmail address if you can — deliverability often differs between providers.",
+                    href: "/auth/register",
+                },
+                {
+                    key: "auth-email-links-single-use",
+                    label: "A used or expired verification / password-reset link fails cleanly with a readable message — it never silently succeeds twice",
+                    description: "Added 2026-08-21. Complete a password reset, then click the SAME link in that email a second time. Confirm you get a clear, human-readable \"this link has already been used or has expired\" style message with a way to request a fresh one — not a blank page, not a raw Firebase error code, and definitely not a second successful password change. Repeat the same double-click test with a signup verification link.",
+                    href: "/auth/forgot-password",
+                },
             ],
         },
         {
@@ -185,6 +197,72 @@ const rawTesterChecklistItems = [
                     description: "Verify against the seeded fixtures: \"Test Collectible — Sold Out\" (standard, hidden until \"Show sold\" is on), \"Test Auction — Already Won\" (hidden until \"Show ended\" is on), \"Test Prize Draw — Already Closed\" (hidden until \"Show closed\" is on). All three should be genuinely absent by default, not just from an unrelated broken query.",
                     href: "/products",
                 },
+                {
+                    key: "product-type-chips-cover-all-types",
+                    label: "The TYPE chip row on /products lists ALL nine listing types — Standard, Auctions, Pre-Orders, Prize Draws, Classifieds, Digital Codes, Live Items, Art and Stickers",
+                    description: "Fixed 2026-08-21 — the row used to show only 5 chips (All / Standard / Classified / Digital Codes / Live Items), so auctions, pre-orders, prize draws, art and stickers were unreachable from the main catalogue even though items of those types existed. Count the chips: there should be nine, and none labelled \"Bundles\" (bundles are not a listing type).",
+                    href: "/products",
+                },
+                {
+                    key: "product-type-chips-multi-select",
+                    label: "The TYPE chips behave as CHECKBOXES, not radio buttons — several can be ticked at once, and ticking Auctions + Pre-Orders shows both types in one grid",
+                    description: "Tick Auctions, then tick Pre-Orders WITHOUT unticking Auctions. Both must stay highlighted and the grid must contain items of both types. Untick both and the grid returns to showing every type.",
+                    href: "/products",
+                },
+                {
+                    key: "product-type-chips-none-means-all",
+                    label: "With NO type chip ticked, /products shows a mix of listing types — check the coloured type badges on the cards",
+                    description: "\"Nothing ticked\" means \"every type\", so you should be able to spot at least two different badges (e.g. an \"Auction\" and a \"Digital Code\") within the first page without filtering.",
+                    href: "/products",
+                },
+                {
+                    key: "product-type-chip-drives-sort-options",
+                    label: "Ticking exactly ONE type changes the Sort dropdown to that type's own sorts — Auctions alone offers \"Ending Soon\", Pre-Orders alone offers \"Earliest Delivery\"",
+                    description: "Tick only Auctions and open Sort: \"Ending Soon\" must be present. Untick it, tick only Pre-Orders: \"Earliest Delivery\" must be present and \"Ending Soon\" gone. With two types ticked only the sorts valid for both remain (Newest / Price / Name) — that is correct, not a bug.",
+                    href: "/products",
+                },
+                {
+                    key: "product-type-chip-sort-resets-no-empty-page",
+                    label: "Choosing a type-specific sort and THEN changing the type selection never leaves an empty grid or an error",
+                    description: "The important regression check. Tick Auctions, sort by \"Ending Soon\", then untick Auctions and tick Standard instead. The grid must repopulate with products. A blank page here means a stale sort leaked into the new query.",
+                    href: "/products",
+                },
+                {
+                    key: "product-type-toggles-follow-selection",
+                    label: "The toolbar toggles follow the type selection — \"Show ended\" appears only when a time-limited type is in play, \"Show sold\" only when a sellable type is",
+                    description: "Tick only Auctions: a \"Show ended\" toggle appears. Tick only Standard instead: \"Show ended\" disappears and \"Show sold\" remains. With nothing ticked (= all types) both may appear, which is correct.",
+                    href: "/products",
+                },
+                {
+                    key: "product-type-chip-dedicated-page-link",
+                    label: "Ticking exactly one type that has its own browse page shows a \"Full <type> filters\" link that lands on the right page",
+                    description: "Tick only Auctions — a \"Full Auctions filters\" link should appear beside the chips and open /auctions. Repeat for Pre-Orders and Prize Draws.",
+                    href: "/products",
+                },
+                {
+                    key: "product-type-selection-survives-reload",
+                    label: "The ticked type chips are reflected in the URL and survive a reload and the browser Back button",
+                    description: "Tick Auctions + Art, copy the URL, open it in a new tab: the same two chips must come back ticked with the same grid. Then press Back and confirm the previous selection returns.",
+                    href: "/products",
+                },
+                {
+                    key: "free-shipping-toggle-actually-filters",
+                    label: "The \"Free shipping\" toggle on /products actually REDUCES the number of results — it is not a no-op",
+                    description: "Fixed 2026-08-21 — the toggle sent a filter on a field that was not permitted, so it was silently discarded and the toggle did nothing at all. Note the result count with it off, switch it on, and confirm the count drops and every remaining card really is free-shipping.",
+                    href: "/products",
+                },
+                {
+                    key: "filter-drawer-facets-actually-filter",
+                    label: "The Tags, Sublisting Type and Features sections in the Filters drawer actually change the results — not just the number on the Filters button",
+                    description: "Fixed 2026-08-21 — all three were drawn and counted toward the Filters badge but were never sent to the server. Pick a value in each, Apply, and confirm the result set genuinely narrows instead of staying identical while the badge increments.",
+                    href: "/products",
+                },
+                {
+                    key: "pre-orders-reachable-from-products",
+                    label: "Pre-orders are reachable from /products — tick the Pre-Orders chip and confirm real pre-order items appear with a \"Pre-Order\" badge",
+                    description: "This was the original report: pre-orders (and auctions, prize draws, art, stickers) had no chip at all, so they could only be found via their own dedicated pages.",
+                    href: "/products",
+                },
                 {
                     key: "art-stickers-default-not-empty",
                     label: "The Art & Stickers listing (/art) shows real items by default — not an empty grid that only populates after clicking \"Show sold\"",
@@ -258,6 +336,12 @@ const rawTesterChecklistItems = [
                     label: "Product image gallery thumbnails load reliably (no broken-image icons) and click-to-zoom/rotate works in the lightbox",
                     description: "The thumbnail strip occasionally showed a broken-image icon instead of the photo (transient 3rd-party fetch failures with no retry, fixed 2026-08-19). Reload an auction or product detail page a few times and confirm every thumbnail — not just the main image — renders correctly each time.",
                 },
+                {
+                    key: "image-gallery-thumbnails-not-blank",
+                    label: "The mini thumbnail strip under the main gallery image shows the ACTUAL photos — not empty/blank boxes",
+                    description: "Fixed 2026-08-21 — the thumbnails rendered as blank bordered squares while the large main image above them was fine. Cause: a wrapper element inside the appkit <Button> primitive collapsed to zero size, so every image inside a button-shaped image tile had nothing to fill. Open \"Beyblade Burst B-01 Valkyrie\" (product-beyblade-burst-valkyrie) or any product with 2-3 photos and confirm each mini thumbnail below the main image shows its own picture, that the active one is outlined, and that clicking one swaps the large image.",
+                    href: "/products/product-beyblade-burst-valkyrie",
+                },
                 {
                     key: "video-playback",
                     label: "A product's video slide opens in theater mode with playback, zoom, and rotate controls",
@@ -299,6 +383,12 @@ const rawTesterChecklistItems = [
                     description: "Verify against \"Test Product Set — Standard #1 + Standard #2\" (group-tester-sandbox-bundle) and either of its two children (product-tester-standard-1 / product-tester-standard-2), findable from the products listing page — all three should show the panel with each other listed, the arrow/triangle expand icons should render as real glyphs (not garbled text), and \"View whole group\" should open a working modal/drawer.",
                     href: "/products/group-tester-sandbox-bundle",
                 },
+                {
+                    key: "grouped-listings-carousel-on-detail",
+                    label: "A \"Grouped listings\" themed carousel appears on a product detail page with real, clickable member items",
+                    description: "Added 2026-08-21 — this carousel previously had no test case of its own outside the category/brand check. It is DIFFERENT from the \"Part of / Parts in this group\" set panel: this one is a horizontal themed scroller (titled by the group's theme, e.g. \"Same character\" / \"From the same set\"), it sits lower down near the related-items carousels, and it only shows for products that belong to an active, visible group. Confirm the cards show real titles and images (not placeholders) and that clicking one lands on that item's own detail page.",
+                    href: "/products/product-tester-standard-1",
+                },
                 { key: "classified-contact-flow", label: "A classified listing shows a contact-seller flow with deliberately no checkout/buy button", href: "/classified/classified-tester-sandbox-1" },
                 { key: "digitalcode-delivery", label: "Purchasing a digital-code listing delivers the code to the buyer post-purchase", href: "/digital-codes/digitalcode-tester-sandbox-1" },
                 { key: "live-item-detail", label: "A live-item listing's detail page shows the livestream link correctly", href: "/live/live-tester-sandbox-1" },
@@ -394,6 +484,18 @@ const rawTesterChecklistItems = [
                     label: "Each order row has a visible \"View Details\" button (in addition to the row itself being clickable) that opens that exact order's detail page",
                     href: "/user/orders",
                 },
+                {
+                    key: "orders-type-tabs-actually-filter",
+                    label: "The Type filter (All / Normal / Auction wins / Offer wins) on My Orders actually narrows the list — picking \"Auction wins\" must show only auction-won orders, not the full list",
+                    description: "Fixed 2026-08-21. The tabs rendered and were clickable but the server never read the orderType filter, so every tab returned the complete unfiltered list with no error. Pick each tab in turn and confirm the row count and contents genuinely change. Against the tester sandbox, \"Auction wins\" should surface the won-auction order and \"Normal\" should not.",
+                    href: "/user/orders",
+                },
+                {
+                    key: "orders-normal-tab-includes-legacy",
+                    label: "The \"Normal\" Type tab also lists older orders placed before order types existed — it must not silently drop them",
+                    description: "Legacy orders carry no orderType value at all, so a strict database match would exclude every one of them. \"Normal\" is deliberately resolved differently for that reason. Confirm your oldest seeded orders still appear under \"Normal\", not only under \"All\".",
+                    href: "/user/orders",
+                },
                 {
                     key: "dashboard-recent-orders-linked",
                     label: "The My Account dashboard's \"Recent Orders\" widget rows are clickable and each shows a \"View Details\" button linking to the correct order — not a dead, non-interactive preview",
@@ -446,6 +548,12 @@ const rawTesterChecklistItems = [
                     description: "Pair with the admin-side case `admin-orders-reject-fraud`. Use a throwaway buyer account — this really does ban it for 7 days.",
                     href: "/user/orders",
                 },
+                {
+                    key: "order-lifecycle-emails-arrive",
+                    label: "As a buyer you get an email at each real order milestone — placed, shipped, delivered, cancelled/refunded — and each one names the right item and order",
+                    description: "Added 2026-08-21. Walk one throwaway order through its whole life with a seller account driving the status changes, keeping the buyer's real inbox open. At each transition confirm an email arrives and that it names the actual product (not a bare order id / GUID), shows the correct status, and links to that specific order. Note which transitions produce NO email — a missing \"delivered\" or \"refunded\" email is exactly the kind of gap this case exists to surface, so record it in the comment rather than passing the case.",
+                    href: "/user/orders",
+                },
             ],
         },
         {
@@ -494,6 +602,51 @@ const rawTesterChecklistItems = [
                     key: "bid-increment-live-tier-change",
                     label: "The displayed \"min increment\" on an open auction updates live (without a page refresh) if another bidder's bid pushes the current bid across a tier boundary",
                 },
+                {
+                    key: "bid-presets-are-increment-multiples",
+                    label: "The quick-bid buttons above the amount field are multiples of the auction's OWN minimum increment — never a flat +₹1 / +₹5 / +₹10",
+                    description: "Fixed 2026-08-21 — the presets were always 1x/5x/10x of the effective increment, but `resolveTieredBidIncrement` treated an empty `auctionConfig.bidIncrementTiers` array as \"no rule\" and fell through to the ₹1 last-resort constant, so every auction on the site rendered +₹1 / +₹5 / +₹10. On an auction whose current bid is in the ₹100-₹1,000 band (₹100 increment) the three buttons must read +₹100 / +₹500 / +₹1,000; on one above ₹10,000 (₹1,000 increment) they must read +₹1,000 / +₹5,000 / +₹10,000. Each button also shows the resulting bid amount underneath the step.",
+                    href: "/auctions/auction-tester-sandbox-cycle-1",
+                },
+                {
+                    key: "bid-preset-follows-live-price",
+                    label: "With a quick-bid preset selected, another bidder raising the price updates the amount in the field too — it does not leave a now-too-low number behind",
+                    description: "Fixed 2026-08-21 — the amount was only ever written on mount or on button click, while the current bid keeps updating over SSE. Open the auction in two tabs, select the +1x preset in tab A, place a higher bid from tab B, then watch tab A: the preset button labels, the \"minimum next bid\" helper text AND the number in the field must all move up together. Before the fix the buttons relabelled but the field kept its stale value, so pressing Place Bid was a guaranteed \"bid must exceed the current winning bid\" rejection.",
+                    href: "/auctions/auction-tester-sandbox-cycle-2",
+                },
+                {
+                    key: "bid-below-current-plus-increment-rejected",
+                    label: "A bid below current bid + minimum increment is rejected with a clear inline error on the amount field — and the rejection is identical whether it is typed in Custom mode or forced through the API",
+                    description: "Switch the preset row to \"Custom\", type an amount between the current bid and current+increment, and submit. Expect an inline error on the field (not a toast, not a silent no-op). Also confirm an amount BELOW the current bid gives the distinct \"must exceed the current winning bid\" message rather than the increment one.",
+                    href: "/auctions/auction-tester-sandbox-cycle-1",
+                },
+                {
+                    key: "bid-custom-need-not-be-exact-multiple",
+                    label: "In Custom mode any amount at or above the minimum is accepted — it does NOT have to be an exact multiple of the increment",
+                    description: "With a ₹100 increment and a ₹1,000 current bid, ₹1,137 must be accepted (it is above the ₹1,100 minimum). The helper text under the field states this explicitly. A client-side rule claiming to enforce exact multiples existed but was a no-op; it was removed rather than made real, because the server never enforced multiples and a real client rule would have rejected bids the server accepts.",
+                    href: "/auctions/auction-tester-sandbox-cycle-1",
+                },
+                {
+                    key: "first-bid-can-equal-starting-bid",
+                    label: "On an auction with NO bids yet, the seller's starting bid is itself an acceptable opening bid — you are not forced to bid starting bid + increment",
+                    description: "Changed 2026-08-21. On a bid-free auction the card's big number is labelled \"Starting bid\" (not \"Current bid\" beside an identical \"Starting bid\"), the first quick-bid button reads \"Minimum\" rather than \"+₹0\", and bidding exactly the starting bid succeeds. Previously a ₹100 auction could only be opened at ₹110, contradicting the \"Starting bid ₹100\" label right next to the field. The increment applies from the second bid onward — confirm the second bidder IS held to current + increment.",
+                },
+                {
+                    key: "first-bid-displays-at-starting-price",
+                    label: "The opening bid displays at the starting price, even when the opening bidder's maximum is much higher",
+                    description: "Proxy-bid semantics: the amount submitted is a MAXIMUM, and with no competition the visible price should sit at the seller's starting price. On a bid-free ₹100 auction with a ₹100 increment, bid ₹500 — the auction's current bid must then read ₹100, not ₹200. Place a second, competing bid from another account and confirm the price then steps up in increments against that ₹500 proxy maximum as expected.",
+                },
+                {
+                    key: "bid-count-increments-by-one",
+                    label: "Placing one bid increases the auction's bid count by exactly ONE, and the current bid never moves backwards",
+                    description: "Fixed 2026-08-21 — the `onBidPlaced` Firestore trigger duplicated work `placeBid` already did atomically: it incremented the bid count a second time (so one bid read as two), force-marked every new bid as winning, and overwrote the current bid with the new bid's amount. On the proxy path where a new bid LOSES to a standing higher maximum, that last part actually lowered the current bid to the loser's amount and named the loser as the leading bidder. Place a single bid and confirm the count goes up by 1, not 2. Then, from a second account, bid BELOW the standing proxy maximum: your bid must be recorded as outbid, and the auction's current bid must go UP (or hold), never down.",
+                    href: "/auctions/auction-tester-sandbox-cycle-3",
+                },
+                {
+                    key: "outbid-notification-goes-to-outbid-user",
+                    label: "The outbid notification goes to the bidder who actually lost the lead — and only when someone genuinely takes the lead from them",
+                    description: "Fixed 2026-08-21 alongside bid-count-increments-by-one — the notification used to be sent from a Firestore trigger that re-read \"who is winning\" AFTER the fact, racing the write that had just changed it, so it could notify the wrong account or nobody. It now fires from the same code path that decides the outcome. Check both directions: (a) outbid the leader and confirm THEY get the notification; (b) place a bid that loses to a standing proxy maximum and confirm the existing leader is NOT sent an \"outbid\" notification, since they never lost the lead.",
+                },
             ],
         },
         {
@@ -556,6 +709,13 @@ const rawTesterChecklistItems = [
                 {
                     key: "cart-mobile-no-overflow",
                     label: "On mobile, cart item cards stay fully within the screen width per seller group — no horizontal overflow/clipping — and a floating checkout bar (styled like the bulk-action bar, sitting above the bottom nav) shows the total and a Checkout button, with enough bottom margin that the last cart item is never hidden behind it",
+                    description: "Root-caused 2026-08-21 — the appkit <Checkbox> root div is width:100%, and the caller's className landed on the inner <input> instead of that root, so the select-item checkbox claimed the whole row, squeezed each item card to ~0px, and pushed its 80px thumbnail outside the seller card's border (same defect class as <Select>/wrapperClassName, Root Cause #29). Test at a 360px viewport with at least two sellers.",
+                    href: "/cart",
+                },
+                {
+                    key: "cart-seller-group-contains-items",
+                    label: "At a 360px viewport, every cart item row sits fully inside its seller's rounded card, separated by thin divider lines — no card-inside-a-card look, nothing overlapping or extending past the card border, and no horizontal scrolling of the page",
+                    description: "Add items from two different sellers, ideally one with a very long product title. The seller card should be the only card: header with \"Sold by <store>\" and that seller's subtotal, then divider-separated item rows, then that seller's fees and add-ons.",
                     href: "/cart",
                 },
                 {
@@ -569,6 +729,18 @@ const rawTesterChecklistItems = [
                     label: "With an accepted offer pending (and no won auction), only the Cart tab's checkout is disabled — the Offers tab itself is checkoutable",
                     href: "/cart",
                 },
+                {
+                    key: "auction-win-countdown-visible",
+                    label: "A won-auction cart line shows a live countdown next to \"payment required\" — days/hours/minutes remaining out of the 48-hour window — that ticks down while you watch",
+                    description: "Payment for a won auction is MANDATORY (unlike an accepted offer, which the buyer may walk away from). The deadline was being written by settlement and enforced by the expiry sweep, but nothing ever rendered it, so a win could silently lapse and be forfeited with no warning anywhere in the UI. Use auction-tester-sandbox-won.",
+                    href: "/cart",
+                },
+                {
+                    key: "auction-win-forfeits-after-deadline",
+                    label: "A won auction left unpaid past its 48-hour deadline is forfeited — the cart line disappears, the bid shows as forfeited, and the buyer is notified that repeated non-payment can restrict their account",
+                    description: "An accepted offer past its deadline must lapse quietly instead, with no penalty — walking away from your own offer is allowed. Confirm the two behave differently.",
+                    href: "/user/bids",
+                },
                 {
                     key: "checkout-lanes-totals-scoped",
                     label: "Each cart tab's summary total reflects ONLY that tab's items — the Cart tab total never includes a pending auction or offer amount, and vice versa",
@@ -579,6 +751,154 @@ const rawTesterChecklistItems = [
                     label: "Opening checkout from a specific cart tab lands on the matching lane, shows only that lane's items and total, and (for Auction/Offer lanes) shows an info banner and hides the coupon field",
                     href: "/checkout",
                 },
+                // --- Mobile bar parity with the desktop summary ---------------------
+                {
+                    key: "cart-mobile-bar-lane-scoped",
+                    label: "The mobile bottom bar's total matches the desktop Summary total on every cart tab, and both name which lane the total covers (\"This total covers your cart only\" / \"…your won auctions only\")",
+                    description: "The desktop Summary was converted to per-lane totals but the mobile bar was left reading the old blended figure, so the two disagreed on the same cart. Needs items in more than one lane — e.g. a normal product plus auction-tester-sandbox-won. Switch tabs and compare both viewports.",
+                    href: "/cart",
+                },
+                {
+                    key: "cart-mobile-bar-lane-gated",
+                    label: "On a cart tab that is not currently payable, the mobile Checkout button is disabled and shows the same blocking reason the desktop button shows — tapping it does nothing",
+                    description: "On a phone viewport with a won auction pending, open the Cart tab. The total still shows (so you can see what's there), but Checkout must be disabled with a reason naming the blocking lane. Previously the mobile button stayed enabled and navigated.",
+                    href: "/cart",
+                },
+                {
+                    key: "cart-mobile-checkout-carries-lane",
+                    label: "Tapping Checkout from the Won Auctions or Accepted Offers tab on mobile lands on the checkout page already on that lane (URL contains ?lane=auction or ?lane=offer)",
+                    description: "The desktop button already carried the lane; the mobile one navigated to a lane-less /checkout.",
+                    href: "/cart",
+                },
+                {
+                    key: "cart-select-all-lane-scoped",
+                    label: "\"Select all (N)\" counts only the items on the current tab, and \"Remove all\" never deletes won-auction or accepted-offer lines",
+                    href: "/cart",
+                },
+                // --- Expandable price breakdown -------------------------------------
+                {
+                    key: "cart-breakdown-expand-mobile",
+                    label: "On mobile, the total row in the bottom bar shows an up-arrow; tapping it opens a panel ABOVE the checkout bar with the full price breakdown, and tapping again (or outside) closes it",
+                    href: "/cart",
+                },
+                {
+                    key: "cart-breakdown-expand-desktop",
+                    label: "On desktop, \"Show details\" in the Summary panel expands the same breakdown below the subtotal, and \"Hide details\" collapses it",
+                    href: "/cart",
+                },
+                {
+                    key: "cart-breakdown-aggregate-only",
+                    label: "The expanded breakdown shows ONE line per fee type (Shipping, WhatsApp updates, Gift wrap, Platform fee, GST…) with a \"(N stores)\" qualifier where a fee applies to several sellers — not a separate block per store",
+                    description: "Per-store detail belongs on each seller card, not in this panel. Confirm the two don't duplicate each other.",
+                    href: "/cart",
+                },
+                {
+                    key: "cart-breakdown-checked-items-only",
+                    label: "Deselecting an item lowers the breakdown's item count and every affected line; deselecting ALL of one seller's items removes that seller's shipping and add-on fees from the total entirely",
+                    description: "Use a two-seller cart. Deselect everything from seller B and confirm B's shipping leaves the breakdown and the total drops — the preview prices only what is actually being checked out.",
+                    href: "/cart",
+                },
+                {
+                    key: "cart-breakdown-no-coupon-on-locked-lanes",
+                    label: "The Won Auctions and Accepted Offers tabs show no coupon-discount line in the breakdown (those prices are already won/negotiated)",
+                    href: "/cart",
+                },
+                {
+                    key: "cart-guest-breakdown-fallback",
+                    label: "Signed out, the cart shows subtotals plus a \"Sign in to see shipping & fees\" note instead of fee lines — no error and no blank panel",
+                    href: "/cart",
+                },
+                // --- Per-store add-ons ----------------------------------------------
+                {
+                    key: "cart-store-card-fee-lines",
+                    label: "Each seller card shows that seller's own shipping and add-on fees below its items, and those per-store figures add up to the matching lines in the expanded breakdown",
+                    href: "/cart",
+                },
+                {
+                    key: "cart-addons-per-store",
+                    label: "Ticking \"WhatsApp order updates\" on ONE seller's card charges the fee once (₹10, not ₹20 on a two-seller cart) and shows it under that seller only",
+                    description: "Requires Site Settings → Fees → WhatsApp notify fee enabled. Core regression guard: the selection used to be a single cart-wide checkbox while the fee was billed per seller, so one tick charged every store in the cart.",
+                    href: "/cart",
+                },
+                {
+                    key: "cart-addons-deselected-store-excluded",
+                    label: "Deselecting all of a seller's items disables that seller's add-on checkboxes with an explanation and removes their fees from the total; re-selecting restores both",
+                    href: "/cart",
+                },
+                {
+                    key: "cart-addons-persist-to-checkout",
+                    label: "Add-ons ticked per seller in the cart are still ticked against the SAME seller at checkout, and survive a page reload",
+                    description: "Tick gift wrap for seller A only, go to checkout, confirm A's block is ticked and B's is not, then reload and confirm it holds.",
+                    href: "/checkout",
+                },
+                {
+                    key: "cart-addons-editable-at-checkout",
+                    label: "Add-ons can still be changed on the checkout page itself, per seller — important because Buy Now skips the cart entirely",
+                    description: "Use Buy Now on a product without touching the cart page, and confirm checkout still offers that seller's add-on checkboxes and that ticking one updates the Order Summary total.",
+                    href: "/checkout",
+                },
+                {
+                    key: "cart-addons-hidden-when-disabled",
+                    label: "With an add-on disabled in Site Settings → Fees, its checkbox does not appear on any seller card in the cart or at checkout",
+                    href: "/cart",
+                },
+                {
+                    key: "cart-addons-order-record",
+                    label: "After placing a multi-seller order, only the seller whose add-on was ticked has that fee on their order — the other seller's order shows no add-on fee",
+                    href: "/user/orders",
+                },
+                {
+                    key: "order-addon-icons-visible",
+                    label: "An order that included add-ons shows icon chips for them (WhatsApp updates / Gift wrap / Protected) plus the coupon code, on the buyer's order page, the seller's order detail AND the admin order drawer",
+                    description: "These are fulfilment instructions, not decoration: WhatsApp tells the notifier to message this buyer on status change, and gift wrap tells the packer to wrap the parcel. Check all three surfaces — they render from one shared component, so if one is missing something is unwired.",
+                    href: "/user/orders",
+                },
+                {
+                    key: "order-gift-message-visible-to-seller",
+                    label: "When a buyer bought gift wrap and left a message, the seller sees the full message text on the order detail — not truncated and not hidden behind a tooltip",
+                    description: "The packer has to physically write or enclose it, so it must be readable in full.",
+                    href: "/store/orders",
+                },
+                {
+                    key: "order-addons-queryable",
+                    label: "Admin can filter the orders list down to orders that opted into a given add-on (e.g. only gift-wrap orders), so \"who do I need to do this for?\" is answered from the orders list itself and not a side list",
+                    href: "/admin/orders",
+                },
+                {
+                    key: "order-coupon-shown-all-lanes",
+                    label: "A coupon applied to an order is shown on the order for every lane — standard, won-auction and accepted-offer orders alike",
+                    href: "/user/orders",
+                },
+                // --- Platform fee ----------------------------------------------------
+                {
+                    key: "platform-fee-capped",
+                    label: "The buyer's platform fee stops at the configured maximum instead of scaling with cart value",
+                    description: "With Site Settings → Fees at platform fee 5%, maximum platform fee ₹10, GST 18%: a ₹100 cart must show a ₹5.00 platform fee and ₹0.90 GST on it; a ₹700 cart must show ₹10.00 and ₹1.80 — NOT ₹35.00. Check the arithmetic, not just that a line exists.",
+                    href: "/checkout",
+                },
+                {
+                    key: "platform-fee-all-methods",
+                    label: "The platform fee is charged on every payment method — COD, UPI-manual/cash and Razorpay all include it; COD additionally shows the COD handling fee and the 10% token",
+                    description: "It used to be added only on the Razorpay path, so COD and UPI buyers were never charged it. Compare the same cart across each available method.",
+                    href: "/checkout",
+                },
+                {
+                    key: "platform-fee-charged-once",
+                    label: "A three-seller cart is charged the platform fee ONCE for the checkout, not once per seller",
+                    href: "/checkout",
+                },
+                {
+                    key: "platform-fee-sums-across-orders",
+                    label: "After placing a multi-seller order, the platform fees recorded on the resulting orders add up to exactly the single figure the cart and checkout showed — no rupee of drift",
+                    href: "/user/orders",
+                },
+                // --- The money has to agree everywhere -------------------------------
+                {
+                    key: "cart-checkout-order-totals-agree",
+                    label: "For the same cart, the expanded cart breakdown, the sum of the per-seller card fee lines, the checkout Order Summary and the created orders all show the SAME total",
+                    description: "Repeat on COD, UPI-manual and Razorpay. Acceptance test for the whole pricing change — if any two of those four disagree, something is reading a different source than it charges from.",
+                    href: "/checkout",
+                },
             ],
         },
         {
@@ -767,6 +1087,87 @@ const rawTesterChecklistItems = [
                 },
             ],
         },
+        {
+            pageKey: "reviews-pagination",
+            pageLabel: "Reviews — Pagination, Sort & Filter",
+            // "Beyblade Original Dranzer S" is the deep-review fixture: 19 approved reviews
+            // spread across all five star ratings, so it is the only product where page 2
+            // and the rating filter have anything to show.
+            href: "/products/product-beyblade-original-dranzer-s",
+            cases: [
+                {
+                    key: "detail-tab-paginates",
+                    label: "The Reviews tab on a product page shows at most 10 reviews with page controls underneath — it does NOT dump every review into one endlessly long tab",
+                    description: "Open the Dranzer S product page and click the Reviews tab. It has 19 approved reviews, so you should see 10 and a pager offering page 2. Before this change every approved review rendered at once, which is what made these pages so long.",
+                },
+                {
+                    key: "detail-tab-newest-first",
+                    label: "Reviews are ordered newest first by default (the dates run downward as you read down the list)",
+                },
+                {
+                    key: "detail-tab-page-2-differs",
+                    label: "Page 2 shows DIFFERENT reviews from page 1 — not a repeat of the same 10",
+                    description: "This is the one to be fussy about. The first page is server-rendered and handed to the browser cache; if that hand-off is wired wrong, page 2 silently re-displays page 1's reviews. Note the top review's title on page 1, go to page 2, and confirm it is not there.",
+                },
+                {
+                    key: "detail-tab-url-unchanged",
+                    label: "Paging through reviews on a product page does NOT change the page URL, and does not reload/flicker the rest of the product page (gallery, price, Add to Cart all stay put)",
+                    description: "Deliberate: on a detail page the review pager keeps its state in the component, because writing it to the URL would re-run the whole product page just to turn a page of reviews.",
+                },
+                {
+                    key: "detail-tab-sort",
+                    label: "The sort dropdown in the Reviews tab works — Newest / Oldest / Highest rated / Lowest rated each reorder the list correctly",
+                },
+                {
+                    key: "detail-tab-rating-filter",
+                    label: "Filtering by star rating in the Reviews tab works — picking 5★ shows only 5-star reviews, and the result count/pager updates to match",
+                    description: "Open the Filters drawer in the Reviews tab. The fixture has reviews at every star level from 1 to 5. If this shows an error or an empty list for every rating, the Firestore index for it has not been deployed yet — report that.",
+                },
+                {
+                    key: "detail-tab-summary-stable",
+                    label: "The average rating and total review count above the list describe ALL reviews — they do not shrink when you apply a rating filter",
+                    description: "Note the \"x.x / 5 · N reviews\" line, then filter to 5★ only. The list shortens but that summary line should stay the same, because it describes the product overall, not the current filter.",
+                },
+                {
+                    key: "detail-tab-filters-all-work",
+                    label: "Every control shown in the Reviews tab's Filters drawer actually does something — there is no filter you can set that changes nothing",
+                    description: "A filter that renders but is never applied looks broken to a buyer. Set each control in turn and confirm the list responds.",
+                },
+                {
+                    key: "date-range-sort-options",
+                    label: "While a review date range is set, the sort dropdown offers only the date-based sorts — and choosing a date range never produces an error page",
+                    description: "Set a From/To date in the Filters drawer. \"Highest rated\"/\"Lowest rated\" are withdrawn on purpose while a date range is active — the database cannot serve that combination, so it is hidden rather than allowed to fail.",
+                },
+                {
+                    key: "other-listing-types-paginate",
+                    label: "The Reviews tab paginates the same way on a digital-code and a live-item page, not just standard products",
+                    href: "/digital-codes/digitalcode-beyblade-x-app-unlock",
+                },
+                {
+                    key: "auction-store-reviews-paginated",
+                    label: "An auction page's \"Store Reviews\" section is paginated and genuinely newest-first — not a fixed block of 10 with no way to see more",
+                    description: "Previously this section showed exactly 10 reviews with no pager, and they were grouped by product rather than ordered by date, so the \"latest\" reviews were not actually the latest. Scroll to Store Reviews on this auction and confirm you can page through and that the dates run downward.",
+                    href: "/auctions/auction-beyblade-original-dragoon-storm",
+                },
+                {
+                    key: "store-reviews-tab-url-state",
+                    label: "On the store's own Reviews tab (a full page, not a tab inside a product), the page number and sort DO appear in the URL and survive a browser refresh / can be shared as a link",
+                    description: "Open the store below and click its Reviews tab. The opposite of the product-page behaviour above, and intentional: this is a page in its own right, so its state belongs in the URL. Go to page 2, refresh, and confirm you are still on page 2.",
+                    href: "/stores/store-beyblade-arena",
+                },
+                {
+                    key: "reviews-index-unchanged",
+                    label: "The site-wide /reviews page still works exactly as before — search, sort, filters, paging, and grid/list toggle",
+                    description: "This page was rebuilt on shared internals during the pagination work, so it is worth a regression pass even though nothing about it was meant to change.",
+                    href: "/reviews",
+                },
+                {
+                    key: "empty-state",
+                    label: "A product with no reviews yet shows \"No reviews yet — be the first to review this product.\" and no pager, rather than an empty box or a stray page control",
+                    href: "/products/product-beyblade-x-dran-sword-video-demo",
+                },
+            ],
+        },
         {
             pageKey: "messaging",
             pageLabel: "Messaging a Seller",
@@ -868,12 +1269,49 @@ const rawTesterChecklistItems = [
                 { key: "seller-quick-add-drawer-flips", label: "With Left-hand mode ON, the seller's quick-add-listing side drawer opens from the left instead of the right" },
             ],
         },
+        {
+            pageKey: "seller-bids-bundles-filters",
+            pageLabel: "Seller — Bids & Bundles Filtering",
+            href: "/store/bids",
+            cases: [
+                {
+                    key: "seller-bids-status-filter",
+                    label: "The status filter on the seller Bids page actually narrows the list",
+                    description: "Fixed 2026-08-21. The status chips, the sort dropdown AND the bidder search box on this page were all inert — the server read none of the three, so every control silently returned the same unfiltered list. Pick a status and confirm the rows genuinely change.",
+                    href: "/store/bids",
+                },
+                {
+                    key: "seller-bids-sort-dropdown",
+                    label: "Changing the Sort dropdown on the seller Bids page reorders the rows",
+                    description: "The sort was hardcoded to bid date server-side regardless of what the dropdown said. Switch to a different sort (e.g. bid amount) and confirm the ordering visibly changes.",
+                    href: "/store/bids",
+                },
+                {
+                    key: "seller-bids-bidder-search",
+                    label: "Typing a bidder's name into the search box on the seller Bids page and pressing Enter narrows the list to that bidder",
+                    description: "Search matches from the START of the bidder name (a database limitation — mid-name fragments will not match), so type the first part of the name rather than a middle fragment.",
+                    href: "/store/bids",
+                },
+                {
+                    key: "seller-bundles-active-filter",
+                    label: "The Active / Inactive and \"Sold out\" chips on the seller Bundles page actually narrow the list",
+                    description: "Fixed 2026-08-21 — these chips existed and were clickable but the seller endpoint ignored them entirely, unlike the admin Bundles page which honoured the same chips. Compare the two pages: they should now behave identically.",
+                    href: "/store/bundles",
+                },
+            ],
+        },
         {
             pageKey: "seller-orders",
             pageLabel: "Seller Order Management & Shipping/Tracking",
             href: "/store/orders",
             cases: [
                 { key: "view-orders", label: "Seller order list shows accurate incoming orders", href: "/store/orders" },
+                {
+                    key: "seller-auction-forfeit-notification",
+                    label: "When a winning bidder fails to pay by the deadline, the SELLER also receives a notification that the win was forfeited and the item is unsold",
+                    description: "Added 2026-08-21. Only the buyer was told, so to a seller a forfeited win looked like a completed sale that simply never paid out. Check the seller's notification bell after an auction win lapses — the message should say the item can be relisted or offered to the next highest bidder.",
+                    href: "/store/orders",
+                },
                 {
                     key: "seller-order-manual-payment-badge",
                     label: "A manual-payment (UPI/Cash) order's seller detail shows a payment badge — Awaiting payment / Awaiting verification / Verified / Re-upload requested / Rejected — next to the Payment heading, plus the UTR once the buyer submits one",
@@ -892,6 +1330,12 @@ const rawTesterChecklistItems = [
                     description: "Added 2026-08-21 — sellers previously had no dedicated order-detail page, only a drawer, unlike buyer/admin. The drawer and the new page now share one content component (SellerOrderDetailPanel) so they can't drift.",
                     href: "/store/orders",
                 },
+                {
+                    key: "seller-new-order-notification-reaches-seller",
+                    label: "A seller is actually told when an order lands — in-app AND by email — without having to sit refreshing the orders page",
+                    description: "Added 2026-08-21. Place an order against your store from a separate buyer account, then check the seller side WITHOUT opening /store/orders first: does the notification bell update, and does an email reach the seller account's inbox? A marketplace where sellers only discover orders by polling the dashboard is a real (and easily-missed) failure. Also confirm the notification/email names the buyer's item and links straight to that order.",
+                    href: "/store/orders",
+                },
             ],
         },
         {
@@ -928,6 +1372,24 @@ const rawTesterChecklistItems = [
             pageLabel: "Seller — All Listing Types (Coupons, Bundles, Classifieds, Digital Codes, Live, Prize Draws, Art, Stickers)",
             href: "/store/products",
             cases: [
+                {
+                    key: "seller-listing-type-dropdown-all-types",
+                    label: "The \"Listing type\" dropdown on the seller Products page offers all nine types including Art and Stickers, and no longer offers \"Bundle\"",
+                    description: "Fixed 2026-08-21 — the dropdown was a hand-written list missing art and stickers, and still offered \"Bundle\", which is a category type rather than a listing type and therefore always returned zero rows. Open the dropdown and check every option returns results for a store that has that type.",
+                    href: "/store/products",
+                },
+                {
+                    key: "seller-products-badge-per-type",
+                    label: "Each row in the seller Products list shows a badge naming its real listing type — a classified row says \"classified\", a sticker row says \"stickers\", and so on",
+                    description: "Fixed 2026-08-21 — the row mapper collapsed classified, digital-code, live, art and stickers all down to \"standard\", so five of the nine types were mislabelled in the table. Create or find one listing of each type and confirm each badge is correct.",
+                    href: "/store/products",
+                },
+                {
+                    key: "seller-products-featured-promoted-sorts",
+                    label: "The seller Products \"Featured first\" and \"Promoted first\" sorts actually reorder the list",
+                    description: "Same fix as the admin equivalent — both sorts previously did nothing at all. Confirm the order genuinely changes.",
+                    href: "/store/products",
+                },
                 { key: "seller-coupons-crud", label: "Seller can create, edit, and list their own coupons", href: "/store/coupons" },
                 {
                     key: "seller-coupon-auto-scoped-to-own-store",
@@ -1009,6 +1471,12 @@ const rawTesterChecklistItems = [
                 { key: "seller-features-crud", label: "Seller can create and edit product features", href: "/store/features" },
                 { key: "seller-google-reviews-sync", label: "Google Reviews sync pulls in real reviews correctly", href: "/store/google-reviews" },
                 { key: "seller-whatsapp-catalog", label: "WhatsApp catalog import/push works", href: "/store/whatsapp" },
+                {
+                    key: "seller-whatsapp-token-save",
+                    label: "Saving a WhatsApp access token on the store succeeds and comes back masked — it must not error out",
+                    description: "Added 2026-08-21. The store's WhatsApp access token is encrypted before storage by the same mechanism as the admin Integrations keys, and that mechanism was failing in production — so this save path was broken too, in a place nobody would think to check. Enter a throwaway token value, save, reload the page, and confirm you got a success toast and the field shows a masked value rather than an error or a blank field.",
+                    href: "/store/whatsapp",
+                },
                 { key: "seller-reviews-response", label: "Seller can view and respond to product reviews", href: "/store/reviews" },
             ],
         },
@@ -1131,6 +1599,24 @@ const rawTesterChecklistItems = [
                 { key: "notification-channel-prefs", label: "Per-channel notification preferences (in-app / email / WhatsApp) save and are respected" },
                 { key: "notification-type-sample", label: "A sample of notification types (order status change, bid outbid, message received, payout) each trigger correctly end-to-end" },
                 { key: "notification-tab-filters", label: "Notification tab filters correctly narrow the list", href: "/user/notifications" },
+                {
+                    key: "notification-email-actually-arrives",
+                    label: "With email enabled for a notification type, the email really lands in your inbox — and comes from the site's configured sender name and address",
+                    description: "Added 2026-08-21. Existing cases only checked that the preference SAVES and that the in-app notification appears; nobody ever checked the email itself leaves the building. Turn email on for one notification type, trigger that event for real (e.g. have a seller mark your order shipped), then open the actual inbox for the address on your account. Confirm: (a) an email arrives within a few minutes; (b) the From name and address match what Site Settings → Notifications is configured with, not a stranger's domain or a bare no-reply; (c) it landed in the inbox, not spam; (d) the links inside it open the right page on the live site and don't 404.",
+                    href: "/user/notifications",
+                },
+                {
+                    key: "notification-email-opt-out-respected",
+                    label: "Turning email OFF for a notification type stops the emails but still shows the in-app notification",
+                    description: "Added 2026-08-21. The two channels are meant to be independent — opting out of email must never silently opt you out of the in-app bell too. Turn email off for a type you can trigger on demand, trigger it, then confirm: no new email arrives, but the notification still appears in /user/notifications. Then turn it back on, trigger again, and confirm the email resumes — an opt-out that can't be reversed is just as much a bug.",
+                    href: "/user/notifications",
+                },
+                {
+                    key: "notification-links-to-right-entity",
+                    label: "Clicking a notification opens the exact order / bid / message it refers to — not a generic list page",
+                    description: "Added 2026-08-21. Click through several different notification types and confirm each one lands on the specific record it names. A notification that says \"Your order was shipped\" must open THAT order, not /user/orders. Also confirm nothing dead-ends on a 404 or an \"unauthorized\" page.",
+                    href: "/user/notifications",
+                },
             ],
         },
         {
@@ -1184,6 +1670,17 @@ const rawTesterChecklistItems = [
                 { key: "error-states", label: "Error states (404, form validation) look correct" },
                 { key: "card-row-heights-aligned", label: "Product/auction/pre-order/event cards in the same row are the same height, with their action button (Reserve now, Place bid, View details, etc.) aligned along a common bottom edge even when one card's description is longer than another's" },
                 { key: "image-watermark-subtle", label: "Product and listing images show a small, subtle watermark (not oversized or fully opaque, doesn't obscure the image)" },
+                {
+                    key: "clickable-image-tiles-not-blank",
+                    label: "Every CLICKABLE image tile across the site shows its picture, not an empty box — check all six surfaces listed below",
+                    description: "Fixed 2026-08-21. All of these are the same shape (a small image inside a clickable tile) and all broke together, so they must be re-checked together: (1) the mini thumbnail strip under a product's main gallery image; (2) the \"Photos (N)\" grid on a review detail page, AND the thumbnail strip along the bottom of that page's photo lightbox; (3) the image thumbnails inside a review popup/modal; (4) the tile grid on a prize-draw's collage of prizes; (5) the tile grid on a bundle's collage of included items; (6) the \"choose an existing file\" grid in the media picker when adding an image as a seller/admin. In every case the picture itself must be visible — a bordered but empty square is a fail.",
+                    href: "/products/product-beyblade-burst-valkyrie",
+                },
+                {
+                    key: "icon-button-label-spacing",
+                    label: "Buttons that show an icon next to their text have a normal gap between the icon and the word — the two are not jammed together",
+                    description: "Same 2026-08-21 fix as the blank image tiles: the button's spacing setting had stopped reaching its contents, so icon+label buttons were rendering with no gap at all. Scan a few pages with icon buttons (product detail actions, dashboard toolbars, the cart) and confirm the spacing looks deliberate rather than cramped.",
+                },
                 { key: "section-cta-buttons-visible", label: "Homepage section \"View all →\" / \"Go to…\" buttons use a solid primary-colored fill so they're clearly identifiable as clickable CTAs, not a plain white/outline box that blends into the page" },
                 {
                     key: "mobile-search-bar-proportions",
@@ -1192,6 +1689,197 @@ const rawTesterChecklistItems = [
                 },
             ],
         },
+        {
+            pageKey: "sticky-cta-bar",
+            pageLabel: "Sticky Buy/Bid Bar on Scroll",
+            href: "/products/product-beyblade-original-dranzer-s",
+            cases: [
+                {
+                    key: "desktop-hidden-at-top",
+                    label: "ON DESKTOP: when a product page first loads, there is NO floating bar across the bottom of the window — the page looks exactly as it always has",
+                    description: "Use a full-size browser window (not a phone or a narrow window). The bar is meant to stay out of the way while the real Add to Cart / Buy Now buttons are still visible on screen.",
+                },
+                {
+                    key: "desktop-appears-on-scroll",
+                    label: "ON DESKTOP: after scrolling down past the product images and buy buttons, a bar slides up from the bottom of the window with the price and the same Add to Cart / Buy Now actions",
+                    description: "This is the whole point of the change: on a long page the buy buttons used to scroll away with no way back except scrolling up.",
+                },
+                {
+                    key: "desktop-hides-scrolling-back-up",
+                    label: "ON DESKTOP: scrolling back to the top of the page slides the bar away again",
+                },
+                {
+                    key: "desktop-buttons-work",
+                    label: "ON DESKTOP: the buttons in the floating bar actually work — Add to Cart adds the item, Buy Now starts checkout, and the wishlist button saves it",
+                    description: "They should behave identically to the buttons in the main product panel, including going disabled for an out-of-stock item.",
+                },
+                {
+                    key: "desktop-not-covering-footer",
+                    label: "ON DESKTOP: scrolling to the very bottom of the page, the floating bar does not permanently cover the footer — you can still read and click footer links",
+                },
+                {
+                    key: "mobile-unchanged",
+                    label: "ON MOBILE: the bottom action bar behaves exactly as it did before — visible while you browse the product, sitting above the bottom navigation, not overlapping it",
+                    description: "Regression check. Nothing about the phone experience was supposed to change; only desktop gained the bar.",
+                },
+                {
+                    key: "auction-countdown-in-bar",
+                    label: "On an auction page the sticky bar shows the live countdown (\"Ends in …\"), the current bid and bid count, and its Place Bid button jumps to the bidding form",
+                    description: "The countdown should tick, not sit frozen.",
+                    href: "/auctions/auction-beyblade-original-dragoon-storm",
+                },
+                {
+                    key: "ended-auction-no-bar",
+                    label: "An auction that has already ended shows NO sticky bar at all — there is nothing left to bid on",
+                    href: "/auctions/auction-tester-sandbox-won",
+                },
+                {
+                    key: "preorder-bar",
+                    label: "A pre-order page's sticky bar says Reserve Now and shows the price, and the button jumps to the reserve panel",
+                    href: "/pre-orders/preorder-tester-sandbox-1",
+                },
+                {
+                    key: "prize-draw-bar-label",
+                    label: "A prize-draw page's sticky bar CTA reads \"Enter Draw\" (not \"Buy Now\") and the info line shows the price per entry",
+                    description: "Label changed on purpose — you are entering a draw, not buying a specific item. Flag it if \"Buy Now\" still appears.",
+                    href: "/prize-draws/prizedraw-tester-sandbox-1",
+                },
+                {
+                    key: "closed-prize-draw-no-bar",
+                    label: "A closed prize draw shows NO sticky bar",
+                    href: "/prize-draws/prizedraw-tester-sandbox-closed",
+                },
+                {
+                    key: "classified-bar-no-cart",
+                    label: "A classified listing's sticky bar offers \"Make an Offer\" and does NOT offer Add to Cart or Buy Now — classifieds are arranged directly with the seller",
+                    description: "Tapping it should jump to the contact-seller panel. An Add to Cart button appearing here is a real bug.",
+                    href: "/classified/classified-tester-sandbox-1",
+                },
+                {
+                    key: "digital-code-bar",
+                    label: "A digital-code listing has a sticky Buy Now bar, and a sold-out one has no bar at all",
+                    href: "/digital-codes/digitalcode-tester-sandbox-1",
+                },
+                {
+                    key: "live-item-bar",
+                    label: "A live-item listing has a sticky Buy Now bar that jumps to its buy panel",
+                    href: "/live/live-tester-sandbox-1",
+                },
+                {
+                    key: "bar-not-overlapping-content",
+                    label: "On every page above, nothing at the bottom of the page is left permanently hidden behind the sticky bar — you can always scroll far enough to read the last line of content",
+                },
+                {
+                    key: "no-bar-on-non-listing-pages",
+                    label: "Pages that never had a bottom bar still do not have one — homepage, blog posts, FAQ, and the site-wide listing pages show no floating buy bar on desktop",
+                    description: "The bar is opt-in per page; a stray one on the homepage would be a bug.",
+                    href: "/",
+                },
+                {
+                    key: "bar-with-keyboard-open",
+                    label: "ON MOBILE: opening the on-screen keyboard (e.g. tapping a bid amount or search field) does not leave the sticky bar floating in the middle of the screen or hidden behind the keyboard",
+                },
+            ],
+        },
+        {
+            pageKey: "status-badge-legibility",
+            pageLabel: "Listing Tags & Status Chips — Light vs Dark Mode",
+            href: "/products",
+            cases: [
+                {
+                    key: "listing-type-tags-readable-light",
+                    label: "IN LIGHT MODE: on the main Products grid, every listing-type tag on a card — Auction, Pre-Order, Live Item, Digital Code, Prize Draw, Classified, Art Print, Sticker Sheet — is clearly readable, with a solid colored pill behind dark-enough text",
+                    description: "This is the headline fix for 2026-08-21. Reported as \"the auction tag / live tag is white text on a white pill, or a faint grey you cannot read.\" Switch the site to LIGHT mode first (theme toggle in the header) — the bug only appeared there. Read every tag out loud; a tag you have to squint at, tilt the screen for, or that shows text with no pill behind it at all, is still a bug.",
+                    href: "/products",
+                },
+                {
+                    key: "listing-type-tags-readable-dark",
+                    label: "IN DARK MODE: the same listing-type tags on the Products grid are still clearly readable — fixing light mode must not have broken dark mode",
+                    description: "Regression check, and a real risk here: the two modes use inverted color tokens, so it is genuinely possible to fix one and break the other. Toggle between light and dark a few times on the same page and confirm every tag survives both.",
+                    href: "/products",
+                },
+                {
+                    key: "live-item-tag-has-background",
+                    label: "The \"Live Item\" tag has an actual colored pill behind it — not bare red text floating directly on the product photo with no background",
+                    description: "This tag was a separate bug from the others: its background color name did not exist at all, so the browser threw the style away and rendered nothing behind the text. Easiest to spot on a card whose photo is busy or light-colored.",
+                    href: "/live",
+                },
+                {
+                    key: "promo-badges-readable",
+                    label: "IN LIGHT MODE: the small promotional badges on product cards — NEW, SALE, LIMITED, the bundle discount percentage, an auction's \"Ending soon\" / \"Reserve\" pill — are all readable against their colored background",
+                    href: "/products",
+                },
+                {
+                    key: "notification-count-bubbles-readable",
+                    label: "The unread-count bubbles (the small number circles on the header bell icon, the Messages nav item, and the cart/bottom action bar) show a readable number in BOTH light and dark mode — not a colored blob with an invisible digit",
+                    description: "You need at least one unread notification or message for the bubble to appear. Check both themes.",
+                    href: "/user/messages",
+                },
+                {
+                    key: "admin-status-chips-colored",
+                    label: "Admin and seller listing pages show status chips (Pending / Verified / Resolved / High priority / Featured / Sale, etc.) as genuinely COLORED pills — amber for pending, green for success, red for problems — not plain uncolored text",
+                    description: "Found 2026-08-21: a configuration gap meant every one of these colored chips authored inside the shared component library compiled to no CSS at all, so they had silently always rendered as plain unstyled text. Spot-check across a few pages: /admin/support-tickets, /admin/scammers, /admin/orders, /store/orders.",
+                    href: "/admin/support-tickets",
+                },
+                {
+                    key: "faq-helpful-buttons-readable",
+                    label: "On a FAQ, after clicking Yes or No on \"Was this helpful?\", the button you picked stays readable in BOTH light and dark mode — the selected button is a solid color with legible text, not white-on-pale",
+                    href: "/faqs",
+                },
+                {
+                    key: "detail-page-tags-readable",
+                    label: "Opening an individual auction, pre-order, prize draw, classified, digital code and live-item page, each one's type tag and status chips are readable in light mode",
+                    description: "Card grids and detail pages don't always share the same component, so check both. Use the sandbox listings linked from the Tester Hub if you need one of each type.",
+                    href: "/auctions/auction-beyblade-original-dragoon-storm",
+                },
+                {
+                    key: "whatsapp-community-member-pill",
+                    label: "IN LIGHT MODE: on the homepage's green WhatsApp community card, the member-count pill in its top-right corner (e.g. \"5,000+ members\") is readable — white text on a translucent darker pill, not white text on a white pill",
+                    description: "Reported alongside the tag bug: this pill was invisible in light mode. The people icon next to the number should be visible too.",
+                    href: "/",
+                },
+                {
+                    key: "image-lightbox-close-hover",
+                    label: "Opening a product image in the full-screen lightbox and hovering the X close button, the X stays visible as the button turns red — it does not vanish on hover",
+                    href: "/products/product-beyblade-original-dranzer-s",
+                },
+            ],
+        },
+        {
+            pageKey: "back-to-top-button",
+            pageLabel: "Back-to-Top Button",
+            href: "/products",
+            cases: [
+                {
+                    key: "appears-and-clickable-on-long-page",
+                    label: "Scrolling down a long listing page, the floating back-to-top arrow appears in the bottom corner AND actually responds to a click — it is not sitting behind the bottom navigation bar, a sticky toolbar, or a buy bar",
+                    description: "Fixed 2026-08-21 — it previously shared a stacking level with the bottom navigation bar, so on many pages it was either partly covered or completely unclickable. Try it on a page that also has a sticky bottom bar (a product page scrolled down) — that is where it used to fail.",
+                    href: "/products",
+                },
+                {
+                    key: "above-sticky-buy-bar",
+                    label: "On a product page scrolled far enough for BOTH the sticky buy bar and the back-to-top arrow to be showing, the arrow sits above/clear of the buy bar rather than being hidden underneath it",
+                    href: "/products/product-beyblade-original-dranzer-s",
+                },
+                {
+                    key: "scrolls-to-top",
+                    label: "Clicking the back-to-top arrow smoothly scrolls the page back to the very top",
+                    href: "/products",
+                },
+                {
+                    key: "dismiss-returns-on-navigation",
+                    label: "Clicking the small X next to the back-to-top arrow hides it for the current page, and navigating to a different page brings it back",
+                    description: "Regression check on an older fix — dismissing it must not hide it for the rest of the browsing session.",
+                    href: "/products",
+                },
+                {
+                    key: "not-covering-toast-or-modal-actions",
+                    label: "The back-to-top arrow does not cover anything you need to click — check that a toast message, an open confirmation dialog's buttons, and the footer's bottom-right links are all still fully clickable while it is on screen",
+                    description: "It was deliberately raised to the frontmost layer, so this is the specific risk that change introduces. It should only ever float in the empty corner gutter.",
+                    href: "/products",
+                },
+            ],
+        },
         {
             pageKey: "form-validation-errors",
             pageLabel: "Form Validation & Error Summary",
@@ -1281,6 +1969,27 @@ const rawTesterChecklistItems = [
                     description: "Added 2026-08-20 — GITHUB was a new socialUrls key with no footer icon before this. Confirm the icon renders (not a broken/missing glyph) and the link target is a real, working github.com profile, not a placeholder or dead link.",
                     href: "/",
                 },
+                {
+                    key: "footer-text-weight-readable",
+                    label: "Footer text is comfortably readable, not thin and washed out — the link lists, the brand description paragraph, the copyright line and the small sitemap/legal links at the very bottom all render in a slightly heavier weight than plain body text",
+                    description: "Changed 2026-08-21 — the footer's greyed text was previously at the lightest weight, which made it hard to read against the page background, especially on a laptop screen at an angle. Compare the footer against the same grey text elsewhere on the page; the footer should read as more solid, without looking bold.",
+                    href: "/",
+                },
+                {
+                    key: "footer-column-headings-stand-out",
+                    label: "On DESKTOP, each footer link column's heading (Shop, Company, Support, etc.) clearly stands out as a heading above its list of links, rather than looking like just another link in the list",
+                    href: "/",
+                },
+                {
+                    key: "footer-weight-both-themes",
+                    label: "The footer text weight change looks right in BOTH light and dark mode — heavier but not bold, and it never turns into an unreadable smudge in dark mode",
+                    href: "/",
+                },
+                {
+                    key: "footer-mobile-accordions",
+                    label: "ON MOBILE, the footer's collapsible link sections still open and close correctly, and their links are as readable as the desktop columns",
+                    href: "/",
+                },
             ],
         },
         {
@@ -1393,6 +2102,12 @@ const rawTesterChecklistItems = [
             href: "/",
             cases: [
                 { key: "homepage-loads", label: "The homepage loads without errors on both desktop and mobile", href: "/" },
+                {
+                    key: "whatsapp-community-link-real",
+                    label: "The \"Join the Community\" WhatsApp button on the homepage opens the real LetItRip WhatsApp group, not a dead link",
+                    description: "Fixed 2026-08-21 — the seeded link was a placeholder that was never a valid WhatsApp invite code, so the button opened a page that could not resolve to any group. Tap it on a device with WhatsApp installed and confirm it offers to join an actual group. The Contact page's WhatsApp link must open the same group.",
+                    href: "/",
+                },
                 { key: "about-us-in-main-nav", label: "\"About Us\" appears as an item in the main public top navigation, not just the footer", href: "/about" },
                 {
                     key: "about-team-real-founder",
@@ -1444,12 +2159,64 @@ const rawTesterChecklistItems = [
             cases: [
                 { key: "store-directory", label: "The store directory page loads correctly", href: "/stores" },
                 { key: "store-detail-tabs", label: "A store detail page's listing-type dropdown (Products/Auctions/Pre-Orders/Prize Draws/Bundles/Classifieds/Digital Codes/Live Items/Art & Stickers) switches correctly between listing types, and the separate Coupons/Reviews/About tabs next to it all load correctly", description: "The listing-type dropdown is always a dropdown (not just on narrow/mobile widths, unlike category/brand/product/event tabs) since a store can have up to 9 listing types — Coupons, Reviews, and About stay as standalone tabs beside it, never folded into the dropdown." },
+                {
+                    key: "category-tabs-every-type-renders",
+                    label: "On a category page, EVERY listing-type tab that is offered renders real content when opened — none show a blank panel",
+                    description: "Fixed 2026-08-21 — the Classifieds, Digital Codes, Live Items and Art & Stickers tabs were clickable but had no content behind them, so selecting one highlighted the tab and showed nothing at all. Open every tab the page offers, one by one.",
+                    href: "/categories/category-beyblade-burst",
+                },
+                {
+                    key: "brand-tabs-every-type-offered",
+                    label: "A brand page offers the same listing-type tabs a category page does (minus Stores) — Classifieds, Digital Codes, Live Items and Art & Stickers are not silently missing",
+                    description: "Fixed 2026-08-21 — the brand page dropped those four tabs entirely rather than rendering them, so those listing types were unreachable from any brand. Compare the tab row on a brand page against the same brand's category page.",
+                    href: "/brands/brand-beyblade",
+                },
+                {
+                    key: "category-brand-tab-counts-match",
+                    label: "Each category/brand tab's count badge matches the number of items the tab actually shows",
+                    href: "/categories/category-beyblade-burst",
+                },
                 {
                     key: "empty-tabs-hidden",
                     label: "A store/category/brand detail page never shows a tab for a listing type it has zero items of — e.g. a store with no products doesn't show a \"Products\" tab at all, not an empty products page",
                     description: "Fixed 2026-08-20 — tab visibility now checks the already-fetched per-type count and omits the tab entirely when it's zero, instead of always rendering all tabs regardless of whether they'd show anything. \"About\" always stays visible on store pages (no item-count concept). Verify on a real store/category/brand that's genuinely missing at least one listing type.",
                     href: "/stores",
                 },
+                {
+                    key: "store-art-stickers-tab-shows-items",
+                    label: "A store's \"Art & Stickers\" tab opens a real page with art and sticker items on it — not an empty grid or a page full of ordinary products",
+                    description: "Fixed 2026-08-21 — the tab showed a genuine non-zero count but linked to the store's Products tab, which filters to standard products only, so it always landed on a page containing none of the items it had just counted. It now has its own /stores/{slug}/art page.",
+                    href: "/stores/store-beyblade-arena/art",
+                },
+                {
+                    key: "store-tab-counts-match-contents",
+                    label: "Every store tab's count badge matches what the tab actually contains — open each of Products, Auctions, Pre-Orders, Prize Draws, Classifieds, Digital Codes, Live Items, Art & Stickers and Bundles in turn",
+                    description: "A tab showing \"5\" and then rendering an empty grid (or somebody else's items) is the bug class this checks for. Any mismatch is a failure.",
+                    href: "/stores/store-beyblade-arena",
+                },
+                {
+                    key: "store-tab-sort-survives-reload",
+                    label: "Changing the sort on a store tab and reloading the page keeps that sort applied — the first paint matches what the Sort dropdown shows",
+                    description: "Fixed 2026-08-21 — store tab pages ignored the URL when rendering server-side, so a reload always painted page 1 in the default order while the toolbar still displayed the sort you had picked. Set a non-default sort, reload, and confirm the item order matches the dropdown.",
+                    href: "/stores/store-beyblade-arena/auctions",
+                },
+                {
+                    key: "store-preorders-tab-default-sort",
+                    label: "A store's Pre-Orders tab opens in the same default order as the public /pre-orders page (earliest delivery first)",
+                    description: "Fixed 2026-08-21 — the store tab had its own drifted copy of the sort list and opened Newest-first while /pre-orders opened Earliest-Delivery-first for the same items. Compare the two side by side; the first item should match.",
+                    href: "/stores/store-beyblade-arena/pre-orders",
+                },
+                {
+                    key: "store-classified-live-facets-filter",
+                    label: "The type-specific filters on a store's Classifieds and Live Items tabs actually narrow the results (city / negotiable / accepts shipping, and species / sex / jurisdiction)",
+                    description: "Fixed 2026-08-21 — these were rendered and counted toward the Filters badge but never sent to the server, so they changed nothing. Apply one and confirm the grid genuinely shrinks.",
+                    href: "/stores/store-beyblade-arena/classified",
+                },
+                {
+                    key: "store-tab-empty-state-not-error",
+                    label: "A store tab with genuinely no items shows a friendly empty state — never a blank white area, a spinner that never stops, or an error toast about a missing index",
+                    href: "/stores/store-tester-qa-seller",
+                },
                 { key: "sellers-directory", label: "The sellers directory page loads correctly", href: "/sellers" },
                 { key: "seller-detail-page", label: "An individual seller's public detail page loads correctly" },
                 { key: "scams-registry", label: "The scams registry page and an individual scam detail page load correctly", href: "/scams" },
@@ -1531,6 +2298,48 @@ const rawTesterChecklistItems = [
                     description: "Verify against the seeded \"Test Inactive Category\" fixture (isActive:false) — it should only appear when the Active filter is switched to show inactive categories.",
                     href: "/admin/categories",
                 },
+                {
+                    key: "admin-products-type-chips-all-types",
+                    label: "The admin Products \"Type\" filter lists all nine listing types including Art and Stickers, and does NOT offer \"Bundles\"",
+                    description: "Fixed 2026-08-21 — the chips used display labels as the underlying filter values, and had no entry at all for art or stickers, so admin could never filter to either. Bundles are a category type, not a listing type; a Bundles chip here would always return zero rows.",
+                    href: "/admin/products",
+                },
+                {
+                    key: "admin-products-type-chips-multi-select",
+                    label: "The admin Products \"Type\" chips are multi-select — ticking Auctions AND Prize Draws lists both, and every single chip on its own returns rows (never zero)",
+                    description: "Tick each of the nine chips one at a time and confirm each returns results (given seeded data exists for that type). A chip that always returns nothing means its value no longer matches what the database stores.",
+                    href: "/admin/products",
+                },
+                {
+                    key: "admin-products-featured-promoted-sorts",
+                    label: "The admin Products \"Featured first\" and \"Promoted first\" sorts actually reorder the list — featured/promoted items move to the top",
+                    description: "Fixed 2026-08-21 — both options existed in the code but targeted fields that were not sortable, so the sort was silently discarded and the list never changed order. Toggle a couple of items' Featured flags first so there is something to sort, then pick the sort and confirm they rise to the top.",
+                    href: "/admin/products",
+                },
+                {
+                    key: "admin-per-type-pages-have-filters",
+                    label: "The admin Art, Stickers, Classified, Digital Codes and Live Items pages each have a working Status filter and a sort dropdown, and clicking a row opens the product editor",
+                    description: "Fixed 2026-08-21 — all five pages were near-identical copies with no filter drawer at all. They now share one config. Check each page: a Status filter exists, sorting works, and a row click lands on the real product edit page.",
+                    href: "/admin/art",
+                },
+                {
+                    key: "admin-listing-reset-restores-defaults",
+                    label: "The \"Reset\" button on an admin listing returns it to exactly what a fresh page load shows — not to a wider, unfiltered list",
+                    description: "Fixed 2026-08-21 — Reset cleared every filter to empty instead of restoring each view's configured default, so Reset could show MORE rows than opening the page fresh. Compare: load the page, note the row count, apply some filters, hit Reset, and the count should return to the original.",
+                    href: "/admin/tester-checklist",
+                },
+                {
+                    key: "admin-address-payment-status-chips-in-url",
+                    label: "The status chips on Admin > Addresses and Admin > Payment Methods are reflected in the URL and survive a reload and the Back button",
+                    description: "Fixed 2026-08-21 — these chips were held in local component state only, so the selection vanished on reload, could not be shared as a link, and the browser Back button skipped past it. Pick a status, reload, and confirm it is still selected.",
+                    href: "/admin/addresses",
+                },
+                {
+                    key: "admin-listing-sort-dropdown-preselected",
+                    label: "Every admin listing opens with its Sort dropdown showing a selected option — never blank",
+                    description: "Fixed 2026-08-21 on Addresses and Payment Methods, whose default sort was not among the options they offered, so the dropdown opened with nothing selected. Spot-check several admin listings.",
+                    href: "/admin/addresses",
+                },
                 { key: "sublisting-categories-crud", label: "Admin can create, edit, and list sublisting categories", href: "/admin/sublisting-categories" },
                 { key: "carousel-crud", label: "Admin can create, edit, and reorder carousel slides", href: "/admin/carousel" },
                 { key: "sections-crud", label: "Admin can create, edit, and reorder homepage sections", href: "/admin/sections" },
@@ -1653,6 +2462,18 @@ const rawTesterChecklistItems = [
             href: "/admin/orders",
             cases: [
                 { key: "orders-status-change", label: "Admin orders list shows accurate orders and status changes save correctly", href: "/admin/orders" },
+                {
+                    key: "admin-emi-order-reviewable",
+                    label: "Opening an EMI order in admin shows the full Payment Proof panel — screenshot, UTR, expected-vs-reported UPI, and the Verify / Request re-upload / Reject-as-fraud buttons",
+                    description: "Fixed 2026-08-21. The panel used to check only for cash and UPI orders and omitted EMI entirely, so an admin could see an EMI order sitting in the queue labelled \"Awaiting verification\" and have literally no way to action it. Check BOTH the row drawer and the full /admin/orders/[id]/view page — they must behave identically.",
+                    href: "/admin/orders",
+                },
+                {
+                    key: "admin-decided-order-no-live-buttons",
+                    label: "An order already rejected as fraud, or already sent back for re-upload, shows that state instead of offering live Verify / Reject buttons again",
+                    description: "Previously only the payment status was consulted, so a decided order still rendered as a fresh \"please verify\" and could be actioned a second time. Reject one order as fraud, reopen it, and confirm it now reads as rejected with no action buttons.",
+                    href: "/admin/orders",
+                },
                 {
                     key: "admin-orders-payment-review-filters",
                     label: "The Admin Orders filter drawer has a \"Manual payment\" chip group with \"Awaiting payment\" and \"Awaiting verification\" — and each one actually returns the right orders",
@@ -1704,6 +2525,12 @@ const rawTesterChecklistItems = [
                     description: "Fixed 2026-08-21 — AdminOrdersView.mapRows built \"Order {id}\" from a nonexistent orderNumber field, and AdminOrderEditorView showed zero items even when opened. Both now read the order's already-denormalized items[] (Root Cause #52).",
                     href: "/admin/orders",
                 },
+                {
+                    key: "admin-order-detail-standalone-page",
+                    label: "An admin order's \"Open full page\" action lands on a real bookmarkable /admin/orders/[id]/view page — not just the side drawer",
+                    description: "Added 2026-08-21 — the standalone admin order page had no case of its own; it was only tested indirectly through the list-row check. Open an order's row menu, choose \"Open full page\", and confirm: (a) the URL changes to a real per-order path you can copy and reopen in a fresh tab; (b) the page shows the full items list with thumbnails, the shipping address, and the payment breakdown; (c) reloading that URL directly still works rather than bouncing you back to the list.",
+                    href: "/admin/orders",
+                },
                 {
                     key: "admin-payout-detail-view",
                     label: "Every admin payout row has an \"Open full page\" action + a working \"Mark as paid\" action, landing on a real /admin/payouts/[id]/view page with a full gross/platform-fee/gateway-fee/GST/refund-deduction/net breakdown and linked order ids — not just a bare \"transaction ID\" modal",
@@ -1794,6 +2621,30 @@ const rawTesterChecklistItems = [
                     description: "Added 2026-08-21. The digest runs automatically at 10:00 IST, but you don't need to wait — an admin can trigger it on demand by POSTing to /api/admin/daily-digest/trigger (e.g. from the browser console while logged in as admin: fetch('/api/admin/daily-digest/trigger',{method:'POST'})). Confirm the email reaches every configured recipient AND any CC addresses, and that the numbers match what the admin orders list actually shows for the last 24 hours. Note: this requires the Firebase Functions deploy to have happened for the scheduled 10:00 run — the manual trigger works regardless.",
                     href: "/admin/site",
                 },
+                {
+                    key: "site-settings-credentials-save",
+                    label: "Site Settings → Integrations: saving a real API key succeeds, shows back masked after reload, and never throws an error toast",
+                    description: "Added 2026-08-21 — this path was BROKEN in production and nothing caught it. Every key here is AES-encrypted before storage, and the encrypt call throws outright when the server's encryption key is unset, so \"Save\" failed for every integration. Enter any non-empty value in one field (a throwaway value is fine — do NOT paste a real production secret just to test), hit Save, and confirm: (a) you get a success toast, NOT an error; (b) after a full page reload the field shows a MASKED value (e.g. \"re_abc...wxyz\"), not blank and not the raw value you typed; (c) the page doesn't show a red error banner anywhere.",
+                    href: "/admin/site",
+                },
+                {
+                    key: "site-settings-credentials-partial-save-keeps-others",
+                    label: "Site Settings → Integrations: saving one API key does NOT wipe the other keys that were already saved",
+                    description: "Added 2026-08-21. Fields left blank are meant to keep whatever was stored before, not overwrite it with empty. Save a value into ONE integration field, reload, then save a value into a DIFFERENT field while leaving the first one showing its masked value untouched. Reload again and confirm BOTH fields still show masked values — if the first one came back blank, that's the bug.",
+                    href: "/admin/site",
+                },
+                {
+                    key: "site-settings-themes-tab",
+                    label: "Site Settings → Themes: a theme can be duplicated, edited, previewed and set as the light/dark default, and the site actually restyles",
+                    description: "Added 2026-08-21 — this tab had no test case at all. Duplicate one of the two built-in themes, change a colour or gradient on the copy, confirm the live preview updates, then set it as the default for light mode and save. Reload the public homepage and confirm the new colour is actually in use. Also confirm the two built-in themes (default-light / default-dark) cannot be deleted.",
+                    href: "/admin/site",
+                },
+                {
+                    key: "site-settings-notifications-non-digest",
+                    label: "Site Settings → Notifications: the non-digest settings (sender name, from address, reply-to, per-channel toggles) save and survive a reload",
+                    description: "Added 2026-08-21 — only the digest recipient lists on this tab had a test case. Change the sender display name and reply-to address, toggle a notification channel, save, then reload Site Settings and confirm every value came back as entered. Then trigger any real notification (e.g. place a test order) and confirm the email that arrives actually uses the sender name / from address you just set, rather than an older hardcoded one.",
+                    href: "/admin/site",
+                },
                 { key: "admin-dashboard-widgets", label: "Admin dashboard widgets show accurate data", href: "/admin/dashboard" },
                 { key: "analytics-admin", label: "Admin analytics dashboard shows accurate data", href: "/admin/analytics" },
                 {
@@ -1811,6 +2662,30 @@ const rawTesterChecklistItems = [
                 { key: "maintenance-pages-admin", label: "The maintenance pages (analysis, client-errors, cloud-logs, function-errors, payment-rollbacks, server-errors + detail) all load correctly", href: "/admin/maintenance" },
                 { key: "copilot-admin", label: "Admin copilot page works correctly", href: "/admin/copilot" },
                 { key: "team-admin", label: "Admin team page works correctly", href: "/admin/team" },
+                {
+                    key: "team-permission-group-filter",
+                    label: "The permission-group filter on /admin/team actually narrows the employee list",
+                    description: "Fixed 2026-08-21. The filter emitted a field the database layer was never told to accept, so the clause was discarded silently and every group showed the complete employee list. Pick a group and confirm the rows genuinely change.",
+                    href: "/admin/team",
+                },
+                {
+                    key: "audit-log-actor-search",
+                    label: "The \"Search by actor uid\" box on /admin/audit-log narrows results to that actor",
+                    description: "Fixed 2026-08-21 — the box was inert, the endpoint never read it. Paste a full actor uid from a visible row and confirm only that actor's entries remain.",
+                    href: "/admin/audit-log",
+                },
+                {
+                    key: "notifications-user-search",
+                    label: "The search box on /admin/notifications narrows results to one user, and its placeholder reads \"Search by user ID\"",
+                    description: "Fixed 2026-08-21 — the box was inert. Its placeholder also used to promise title search, which is not possible against this collection, so the wording was corrected rather than left as a promise the search cannot keep. Paste a user ID from a visible row and confirm only that user's notifications remain.",
+                    href: "/admin/notifications",
+                },
+                {
+                    key: "carousel-edit-and-delete",
+                    label: "A named carousel can be renamed, switched between draft and active, and deleted after it has been created",
+                    description: "Fixed 2026-08-21 — the editor could only CREATE. There was no way to load an existing carousel back, so a typo'd or draft carousel was stuck permanently. Create one, reopen it, rename it, publish it, then delete it.",
+                    href: "/admin/carousels",
+                },
                 { key: "guide-pages-admin", label: "The 8 admin guide pages all load correctly", href: "/admin/guide" },
                 { key: "tester-checklist-crud-admin", label: "Admin can create, edit, and toggle adminOnly on tester checklist items", href: "/admin/tester-checklist" },
                 { key: "tester-feedback-report-export", label: "Admin tester-feedback report shows Yes/No analytics grouped correctly and the Download Report export works", href: "/admin/tester-feedback" },