docs/website: align model + temperature examples with the gpt-5.4 / temperature=1.0 standard

[ango10]

Summary

PR #254 upgraded the examples/ eval configs to the gpt-5.4 family with temperature: 1.0 (gpt-5 models only support temperature=1). However, several other user-facing surfaces still show the old azure/gpt-4o-mini, and at least one still teaches temperature: 0.0 — the exact gpt-5 footgun that PR fixed. Since these are copy-paste sources, users land on the outdated pattern and can hit litellm.UnsupportedParamsError at runtime.

This is a follow-up to keep things consistent end-to-end. No need to expand #254 — that PR is intentionally scoped to examples/.

Motivation

• Docs/website are the first place new users copy config from. Showing gpt-4o-mini + temperature: 0.0 actively teaches a pattern that breaks on the gpt-5 family.
• Inconsistency between examples/ (now gpt-5.4) and docs (still gpt-4o) is confusing.

Affected surfaces

Docs — model examples (azure/gpt-4o-mini → azure/gpt-5.4 / azure/gpt-5.4-mini):

• docs/config/overview.md (L42, L49, L58)
• docs/config/schema.md (multiple: L115, L160, L165, L214, L227, L236 simulator:, L239, L272, L396, L423, L433, L457, L482, L504, L524)
• docs/targets/callable.md (L100, L123 — litellm.completion(model="azure/gpt-4o-mini"))
• docs/targets/model-and-tools.md (L20, L27 simulator:, L41, L57)

Docs — temperature: 0.0 → 1.0 (the gpt-5 footgun):

• docs/targets/model-and-tools.md (L21 and L58)

CLI docs:

• docs/cli/commands.md (L43) — documents --model default as azure/gpt-4o-mini.

Website:

• website/app/CodeSnippets.tsx (L45) — landing-page snippet shows name: azure/gpt-4o-mini.

Minor / informational (likely no change needed):

• The viewer "new run" wizard uses openai/gpt-4o-mini only as placeholder text, not a functional default.

Proposed change

Apply the same mapping used in #254:

• Judge / systematize examples → azure/gpt-5.4
• All other pipeline + target examples → azure/gpt-5.4-mini
• Every temperature in these snippets → 1.0

Note: the callable-target docs (callable.md) describe agent-owned code where the model lives in user code and may set non-1 temperatures — mirror the #254 decision and either leave those on gpt-4o-mini or annotate them, rather than implying gpt-5 with a hardcoded low temperature. Worth a quick decision during the fix.

If the CLI --model default itself should move to gpt-5.4, that's a code change (not just docs) and may warrant its own discussion — flagging separately.

Acceptance criteria

• No gpt-4o / gpt-4o-mini left in docs/config/*, docs/targets/model-and-tools.md, website/app/CodeSnippets.tsx (except intentional callable-agent examples).
• No temperature: 0.0 (or other non-1 values) in gpt-5 example snippets.
• docs/cli/commands.md reflects the agreed --model default.
• Callable-target docs decision documented.

Out of scope

• The examples/ configs (already handled in fix(examples): upgrade eval configs to gpt-5.4 family with temperature=1.0 #254).
• Callable agent internal models in code (agent.py / travel_*.py) — these hardcode non-1 temperatures and are overridable via ASSERT_TARGET_MODEL; tracked separately if desired.