Session limit banner contradicts /usage after window reset: usage shows ~3%, requests refused with a reset time 4+ hours later than actual recovery

Environment

• Claude Code 2.1.201, macOS (Darwin 25.4, M4), Max subscription
• Timezone: Europe/Belgrade
• Heavy parallel use: interactive CLI session + multiple Claude Agent SDK sessions on the same account

Timeline (2026-07-04, local time)

1. ~10:40 — hit session limit: banner "You've hit your session limit · resets 11:10am (Europe/Belgrade)". Expected, heavy morning.
2. Waited past 11:10, made a fresh request shortly after 11:00–11:10.
3. Immediately refused again: "You've hit your session limit · resets 4pm (Europe/Belgrade)".
4. /usage at that same moment showed ~3% used — consistent with a freshly reset window, contradicting the refusal.
5. Requests actually started succeeding around 11:39 — more than 4 hours before the stated 4pm reset.

Expected

Either /usage and the session limiter agree (if the rolling window still holds morning usage, /usage should not show ~3%), or a fresh window should accept requests. The stated reset time was off by 4+ hours versus actual recovery.

Impact

The contradictory signals make it impossible to schedule work around the limit. Both the interactive session and Agent SDK sessions (same account) were refused during the window in which /usage reported ~3%.

Notes

• The refusal text was received identically by query() sessions from @anthropic-ai/claude-agent-sdk and by the interactive CLI, so it is account-level, not per-surface.
• Happy to provide request IDs/timestamps if pointed at where to find them.