Model "auto" always runs with reasoning effort disabled (reasoningEffort: null), and rejects any attempt to configure one

Describe the bug

When the model is set to auto, every request is sent without any reasoning effort:

1. Selecting auto sets the session's reasoningEffort to null (visible in the session's events.jsonl as session.model_change → "reasoningEffort": null).
2. The auto router (auto_v2) picks a model per prompt (session.auto_mode_resolved) but never assigns a reasoning effort to it — the request goes out with none, confirmed by reasoning_effort = NULL and reasoning_tokens = 0 in ~/.copilot/session-store.db (assistant_usage_events).
3. Trying to set one explicitly is rejected: copilot --model auto --effort xhigh fails with Error: Model "auto" does not support reasoning effort configuration (requested: "xhigh").

So with auto there is no way at all to run with reasoning enabled. The degradation is silent — no error, no indication in the UI — and the impact on agentic work is severe: on a large agentic prompt (spec generation with mandatory file reads), the routed model (gpt-5.3-codex) ends its turn without making a single tool call, replying that it "could not perform the investigation". The exact same prompt, on the exact same routed model, works flawlessly when a reasoning effort is set (see "Same model, only effort differs" below).

Affected version

GitHub Copilot CLI 1.0.80.

Steps to reproduce the behavior

# 1) auto → no reasoning (silent)
copilot --model auto --allow-all-tools -p "Reply with exactly: ok"

# 2) control: explicit model → reasoning works
copilot --model gpt-5.4 --allow-all-tools -p "Reply with exactly: ok"

# 3) auto + explicit effort → hard error
copilot --model auto --effort xhigh --allow-all-tools -p "Reply with exactly: ok"

Then inspect what was actually sent (replace the session ids printed in the Resume line):

sqlite3 -readonly ~/.copilot/session-store.db \
  "SELECT session_id, model, reasoning_effort, reasoning_tokens
   FROM assistant_usage_events ORDER BY id DESC LIMIT 5;"

Observed results:

The same happens in interactive mode: switching to auto logs
session.model_change ... "previousReasoningEffort": "xhigh", "reasoningEffort": null
in ~/.copilot/session-state/<session-id>/events.jsonl, and every subsequent session.auto_mode_resolved runs the chosen model with no effort.

Same model, only effort differs — night and day

Real-world case that led us here (a large spec-generation prompt, ~19.6k input tokens, requiring file reads and skill loading):

• auto → routed to gpt-5.3-codex, reasoning_effort = NULL: the model ends the turn after 158 output tokens, 0 reasoning tokens, 0 tool calls, claiming it could not perform the investigation. Reproduced consistently across several sessions.
• Same prompt, same gpt-5.3-codex, with reasoning_effort = xhigh: normal agentic behavior — tool calls, thousands of reasoning tokens, task completed.

The only variable is the reasoning effort. auto mode currently guarantees the degraded path.

Expected behavior

auto should never silently disable reasoning. Either:

• the auto router assigns an appropriate reasoning effort for the routed model on each request (clamping to what that model supports), and/or
• a user-provided effort (--effort, settings effortLevel, session config) is honored under auto and clamped per routed model — instead of being cleared on switch and rejected on the CLI flag.

Additional context

• This looks like an overcorrection of #2870: there, switching to auto kept the previous effort and caused loud 400 errors on models that don't support it; the fix apparently clears the effort entirely, trading a loud error for a silent, permanent degradation. #4459 and #4445 show the invalid-combination side of this is still not fully solved either — both symptoms share the same root: the auto router does not manage effort per routed model.
• The ACP server mode (copilot --acp) is affected identically, with no workaround at all: session/set_config_option with model=auto clears the effort and removes the reasoning-effort config option from the session, so ACP clients cannot restore it.

copilot --model auto と --effort のエントリーポイントから始め、events.jsonl と session-store.db 内の assistant_usage_events を比較しながら、auto_v2、session.model_change、session.auto_mode_resolved を追跡します。完了条件は、自動モードが推論の effort を暗黙にクリアしなくなり、設定された effort を安全に受け付け、モデルごとに無効なリクエストを送ることなくエージェント動作を維持することです。