Problem
When advisorModel: "fable" is configured in settings but Fable is unavailable (model outage, rate limit, etc.), the wizard provides no guidance on what to use as a fallback for cross-model review.
Current behavior
User has to figure out on their own to switch to Codex (GPT 5.5 xhigh) or another reviewer. No error handling, no docs, no wizard guidance.
Expected behavior
The wizard should:
- Document the fallback procedure in the wizard doc (e.g., "if advisor is unavailable, use
codex exec with GPT 5.5 xhigh for cross-model review")
- Optionally: detect advisor unavailability at session start and surface the fallback recommendation
- The
/update skill could check advisor health and suggest alternatives
Context
Discovered June 19, 2026 when Fable advisor was unavailable during an anticheat session. User had to manually recall the Codex fallback procedure. This should be documented so it's not a tribal-knowledge gap.
Acceptance criteria
Problem
When
advisorModel: "fable"is configured in settings but Fable is unavailable (model outage, rate limit, etc.), the wizard provides no guidance on what to use as a fallback for cross-model review.Current behavior
User has to figure out on their own to switch to Codex (GPT 5.5 xhigh) or another reviewer. No error handling, no docs, no wizard guidance.
Expected behavior
The wizard should:
codex execwith GPT 5.5 xhigh for cross-model review")/updateskill could check advisor health and suggest alternativesContext
Discovered June 19, 2026 when Fable advisor was unavailable during an anticheat session. User had to manually recall the Codex fallback procedure. This should be documented so it's not a tribal-knowledge gap.
Acceptance criteria