[macOS][26.1002.52244] Desktop won't load account/usage data — JWT has no chatgpt_account_id, everything returns 432

Finding: In an external report (https://github.com/openai/codex/issues/52112), Codex Desktop 26.1002.52244 on macOS 15.7.3 (Apple Silicon), with bundled app-server codex-cli 0.162.0-alpha.2, fails to load account and usage data after ChatGPT login. Workspace-routed endpoints (/settings/user, /wham/usage, /wham/statsig/bootstrap, /wham/onboarding/context) return 432 with the message "Workspace routing is unavailable". The account, usage and subscription entries are missing from the settings UI. Per the reporter, the CLI works on the same machine, account and network, and codex doctor reports healthy. Reported reproduction: sign out in the desktop app (auth.json is removed and login status shows not logged in), then sign back in with the same account. The same 432 errors return. Reporter's diagnosis (HYPOTHESIS, not maintainer-confirmed): after re-login, tokens.account_id in ~/.codex/auth.json is None, whereas it previously held an id. The decoded access token reportedly has no chatgpt_account_id claim under the OpenAI auth namespace. Running the app-server directly and calling account/read reportedly returns workspaceRouting null with planType unknown, whereas it previously returned a full routing object. The reporter says the app compares the workspace routing account id to the JWT-derived account id and throws a routing-mismatch error when they differ. Since the JWT value would be undefined, the comparison cannot match, and the caller maps the failure to the 432 error. The reporter also notes that a legacy discovery branch applies only when workspaceRouting is undefined, not null, and only within a limited app-server version range, so it would not run. The reporter suspects the server stopped issuing the claim for this account. This is the reporter's reading of app.asar and of auth data; none of it was verified by maintainers or KFA. Ruled out by the reporter: CODEX_CLI_PATH being set, proxy/VPN, expired token, account-id mismatch, outdated app version, configRequirements/read returning requirements, stale downloaded app-server-daemon releases, and simple app restarts. Status: the issue is closed, but the visible timeline contains only an automated duplicate-suggestion comment referencing #51213. No maintainer-confirmed cause, workaround, fix commit or released fix appears in the supplied sources. Closure alone does not show a fix. This record is an external report; KFA did not reproduce it. No safe remediation is supported by the sources, so no solution is offered.