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,19 @@
+# Hanzo Frames — the programmatic video toolkit (14 workspace packages, bun).
+#
+# The gate is upstream's own build job, verbatim: install from the frozen
+# bun.lock, build every package in dependency order, then typecheck all of them.
+# The build alone would miss type errors in code it does not emit, which is why
+# the typecheck follows rather than replaces it.
+#
+# bun is curl-installed when absent — the runner image has none, and this repo
+# is bun-native (bun.lock, `bun run --filter`), so there is no npm spelling of
+# this that would be the same gate.
+test:
+  - name: build
+    run: |
+      set -e
+      command -v bun >/dev/null 2>&1 || curl -fsSL https://bun.sh/install | bash
+      export PATH="$HOME/.bun/bin:$PATH"
+      bun install --frozen-lockfile
+      bun run build
+      bun run --filter '*' typecheck