When logging workouts around UTC boundary cutoffs, the date displayed in the workout history/calendar view can shift by +/- 1 day depending on how dates are stored versus rendered.
Suggested fix:
- Store all timestamps in UTC ISO format.
- Ensure the frontend renders and groups sessions using the user's local timezone (
Intl.DateTimeFormat or dayjs/date-fns) rather than naive UTC strings.
When logging workouts around UTC boundary cutoffs, the date displayed in the workout history/calendar view can shift by +/- 1 day depending on how dates are stored versus rendered.
Suggested fix:
Intl.DateTimeFormator dayjs/date-fns) rather than naive UTC strings.