Rate limit reset time displays wrong timezone offset after travel

Description

The session limit status bar shows the reset time with a stale timezone offset. After travelling to a different timezone (Morocco, UTC+1) and returning home (UK, Europe/London, currently GMT/UTC+0), the displayed reset time remains 1 hour off.

Example message:

You've used 97% of your session limit · resets 11am (Europe/London)

The system timezone is correctly set to Europe/London (verified via /etc/localtime symlink, date +%Z → GMT, date +%z → +0000), but Claude Code appears to be using a cached +1 offset from the previous location.

Expected Behaviour

The reset time should reflect the current system timezone, not a previously cached one. Since Europe/London is currently GMT (UTC+0), the displayed time should update accordingly.

Steps to Reproduce

1. Travel to a UTC+1 timezone (e.g. Morocco)
2. Use Claude Code (timezone offset gets cached)
3. Return to a UTC+0 timezone (e.g. UK in winter)
4. Observe that the rate limit reset time is still 1 hour off

Environment

• OS: macOS 15 (Sequoia)
• Claude Code: installed via Homebrew
• System timezone: Europe/London (GMT, +0000)
• Previous timezone: Morocco (UTC+1)