[Feature]: Automatically redeem a banked Codex reset at the usage limit #22467

Problem

T3 shows available banked Codex resets in Usage → Limits and lets a user redeem one with Use reset, but limited threads cannot use an available reset without someone noticing the limit and applying it manually.

For unattended work, I would prefer T3 to use a previously granted reset when the included allowance is exhausted, then continue the waiting thread, rather than leave the work parked until the natural reset time.

Proposed behaviour

• Add an explicit opt-in setting for a Codex account/provider instance to redeem one banked reset when its included usage limit is exhausted.
• Do not redeem while included usage remains. Use a reset only for the account that hit the limit, and report which account/reset was consumed and whether the provider confirmed it.
• If no reset is available, or redemption is not confirmed, keep the thread limited and retain the existing wait/manual-resume choices.
• After confirmed redemption, refresh that account's limits and resume eligible limited threads as soon as the refreshed allowance permits, while respecting a thread's Stop/cancel state.
• Keep this opt-in and off by default because banked resets are finite and consuming one is irreversible.

Current behaviour

T3's Usage and limits guide documents a reset count and manual Use reset action. OpenAI describes banked resets as resets the account holder applies manually in How banked Codex resets work. The upstream Codex app has a related request to queue a reset for when a usage limit is exhausted: openai/codex#32218.