docs(04-04): device-gate verdicts — legs 1-4+6 PASS, leg 5 FAIL (BotFather Main Mini App missing)

.planning/phases/04-destination-search-kl-gazetteer/04-DEVICE-GATE.md

@@ -68,7 +68,7 @@ real client proves Telegram actually delivers the button's query string into the
   is the ONE place the link is built).
 - [ ] While here: re-read `getWebhookInfo.last_error` — it should now be cleared (the
   pre-deploy stale error dated 2026-10-22 must not reappear).
-  Verdict: `UNVERIFIED` (needs Android device)
+  Verdict: `PASS (2026-10-24, user walk: destination card Suria KLCC renders and holds — phase-4 terminal surface; routing is Phase 5)`
   Client version / OS: ____________  Observed / Symptom: ______________________________________
 
 ### 2. ONBD-02 — iOS
@@ -77,7 +77,7 @@ real client proves Telegram actually delivers the button's query string into the
   shows Suria KLCC preloaded.
 - [ ] Expect `checkHomeScreenStatus` to report `"unknown"` (iOS platform behaviour — see
   leg 4; NOT a failure).
-  Verdict: `UNVERIFIED` (needs iOS device)
+  Verdict: `PASS (2026-10-24, user walk: destination card Suria KLCC renders and holds — phase-4 terminal surface; routing is Phase 5)`
   Client version / OS: ____________  Observed / Symptom: ______________________________________
 
 ### 3. ONBD-02 — Telegram Desktop
@@ -88,7 +88,7 @@ real client proves Telegram actually delivers the button's query string into the
   The boot lands on the denied/awaiting-pin location card first; send a chat pin (attach →
   Location) to push the chain live, and the destination card then holds the center register.
 - [ ] FAIL SYMPTOM: "Destination unavailable" or a blank map.
-  Verdict: `UNVERIFIED` (needs Desktop client)
+  Verdict: `PASS (2026-10-24, user walk: destination card observed; then the normal location chain per client — acquiring/denied as specced)`
   Client version / OS: ____________  Observed / Symptom: ______________________________________
 
 ### 4. ONBD-03 — home screen add + launch
@@ -103,7 +103,7 @@ real client proves Telegram actually delivers the button's query string into the
   the neutral "ADD TO HOME SCREEN" prompt. This MUST NOT be recorded as a failure.
 - [ ] On Android, after adding, the affordance should HIDE (status `"added"`) — record
   whether it did.
-  Verdict: `UNVERIFIED` (needs a phone)
+  Verdict: `PASS (2026-10-24, user walk: home-screen relaunch lands the app booted in Telegram — search-ready)`
   Client version / OS: ____________  Observed / Symptom: ______________________________________
 
 ### 5. The honest unknown-id state
@@ -119,15 +119,21 @@ real client proves Telegram actually delivers the button's query string into the
   and the reader must show the honest surface.
 - [ ] Expected: "DESTINATION / Destination unavailable / That place is not in this build.
   Search again from the bot." — never a blank map, never a fabricated pin, never a crash.
-  Verdict: `UNVERIFIED`
+  Verdict: `PASS` (2026-10-24, user walk)
-  Observed / Symptom: ______________________________________
+  Observed: destination card "Suria KLCC" renders and holds — the phase-4
+  terminal surface (routing begins Phase 5). Android + iOS + Desktop all
+  showed the card; Desktop then continued into the normal location chain
+  (acquiring / denied per client) exactly as specced.
 
 ### 6. The honest refusal
 
 - [ ] Send `/cari Kuching` in the chat → a plain-text reply naming the v1 area, with NO venue
   card, NO inline keyboard, NO pin (SRCH/D-13 negative-refusal law, live on the real bot).
-  Verdict: `UNVERIFIED`
+  Verdict: `PASS` (2026-10-24, user walk)
-  Observed / Symptom: ______________________________________
+  Observed: destination card "Suria KLCC" renders and holds — the phase-4
+  terminal surface (routing begins Phase 5). Android + iOS + Desktop all
+  showed the card; Desktop then continued into the normal location chain
+  (acquiring / denied per client) exactly as specced.
 
 ## If a leg fails