Auto-approve Bash blocked by transient model unavailability (cannot determine safety) — Opus 4.8 1M, recurring across days

Environment: Claude Code, model claude-opus-4-8[1m] (Opus 4.8, 1M context), Windows 10 / PowerShell, auto-approval mode.

Symptom: Bash tool calls intermittently fail with:

"claude-opus-4-8[1m] is temporarily unavailable, so auto mode cannot determine the safety of Bash right now."

The command is rejected outright — not queued or retried by the harness.

Impact: When the safety classifier can't reach the model, all Bash is blocked (git, npm, gh, build/test) even for plainly safe, previously-approved commands. Read-only tools (Read/Grep/Glob) are unaffected, so work stalls mid-task on anything requiring a shell. Retrying eventually succeeds, but it's disruptive and non-deterministic.

Frequency: Recurring — multiple times on 2026-05-30 and again 2026-05-29 (two consecutive days). Notably, attempts to file this very report via gh were themselves blocked by the same error.

Expected: When the safety-classification model is transiently unavailable, the harness should retry/back off transparently, or fall back to a cached/last-known permission decision for known-safe commands — not hard-fail the tool call.

Workaround: Re-issue the command after a short wait; lean on read-only tools meanwhile.