fix(todo): turn to GPS where the fused provider stays silent (ADR 0033, D32)

A stock Android 17 emulator without Google's services left GPS off at
balanced accuracy and gave no fix in five minutes, while the
notification said it was watching. A Pixel's fused provider turns GPS
and the network on by itself, but nothing noticed where one doesn't.
After twice the wait asked for without a usable fix, the service asks
GPS as well, and leaves it once the fused provider gives a usable fix;
a rough one can't tell a circle, so it counts as silence.

All four walks (arrive, drive past, reboot, leave) passed on that
emulator on GPS alone, 22 fixes, no crash.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Signed-off-by: Tizian 「ティツィアーン」 <raisondetredev@pm.me>

docs/adr/0033-halkyon-todo.md

@@ -650,7 +650,12 @@ The developer's review of 4 Nov 2026, again beside Todoist's screens.
     phone lay still (moved under 50 m, and the wait asked for over, at least three
     quarters of it, as asking anew brings a fix at once and an emulator's walk reached
     2 min within 40 s), between 30 s and 5 min, at balanced accuracy on
-    the fused provider of Android's own, GPS before Android 12. What it costs a day
+    the fused provider of Android's own, GPS before Android 12. Where that provider
+    gives no usable fix for twice the wait, the service asks GPS as well, until it
+    does: on a Pixel it turns GPS and the network on itself, but a stock Android 17
+    emulator without Google's services left GPS off and gave nothing, unnoticed,
+    behind a notification saying it watches. Always asking high accuracy was the
+    alternative, simpler, with GPS busier on every phone. What it costs a day
     wants measuring. A fix rougher than 100 m says nothing of a circle.
   - *Dwell*, so that driving past an EDEKA on the way to the next doesn't remind (the
     developer's question): crossing the circle (in at 150 m, out beyond 200 m, so a fix's error