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/public-contract.md

@@ -30,11 +30,11 @@ documents the chat-host path the project is actively shaping.
 The intended user journey is:
 
 1. `pyro doctor`
-2. `pyro env list`
-3. `pyro env pull debian:12`
-4. `pyro run debian:12 -- git --version`
-5. `pyro mcp serve`
-6. connect Claude Code, Codex, or OpenCode
+2. `pyro prepare debian:12`
+3. `pyro run debian:12 -- git --version`
+4. `pyro mcp serve`
+5. connect Claude Code, Codex, or OpenCode
+6. use `workspace reset` as the normal retry step
 7. run one of the documented recipe-backed workflows
 8. validate the whole story with `make smoke-use-cases`
 
@@ -44,6 +44,7 @@ These terminal commands are the documented companion path for the chat-host
 product:
 
 - `pyro doctor`
+- `pyro prepare`
 - `pyro env list`
 - `pyro env pull`
 - `pyro run`
@@ -55,10 +56,12 @@ What to expect from that path:
 - `pyro run` fails if guest boot or guest exec is unavailable unless
   `--allow-host-compat` is set
 - `pyro run`, `pyro env list`, `pyro env pull`, `pyro env inspect`,
-  `pyro env prune`, and `pyro doctor` are human-readable by default and return
-  structured JSON with `--json`
+  `pyro env prune`, `pyro doctor`, and `pyro prepare` are human-readable by
+  default and return structured JSON with `--json`
 - the first official environment pull downloads from public Docker Hub into the
   local environment cache
+- `pyro prepare debian:12` proves the warmed daily loop with one throwaway
+  workspace create, exec, reset, and delete cycle
 - `pyro demo` proves the one-shot create/start/exec/delete VM lifecycle end to
   end