Add workspace review summaries

Add workspace summary across the CLI, SDK, and MCP, and include it in the workspace-core profile so chat hosts can review one concise view of the current session.

Persist lightweight review events for syncs, file edits, patch applies, exports, service lifecycle, and snapshot activity, then synthesize them with command history, current services, snapshot state, and current diff data since the last reset.

Update the walkthroughs, use-case docs, public contract, changelog, and roadmap for 4.3.0, and make dist-check invoke the CLI module directly so local package reinstall quirks do not break the packaging gate.

Validation: uv lock; ./.venv/bin/pytest --no-cov tests/test_vm_manager.py tests/test_cli.py tests/test_api.py tests/test_server.py tests/test_public_contract.py tests/test_workspace_use_case_smokes.py; UV_OFFLINE=1 UV_CACHE_DIR=.uv-cache make check; UV_OFFLINE=1 UV_CACHE_DIR=.uv-cache make dist-check; real guest-backed workspace create -> patch apply -> workspace summary --json -> delete smoke.

docs/first-run.md

@@ -27,7 +27,7 @@ Networking: tun=yes ip_forward=yes
 
 ```bash
 $ uvx --from pyro-mcp pyro env list
-Catalog version: 4.2.0
+Catalog version: 4.3.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.
@@ -155,6 +155,7 @@ $ uvx --from pyro-mcp pyro workspace sync push "$WORKSPACE_ID" ./changes
 $ uvx --from pyro-mcp pyro workspace file read "$WORKSPACE_ID" note.txt --content-only
 $ uvx --from pyro-mcp pyro workspace patch apply "$WORKSPACE_ID" --patch-file fix.patch
 $ uvx --from pyro-mcp pyro workspace exec "$WORKSPACE_ID" -- cat note.txt
+$ uvx --from pyro-mcp pyro workspace summary "$WORKSPACE_ID"
 $ uvx --from pyro-mcp pyro workspace snapshot create "$WORKSPACE_ID" checkpoint
 $ uvx --from pyro-mcp pyro workspace reset "$WORKSPACE_ID" --snapshot checkpoint
 $ uvx --from pyro-mcp pyro workspace export "$WORKSPACE_ID" note.txt --output ./note.txt

docs/install.md

@@ -93,7 +93,7 @@ uvx --from pyro-mcp pyro env list
 Expected output:
 
 ```bash
-Catalog version: 4.2.0
+Catalog version: 4.3.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.
@@ -239,6 +239,7 @@ pyro workspace sync push "$WORKSPACE_ID" ./changes
 pyro workspace file read "$WORKSPACE_ID" note.txt --content-only
 pyro workspace patch apply "$WORKSPACE_ID" --patch-file fix.patch
 pyro workspace exec "$WORKSPACE_ID" -- cat note.txt
+pyro workspace summary "$WORKSPACE_ID"
 pyro workspace snapshot create "$WORKSPACE_ID" checkpoint
 pyro workspace reset "$WORKSPACE_ID" --snapshot checkpoint
 pyro workspace export "$WORKSPACE_ID" note.txt --output ./note.txt

docs/public-contract.md

@@ -117,6 +117,7 @@ setup and repair path for supported hosts.
 - `workspace_sync_push`
 - `workspace_exec`
 - `workspace_logs`
+- `workspace_summary`
 - `workspace_file_list`
 - `workspace_file_read`
 - `workspace_file_write`
@@ -133,6 +134,7 @@ That is enough for the normal persistent editing loop:
 - sync or seed repo content
 - inspect and edit files without shell quoting
 - run commands repeatedly in one sandbox
+- review the current session in one concise summary
 - diff and export results
 - reset and retry
 - delete the workspace when the task is done

docs/roadmap/llm-chat-ergonomics.md

@@ -6,7 +6,7 @@ goal:
 make the core agent-workspace use cases feel trivial from a chat-driven LLM
 interface.
 
-Current baseline is `4.2.0`:
+Current baseline is `4.3.0`:
 
 - `pyro mcp serve` is now the default product entrypoint
 - `workspace-core` is now the default MCP profile
@@ -81,7 +81,7 @@ capability gaps:
 11. [`4.0.0` Workspace-Core Default Profile](llm-chat-ergonomics/4.0.0-workspace-core-default-profile.md) - Done
 12. [`4.1.0` Project-Aware Chat Startup](llm-chat-ergonomics/4.1.0-project-aware-chat-startup.md) - Done
 13. [`4.2.0` Host Bootstrap And Repair](llm-chat-ergonomics/4.2.0-host-bootstrap-and-repair.md) - Done
-14. [`4.3.0` Reviewable Agent Output](llm-chat-ergonomics/4.3.0-reviewable-agent-output.md) - Planned
+14. [`4.3.0` Reviewable Agent Output](llm-chat-ergonomics/4.3.0-reviewable-agent-output.md) - Done
 15. [`4.4.0` Opinionated Use-Case Modes](llm-chat-ergonomics/4.4.0-opinionated-use-case-modes.md) - Planned
 16. [`4.5.0` Faster Daily Loops](llm-chat-ergonomics/4.5.0-faster-daily-loops.md) - Planned
 
@@ -120,10 +120,12 @@ Completed so far:
 - `4.2.0` adds first-class host bootstrap and repair helpers so Claude Code,
   Codex, and OpenCode users can connect or repair the supported chat-host path
   without manually composing raw MCP commands or config edits.
+- `4.3.0` adds a concise workspace review surface so users can inspect what the
+  agent changed and ran since the last reset without reconstructing the
+  session from several lower-level views by hand.
 
 Planned next:
 
-- [`4.3.0` Reviewable Agent Output](llm-chat-ergonomics/4.3.0-reviewable-agent-output.md)
 - [`4.4.0` Opinionated Use-Case Modes](llm-chat-ergonomics/4.4.0-opinionated-use-case-modes.md)
 - [`4.5.0` Faster Daily Loops](llm-chat-ergonomics/4.5.0-faster-daily-loops.md)
 

docs/roadmap/llm-chat-ergonomics/4.3.0-reviewable-agent-output.md

@@ -1,6 +1,6 @@
 # `4.3.0` Reviewable Agent Output
 
-Status: Planned
+Status: Done
 
 ## Goal
 

docs/use-cases/README.md

@@ -30,3 +30,9 @@ That runner generates its own host fixtures, creates real guest-backed workspace
 verifies the intended flow, exports one concrete result when relevant, and cleans
 up on both success and failure. Treat `make smoke-use-cases` as the trustworthy
 guest-backed verification path for the advertised workspace workflows.
+
+For a concise review before exporting, resetting, or handing work off, use:
+
+```bash
+pyro workspace summary WORKSPACE_ID
+```

docs/use-cases/review-eval-workflows.md

@@ -16,9 +16,10 @@ Chat-host recipe:
 1. Create a named snapshot before the review starts.
 2. Open a readable PTY shell and inspect the checklist interactively.
 3. Run the review or evaluation script in the same workspace.
-4. Export the final report.
-5. Reset back to the snapshot if the review branch goes sideways.
-6. Delete the workspace when the evaluation is done.
+4. Capture `workspace summary` to review what changed and what to export.
+5. Export the final report.
+6. Reset back to the snapshot if the review branch goes sideways.
+7. Delete the workspace when the evaluation is done.
 
 This is the stable shell-facing story: readable PTY output for chat loops,
 checkpointed evaluation, explicit export, and reset when a review branch goes