One small addition to the warming endpoint: since /warm makes a real LLM call, it's worth excluding it from the request-count and latency dashboards (or tagging it), otherwise post-deploy warmups skew the p50/p95 you're using to tune min_instances. Also, Cloud Run's startup CPU boost pairs well with this: it shortens the 2–5s import/pool init for the cold starts that still happen after a scale-to-zero, without paying for an extra always-on instance.