docs: refresh model ID examples and document shorthand format

Merged
KE
5mo ago
+4-4

What type of PR is this?

/kind docs

What this PR does / why we need it:

Two related docs problems were confusing new users picking a value for spec.model (issue #1143):

  1. Stale example model IDs (Sonnet 4 / Sonnet 4.5 from 2025) in docs/reference.md and skills/kelos/SKILL.md — bumped to claude-sonnet-4-6.
  2. Shorthand names like opus / sonnet are used throughout self-development/ YAML and the SKILL.md CLI quick reference, but never documented. The spec.model value is passed through to the agent container as KELOS_MODEL without validation, so any value the underlying CLI accepts works. The spec.model and spec.taskTemplate.model rows in docs/reference.md now state this explicitly, and the SKILL.md config example notes the shorthand alternative inline.

No code changes; CRDs and behavior are unchanged.

Which issue(s) this PR is related to:

Fixes #1143

Special notes for your reviewer:

Test fixtures under internal/ and test/integration/ still use the older IDs as opaque pass-through strings — they're not user-facing examples, so they're left alone to keep the diff minimal.

Does this PR introduce a user-facing change?

Documentation: refreshed stale model ID examples in `docs/reference.md` and `skills/kelos/SKILL.md`, and documented that `spec.model` / `spec.taskTemplate.model` are passed through to the agent container as `KELOS_MODEL` without validation, so agent-native shorthand names (e.g., `sonnet`, `opus` for Claude Code) are also valid.

Summary by cubic

Update docs to lead with agent-native shorthand model names (sonnet, opus) and keep claude-sonnet-4-6 as the versioned alternative. Clarifies that spec.model and spec.taskTemplate.model pass through to the agent container as KELOS_MODEL without validation, so either format works; fixes #1143.