Issue: charmbracelet/crush#1050

Display "Yolo mode enabled/disabled" via ReportInfo so the user gets
immediate visual feedback after pressing ctrl+y.

Assisted-by: Crush:claude-opus-4-6

💘 Generated with Crush

Assisted-by: Crush:qwen3.7-max

The auto-expand logic now fires only when the todo/queue panel is first
created, not on subsequent session updates. A `pillsAutoExpanded` guard
flag prevents re-triggering until the next session.

💘 Generated with Crush

Assisted-by: Crush:kimi-k2.6

The todo/queue panel now opens automatically when the terminal is tall
enough (≥40 rows) and there are active items, eliminating the need for
a manual ctrl+t toggle in typical desktop use.

💘 Generated with Crush

Assisted-by: Crush:kimi-k2.6

💘 Generated with Crush

Assisted-by: Crush:qwen3.7-max

Co-authored-by: Amolith <amolith@secluded.site>
Assisted-by: Crush:deepseek-v4-pro

This is the only region with access to all models.

Having a fixed region should avoid confusion as some users might have
`AWS_REGION` or `AWS_DEFAULT_REGION` set, but other regions won't really
work.

* Catwalk PR: https://github.com/charmbracelet/catwalk/pull/289
* Fantasy PR: https://github.com/charmbracelet/fantasy/pull/248
* Closes #2568
* Closes #2759

For some reason, I sometimes see a reasoning effort set on
`model.ModelCfg.ReasoningEffort` (like "high") when the model doesn't
supports it. This may being set by a previous select model and not
properly cleared.

We should check if the model supports reasoning effort levels before
setting it. Otherwise, we should set only `thinking` (if supported).

Otherwise, if contextWindow == 0, then it's a divide-by-zero error
and a wild number % is shown. Now it defaults to 0% in that case.

Signed-off-by: Evan Wies <evan@neomantra.net>

Needed to prevent race conditions, which may segfault.

Signed-off-by: Evan Wies <evan@neomantra.net>

Keep estimated usage state in memory across session fetch-modify-save updates so unrelated saves do not clear the UI marker, and align the marker color with context percentages.

Add a fallback token estimator for streamed steps that return zero usage so session context pressure remains accurate when providers omit final usage chunks.

Estimated usage updates prompt/completion counters but never contributes cost, while provider-reported usage continues to preserve normal cost accounting and OpenRouter overrides. Zero-usage updates now leave existing nonzero token counters intact.

* https://github.com/charmbracelet/fantasy/pull/245
* https://github.com/charmbracelet/fantasy/pull/246

By @ethanndickson