v0.24.2

Remove the claude-fable-5[1m] model option, which could never differ from plain Fable 5

Context

Fable 5 runs at 1M context unconditionally. The client's model registry marks it
native_1m and, unlike Opus, withholds the supports_1m_suffix flag, so a [1m]
suffix on it was stripped before the request was sent -- verified end to end:
selecting claude-fable-5[1m] reported model claude-fable-5 with a 1,000,000
token window, identical to the plain id.

The option therefore offered a choice that did not exist, and when an unrelated
usage-credits dialog appeared it read as though 1M context were the thing being
refused. It was not; direct API probes at 396k input tokens returned 200 with
and without the 1M beta header.

Removing it from the defaults does not reach an options.json that already lists
it, so a migration cleans values, pinned, and metadata. The entry stays in
HISTORICAL_DEFAULTS, which records what ever shipped rather than what currently
does -- migration 3 reads it to tell a former default apart from a user-added
value.

Fixes

• Removed the claude-fable-5[1m] model option. Fable 5 runs at 1M context unconditionally, so the suffix was discarded by Claude Code and the option could never differ from plain claude-fable-5 — while making an entitlement wall look like the reason. Existing options.json files are cleaned automatically.