@mohasinac/appkit 4.58.0 → 4.60.0

package/dist/features/tester/seed-data/authored/selling__product-upload-details.js

@@ -1,155 +0,0 @@
-/*
- * WHY: Authored six-part procedures for the selling/product-upload-details page.
- * WHAT: 6 case(s), keyed by full checklist id.
- *
- * The seller product form has THREE separate media controls and they are easy to
- * conflate. Grounded in SellerProductShell.tsx `StepMedia` (:342-497):
- *
- *   Main image    ImageUpload,      label "Main Image", enableAdvancedCrop,
- *                                   cropAspectRatio 1, max 10 MB, index 1
- *   Gallery       MediaUploadList,  label "Gallery (up to N images + 1 video)",
- *                                   maxItems PRODUCT_MAX_IMAGES + PRODUCT_MAX_VIDEOS,
- *                                   maxSizeMB 50, indices 2..PRODUCT_IMAGE_INDEX_MAX
- *   Video panel   MediaUploadField, YouTube / external URL / trim / poster
- *
- * 🛑 The caps are deliberately named here rather than numbered. They are one
- * constant (`_internal/shared/media/limits.ts`) and they MOVE — 5 -> 10 -> 24 so
- * far — and every previous revision of this comment pinned the number of the day.
- *
- * The existing pages already cover the CAPS (selling/media-limits: the last
- * allowed image uploads, the first over the cap is refused client-side, a second
- * video is refused) and the basics (selling/listing-a-product:
- * upload, preview, remove, crop, multiple). This page covers what neither does:
- * refusal copy, type refusal, ordering, index collision, and the video path that
- * was returning a 500 until 2026-09.
- *
- * @tag domain:tester
- * @tag layer:seed
- * @tag pattern:none
- * @tag access:server-only
- * @tag consumers:seed-data/authored/index.ts
- * @tag sideEffects:none
- */
-import { MEDIA_ENDPOINTS } from "../../../../constants/api-endpoints.js";
-/*
- * The endpoint comes from the registry, not a literal.
- *
- * These cases genuinely need to name it — the tester is told to open the
- * network panel and read that exact request, and "the signing request" would be
- * too vague for R8, which requires literal values. But a pasted copy of the path
- * is a second definition that silently rots the day the route moves, leaving a
- * tester hunting a request that no longer exists and reporting a bug that is
- * really a stale case. Interpolating keeps it precise AND single-sourced.
- */
-const SIGN = MEDIA_ENDPOINTS.SIGN;
-const SIGN_IN_SELLER = "Sign in as tyson@beybladearena.in / TempPass123!.";
-export const authored = {
-    "checklist-selling-product-upload-details-main-image-crop-applies": {
-        roles: ["seller"],
-        startPage: "/store/products/new",
-        steps: [
-            SIGN_IN_SELLER,
-            "Open /store/products/new and click 'Show all fields (advanced)' to reach the sectioned form.",
-            "Open the Media section and choose public/test-media/sample-image.png for 'Main Image'.",
-            "Wait for the crop dialog to appear and note the shape of the crop box.",
-            "Drag the crop box to cover clearly only the LEFT half of the picture, then confirm.",
-            "Read the thumbnail that appears afterwards and compare what it shows against the original.",
-        ],
-        inputs: { image: "public/test-media/sample-image.png" },
-        expectedBehaviour: "The crop is applied to the bytes that are uploaded, not merely previewed. A cropper that shows a selection and then stores the original is worse than no cropper — the seller believes they framed the photo and the marketplace shows something else. The box is locked square because the main image is rendered square on every card.",
-        expectedUiState: "A crop dialog opens before any upload begins, and its box is square and stays square when dragged. The resulting thumbnail shows the LEFT half that was selected, not the whole picture.",
-        expectedData: { cropAspectRatio: 1 },
-        endResult: "Leave without saving. Re-open the form: no half-uploaded image is left attached to a draft.",
-    },
-    "checklist-selling-product-upload-details-oversize-image-refused-client-side": {
-        roles: ["seller"],
-        startPage: "/store/products/new",
-        steps: [
-            SIGN_IN_SELLER,
-            "Open /store/products/new and switch to the advanced form.",
-            "Open the Media section and read the size limit stated next to 'Main Image'.",
-            "Choose public/test-media/oversized.png for the Main Image and start a timer. 🛑 THE BATCH DOES NOT GENERATE THIS FILE — there is no fixture manifest for this page. Run `node tester/scripts/make-media-fixtures.mjs --with-oversized` first; it sizes the fixture by reading the caps out of appkit/src/_internal/shared/media/limits.ts rather than from a remembered number. It is >10 MB of incompressible noise and deliberately not committed.",
-            "Read the message that appears and note how long it took.",
-            `Open the browser network panel and check whether any request to ${SIGN} was made.`,
-        ],
-        inputs: { image: "public/test-media/oversized.png", limitMb: 10 },
-        expectedBehaviour: "A file over the limit is refused BEFORE any bytes leave the browser. The point is the seller's time: a 12 MB upload that travels, then finalises, then fails validation has taken a minute to tell them something the form already knew when they picked the file. The limit is also stated up front rather than only in the refusal.",
-        expectedUiState: `The refusal is immediate (well under a second) and reads 'File size must be less than 10MB (current: …)', naming the actual size — 10 is MAX_IMAGE_BYTES from limits.ts. 🛑 EXPECT 50MB INSTEAD, AND RECORD IT: the gallery field passes maxSizeMB={50} explicitly, which is the VIDEO cap applied to a field accepting image/* and video/* alike, so a 12 MB image is accepted client-side. MediaUploadField's own auto-derived defaults (image 25, video 200, pdf 10) disagree with limits.ts (10, 50, 20) on all three. Report the number the message actually states. No ${SIGN} request appears in the network panel. The field keeps whatever image it had before.`,
-        expectedData: { signRequestsMade: 0 },
-        endResult: "Leave without saving; nothing was uploaded.",
-    },
-    "checklist-selling-product-upload-details-disallowed-type-refused": {
-        roles: ["seller"],
-        startPage: "/store/products/new",
-        steps: [
-            SIGN_IN_SELLER,
-            "Open /store/products/new and switch to the advanced form.",
-            "Open the Media section and choose public/test-media/sample-vector.svg for the Main Image.",
-            "Read the message that appears.",
-            "Now choose public/test-media/sample-image.png for the same field.",
-            "Read whether it is accepted.",
-        ],
-        inputs: { rejected: "public/test-media/sample-vector.svg", accepted: "public/test-media/sample-image.png" },
-        expectedBehaviour: "SVG is deliberately outside the allowed image types — it is a document format that can carry script, and it is served from our own origin. The refusal happens on type, not on extension alone, and the control recovers: refusing one file must not leave the field wedged.",
-        expectedUiState: "The SVG is refused with a message naming the accepted types. Immediately afterwards the PNG uploads normally in the same field — no reload needed.",
-        endResult: "Leave without saving.",
-    },
-    "checklist-selling-product-upload-details-gallery-order-persists": {
-        roles: ["seller"],
-        startPage: "/store/products/new",
-        steps: [
-            SIGN_IN_SELLER,
-            "Open /store/products/new and switch to the advanced form.",
-            "Open the Media section and add three gallery images one at a time: public/test-media/sample-image.png, then public/test-media/sample-image-2.png, then public/test-media/sample-image-3.png.",
-            "Note the order the three thumbnails appear in, left to right.",
-            "Drag the THIRD thumbnail to the first position.",
-            "Fill Title 'Gallery Order Probe', Description 'Checking that gallery ordering survives a save and reload.', Category 'Beyblade Burst', Price 499, then Publish.",
-            "Re-open the product for editing and read the gallery order again.",
-        ],
-        inputs: {
-            images: "public/test-media/sample-image.png + sample-image-2.png + sample-image-3.png",
-            title: "Gallery Order Probe",
-            price: 499,
-        },
-        expectedBehaviour: "Gallery order is the seller's editorial decision about which angle a buyer sees second, so it is stored, not just displayed. Order that survives in the form but resets on reload means the array is being rebuilt from upload time rather than from the arrangement.",
-        expectedUiState: "After the drag the moved image is first. After publish and re-open it is STILL first, in the same order as before the save.",
-        expectedData: { firstGalleryImage: "public/test-media/sample-image-3.png" },
-        endResult: "The published product's gallery order matches what was arranged. Delete the product afterwards.",
-    },
-    "checklist-selling-product-upload-details-main-image-does-not-collide-with-gallery": {
-        roles: ["seller"],
-        startPage: "/store/products/new",
-        steps: [
-            SIGN_IN_SELLER,
-            "Open /store/products/new and switch to the advanced form.",
-            "Open the Media section and set the Main Image to public/test-media/sample-image.png, accepting the crop.",
-            "Add public/test-media/sample-image-2.png as the first GALLERY image.",
-            "Read both previews and confirm they show different pictures.",
-            "Publish with Title 'Slot Collision Probe', Description 'Main image and first gallery image must not overwrite each other.', Category 'Beyblade Burst', Price 499.",
-            "Open the product's public page at /products/{its slug} and read the main image and the first gallery thumbnail.",
-        ],
-        inputs: { mainImage: "public/test-media/sample-image.png", firstGalleryImage: "public/test-media/sample-image-2.png", price: 499 },
-        expectedBehaviour: "The main image occupies index 1 and the gallery starts at index 2. Filenames here are content-derived with no timestamp, so two uploads that computed the same index would write the same storage path and the second would silently overwrite the first — the seller would see one of their two pictures simply vanish.",
-        expectedUiState: "The main image and the first gallery thumbnail show DIFFERENT pictures, both in the form and on the published page. Neither is blank.",
-        expectedData: { distinctImages: 2 },
-        endResult: "Both images survive a reload of the public page. Delete the product afterwards.",
-    },
-    "checklist-selling-product-upload-details-video-upload-succeeds": {
-        roles: ["seller"],
-        startPage: "/store/products/new",
-        steps: [
-            SIGN_IN_SELLER,
-            "Open /store/products/new and switch to the advanced form.",
-            "Open the Media section and open the video panel's 'Upload' tab.",
-            "Choose public/test-media/sample-video.mp4 and wait for it to finish.",
-            `Open the browser network panel and read the status of the ${SIGN} request.`,
-            "Read whether a poster frame and a duration appear.",
-            "Publish with Title 'Video Upload Probe', Description 'Checking the seller video upload path end to end.', Category 'Beyblade Burst', Price 499, then open the public page and play the video.",
-        ],
-        inputs: { video: "public/test-media/sample-video.mp4", price: 499 },
-        expectedBehaviour: "The dedicated video panel uploads through the same signed-URL flow as the gallery. This path returned HTTP 500 until 2026-09 because the panel omitted the category from the upload context and the filename generator threw on it — so every seller video upload from this panel failed while the gallery path worked. This case is that defect's regression test.",
-        expectedUiState: `${SIGN} returns 200, not 400 or 500. A poster frame and a duration appear. The published page plays the video.`,
-        expectedData: { signStatus: 200 },
-        endResult: "The video survives a reload of the public page. Delete the product afterwards.",
-    },
-};

package/dist/features/tester/seed-data/authored/selling__quick-add-minimum-details.d.ts

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

package/dist/features/tester/seed-data/authored/selling__quick-add-minimum-details.js

@@ -1,138 +0,0 @@
-/*
- * WHY: Authored six-part procedures for the selling/quick-add-minimum-details page.
- * WHAT: 6 case(s), keyed by full checklist id.
- *
- * 🛑 THE QUICK FORM AND "THE FIELDS VISIBLE ON WHATSAPP" ARE THE SAME SET. That is
- * what makes this one page rather than two.
- *
- * `/store/products/new` does NOT open the sectioned form. SellerProductShell.tsx
- * :1379 picks `formMode = "quick"` whenever mode is create and listingType is
- * standard, so the default is QuickProductForm — six fields: title*, category*,
- * price*, mainImage*, description, stockQuantity. The sectioned form is behind
- * "Show all fields (advanced)".
- *
- * And the WhatsApp catalog push (catalog-sync/route.ts:70-86) sends exactly
- * title, price, mainImage, condition and stockQuantity plus a derived slug and
- * link. That is the quick form's field set. A seller who fills only the short
- * form has, by construction, filled everything a WhatsApp buyer will ever see.
- *
- * 🛑 TWO CASES HERE ARE EXPECTED TO FAIL, and their expectations are written as
- * the CORRECT behaviour rather than the current one. A case that documents a bug
- * as intended passes forever and locks the defect in. Both are known:
- *
- *   condition-options-are-all-saveable  the form offers Like New / Good / Fair
- *                                       (SellerProductShell.tsx:228-235) but
- *                                       productBaseSchema accepts only new /
- *                                       used / refurbished / broken
- *                                       (request-schemas.ts:155)
- *   description-requirement-is-honest   QuickProductForm labels description
- *                                       "Brief description (optional)" and never
- *                                       validates it, while the server requires
- *                                       >= 20 characters (:122-128)
- *
- * @tag domain:tester
- * @tag layer:seed
- * @tag pattern:none
- * @tag access:server-only
- * @tag consumers:seed-data/authored/index.ts
- * @tag sideEffects:none
- */
-const SIGN_IN_SELLER = "Sign in as tyson@beybladearena.in / TempPass123!.";
-export const authored = {
-    "checklist-selling-quick-add-minimum-details-quick-form-is-the-default": {
-        roles: ["seller"],
-        startPage: "/store/products/new",
-        steps: [
-            SIGN_IN_SELLER,
-            "Open /store/products/new without clicking anything else.",
-            "Read the heading and count the input fields on screen.",
-            "List the field labels in order.",
-            "Read whether a control offering the full form is present, and read its label.",
-            "Open /store/art/new and count its fields for comparison.",
-        ],
-        expectedBehaviour: "Creating an ordinary product opens the SHORT form, because most listings need six fields and the sectioned form asks for thirty. The full form stays one click away rather than being the default. Non-standard types (art, auctions) open the sectioned form directly, since they carry type-specific fields the short form has no room for.",
-        expectedUiState: "Six fields: Product Name, Category, Price, Product Image, Description, Stock Quantity — and a control reading 'Show all fields (advanced)'. /store/art/new shows the sectioned form instead.",
-        expectedData: { quickFormFields: 6 },
-        endResult: "Read-only; leave without saving.",
-    },
-    "checklist-selling-quick-add-minimum-details-publish-with-the-minimum": {
-        roles: ["seller"],
-        startPage: "/store/products/new",
-        steps: [
-            SIGN_IN_SELLER,
-            "Open /store/products/new.",
-            "Enter Product Name 'Minimum Details Probe'.",
-            "Pick Category 'Beyblade Burst'.",
-            "Enter Price 499.",
-            "Upload public/test-media/sample-image.png as the Product Image.",
-            "Enter Description 'A short-form listing created with only the required fields present.'",
-            "Click Publish and read what happens.",
-            "Open the product's public page at /products/{its slug} and read the title, price and image.",
-        ],
-        inputs: {
-            title: "Minimum Details Probe",
-            category: "Beyblade Burst",
-            price: 499,
-            image: "public/test-media/sample-image.png",
-            description: "A short-form listing created with only the required fields present.",
-        },
-        expectedBehaviour: "The short form can produce a real, published, buyable listing on its own. If it cannot, it is a decoy: the seller fills it, is refused, and has to learn the long form anyway — having already done the work twice.",
-        expectedUiState: "Publish succeeds with no inline errors and no error toast. The public page renders the title, ₹499 and the uploaded image.",
-        expectedData: { published: true },
-        endResult: "The listing survives a reload of the public page and appears in /store/products. Delete it afterwards.",
-    },
-    "checklist-selling-quick-add-minimum-details-advanced-flip-keeps-values": {
-        roles: ["seller"],
-        startPage: "/store/products/new",
-        steps: [
-            SIGN_IN_SELLER,
-            "Open /store/products/new.",
-            "Enter Product Name 'Flip Probe', Price 750, and Description 'Checking that switching to the full form keeps what was already typed.'",
-            "Pick Category 'Beyblade Burst'.",
-            "Click 'Show all fields (advanced)'.",
-            "Read the Title, Price, Description and Category fields in the sectioned form.",
-            "Read whether any value is blank that was filled a moment ago.",
-        ],
-        inputs: { title: "Flip Probe", price: 750, category: "Beyblade Burst" },
-        expectedBehaviour: "The flip changes the presentation, not the draft. Losing typed values on the way to the full form punishes the seller for outgrowing the short one, and teaches them to start with the long form every time — which defeats the point of having a short one.",
-        expectedUiState: "Title reads 'Flip Probe', Price 750, Category 'Beyblade Burst' and the description is intact in the sectioned form's Basic and Pricing sections.",
-        expectedData: { valuesPreserved: 4 },
-        endResult: "Leave without saving.",
-    },
-    "checklist-selling-quick-add-minimum-details-condition-options-are-all-saveable": {
-        roles: ["seller"],
-        startPage: "/store/products/new",
-        steps: [
-            SIGN_IN_SELLER,
-            "Open /store/products/new and click 'Show all fields (advanced)'.",
-            "Open the Basic section and read every option in the Condition dropdown, writing them all down.",
-            "Fill Product Name 'Condition Probe', Description 'Checking that every condition the form offers can actually be saved.', Category 'Beyblade Burst', Price 499 and a Product Image. The six labels are exactly: Product Name, Category, Price (₹), Stock Quantity, Description, Product Image — there is no field labelled Title or Main Image.",
-            "Select Condition 'Like New' and click Publish.",
-            "Read the result — inline error, toast, or success.",
-            "Repeat with 'Good', then with 'Fair', then with 'New', reading the result each time.",
-        ],
-        inputs: { title: "Condition Probe", price: 499, conditions: "Like New, Good, Fair, New" },
-        expectedBehaviour: "Every option the dropdown offers can be saved. A select that lists a value the server rejects is a trap with no way out — the seller picks the option that describes their item honestly and is refused, with nothing on screen saying which options are real.",
-        expectedUiState: "Publishing succeeds for EVERY option in the list, including Like New, Good and Fair. Any option that produces a validation failure is the finding — record which ones and quote the message.",
-        expectedData: { saveableConditions: "all options listed in the dropdown" },
-        endResult: "Each successful publish is visible on the public page with the chosen condition. Delete the listings afterwards.",
-    },
-    "checklist-selling-quick-add-minimum-details-description-requirement-is-honest": {
-        roles: ["seller"],
-        startPage: "/store/products/new",
-        steps: [
-            SIGN_IN_SELLER,
-            "Open /store/products/new.",
-            "Read the Description field's label and note exactly whether it says required or optional.",
-            "Fill Product Name 'Short Description Probe', Category 'Beyblade Burst', Price 499 and a Product Image.",
-            "Type exactly 'Nice bey' in Description — eight characters.",
-            "Click Publish and read what happens, and WHERE it appears.",
-            "If it was refused, read whether the message appeared on the Description field itself or somewhere else.",
-        ],
-        inputs: { title: "Short Description Probe", description: "Nice bey", price: 499 },
-        expectedBehaviour: "The form tells the truth about what it requires, and it tells it at the field. Either the description really is optional and a short one publishes, or it is required and the label says so with the minimum length stated. What must not happen is a field marked optional being refused by the server after the seller commits — that is the form making a promise the save does not keep.",
-        expectedUiState: "Label and behaviour agree. If a minimum length applies, the label states it and a short entry is caught inline on the Description field BEFORE publishing. A toast appearing after Publish, with the field itself showing no error, is the failure.",
-        expectedData: { errorShownInline: true },
-        endResult: "Either the listing publishes, or nothing is created and the form still holds what was typed. Delete anything created.",
-    },
-};

package/dist/features/tester/seed-data/authored/selling__sectionised-forms.d.ts

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

package/dist/features/tester/seed-data/authored/selling__sectionised-forms.js

@@ -1,191 +0,0 @@
-/*
- * WHY: Authored six-part procedures for the selling/sectionised-forms 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 FIRST AND LAST CASES ARE THE SAME ASSERTION AT TWO SCALES: saving a form
- * writes back only what changed. A form that submits its whole object from
- * partly-populated state overwrites every field it did not load, returns a normal
- * success, and is invisible without a reload — which is why both end in one.
- *
- * @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-sectionised-forms-form-sections-save-unchanged": {
-        roles: ["seller"],
-        startPage: "/store/products",
-        steps: [
-            "Sign in as tyson@beybladearena.in / TempPass123!.",
-            "Open the editor for 'Beyblade Burst B-01 Valkyrie' and expand every section.",
-            "Write down the value of every field in every section.",
-            "Change one field in ONE section — the description — and save.",
-            "RELOAD the editor and expand every section again.",
-            "Compare every field against what was written down.",
-            "Restore the description and save.",
-        ],
-        inputs: { productId: "product-beyblade-burst-valkyrie" },
-        expectedBehaviour: "Editing one section leaves every other section's values untouched. A sectionised form that submits its whole object from state populated only by the sections the user opened silently blanks the rest — and the save reports success either way.",
-        expectedUiState: "After the reload only the description differs. Every other field in every other section holds its original value, including images, category, brand, stock and the type-specific fields.",
-        expectedData: { unintendedFieldChanges: 0 },
-        endResult: "The product is restored. Any field that emptied itself is the failure, and it is invisible without expanding every section after the reload.",
-    },
-    "checklist-selling-sectionised-forms-form-error-summary-jumps": {
-        roles: ["seller"],
-        startPage: "/store/products/new",
-        steps: [
-            "Sign in as tyson@beybladearena.in / TempPass123!.",
-            "Open /store/products/new and read the page before typing — note whether any errors are listed.",
-            "Click 'Show all fields (advanced)' first. 🛑 /store/products/new opens the QUICK form for a standard create — six flat fields, NO sections at all — so every section, chevron and error-summary step below needs the advanced form, which is the sectionised one this page is about.",
-            "Leave required fields empty in two DIFFERENT sections.",
-            "Collapse both of those sections.",
-            "Attempt to publish.",
-            "Read the error summary and click an error belonging to a collapsed section.",
-        ],
-        expectedBehaviour: "The summary appears only after a submit is attempted, and clicking an entry expands the owning section and moves to the field. An error in a collapsed section is otherwise unreachable — the user is told something is wrong and cannot see what.",
-        expectedUiState: "No summary before the publish attempt. Afterwards it lists errors from both sections, tagged with their section. Clicking one expands that section and scrolls the field into view.",
-        endResult: "Nothing is published. Leave the editor without saving.",
-    },
-    "checklist-selling-sectionised-forms-required-section-has-no-dead-chevron": {
-        roles: ["seller"],
-        startPage: "/store/products/new",
-        steps: [
-            "Sign in as tyson@beybladearena.in / TempPass123!.",
-            "Open /store/products/new and look at every section header.",
-            "Click 'Show all fields (advanced)' first. 🛑 /store/products/new opens the QUICK form for a standard create — six flat fields, NO sections at all — so every section, chevron and error-summary step below needs the advanced form, which is the sectionised one this page is about.",
-            "Find any section that is always open because it is required.",
-            "Look at whether it still shows an expand chevron.",
-            "Click that chevron and read what happens.",
-            "Compare against a collapsible section's chevron.",
-        ],
-        expectedBehaviour: "A section that cannot collapse does not display a collapse control. A chevron that responds to nothing teaches the user the whole form's chevrons are unreliable, which is a worse cost than the one dead control.",
-        expectedUiState: "Always-open sections have no chevron, or their chevron is visibly non-interactive. A chevron that looks identical to a working one and does nothing on click is the failure.",
-        endResult: "Read-only; leave the editor without saving.",
-    },
-    "checklist-selling-sectionised-forms-open-section-does-not-clip-dropdowns": {
-        roles: ["seller"],
-        startPage: "/store/products/new",
-        steps: [
-            "Sign in as tyson@beybladearena.in / TempPass123!.",
-            "Open /store/products/new and expand a section containing a picker.",
-            "Click 'Show all fields (advanced)' first. 🛑 /store/products/new opens the QUICK form for a standard create — six flat fields, NO sections at all — so every section, chevron and error-summary step below needs the advanced form, which is the sectionised one this page is about.",
-            "Open that picker and read whether its full option list is visible.",
-            "Scroll while it is open and check it stays anchored to its field.",
-            "Open a picker in the LAST section of the form, near the bottom of the page.",
-            "Read whether its list is clipped by the section's own boundary.",
-            "Resize to 390 pixels wide and open the same picker.",
-        ],
-        inputs: { mobileWidth: 390 },
-        expectedBehaviour: "A picker's list escapes its section's bounds. A section with overflow hidden — which is what a collapsing container needs to animate — clips any list that opens inside it, so the options exist and cannot be seen.",
-        expectedUiState: "The full option list is visible in every case, including in the last section and at 390 pixels. A list cut off at the section's edge is the failure, and it is worst at the bottom of the form where there is least room.",
-        endResult: "Read-only; leave the editor without saving.",
-    },
-    "checklist-selling-sectionised-forms-error-jump-lands-on-the-field": {
-        roles: ["seller"],
-        startPage: "/store/products/new",
-        steps: [
-            "Sign in as tyson@beybladearena.in / TempPass123!.",
-            "Open /store/products/new and leave a required field empty in a section far down the form.",
-            "Click 'Show all fields (advanced)' first. 🛑 /store/products/new opens the QUICK form for a standard create — six flat fields, NO sections at all — so every section, chevron and error-summary step below needs the advanced form, which is the sectionised one this page is about.",
-            "Collapse that section and attempt to publish.",
-            "Click the error for that field in the summary.",
-            "Read where the page has scrolled to and whether the field is visible.",
-            /*
-             * 🛑 EXPECT THIS TO FAIL TODAY, AND RECORD IT AS A FAILURE.
-             *
-             * Measured 2026-09-29: FormErrorList's entire click handler is
-             * `onClick={() => ctx.goToStep(stepIndex!)}`. There is no focus() call,
-             * no scrollIntoView, and no element lookup — so it opens the owning
-             * section and stops, which is exactly what this case calls the failure.
-             *
-             * Kept as written rather than softened to match. The rationale holds: a
-             * section can carry a dozen fields, and an error summary that drops the
-             * user at the heading has told them something is wrong without showing
-             * them what. Softening it to "lands on the section" would convert a real
-             * UX gap into a passing case.
-             *
-             * So a tester who lands on the heading records a FAILURE with a
-             * screenshot — not "could not test", and not a lenient pass because the
-             * section did open.
-             */
-            "Check whether the field is focused and marked, not merely on screen.",
-        ],
-        expectedBehaviour: "Clicking an error lands ON the field — section expanded, field scrolled into view, focused and marked. Landing on the section heading leaves the user hunting through a section that may hold a dozen fields.",
-        expectedUiState: "The offending field is visible, focused, and carries its own error message. Scrolling to the section heading and stopping there is the failure, as is scrolling past the field so it sits under a sticky bar.",
-        endResult: "Nothing is published. Leave the editor without saving.",
-    },
-    "checklist-selling-sectionised-forms-long-form-typing-is-smooth": {
-        roles: ["seller"],
-        startPage: "/store/products/new",
-        steps: [
-            "Sign in as tyson@beybladearena.in / TempPass123!.",
-            "Open /store/products/new and expand every section.",
-            "Click 'Show all fields (advanced)' first. 🛑 /store/products/new opens the QUICK form for a standard create — six flat fields, NO sections at all — so every section, chevron and error-summary step below needs the advanced form, which is the sectionised one this page is about.",
-            "Type a long paragraph into the description field at normal speed.",
-            "Watch for characters lagging behind the keystrokes.",
-            "Attempt a publish so validation is running live, then keep typing into another field.",
-            "Watch again for lag.",
-        ],
-        expectedBehaviour: "Typing stays responsive with every section open and live validation running. Validation runs on every change once a submit has been attempted — that is what keeps the error summary current — so this is the state where a form is most likely to stutter.",
-        expectedUiState: "Characters appear as they are typed, with no visible catch-up. The error summary updates as fields are fixed without the field itself becoming laggy.",
-        endResult: "Nothing is published. Leave the editor without saving.",
-    },
-    "checklist-selling-sectionised-forms-form-mobile-action-bar": {
-        roles: ["seller"],
-        startPage: "/store/products/new",
-        steps: [
-            "Sign in as tyson@beybladearena.in / TempPass123!.",
-            "Resize the browser window to 390 pixels wide, open /store/products/new, and click 'Show all fields (advanced)' — the quick form has no sections and therefore no section-scoped error sheet, which is what this case reads.",
-            "Read the action bar at the bottom and every control in it.",
-            "Type into a field so the form becomes dirty and read the bar again.",
-            "Attempt a publish with fields missing and read what the bar shows.",
-            "Open the error sheet from the bar, close it, then attempt a publish again and check it reopens.",
-            "Count the fixed bars at the bottom.",
-        ],
-        inputs: { mobileWidth: 390 },
-        expectedBehaviour: "The form's save row and its error sheet occupy the same measured bottom tier as everything else. The sheet's label carries the error COUNT, because the panel only republishes when that label changes — a static label would freeze the sheet's contents while the user fixes fields. Reopening on a second failed submit is driven by a counter rather than a flag, so an ordinary re-render does not reopen what the user just closed.",
-        expectedUiState: "Discard, Save draft and Publish are all reachable and none is clipped. The sheet's label states how many issues remain and that number falls as fields are fixed. Closing it and submitting again reopens it. Exactly one bottom tab bar sits below the action bar.",
-        endResult: "Nothing is published. Restore the window width afterwards.",
-    },
-    "checklist-selling-sectionised-forms-form-conditional-fields-drop-values": {
-        roles: ["seller"],
-        startPage: "/store/products/new",
-        steps: [
-            "Sign in as tyson@beybladearena.in / TempPass123!.",
-            "Open /store/products/new and find a control that reveals conditional fields — a listing type or a shipping choice.",
-            "Click 'Show all fields (advanced)' first. 🛑 /store/products/new opens the QUICK form for a standard create — six flat fields, NO sections at all — so every section, chevron and error-summary step below needs the advanced form, which is the sectionised one this page is about.",
-            "Set it so the conditional fields appear and fill them in, noting each value.",
-            "Change the controlling field so those conditionals are hidden.",
-            "Change it back so they reappear.",
-            "Read whether the values are still there.",
-            "Publish and then reload the editor, reading those fields again.",
-        ],
-        expectedBehaviour: "A hidden conditional field either keeps its value or is genuinely dropped — but whichever it does, the saved record must match what the form displayed at submit. The dangerous case is a field that looks retained on screen and is dropped on save, or one dropped from view and still written.",
-        expectedUiState: "Toggling the controlling field back and forth leaves the conditional values in a state the form shows honestly. After publishing and reloading, the stored values match what was on screen when Publish was pressed.",
-        endResult: "Delete the created listing afterwards. A field the form showed and did not save is the failure, and so is one it hid and saved anyway.",
-    },
-    "checklist-selling-sectionised-forms-site-settings-save-still-writes-everything": {
-        roles: ["admin"],
-        startPage: "/admin/site",
-        steps: [
-            "Sign in as admin@letitrip.in / TempPass123!.",
-            "Open /admin/site and walk every tab, writing down a distinctive value from each.",
-            "Open one tab — Fees — and change a single field.",
-            "Save.",
-            "RELOAD /admin/site and walk every tab again.",
-            "Compare each noted value against what was written down.",
-            "Restore the changed field and save.",
-        ],
-        expectedBehaviour: "Saving one tab of the settings singleton preserves every other tab. This is the same defect as the first case at the largest possible scale: the whole document is one record, so a form submitting its full object from a partly-populated state can blank branding, fees, integrations and legal copy in one save that reports success.",
-        expectedUiState: "After the reload only the Fees field differs. Every noted value on every other tab is unchanged — branding, announcement copy, integrations, shipping, legal pages. The masked credentials are still shown as masked rather than blank.",
-        expectedData: { unintendedFieldChanges: 0 },
-        endResult: "The changed field is restored. This is the highest-blast-radius save in the application; check every tab rather than sampling two.",
-    },
-};

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

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