Under the hood
Usage-limits data is now documented as null whenever the usage fetch is failing, not just when it predates rate limits
What
The documentation for the usage-limits data (limits[]) now clarifies that this field is null not only when the server's response predates the usage meters, but also any time the usage fetch is currently failing. Even though the CLI may separately build its own fallback row from rate-limit response headers, that fallback is never surfaced through this field — it stays null during a failure.
Why
This clarifies that a null value doesn't distinguish between "no data yet" and "the fetch is currently failing," and that a fallback estimate elsewhere in the CLI won't appear here.