From de07c99e8ac3fe1aba1b83a8ddeff94424711dfe Mon Sep 17 00:00:00 2001
From: araharah-executor <executor@araharah.local>
Date: Fri, 23 Oct 2026 01:19:41 +0800
Subject: [PATCH] =?UTF-8?q?docs(03-04):=20log=20debug=20round=204=20?=
 =?UTF-8?q?=E2=80=94=20settings=20CTA=20on=20the=20wrong=20instance?=
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit

---
 .../03-DEVICE-MATRIX.md                              | 12 ++++++++++++
 1 file changed, 12 insertions(+)

diff --git a/.planning/phases/03-mini-app-shell-geolocation/03-DEVICE-MATRIX.md b/.planning/phases/03-mini-app-shell-geolocation/03-DEVICE-MATRIX.md
index 9364c5e..c966fda 100644
--- a/.planning/phases/03-mini-app-shell-geolocation/03-DEVICE-MATRIX.md
+++ b/.planning/phases/03-mini-app-shell-geolocation/03-DEVICE-MATRIX.md
@@ -171,3 +171,15 @@ Erratum recorded in 03-RESEARCH.md.
 **Re-test:** restart Telegram client, reopen web app from the menu button —
 expect the REAL boot (BOT-01 → BOT-02 → LIVE with an actual permission ask or
 a live LocationManager read + LOCATION SETTINGS available on denial).
+
+## 2026-10-23 debug round 4 (missing LOCATION SETTINGS on the main denied card)
+
+**Symptom:** user still sees only TRY AGAIN / ASK VIA CHAT — no LOCATION SETTINGS.
+
+**Root cause:** executor patch-order bug — round 2 attached
+`withLocationSettings` only to the awaiting-pin card instance; the primary
+denied card (the one shown at denial) never got the CTA.
+
+**Fix (deploy `253d7a3e`):** both denied-shaped instances now build with the
+Telegram-only settings CTA. Deployed `index.html` verified to carry
+telegram-web-app.js (round 3 fix verified live via curl).