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,14 @@
+# Canonical CI/CD config for hanzoai/unrs-resolver — read by hanzoai/ci (via
+# .hanzo/workflows/cicd.yml) and by platform.hanzo.ai.
+#
+# Rust napi addon published to npm. The gate is `cargo check` over the whole
+# workspace INCLUDING test and bench targets — the resolver is Rust, the npm
+# package is a thin binding around it, so a type or borrow error in src/ is the
+# break, and --all-targets is what stops a test file from rotting unnoticed.
+#
+# `check`, not `build --release`: the release napi link step produces the
+# artifact but proves nothing the type check has not already proven, and the
+# release lane (release-napi.yml) is where the artifact belongs.
+test:
+  - name: cargo-check
+    run: cargo check --workspace --all-targets