[Bug] Auto mode circuit-breaker permanently disabled after declining opt-in dialog

Bug Description
Title: tengu_auto_mode_config returns "disabled" for one machine, "enabled" on
another — same Anthropic account

Body:

Summary
-------
On one of my two machines, auto mode is permanently disabled by the
circuit-breaker check. On the other machine — same Anthropic account
— auto mode works normally.

Behavior
--------
Affected machine (Darwin 25.4.0, arm64, claude 2.1.144):

• claude auto-mode config returns the full ruleset (so the feature

is wired up), but auto mode is never available in sessions.

• ~/.claude.json contains: "tengu_auto_mode_config": { "enabled": "disabled" }
• The value is restored from the server on every restart — local

edits to ~/.claude.json are overwritten.

• --permission-mode auto, permissions.defaultMode: "auto" in

settings.json, and skipAutoPermissionPrompt: true in settings.json
all have no effect — circuit breaker trips before any of those are
consulted.

• Decompiled gate (isAutoModeAvailable) confirms the circuit-breaker

check runs first and returns false.

Working machine (same Anthropic account):

• settings.json contains skipAutoPermissionPrompt: true (set when I

clicked "Yes, enable auto mode" in the opt-in dialog).

• Auto mode is available and active.

History
-------
On the affected machine I originally clicked "decline, don't ask again"
on the opt-in dialog. I'd like that decision cleared so I can re-opt-in,
or to have my account's auto-mode entitlement enabled the same way it
is on the other machine.

Ask
---
Please clear whatever per-machine state is causing
tengu_auto_mode_config.enabled === "disabled" on this machine, or
explain whether this is a plan-tier restriction (the user-facing
message in the binary is "auto mode is unavailable for your plan").

Environment Info

• Platform: darwin
• Terminal: iTerm.app
• Version: 2.1.144
• Feedback ID: e5bfe595-88e1-4ce3-a3ad-137e074f6b18