v6.11.3

Three bug fixes, all affecting authentication reliability.

Fixed

Login could add an account that was already disabled (#213). A successful opencode auth login could annotate the new account Re-auth required for missing OAuth scope(s): openid, profile, email, offline_access. — all four required scopes at once, which is what absent scope metadata looks like rather than a denied grant. Required-scope enforcement now fires only when the granted scope is genuinely known; an explicit partial grant still disables exactly as before.

Accounts stranded by 6.11.2 recover automatically. No re-login is needed — the repair is applied on first launch and flushed to disk, so the TUI and CLI stop reporting stale state too. Re-login alone could not fix it previously, because the disabled state was persisted. An account you disabled by hand stays disabled.

A record could carry two contradictory re-auth notes, the stale one listed first, telling you to re-authenticate for scopes that were not actually missing (#215).

One transient storage read failure disabled the plugin until OpenCode was restarted (#216). A rejected account load was cached and re-awaited by every later request, so the failure outlived its own cause — a momentary Windows file lock or a partially-written save was enough.

Upgrading

No action required. Disabled accounts are repaired on first launch.

Thanks to @Grelo4ka for reporting #213.

Full changelog: v6.11.2...v6.11.3