Confusing model labels in /model picker: 'Opus 4.6' entry says 'select Opus for Opus 4.1'

Description

<img width="572" height="134" alt="Image" src="https://github.com/user-attachments/assets/cb6b5e42-1b0e-463f-a652-011f8504282a" />

The /model picker has confusing labels for Opus models. ~~There are two entries that both resolve to the same model ID (us.anthropic.claude-opus-4-6-v1):~~

• "Opus" — labeled "Opus 4.6 · Most capable for complex work"
• "Opus 4.6" — labeled "Newer version available · select Opus for Opus 4.1"

~~Both set the model to us.anthropic.claude-opus-4-6-v1, so they're identical.~~

"Opus 4.6" set the model to us.anthropic.claude-opus-4-6-v1, while "Opus" set the model to global.anthropic.claude-opus-4-6-v1 and removed the entry for "Opus 4.6".

What's confusing

1. "Opus 4.6" says "newer version available" — but it is Opus 4.6, so what's newer?
2. "select Opus for Opus 4.1" — this reads like selecting "Opus" gives you the older 4.1, which is the opposite of the intended meaning.
3. Two entries, same model — having both "Opus" and "Opus 4.6" resolve to the same model ID is redundant and adds to the confusion.

Expected behavior

• If "Opus" and "Opus 4.6" are the same model, only one entry should appear.
• If the "Opus 4.6" entry is a legacy/deprecated alias, the deprecation message should clearly say something like: "This entry is deprecated. Use Opus instead (also Opus 4.6)."
• The phrase "select Opus for Opus 4.1" should not appear, as it implies the wrong version mapping.

Environment

• Claude Code CLI
• macOS