fix(todo): only a full wait counts towards lying still (ADR 0033, D32)

Asking for fixes at a new interval brings one at once, so each doubling
brought the next: on the emulator's walk the wait went from 30 s to
120 s within 40 s, and would reach 5 min within a couple of minutes,
leaving someone who sets off again unnoticed for that long. A still fix
now counts only once at least three quarters of the wait asked for
has passed; a move still starts over at once.

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

docs/adr/0033-halkyon-todo.md

@@ -647,7 +647,9 @@ The developer's review of 4 Nov 2026, again beside Todoist's screens.
     Google's. The price is a notification while places wait, on a channel of the least
     importance (`places_watched`), and the fixes, kept few (`LocationDwell.interval`):
     as long as reaching the nearest circle takes at 30 m/s, doubled for each fix the
-    phone lay still (moved under 50 m), between 30 s and 5 min, at balanced accuracy on
+    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
     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