Quota error (403) omits session-cap refresh time, presents only paid options

What version of Kimi Code is running?

0.29.0

Which open platform/subscription were you using?

Moderato

Which model were you using?

kimi code k3

What platform is your computer?

Microsoft Windows NT 10.0.22631.0 x64

What issue are you seeing?

When the 5-hour session usage cap is reached, the CLI shows:
"403 You've reached your usage limit for this billing cycle. Your quota
will be refreshed in the next cycle. To continue now, purchase extra
usage or upgrade your plan."

Problems:

1. It says "billing cycle" when the binding limit is the 5-hour session
   window. My weekly budget was only 20% used — the weekly cycle was
   nowhere near exhausted. The message implies it was.
2. It never states when the session cap refreshes — in my case, ~1 hour
   later. Waiting was the correct remedy and it isn't mentioned at all.
3. It presents only paid remedies (purchase/upgrade), funneling users
   who don't know about the session cap toward purchases they don't need.

For these reasons, the error message comes across as openly deceitful, providing just enough information to receive payment, but no link, or guidance for the user to check if their refreshable budgets are the culprit, either 5-hour, or weekly.

What steps can reproduce the bug?

i assume its as simple as hitting either the 5-hour budget, or the weekly budget.

What is the expected behavior?

i would expect the error message to at least contain a link to kimi.com/code/console, or at LEAST a mention that session budget may be a suspect. i find it highly disturbing that instead of such transparency, the error message is followed up with a message that seems to be intended to keep this message out of the public eye. this supports my assumption that this is a malicious attempt to FOMO unsuspecting customers into parting with even more money.

Additional information

this is my first session using kimi code, and i was incredibly impressed with how thoughtful and efficient it is. i was actually quite jubilant with my discovery of it, and the performance of k3 in the coding environment, but this error message really soured my overall opinion of the product. i still intend on using it, but if i feel that strongly, i can be certain that if other people feel the same way, they may not be as forgiving. this feels counterproductive, as I'd be willing to pay for extra usage if i felt like this was more transparent. instead of rewarding you because of my positive experience, i feel like you're farming your already loyal and subscribed consumers for even more. its disappointing, because your product is fantastic, you've EARNED more loyalty with its performance, but you destroy that loyalty with what appears to be exploitative tactics.

Reproduce the 403 after reaching the 5-hour session cap, then trace the CLI's quota-error handling and message formatting. Confirm how the session refresh time and weekly budget status are obtained. Done means the error identifies the binding limit, states when it refreshes when available, and does not present paid options as the only remedy.