session start reports codex_timeout when the Codex account has hit its usage limit

[0thernet]

Summary

oompa session start personal --provider codex --json fails with UNAVAILABLE / codex_timeout ("Codex did not complete the operation within Oompa's bounded deadline") when the underlying cause is that the ChatGPT account has exhausted its Codex usage quota. The timeout wording tells the operator to inspect state and retry, which cannot help.

Reproduction

• Daemon at schema 60 (main after Repair the pre-authority upgrade migration and prepare the Oompa 0.8.4 candidate #221), one signed-in Codex profile, oompa doctor --offline passing, oompa status showing 0 starting sessions.
• oompa session start personal --provider codex --json twice: both return codex_timeout after the bounded deadline.
• Under the same isolated profile home, the pinned runtime answers directly:

$ CODEX_HOME=<profile>/codex-home codex login status
Logged in using ChatGPT
$ CODEX_HOME=<profile>/codex-home codex exec --skip-git-repo-check "Reply with exactly OK and nothing else."
ERROR: You've hit your usage limit. Visit https://chatgpt.com/codex/settings/usage to purchase more credits or try again at Sep 20th, 2026 3:53 AM.

Expected

Session start should surface the provider's usage-limit rejection as its own closed reason (for example codex_usage_limit with the reset time when the runtime reports one) instead of a deadline timeout, and oompa status should reflect the account's exhausted quota. The observed usage snapshot for the profile predates the exhaustion, so the local usage view did not warn either.

Environment

macOS 15 arm64, Bun 1.3.14, pinned Codex 0.153.2, daemon started from main 749d0e6.