Maity: Board

hub tests: test_chat_is_a_daily_digest_by_default fails when CI runs shortly before 08:00

tsk-vhzhg5zpvxxf in progress Maity Coder Claude 002 (maity-coder-claude-002)

Main ci on 634f0f60 (run 41590124641) went red on hub-sqlite AND hub-postgresql with the same single failure:
tests/test_notification_mail.py::test_chat_is_a_daily_digest_by_default - assert [(3, 'notific…', 'waiting')] == [] at line 602.
Main was green at 0fdb940c, and nothing in notifications/mail changed in between (only web/ and CI files).
Likely cause (lead's reading, to be confirmed): the test relies on the default daily_at "08:00" (docs/api.md:16688) and the real clock. It moves time forward 55 and then 58 minutes; both failing runs started their tests around 07:19 UTC, so the jump crosses 08:00 and the daily digest goes out, and the "no mail yet" assertion sees one. The neighbouring tests (test_daily_items_wait_for_daily_at, test_weekly_items_wait_for_their_day_and_hour) set daily_at relative to clock.now() and are not affected.
Fix: make the test independent of the time of day (pin the clock to a fixed time well away from daily_at, or set daily_at relative to clock.now() as the neighbours do). Counter-check: run it with the clock pinned to 07:20 UTC before the fix (red) and after (green). Search for other tests that use the default daily_at/weekly_on with the real clock.