Pin jvspatial 0.0.22 and release 0.1.8rc18

.planning/reference/jvspatial-integration.md

@@ -7,7 +7,7 @@
 ## 1. Where jvspatial lives
 
 - **Source**: `/Users/eldonmarks/Briefcase/dev/jv/jvspatial` (sibling directory in this workspace).
-- **Pip install**: declared in [`pyproject.toml`](../../pyproject.toml) as `jvspatial==0.0.21`.
+- **Pip install**: declared in [`pyproject.toml`](../../pyproject.toml) as `jvspatial==0.0.22`.
 - **Own docs**: jvspatial has its own [`README.md`](../../../jvspatial/README.md) and [`SPEC.md`](../../../jvspatial/SPEC.md). Treat those as authoritative for anything below.
 
 ---
@@ -171,7 +171,7 @@ Things jvagent **owns**:
 
 ## 5. Version policy
 
-- Minimum required jvspatial: pinned in [`pyproject.toml`](../../pyproject.toml) as `jvspatial==X.Y.Z`. Current: `==0.0.21`.
+- Minimum required jvspatial: pinned in [`pyproject.toml`](../../pyproject.toml) as `jvspatial==X.Y.Z`. Current: `==0.0.22`.
 - When jvspatial introduces breaking changes (e.g., walker API rename, persistence shape change), bump the pin and update this section.
 - When adding a new dependency on a jvspatial feature, document the symbol + version it was introduced in. Helps downstream consumers know the floor.
 - Rationale: [`adr/0006-jvspatial-dependency.md`](../adr/0006-jvspatial-dependency.md).

CHANGELOG.md

@@ -521,6 +521,13 @@ and this project adheres to [PEP 440](https://peps.python.org/pep-0440/) /
   ``get_access_control_action`` / ``get_action_by_type`` heal duplicates on
   read; graph repair uses the same keeper heuristic as bootstrap dedupe.
 
+## [0.1.8rc18] - 2026-09-26
+
+### Changed
+
+- **Require `jvspatial==0.0.22`.** Picks up public `graph_transaction` so a
+  multi-write facet can commit or roll back as one unit.
+
 ## [0.1.8rc17] - 2026-09-24
 
 ### Added

jvagent/version.py

@@ -1,3 +1,3 @@
 """Version information for jvagent package."""
 
-__version__ = "0.1.8rc17"
+__version__ = "0.1.8rc18"

pyproject.toml

@@ -31,7 +31,7 @@ classifiers = [
 dependencies = [
     "aiohttp>=3.9.0",
     # CI records the resolved jvspatial version after install (see .github/workflows/test-jvagent.yaml).
-    "jvspatial==0.0.21",
+    "jvspatial==0.0.22",
     "python-dotenv>=1.0.0",
     "pyyaml>=6.0.0",
     "httpx>=0.27.0",

requirements-all.txt

@@ -6,7 +6,7 @@
 # Must stay in sync with [project] dependencies in pyproject.toml —
 # enforced by tests/test_requirements_sync.py.
 aiohttp>=3.9.0
-jvspatial==0.0.21
+jvspatial==0.0.22
 python-dotenv>=1.0.0
 pyyaml>=6.0.0
 httpx>=0.27.0

requirements.txt

@@ -3,7 +3,7 @@
 # Test-only deps (incl. Docling for PageIndex): pyproject.toml
 # [project.optional-dependencies] test — install with: pip install -e ".[test]"
 aiohttp>=3.9.0
-jvspatial==0.0.21
+jvspatial==0.0.22
 python-dotenv>=1.0.0
 pyyaml>=6.0.0
 httpx>=0.27.0