- Ya
- 11 Agosti 2026, 23:37 UTC
- Mwandishi
- kamo
- Ahadi ya
- b70732f
The client Organization model had no timezone field, useFormatters and next-intl are both configured with no timeZone, and timezoneService's backend call 404'd -- so every timestamp rendered in the browser's zone, and the server's during SSR. Mirrors all 27 TimezoneType values rather than a subset: a partial map is a silent half-mirror where an unmapped org falls through to the browser zone with no signal. GMT maps to Europe/London, not UTC -- it observes BST, so conflating them shifts a whole day's hours by an hour for half the year. The org zone is a DISPLAY fallback only. A production census found all 13 orgs on the untouched PACIFIC default while members span PACIFIC/EASTERN/ARIZONA/UTC/ INDIA, so the timecard zone of record comes from the work site instead.