Usage UI is misleading when weekly limit is exhausted but the 5-hour meter is full

Summary

When the weekly included Codex allowance is exhausted, the Usage UI can still show the 5-hour window as fully available. This suggests that included usage is available even though the weekly limit blocks it and subsequent supported usage draws from purchased credits.

Why this is confusing

A user sees a full 5-hour meter and may reasonably assume they have included usage available. The UI does not make it prominent that the 5-hour allowance is currently inactive because the weekly allowance is exhausted, or that paid credits are now being consumed.

Suggested UX

• Show a primary status: Included usage unavailable until the weekly reset.
• Label or visually disable the 5-hour meter: 100% remaining, inactive while weekly limit is exhausted.
• Show Using purchased credits now prominently, with the remaining credit balance and expiration date.
• Clearly separate included plan allowance from pay-as-you-go credits.
• Optionally show estimated/current task credit consumption.

Environment

Codex desktop on Windows, personal Plus account. No account identifiers or balance values included.

No file or test is named. Start by locating the desktop Usage UI and the logic that combines weekly included usage, the 5-hour meter, and purchased credits. Reproduce the state where the weekly allowance is exhausted while the 5-hour meter remains full, then verify that the UI clearly distinguishes inactive included usage from active purchased-credit usage.