Resuming a session can silently change the model (--resume should pin or warn)

Context: solo owner running Claude Code across 4 projects with autonomous ticket-runner sessions and per-model cost/quality routing (~1000 session transcripts / 17 days). macOS, CLI + VSCode extension.

A runner session started on Opus was resumed later and continued on a different (more expensive) default model, with no warning. For autonomous pipelines with per-model cost/quality routing this is a silent budget/quality drift.

Ask: --resume should pin the original session model by default, or at least warn on mismatch.

Happy to share sanitized transcript excerpts.