Add daily-loop prepare and readiness checks

Make the local chat-host loop explicit and cheap so users can warm the machine once instead of rediscovering environment and guest setup on every session.

Add cache-backed daily-loop manifests plus the new `pyro prepare` flow, extend `pyro doctor --environment` with warm/cold/stale readiness reporting, and add `make smoke-daily-loop` to prove the warmed repro-fix reset path end to end.

Also fix `python -m pyro_mcp.cli` to invoke `main()` so the new smoke and `dist-check` actually exercise the CLI module, and update the docs/roadmap to present `doctor -> prepare -> connect host -> reset` as the recommended daily path.

Validation: `uv lock`, `UV_OFFLINE=1 UV_CACHE_DIR=.uv-cache make check`, `UV_OFFLINE=1 UV_CACHE_DIR=.uv-cache make dist-check`, and `UV_OFFLINE=1 UV_CACHE_DIR=.uv-cache make smoke-daily-loop`.

docs/roadmap/llm-chat-ergonomics/4.5.0-faster-daily-loops.md

@@ -1,6 +1,6 @@
 # `4.5.0` Faster Daily Loops
 
-Status: Planned
+Status: Done
 
 ## Goal
 
@@ -9,11 +9,11 @@ for normal work, not only for special high-isolation tasks.
 
 ## Public API Changes
 
-The product should add an explicit fast-path for repeated local use, such as:
+The product now adds an explicit fast-path for repeated local use:
 
-- a prewarm or prepare path for the recommended environment and runtime
-- a clearer fast reset or retry path for repeated repro-fix loops
-- visible diagnostics for cache, prewarm, or ready-state health
+- `pyro prepare [ENVIRONMENT] [--network] [--force] [--json]`
+- `pyro doctor --environment ENVIRONMENT` daily-loop readiness output
+- `make smoke-daily-loop` to prove the warmed machine plus reset/retry story
 
 The exact command names can still move, but the user-visible story needs to be:
 
@@ -50,8 +50,8 @@ The exact command names can still move, but the user-visible story needs to be:
 
 ## Required Repo Updates
 
-- docs updated to show the recommended daily-use fast path
-- diagnostics and help text updated so the user can tell whether the machine is
-  already warm and ready
-- at least one repeat-loop smoke or benchmark-style verification scenario
-  added to prevent regressions in the daily workflow
+- docs now show the recommended daily-use fast path
+- diagnostics and help text now show whether the machine is already warm and
+  ready
+- the repo now includes `make smoke-daily-loop` as a repeat-loop verification
+  scenario for the daily workflow