account.getQuota returns the request timestamp as resetDate instead of the quota reset date

Describe the bug

The Copilot CLI JSON-RPC account.getQuota response returns an incorrect resetDate for quota snapshots.

Environment:

• GitHub Copilot CLI: 1.0.80
• CLI started with:
  copilot --server --no-auto-update --log-level error --stdio

I sent the following JSON-RPC request:

{"jsonrpc":"2.0","id":2,"method":"account.getQuota","params":{}}

For premium_interactions, the raw response included:

{
"entitlementRequests": 1500,
"usedRequests": 1500,
"remainingPercentage": 0,
"resetDate": "2026-08-15T23:06:14.840-07:00"
}

This timestamp matched the time the account.getQuota request was made, rather than the account's actual premium quota reset date. The same resetDate timestamp was returned for chat, completions, and premium_interactions.

The GitHub Copilot web UI shows the actual billing-cycle reset date, for example:

Resets in 16 days on Sep 1, 2026

The CLI response does not include a separate quota_reset_at or equivalent field.

Because resetDate tracks the request time, CLI/API consumers cannot accurately display when the premium quota resets.

Expected behavior:

• resetDate should contain the actual quota/billing-cycle reset timestamp; or
• account.getQuota should expose a separate reset timestamp field for each quota bucket.

Actual behavior:

• resetDate is effectively the quota-fetch timestamp and changes each time account.getQuota is called.

Affected version

No response

Steps to reproduce the behavior

No response

Expected behavior

No response

Additional context

No response

首先定位 JSON-RPC 处理程序 account.getQuota 以及构建配额快照的代码。跟踪每个配额 bucket 的 resetDate 是如何填充的，然后验证重复请求不再返回请求时间戳，并且响应会公开实际的配额重置时间。