Marc-André Bombeck be112df972 fix(profile): report the time zone the server uses on /api/user/profile ...

`/api/auth/me` has reported the resolved zone, the stored one or the
instance default when the stored value is unusable, while
`/api/user/profile` returned the raw column. A client reading the
profile could cut days differently from the server, and sending the
value back in a PATCH was refused.

Both reads, and the profile PATCH answer, now go through one
`resolveStoredTimezone`. The field stays a string and always holds a
valid IANA name. The web account editor already reads the resolved
zone from `/api/auth/me` and saves through the validating timezone
route, so it shows the zone in use and can only write a valid one.

2026-09-25 07:39:07 +02:00

..

__tests__

fix(tz): refuse bare UTC offsets as a timezone

2026-09-24 12:23:00 +02:00

format.ts

fix(tz): refuse bare UTC offsets as a timezone

2026-09-24 12:23:00 +02:00

intl-cache.ts

fix(api,lib): consent before reuse, tighter inputs and caches that tell on themselves

2026-06-11 23:20:38 +02:00

local-day.ts

fix(tz): settle localHmAsUtc's offset at the target local time

2026-07-19 02:05:24 +02:00

resolver.ts

fix(profile): report the time zone the server uses on /api/user/profile

2026-09-25 07:39:07 +02:00

start-of-utc-day.ts

fix(mood): key mood rollups by the local day, not the UTC day

2026-07-24 03:50:14 +02:00

wall-clock.ts

fix(medications): drop the fabricated-Date wall clock from the window status

2026-07-19 02:13:08 +02:00