chore(deps): pin jvspatial 0.1.1

[eldonm]

Summary

Pin published jvspatial==0.1.1 consistently in package metadata and both requirements files. Update the agent guide and integration reference to match the published dependency policy.

Review and validation

• Reviewed jvagent's jvspatial boundary, including the Action compound index that uses long PostgreSQL names. The jvspatial 0.1.1 changes are internal PostgreSQL index and bootstrap fixes; no jvagent API migration was needed.
• Fresh Python 3.11 environment: pip install -e '.[test]' resolved jvspatial 0.1.1 from PyPI; pip check passed and jvspatial had no direct_url.json source override.
• Dependency synchronization, wire-contract, and PostgreSQL server-config tests passed.
• With published jvspatial 0.1.1, a real PostgreSQL schema created all ten indexes for jvagent's Action, including the long unique action index.
• Changed-file pre-commit hooks passed.