deps: floor hanzo-tools at the version that actually has HanzoCloud

The unified `hanzo` tool imports HanzoCloud from hanzo_tools.core, which
hanzo-tools first shipped in 0.3.3 — but nothing in the dependency graph
required it. hanzo-tools-api asked for `hanzo-tools-core>=0.1.0`, an empty
shim whose own floor is hanzo-tools>=0.3.2, and 0.3.2 has no cloud.py at all.
A resolver was therefore free to satisfy every constraint and still produce an
install where `from hanzo_tools.core import HanzoCloud` raises ImportError.
That is exactly what happened: the legacy-tool gate logged "unified hanzo tool
not importable" and fell back, and the dev venv had to install hanzo-tools
editable to get a working `hanzo`.

Name the real dependency at the real floor:
- hanzo-tools-api: hanzo-tools-core>=0.1.0 -> hanzo-tools>=0.3.4. It imports
  hanzo_tools.core directly, so it must depend on the package that owns it;
  the >=0.1.0 shim floor also still admitted the shadowing duplicate.
- hanzo-tools-vector: hanzo-tools>=0.3.0 -> >=0.3.4 (cloud_vector.py).
- hanzo-mcp: hanzo-tools>=0.3.2 -> >=0.3.4, hanzo-tools-api>=0.3.1 -> >=0.3.2.

Metadata only, on versions not yet published. No version bumps.

Co-authored-by: Hanzo Dev <[email protected]>

pkg/hanzo-mcp/pyproject.toml

@@ -30,7 +30,7 @@ dependencies = [
     "hanzo-async>=0.1.3",
     "uvloop>=0.22.1; sys_platform != 'win32'",
     # Hanzo tool infrastructure (all tools)
-    "hanzo-tools>=0.3.2",        # 0.3.2 owns hanzo_tools.core exclusively + adds ToolImage (native MCP images)
+    "hanzo-tools>=0.3.4",        # 0.3.4 owns hanzo_tools.core exclusively, incl. HanzoCloud (the unified `hanzo` tool needs it)
     "hanzo-tools-fs>=0.3.4",     # 0.3.4 returns image files as native MCP ImageContent
     "hanzo-tools-shell>=0.6.5",  # 0.6.5 pairs with hanzo-tools>=0.3.0 (ToolError)
     "hanzo-tools-core>=0.3.1",   # 0.3.1 is the EMPTY shim — no longer shadows canonical hanzo-tools.core
@@ -48,7 +48,7 @@ dependencies = [
     "hanzo-tools-vcs>=0.1.0",
     "hanzo-tools-net>=0.1.0",
     "hanzo-tools-agent>=0.3.1",
-    "hanzo-tools-api>=0.3.1",
+    "hanzo-tools-api>=0.3.2",    # 0.3.2 is the unified `hanzo` tool projected from cloud's OpenAPI registry
     "hanzo-tools-auth>=0.1.0",
     "hanzo-tools-kms>=0.1.0",
     "hanzo-tools-paas>=0.1.0",

pkg/hanzo-tools-api/pyproject.toml

@@ -16,7 +16,11 @@ classifiers = [
 ]
 
 dependencies = [
-    "hanzo-tools-core>=0.1.0",
+    # hanzo_tool.py imports HanzoCloud from hanzo_tools.core, which canonical
+    # hanzo-tools owns and first shipped in 0.3.3. The old hanzo-tools-core dep
+    # named a shim whose floor (0.1.0) both allowed the shadowing duplicate and
+    # guaranteed nothing about HanzoCloud, so the unified tool failed to import.
+    "hanzo-tools>=0.3.4",
     "httpx>=0.27.0",
     "pydantic>=2.0",
     "pyyaml>=6.0",

pkg/hanzo-tools-vector/pyproject.toml

@@ -12,7 +12,7 @@ license = { text = "MIT" }
 authors = [{ name = "Hanzo Industries Inc", email = "[email protected]" }]
 keywords = ["hanzo", "tools", "vector", "embeddings", "rag", "mcp", "ai"]
 dependencies = [
-    "hanzo-tools>=0.3.0",
+    "hanzo-tools>=0.3.4",  # cloud_vector.py imports HanzoCloud (hanzo_tools.core, 0.3.3+)
     "mcp>=1.25.0",
     "fastmcp>=2.14.1",
     "pydantic>=2.12.5",