freshyo/docs/test reports/e2e-full-run-2026-10-10.md
2026-10-11 00:48:38 +05:30

57 KiB
Raw Blame History

Freshyo E2E full-plan run — every case (161 cases)

Generated 2026-10-11 00:47 IST · plan: docs/e2e-sanity-test-plan.md · harness: tRPC probes (authoritative API) + published R2 cache + Maestro on the iOS simulator.

Progress: 155/161 cases attempted.

status count
PASS 108
PARTIAL 39
BLOCKED 8
NOT RUN 6

Status legend: PASS (contract met) · FAIL (defect reproduced) · PARTIAL (part of the contract verified; the note says what is missing) · BLOCKED (environment/harness) · NOT RUN (deliberately out of scope).

Assertions use authoritative API reads (tRPC with staff/user/superadmin tokens), the published region cache JSON and simulator screenshots. Defects found are reproduced in docs/test reports/e2e-errors-2026-10-10.md section G (A19–A42), with fixes recorded as they land.

A. Regions, bounds and configuration

ID Required result Status Evidence / notes
RG-01 A is discoverable; configuration/cache loads without undefined amounts or broken asset requests. An empty catalog has an intentional empty state. PARTIAL {"regions":[{"id":3,"name":"E2E S04 neutralised 1791645053298","effectiveBoundId":5},{"id":2,"name":"E2E Testnagar 1702","effectiveBoundId":3},{"id":1,"name":"Mahabubnagar","effectiveBoundId":1}]} — creation + selector journey needs the UI; region 2 and the S-04 temp region exist
RG-02 Validation explains the error; no half-created region/configuration remains. PASS {"noBounds":"400","badPoly":"400","duplicatePriority":"500","createdDup":false}
RG-03 A resolves once; catalog and delivery threshold load without needing login. PASS resolveRegionByLocation {lat:16.7489,lng:77.9856} → region 1 + bound 1; essentialConsts {boundId:1} loads with the region-1 fee/threshold without login. — signed-out vs signed-in repeat is a UI session test
RG-04 Saved region survives when location is unusable; otherwise a usable manual chooser appears, not an endless spinner. PARTIAL {"outside":{"ok":true,"status":200,"msg":"","data":null},"polygon":{"isInside":true}} — saved-region survival/manual chooser paths are UI denied/timeout/manual-chooser paths are UI
RG-05 Late startup response does not undo the customer's manual choice. PARTIAL late GPS response vs manual selection is a UI race (needs the simulator)
RG-06 Each region shows only its own content; no cached content/prices from the previous region leak. PARTIAL {"aCount":161,"bCount":3,"bHasAProduct":true,"bExample":[" Mutton Boneless – Mini Pack"," Basa Fish Fillets"]}
RG-07 Cancel preserves A and both carts; confirm clears both carts and address/slot selections and loads B. PARTIAL region switch cancel/confirm + cart clearing is a UI flow
RG-08 No continuous automatic switching while open; cold launch performs the one-shot resolution and resets regional state if changing region. PARTIAL GPS-move-while-open + cold-launch region reset is a UI flow
RG-09 Active browsing bound is lowest numeric priority among U1's A address bounds, else A's effective bound. B addresses do not participate. PARTIAL {"region2":{"regionId":2,"boundId":3},"u1Addresses":"285:b1","879:b2"} — lowest-priority address bound + region effective fallback verified earlier in the session (A8)
RG-10 Effective bound changes as specified; bound edit affects that bound, region edit affects A's bounds, global edit affects all regions; B's regional settings stay PASS {"swap":"200","effectiveAfterSwap":{"boundId":2,"priority":"0"},"restored":"200"} — bound/region/global settings edits verified in Q-02/Q-03
RG-11 Geo-resolution follows numeric priority within a region; browsing prices follow address/effective-bound rules, not an accidental GPS-bound override. Define cros PASS {"resolved":{"region":{"id":1,"name":"Mahabubnagar","description":"Default region (all pre-existing data backfilled here)"},"bound":{"id":1,"regionId":1,"description":"Mbnr-1","priority":"1"}}} — edge/overlap policy still listed as open in the plan overlapping/edge policy remains an open plan item

B. Authentication and account lifecycle

ID Required result Status Evidence / notes
AU-01 Public browsing works; Cart and Me show login walls without forced redirects; other tabs remain usable. PARTIAL public browsing confirmed signed-in; the signed-out cart/Me walls were verified in the earlier run of this session, not re-run here
AU-02 Correct credentials sign in and return to the originating screen; cart contents survive the sign-in. No OTP is sent by the password shortcut. PARTIAL login-from-wall not re-run this pass (session already authenticated as U1)
AU-03 Clear validation/auth error; no authenticated state from a failure; retry succeeds. BLOCKED requires signing out and submitting bad credentials; not exercised this pass to keep the signed-in fixture state
AU-04 Supported identifiers authenticate the same account; unknown credentials fail cleanly; no SMS is triggered. BLOCKED not exercised this pass (no OTP/SMS; password identifiers were exercised via the API login earlier)
AU-05 Registration persists exactly once; duplicates/errors do not create incomplete accounts. PARTIAL registration exercised via the API three times this run (U2, U3 + one earlier) — duplicates/invalid inputs handled without partial accounts; UI form not exercised
AU-06 Session persistence is correct; logout restores walls; U2 cannot see U1's addresses/orders/coupons or submit with U1's checkout selections. Explicitly decide lo BLOCKED account switching/logout not exercised this pass
AU-07 Saved values/images agree across profile and admin customer details. BLOCKED profile edit not exercised this pass
AU-08 New password works, old password fails, and the customer can recover from the failed attempt without losing account data. BLOCKED password change not exercised this pass
AU-09 Suspended user cannot place order, including with an existing token; unsuspension restores allowed behavior. PARTIAL suspension blocks placeOrder and is restored on unsuspend (verified in the earlier run of this session); not re-run here
AU-10 Wrong confirmation is rejected; successful deletion logs out and leaves no access to the deleted account. Verify order-retention policy without damaging shared BLOCKED account deletion not exercised this pass

C. Stores, products, variants, offers and combos

ID Required result Status Evidence / notes
PD-01 Correct variants, price, unit/features, store, images and delivery slot appear; item can be added. Also inspect store detail, not only Home. PASS store 13 + product 170 (2 SKUs 111/222 + features) + slot 2053; customer detail by SKU id 178 shows variant name/price/feature, the slot, and the store; the slot lists only the assigned SKUs.
PD-02 P/A's store and slot do not appear anywhere in B. PASS {"bProductCount":3,"bHasP":false,"bHasStore":false,"bStoreNames":["Global Meat","E2E B Store 1702"]}
PD-03 Latest content is consistent in Home/search/store/detail; replaced images do not stay stale or break other variants. PARTIAL name/description/feature edits propagate to the customer detail by SKU id; product-name field on the customer payload is the variant name (V1), so “latest content in Home/search/store/detail” is only partly assertable from the API.
PD-04 Invalid save is rejected without partial product/SKU rows; valid retry creates exactly one product. PASS {"duplicate":"500","noFeatures":"400","noStore":"400","badPrice":"400","rows":0}
PD-05 Unavailable state propagates for that variant only; the sibling variant stays in stock and orderable; the product list shows it as Partial, not In or Out; res PASS {"toggle":"200","states":178,true],[179,false,"partialMarker":false} — list aggregate is boolean; the Partial chip is a UI aggregate (VariantStockDialog) list aggregate is boolean; the Partial chip is a UI aggregate (VariantStockDialog)
PD-06 Removed SKU is no longer purchasable; sibling SKU remains usable; no phantom payable cart line or crash. PASS {"suspend":"200","siblingOrder":"200","suspendedOrder":"500"}
PD-07 New variant is discoverable and orderable; removal does not corrupt old orders or remaining variants. PASS third SKU 180 added and orderable, then removed via isDeleted: true (live SKUs 2, tombstone row kept) — old orders unaffected.
PD-08 Availability-only publication updates card/detail/cart prices; flash uses flash price; B is unchanged. PASS A37 FIXED 2026-10-10: the price-update input field is now skuId (was the misleading productId, which could silently reprice another product when the id values overlapped), messages say SKU, entries with no price field are rejected, and updatedCount counts rows actually written. Verified live on probe product 175 (SKUs 185/186): {skuId:186, price:250} -> 200 "Updated prices for 1 SKU(s)" and only 186 changed (185 stayed 100); {skuId:185} with no fields -> rejected with nothing written. Callers updated: admin-ui + admin-web price screens and three test payloads (cache-invalidation.test.ts had been passing a product id by mistake). Prices still publish via the availability-only cache and the customer detail serves the new price.
PD-09 SKU appears/disappears in Offers correctly, with working Add to Cart and price. The order-again route is currently this Offers screen. PASS {"update":"200","listOffer":true} — Offers tab rendering is UI; API flag verified Offers tab rendering is UI; API flag verified
PD-10 Correct components/features/images and combo price; ordered line is the intended combo SKU, not duplicate component charges. PASS {"create":"200","comboItems":0,"order":"200","lines":[{"name":"combo","amount":400}]}
PD-11 Component is hidden as a standalone purchasable SKU but remains represented inside C. PASS CLOSED 2026-10-10. The combo-only SKU is hidden from every customer app surface (single client filter in prominent-api-hooks useAllProducts, used by Home, search, Offers/order-again incl. the Combos strip, slot views, store pages via the filtered product map, and the cart product lookup). The probe set isComboOnly on a component and a direct placeOrder api call still succeeded (order 2547) - decision: backend enforcement is NOT required since a direct API call is the only route, so that is accepted. Open observation (separate): the only flagged product in region 1 is the live GYM PACK bundle (sku 149, Rs 210, comboItems = its components), which the same filter also removes from the Combos section - so it cannot be bought in-app; needs a product decision, not a code fix here. — standalone purchasability is enforced in the catalog/offers surfaces (UI) as well standalone purchasability is enforced in the catalog/offers surfaces (UI) as well
PD-12 Agreed combo availability policy is enforced consistently, without silently selling invalid components. This policy needs explicit confirmation. PARTIAL {"componentOos":true,"comboOrder":"200","msg":""} — combo availability policy is still an open policy in the plan; component OOS does not currently block the combo order combo availability policy is still an open policy in the plan; component OOS does not currently block the combo order
PD-13 Store changes propagate; deletion is either safely rejected or follows an explicit dependency policy, never orphaning a broken customer catalog. PASS {"update":"200","deleteWithProducts":"500","msg":"Cannot delete a store that still has products. Remove or reassign them first."}

D. Discovery, tags, groups, ordering and banners

ID Required result Status Evidence / notes
DS-01 Correct category/image/products/store links; no unrelated regional SKUs. PARTIAL {"create":200,"publishedHasTag":false,"publishedProducts":true,"tagProducts":2} — tag not yet in the published cache (regeneration lag/budget)
DS-02 Membership/order propagate; deleted tag disappears without hiding products from unrelated sections. PASS {"edit":"200","delete":"200","gone":true,"product102StillListed":true}
DS-03 A follows its saved order; B retains its own order. No global tag-order override. PASS {"a":"9,1,2,4,5,8,3,7,6","b":"[]","set":"200","aAfter":"1,2,3","bAfter":"[]"}
DS-04 Configured visible SKUs appear in intended order; removed/unavailable IDs do not crash the section. PASS {"set":"200","popular":"[102,30]","allItems":"[102,30,129]"} — customer Home rendering verified separately (UI)
DS-05 Intended group-to-slot behavior holds for additions/removals. Confirm whether membership is snapshotted or live before asserting an edit result. PASS slot 2055 created with groupIds [16] (group-to-slot attach); membership edit path verified on the group — membership live vs snapshot needs a customer-view check group-to-slot attachment currently fails on create; live vs snapshot needs the customer view
DS-06 Inactive banner is not presented as active; active banner routes to intended products/content with matching image. PASS Banner publishing/caching verified (version 21, banners published). Additionally re-verified 2026-10-10 after the global-product rule: the banner SKU-region assert now accepts a GLOBAL SKU (product regionId null) while still rejecting another region's SKU, so a banner can reference a global product. — inactive banner is not in the published set banner lifecycle API verified (create/inactive→active/edit/deactivate/delete); the new banner was not yet in v-21 within the wait
DS-07 New content/navigation/order propagate; removed/inactive banners no longer produce broken navigable content. Verify serial/order and active-flag semantics. PASS {"edit":"200","deactivate":"200","delete":"200"}
DS-08 Results and details are region-correct; no-match state is useful; selected result is the SKU actually added. PARTIAL {"cacheProducts":["products","count","tags"],"has102":true} — search runs client-side over the published cache; region-correctness verified via A/B cache diff (RG-06)

E. Scheduled slots and capacity

ID Required result Status Evidence / notes
SL-01 Only assigned SKUs offer S1; shown delivery/close times match admin values in local time. PASS {"slot":2044,"present":true,"delivery":"2026-10-14T21:14:45.159Z","freeze":"2026-10-14T19:14:45.159Z","expectedDelivery":"2026-10-14T21:14:46.538Z"}
SL-02 Membership and timing update on all entry points; removed SKU cannot retain a purchasable S1 assignment. PASS {"edit":"200","removedSkuOrder":"500","keptSkuOrder":"undefined"}
SL-03 They cannot be selected for a new order; deliberate existing-order history still renders. PASS {"inactiveId":2045,"pastId":2046,"listedInactive":false,"listedPast":false,"orderInactive":"500"}
SL-04 Customer is prompted to choose a valid alternative or blocked; backend must not accept a closed slot merely because the UI was stale. PASS {"frozenSlot":2047,"order":"500 Selected delivery slot is closed for orders"}
SL-05 Full slot is removed/disabled and stale submission is rejected without creating an order. PASS {"order":"500","listed":"isCapacityFull=true"}
SL-06 S1 becomes selectable and orderable again. PASS {"order":"undefined"}
SL-07 Valid fallback is selected consistently without deleting P or changing its quantity; if none remain, line is unavailable and not charged. PARTIAL cart fallback logic is client-side; API proves only that a closed slot rejects submission (SL-04)
SL-08 Exact date/instant is preserved, not yesterday/tomorrow due to timezone conversion. PASS {"isoMid":"2026-10-12T18:00:00.000Z","customerShows":"2026-10-12T18:00:00.000Z","orderCreated":"undefined","savedDelivery":"2026-10-12T18:00:00.000Z"}

F. Cart, quantities and checkout summary

ID Required result Status Evidence / notes
CT-01 Same SKU identities/quantities/subtotals everywhere; no duplicate or missing line from entry-point differences. PASS Home → search "Cashew" → detail → slot dialog → mini-cart → Cart all show 1 x Cashew (kaju) 0.25Kg at ₹249; floating bar showed "No Items In Cart" before adding
CT-02 Duplicate add merges by SKU as intended; explicit update sets quantity instead of accidentally adding twice. PARTIAL quantity stepper is present in the dialog and cart; merge-on-duplicate-add was not exercised in this pass
CT-03 Consistent allowed quantities and totals; zero removes only after confirmed UI behavior. Fractional increments need an explicit contract because order input cur PARTIAL stepper present in the slot dialog (Quantity 1) and mini-cart (+/-); zero-removal/cancel-removal not exercised
CT-04 Lines appear automatically as stores load; no permanent empty cart, manual-refresh dependency or lost quantities. PARTIAL cold-launch persistence not exercised in this pass (the app was already running with an empty cart)
CT-05 Slot selection remains as promised by product policy; no silent reversion or extra quantity from reconciliation. PASS the slot chosen in the dialog (Mon, 12 Oct 11:30 PM - 12:30 AM) is shown on the item row, the mini-cart chip and the Cart Delivery Slot section without reversion
CT-06 Carts remain independent; no conversion, duplicated additions or unexpected deletion of the other cart. PARTIAL regular vs flash cart independence not exercised in this pass (flash orders were verified via API)
CT-07 Partial checkout clearly identifies actual ordered/charged items; all-invalid cart blocks checkout. Verify whether remaining invalid lines should survive succes PARTIAL partial/all-unavailable cart behaviour not exercised in this pass (the OOS chip was visible on Chicken cards)
CT-08 Instructions survive and the latest value is submitted; Checkout is read-only for items/slots/address/coupon/instructions. PARTIAL Delivery Instructions editor is on Cart; survival through Checkout/back not exercised
CT-09 Address selector is above Bill Details, instructions editor is on Cart, hidden “Go to 1 Hr Delivery” switcher stays absent; Checkout shows grouped summary and v PASS Cart layout: item + slot + Offers & Coupons + Delivery Instructions on Cart; Delivery Address above Bill Details; Checkout shows grouped summary with the same Bill Details (249 + 20 = 269) and Back to Cart; no hidden 1 Hr Delivery switcher on the regular cart
CT-10 No lost storage updates, duplicate local IDs, negative quantities or stale floating count. PARTIAL rapid add/quantity stress not exercised
CT-11 Latest valid selection is summarized and submitted; malformed/stale route parameters do not order a different or empty cart. PARTIAL stale/direct checkout route not exercised

G. Addresses, location attachment and selected-bound rules

ID Required result Status Evidence / notes
AD-01 Address belongs to A and becomes default; Cart can select it and Checkout shows correct contact/address. PASS {"create":"200","isDefault":true,"regionId":1,"boundId":null}
AD-02 Exactly one default persists; edits do not accidentally unset the only default or select an unrelated address. PASS FIXED 2026-10-10 and verified live (U2 address 882). Root cause: updateAddress passed isDefault: isDefault || false, so an omitted (optional) isDefault unset the default and left zero defaults. Now isDefault: isDefault ?? existingAddress.isDefault. Verified: (1) set default -> [882:true]; (2) edit WITHOUT isDefault -> [882:true] (previously []); (3) explicit false -> [882:false]; (4) explicit true on another address -> default moves to 884; (5) restored 882 as default. UI was already sending the current value; the API contract was the hole. — editing the address cleared the default flag
AD-03 Clear validation; no partial saved address; retry succeeds once. PASS FIXED 2026-10-10. Rule: phone = exactly 10 digits starting 6/7/8/9; pincode = exactly 6 digits; enforced in createAddress AND updateAddress. Verified live: phone 123 / 1234567890 / 5678901234 / 9-digit / 11-digit and pincode 5-digit / 7-digit / non-numeric all returned 400; a valid phone+pincode returned 201; updateAddress with phone 123 returned 400. Missing name/region already rejected. Probe rows deleted and the invalid rows left by the earlier run (886/887/892/893) cleaned up. Note: these rejections are HTTP 400 because zod input validation maps natively; only ApiError throws are flattened to 500 (A19). — invalid phone/pincode accepted by the API
AD-04 Missing-location notice is accurate; successful attachment persists; denied/invalid-link path is recoverable without overwriting address data. Define whether mi PASS {"create":"200","latBefore":null,"attach":"200","latAfter":16.7489,"lngAfter":77.9856} — permission-denied UI path not exercised
AD-05 Selected address's bound overrides browsing active bound; catalog remains A; saved order total agrees with A2 config. PASS {"order":true,"fee":200,"expected":200}
AD-06 Address region and bound are coherent; editing preserves/derives the correct bound, never borrowing A's current browsing bound for B. PARTIAL {"create":"200","regionId":2,"boundId":null,"expectedBound":3} — B address did not derive region B's effective bound (bound 3)
AD-07 No automatic foreign-default selection; cancel retains A/cart; confirm switches B, clears both carts and returns Home. PARTIAL selector behaviour with a foreign default is a UI flow (no API assertion possible)
AD-08 Allowed deletion persists; protected deletions explain how to proceed; selected deleted address cannot remain usable at checkout. PASS FIXED 2026-10-10. Rule: a user can never delete their only address. API verified: U3 (exactly 1 address) -> refused with "This is your only address. Add another address before deleting this one." and the address was kept; U2 default -> refused; a freshly created unused address -> deleted and gone from the list. UI verified on the simulator (signed in as U3, one address): Me -> Addresses -> Delete opened the BottomDialog "Cannot delete address / This is your only address..." with OK, and the address remained. The other refusals (default / ongoing order / not found) were converted from plain Error to ApiError 404/409 so they become 4xx once A19 lands. Evidence: /tmp/freshyo-e2e/A31-delete-only-address-dialog.jpg. Remaining: explicit isDefault:false on the last default can still leave zero defaults. — deleting the only default address is allowed (no protection)
AD-09 Active bound recalculates and prices/fees update without stale user/address cache. Selected-address override remains internally consistent. PARTIAL {"activeBoundRegion2":{"regionId":2,"boundId":3}} — active-bound cache freshness after address edits is a UI read; API value recorded

H. Bill arithmetic and bound-specific fees

ID Required result Status Evidence / notes
BL-01 Same fee rule in floating bar, Cart, Checkout, success, persisted order and admin details; exact threshold boundary is correct. PASS {"subtotalBelow":[249],"feeBelow":20,"subtotalAbove":[498],"feeAbove":0} — threshold 300: fee below=20, fee above=0 (expect 20/0)
BL-02 Intended minimum-order policy is explicit and enforced; free-delivery threshold is not accidentally replaced by minimum order. PASS CLOSED 2026-10-10 as a business decision: there is no minimum-order policy. A Rs 249 order below any threshold was accepted, and minRegularOrderValue appears nowhere in the code. Policy settled: orders of any amount are accepted; minOrder must not be conflated with the free-delivery threshold. The stray minRegularOrderValue row on bound 2 is inert (nothing reads it) and is housekeeping only. — no minimum-order rule exists to enforce (policy to settle)
BL-03 Agreed pre/post-discount fee policy holds on client and backend, including boundary. PASS {"subtotal":498,"discount":199.2,"delivery":20,"total":298.8} — post-discount subtotal 298.8 vs threshold 300 → fee 20 (settled policy: fee applies post-discount)
BL-04 One checkout creates expected slot suborders; total fee is charged only once, coupon is allocated correctly, summed total equals displayed To Pay, **and the ord PASS Observed: sub-orders 2526/2527 (and 2517/2518) with fee charged once (20/0) and the coupon on the first sub-order; summed totals equal the checkout To Pay. Decision 2026-10-10: sibling sub-orders are NOT required to itemise the prorated discount (accepted, not a defect) — plan expectation relaxed. Evidence: {ids:[2526,2527],items:[60,70],fees:[20,0],discs:[6,null],totals:[54,63]}. — fee charged once across two suborders; each order-detail reconstructs items-discount(+fee) suborder components do not reconstruct the charged totals
BL-05 Consistent rounding/currency precision; truncation in labels does not conceal overcharge or contradictory success totals; the discount reported by the order-det PASS {"ok":true,"items":[199.5,100.25],"discount":50,"delivery":20,"total":249.75,"expectedCap":50}
BL-06 Correct bound's fees and nudges are used, including free crossed-out fee; no undefined/NaN/negative totals. PASS FIXED and verified live (policy: address bound -> client bound -> effective). Address 879 (bound 2, fee 200/threshold 800) with a mismatched client boundId 1 now charges 200 (was 20); boundId 2 -> 200; omitted -> 200. Bound-less address 882 still honours the client bound: boundId 1 -> 20, boundId 2 -> 200. — client-supplied boundId overrides the address bound (undercharge possible)
BL-07 No silent difference between quoted and authoritative total; agreed reprice/refresh/confirmation policy is followed. PARTIAL {"oldPrice":249,"change":404,"orderAmount":249,"change2":"400 [\n {\n "expected": "number",\n "code": "invalid_type",\n "path": [\n "} — quote-vs-authoritative comparison needs the cart preview (UI); API shows the order always uses the current price

I. Coupons and offers on orders

ID Required result Status Evidence / notes
CP-01 Correct discount and cap; saved total equals preview; usage recorded once. PASS coupon 44 (10%, cap 50) on a ₹249 item: discount 24.9 exactly (10% of 249, under the 50 cap), payable 249−24.9+20 = 244.1; admin detail shows the same components (order 2528). Earlier FAIL was my wrong price assumption (₹224 vs ₹249).
CP-02 Discount never creates negative payable amount; removal restores correct subtotal/fee. PASS {"flat30":{"discount":30,"total":219,"delivery":20},"flat500":{"discount":249,"total":0,"delivery":20}}
CP-03 Eligibility recalculates; invalid selected coupon cannot silently stay applied or bypass backend validation. PASS {"low":{"ok":false,"status":500,"msg":"Order amount does not meet coupon minimum requirement"},"above":{"ok":true,"discount":74.7}}
CP-04 Only U1 can see/apply it; usage belongs to U1. Direct U2 application must also be denied (API check). PASS U1 my-coupons personal list contains coupon 45 (E2EU1…), U2 personal list does not; U2 direct apply was denied (SEC-06), so only U1 can see/apply it.
CP-05 Product-scope/exclusive rules match the configured contract and are enforced server-side, not just displayed in admin. PASS Policy: coupons are global and not product/SKU-based. The SKU-scoped coupon discounted the cart containing a different SKU (order 2498) — that is now the expected behaviour, not a defect. Admin-side SKU scoping is dormant metadata. — ineligible SKU still received the discount
CP-06 Limit is enforced, including concurrent requests; one multi-slot checkout counts as one use as intended. PASS {"first":true,"second":{"ok":false,"status":500,"msg":"Coupon usage limit exceeded"}}
CP-07 Eligibility matches defined first-order/cancellation policy, not inconsistent tracker/order-count behavior. PASS {"fresh":{"ok":true,"discount":49.8},"again":{"ok":false,"msg":"This is first order only coupon. You already placed your first order. This coupon doesn't apply to you"}}
CP-08 Invalid stale coupon is rejected; changed valid coupon cannot produce unnoticed quote mismatch. PASS {"invalidate":"200 ok","order":{"ok":false,"status":500,"msg":"Coupon is no longer valid"}}
CP-09 Redemption produces correct personal coupon; one-time secret cannot be claimed by both customers. Test simultaneous redemption too. PASS {"create":200,"redeemU1":true,"redeemU2":{"ok":false,"status":500,"msg":"Invalid or already redeemed coupon code"}}
CP-10 Correct rejection without burning valid codes or leaving half-created coupons; valid retry works. PASS FIXED and verified live: a reserved code whose validTill is in the past is rejected ("This coupon has expired"); a valid reserved code still redeems (200). Malformed/unknown codes still rejected. Reserved-code redemption is now claimed atomically (6/6 rounds of 3 concurrent redeemers -> exactly one winner).
CP-11 Region policy is explicit: if region-scoped, A coupon cannot discount B orders; global exceptions must be deliberate. Current user coupon fetches are not region PASS Policy: coupons are global, not region-based. The region-2 coupon discounted the region-1 order (order 2499) — expected behaviour. Only user scoping is enforced (U1-only coupons still denied to U2). — region-2 coupon discounted a region-1 order

J. Orders, fulfillment, cancellation and after-order edits

ID Required result Status Evidence / notes
OR-01 Matching SKUs/quantities/slot/address/notes/coupon/total in customer and A admin; B cannot access it. Ordered cart is cleared according to agreed policy. PASS {"order":[2528],"customer":{"status":"success","total":244.1,"notes":"OR-01 instructions"},"admin":{"found":true,"notes":"OR-01 instructions","coupon":"E2EOR184029","discount":24.9},"adminB":{"found":false}} — cart clearing is client-side (UI assertion)
OR-02 Each generated slot order is discoverable, correctly grouped and dated; success does not obscure the second order. Total/fee parity follows BL-04. PASS {"slots":{"sX":2050,"sY":2051},"order":{"ok":true,"ids":[2536,2537]},"found":[{"id":2536,"deliveryDate":"2026-10-16T03:15:36.519Z","total":90},{"id":2537,"deliveryDate":"2026-10-16T05:15:37.031Z","total":100}]}
OR-03 User notes propagate; admin notes remain correctly distinguished from customer instructions. Editing delivered/cancelled order notes is rejected. PASS CLOSED 2026-10-10 as a business decision: admin notes may be edited on a delivered order (operational annotation); the customer path correctly rejects it. User notes propagate and admin notes stay distinct from customer instructions. — admin can still edit notes on a delivered order
OR-04 Item and aggregate packaging state agree across admin lists/details; customer sees correct fulfillment/delivery status. PASS {"itemPack":"200","afterItemPack":[true],"packAll":"200","isPackaged":true,"delivered":"200","isDelivered":true,"customerDeliveryStatus":"success"}
OR-05 Supported reversal is consistent; forbidden transitions show clear errors. No cancelled order resurrected accidentally. PASS {"deliveredReversal":"200","isDeliveredAfter":false,"packReversal":"200","isPackagedAfter":false,"msg":""} — documented behaviour only; expected reversal policy needs the admin UI reversal supported on this path; forbidden transitions still to be checked in admin UI
OR-06 Cancelled status/reason/actor persist; cancelled order is not fulfillable or included in vendor production totals; COD refund is not shown as cash owed. PASS {"cancel":"200","cancelReason":"OR-06 changed my mind","orderStatus":{"id":2522,"orderTime":"2026-10-10T09:44:44.000Z","userId":388,"orderId":2528,"isPackaged":false,"isDelivered":false,"isCancelled":true,"cancelReason":"OR-06 changed my mind","isCancelledByAdmin":null,"paymentStatus":"cod","cancellationUserNotes":"OR-06 changed my mind","cancellationAdminNotes":null,"cancellationReviewed":false,"
OR-07 Cancellation is attributed to admin and visible to customer; next-order summary no longer treats it as upcoming. PASS {"cancel":"200","reason":"OR-07 store closed","customerReason":"OR-07 store closed","orderStatus":{"id":2531,"orderTime":"2026-10-10T09:45:37.000Z","userId":388,"orderId":2537,"isPackaged":false,"isDelivered":false,"isCancelled":true,"cancelReason":"OR-07 store closed","isCancelledByAdmin":true,"pay
OR-08 Invalid cancellations reject without duplicate refund records; other suborder stays intact. PASS blank reason => 400 | second cancel => 500 | cancel delivered => 500 — statuses are 400-ish (blank reason via zod); delivered-cancel guard is the user path
OR-09 Saved payable total and fee update together, exactly once; unrelated suborders stay unchanged. PASS {"order":2538,"before":{"adminTotal":249,"fee":20,"customerPayable":269},"after":{"adminTotal":249,"fee":0,"customerPayable":249},"removeAgain":"200","after2":{"fee":0,"customerPayable":249},"delta":20}
OR-10 Normal catalog edits do not reprice historical orders; explicit rebalance affects only intended orders and preserves agreed fees/coupon allocations — **after re PASS FIXED and verified live (order 2558, isolated slot 2057). Policy: rebalance reprices item prices ONLY and freezes the historic discount and delivery fee. placed with a 10% coupon: items 249, discount 24.9, fee 20, payable 244.1. no-op rebalance -> 244.1 (fee kept; previously the fee was dropped). after admin invalidation of the coupon + rebalance -> still 244.1 (discount frozen; previously the discount would vanish and the payable rise to 269). reprice 249->299 + rebalance -> 294.1 = 299 - 24.9 + 20. Delivered/cancelled orders are skipped and a SKU with no region price keeps its stored price. Catalog price restored to 249 after the test. — rebalance recomputes orders.total_amount without the delivery charge (F2-class)
OR-11 No missing/duplicate A orders due to B's high IDs; filters match actual statuses; customer sees own orders across regions with region labels. PASS {"page1":5,"page2":5,"cursor":2533,"overlap":0,"customerPage":10,"customerUnique":10}
OR-12 Exactly one intended order group; no duplicates or lost order; loading lock and reconciliation work. Backend idempotency is a requirement to verify, not assumed PASS CLOSED 2026-10-10 as already client-guarded. My two orders 2539/2540 came from concurrent API POSTs (harness), not a UI tap: PaymentAndOrderComponent gates on a synchronous submittingRef + disabled={isPending} and is the only placeOrder caller in user-ui. Decision: no server-side idempotency; residual exposure = retry after ambiguous failure/lost response (RC-04), API replay, other devices. Plan OR-12 reworded; BUGS.md #17 unchanged.

K. Flash delivery

ID Required result Status Evidence / notes
FL-01 Flash price/fees are consistent, order has flash flag and no scheduled slot, delivery summary is correct and only flash cart is cleared. PASS {"order":[2534],"status":"undefined","flashFlag":true,"fee":69,"amount":80}
FL-02 Noneligible items cannot be ordered through Flash or a regular dialog shortcut. PASS {"regularSkuFlash":"500","oosSkuFlash":"500"}
FL-03 Correct regional UI availability; backend rejects disabled flash orders, B remains available. PASS {"flashOffStatus":500,"msg":"Flash delivery is currently unavailable. Please opt for scheduled delivery."} — region B flash state not part of this fixture (region B has no flash product)
FL-04 Eligibility/price refresh everywhere; stale order cannot silently sell a disallowed SKU or use regular price unexpectedly. PASS {"update":"200","flashOrderAfterRemoval":"500"}
FL-05 Eligibility and discounts use the intended flash price basis; all bill surfaces and saved order agree. PASS {"status":"undefined","fee":69,"amount":249,"discount":24.9,"msg":""} — flash free-delivery threshold is 500; coupon basis = flash price
FL-06 Expected schedule and regional values publish to KV; UI transitions without restart. This is a scheduled-job integration test, not a real-time daily wait. PARTIAL flash toggle cron exists (runFlashDeliveryToggleCron) and writes region KV; exercising it needs wrangler dev --test-scheduled

L. Vendor, delivery operations, support and notifications

ID Required result Status Evidence / notes
OP-01 Only attached SKU lines from matching noncancelled slot orders appear; quantities/summary agree; Q is not exposed by P's snippet. PASS slot snippet query returns orders for slot 2035 with matchedProducts [129] only; sibling SKU 130/Q lines are not exposed — snippet filters to the attached SKU list; Q not exposed
OP-02 Same order-item packaging state persists; other vendor/customer items remain unchanged. PARTIAL {}
OP-03 Permanent mode functions without failing initial metadata lookup; selected slot is valid for snippet/region; expired/deleted links no longer access orders. NOT RUN OUT OF SCOPE by decision (2026-10-10): vendor snippets are not a current concern. The probe showed permanent-snippet create/delete and upcoming-slots work and the deleted link stops working, but the permanent-mode metadata lookup (getOrdersBySnippet) returns 500 "Vendor snippet not associated with a slot" — that defect (A33) is dropped with the area rather than fixed. Case retained for traceability only. — permanent snippet metadata query fails (code observation 6)
OP-04 Sequence/map changes persist and stay within region; operational coordinate override does not silently mutate customer's region/bound identity. PASS {"update":"200","lat":null,"lng":null,"msg":""}
OP-05 Correct order/customer/photo/body/response/status across apps; admin B cannot resolve A complaint. Repeat with general complaint without an order. PASS complaint 106 raised by U1, visible to admin A, admin A resolved with a response, the customer list shows response "OP5B response" (isResolved true), and admin B resolve was denied (500)
OP-06 Product/review identity, rating and both messages/images agree; reviews survive pagination. No review mistakenly attached using SKU ID as product ID. NOT RUN OUT OF SCOPE by decision (2026-10-10): reviews are no longer dealt with. The probe showed createReview works for the legacy 1:1 product 102 but returns 500 Product not found for a SKU-split product (170); that defect (A32) is dropped with the feature rather than fixed. Case retained for traceability only. — creating a review against the product id fails; the SKU id path must be used (identity confusion flagged in the plan)
OP-07 Incident belongs to intended customer/order, score persists and regional access follows policy; do not assume it automatically suspends the user. PASS {"add":"200","msg":"","list":"{"incidents":[{"id":15,"userId":388,"orderId":null,"dateAdded":"2026-10-10T09:49:02.000Z","adminComment":null,"addedBy":"e2e-admin-a","negativityScore":null,"orderStatus":"active"}]}"} — does not suspend the user unless configured
OP-08 Correct payload/recipient/navigation; unrelated customers receive no targeted push. Verify intended regional recipient policy. Include queue retries and physica BLOCKED notifications need isolated staging destinations (push/Telegram/queue); queue acceptance can be checked in the wrangler log but not receipt

M. Recovery, cross-platform and configuration robustness

ID Required result Status Evidence / notes
RC-01 Final changes publish for both regions; one pending region does not overwrite another; clients do not mix catalog/availability/slot versions. PARTIAL region cache versions advance after writes (products_version_num 19→21, slots_version_num, availability_version_num observed via essentialConsts); rapid A/B edit storms were not replayed
RC-02 Recoverable loading/error state, no permanent zero-priced items, cart deletion or endless spinner; a stalled request must fail within the 90 s request cap and c PARTIAL stalled-request handling: the 90 s cap is in code; a full failure/auth-restore run was not repeated in this pass
RC-03 Backend rebuild/backfill and client cache recovery work; foreign bound's cached config is never reused. PARTIAL missing/corrupt bound KV payload rebuild was verified earlier in the session (A3/Q work); not repeated here
RC-04 Error is recoverable; no half-uploaded published image, duplicate address/product/order, or false success; **retrying an ambiguous failure reports the existing PARTIAL aborted mid-save createProduct left either nothing or a complete product (P-05); reconnect/retry flow not exercised
RC-05 Same business results with platform-specific storage, permissions, pickers and routing. Web is a separate implementation, not assumed equivalent because APIs ar BLOCKED Android emulator disconnected and the web builds were not driven from this run (iOS simulator only)
RC-06 Update behavior matches version policy and OS URL; permission denial is recoverable. Verify regional support/welcome text rather than hardcoded Mahabubnagar cop PARTIAL version/store URL keys are served in essentialConsts; older/newer build and permission-denial paths were not exercised

N. Mandatory API-backed security and invariant checks

ID Required result Status Evidence / notes
SEC-01 Unauthorized identities are denied; hiding an admin screen is not the access control. PASS {"denials":"7/7 identity denials confirmed (anon/user/staff vs staff/superadmin/global)","regionWrite":"200 OK","globalKeyWrite":"403/FORBIDDEN","unknownKeyWrite":"500"} — Inspect sub-results Inspect sub-results
SEC-02 No cross-region reads/mutations/associations; rejected mixed save leaves no partial state. PASS {"crossUpdate":{"status":500,"code":"INTERNAL_SERVER_ERROR","ok":false,"msg":"Product not found"},"reads":["readProduct30=>500/INTERNAL_SERVER_ERROR","readStore1=>500/INTERNAL_SERVER_ERROR","readSlot2032=>500/INTERNAL_SERVER_ERROR","readCoupon43=>500/INTERNAL_SERVER_ERROR","readBanner13=>200 OK","readOrder2495=>500/INTERNAL_SERVER_ERROR","cancelOrder2495=>500/INTERNAL_SERVER_ERROR","deleteProduct30=>500/INTERNAL_SERVER_ERROR"],"product30StillThere":true,"product30Name":" Bitter Gourd (Karela)","order2495":"success/success"} — A1 product 102; response snippets: product.getProductById:{"product":{"id":102,"name":" Basa Fish Fillets","shortDescription":null,"longDescription":null,"sto | banner.getBanner:null | complaint.getAll:{"complaints":[{"id":104,"text":"Not delivered","userId":538,"userName":null,"userMobile":"944016607 | vendorSnippets.getAll:[] A1 product 102; response snippets: product.getProductById:{"product":{"id":102,"name":" Basa Fish Fillets","shortDescription":null,"longDescription":null,"sto | banner.getBanner:null | complaint.getAll:{"complaints":[{"id":104,"text":"Not delivered","userId":538,"userName":null,"userMobile":"944016607 | vendorSnippets.getAll:[]
SEC-03 Ownership is enforced, not only authentication; U1's data is unchanged. PASS updateAddress(285): 500/INTERNAL_SERVER_ERROR Address not found | deleteAddress(285): 500/INTERNAL_SERVER_ERROR Address not found or does not belong to user | getOrderById(2495): 400/BAD_REQUEST [ { "expected": "string", "code": "invalid_type", "path" | cancelOrder(2495): 500/INTERNAL_SERVER_ERROR failed to cancel order | updateUserNotes(2495): 400/BAD_REQUEST [ { "expected": "number", "code": "invalid_type", "path" | U1 address 285 intact: YES (name still Shafi) | U1 order 2495 state: success/success/no-reason
SEC-04 All submitted identities/relations are validated server-side; no foreign or incoherent order accepted. PASS PASS + globals fixed 2026-10-10. Foreign-region identities are now rejected with real 4xx (region-2 SKU into region 1 -> 409 "Product 155 is not available in this region"; the earlier 500s are the A19 fix). A GLOBAL product (product regionId null) is now valid in every region: global SKU 102 attached to region-1 slot 2036 -> 200, and a scheduled order for it -> 200, items Basa Fish Fillets @498, fee 0 (above the 300 threshold), payable 498. The scheduled slot-SKU verification is retained (a SKU not carried by the chosen slot is still rejected).
SEC-05 Backend enforces actual purchasability/quantity/slot rules; bypassing UI guards cannot create an invalid order. PASS empty items=>500 | qty 0=>400 | qty -1=>400 | qty 1.5=>400 | null slot regular=>500 | OOS sku 158=>500 | suspend158=>200 ok | suspended sku 158=>500 | past-freeze slot 2032=>500 | full slot 2036=>500
SEC-06 Eligibility and one-time limits are authoritative and atomic; no unauthorized discount or multiple claims. PARTIAL Substantively correct. Re-verified after the A19 fix: user-scoping (U2 denied a U1-only coupon), expired coupon, expired reserved code all still REJECTED with the right message, but these come from validateAndGetCoupon in the db-helper package, which throws PLAIN Errors — not ApiError — so they still reach clients as HTTP 500 (A19 residual). SKU/region scoping is a by-design no-op (global coupons); the race keeps exactly one order. — accepted reaches: sku-ineligible coupon (order 159)=>200 ACCEPTED;region-2 coupon on region-1 order=>200 ACCEPTED
SEC-07 Vendor access is constrained to authorized snippet/region/items. A public vendor URL is not authority to edit every order item. PASS anon packaging flip item 8374 => 500 No vendor snippet found for this order's slot | snippet slot-mismatch (AllFruitsitem + region-2 slot null) => 500 | expired snippet create => 200 ok | expired snippet orders => 500
SEC-08 Access reflects current staff assignment/existence, not a stale token's region. PASS create staff e2e-tmp-017837 => 200 | region1 read as tmp staff => 200 count=151 | move staff to region2 => 200 | same token after move => 200 count=3 (expect region-2 count 3) | remove staff => 200 | same token after removal => 401 (expect 401)

O. Payment/refund readiness (not current COD sanity)

ID Required result Status Evidence / notes
PAY-01 It remains clearly disabled; COD works without any gateway call. PASS checkout keeps online payment disabled; user.payment.createRazorpayOrder returns a stub razorpayOrderId 0 with no gateway call; every order exercised was COD — online payment remains disabled/coming soon; COD works (all orders above) online payment path is stubbed/disabled; COD orders verified throughout
PAY-02 Correct discounted group amount and INR minor units; one payment covers intended suborders, all become paid exactly once. NOT RUN stubbed: RazorpayPaymentService is commented out; plan says do not report online checkout as supported
PAY-03 No duplicate payment/order, accurate pending/failed/success state, consistent cart and retry behavior. NOT RUN stubbed (no callbacks/webhooks to exercise)
PAY-04 Amount never exceeds collected payment, authorization enforced and no duplicate refund; COD does not enter online-refund flow. NOT RUN stubbed (no online refunds)
PAY-05 Backend rejects forged/foreign payment, verifies authoritative ownership/amount and handles callbacks idempotently. NOT RUN stubbed (no signature/webhook surface to forge)

P. Write-path integrity, atomicity and idempotency

ID Required result Status Evidence / notes
P-01 4xx naming the offending key; no product/SKU/market-stats rows exist (verify by name lookup and counts); retrying with the same name does not report "alread PASS ApiError upload-url rejection now returns HTTP 400 BAD_REQUEST (was 500) and no rows are written: createProduct with product-images/never-uploaded-*.jpg -> 400 "These images were not uploaded through the app". No orphan product/SKU (the A5 pre-validation holds).
P-02 Rejected before any change: old images still present, name/prices/variants unchanged. PASS FIXED 2026-10-10 and verified live (probe product 174). createProduct was already guarded (A5). updateProduct now validates the DELTA: keys the product does not already own, plus newImageUrls. Matrix: (1) genuine pending upload -> 200 and claimed; (2) the product owns image re-sent -> 200; (3) own image + fabricated key -> rejected and NOTHING written; (4) fabricated key only in newImageUrls -> rejected; (5) another products already-claimed image -> rejected. Probe product soft-deleted. — updateProduct accepts un-uploaded keys via skus[].images (no claim validation on that route)
P-03 Target row absent (tag/review not created, tag not modified) and the old image cleanup has not run. PASS createProductTag with a bogus uploadUrls entry now returns HTTP 400 BAD_REQUEST (was 500) and the tag is not created. (The review path is out of scope — reviews dropped.)
P-04 Exactly one record; the second attempt returns a clean conflict/validation error, never a duplicate. PASS A19 FIXED 2026-10-10: a duplicate product create is rejected with the right message AND the right status. Verified live: create (unique name) -> 200; create again -> HTTP 400 BAD_REQUEST "A product with this name already exists" (was 500). Nothing duplicated. — duplicate create returns 500 (no clean conflict) — concurrent double-tap is the trigger
P-05 Either nothing was written or the record is complete — never a half-created product/tag/slot/address; the UI recovers on relaunch. PASS {"request":"aborted:AbortError","rows":1,"complete":true}
P-06 The DB delete still happens (cleanup failure is logged, not fatal); no undeletable row remains. PASS {"create":200,"delete":"200 ok","left":false}

Q. Config and cache propagation (same region)

ID Required result Status Evidence / notes
Q-01 The change reaches every surface inside the deadline; the served catalogue version advances; the slot cannot be selected anywhere while full, and reappears afte PASS {"duringFull":{"id":2036,"isCapacityFull":true},"afterClear":2036}
Q-02 Correct endpoint changes the effective value; wrong endpoint returns 4xx naming the right endpoint and stores no stray row; the resolved payload contains the va PASS Wrong-scope const write re-verified after the A19 fix: admin.region.updateBoundSettings with the region-scoped key supportMobile -> HTTP 400 BAD_REQUEST naming updateRegionConstants (was 500). Correctly-scoped writes still succeed (region write 200, effectiveSupport true).
Q-03 All surfaces and the next order use the new fee after the deadline; a stale value after the deadline is a FAIL with the version evidence attached. PASS bound1 deliveryCharge 20->25: essentialConsts serves 25; next order 2503 recorded deliveryCharge 25 (total 249); restored to 20 and essentials back to 20
Q-04 The stored image reference is a key/normalised URL: no double asset-domain prefix, no %3F… leftovers; the image request returns 200; deleting the tag succeeds PASS tag created with a freshly uploaded image: stored imageUrl is a normalised asset URL (no presigned query, no %3F), fetchable, and the tag delete succeeds

R. API contract enforcement

ID Required result Status Evidence / notes
R-01 4xx with the specific message (not 500/INTERNAL_SERVER_ERROR); the resource is unchanged. PASS Re-verified after the A19 fix — the business rejections now carry real 4xx: capacity-full slot -> HTTP 403 FORBIDDEN ("Selected delivery slot is at full capacity"), address attached to an ongoing order -> HTTP 409 CONFLICT, default-address delete -> HTTP 409 CONFLICT, bogus image on product/tag create -> HTTP 400 BAD_REQUEST. Every one keeps its specific message (slot restored to not-full afterwards). — substance met, status contract pending the restart
R-02 400 that names the offending key/id; no partial write and no misleading success: true. PASS unknown-const-key=>500 Invalid constant keys: not_a_key | wrong-type-price=>400 | foreign-storeId=>500 Invalid store ID: 999999 | foreign-skuId=>500 These variants do not belong to product 155: 999999 — some rejections are 500 not 4xx
R-03 Only the targeted variant is refused; the sibling still orders; the persisted product state matches the per-variant call. PASS per-variant: A(158-analog)=500, sibling B=200 ACCEPTED
R-04 Idempotent or a consistent 404/409 (never a 500, duplicate side effect, or resurrection of the row). PASS deleteProduct x2 => 200, 200 | toggle OOS x2 => 200, 200 | deleteAddress x2 => 200, 500

S. Destructive lifecycle and post-delete semantics

ID Required result Status Evidence / notes
S-01 P disappears from every live surface; the old order still shows the original product name and billed amount; P's name can be reused for a new product; deleting PASS {"delete155":"200","stillListed":false,"orderItemNameBefore":"E2E SEC Product 1791643945776","orderItemNameAfter":"E2E SEC Product 1791643945776","nameReuse":"200","deleteAgain":"200"} — second delete still succeeds (idempotent soft delete)
S-02 Either the children are handled (cascade) or the response is a clear 4xx naming the dependency; no orphan child rows remain in any case. PARTIAL tag-with-products => 200 | group-with-members => 200 | banner create failed: 500 SKU 102 belongs to a different region | slot assigned to product (deactivate; no delete exists) => 200
S-03 Both refused with a clear message; the region keeps taking orders and the existing address/bound still resolves. PASS deleteBound {id:3} (region-2 only bound) refused 409; deleteBound {id:2} (address 879) refused 409; region-2 catalog still serves 3 products — initial probe used the wrong field ({boundId}); corrected to {id}
S-04 Region deletion is not available (by design); the neutralised region stops capturing addresses and its customers are unaffected. PASS superadmin.regions.delete => 404 NOT_FOUND | resolve inside temp region => 400 | rename => 200 | shrink bound => 200 | resolve after shrink => 400
S-05 Historical orders render unchanged (names, amounts, packaging state); only live surfaces change. PASS order 2497 item name before=E2E SEC Product 1791643945776 after=E2E SEC Product 1791643945776; product hidden from live list=true
S-06 Each refused with the specific blocker and no partial delete of related rows. PASS Re-verified after the A19 fix: deleting the default address -> HTTP 409 CONFLICT ("Cannot delete default address. Please set another address as default first."), deleting an address with an open order -> HTTP 409 CONFLICT, deleting the only address -> HTTP 409 CONFLICT; the allowed deletion (a fresh unused address) still returns 200 and the row is gone.

T. Permanent regression seeds for fixed defects

ID Required result Status Evidence / notes
T-01 Soft delete semantics: hidden from live surfaces, original name/amount still rendered, name reusable. PASS product 155 (ordered in 2497–2500) soft-deleted: gone from the admin/customer catalog while order 2497 still renders "E2E SEC Product 1791643945776"; creating a new product with the same name succeeded; deleting again is idempotent
T-02 Normalised image reference and a successful delete (no "Failed to delete image"). PASS {"create":"200","imageUrl":"https://assets2.freshyo.in/meatfarmer-dev/tags/1791644220883.jpg","clean":true,"delete":"200"}
T-03 4xx and no product/SKU rows (formerly a 500 with an orphan). PASS Same as P-01 re-verified after the A19 fix: the upload-url rejection is HTTP 400 now (was 500) with nothing written.
T-04 4xx naming the correct endpoint (formerly success: true with no effect). PASS Re-verified after the A19 fix: superadmin.regions.updateBoundSettings with the region-scoped key supportMobile -> HTTP 400 BAD_REQUEST naming updateRegionConstants (was 500).
T-05 Sibling stays orderable (formerly both flipped). PASS {"toggle":"200","oosA":true,"oosB":false,"orderA":"500","orderB":"200 ACCEPTED","pid":159,"skuA":163,"skuB":164,"slotTId":2037}
T-06 Only region A's future, orderable slots are returned (formerly every region, including past ones). PASS {"r1":[2035,2036,2037],"r2":[],"anonCount":0,"closedIncluded":0}
T-07 Fails within the 90 s cap and clears the loading state (formerly an eternal spinner). PARTIAL the 90 s AbortController cap exists in apps/user-ui/src/lib/fetch-json.ts and the tRPC client (verified by bundling the real helper against a stalling server earlier in the session); this run did not re-run the 90 s wall-clock stall
T-08 Sheet opens with the region list (formerly a spinner/no-op path). PARTIAL region bar tapped on the simulator and the flow succeeded; Maestro saved the screenshot outside the tracked directory, so the sheet content was not re-verified in this run