docs(04-04): device gate final verdict — PASSED

This commit is contained in:
araharah-executor
2026-10-24 03:18:26 +08:00
parent b427ca071c
commit 280fd68147
@@ -175,3 +175,21 @@ real client proves Telegram actually delivers the button's query string into the
script later (`node bot/scripts/register-commands.mjs`) — non-default writes worked script later (`node bot/scripts/register-commands.mjs`) — non-default writes worked
for this same token in phase 2, so this is plausibly a transient DC defect, and for this same token in phase 2, so this is plausibly a transient DC defect, and
default scope + client cache may also simply recover it. default scope + client cache may also simply recover it.
---
## FINAL VERDICT — 2026-10-24: **PASSED** (user: "everything else is approved")
| Leg | Verdict |
|---|---|
| 1. Android deep-link hand-off | PASS — destination card preloaded |
| 2. iOS deep-link hand-off | PASS |
| 3. Desktop deep-link hand-off | PASS — destination card + normal location chain |
| 4. Home-screen relaunch | PASS |
| 5. Unknown-id state | ACCEPTED (user) — BotFather Main Mini App now configured (carrier fixed); the honest-unavailable surface itself is covered by automated DP gates + the `?mock` capture; on-device re-send of the startapp link not re-confirmed after the BotFather change (user deferred) |
| 6. Out-of-area refusal | PASS |
Post-gate fixes shipped during this round: map tilt + building extrusion (`c6bbd414`),
/start logo (`135621f`), command-scope shadow law (`54a2b54`). Live deploy `41dedd84`.
Known-open cosmetic: /cari absent from the client command menu (Telegram non-default
setMyCommands defect — diagnosis above; command itself works when typed).