Session limit still enforced after plan upgrade — upgrade doesn't lift the cap it was purchased to remove

Summary

Upgraded my subscription specifically to get higher usage limits, and Claude Code still blocks me with a session-limit message after the upgrade. Re-authenticating did not fix it. If an upgrade doesn't lift the cap in the same session window the user upgraded to escape, the upgrade isn't delivering what was paid for.

Environment

• Claude Code 2.1.214, macOS (Darwin 25.5.0)
• Auth: claude.ai OAuth (subscription, not API key)

Steps to reproduce

1. Hit the session usage limit on the lower plan mid-window.
2. Upgrade the plan (upgrade confirmed on the account).
3. Run /logout then /login in Claude Code to refresh credentials.
4. Continue working.

Expected

Limit is lifted (or re-evaluated against the new plan's cap) once the upgraded plan is active on the account.

Actual

Still shown the session-limit message and blocked.

Diagnostics already ruled out

• Not a stale token: fresh OAuth token issued after the upgrade (verified expiry timestamp post-login).
• Not the wrong account: cached credential is the upgraded account, and it carries subscriptionType: max.
• So the client knows the plan; the limit enforcement apparently doesn't, or prior-window usage is being counted against the user in a way that makes the upgrade have no effect at the exact moment it was purchased for.

Ask

Either apply the new plan's cap immediately on upgrade (re-evaluate the current window against the new limit), or state clearly at the point of upgrade that the current window's block persists until reset. Paying to remove a cap and remaining capped with no explanation is a bad purchase experience.