@mohasinac/appkit 4.34.1 → 4.35.0

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

@@ -0,0 +1,166 @@
+/*
+ * WHY: Authored six-part procedures for the selling/seller-marketing-extras page.
+ * WHAT: 9 case(s), keyed by full checklist id.
+ *
+ * Written by hand, case by case, against the label each one states. There is no
+ * generator: the authoring scripts were deleted once it was clear they were
+ * scaffolding around work that is simply writing.
+ *
+ * 🛑 THE WHATSAPP ACCESS TOKEN IS DOUBLE-ENCRYPTED and decrypted on EVERY read of
+ * the store document, so any code path that forgets to project is handling
+ * plaintext. Four pages once passed the raw document into a client component and
+ * published that token in the page HTML. The token case therefore reads the page
+ * source rather than trusting the masked field.
+ *
+ * @tag domain:tester
+ * @tag layer:seed
+ * @tag pattern:none
+ * @tag access:server-only
+ * @tag consumers:seed-data/authored/index.ts
+ * @tag sideEffects:none
+ */
+export const authored = {
+    "checklist-selling-seller-marketing-extras-seller-offers-list": {
+        roles: ["seller"],
+        startPage: "/store/offers",
+        steps: [
+            "Sign in as tyson@beybladearena.in / TempPass123!.",
+            "Open the store's offers list and read every row — product, offered amount, listed price, status and round.",
+            "Read every status filter offered and select each in turn, noting any that returns nothing.",
+            "For each empty filter, check the unfiltered list for rows carrying that status.",
+            "Open one offer and read its detail, including any earlier rounds.",
+            "Read the row actions offered and check at least one lets you VIEW rather than only act.",
+        ],
+        expectedBehaviour: "The list shows offers against this store with enough context to decide — the offered amount against the listed price is the entire negotiation. A chain of counters is one story: each round is its own document, linked forwards and backwards and denormalised to the chain's root so a row can say 'Round 2' with no extra reads.",
+        expectedUiState: "Rows show product, offered amount, listed price and round number. Every status filter either returns its own rows or is empty with none unfiltered either — the real statuses include countered and withdrawn, and a chip naming 'Rejected' when the stored value is 'Declined' matches nothing forever. A view affordance exists; a menu of pure mutations lets a seller act on an offer they never read.",
+        endResult: "Read-only; nothing persists beyond the URL.",
+    },
+    "checklist-selling-seller-marketing-extras-seller-features-crud": {
+        roles: ["seller"],
+        startPage: "/store/features",
+        steps: [
+            "Sign in as tyson@beybladearena.in / TempPass123!.",
+            "Open the store's product-features page and read the existing features.",
+            "Create one named 'QA Feature marketing-extras' with an icon and a description, and save.",
+            "RELOAD and read every field.",
+            "Open a product editor and attach that feature to 'Beyblade Burst B-01 Valkyrie', then save.",
+            "Open the product's public page and read whether the feature is shown.",
+            "Detach it, then delete the feature.",
+        ],
+        inputs: { name: "QA Feature marketing-extras", productId: "product-beyblade-burst-valkyrie" },
+        expectedBehaviour: "A feature is created once and attached to many listings, and it reaches the public page. A feature that saves in its own list but never renders on a product is a field with no reader — the seller believes they have said something the buyer never sees.",
+        expectedUiState: "After the reload the feature holds its name, icon and description. The product's public page shows it. A public page with no trace of the attached feature is the failure.",
+        endResult: "The feature is detached and deleted by the final step, so the seeded product is left as it was.",
+    },
+    "checklist-selling-seller-marketing-extras-seller-google-reviews-sync": {
+        roles: ["seller"],
+        startPage: "/store",
+        steps: [
+            "Sign in as tyson@beybladearena.in / TempPass123!.",
+            "Open the store's Google reviews sync surface and read what it asks for.",
+            "Read whether it states that credentials are required and which ones.",
+            "Trigger a sync without credentials configured and read the message.",
+            "Read whether any error mentions a provider, a key, or a raw response.",
+            "Read the store's public page for any Google reviews section.",
+        ],
+        expectedBehaviour: "With no Google credentials configured the sync declines cleanly and says so. The Places credentials are seeded as EMPTY strings rather than placeholders precisely so an unconfigured consumer skips instead of making a billed call that fails — a placeholder would be treated as a usable key.",
+        expectedUiState: "The message names the missing configuration in plain English. It does not surface a provider error code, an API key, or a raw response body. The public store page shows no empty Google reviews section.",
+        endResult: "Nothing is synced. If credentials ARE configured on this environment, record that and read what the sync actually imported instead.",
+    },
+    "checklist-selling-seller-marketing-extras-seller-whatsapp-catalog": {
+        roles: ["seller"],
+        startPage: "/store",
+        steps: [
+            "Sign in as tyson@beybladearena.in / TempPass123!.",
+            "Open the store's WhatsApp catalog surface and read every control.",
+            "Read what it says about the connection state.",
+            "Read whether it names the business account and catalog it would sync with.",
+            "Trigger a catalog action without a token configured and read the message.",
+        ],
+        expectedBehaviour: "The catalog surface reports its connection state honestly and declines cleanly when unconfigured. It is the reader of the store's WhatsApp configuration, which is stored encrypted and decrypted on every store read — so what this page shows is the one place the configuration is legitimately visible to its owner.",
+        expectedUiState: "The connection state is stated rather than implied. An unconfigured action produces a readable message naming what is missing, not a provider error. The business account and catalog identifiers are shown to the owner but partially masked.",
+        endResult: "Nothing is synced.",
+    },
+    "checklist-selling-seller-marketing-extras-seller-whatsapp-token-save": {
+        roles: ["seller", "guest"],
+        startPage: "/store",
+        steps: [
+            "Sign in as tyson@beybladearena.in / TempPass123!.",
+            "Open the store's WhatsApp settings and type QA-WHATSAPP-TOKEN-118427 into the access-token field.",
+            "Save and RELOAD, then read how the token is displayed.",
+            "Open the browser's View Source on that settings page and search for QA-WHATSAPP-TOKEN-118427.",
+            "Open /stores/store-beyblade-arena in a private window with no session.",
+            "Open View Source there and search for QA-WHATSAPP-TOKEN-118427 and for accessToken.",
+            "Clear the token field, save, and reload to confirm it is gone.",
+        ],
+        inputs: { token: "QA-WHATSAPP-TOKEN-118427" },
+        expectedBehaviour: "The token is stored double-encrypted and shown masked to its owner. Because it is decrypted on every read of the store document, the real risk is a page that passes that document to a client component — which serialises it into the public page HTML. The PUBLIC page source is therefore the assertion, not the masked field.",
+        expectedUiState: "After the reload the owner sees a masked value rather than the full token. The public store page's source contains neither the token nor the word accessToken anywhere, including inside the embedded data payload.",
+        expectedData: { tokenInPublicSource: 0 },
+        endResult: "The token is cleared by the final step. A hit on the public page is a credential leak and fails the case outright, however the settings page renders.",
+    },
+    "checklist-selling-seller-marketing-extras-seller-whatsapp-import-runs-in-background": {
+        roles: ["seller"],
+        startPage: "/store",
+        steps: [
+            "Sign in as tyson@beybladearena.in / TempPass123!.",
+            "Open the store's WhatsApp catalog surface and start an import.",
+            "Read what the page shows immediately — whether it blocks or returns.",
+            "Navigate to another store page and back.",
+            "Read whether the import's progress is still reported.",
+            "Wait for it to finish and read the summary.",
+        ],
+        expectedBehaviour: "An import of unknown size is enqueued as a job rather than run inside the request — a route that fans out over a whole catalogue is exactly the shape the ten-second function ceiling kills in production while local runs pass. The page subscribes to the job's progress instead of waiting on a response.",
+        expectedUiState: "The page returns immediately with a job accepted rather than freezing. Progress survives navigating away and back. A completion summary states what was imported. A request that hangs and then times out is the failure this case exists for.",
+        endResult: "Whatever was imported persists. With no credentials configured the import will decline instead — record that rather than failing the case.",
+    },
+    "checklist-selling-seller-marketing-extras-seller-whatsapp-import-skips-already-synced": {
+        roles: ["seller"],
+        startPage: "/store",
+        steps: [
+            "Sign in as tyson@beybladearena.in / TempPass123!.",
+            "Open the store's WhatsApp catalog surface and run an import, noting the summary and the store's product count.",
+            "Run the SAME import a second time without changing anything.",
+            "Read the second summary and compare it against the first.",
+            "Open /store/products and read the product count again.",
+            "Search the products list for any duplicated title.",
+        ],
+        expectedBehaviour: "A second import skips what is already synced rather than creating duplicates. This is the same idempotency the seed data needs: an import keyed on a stable external identifier upserts, while one keyed on anything regenerated per run creates a fresh copy every time and reports success.",
+        expectedUiState: "The second summary reports items skipped rather than a second full import. The product count is unchanged and no title appears twice.",
+        expectedData: { duplicateTitles: 0 },
+        endResult: "No duplicates exist. A doubled product count after a repeated import is the failure, and the summary will still have read as successful.",
+    },
+    "checklist-selling-seller-marketing-extras-seller-whatsapp-push-product-link-opens": {
+        roles: ["seller"],
+        startPage: "/store/products",
+        steps: [
+            "Sign in as tyson@beybladearena.in / TempPass123!.",
+            "Open /store/products and use the WhatsApp push or share control on 'Beyblade Burst B-01 Valkyrie'.",
+            "Read the message it composes before sending anything.",
+            "Read the product link inside it and note its host and path.",
+            "Open that link in a private window with no session.",
+            "Read the page it opens.",
+        ],
+        inputs: { productId: "product-beyblade-burst-valkyrie" },
+        expectedBehaviour: "The shared link is a public, canonical URL a stranger can open. There is one definition of the site host and everything derives from it — two owners drifted once and every sitemap URL pointed at a host that redirected, which is what took the site out of search.",
+        expectedUiState: "The message contains a link on the canonical host with an unprefixed path. Opening it signed out renders the product page directly rather than redirecting, and does not 404.",
+        endResult: "Nothing is sent. A link that redirects before landing is worth recording — every redirect is a hop a shared link pays on every open.",
+    },
+    "checklist-selling-seller-marketing-extras-seller-reviews-response": {
+        roles: ["seller", "guest"],
+        startPage: "/store/reviews",
+        steps: [
+            "Sign in as tyson@beybladearena.in / TempPass123!.",
+            "Open the store's reviews list and open a review with no seller response.",
+            "Type 'QA Response seller-reviews-response — thanks for the feedback.' as the response and save.",
+            "RELOAD and read the response.",
+            "Open that review on the product's public page in a private window.",
+            "Read whether the response is shown and how it is attributed.",
+            "Edit the response, save, reload, and read it again.",
+        ],
+        inputs: { response: "QA Response seller-reviews-response — thanks for the feedback." },
+        expectedBehaviour: "A seller response is stored on the review and rendered publicly, attributed to the store rather than to a person. It can be edited afterwards — a response that can only be written once leaves a typo permanent on a public page.",
+        expectedUiState: "After the reload the response is on the review in the dashboard AND on the public product page, attributed to the store. The edit persists too. The reviewer's own name stays masked; a response does not unmask it.",
+        endResult: "Delete the response afterwards so the seeded review is left as it was.",
+    },
+};

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

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

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

@@ -0,0 +1,89 @@
+/*
+ * WHY: Authored six-part procedures for the selling/seller-ops-comms page.
+ * WHAT: 4 case(s), keyed by full checklist id.
+ *
+ * Written by hand, case by case, against the label each one states. There is no
+ * generator: the authoring scripts were deleted once it was clear they were
+ * scaffolding around work that is simply writing.
+ *
+ * 🛑 THE LAST TWO CASES OVERLAP ON PURPOSE. One print surface is the real one and
+ * the other is a degraded duplicate of it rendered with no store — two features
+ * that look alike is exactly how one of them ships broken and unnoticed, so both
+ * are opened and compared rather than either being trusted.
+ *
+ * @tag domain:tester
+ * @tag layer:seed
+ * @tag pattern:none
+ * @tag access:server-only
+ * @tag consumers:seed-data/authored/index.ts
+ * @tag sideEffects:none
+ */
+export const authored = {
+    "checklist-selling-seller-ops-comms-seller-addresses-crud": {
+        roles: ["seller"],
+        startPage: "/store/addresses",
+        steps: [
+            "Sign in as tyson@beybladearena.in / TempPass123!.",
+            "Open /store/addresses and read the existing addresses.",
+            "Create one: 'QA Address ops-comms', '11 Test Lane', Indore, Madhya Pradesh, 452010, landmark 'Next to the arena'.",
+            "Save, RELOAD, and read every field including the landmark.",
+            "Edit only the street to '12 Test Lane', save, RELOAD, and read every field again.",
+            "Mark it as the default pickup location, save and RELOAD.",
+            "Delete it and RELOAD to confirm.",
+        ],
+        inputs: {
+            name: "QA Address ops-comms",
+            streetBefore: "11 Test Lane",
+            streetAfter: "12 Test Lane",
+            landmark: "Next to the arena",
+        },
+        expectedBehaviour: "Create, edit, default-set and delete all persist, and an edit touching one field leaves the others alone. The edit step is the important one: a form that cannot name a field sends undefined for it, and undefined overwrites — which is how the landmark disappeared on every edit.",
+        expectedUiState: "After each reload the address holds exactly what was typed. Following the street edit, the landmark still reads 'Next to the arena'. A blank landmark after an unrelated edit is the failure.",
+        endResult: "The address is deleted by the final step.",
+    },
+    "checklist-selling-seller-ops-comms-seller-fulfillment-queue": {
+        roles: ["seller"],
+        startPage: "/store/orders",
+        steps: [
+            "Sign in as tyson@beybladearena.in / TempPass123!.",
+            "Open the store's fulfillment queue and read the rows.",
+            "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.",
+            "Check the queue's ordering — whether the oldest unfulfilled order is first.",
+        ],
+        expectedBehaviour: "The queue lists orders needing action, keyed on what the seller has to pack rather than on an identifier they cannot act on. Order documents denormalise the item title and image precisely so a list row needs no extra fetch — a row reading only 'Order {id}' is a row-mapper that never read them.",
+        expectedUiState: "Each row names the product and shows its thumbnail, with the order id de-emphasised rather than being the whole label. Every filter returns rows or a named empty state. Rows open the order.",
+        endResult: "Read-only; nothing persists beyond the URL.",
+    },
+    "checklist-selling-seller-ops-comms-seller-print-center": {
+        roles: ["seller"],
+        startPage: "/store/print-center",
+        steps: [
+            "Sign in as tyson@beybladearena.in / TempPass123!.",
+            "Open /store/print-center 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.",
+            "Check the barcode or code shown resolves to the right product.",
+        ],
+        expectedBehaviour: "The print centre renders with the seller's own store context — name, logo, pickup address — because that context is what makes a label usable. A barcode is derived deterministically from the product id, so the same product always produces the same code.",
+        expectedUiState: "The preview carries the store's name, logo and address rather than blanks or placeholders. The output includes the selected items. The barcode matches the product it is printed for.",
+        endResult: "Nothing is persisted by previewing. Do not send anything to a physical printer.",
+    },
+    "checklist-selling-seller-ops-comms-seller-inventory-print": {
+        roles: ["seller"],
+        startPage: "/store/print-center",
+        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.",
+        ],
+        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.",
+    },
+};

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

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

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

@@ -0,0 +1,195 @@
+/*
+ * WHY: Authored six-part procedures for the selling/seller-orders page.
+ * WHAT: 11 case(s), keyed by full checklist id.
+ *
+ * Written by hand, case by case, against the label each one states. There is no
+ * generator: the authoring scripts were deleted once it was clear they were
+ * scaffolding around work that is simply writing.
+ *
+ * 🛑 THE SELLER SEES LESS OF A MANUAL PAYMENT THAN THE ADMIN DOES, on purpose. The
+ * proof screenshot is a bank or UPI capture and stays admin-only; the seller gets
+ * a status badge and the reference. Three cases here check the seller CANNOT do
+ * what only an admin may — verify, request a re-upload, or reject as fraud.
+ *
+ * @tag domain:tester
+ * @tag layer:seed
+ * @tag pattern:none
+ * @tag access:server-only
+ * @tag consumers:seed-data/authored/index.ts
+ * @tag sideEffects:none
+ */
+export const authored = {
+    "checklist-selling-seller-orders-view-orders": {
+        roles: ["seller"],
+        startPage: "/store/orders",
+        steps: [
+            "Sign in as tyson@beybladearena.in / TempPass123!.",
+            "Open /store/orders and read every row's primary label.",
+            "Check each names the ITEM and shows its thumbnail rather than only an order id.",
+            "Read the availability or scope tabs offered and select each in turn.",
+            "Read every status filter and select each, noting any that returns nothing.",
+            "Open one order and read its detail.",
+        ],
+        expectedBehaviour: "Every order carries its item title and image denormalised onto the document precisely so a list row needs no extra fetch. A row reading 'Order {id}' is a row-mapper that threw that away, leaving the seller to open each order to find out what it is.",
+        expectedUiState: "Rows name the product with a thumbnail, and a multi-item order shows a '+N more' style suffix rather than only the first item. The order id is present but de-emphasised. Scope tabs read Active / Closed / All. Every status filter returns rows or is genuinely empty.",
+        endResult: "Read-only; nothing persists beyond the URL.",
+    },
+    "checklist-selling-seller-orders-seller-order-manual-payment-badge": {
+        roles: ["seller"],
+        startPage: "/store/orders",
+        steps: [
+            "Sign in as tyson@beybladearena.in / TempPass123!.",
+            "Open /store/orders and find an order paid by cash or UPI.",
+            "Read its manual-payment badge in the list and note the state it reports.",
+            "Open the order and read the badge and the payment reference there.",
+            "Look for the buyer's uploaded proof screenshot anywhere on the page.",
+            "Look for any control to verify, request a re-upload, or reject the payment.",
+        ],
+        expectedBehaviour: "The state is DERIVED from two fields rather than stored, so every surface computes the same four states — awaiting payment, awaiting verification, re-upload requested, resolved. A stored mirror would drift the first time a write path forgot it.",
+        expectedUiState: "The badge states which of the four the order is in, in both the list and the detail. The reference is shown. The proof SCREENSHOT is not — it is a bank or UPI capture and is admin-only. No verify, re-upload or reject control is offered to the seller.",
+        expectedData: { proofScreenshotVisibleToSeller: false },
+        endResult: "Read-only. A visible screenshot or an actionable verify control here is a permissions finding, not a UI one.",
+    },
+    "checklist-selling-seller-orders-confirm-payment": {
+        roles: ["seller"],
+        startPage: "/store/orders",
+        steps: [
+            "Sign in as tyson@beybladearena.in / TempPass123!.",
+            "Open /store/orders and open an order awaiting payment verification.",
+            "Read every control the page offers.",
+            "Look specifically for a control that would mark the payment verified.",
+            "Sign out and sign in as admin@letitrip.in / TempPass123!.",
+            "Open the same order in /admin/orders and read the controls offered there.",
+        ],
+        expectedBehaviour: "Verifying a manual payment is an admin and moderator action. The seller is the beneficiary of the payment, so letting them confirm it is the party with the incentive marking their own money received — the split is deliberate and the admin view is where the control lives.",
+        expectedUiState: "The seller's view offers no verify control. The admin's view offers Verify alongside Request re-upload and Reject as fraud, with the proof screenshot visible. A verify control on the seller's page is the failure.",
+        endResult: "Do not verify anything. Read-only on both sides.",
+    },
+    "checklist-selling-seller-orders-request-reupload": {
+        roles: ["seller", "admin"],
+        startPage: "/store/orders",
+        steps: [
+            "Sign in as tyson@beybladearena.in / TempPass123! and open an order whose proof has been submitted.",
+            "Confirm no re-upload control is offered to the seller.",
+            "Sign out and sign in as admin@letitrip.in / TempPass123!.",
+            "Open the same order in /admin/orders and use Request re-upload, typing a note.",
+            "Sign in as the buyer who placed that order and open the order's payment page.",
+            "Read whether the upload form is active again and what the deadline shows.",
+        ],
+        expectedBehaviour: "Only an admin may request a re-upload, and doing so reopens the buyer's window. The note is required — a re-upload request with no reason leaves the buyer resubmitting the same thing.",
+        expectedUiState: "The seller has no such control. The admin's request requires a note before it will submit. The buyer's payment page becomes active again with an extended deadline rather than staying locked.",
+        endResult: "The order is left in the re-upload-requested state. Note that a corrected re-upload must clear that state — an order stuck in it is invisible to both the auto-approve sweep and the admin queue, and stalls forever.",
+    },
+    "checklist-selling-seller-orders-reject-fraud": {
+        roles: ["seller", "admin"],
+        startPage: "/store/orders",
+        steps: [
+            "Sign in as tyson@beybladearena.in / TempPass123! and open an order awaiting verification.",
+            "Confirm no reject-as-fraud control is offered.",
+            "Sign out and sign in as admin@letitrip.in / TempPass123!.",
+            "Open the same order in /admin/orders and read the reject-as-fraud control and what it requires.",
+            "Read any confirmation dialog it opens, without confirming it.",
+            "Cancel out of the dialog.",
+        ],
+        expectedBehaviour: "Rejecting as fraud is admin-only and requires a note, because it cancels the order, restores stock and enqueues a seven-day ban cascade against the buyer. A destructive action of that reach must carry a confirmation naming what it will do — one without it executes immediately with no warning.",
+        expectedUiState: "The seller has no such control. The admin's version requires a note and opens a confirmation that names the consequences rather than asking a generic 'Are you sure?'. Cancelling leaves the order untouched.",
+        endResult: "Nothing is rejected. Cancel rather than confirm — this action bans a real account for seven days.",
+    },
+    "checklist-selling-seller-orders-mark-shipped": {
+        roles: ["seller"],
+        startPage: "/store/orders",
+        steps: [
+            "Sign in as tyson@beybladearena.in / TempPass123!.",
+            "Open /store/orders and open an order that is ready to ship.",
+            "Use the mark-shipped control and read what it asks for.",
+            "Type 'QA Carrier mark-shipped' as the carrier and 'QATRACK118427' as the tracking number, then submit.",
+            "RELOAD the order and read its status, carrier and tracking number.",
+            "Open /store/orders and check the row's status has moved too.",
+            "Check the scope tabs — the order should still be under Active, not Closed.",
+        ],
+        inputs: { carrier: "QA Carrier mark-shipped", trackingNumber: "QATRACK118427" },
+        expectedBehaviour: "Marking shipped records the carrier and tracking number alongside the status. Shipping is manual here — there is no carrier integration — so the seller's typed values ARE the tracking data, and a status change that discards them leaves the buyer with nothing to follow.",
+        expectedUiState: "After the reload the order reads as shipped and holds both the carrier and the tracking number. The list row reflects the new status. The order stays in the Active scope, since shipped is not a closed state.",
+        expectedData: { trackingNumber: "QATRACK118427" },
+        endResult: "The order is shipped and carries its tracking data. A status that moved while the carrier and tracking are blank is the failure.",
+    },
+    "checklist-selling-seller-orders-tracking-visible": {
+        roles: ["seller", "buyer"],
+        startPage: "/store/orders",
+        steps: [
+            "Sign in as tyson@beybladearena.in / TempPass123! and open the order marked shipped in the previous case.",
+            "Read the carrier and tracking number shown.",
+            "Sign out and sign in as the buyer who placed that order.",
+            "Open /user/orders and open the same order.",
+            "Read the carrier and tracking number there.",
+            "Open the order's tracking page and read what it shows.",
+        ],
+        inputs: { trackingNumber: "QATRACK118427" },
+        expectedBehaviour: "What the seller entered reaches the buyer. The buyer's tracking page renders a timeline from the order's real per-status dates — a status with no recorded date shows no timestamp rather than a guessed one, because a fabricated date is worse than a missing one.",
+        expectedUiState: "Both sides show the same carrier and tracking number. The buyer's tracking page renders a timeline with real dates against the statuses that have them, and an em-dash against those that do not.",
+        endResult: "Read-only on the buyer side. A tracking page that is blank, or that shows invented dates for every status, are both failures.",
+    },
+    "checklist-selling-seller-orders-whatsapp-admin-share": {
+        roles: ["seller"],
+        startPage: "/store/orders",
+        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.",
+            "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.",
+        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": {
+        roles: ["seller"],
+        startPage: "/store",
+        steps: [
+            "Sign in as tyson@beybladearena.in / TempPass123!.",
+            "Open /store and open the notification list.",
+            "Look for any notification about an auction win that lapsed unpaid.",
+            "Read its title, body and destination if one exists.",
+            "Open the store's auctions list and find an auction whose win was forfeited.",
+            "Read what state that auction is now in.",
+        ],
+        expectedBehaviour: "When a win lapses unpaid the bid is forfeited and the buyer is notified. Whether the SELLER is notified is the question this case answers rather than assumes — for an unpaid buyout the seller is deliberately not told, because nothing was ever sold, and the same reasoning may or may not apply here.",
+        expectedUiState: "Record what the seller actually receives. If a notification exists it has a readable title, a body and a destination that resolves. If none exists, record that as the observed behaviour rather than as a failure.",
+        endResult: "Read-only. This case documents behaviour; report what happened rather than forcing a yes or no.",
+    },
+    "checklist-selling-seller-orders-seller-order-detail-full-page": {
+        roles: ["seller"],
+        startPage: "/store/orders",
+        steps: [
+            "Sign in as tyson@beybladearena.in / TempPass123!.",
+            "Open /store/orders and open an order's detail panel from the list.",
+            "Write down every field label and section it shows.",
+            "Note the order id and close the panel.",
+            "Open that order's standalone detail page directly by URL.",
+            "Write down every field and section, and compare the two lists.",
+            "Reload the standalone page and confirm it still loads the same order.",
+        ],
+        expectedBehaviour: "The panel and the page render from one shared content component, so their fields match by construction. The standalone page exists because a panel cannot be bookmarked or sent to someone — and an order is exactly the record a seller needs to share.",
+        expectedUiState: "Both surfaces show the same fields and sections with the same values. The standalone page survives a reload on the same order. A field in one and not the other means a second copy of the content component has appeared and the two will drift.",
+        endResult: "Read-only; nothing persists.",
+    },
+    "checklist-selling-seller-orders-seller-new-order-notification-reaches-seller": {
+        roles: ["buyer", "seller"],
+        startPage: "/products/product-beyblade-burst-valkyrie",
+        steps: [
+            "Sign in as rehan.sheikh@gmail.com / TempPass123!.",
+            "Add product-beyblade-burst-valkyrie (₹999, Beyblade Arena) to the cart.",
+            "Open /checkout, select the first saved address, choose Cash on Delivery, and place the order.",
+            "Sign out and sign in as tyson@beybladearena.in / TempPass123!, who owns that store.",
+            "Open /store and read the notification bell.",
+            "Open the notification list, read the newest entry's title and body, and click it.",
+            "Read where it lands.",
+        ],
+        inputs: { productId: "product-beyblade-burst-valkyrie", paymentMethod: "Cash on Delivery" },
+        expectedBehaviour: "A new order notifies the store that received it. The audience is a property of the EVENT, not of the person — the same account is a buyer elsewhere, so the notification has to be addressed to the store portal rather than to whichever dashboard the user happens to open.",
+        expectedUiState: "The bell shows an unread count and the newest entry names the new order with a readable body. Clicking it opens that order in the STORE portal, not the buyer's own order page.",
+        endResult: "The order exists and the notification survives a reload. No notification at all means the hook did not fire; one landing in the buyer portal means the audience was resolved from the person rather than the event.",
+    },
+};

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

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