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 c934b26..867d777 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
@@ -232,3 +232,23 @@ the deployed origin (pre-fix equivalent → 401/tampered).
 **Re-test:** app should now validate → chain runs → permission ask /
 LocationManager read → LIVE. Probe should read `s ok · loc live` on
 success.
+
+## 2026-10-23 round 7 — probe readings (legs largely passing)
+
+- **Android Telegram:** `s ok`, app live — leg 1 core WORKS.
+- **Telegram Desktop:** `s ok · loc live` — tdesktop webview delivered a real
+  geolocation fix natively (better than the assumed issue #77 denial class);
+  GEO-02's denied path remains provable on the plain-browser leg / clients
+  where geolocation is unavailable.
+- **Plain Chrome:** `WA 6.0/unknown · q 0ch · s malformed · loc denied` — the
+  DESIGNED off-Telegram state; leg 5's pass condition (denial is deliberate,
+  not blank). No webview can work without Telegram identity — correct.
+
+**Cosmetic fix (`19a51e5`, deploy `1a6947ef`):** LOCATION SETTINGS was visible
+off-Telegram (SDK stub defines LocationManager and reports 6.0) where
+`openSettings()` is a no-op. CTA eligibility now shares the chain's
+`isVersionAtLeast("8.0")` gate → the button hides on unsupported clients.
+
+**Remaining for the exit:** Android boot-state choreography + reopen
+(no second prompt), Android stale-fix walk (A1), iOS (device permitting),
+mid-session theme flip leg, then verdicts on all six legs + probe removal.