Cian Johnston c8b1fa3196 fix: use UTC day boundaries for chat auto-archive eligibility (#25597) ...

Fixes CODAGT-311.

Users receive too many auto-archive notification emails because the
dbpurge loop runs every 10 minutes and archives chats on each tick using
timestamp-precise cutoffs, causing chats to trickle past the threshold
continuously.

Switch archive eligibility from timestamp arithmetic to date arithmetic
(UTC day boundaries). All chats whose last activity falls on the same
UTC date are now archived together on the first tick after midnight UTC,
reducing notification emails to ~at most~ probably one per day.
(Exception: if we hit the auto-archive limit)

- SQL compares `(last_activity AT TIME ZONE 'UTC')::date` against cutoff
date
- Go truncates current time to start-of-day before subtracting archive
days
- Tests verify date boundary semantics including late-activity and batch
edge cases
- Docs updated to describe UTC day boundary behavior and at-most-daily
notification cadence

> [!NOTE]
> Generated by Coder Agents

2026-05-22 11:39:44 +01:00

..

dbpurge_internal_test.go

feat: implement non-brittle TestDBPurgeAuthorization (#21442)

2026-01-21 11:27:01 +11:00

dbpurge_test.go

fix: use UTC day boundaries for chat auto-archive eligibility (#25597)

2026-05-22 11:39:44 +01:00

dbpurge.go

fix: use UTC day boundaries for chat auto-archive eligibility (#25597)

2026-05-22 11:39:44 +01:00