v2.3.2

Fixes a broken app-bind state that the CLI couldn't recover from.

npm i -g codex-multi-auth

What was wrong

App-bind rewrites ~/.codex/config.toml to point Codex at the rotation proxy, and keeps state and backup files so it can undo that later. If those files went missing — cleanup, a partial unbind, a crash, a re-run of first-run setup — the config stayed pointed at the proxy while rotation status and rotation unbind-app both reported "not configured" and refused to do anything.

So the official Codex CLI and Desktop were routed to a dead proxy port, and there was no way to fix it from the CLI.

What's fixed

rotation unbind-app now self-heals. With no backup and no state but a config that's still bound, it strips the proxy block, restores your model_provider (falling back to openai if there's no backup to read), and tells you what it did.

rotation status also reports "bound but unmanaged" with the fix to run, instead of claiming nothing is configured.

If you hit this, just run:

codex-multi-auth rotation unbind-app

It now works even without a saved backup.

One edge case fixed along the way: a half-orphaned config — proxy block present but model_provider already pointing somewhere real — would get a second model_provider line spliced in during restore, producing TOML that Codex refuses to parse.

---

PR #614