CodexPeek v0.3.6

Windows stability fixes and local usage-exhaustion forecasting.

Highlights

Adds rounded exhaustion forecasts for the Primary and Secondary usage windows, calculated independently for each local profile.
Shows whether the current pace is likely to exhaust the limit before reset and estimates the remaining allowance at reset.
Displays explicit collecting, low-activity, stale, invalid, and already-exhausted states instead of presenting unreliable estimates.
Fixes update checks that could terminate the app when the TLS provider was not initialized.
Fixes browser authorization not opening when the default account was logged out by initializing COM on the shell worker thread.
Ensures user-requested update checks show one owned result dialog for current, failed, or available-release results.

Forecasting is enabled by default and can be disabled from the tray menu.
Successful samples are stored only in %APPDATA%\CodexPeek\usage-history.json.
Stored fields are limited to the internal profile ID, Primary or Secondary window kind, usage percentage, reset timestamp, and observation timestamp.
Email addresses, account IDs, profile names and paths, authentication tokens or files, prompts, conversations, proxy settings, and raw CLI responses are not stored.
History stays on the device and is never uploaded or synchronized. It is retained for at most 30 days and 1,000 samples per profile/window.
Use Clear usage forecast history in the tray menu to remove all samples. Removing a managed profile removes its samples.
Installer and portable removal preserve %APPDATA%\CodexPeek, so history can remain until it is cleared in the app or deleted manually.
Forecasts are estimates based on recent local observations and do not guarantee actual OpenAI limits, policy, or future usage.

CodexPeek is currently unsigned, so Windows SmartScreen may show a warning.

Release packaging contract, formatting, all-target tests, Clippy with warnings denied, release build, checksums, and installer install/uninstall smoke tests passed in GitHub Actions.
The full Windows UI and multi-DPI manual matrix was not independently rerun before publication.