ci: canonical pair — hanzo.yml + forge caller

github.com has no runner for hanzo-build-linux-amd64, so a caller under
.github/workflows is a gate that can never be scheduled. This is the ~7-line
caller on the plane that can (git.hanzo.ai git-runner fleet), pinned @v1.

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

.hanzo/workflows/cicd.yml

@@ -0,0 +1,15 @@
+# Canonical caller — every knob lives in /hanzo.yml, none here.
+# Runs on the git-runner fleet at git.hanzo.ai, the only pool serving these
+# labels. github.com resolves only .github/workflows and has no runner for
+# them, so a caller placed there is a gate that cannot be scheduled.
+name: CI/CD
+on:
+  push:
+    branches: [main]
+    tags: ['v*']
+  pull_request:
+  workflow_dispatch:
+jobs:
+  cicd:
+    uses: hanzoai/ci/.hanzo/workflows/build.yml@v1
+    secrets: inherit

hanzo.yml

@@ -0,0 +1,13 @@
+# Rust bindings to the ROCm stack (HIP, rocBLAS, rocFFT, MIOpen, …).
+#
+# Gate: the crate compiles against the bindings committed under src/*/bindings.rs.
+# SKIP_BINDGEN is the escape build.rs itself declares for exactly this case — a
+# host with no /opt/rocm regenerates nothing and uses the checked-in bindings, so
+# what CI proves is that the Rust in this repo compiles against the bindings this
+# repo ships. Regenerating them needs ROCm headers and an AMD host; that is a
+# hardware lane, not a push gate.
+test:
+  - name: build
+    run: |
+      set -euo pipefail
+      SKIP_BINDGEN=1 cargo build --locked --all-features