API errors causing quota limits/usage

Bug Description
My weekly usage limit was reached last night, when I look at the /insights report the primary cause for this appears to be (server-side) API errors that were triggered repeatedly on Tuesday and Wednesday while I was in several bigger sessions. I was not aware that server-side errors would have any (let alone this large of an) impact on token usage. The report from /insights shows it as:

Output Token Limit Errors
A large share of your sessions hit the 500 output token maximum, causing API errors that truncate or entirely lose transcript content. Raising your output token limit or asking Claude to summarize concisely and chunk long responses would preserve your work history and avoid mid-task failures.

But this is likely the 529 API server overloaded errors that I hit repeatedly during the week.

I tried switching to Sonnet for the remainder of my time until reset, but then almost immediately hit the limit there too (despite the interface making it look like a separate quota)

Two different suggestions/feedback items:

1) Server-side API errors should not cause significant quota impact, or any impact on quota should be detected and limits adjusted to account for it.
2) Sonnet having a separate usage meter in the interface but then not having it's own limit is counterintuitive, recommend clearing that up in the UI.

Several similar/related community posts to illustrate this is not a problem limited to my account:

https://www.reddit.com/r/ClaudeCode/comments/1ugx6ne/cache_misses_because_of_api_error_server_is/
https://www.reddit.com/r/ClaudeCode/comments/1uhr5pi/limits_reduced/
https://www.reddit.com/r/ClaudeCode/comments/1uhh2xv/sonnet_weekly_limit_bound_to_all_models/
https://www.reddit.com/r/ClaudeCode/comments/1uhgp8x/anyone_elses_usage_getting_eaten_alive_today/

Environment Info

• Platform: darwin
• Terminal: tmux
• Version: 2.1.191
• Feedback ID: 45ee1093-cb6e-4bab-b078-17808481e630

Errors

[]