[Bug] Session limit reset time recalculates on each retry instead of reflecting fixed window

Bug Description
Bug: Session limit reset time changes inconsistently between attempts
What happened:
I hit my Claude Code session limit. The message shown was:
"You've hit your session limit · resets 8pm (Europe/Amsterdam)"
About 1 minute later (around 20:01), I sent another message ("ga verder"). The session limit message now showed a completely different reset time:
"You've hit your session limit · resets 1am (Europe/Amsterdam)"
Why this is unexpected:
Only ~1 minute passed between the two attempts, not the 5 hours that would justify a new rolling window starting fresh. The reset time jumped forward by 5 hours based on a 1-minute-later retry, which suggests the reset time shown isn't reflecting my actual original session window, but appears to be recalculated as "now + 5 hours" on every blocked attempt — making the displayed time meaningless as a way to know when I can actually resume.
Impact:
I can't plan my work around the reset time because it doesn't seem to reflect a real, fixed window. Every time I retry, the countdown effectively resets, which could mean I'm being shown a later time than when I actually regain access — or the tracking itself is broken.
Evidence:
Two screenshots taken ~1 minute apart, timestamps and reset times as described above. Happy to attach if needed.

Environment Info

• Platform: darwin
• Terminal: cursor
• Version: 2.1.206
• Feedback ID: e3d21222-49fc-489a-9bac-69edb00344cf

<img width="566" height="178" alt="Image" src="https://github.com/user-attachments/assets/8cc532d4-295b-4628-bc50-195c4ac8c59f" />

Errors

[]