Copilot CLI incorrectly blocks usage with quota_exceeded (402) despite paid over‑quota enabled

[vlk-cmd]

Describe the bug

We encountered an issue in Copilot CLI where requests are rejected with a 402 quota_exceeded error, even though over‑quota billing is enabled and should allow continued usage.
The behavior effectively blocks Copilot usage instead of charging for additional requests beyond the quota.

Affected version

v1.0.49

Steps to reproduce the behavior

1. Give a seat for a new account in the company
2. Let account use all quota for a month (300 premium requests)
3. Pay attention that additional requests not billed and instead user getting the error

Actual result:
Copilot CLI rejects all further requests with quota_exceeded
No fallback or paid continuation occurs
Tool becomes unusable after quota is reached

402 {"error":{"message":"You have no quota","code":"quota_exceeded"}}
(Request ID: F499:17ECFD:1915C27:1AA3993:6A0DC655)

Expected behavior

When the premium request quota is exceeded:
Requests should continue to be processed
Additional usage should be billed according to overage pricing like before

Additional context

This functionality was working correctly before:

Requests continued after quota exhaustion
Over‑quota usage was successfully billed

The issue started occurring between May 19 and May 20
No intentional configuration changes were made on our side

[vlk-cmd]

It would be helpful to extend the error message to clearly indicate which quota has been exceeded — for example:

User quota
Organization quota
Organization budget limit

Currently, the message is too generic and does not provide enough context to identify the root cause.
In our case, the issue was resolved after increasing the organization budget, which suggests that the actual limit exceeded was at the organization budget level, not the user quota.