v2.1.10

Runtime Rotation

Bugfixes

• Runtime pool exhaustion on no-account now resets volatile runtime trackers, reloads accounts from disk once, and retries selection even when stale in-memory circuit breakers are open. This prevents a long-lived proxy from staying wedged after disk state has recovered.
• Runtime proxy shutdown now flushes only the active account manager after a stale-state reload, avoiding stale-vs-fresh manager save races during close.
• Pinned-account hard-fail behavior remains preserved: unavailable pinned accounts still return the explicit pinned-account error instead of silently rotating.

Diagnostics

Improvements

• Pool-exhausted 503 responses include per-account runtime skip reasons and a targeted recovery hint.
• report and doctor now include persisted quota-cache inputs when computing forecast readiness, so quota-exhausted cache state cannot be reported as ready by those diagnostics.
• doctor keeps the forecast-runtime-alignment warning for disk/runtime divergence.
• rotation reset-runtime --json no longer clears runtime diagnostics if the app bind restart fails, preserving evidence needed for follow-up diagnosis.

Release Hygiene

Improvements

• The npm package now includes only runtime/install scripts instead of internal benchmark, audit, and maintenance scripts.
• Production dependency patch lines were refreshed (undici and zod) while keeping the published package on the current Node 18-compatible runtime line.
• Release index labels were corrected so older release-note rows are not shown as current stable.

Validation

• Published to npm as codex-multi-auth@2.1.10.
• npm run typecheck, npm run lint, npm test, npm run build, npm run pack:check, and production npm audit passed on the release checkout.
• Fresh npm install smoke verified codex-multi-auth@2.1.10 command/version/help/doctor/forecast/report/reset-runtime paths.