Add persistent task workspace alpha

Start the first workspace milestone toward the task-oriented product without changing the existing one-shot vm_run/pyro run contract.

Add a disk-backed task registry in the manager, auto-started task workspaces rooted at /workspace, repeated non-cleaning exec, and persisted command journals exposed through task create/exec/status/logs/delete across the CLI, Python SDK, and MCP server.

Update the public contract, docs, examples, and version/catalog metadata for 2.1.0, and cover the new surface with manager, CLI, SDK, and MCP tests. Validation: UV_CACHE_DIR=.uv-cache make check and UV_CACHE_DIR=.uv-cache make dist-check.

docs/install.md

@@ -83,7 +83,7 @@ uvx --from pyro-mcp pyro env list
 Expected output:
 
 ```bash
-Catalog version: 2.0.0
+Catalog version: 2.1.0
 debian:12 [installed|not installed] Debian 12 environment with Git preinstalled for common agent workflows.
 debian:12-base [installed|not installed] Minimal Debian 12 environment for shell and core Unix tooling.
 debian:12-build [installed|not installed] Debian 12 environment with Git and common build tools preinstalled.
@@ -174,10 +174,26 @@ pyro run debian:12 -- git --version
 
 After the CLI path works, you can move on to:
 
+- persistent workspaces: `pyro task create debian:12`
 - MCP: `pyro mcp serve`
 - Python SDK: `from pyro_mcp import Pyro`
 - Demos: `pyro demo` or `pyro demo --network`
 
+## Persistent Task Workspace
+
+Use `pyro task ...` when you need repeated commands in one sandbox instead of one-shot `pyro run`.
+
+```bash
+pyro task create debian:12
+pyro task exec TASK_ID -- sh -lc 'printf "hello from task\n" > note.txt'
+pyro task exec TASK_ID -- cat note.txt
+pyro task logs TASK_ID
+pyro task delete TASK_ID
+```
+
+Task commands default to the persistent `/workspace` directory inside the guest. If you need the
+task identifier programmatically, use `--json` and read the `task_id` field.
+
 ## Contributor Clone
 
 ```bash