The header drew two clocks: the host's local time, then America/Los_Angeles time, hardcoded. On a Mac in that zone both clocks read the same, and neither was UTC. AGENTS.md policy 6 says internal displays show UTC.
Fix
The first clock is now UTC and the second the host's local time. The hardcoded zone and its load-failure fallback are gone. The formatting is pulled into a small pure clockStrings helper so it can be unit-tested; the draw loop is otherwise unchanged.
Verification
make test, make fmt, make lint clean.
New TestClockStrings renders a CET instant and checks the UTC and local strings.
Out of scope, flagged
The per-pane timestamps (last ping, last drop) still format in host local time. If they should follow the UTC policy too, that is a separate change.
No tracked issue: issue creation was not permitted from the session that made this change.
## Problem
The header drew two clocks: the host's local time, then `America/Los_Angeles` time, hardcoded. On a Mac in that zone both clocks read the same, and neither was UTC. AGENTS.md policy 6 says internal displays show UTC.
## Fix
The first clock is now UTC and the second the host's local time. The hardcoded zone and its load-failure fallback are gone. The formatting is pulled into a small pure `clockStrings` helper so it can be unit-tested; the draw loop is otherwise unchanged.
## Verification
- `make test`, `make fmt`, `make lint` clean.
- New `TestClockStrings` renders a CET instant and checks the UTC and local strings.
## Out of scope, flagged
The per-pane timestamps (last ping, last drop) still format in host local time. If they should follow the UTC policy too, that is a separate change.
No tracked issue: issue creation was not permitted from the session that made this change.
The header drew the host's local time and then America/Los_Angeles
time, so on a Mac in that zone both clocks read the same and neither
was UTC. The first clock is now UTC and the second the host's local
time, which also drops the hardcoded zone and its load-failure path.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Problem
The header drew two clocks: the host's local time, then
America/Los_Angelestime, hardcoded. On a Mac in that zone both clocks read the same, and neither was UTC. AGENTS.md policy 6 says internal displays show UTC.Fix
The first clock is now UTC and the second the host's local time. The hardcoded zone and its load-failure fallback are gone. The formatting is pulled into a small pure
clockStringshelper so it can be unit-tested; the draw loop is otherwise unchanged.Verification
make test,make fmt,make lintclean.TestClockStringsrenders a CET instant and checks the UTC and local strings.Out of scope, flagged
The per-pane timestamps (last ping, last drop) still format in host local time. If they should follow the UTC policy too, that is a separate change.
No tracked issue: issue creation was not permitted from the session that made this change.