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: [canary]
+    tags: ['v*']
+  pull_request:
+  workflow_dispatch:
+jobs:
+  cicd:
+    uses: hanzoai/ci/.hanzo/workflows/build.yml@v1
+    secrets: inherit

hanzo.yml

@@ -0,0 +1,14 @@
+# Next.js. npm packages, no image.
+#
+# The gate is the project's own `pnpm build` — turbo across every workspace
+# package (next, next-swc bindings' JS side, font, eslint-plugin, the codemods
+# and the create-next-app CLI). It compiles and bundles the whole tree, so a
+# type error or a broken build script in any package fails it.
+#
+# Not the jest suites: `test-dev` / `test-start` / `test-prod` each boot real
+# browsers against a built app and upstream runs them as a large sharded matrix.
+# One runner cannot hold that, and a fraction of it declared as the gate would
+# report less than it appears to.
+test:
+  - name: build
+    run: pnpm install --frozen-lockfile && pnpm build