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.
This commit is contained in:
parent
6e16e74fd5
commit
58df176148
19 changed files with 1730 additions and 48 deletions
10
CHANGELOG.md
10
CHANGELOG.md
|
|
@ -2,6 +2,16 @@
|
|||
|
||||
All notable user-visible changes to `pyro-mcp` are documented here.
|
||||
|
||||
## 2.1.0
|
||||
|
||||
- Added the first persistent task workspace alpha across the CLI, Python SDK, and MCP server.
|
||||
- Shipped `task create`, `task exec`, `task status`, `task logs`, and `task delete` as an additive
|
||||
surface alongside the existing one-shot VM contract.
|
||||
- Made task workspaces persistent across separate CLI/SDK/MCP processes by storing task records on
|
||||
disk under the runtime base directory.
|
||||
- Added per-task command journaling so repeated workspace commands can be inspected through
|
||||
`pyro task logs` or the matching SDK/MCP methods.
|
||||
|
||||
## 2.0.1
|
||||
|
||||
- Fixed the default `pyro env pull` path so empty local profile directories no longer produce
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue