A failed write says so

Steps

1. 1 None Offstage: provisioning an event to sell (the instance had none on sale) 0:10
2. 2 Member A member puts a ticket in the cart 0:39 ▣

   411px — a phone, where a silent reload is completely indistinguishable from a dead button.

3. 3 Member Offstage: the ticket goes into the cart 0:43
4. 4 Member The cart, with the ticket in it 0:48 ▣

   One line, one Remove button. Everything below happens without this page being reloaded — which is the point.

5. 5 Member Offstage: another device empties the cart 0:50
6. 6 Member Press the button that is now stale 0:51 ▣

   Before plan 128 this reloaded as though it had worked. The item was already gone, so the page even looked correct — which is exactly how a silent failure survives review.

7. 7 Member The helper hands back an outcome, never a bare body 0:54

   `{ok, status, code, message, data}`. The old helper returned the parsed body and discarded `res.ok`, so there was nothing to check and nothing to paint.

Notes

Add note

Sign in to leave a timestamped review note. Notes land in the same review backlog as in-page annotations.

1. No notes on this clip yet.

Run history (6)

• 20260830T213639Z-3499cea — passed · 3499cea
• 20260830T182912Z-77584d6 — passed · 77584d6
• 20260830T180118Z-bd2e5e8 — passed · bd2e5e8
• 20260830T175010Z-7720b19 — passed · 7720b19
• 20260830T170145Z-b690bff — passed · b690bff
• 20260826T040827Z-eadc380 — passed · eadc380