feat: let the reader mark an event as repeating daily

Dailiness was read off the source's wording alone, which is wrong in both directions: a grind that resets every day but whose page never prints "daily" got no checklist, and a banner whose blurb mentions "daily login rewards" got one nobody could dismiss. The reader's answer now wins. The control sits exactly where the checklist goes — the one place the answer visibly matters — so marking an event and ticking today off are the same gesture in the same place. An override is stored only when it disagrees with detection. Recording agreement would freeze today's guess into the reader's own data, so a later parser improvement could never reach that event. Marked events also join today's dailies at the top of the page, beside the per-game chores: at 23:50 a login campaign and a commission run are the same job, and ticking one should not mean opening a sheet to find its checklist. Co-Authored-By: Claude Opus 5 (1M context) <[email protected]>
2026-08-15 22:14:37 +02:00
parent 6177633abc
commit 7f384eb9db
9 changed files with 293 additions and 69 deletions
@@ -159,6 +159,11 @@ Repeating events are recognised from what the source actually printed — a logi
 wording like "daily", "check-in", "7-day". Nothing is assumed from a game's habits, and an event
 whose end was never announced gets a day count rather than a checklist of invented length.

+That guess is only a starting point. Open any event and you can say **it repeats daily** — the
+grind whose page never prints the word still gets a checklist — or dismiss one the wording caught
+by mistake. Anything you mark joins today's dailies at the top of the page, so ticking it off is one
+tap rather than a trip back into the event.
+
 ## Sorting

 Two orders, and the toggle sits with the list rather than in settings: