@mohasinac/appkit 4.57.0 → 4.59.0

package/dist/features/tester/seed-data/authored/account-auth__signup-login.js

@@ -1,329 +0,0 @@
-/*
- * WHY: Authored six-part procedures for the account-auth/signup-login checklist page.
- * WHAT: 15 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.
- *
- * 🛑 TWO CASES HERE CHANGE A PASSWORD, and each owns a persona nothing else uses —
- * `password-reset` has neha.op@gmail.com, `auth-email-links-single-use` has
- * divya.funko@gmail.com. `seed-cli` sets `TempPass123!` only when it CREATES an
- * Auth record and never resets an existing one, so a changed password outlives
- * every future re-seed. Both cases restore it in their last step. They used to
- * point at vivaan.kapoor@gmail.com, which four other authored pages sign in as.
- *
- * 🛑 THE GOOGLE CASES NEED REAL GOOGLE CREDENTIALS and cannot be seeded — a
- * provider link lives in Firebase Auth, not Firestore. They are NOT flagged
- * `needsReview`: their intent is perfectly clear, and a case that cannot be
- * reached is a `null` verdict at run time, not an authoring doubt. Confusing the
- * two hides the unwritten cases inside the unanswerable ones.
- *
- * @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-account-auth-signup-login-auth-email-links-single-use": {
-        roles: ["guest"],
-        startPage: "/auth/forgot-password",
-        steps: [
-            "Open /auth/forgot-password.",
-            "Type divya.funko@gmail.com in the 'Email address' field.",
-            "Click 'Send reset link'.",
-            "Open the inbox for divya.funko@gmail.com and copy the reset link URL out of the email before opening it.",
-            "Open the copied URL, type QaSingleUse789! as the new password, confirm it, and submit.",
-            "Open the same copied URL a second time.",
-            "Register a fresh account at /auth/register using an inbox you can open, then open its verification link once, and then open that same link a second time.",
-            "Open /auth/forgot-password, request a link for divya.funko@gmail.com again, and use it to set the password back to TempPass123!.",
-        ],
-        inputs: {
-            email: "divya.funko@gmail.com",
-            newPassword: "QaSingleUse789!",
-            restoredPassword: "TempPass123!",
-        },
-        expectedBehaviour: "The action code in each link is one-time. The second open is refused by Firebase and the site turns that refusal into readable English with a way to get a fresh link. No second password change is applied and no second verification is recorded.",
-        expectedUiState: "On the second open of the reset link: a message in the shape of 'This link has already been used or has expired', plus a control to request a new one. Not a blank page, not a raw 'auth/invalid-action-code', not a stack trace, and not a working password form. The second open of the verification link reads the same way.",
-        expectedData: { passwordChangesApplied: 1 },
-        endResult: "Account state after the second click is identical to after the first. divya.funko@gmail.com is back on TempPass123! by the final step — skipping that restore leaves the account unusable by every later case, since the seeder never resets an existing password.",
-    },
-    "checklist-account-auth-signup-login-auth-emails-sender-identity-and-inbox": {
-        roles: ["guest"],
-        startPage: "/auth/register",
-        steps: [
-            "Open /auth/register.",
-            "Type QA Sender Test in 'Full name', a real Gmail address you can open in 'Email address', TestPass123! in both password fields, tick the terms checkbox, and click 'Create account'.",
-            "Open that Gmail inbox, checking the Spam and Promotions tabs as well, and find the verification email.",
-            "Read its From name and From address, and open the link inside it.",
-            "Open /auth/forgot-password, type the same Gmail address, and click 'Send reset link'.",
-            "Open the Gmail inbox again, find the password-reset email, and read its From name and From address.",
-            "Repeat both flows with a non-Gmail address if one is available, and check that inbox the same way.",
-        ],
-        inputs: { fullName: "QA Sender Test", password: "TestPass123!" },
-        expectedBehaviour: "Both emails are delivered to the inbox within a few minutes, from the site's own configured sender. The links inside resolve to the live site and complete their flows rather than 404ing or landing on a Firebase-hosted page the site does not control.",
-        expectedUiState: "The From display name is spelled 'LetItRip' exactly — not 'Letitrip', not 'LetiTrip', not 'letitrip.in'. Both messages sit in the Primary inbox, not Spam or Promotions. Clicking through opens letitrip.in and the flow finishes.",
-        expectedData: { senderDisplayName: "LetItRip" },
-        endResult: "Verification marks the new account verified and the reset link changes its password. If Gmail and non-Gmail were both tried, note in the comment whether delivery differed — that difference is the point of testing two providers.",
-    },
-    "checklist-account-auth-signup-login-email-signup": {
-        roles: ["guest"],
-        startPage: "/auth/register",
-        steps: [
-            "Open /auth/register.",
-            "Type QA Signup Tester in the 'Full name' field.",
-            /*
-             * 🛑 SUBSTITUTE THE RUN ID — this is the one input in the catalogue that
-             * is deliberately not literal.
-             *
-             * `users` is PRESERVE tier: it survives every catalogue wipe, so an
-             * account created here is permanent and the harness cannot clean it up.
-             * The previous instruction ("increment the number if it already exists")
-             * made that explicit and unbounded — one more dead account per run,
-             * forever.
-             *
-             * A run-stamped address under `letitrip-qa.test` fixes both halves:
-             * the address is unique per run so signup never collides, and
-             * `.test` is an RFC 2606 reserved TLD that can never be registered and
-             * can never receive mail — so no real person can ever hold one, which is
-             * what makes `tester/scripts/purge-qa-signups.mjs` safe to point at the
-             * PRESERVE tier at all.
-             *
-             * Run that purge after the run to remove exactly these accounts.
-             */
-            "Type qa-signup+<runId>@letitrip-qa.test in the 'Email address' field, substituting the current run id — e.g. qa-signup+run-1789483929743@letitrip-qa.test.",
-            "Type TestPass123! in the 'Password' field.",
-            "Type TestPass123! in the 'Confirm password' field.",
-            "Tick the 'I accept the terms' checkbox.",
-            "Click 'Create account'.",
-            "Open /user.",
-        ],
-        inputs: {
-            fullName: "QA Signup Tester",
-            email: "qa-signup+<runId>@letitrip-qa.test",
-            password: "TestPass123!",
-        },
-        expectedBehaviour: "A Firebase Auth record and a matching Firestore user document are created, keyed on the Auth uid rather than on a generated user-* slug. A verification email is dispatched. The browser is signed in and moved off /auth/register.",
-        expectedUiState: "The address bar leaves /auth/register for / or /user, and the header shows a signed-in avatar with no 'Sign in' link. Submitting the same address a second time is refused with a readable 'email already in use' message, not a duplicate account.",
-        expectedData: { displayName: "QA Signup Tester" },
-        endResult: "Reloading /user shows 'QA Signup Tester' and the address used. The account persists — this case creates a real row that a later teardown does not remove, which is why the address is numbered rather than fixed.",
-    },
-    "checklist-account-auth-signup-login-email-verify": {
-        roles: ["guest"],
-        startPage: "/auth/register",
-        steps: [
-            "Open /auth/register and create an account with an inbox you can open, using TestPass123! as the password.",
-            "Open the inbox and find the verification email from Firebase.",
-            "Open the verification link in the email.",
-            "Open /auth/login and sign in with that account.",
-            "Open /user.",
-        ],
-        inputs: { password: "TestPass123!" },
-        expectedBehaviour: "Following the link flips the account's emailVerified flag in Firebase Auth, and the site reads that flag rather than a separate copy of its own. The verified state survives sign-out and sign-in.",
-        expectedUiState: "The link lands on a confirmation page. After signing in, /user carries no 'Your email is not verified' banner and no prompt to resend the verification email.",
-        expectedData: { emailVerified: true },
-        endResult: "Reloading /user still shows no verification warning. An account that reads as unverified after a successful link click is the failure this case catches.",
-    },
-    "checklist-account-auth-signup-login-forgot-password-no-account-enumeration": {
-        roles: ["guest"],
-        startPage: "/auth/forgot-password",
-        steps: [
-            "Open /auth/forgot-password.",
-            "Type nobody-here-12345@example.com in the 'Email address' field.",
-            "Click 'Send reset link'.",
-            "Read the resulting message and note its exact wording.",
-            "Reload /auth/forgot-password, type rehan.sheikh@gmail.com, and click 'Send reset link'.",
-            "Read that message and compare the two word for word.",
-        ],
-        inputs: { unknownEmail: "nobody-here-12345@example.com", knownEmail: "rehan.sheikh@gmail.com" },
-        expectedBehaviour: "The browser calls Firebase directly, so it is the client that must swallow auth/user-not-found. Both submissions produce the identical generic response; nothing in the message, the timing or an error toast distinguishes an address that has an account from one that does not.",
-        expectedUiState: "Both attempts show the same text — 'If an account exists for that email, a reset link is on its way.' or equivalent. The unknown address produces no red toast, no 'user not found', no field-level error, and no different button state.",
-        endResult: "No email arrives for nobody-here-12345@example.com. The two on-screen responses were indistinguishable, which is the whole point — a difference of any kind is an account-enumeration leak.",
-    },
-    "checklist-account-auth-signup-login-google-link-confirmation-shown": {
-        requiresHumanChannel: true,
-        humanChannelReason: "interactive Google account",
-        roles: ["buyer"],
-        startPage: "/user",
-        steps: [
-            "Sign in as an account that already has Google linked — or link one first through /user/settings > 'Linked Accounts' > 'Connect Google'.",
-            "Open /user.",
-            "Read the alert area near the top of the dashboard.",
-            "Reload the page.",
-        ],
-        expectedBehaviour: "The dashboard handles the linked case explicitly, not just by omitting the unlinked prompt. Before this was fixed the whole alert block disappeared once linked, so a user had no confirmation on /user at all — only Settings showed a Connected badge.",
-        expectedUiState: "A green confirmation alert reading 'Google account connected', carrying a Connected badge and the linked Google email address. The blue 'Connect your Google account' prompt is absent. An empty space where the alert used to be is a fail, not a pass.",
-        endResult: "After reload the green confirmation is still there and the blue prompt has not returned. Needs a Google account to reach — answer null with that reason rather than guessing if none is available.",
-    },
-    "checklist-account-auth-signup-login-google-link-conflict-rejected": {
-        requiresHumanChannel: true,
-        humanChannelReason: "interactive Google account",
-        roles: ["buyer"],
-        startPage: "/user/settings",
-        steps: [
-            "Sign in as rehan.sheikh@gmail.com / TempPass123!.",
-            "Open /user/settings, expand 'Linked Accounts', click 'Connect Google', and complete the popup with a Google account G.",
-            "Sign out.",
-            "Sign in as vivaan.kapoor@gmail.com / TempPass123!.",
-            "Open /user/settings.",
-            "Expand the 'Linked Accounts' accordion.",
-            "Click 'Connect Google'.",
-            "Select the same Google account G in the popup and complete the flow.",
-            "Reload /user/settings and expand 'Linked Accounts'.",
-        ],
-        inputs: { accountA: "vivaan.kapoor@gmail.com", accountB: "rehan.sheikh@gmail.com" },
-        expectedBehaviour: "The second link is refused because G already belongs to rehan.sheikh@gmail.com. Neither account is modified: the two are not merged, and G's email is not moved from one to the other. A silent merge here would join two people's orders, addresses and wishlists.",
-        expectedUiState: "A readable error in the shape of 'This Google account is already linked to another account'. vivaan.kapoor@gmail.com still shows a 'Connect Google' button, not a Connected badge.",
-        endResult: "After reload vivaan.kapoor@gmail.com has no Google link and rehan.sheikh@gmail.com still has G. Unlink G from rehan.sheikh@gmail.com afterwards. Needs a real Google account — answer null if none is available.",
-    },
-    "checklist-account-auth-signup-login-google-link-different-email": {
-        requiresHumanChannel: true,
-        humanChannelReason: "interactive Google account",
-        roles: ["buyer"],
-        startPage: "/user/settings",
-        steps: [
-            "Sign in as vivaan.kapoor@gmail.com / TempPass123!.",
-            "Open /user/settings.",
-            "Expand the 'Linked Accounts' accordion.",
-            "Click 'Connect Google'.",
-            "Select a Google account whose email is NOT vivaan.kapoor@gmail.com, and complete the popup.",
-            "Reload /user/settings and expand 'Linked Accounts'.",
-            "Sign out, open /auth/login, and click 'Sign in with Google' choosing that same Google account.",
-        ],
-        inputs: { primaryEmail: "vivaan.kapoor@gmail.com" },
-        expectedBehaviour: "Linking a differently-addressed Google account requires this explicit button press — it never happens as a side effect of merely signing in with Google. One account now answers to two emails; a second account is not created. The primary login email is unchanged.",
-        expectedUiState: "'Linked Accounts' shows Google as Connected and displays the OTHER email. The account's own email elsewhere in Settings still reads vivaan.kapoor@gmail.com. Signing in with that Google account afterwards lands in this same account, with its existing orders and wishlist.",
-        expectedData: { primaryEmail: "vivaan.kapoor@gmail.com" },
-        endResult: "After reload the link persists and the primary email is still vivaan.kapoor@gmail.com. Unlink afterwards. Needs a second Google account — answer null if none is available.",
-    },
-    "checklist-account-auth-signup-login-google-link-existing": {
-        requiresHumanChannel: true,
-        humanChannelReason: "interactive Google account",
-        roles: ["guest"],
-        startPage: "/auth/register",
-        steps: [
-            "Open /auth/register.",
-            "Type QA Google Merge in 'Full name', the email address of a Google account you control in 'Email address', TestPass123! in both password fields, tick the terms checkbox, and click 'Create account'.",
-            "Add any product to the wishlist so the account has something identifying in it.",
-            "Sign out.",
-            "Open /auth/login.",
-            "Click 'Sign in with Google'.",
-            "Select that same Google account in the popup and complete it.",
-            "Open /wishlist.",
-            "Open /user/settings and expand 'Linked Accounts'.",
-        ],
-        inputs: { fullName: "QA Google Merge", password: "TestPass123!" },
-        expectedBehaviour: "Because the Google email matches an existing password account exactly, the sign-in resolves to that same account automatically — no duplicate, and no explicit linking step asked of the user. Google is recorded as connected as a side effect.",
-        expectedUiState: "No 'create account' step appears after the popup. The header shows 'QA Google Merge', and /wishlist still holds the item added before signing out — the proof it is the same account and not a fresh one wearing the same email. 'Linked Accounts' shows Google Connected.",
-        expectedData: { displayName: "QA Google Merge" },
-        endResult: "One account exists for that email, not two, and it kept its wishlist. Needs a Google account whose address you can also register with — answer null if none is available.",
-    },
-    "checklist-account-auth-signup-login-google-oauth": {
-        requiresHumanChannel: true,
-        humanChannelReason: "interactive Google account",
-        roles: ["guest"],
-        startPage: "/auth/login",
-        steps: [
-            "Open /auth/login.",
-            "Click 'Sign in with Google'.",
-            "Complete the Google popup by choosing an account.",
-            "Wait for the popup to close and the site to respond.",
-            "Open /user.",
-        ],
-        expectedBehaviour: "The popup opens, Google authenticates, the popup closes, and the site establishes its own session cookie from the returned credential. An account is created if the email is new, or signed into if it already exists.",
-        expectedUiState: "The address bar leaves /auth/login. The header shows a signed-in avatar and no 'Sign in' link. No error toast, and no popup left hanging open after authentication.",
-        endResult: "Reloading /user keeps the session. Needs a Google account — answer null with that reason if none is available.",
-    },
-    "checklist-account-auth-signup-login-google-popup-blocked-fallback": {
-        requiresHumanChannel: true,
-        humanChannelReason: "interactive Google account",
-        roles: ["guest"],
-        startPage: "/auth/login",
-        steps: [
-            "Set the browser to block popups for letitrip.in.",
-            "Open /auth/login.",
-            "Click 'Sign in with Google'.",
-            "Leave the blocked-popup notification alone without unblocking it.",
-            "Wait up to 30 seconds and watch the page.",
-            "Open /user.",
-        ],
-        expectedBehaviour: "The site notices the popup never opened and falls back — either to a full-page redirect flow, or to the RTDB signal plus postMessage path — and completes sign-in without asking the user to change browser settings.",
-        expectedUiState: "Within 30 seconds the page reaches a signed-in state: avatar in the header, no 'Sign in' link. What must NOT happen is a button stuck in a loading state forever, or an error toast telling the user to allow popups and nothing else.",
-        endResult: "Reloading /user keeps the session. Needs a Google account plus popup blocking — answer null if either is unavailable.",
-    },
-    "checklist-account-auth-signup-login-login": {
-        roles: ["guest"],
-        startPage: "/auth/login",
-        steps: [
-            "Open /auth/login.",
-            "Type vivaan.kapoor@gmail.com in the 'Email address' field.",
-            "Type TempPass123! in the 'Password' field.",
-            "Click 'Sign in'.",
-            "Open /user.",
-        ],
-        inputs: { email: "vivaan.kapoor@gmail.com", password: "TempPass123!" },
-        expectedBehaviour: "Firebase validates the credential, the site exchanges it for its own __session cookie, and the browser is moved off /auth/login. A wrong password is refused with a readable message rather than a raw Firebase code.",
-        expectedUiState: "The address bar leaves /auth/login for / or /user, and the header shows the avatar for Vivaan Kapoor. No error toast.",
-        expectedData: { signedInUid: "user-seto-kaiba" },
-        endResult: "Reloading /user keeps the session as user-seto-kaiba. Every seeded account uses TempPass123!, so no separate credential lookup is needed.",
-    },
-    "checklist-account-auth-signup-login-logout": {
-        roles: ["buyer"],
-        startPage: "/user",
-        steps: [
-            "Sign in as vivaan.kapoor@gmail.com / TempPass123!.",
-            "Open /user.",
-            "Click 'Log out' in the sidebar.",
-            "Open /user again.",
-        ],
-        expectedBehaviour: "Both halves of the session end: the server __session cookie is cleared and the Firebase client session is revoked. Clearing only one leaves the browser able to re-mint a session on the next request, which is what makes the second navigation the real check.",
-        expectedUiState: "After Log out the page redirects and the header shows the signed-out state. Opening /user afterwards redirects to /auth/login rather than rendering the dashboard, even briefly with real data in it.",
-        expectedData: { redirectTarget: "/auth/login" },
-        endResult: "Navigating to /user lands on /auth/login and no data for Vivaan Kapoor is rendered at any point. A back-button press does not restore the dashboard.",
-    },
-    "checklist-account-auth-signup-login-password-reset": {
-        roles: ["guest"],
-        startPage: "/auth/login",
-        steps: [
-            "Open /auth/login.",
-            "Click 'Forgot password?'.",
-            "Type neha.op@gmail.com in the 'Email address' field.",
-            "Click 'Send reset link'.",
-            "Open the inbox for neha.op@gmail.com and open the reset link.",
-            "Type QaReset321! as the new password, confirm it, and submit.",
-            "Open /auth/login, type neha.op@gmail.com and TempPass123!, and click 'Sign in'.",
-            "Type neha.op@gmail.com and QaReset321! instead, and click 'Sign in'.",
-            "Request another reset link for neha.op@gmail.com and use it to set the password back to TempPass123!.",
-        ],
-        inputs: {
-            email: "neha.op@gmail.com",
-            newPassword: "QaReset321!",
-            restoredPassword: "TempPass123!",
-        },
-        expectedBehaviour: "The reset email arrives, its link opens a set-password form, and the submitted password replaces the old one in Firebase Auth. The old password stops working at that moment — a reset that leaves both passwords valid is the failure worth catching.",
-        expectedUiState: "'Send reset link' produces the generic 'If an account exists for that email…' message. Signing in with TempPass123! after the reset is refused with a readable error; signing in with QaReset321! succeeds and lands on the dashboard.",
-        endResult: "The password is back at TempPass123! by the final step. That restore is mandatory: the seeder never resets an existing password, so skipping it leaves this account permanently signed out of every later case.",
-    },
-    "checklist-account-auth-signup-login-signup-verification-email-arrives": {
-        roles: ["guest"],
-        startPage: "/auth/register",
-        steps: [
-            "Open /auth/register.",
-            "Type QA Verify Tester in the 'Full name' field.",
-            "Type a real inbox address you can open in the 'Email address' field.",
-            "Type TestPass123! in the 'Password' field.",
-            "Type TestPass123! in the 'Confirm password' field.",
-            "Tick the 'I accept the terms' checkbox.",
-            "Click 'Create account'.",
-            "Open that inbox, checking Spam as well, and wait up to five minutes.",
-            "Open the verification link in the email.",
-        ],
-        inputs: { fullName: "QA Verify Tester", password: "TestPass123!" },
-        expectedBehaviour: "Firebase's client SDK sends the verification mail directly, so it carries Firebase's own template and sender rather than the branded LetItRip one. The link resolves to the live site and marks the account verified. The on-screen 'check your email' message is not the thing being tested — the arrival is.",
-        expectedUiState: "An email is present in the inbox within a few minutes. It looks like Firebase's default template, and that difference from the branded Resend emails is expected here, not a defect. Its link opens letitrip.in and reports success.",
-        expectedData: { emailVerified: true },
-        endResult: "Signing in and reloading /user shows no 'email not verified' warning. A 'check your email' screen with no email ever arriving is exactly the failure this case exists to separate from success.",
-    },
-};

package/dist/features/tester/seed-data/authored/addresses__address-filters.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/addresses__address-filters.js

@@ -1,41 +0,0 @@
-/*
- * WHY: Authored six-part procedures for the addresses/address-filters page.
- * WHAT: 1 case, keyed by full checklist id.
- *
- * Written by hand, case by case, against the label each one states. There is no
- * generator: the authoring scripts were deleted once it was clear they were
- * scaffolding around work that is simply writing.
- *
- * @tag domain:tester
- * @tag layer:seed
- * @tag pattern:none
- * @tag access:server-only
- * @tag consumers:seed-data/authored/index.ts
- * @tag sideEffects:none
- */
-export const authored = {
-    "checklist-addresses-address-filters-filters-actually-filter": {
-        roles: ["buyer"],
-        startPage: "/user/addresses",
-        steps: [
-            "Sign in as rehan.sheikh@gmail.com / TempPass123!.",
-            "Open /user/addresses. No address is seeded for this buyer, so create two — one labelled 'Home' at '7 Test Lane', Indore, Madhya Pradesh, 452010, and one labelled 'Office' at '8 Test Lane', Bengaluru, Karnataka, 560001.",
-            "Back on /user/addresses, read the controls above the list: a Search input and a Label select. There is no filter drawer and no filter badge.",
-            "Type Indore in Search and read which addresses remain.",
-            "Clear Search, type zzzznope, and read the count.",
-            "Clear Search. Choose Office in the Label select and read which addresses remain.",
-            "Set the Label select back to 'All labels' and confirm both return.",
-            "Finally type Office into Search, with the Label select on All labels, and read the result.",
-        ],
-        inputs: {
-            firstLabel: "Home",
-            secondLabel: "Office",
-            searchHit: "Indore",
-            searchMiss: "zzzznope",
-        },
-        expectedBehaviour: "Both controls narrow the list they sit above, and both are in-memory over the already-fetched addresses rather than a refetch. Search matches the name, street, city, state and postal code; the Label select matches the label, which Search deliberately does not cover. A control that changes nothing is the failure this case exists for.",
-        expectedUiState: "Searching Indore leaves the Indore address and hides the Bengaluru one. 'zzzznope' leaves NONE — that is the control that separates filtering from returning everything. Choosing Office in the Label select leaves only the Office address, and 'All labels' restores both.\n\n🛑 Typing Office into SEARCH returns nothing, and that is CORRECT: search covers name, street, city, state and postal code, not the label. Do not record it as broken search. The Label select does not appear at all until at least one address has a label.",
-        expectedData: { searchMissCount: 0, labelFilteredCount: 1 },
-        endResult: "Both controls are cleared. Delete the two addresses afterwards — the addresses collection is PRESERVE tier and is never wiped between runs, so anything left here accumulates forever."
-    },
-};

package/dist/features/tester/seed-data/authored/addresses__postal-lookup.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/addresses__postal-lookup.js

@@ -1,76 +0,0 @@
-/*
- * WHY: Authored six-part procedures for the addresses/postal-lookup page.
- * WHAT: 3 case(s), keyed by full checklist id.
- *
- * Written by hand, case by case, against the label each one states. There is no
- * generator: the authoring scripts were deleted once it was clear they were
- * scaffolding around work that is simply writing.
- *
- * The three cases are hit / don't-clobber / miss. The miss is the one that
- * matters most: coverage is thinner than India Post's, so an unrecognised code
- * is the COMMON path and has to be a non-event rather than an error state.
- *
- * @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-addresses-postal-lookup-pin-fills-city-and-state": {
-        roles: ["buyer"],
-        startPage: "/user/addresses/new",
-        steps: [
-            "Sign in as rehan.sheikh@gmail.com / TempPass123!.",
-            "Open /user/addresses/new.",
-            "Select India as the country.",
-            "Leave the City and State fields empty.",
-            "Type 560001 in the PIN code field.",
-            "Wait one second without typing anything else.",
-            "Read the City field and the 'State / region' picker, then read the rest of the form.",
-            "If neither filled, open the network panel and find the api.zippopotam.us request before judging.",
-        ],
-        inputs: { country: "India", pincode: "560001", expectedState: "Karnataka" },
-        expectedBehaviour: "A complete PIN code triggers one debounced lookup that fills only City and State. Nothing else on the form moves — a lookup that also rewrites the street or the label is doing more than it was asked and the user has no way to undo it.",
-        expectedUiState: "Within about half a second City and 'State / region' are filled for 560001; the state reads Karnataka. Record the city string rather than asserting one — it is whatever Zippopotam returns for that code. Every other field holds exactly what it held before, including any name or street already typed. No spinner is left running and no error appears.",
-        expectedData: { pincode: "560001" },
-        endResult: "Nothing is saved unless the form is submitted. Two dead modules once carried the shape of a lookup that had been removed, which is why this looked built long before it was.",
-    },
-    "checklist-addresses-postal-lookup-lookup-never-overwrites": {
-        roles: ["buyer"],
-        startPage: "/user/addresses/new",
-        steps: [
-            "Sign in as rehan.sheikh@gmail.com / TempPass123!.",
-            "Open /user/addresses/new.",
-            "Select India as the country.",
-            "Type Whitefield in the City field FIRST, before touching the PIN code.",
-            "Type 560001 in the PIN code field.",
-            "Wait one second.",
-            "Read the City field.",
-        ],
-        inputs: { country: "India", city: "Whitefield", pincode: "560001" },
-        expectedBehaviour: "Autofill only ever lands in an EMPTY field. A lookup that corrects deliberate typing produces a bug the user cannot report — they simply watch their own text disappear and assume they mistyped.",
-        expectedUiState: "City still reads 'Whitefield' after the lookup completes. 'State / region', which was empty, has been filled. Nothing flashes the typed value away and back.",
-        expectedData: { city: "Whitefield" },
-        endResult: "Nothing persists until the form is submitted. 'Whitefield' is chosen because it is a real Bengaluru locality that the 560001 lookup will not return — a city name the lookup agrees with would prove nothing.",
-    },
-    "checklist-addresses-postal-lookup-lookup-miss-is-a-non-event": {
-        roles: ["buyer"],
-        startPage: "/user/addresses/new",
-        steps: [
-            "Sign in as rehan.sheikh@gmail.com / TempPass123!.",
-            "Open /user/addresses/new.",
-            "Select India as the country.",
-            "Type 999999 in the PIN code field.",
-            "Wait two seconds and read the whole form.",
-            "Type 'QA Address lookup-miss' as the name, '3 Test Lane' as the street and 'Indore' as the city, then SELECT 'Madhya Pradesh' from the 'State / region' picker — for India it is a 36-option list, not a text box.",
-            "Save the address.",
-        ],
-        inputs: { country: "India", pincode: "999999", city: "Indore", state: "Madhya Pradesh" },
-        expectedBehaviour: "An unknown but well-formed code resolves to nothing and the form carries on. The code is still valid — six digits — so it must save; only the convenience lookup missed.",
-        expectedUiState: "No error banner, no red PIN code field, no disabled Save. City stays empty and editable and the 'State / region' picker stays on its placeholder, and the typed and selected values are accepted. The address saves with PIN code 999999, which matches the IN postal pattern of six digits not starting with zero.",
-        expectedData: { pincode: "999999", saved: true },
-        endResult: "The address exists in /user/addresses after a reload. Delete it afterwards. Treating a miss as a validation failure would block every address in the many areas the lookup does not cover.",
-    },
-};

package/dist/features/tester/seed-data/authored/addresses__postal-validation.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/addresses__postal-validation.js

@@ -1,78 +0,0 @@
-/*
- * WHY: Authored six-part procedures for the addresses/postal-validation page.
- * WHAT: 3 case(s), keyed by full checklist id.
- *
- * Written by hand, case by case, against the label each one states. There is no
- * generator: the authoring scripts were deleted once it was clear they were
- * scaffolding around work that is simply writing.
- *
- * @tag domain:tester
- * @tag layer:seed
- * @tag pattern:none
- * @tag access:server-only
- * @tag consumers:seed-data/authored/index.ts
- * @tag sideEffects:none
- */
-export const authored = {
-    "checklist-addresses-postal-validation-letters-rejected-on-the-field": {
-        roles: ["buyer"],
-        startPage: "/user/addresses/new",
-        steps: [
-            "Sign in as rehan.sheikh@gmail.com / TempPass123!.",
-            "Open /user/addresses/new.",
-            "Select India as the country.",
-            "Type 'QA Address letters-rejected' as the name, '4 Test Lane' as the street and 'Indore' as the city, then SELECT 'Madhya Pradesh' from the 'State / region' picker.",
-            "Type abcdef in the PIN code field.",
-            "Click Save.",
-            "Read where the error appears.",
-        ],
-        inputs: { country: "India", pincode: "abcdef" },
-        expectedBehaviour: "The format is checked in the browser against the country's own rule, so the request is never sent. A length-only rule passes 'abcdef' — six characters — which is exactly how one admin route treated it as a valid Indian PIN code.",
-        expectedUiState: "An error appears directly under the PIN code field naming the format, before any network request. There is no server 400 with nothing marked, and no error banner detached from the field that caused it.",
-        expectedData: { saved: false },
-        endResult: "No address is created. The form keeps the other typed values so the user only has to fix the one field.",
-    },
-    "checklist-addresses-postal-validation-country-decides-the-rule": {
-        roles: ["buyer"],
-        startPage: "/user/addresses/new",
-        steps: [
-            "Sign in as rehan.sheikh@gmail.com / TempPass123!.",
-            "Open /user/addresses/new.",
-            "Select Canada as the country.",
-            "Read the label on the postal code field.",
-            "Type K1A 0B1 in that field, then fill the name 'QA Address country-rule', the street '5 Test Lane' and the city 'Ottawa', and SELECT 'Ontario' from the 'State / region' picker — Canada has one too.",
-            "Click Save.",
-            "Open the address for editing, switch the country to India, and type K1A 0B1 in the PIN code field.",
-            "Type 560001 instead and read the field.",
-        ],
-        inputs: { canadaPostcode: "K1A 0B1", indiaPincode: "560001" },
-        expectedBehaviour: "The postal rule and its label both follow the selected country. An India-only six-digit rule made every real Canadian postcode unsaveable from every surface in the app.",
-        expectedUiState: "With Canada selected the field is labelled 'Postal code' and K1A 0B1 saves. With India selected the field is labelled 'PIN code', K1A 0B1 is rejected, and 560001 is accepted. The rejection is on the field, not a banner.",
-        expectedData: { canadaAccepted: true, indiaRejectsCanadaFormat: true },
-        endResult: "Delete the address afterwards. The reversal is the whole case — a rule that accepts both formats for both countries is not country-aware, it is just permissive.",
-    },
-    "checklist-addresses-postal-validation-unknown-country-never-blocks": {
-        roles: ["buyer"],
-        startPage: "/user/addresses/new",
-        steps: [
-            "Sign in as rehan.sheikh@gmail.com / TempPass123!.",
-            "Open /user/addresses/new.",
-            "Select United Arab Emirates as the country.",
-            "Type 'QA Address unknown-country' as the name, '6 Test Lane' as the street and 'Dubai' as the city.",
-            "Type 00000 in the postal code field.",
-            "Click Save.",
-            "Open the address for editing, replace the postal code with ABC-1234, and save again.",
-        ],
-        inputs: {
-            country: "United Arab Emirates",
-            firstCode: "00000",
-            secondCode: "ABC-1234",
-            postalMin: 3,
-            postalMax: 12,
-        },
-        expectedBehaviour: "For a country with no known format any code of 3 to 12 characters is accepted, which is the POSTAL_MIN and POSTAL_MAX fallback in the one shared validator. A postal rule exists to catch a typo, never to refuse a real address whose pattern we simply do not have — and an EMPTY code is still refused, because a blank is not a postal code in any country.",
-        expectedUiState: "Both codes save without an error. The field is not marked red and Save is never disabled. What must not happen is India's six-digit rule being applied by default to a country it does not describe.",
-        expectedData: { bothCodesAccepted: true },
-        endResult: "The address holds ABC-1234 after a reload. Delete it afterwards.",
-    },
-};

package/dist/features/tester/seed-data/authored/addresses__state-picker.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/addresses__state-picker.js

@@ -1,59 +0,0 @@
-/*
- * WHY: Authored six-part procedures for the addresses/state-picker page.
- * WHAT: 2 case(s), keyed by full checklist id.
- *
- * Written by hand, case by case, against the label each one states. There is no
- * generator: the authoring scripts were deleted once it was clear they were
- * scaffolding around work that is simply writing.
- *
- * @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-addresses-state-picker-state-is-a-picker-for-india": {
-        roles: ["buyer"],
-        startPage: "/user/addresses/new",
-        steps: [
-            "Sign in as rehan.sheikh@gmail.com / TempPass123!.",
-            "Open /user/addresses/new.",
-            "Select India as the country.",
-            "Click the 'State / region' field and try to type free text into it.",
-            "Type karn in the picker's search box and read the options offered.",
-            "Select Karnataka.",
-            "Change the country to United Arab Emirates.",
-            "Click 'State / region' again and try to type free text.",
-        ],
-        inputs: { country: "India", stateSearch: "karn", state: "Karnataka" },
-        expectedBehaviour: "Where a country's regions are enumerated, State is a searchable picker; where they are not, it is a plain text box. The picker is what stops one column holding 'Karnataka', 'karnataka' and 'KA' depending on which screen created the row — which is what happened while this form and the seller drawer wrote free text into the same field the admin editor filled from a 36-option list.",
-        expectedUiState: "With India selected, 'State / region' cannot be typed into freely and searching 'karn' narrows a list of India's 36 states and union territories to Karnataka. With United Arab Emirates selected the same label becomes an ordinary text input that accepts anything, because the UAE has no subdivisions in the registry.",
-        expectedData: { indiaStateOptionCount: 36 },
-        endResult: "Nothing persists unless the form is submitted. A picker offering 28 or 29 options is missing the union territories.",
-    },
-    "checklist-addresses-state-picker-changing-country-clears-state": {
-        roles: ["buyer"],
-        startPage: "/user/addresses/new",
-        steps: [
-            "Sign in as rehan.sheikh@gmail.com / TempPass123!.",
-            "Open /user/addresses/new.",
-            "Select India as the country.",
-            "Select Karnataka in the 'State / region' picker.",
-            "Change the country to Canada.",
-            "Read the 'State / region' field, and count the options it now offers.",
-            "Change the country back to India and read it again.",
-        ],
-        inputs: {
-            firstCountry: "India",
-            state: "Karnataka",
-            secondCountry: "Canada",
-            canadaOptionCount: 13,
-        },
-        expectedBehaviour: "Changing the country clears the state, because a state only means something inside the country it belongs to. An address carrying Karnataka under Canada is a row nothing can group, rate for shipping, or tax correctly.",
-        expectedUiState: "After switching to Canada 'State / region' is empty and offers 13 Canadian options, its 10 provinces and 3 territories — an emptied field still listing India's 36 would mean the clear ran and the option source did not. Switching back to India leaves it empty too: the clear fires on every country change and does not restore 'Karnataka', which would reintroduce the mismatch it exists to prevent.",
-        expectedData: { stateAfterCountryChange: "", canadaOptionCount: 13 },
-        endResult: "Nothing persists unless the form is submitted. A retained 'Karnataka' under Canada is the failure.",
-    },
-};

package/dist/features/tester/seed-data/authored/addresses__unban-request.d.ts

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