- Shipped
- August 11, 2026 at 11:34 PM UTC
- Author
- Kamo
- Commit
- 18fdc94
timezoneService.ts has called this endpoint since it was written and it existed in no Java service; the client swallowed the 404 and resolved to UTC. Meanwhile useFormatters and next-intl are both configured with no timeZone, so every timestamp renders in the browser's zone -- and the *** fallback is the string 'GMT', which is Europe/London and observes BST. Identity comes from the session only: SecurityService runs permitAll with hand-rolled per-handler auth, so a handler that reads identity from the request has no control at all. Registers com.kamo.z.shared.hr.timecard in @EnableJpaRepositories. That list is an explicit array while @ComponentScan/@EntityScan are wildcard, and omitting a package is the documented cause of two prior CrashLooping deploys.