Fable 5 forced onto usage credits on Max plan before July 20 cutover, despite reset allowance at 0% Fable usage

Summary

I'm on the Max (20×) plan (~£200/mo). Claude Code is routing Fable 5 usage to prepaid usage credits even though:

1. The documented cutover to usage-credits-only is July 20, 2026 — Fable is supposed to be included on paid plans through July 19.
2. My weekly plan allowance reset on ~July 15, and the per-model Fable usage meter on the website reads 0%.

So I have full, unused, included Fable allowance on a Max plan and Code is still gating/charging Fable against usage credits.

Expected

Through July 19, 2026, Fable 5 is included on paid plans (up to 50% of weekly limits). With a freshly reset allowance and 0% Fable usage, Fable requests should draw from my Max plan — not usage credits.

Actual

• Switching to Fable 5 in Claude Code shows "Draws from usage credits".
• I received a "Fable requires usage credits" block.
• Meanwhile the website's Fable plan meter shows 0% used after the weekly reset.

Credits are being demanded regardless of available Max-plan quota.

Related issues

This looks like the same class of bug as:

• #65514 — Pro plan blocked despite 17% usage
• #64398 — blocked, quota available, no workaround
• #65283 — stuck on "Usage credits required" with allowance left

Environment

• Claude Code: 2.1.209
• Model pin: Opus 4.8 (1M context); issue occurs when switching to Fable 5
• OS: macOS 26.5.2 (25F84)
• Plan: Max (20×)

Impact

Paying for Max (20×) but Fable 5 is not being honored as included on the plan — it's being forced onto usage credits before the stated July 20 cutover, despite a reset allowance at 0% Fable usage.

Request

1. Confirm whether this is the known usage-credits gating bug.
2. Ensure Fable 5 draws from the Max plan allowance per the July 19 policy.
3. Refund any usage credits consumed while included plan allowance was available.