Orchestration mode moved [llm] under [agent.llm], so configs still using the old top-level [llm] table fail with a hard error on upgrade. There's no graceful fallback.
Outcome: Old configs with a top-level [llm] table keep working at runtime. A deprecation warning tells users to update their TOML. If both [llm] and [agent.llm] are present, config loading fails with a clear error — we don't guess which one wins.
Acceptance criteria:
- Top-level
[llm] with [agent] present loads successfully, LLM settings applied as if under [agent.llm]
- A deprecation warning is logged at runtime
- Both
[llm] and [agent.llm] present produces a validation error
[llm] without any [agent] section produces a validation error- Shipped example configs updated to the new
[agent.llm] shape
Orchestration mode moved
[llm]under[agent.llm], so configs still using the old top-level[llm]table fail with a hard error on upgrade. There's no graceful fallback.Outcome: Old configs with a top-level
[llm]table keep working at runtime. A deprecation warning tells users to update their TOML. If both[llm]and[agent.llm]are present, config loading fails with a clear error — we don't guess which one wins.Acceptance criteria:
[llm]with[agent]present loads successfully, LLM settings applied as if under[agent.llm][llm]and[agent.llm]present produces a validation error[llm]without any[agent]section produces a validation error[agent.llm]shape