# active-menu-window

_Witnessed 2026-09-04T06:15:29.001Z — QRATE-UAT-1_

_This fixture serves breakfast 06:00-10:00 and dinner 17:00-23:00. I arrive with the phone's timezone set to **Asia/Dhaka**, which puts local time between the two - closed. A real diner gets this by travelling, or by having a phone set wrong. The journey promises a closed state and zero dishes._

### 01 · PATRON

**I expected:** my phone agrees the restaurant is shut right now

**I saw:** My phone reads 12:15:29 local (Asia/Dhaka) - after breakfast, before dinner.

### 02 · PATRON

**I expected:** the very first thing the server tells my phone is that it is shut

**I saw:** Its first answer is menus_closed=true with 0 items. The gate works at the server. Everything after this is about what my phone then SHOWS me.

### 03 · PATRON

**I expected:** so the screen tells me they are closed, and offers me no dishes

**I saw:** STOPPED — It does not. I am shown 1 dishes and no closed message, including "Canary Dinner Special" - a 17:00-23:00 dish, at 12:15:29 local. The server was asked the same question twice: closed=true/items=0 then closed=false/items

---

**Verdict:** STOPPED

**Why it ended here:** It does not. I am shown 1 dishes and no closed message, including "Canary Dinner Special" - a 17:00-23:00 dish, at 12:15:29 local. The server was asked the same question twice: closed=true/items=0 then closed=false/items=0 - the only thing that changed between them is that the app minted a table session for me. Screen reads: Mains C Canary Dinner Special Canary dinner-only item — DO NOT MODIFY. $22.99 ✦ ✦ ✦ ✦ — BEFORE YOU BROWSE — Anything we should know? Do you have any dietary restrictions or allergens? We’ll tailor the 

The server's own answers across this walk: closed=true/items=0 then closed=false/items=0. The gate is correct at the API on a fresh scan; what a person is SHOWN is the thing that diverges.