hanzoai 8.5.161: the import report runs under the interpreter its siblings fetch

v8.5.160 regenerated the client and its release run passed the client check,
then stopped at declared-imports: the step called bare `python`, the runner has
none on its PATH, and exit 127 from a step that is report only ended the run
before anything was published. It now runs through uv like the three steps
beside it. Verified by running the whole test: block with no python on PATH.

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

hanzo.yml

@@ -78,9 +78,18 @@ test:
   # This still earns its place: relying on a transitive dependency is a break
   # waiting for the day that sibling drops it, and 92 rows is a map of where
   # that risk sits. Read it, do not gate on it.
+  #
+  # It runs under the interpreter the steps beside it fetch. The runner has no
+  # `python` on its PATH, so the bare name exited 127 and a step that is report
+  # only stopped a release.
   - name: declared-imports
     run: |
-      python - <<'PY'
+      set -e
+      if command -v uv >/dev/null 2>&1; then UV=uv; else
+        curl -fsSL https://astral.sh/uv/install.sh | sh
+        UV="$HOME/.local/bin/uv"
+      fi
+      "$UV" run --no-project --python 3.12 python - <<'PY'
       import ast, pathlib, sys, tomllib
 
       # import name -> distribution name, where they differ.

pyproject.toml

@@ -1,6 +1,6 @@
 [project]
 name = "hanzoai"
-version = "8.5.160"
+version = "8.5.161"
 description = "The official Python library for the Hanzo API"
 dynamic = ["readme"]
 license = "Apache-2.0"

uv.lock

@@ -2252,7 +2252,7 @@ wheels = [
 
 [[package]]
 name = "hanzoai"
-version = "8.5.160"
+version = "8.5.161"
 source = { editable = "." }
 dependencies = [
     { name = "pydantic" },