Add seeded task workspace creation

Current persistent tasks started with an empty workspace, which blocked the first useful host-to-task workflow in the task roadmap. This change lets task creation start from a host directory or tar archive without changing the one-shot VM surfaces.

Expose source_path on task create across the CLI, SDK, and MCP, add safe archive upload and extraction support for guest and host-compat backends, persist workspace_seed metadata, and patch the per-task rootfs with the bundled guest agent before boot so seeded guest tasks work without republishing environments. Also switch post--- command reconstruction to shlex.join() so documented sh -lc task examples preserve argument boundaries.

Validation:
- uv lock
- UV_CACHE_DIR=.uv-cache uv run pytest --no-cov tests/test_vm_guest.py tests/test_vm_manager.py tests/test_cli.py tests/test_api.py tests/test_server.py tests/test_public_contract.py
- UV_CACHE_DIR=.uv-cache make check
- UV_CACHE_DIR=.uv-cache make dist-check
- real guest-backed smoke: task create --source-path, task exec -- cat note.txt, task delete

CHANGELOG.md

@@ -2,6 +2,15 @@
 
 All notable user-visible changes to `pyro-mcp` are documented here.
 
+## 2.2.0
+
+- Added seeded task creation across the CLI, Python SDK, and MCP server with an optional
+  `source_path` for host directories and `.tar` / `.tar.gz` / `.tgz` archives.
+- Seeded task workspaces now persist `workspace_seed` metadata so later status calls report how
+  `/workspace` was initialized.
+- Reused the task workspace model from `2.1.0` while adding the first explicit host-to-task
+  content import path for repeated command workflows.
+
 ## 2.1.0
 
 - Added the first persistent task workspace alpha across the CLI, Python SDK, and MCP server.