vsh-python 0.4.0__tar.gz → 0.5.0__tar.gz

{vsh_python-0.4.0 → vsh_python-0.5.0}/Cargo.lock

@@ -1686,7 +1686,7 @@ checksum = "b6c140620e7ffbb22c2dee59cafe6084a59b5ffc27a8859a5f0d494b5d52b6be"
 
 [[package]]
 name = "vbash"
-version = "0.4.0"
+version = "0.5.0"
 dependencies = [
  "vsh",
 ]
@@ -1699,14 +1699,14 @@ checksum = "0b928f33d975fc6ad9f86c8f283853ad26bdd5b10b7f1542aa2fa15e2289105a"
 
 [[package]]
 name = "vsh"
-version = "0.4.0"
+version = "0.5.0"
 dependencies = [
  "vsh-runtime",
 ]
 
 [[package]]
 name = "vsh-commit"
-version = "0.4.0"
+version = "0.5.0"
 dependencies = [
  "blake3",
  "cap-fs-ext",
@@ -1719,7 +1719,7 @@ dependencies = [
 
 [[package]]
 name = "vsh-monty"
-version = "0.4.0"
+version = "0.5.0"
 dependencies = [
  "get-size2",
  "monty",
@@ -1733,7 +1733,7 @@ dependencies = [
 
 [[package]]
 name = "vsh-monty-worker"
-version = "0.4.0"
+version = "0.5.0"
 dependencies = [
  "monty",
  "monty-alloc",
@@ -1748,7 +1748,7 @@ dependencies = [
 
 [[package]]
 name = "vsh-policy"
-version = "0.4.0"
+version = "0.5.0"
 dependencies = [
  "vsh-store",
  "vsh-types",
@@ -1757,7 +1757,7 @@ dependencies = [
 
 [[package]]
 name = "vsh-python"
-version = "0.4.0"
+version = "0.5.0"
 dependencies = [
  "monty-proto",
  "pyo3",
@@ -1767,7 +1767,7 @@ dependencies = [
 
 [[package]]
 name = "vsh-runtime"
-version = "0.4.0"
+version = "0.5.0"
 dependencies = [
  "postcard",
  "vsh-commit",
@@ -1780,7 +1780,7 @@ dependencies = [
 
 [[package]]
 name = "vsh-store"
-version = "0.4.0"
+version = "0.5.0"
 dependencies = [
  "blake3",
  "cap-fs-ext",
@@ -1790,14 +1790,14 @@ dependencies = [
 
 [[package]]
 name = "vsh-types"
-version = "0.4.0"
+version = "0.5.0"
 dependencies = [
  "blake3",
 ]
 
 [[package]]
 name = "vsh-vfs"
-version = "0.4.0"
+version = "0.5.0"
 dependencies = [
  "vsh-store",
  "vsh-types",

{vsh_python-0.4.0 → vsh_python-0.5.0}/Cargo.toml

@@ -3,7 +3,7 @@ resolver = "3"
 members = ["crates/vsh-types", "crates/vsh-store", "crates/vsh-vfs", "crates/vsh-policy", "crates/vsh-monty", "crates/vsh-commit", "crates/vbash", "crates/vsh", "crates/vsh-python", "crates/vsh-worker"]
 
 [workspace.package]
-version = "0.4.0"
+version = "0.5.0"
 edition = "2024"
 rust-version = "1.95"
 license = "Apache-2.0"
@@ -23,14 +23,14 @@ monty-proto = { version = "=0.0.22", default-features = false }
 monty-types = { version = "=0.0.22", default-features = false }
 postcard = { version = "=1.1.3", default-features = false, features = ["alloc"] }
 pyo3 = { version = "=0.29.2", default-features = false }
-vsh-monty = { path = "crates/vsh-monty", version = "=0.4.0" }
-vsh-commit = { path = "crates/vsh-commit", version = "=0.4.0" }
-vsh-policy = { path = "crates/vsh-policy", version = "=0.4.0" }
-vsh-types = { path = "crates/vsh-types", version = "=0.4.0" }
-vsh-store = { path = "crates/vsh-store", version = "=0.4.0" }
-vsh-vfs = { path = "crates/vsh-vfs", version = "=0.4.0" }
-vsh-runtime = { path = "crates/vbash", version = "=0.4.0" }
-vsh = { path = "crates/vsh", version = "=0.4.0" }
+vsh-monty = { path = "crates/vsh-monty", version = "=0.5.0" }
+vsh-commit = { path = "crates/vsh-commit", version = "=0.5.0" }
+vsh-policy = { path = "crates/vsh-policy", version = "=0.5.0" }
+vsh-types = { path = "crates/vsh-types", version = "=0.5.0" }
+vsh-store = { path = "crates/vsh-store", version = "=0.5.0" }
+vsh-vfs = { path = "crates/vsh-vfs", version = "=0.5.0" }
+vsh-runtime = { path = "crates/vbash", version = "=0.5.0" }
+vsh = { path = "crates/vsh", version = "=0.5.0" }
 
 [workspace.lints.rust]
 elided_lifetimes_in_paths = "deny"

{vsh_python-0.4.0 → vsh_python-0.5.0}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: vsh-python
-Version: 0.4.0
+Version: 0.5.0
 Classifier: Development Status :: 4 - Beta
 Classifier: Intended Audience :: Developers
 Classifier: Programming Language :: Python :: 3
@@ -11,6 +11,7 @@ Classifier: Programming Language :: Python :: 3.14
 Classifier: Programming Language :: Rust
 Requires-Dist: basedpyright ; extra == 'dev'
 Requires-Dist: maturin==1.15.0 ; extra == 'dev'
+Requires-Dist: pydantic-ai-slim==2.40.0 ; extra == 'dev'
 Requires-Dist: pytest ; extra == 'dev'
 Requires-Dist: pytest-cov ; extra == 'dev'
 Requires-Dist: ruff ; extra == 'dev'
@@ -18,8 +19,10 @@ Requires-Dist: setuptools==84.0.0 ; extra == 'dev'
 Requires-Dist: ty ; extra == 'dev'
 Requires-Dist: zensical==0.0.57 ; extra == 'dev'
 Requires-Dist: fastmcp==3.4.7 ; extra == 'mcp'
+Requires-Dist: pydantic-ai-slim==2.40.0 ; extra == 'pydantic-ai'
 Provides-Extra: dev
 Provides-Extra: mcp
+Provides-Extra: pydantic-ai
 License-File: LICENSE
 Summary: VSH is a low-latency transactional filesystem simulator backed by Rust.
 Keywords: agents,commands,mcp,simulation,workspaces
@@ -84,11 +87,39 @@ print(receipt.state, receipt.result, receipt.changes)
 The GIL is released while snapshotting, executing Monty, generating the diff,
 evaluating policy, revalidating dependencies, and committing.
 
+### Pydantic AI
+
+Install the exact-pinned optional integration:
+
+```bash
+uv add "vsh-python[pydantic-ai]"
+```
+
+```python
+from pydantic_ai import Agent
+from vsh.pydantic_ai import VshCapability
+
+capability = VshCapability("/path/to/workspace")
+agent = Agent("openai:gpt-5", capabilities=[capability])
+```
+
+The capability contributes the ten native `vsh_*` filesystem operations plus
+`vsh_run` for atomic multi-step work. Every call executes in a virtual snapshot first.
+Policy-controlled changes commit exactly once or return `pending_approval`; no internal
+LLM judge is created implicitly.
+
+For explicitly configured model review, attach a
+[`CommitJudge`](https://fswair.github.io/vsh/python/commit-judge/) through
+`hook_handler=judge.hook_handler`. It evaluates canonical changes, before/after
+content, effects and intent together. A valid approval can directly commit pending
+work; native hard-deny and stale checks remain enforced. Review returns actionable
+feedback to the main agent.
+
 ## Rust
 
 ```toml
 [dependencies]
-vsh = "=0.4.0"
+vsh = "=0.5.0"
 ```
 
 ```rust,no_run
@@ -114,7 +145,7 @@ wheels bundle it; native embedders configure its trusted path through
 
 ## Active-snapshot filesystem functions
 
-VSH 0.4.0 injects ten bounded `vsh_*` functions into each Monty program: read, write,
+VSH injects ten bounded `vsh_*` functions into each Monty program: read, write,
 list, make directory, remove, move, copy, glob, literal search and exact text patch.
 They share the same copy-on-write snapshot as `pathlib`, so earlier virtual writes are
 visible to later calls without creating a nested runtime or crossing MCP.
@@ -168,19 +199,16 @@ and sampled process-tree RSS does not establish a repeatable memory reduction. S
 - Process-local preview retention is fail-closed and bounded by both artifact count and
   encoded bytes; it cannot become an unbounded parent-process cache.
 
-See the [threat model](https://fswair.github.io/vsh/rust-rewrite/THREAT_MODEL/),
-[guarantees](https://fswair.github.io/vsh/rust-rewrite/GUARANTEES/), and
-[dependency record](https://fswair.github.io/vsh/rust-rewrite/DEPENDENCY_POLICY/).
-Upgrade and benchmark details are in the
-[migration guide](https://fswair.github.io/vsh/rust-rewrite/MIGRATION/) and current
-[performance report](https://fswair.github.io/vsh/performance/). Merge coverage scope
-and floors are recorded in the
-[coverage contract](https://fswair.github.io/vsh/rust-rewrite/COVERAGE/).
+See the [threat model](https://fswair.github.io/vsh/threat-model/),
+[guarantees](https://fswair.github.io/vsh/guarantees/),
+[dependency policy](https://fswair.github.io/vsh/dependency-policy/), current
+[performance report](https://fswair.github.io/vsh/performance/), and
+[coverage contract](https://fswair.github.io/vsh/coverage/).
 
-## Compatibility handles
+## Package names
 
-Existing declarations may continue to install `vbash==0.4.0` from PyPI or depend on
-`vbash = "=0.4.0"` from crates.io. Both packages are implementation-free mirrors of
+Existing declarations may install `vbash==0.5.0` from PyPI or depend on
+`vbash = "=0.5.0"` from crates.io. Both names are implementation-free mirrors of
 the exact matching VSH release. New projects should use `vsh-python` and `vsh`
 directly; Python code continues to write `import vsh` either way.
 

{vsh_python-0.4.0 → vsh_python-0.5.0}/README.md

@@ -54,11 +54,39 @@ print(receipt.state, receipt.result, receipt.changes)
 The GIL is released while snapshotting, executing Monty, generating the diff,
 evaluating policy, revalidating dependencies, and committing.
 
+### Pydantic AI
+
+Install the exact-pinned optional integration:
+
+```bash
+uv add "vsh-python[pydantic-ai]"
+```
+
+```python
+from pydantic_ai import Agent
+from vsh.pydantic_ai import VshCapability
+
+capability = VshCapability("/path/to/workspace")
+agent = Agent("openai:gpt-5", capabilities=[capability])
+```
+
+The capability contributes the ten native `vsh_*` filesystem operations plus
+`vsh_run` for atomic multi-step work. Every call executes in a virtual snapshot first.
+Policy-controlled changes commit exactly once or return `pending_approval`; no internal
+LLM judge is created implicitly.
+
+For explicitly configured model review, attach a
+[`CommitJudge`](https://fswair.github.io/vsh/python/commit-judge/) through
+`hook_handler=judge.hook_handler`. It evaluates canonical changes, before/after
+content, effects and intent together. A valid approval can directly commit pending
+work; native hard-deny and stale checks remain enforced. Review returns actionable
+feedback to the main agent.
+
 ## Rust
 
 ```toml
 [dependencies]
-vsh = "=0.4.0"
+vsh = "=0.5.0"
 ```
 
 ```rust,no_run
@@ -84,7 +112,7 @@ wheels bundle it; native embedders configure its trusted path through
 
 ## Active-snapshot filesystem functions
 
-VSH 0.4.0 injects ten bounded `vsh_*` functions into each Monty program: read, write,
+VSH injects ten bounded `vsh_*` functions into each Monty program: read, write,
 list, make directory, remove, move, copy, glob, literal search and exact text patch.
 They share the same copy-on-write snapshot as `pathlib`, so earlier virtual writes are
 visible to later calls without creating a nested runtime or crossing MCP.
@@ -138,19 +166,16 @@ and sampled process-tree RSS does not establish a repeatable memory reduction. S
 - Process-local preview retention is fail-closed and bounded by both artifact count and
   encoded bytes; it cannot become an unbounded parent-process cache.
 
-See the [threat model](https://fswair.github.io/vsh/rust-rewrite/THREAT_MODEL/),
-[guarantees](https://fswair.github.io/vsh/rust-rewrite/GUARANTEES/), and
-[dependency record](https://fswair.github.io/vsh/rust-rewrite/DEPENDENCY_POLICY/).
-Upgrade and benchmark details are in the
-[migration guide](https://fswair.github.io/vsh/rust-rewrite/MIGRATION/) and current
-[performance report](https://fswair.github.io/vsh/performance/). Merge coverage scope
-and floors are recorded in the
-[coverage contract](https://fswair.github.io/vsh/rust-rewrite/COVERAGE/).
+See the [threat model](https://fswair.github.io/vsh/threat-model/),
+[guarantees](https://fswair.github.io/vsh/guarantees/),
+[dependency policy](https://fswair.github.io/vsh/dependency-policy/), current
+[performance report](https://fswair.github.io/vsh/performance/), and
+[coverage contract](https://fswair.github.io/vsh/coverage/).
 
-## Compatibility handles
+## Package names
 
-Existing declarations may continue to install `vbash==0.4.0` from PyPI or depend on
-`vbash = "=0.4.0"` from crates.io. Both packages are implementation-free mirrors of
+Existing declarations may install `vbash==0.5.0` from PyPI or depend on
+`vbash = "=0.5.0"` from crates.io. Both names are implementation-free mirrors of
 the exact matching VSH release. New projects should use `vsh-python` and `vsh`
 directly; Python code continues to write `import vsh` either way.
 

{vsh_python-0.4.0 → vsh_python-0.5.0}/crates/vbash/README.md

@@ -54,11 +54,39 @@ print(receipt.state, receipt.result, receipt.changes)
 The GIL is released while snapshotting, executing Monty, generating the diff,
 evaluating policy, revalidating dependencies, and committing.
 
+### Pydantic AI
+
+Install the exact-pinned optional integration:
+
+```bash
+uv add "vsh-python[pydantic-ai]"
+```
+
+```python
+from pydantic_ai import Agent
+from vsh.pydantic_ai import VshCapability
+
+capability = VshCapability("/path/to/workspace")
+agent = Agent("openai:gpt-5", capabilities=[capability])
+```
+
+The capability contributes the ten native `vsh_*` filesystem operations plus
+`vsh_run` for atomic multi-step work. Every call executes in a virtual snapshot first.
+Policy-controlled changes commit exactly once or return `pending_approval`; no internal
+LLM judge is created implicitly.
+
+For explicitly configured model review, attach a
+[`CommitJudge`](https://fswair.github.io/vsh/python/commit-judge/) through
+`hook_handler=judge.hook_handler`. It evaluates canonical changes, before/after
+content, effects and intent together. A valid approval can directly commit pending
+work; native hard-deny and stale checks remain enforced. Review returns actionable
+feedback to the main agent.
+
 ## Rust
 
 ```toml
 [dependencies]
-vsh = "=0.4.0"
+vsh = "=0.5.0"
 ```
 
 ```rust,no_run
@@ -84,7 +112,7 @@ wheels bundle it; native embedders configure its trusted path through
 
 ## Active-snapshot filesystem functions
 
-VSH 0.4.0 injects ten bounded `vsh_*` functions into each Monty program: read, write,
+VSH injects ten bounded `vsh_*` functions into each Monty program: read, write,
 list, make directory, remove, move, copy, glob, literal search and exact text patch.
 They share the same copy-on-write snapshot as `pathlib`, so earlier virtual writes are
 visible to later calls without creating a nested runtime or crossing MCP.
@@ -138,19 +166,16 @@ and sampled process-tree RSS does not establish a repeatable memory reduction. S
 - Process-local preview retention is fail-closed and bounded by both artifact count and
   encoded bytes; it cannot become an unbounded parent-process cache.
 
-See the [threat model](https://fswair.github.io/vsh/rust-rewrite/THREAT_MODEL/),
-[guarantees](https://fswair.github.io/vsh/rust-rewrite/GUARANTEES/), and
-[dependency record](https://fswair.github.io/vsh/rust-rewrite/DEPENDENCY_POLICY/).
-Upgrade and benchmark details are in the
-[migration guide](https://fswair.github.io/vsh/rust-rewrite/MIGRATION/) and current
-[performance report](https://fswair.github.io/vsh/performance/). Merge coverage scope
-and floors are recorded in the
-[coverage contract](https://fswair.github.io/vsh/rust-rewrite/COVERAGE/).
+See the [threat model](https://fswair.github.io/vsh/threat-model/),
+[guarantees](https://fswair.github.io/vsh/guarantees/),
+[dependency policy](https://fswair.github.io/vsh/dependency-policy/), current
+[performance report](https://fswair.github.io/vsh/performance/), and
+[coverage contract](https://fswair.github.io/vsh/coverage/).
 
-## Compatibility handles
+## Package names
 
-Existing declarations may continue to install `vbash==0.4.0` from PyPI or depend on
-`vbash = "=0.4.0"` from crates.io. Both packages are implementation-free mirrors of
+Existing declarations may install `vbash==0.5.0` from PyPI or depend on
+`vbash = "=0.5.0"` from crates.io. Both names are implementation-free mirrors of
 the exact matching VSH release. New projects should use `vsh-python` and `vsh`
 directly; Python code continues to write `import vsh` either way.
 

{vsh_python-0.4.0 → vsh_python-0.5.0}/crates/vbash/examples/native_benchmark.rs

@@ -449,7 +449,7 @@ fn parse_arguments() -> io::Result<Arguments> {
         cold_iterations: 30,
         parallel_workers: 4,
         worker: PathBuf::from("vsh-monty-worker"),
-        output: PathBuf::from("reports/rust-rewrite/native-rust.json"),
+        output: PathBuf::from("benchmarks/results/local/native-rust.json"),
     };
     let mut arguments = std::env::args_os().skip(1);
     while let Some(argument) = arguments.next() {