Show Codex banked reset expiries in Usage

[JaviChulvi]

Summary

• Show the available banked reset count for Codex sessions using an OpenAI subscription.
• List each available reset's expiry date when Codex supplies credit details, and say when dates are unavailable.
• Keep banked resets distinct from the normal usage-window reset time.

Validation

• bun run check
• cargo fmt --check --manifest-path src-tauri/Cargo.toml
• cargo check --manifest-path src-tauri/Cargo.toml
• git diff --check

🛠️ PR Summary

_{Made with ❤️ by Ultralytics Actions}

🌟 Summary

Codex usage now displays available banked resets and their expiry dates when credit details are provided, keeping them separate from usage-window resets.

📊 Key Changes

• Adds banked reset count and expiry data to usage snapshots.
• Reads available Codex reset credits, sorts expiry dates, and preserves entries whose dates are unavailable.
• Shows the count and per-reset expiry details in the Usage panel, including a note when expiry dates are unavailable for remaining resets.

🎯 Purpose & Impact

Users can distinguish banked Codex resets from normal usage-window resets and see when listed resets expire.

[UltralyticsAssistant]

👋 Hello @JaviChulvi, thank you for submitting a ultralytics/lite 🚀 PR! This automated message confirms your contribution was received, and an Ultralytics engineer will assist with the review. To ensure a seamless integration of your work, please review the following checklist:

• ✅ Define a Purpose: Clearly explain the purpose of your fix or feature in your PR description, and link to any relevant issues. Ensure your commit messages are clear, concise, and adhere to the project's conventions.
• ✅ Synchronize with Source: Confirm your PR is synchronized with the ultralytics/lite main branch. If it's behind, update it by clicking the 'Update branch' button or by running git pull and git merge main locally.
• ✅ Ensure CI Checks Pass: Verify all Ultralytics Continuous Integration (CI) checks are passing. If any checks fail, please address the issues.
• ✅ Update Documentation: Update the relevant documentation for any new or modified features.
• ✅ Add Tests: If applicable, include or update tests to cover your changes, and confirm that all tests are passing.
• ✅ Sign the CLA: Please ensure you have signed our Contributor License Agreement if this is your first Ultralytics PR by writing "I have read the CLA Document and I sign the CLA" in a new message.
• ✅ Minimize Changes: Limit your changes to the minimum necessary for your bug fix or feature addition. "It is not daily increase but daily decrease, hack away the unessential. The closer to the source, the less wastage there is." — Bruce Lee

For more guidance, please refer to our Contributing Guide. Don't hesitate to leave a comment if you have any questions. Thank you for contributing to Ultralytics! 🚀

[UltralyticsAssistant]

🔍 PR Review

_{Made with ❤️ by Ultralytics Actions}

Reviewed the Rust usage snapshot and Codex parsing alongside the Usage panel. Banked resets remain distinct from normal usage-window resets, and unavailable expiry details are surfaced. LGTM; no concrete regressions found.

[glenn-jocher]

Thanks @JaviChulvi for adding banked reset expiry details! Merged after a clean full-diff review. I made no code changes to your PR: I verified the fields against the installed Codex protocol and checked the UI cases for dated credits, non-expiring credits, missing details, and zero available resets. Local checks and CI passed.

This ships with v0.0.59, alongside #196. Please test the release with your Codex account, including the expiry details shown in Usage. If you find anything else to improve, please open a new PR with any future fixes or features. Thanks again!