@mohasinac/appkit 4.42.1 → 4.42.2

package/dist/features/tester/seed-data/authored/selling__seller-ops-comms.js

@@ -43,10 +43,10 @@ export const authored = {
     },
     "checklist-selling-seller-ops-comms-seller-fulfillment-queue": {
         roles: ["seller"],
-        startPage: "/store/orders",
+        startPage: "/store/fulfillment",
         steps: [
             "Sign in as tyson@beybladearena.in / TempPass123!.",
-            "Open the store's fulfillment queue and read the rows.",
+            "Open /store/fulfillment and stay on its Queue tab — the page is a two-tab shell, Queue and 'Print centre', and the other tab is a different case.",
             "Read each row's primary label and check it names the ITEM rather than only an order id.",
             "Read every filter offered and select each in turn, reading the rows.",
             "Open one row and read the order it opens.",
@@ -61,7 +61,8 @@ export const authored = {
         startPage: "/store/print-center",
         steps: [
             "Sign in as tyson@beybladearena.in / TempPass123!.",
-            "Open /store/print-center and read what it offers.",
+            "Open /store/print-center and note that it REDIRECTS to /store/fulfillment, carrying the query string with it. Landing on a differently-named page is expected, not a fault.",
+            "Switch to the 'Print centre' tab — note the British spelling — and read what it offers.",
             "Select one or more items or orders to print.",
             "Read the preview and check the store's own name, logo and address appear on it.",
             "Generate the printable output and read it.",
@@ -73,17 +74,17 @@ export const authored = {
     },
     "checklist-selling-seller-ops-comms-seller-inventory-print": {
         roles: ["seller"],
-        startPage: "/store/print-center",
+        startPage: "/store/fulfillment",
         steps: [
             "Sign in as tyson@beybladearena.in / TempPass123!.",
-            "Open /store/print-center and write down what it offers and whether the store context is present.",
-            "Open the store's inventory print page.",
-            "Write down what IT offers and whether the store context is present.",
-            "Compare the two side by side.",
-            "Check the sidebar for which of the two is linked.",
+            "Open /store/fulfillment, switch to the 'Print centre' tab, and write down what it offers and whether the store context is present — name, logo, pickup address.",
+            "Open /store/inventory/print directly by URL. It should NOT resolve: the degraded duplicate was removed when Print Centre became a tab.",
+            "Open /store/print-center and confirm it redirects here rather than rendering a second copy.",
+            "Read the sidebar and check exactly ONE entry leads to this surface, under whichever name it uses.",
+            "Confirm there is no second, store-less print surface reachable from anywhere in the sidebar.",
         ],
-        expectedBehaviour: "Only one of these is the real surface. The other renders the same component with no store attached, so it produces a preview with no name, no logo and no address — a page that looks built and yields an unusable label. Two features that look alike is how one ships broken and unnoticed.",
-        expectedUiState: "One surface carries the full store context and the other does not, or the second no longer exists. Record which is which, and which one the sidebar links to — a sidebar pointing at the degraded copy is the finding.",
-        endResult: "Read-only; nothing persists. If both render identically and correctly, say so — that is a valid outcome and means the duplicate was resolved.",
+        expectedBehaviour: "The duplicate is RESOLVED and this case now guards the resolution rather than measuring the gap. /store/inventory/print used to render the same component with no store attached — a preview with no name, no logo and no address, a page that looked built and produced an unusable label. It was removed when Print Centre became a tab of /store/fulfillment, and /store/print-center became a redirect. What must stay true is that exactly one print surface exists and it has the store context.",
+        expectedUiState: "The Print centre tab carries the store name, logo and pickup address. /store/inventory/print does not resolve. /store/print-center redirects here rather than rendering a second copy. The sidebar offers exactly one route to it. A second print surface reappearing — or this one rendering without store context — is the finding.",
+        endResult: "Read-only; nothing persists. /store/inventory/print resolving at all is a REGRESSION, not a discovery: it was deliberately deleted, so its return means something reinstated it.",
     },
 };

package/dist/features/tester/seed-data/authored/selling__seller-orders-at-scale.js

@@ -44,12 +44,28 @@ export const authored = {
         steps: [
             "Sign in as tyson@beybladearena.in / TempPass123!.",
             "Open /store/orders and count how many orders are listed.",
+            /*
+             * 🛑 ZERO IS ONE FAILURE HERE; TOO HIGH IS THE OTHER, AND ONLY ZERO WAS
+             * BEING CHECKED.
+             *
+             * The route documents two real bugs it fixed, and this case only caught
+             * the first: an unbounded `in` query that threw for any store past its
+             * 30th listing and was swallowed into ₹0 (Root Cause #59's shape). The
+             * second was the opposite direction — `o.status !== "CANCELLED"` against
+             * a lowercase OrderStatusValues, so the exclusion never excluded anything
+             * and headline revenue counted cancelled and refunded orders.
+             *
+             * A "> ₹0" assertion passes cheerfully against that. The cancelled and
+             * refunded totals are what tell the two apart, so the steps below read
+             * them.
+             */
+            "Filter /store/orders to Cancelled and note the total of any one cancelled order.",
             "Open /store.",
             "Read the total-orders figure and the revenue figure on the dashboard.",
         ],
-        expectedBehaviour: "The dashboard's headline numbers come from the same query as the order list, so they must agree with it. A failed query here is swallowed into an empty array, which renders as a confident zero rather than as an error.",
-        expectedUiState: "The order count matches what /store/orders listed, and revenue is greater than ₹0 for a store with delivered orders.",
-        expectedData: { revenueIsZero: false },
+        expectedBehaviour: "The dashboard's headline numbers come from the same query as the order list, so they must agree with it. A failed query here is swallowed into an empty array, which renders as a confident zero rather than as an error. Revenue additionally EXCLUDES cancelled and refunded orders — money that was never kept is not revenue — so a figure that silently includes them is wrong in the opposite direction and looks healthier than the truth.",
+        expectedUiState: "The order count matches what /store/orders listed, and revenue is greater than ₹0 for a store with delivered orders. Revenue is also strictly LESS than the sum of every order's total, because this store has cancelled and refunded orders that must not be counted — a revenue figure equal to the all-orders sum is the exclusion silently not applying.",
+        expectedData: { revenueIsZero: false, cancelledOrdersCountedAsRevenue: false },
         endResult: "The same figures survive a reload.",
     },
     "checklist-selling-seller-orders-at-scale-orders-only-this-store": {

package/dist/features/tester/seed-data/authored/selling__seller-orders.js

@@ -135,13 +135,31 @@ export const authored = {
         steps: [
             "Sign in as tyson@beybladearena.in / TempPass123!.",
             "Open /store/orders and open an order.",
-            "Find the WhatsApp share control and read what it offers.",
-            "Trigger it and read the message it composes before sending anything.",
-            "Check the message for the buyer's full phone number, full address and any payment identifier.",
+            /*
+             * 🛑 NO SUCH CONTROL EXISTS TODAY, AND ABSENCE IS THE EXPECTED ANSWER.
+             *
+             * Measured 2026-09-29: SELLER_ROW_ACTIONS.orders is
+             * [VIEW, EDIT, TRACK, RESEND] — no share. SellerOrdersView mentions
+             * WhatsApp only as the buyer's purchased add-on flag
+             * (whatsappNotifyAddon / whatsappNotifyFee), and every `wa.me` link in
+             * the codebase is on the contact page, the chat button or the buyer's own
+             * payment page. The registry's WhatsApp actions are store SETUP
+             * (whatsapp-connect, catalog-sync, catalog-import).
+             *
+             * The case is kept rather than deleted because it guards a real risk the
+             * day someone adds one: an order share is exactly the control that would
+             * paste a buyer's address and phone into a third-party app. Written so
+             * that absence PASSES and a leaky implementation FAILS — which is the
+             * only shape that stays useful while the feature does not exist.
+             */
+            "Look for a WhatsApp or generic share control on the order — in the row actions, the detail drawer and the full detail page.",
+            "If none exists anywhere, record that and stop: no share control is the expected state and the case passes.",
+            "If one does exist, trigger it and read the message it composes before sending anything.",
+            "Check that message for the buyer's full phone number, full address and any payment identifier.",
             "Close without sending.",
         ],
         expectedBehaviour: "The share composes a message about the order. What it must not do is put more of the buyer's data into a third-party app than the seller needs to fulfil — a share that pastes a full address and phone into an outbound message has moved PII somewhere no policy here covers.",
-        expectedUiState: "The composed message identifies the order and what it contains. Read exactly what buyer data it includes and record it. A full payment identifier in the message is a finding regardless of anything else.",
+        expectedUiState: "No share control is present on the row actions, the drawer or the detail page — that is the current expected state and it passes. If one IS present, the composed message identifies the order and what it contains; read exactly what buyer data it includes and record it, and a full payment identifier in that message is a finding regardless of anything else.",
         endResult: "Nothing is sent. Report precisely which buyer fields the message carries — that is the substance of this case.",
     },
     "checklist-selling-seller-orders-seller-auction-forfeit-notification": {

package/dist/features/tester/seed-data/authored/selling__seller-shipping-payouts-setup.js

@@ -25,7 +25,7 @@ export const authored = {
         startPage: "/store/shipping",
         steps: [
             "Sign in as tyson@beybladearena.in / TempPass123!.",
-            "Open the store's shipping settings and read every field and section.",
+            "Open /store/shipping and read every field and section.",
             "Note which shipping options the store currently offers and their rates.",
             "Read whether a free-shipping threshold is configurable and what it is set to.",
             "Reload the page and confirm the same values are shown.",
@@ -39,10 +39,10 @@ export const authored = {
         startPage: "/store/shipping",
         steps: [
             "Sign in as tyson@beybladearena.in / TempPass123!.",
-            "Open the store's shipping settings and create a config named 'QA Shipping configs-crud' with a rate of 99.",
+            "Open /store/shipping and create a config named 'QA Shipping configs-crud' with a rate of 99.",
             "Save, RELOAD, and read every field of it.",
             "Edit only its rate to 149, save, RELOAD, and read every field again including the name.",
-            "Open a product's editor and check the new config is offered as a shipping choice.",
+            "Open /store/products, then that product's editor, and check the new config is offered as a shipping choice.",
             "Delete the config and RELOAD to confirm.",
         ],
         inputs: { name: "QA Shipping configs-crud", rateBefore: 99, rateAfter: 149 },
@@ -73,7 +73,7 @@ export const authored = {
         startPage: "/store/payouts",
         steps: [
             "Sign in as tyson@beybladearena.in / TempPass123!.",
-            "Open the store's payout settings and read every field and toggle.",
+            "Open /store/payouts and read every field and toggle.",
             "Read whether the payout schedule, hold period and minimum amount are shown.",
             "Change one editable setting and save.",
             "RELOAD and read every setting again.",
@@ -88,13 +88,25 @@ export const authored = {
         startPage: "/store/shipping",
         steps: [
             "Sign in as tyson@beybladearena.in / TempPass123!.",
-            "Open each of the pre-consolidation URLs directly in the address bar, one at a time.",
+            /*
+             * 🛑 THE URLS ARE NAMED NOW. This said "each of the pre-consolidation
+             * URLs" and listed none, so the tester had to guess which ones existed —
+             * and a guess that misses the one that regressed reports a clean pass.
+             *
+             * These are the real shims under /store, each a page.tsx whose whole body
+             * is a redirect. Two of them carry a TAB, which is the part worth
+             * checking: /store/payout-settings redirects to ?tab=settings, and
+             * /store/print-center forwards its own query onto /store/fulfillment.
+             * Landing on the right page but the FIRST tab is the regression this case
+             * exists for, and it is invisible unless the URLs are enumerated.
+             */
+            "Open each of these pre-consolidation URLs directly in the address bar, one at a time: /store/payout-methods, /store/payout-settings, /store/shipping-configs, /store/print-center, /store/auctions, /store/pre-orders, /store/prize-draws, /store/slug.",
             "For each, read where the browser lands and which tab is open.",
             "Note any that 404 or land on the first tab rather than the one they name.",
             "Read the final URL each one settles on.",
         ],
         expectedBehaviour: "An old URL lands on the consolidated page WITH its own tab open. These URLs are live in bookmarks, emails and guides, so a 404 breaks links that were correct when they were written — and landing on tab one is only marginally better, since the user still has to hunt.",
-        expectedUiState: "Every old URL resolves and opens the tab it corresponds to. None 404s and none lands on the default tab. Record any that do, by URL.",
+        expectedUiState: "Every old URL resolves and opens the tab it corresponds to. None 404s and none lands on the default tab. Specifically: /store/payout-settings settles on /store/payouts with the settings tab open (its shim appends ?tab=settings), /store/payout-methods settles on /store/payouts, /store/shipping-configs on /store/shipping, /store/print-center on /store/fulfillment carrying any query it was given, /store/slug on /store/storefront, and /store/auctions, /store/pre-orders and /store/prize-draws each on /store/products carrying its own ?listingType= (auction, pre-order, prize-draw) — arriving without that parameter is the regression, because the page then shows every type. Record any that 404 or land on the default tab, by URL.",
         endResult: "Read-only; nothing persists.",
     },
     "checklist-selling-seller-shipping-payouts-setup-consolidated-tabs-url-writeback": {
@@ -102,7 +114,7 @@ export const authored = {
         startPage: "/store/shipping",
         steps: [
             "Sign in as tyson@beybladearena.in / TempPass123!.",
-            "Open the consolidated settings page and read the URL.",
+            "Open /store/shipping and read the URL. It is the consolidated page: /store/shipping-configs now redirects here, as /store/payout-methods and /store/payout-settings both redirect to /store/payouts.",
             "Click a different tab and read the URL again.",
             "Copy that URL, open it in a new tab, and read which tab is open.",
             "Press the browser back button and read which tab is shown.",
@@ -117,7 +129,7 @@ export const authored = {
         startPage: "/store/print-center",
         steps: [
             "Sign in as tyson@beybladearena.in / TempPass123!.",
-            "Open /store/print-center and select two items to print.",
+            "Open /store/print-center — it REDIRECTS to /store/fulfillment and carries the query string with it, which is the whole mechanism this case depends on — then switch to the 'Print centre' tab and select two items to print.",
             "Read the URL and check the selection is represented in it.",
             "Copy the URL and open it in a new tab.",
             "Read whether the same two items are selected on arrival.",

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

@@ -25,10 +25,10 @@ export const authored = {
         startPage: "/store",
         steps: [
             "Sign in as tyson@beybladearena.in / TempPass123!.",
-            "Open /store and expand every group in the sidebar.",
+            "Open /store and expand ALL SIX sidebar groups: Overview, Listings, Orders & Reviews, Finance, Store, Guides. The last one — Guides — sets defaultOpen:false, so it is the one a tester skips and then reports as missing.",
             "Click each link in turn, reading where it lands and going back each time.",
             "Write down any link that 404s, renders an empty shell, or lands somewhere unrelated.",
-            "Count the links against the number of pages that exist under /store.",
+            "Count the links against the pages that exist under /store. There are 39 sidebar items and 86 page.tsx files beneath /store, so a surplus of pages is EXPECTED — new/, [id]/edit/ and other sub-routes legitimately have no entry of their own. What matters is a top-level page with no route in at all.",
         ],
         expectedBehaviour: "Every sidebar link opens a real page with content. The inverse — a built page with no sidebar entry — is the same defect from the other side and is why the count matters: around seventeen store pages were once reachable only by typing their exact URL.",
         expectedUiState: "Every link resolves to a page that renders content, not a 404 and not chrome with an empty body. Note any page you know exists that has no link — that half is not enforced and has to be spotted by eye.",
@@ -42,7 +42,7 @@ export const authored = {
             "Sign in as tyson@beybladearena.in / TempPass123!.",
             "Open /store and note which sidebar entry is highlighted.",
             "Navigate to /store/products and read which entry is highlighted.",
-            "Navigate to a nested page beneath it — a product's editor — and read the highlight again.",
+            "Navigate to a nested page beneath it — open /store/products, then a product's editor at /store/products/{id}/edit — and read the highlight again. The parent Products entry must stay highlighted two levels down; a highlight that only matches the exact path goes dark on every editor.",
             "Navigate to /store/orders and read it again.",
             "Use the browser's back button and read the highlight.",
         ],
@@ -94,7 +94,7 @@ export const authored = {
             "Click through to /user and read where it lands.",
             "From /user, find the way back to /store and click it.",
             "Check the sidebar changed with the portal each time.",
-            "Open the public store page from within the dashboard and confirm it opens the public view rather than the editor.",
+            "Open the public store page from within the dashboard — it is /stores/store-beyblade-arena, under the PLURAL /stores — and confirm it opens the public view rather than the editor. The two differ by one character, which is exactly how such a link ends up pointing back into the dashboard.",
         ],
         expectedBehaviour: "A seller is also a buyer, so both portals are reachable from each other and each renders its own navigation. The public-store link is a distinct destination from the store settings editor — conflating them is a live defect on the buyer side, where a 'My Profile' entry leads to the edit page rather than the public profile.",
         expectedUiState: "Each cross-link lands in the other portal with that portal's own sidebar. The public store link opens the public store page, not the settings editor.",

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

@@ -69,7 +69,7 @@ export const authored = {
         startPage: "/store/pre-orders",
         steps: [
             SIGN_IN_SELLER,
-            "Open /store/pre-orders.",
+            "Open /store/pre-orders. It REDIRECTS to /store/products?listingType=pre-order — the per-type seller pages were folded into the one products list with a type filter — so landing on a differently-named URL carrying a query is the design, not a broken link. Everything below is read on that filtered list.",
             "Read the listings shown and check each is a pre-order.",
             "Read each one's production status and delivery date in the list.",
             "Create a pre-order from this page titled 'QA Store Preorder Probe' with a full price of 999 and a deposit of 200.",
@@ -86,7 +86,7 @@ export const authored = {
         steps: [
             SIGN_IN_SELLER,
             "Open each of these by URL in turn: /store/guide, /store/guide/capabilities, /store/guide/finance, /store/guide/listings, /store/guide/orders, /store/guide/settings and /store/guide/whatsapp.",
-            "Check every one of them is also linked from the Guide area rather than only reachable by URL.",
+            "Check every one of them is also linked from the sidebar's 'Guides' group — it is the LAST group and sets defaultOpen:false, so EXPAND IT before concluding anything is unlinked. All seven are there: All Guides, Listings Guide, Orders Guide, Finance Guide, Settings, Capabilities, WhatsApp Catalog Sync.",
             "Record any that 404 or render empty.",
             "On two of them, check the screen they describe still exists and is named the same way.",
             "Record any guide describing a control that is no longer there.",

package/dist/features/tester/seed-data/authored/seo__canonical-and-host.js

@@ -55,7 +55,7 @@ export const authored = {
             "Type the products path with an /en prefix in front of it into the address bar.",
             "Watch the network panel and read the first response's status.",
             "Read where the address bar lands.",
-            "Open the products page from the site's own navigation and read the address bar.",
+            "Open /products from the site's own navigation — the Products entry in the main nav, not a typed URL — and read the address bar. It must land on /products with no locale prefix; the site's own links are what matter here, since a typed /en/products would only prove the redirect works, not that the navigation stopped emitting prefixed hrefs.",
             "Compare the two.",
         ],
         expectedBehaviour: "A locale-prefixed path resolves to the unprefixed one, and the site's own links use the unprefixed form so no internal navigation pays the redirect. Two spellings of every path is two addresses a crawler has to reconcile, and one of them is always the slower.",
@@ -66,7 +66,7 @@ export const authored = {
         roles: ["guest"],
         startPage: "/",
         steps: [
-            "Open the homepage on the www host and view the page source.",
+            "Open the homepage on the www host and view the page source. The canonical host has ONE definition — appkit.config.js seo.siteUrl, which defaults to https://www.letitrip.in and can be overridden by NEXT_PUBLIC_SITE_URL. That override is how these drifted apart before: one path read the env var and another held a hardcoded apex, so the sitemap advertised URLs on a host that redirected. Compare what you read here against the host in the address bar, not against a remembered value.",
             "Find the canonical link element and read its href.",
             "Compare its host against the host in the address bar.",
             "Open /products and read its canonical.",
@@ -81,13 +81,13 @@ export const authored = {
     },
     "checklist-seo-canonical-and-host-no-inherited-homepage-canonical": {
         roles: ["guest"],
-        startPage: "/promotions",
+        startPage: "/reviews",
         steps: [
             "Open /reviews and view the page source.",
             "Find the canonical link element, if there is one, and read its href.",
             "Check it is not the homepage's URL.",
-            "Open /promotions and read its canonical the same way.",
-            "Open two more pages that are unlikely to declare their own metadata and read theirs.",
+            "Open /promotions and read its canonical the same way. EXPECT NONE: it is a bare redirect, and a redirect page deliberately carries no metadata at all, because redirect() fires before a document is produced — a crawler follows it and reads the canonical of the page it LANDS on. An absent canonical here is correct; the homepage's URL appearing here is the defect.",
+            "Open /sellers and /brands — two more pages unlikely to declare their own metadata — and read theirs.",
         ],
         expectedBehaviour: "Metadata declared at the root is INHERITED by every page beneath it, so a static absolute canonical there makes every page that does not override it declare itself a duplicate of the homepage. A page either declares its own or has none.",
         expectedUiState: "No page other than the homepage carries the homepage's URL as its canonical. Every page whose canonical reads as the bare site root is a finding, listed by path.",

package/dist/features/tester/seed-data/authored/seo__og-images.js

@@ -95,7 +95,7 @@ export const authored = {
         roles: ["guest"],
         startPage: "/classified/classified-beyblade-stadium-set",
         steps: [
-            "Open /classified in a private window and find a listing whose card shows no photo of its own; if every card has one, say so and answer null rather than guessing.",
+            "🛑 THIS BRANCH CANNOT BE REACHED THROUGH THE UI — answer null and record why, rather than hunting. The OG renderer falls back when a listing has neither mainImage nor images[0] (resolveOgImageUrl is passed null), but EVERY seeded listing carries images, and both product forms require one: the schema is mainImage: z.string().min(1, 'A main image is required'), on the quick form and the advanced form alike. So no listing a tester can find or create reaches the fallback. Confirm the branch exists by reading the source if you wish, then abstain — a fabricated yes here would be coverage of a path no visitor can produce.",
             "Open its detail page and view the source.",
             "Copy the og:image URL and open it in a fresh tab.",
             "Read what renders.",

package/dist/features/tester/seed-data/authored/seo__page-metadata.js

@@ -77,10 +77,10 @@ export const authored = {
         roles: ["guest"],
         startPage: "/products",
         steps: [
-            "Open /products and use the browser's element inspector to count top-level headings.",
-            "Do the same on the homepage.",
-            "Do the same on a product detail page.",
-            "Do the same on a store page and on a blog post.",
+            "Open /products and WAIT for the page to settle before counting anything — this app hydrates client-side and the homepage has been measured with NO h1 at 2.5 seconds and exactly one at 3. A count taken early reports zero and reads as a missing heading. Then use the element inspector to count top-level headings.",
+            "Do the same on / — the page where the early-count trap was actually measured, so wait there especially.",
+            "Do the same on /products/product-beyblade-burst-valkyrie.",
+            "Do the same on /stores/store-beyblade-arena and on /blog/selling-tips-letitrip.",
             "Record the count for each.",
         ],
         expectedBehaviour: "One top-level heading per page states what the page is. Several compete to be that statement, and none makes it clear which describes the page.",
@@ -92,11 +92,11 @@ export const authored = {
         roles: ["guest"],
         startPage: "/products",
         steps: [
-            "Open the network panel and navigate to a product path whose trailing segment is a nonsense word no listing uses.",
+            "Open the network panel and navigate to /products/zzzznope — a nonsense slug no listing uses, deliberately NOT shaped like a real id so nobody mistakes it for a fixture.",
             "Read what the page shows.",
             "View the source and read every robots meta tag.",
-            "Repeat with a nonsense store path and a nonsense auction path.",
-            "Open a REAL product page and read its robots meta tags too.",
+            "Repeat with /stores/zzzznope and /auctions/zzzznope.",
+            "Open a REAL product page — /products/product-beyblade-burst-valkyrie — and read its robots meta tags too. That contrast is the point: a noindex on the 404 is correct, the SAME noindex on a live listing is the defect, and without both readings you cannot tell which you are looking at.",
         ],
         expectedBehaviour: "A missing page renders the site's 404 view and marks itself NOINDEX. Judge the noindex, not the status code: Next streams the response, so the headers are already sent by the time the not-found is raised and the status can no longer be changed. It injects a noindex robots tag into the streamed HTML instead, and that is what actually keeps the URL out of the index. A 200 here is expected and is not the finding.",
         expectedUiState: "All three missing paths render the 404 view and their source carries a robots tag whose content is noindex. The real product page carries no noindex — check it, because a blanket noindex would satisfy the first half while quietly de-indexing the whole catalogue.",

package/dist/features/tester/seed-data/authored/seo__sitemap-and-robots.js

@@ -49,8 +49,8 @@ export const authored = {
         startPage: "/robots.txt",
         steps: [
             "Open /robots.txt directly and read the whole file.",
-            "Read every Disallow line.",
-            "Check no rule disallows the site root for all user agents.",
+            "Read every Disallow line. There are ELEVEN under the '*' group — /admin/, /api/, /store/, /user/, /auth/, /checkout/, /cart/, /wishlist, /preview/, /track/, /unauthorized/ — and each names a surface a crawler has no business indexing. A public browse route appearing among them is the finding.",
+            "Check no rule disallows the site root for the '*' group. 🛑 THERE IS A SECOND GROUP AND IT DOES DISALLOW EVERYTHING: GPTBot, ChatGPT-User, Google-Extended and CCBot are blocked wholesale with Disallow: /. That is deliberate — AI crawlers, not search engines — so finding a bare 'Disallow: /' in this file is expected and is NOT the failure. Check which user-agent block it sits under before recording anything.",
             "Read the Host line, if present, and note the hostname.",
             "Compare that hostname against the address bar and against the sitemap's entries.",
         ],
@@ -91,7 +91,7 @@ export const authored = {
         roles: ["guest"],
         startPage: "/sitemap.xml",
         steps: [
-            "Open /sitemap.xml and search for 'sandbox'.",
+            "Open /sitemap.xml and search for 'tester-sandbox' — that substring is the exact marker every tester fixture carries in its id, so it is a precise check rather than a guess at the naming.",
             "Search for 'qa-'.",
             "Search for 'test-' as a looser check.",
             "Record any match with its full URL.",