Agent Teams: model parameter does not support version pinning

Problem

The Agent tool's model parameter only accepts three values: "sonnet", "opus", "haiku". These resolve to the latest version of each model family, with no way to specify a particular version (e.g., claude-opus-4-6 vs claude-opus-4-7).

This means users cannot pin teammates to a specific model version through the Agent tool, even when they have a configured default via /config.

Current Behavior

model: "opus"         → resolves to latest (currently claude-opus-4-7)
model: "claude-opus-4-6"  → InputValidationError: Invalid option
model: "claude-opus-4.6"  → InputValidationError: Invalid option
(omitted)             → inherits user's /config default (workaround)

The enum validation rejects any value other than the three family shorthand strings.

Expected Behavior

The model parameter should accept full model IDs (e.g., claude-opus-4-6, claude-sonnet-4-6) in addition to the family shorthand, allowing users and orchestration skills to pin teammates to specific model versions.

Workaround

Omitting the model parameter entirely causes the teammate to inherit the user's configured default model (set via /config). This works but only supports a single default — not per-teammate version control.

Impact

Orchestration workflows that require different model versions for different teammates (e.g., a PM on Sonnet 4.6 and an Auditor on Opus 4.6) cannot express this through the Agent tool. The only control point is the global /config default, which applies uniformly to all teammates.

Environment

• Claude Code version: 2.1.114
• Platform: Linux
• Agent Teams: CLAUDE_CODE_EXPERIMENTAL_AGENT_TEAMS=1