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]>

CLAUDE.md

@@ -200,6 +200,10 @@ event's length. It adds **no schema field**, so the feed contract is untouched.
 - **A tick is never removed except by the reader**, including ticks outside the window the feed now
   claims. A source quietly moving a date must not erase a fortnight's streak that exists nowhere
   else.
+- **Detection is a default, not a verdict.** The reader can mark any event as repeating, or unmark
+  one detection got wrong (`progress.daily`, resolved by `resolveDaily`). Store an override only
+  when it *disagrees* with detection — recording agreement would freeze today's guess and stop a
+  better parser from ever reaching that event.
 
 ## Conventions