# uat-w062-resume-served

_Witnessed 2026-09-07T23:38:21.200Z — QRATE-UAT-1_

_W-062's blocker said nothing anywhere could move an order to SERVED. My own W-058 walk refuted that on the new uses_kds=false fixture, so steps 7 and 10 of this journey are reachable for the first time. The backgrounding is simulated — a headless tab cannot truly sleep — and that limit is carried into the verdict._

### 01 · DINER

**I expected:** Walk in and order two dishes

**I saw:** table 10093 · pressed "Place order $10.50 ›" → ledger badges ["Ordered","ORDERED","ORDERED"]

### 02 · WAITER

**I expected:** Sign in and enter the order in the till

**I saw:** entered in POS; kitchen auto-started on the card: true

### 03 · DINER

**I expected:** Put the phone away

**I saw:** document.visibilityState is now "hidden" · last seen ["Ordered","IN THE KITCHEN","IN THE KITCHEN"]

### 04 · WAITER

**I expected:** Carry the food out and mark it served while the phone is away

**I saw:** pressed Mark Served 2x while the diner's tab was hidden

### 05 · DINER

**I expected:** Take the phone back out — no reload — and watch

**I saw:** caught up on its own within 45s: true · badges ["Ordered","SERVED","SERVED"] · absence-guard "a Served badge on the diner's own ledger" present 2x

### 06 · DINER

**I expected:** Now reload deliberately — the control that decides whose fault it is

**I saw:** after reload badges [] → LIVE CATCH-UP WORKS

---

**Verdict:** WALKED

**Why it ended here:** Steps 7 and 10 of this journey were driven for the first time, on the uses_kds=false fixture STR-1235 delivered. Outcome: LIVE CATCH-UP WORKS.