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: [master]
+    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/icons — read by hanzoai/ci (via
+# .hanzo/workflows/cicd.yml) and by platform.hanzo.ai.
+#
+# Library (pnpm workspace, React components). The gate is `tsc --noEmit` over
+# src/: every icon is a typed component, so the typecheck is what fails when one
+# is malformed. The `build` script is not the gate — its first step shells out
+# to `bun`, which is not a toolchain this fleet provisions, so it would fail for
+# a reason that has nothing to do with the code.
+#
+# No lockfile is committed, hence the non-frozen install; pnpm via npx at a
+# pinned major because there is no `packageManager` field for corepack to read.
+test:
+  - name: typecheck
+    run: npx --yes pnpm@10 install --no-frozen-lockfile && npx --yes pnpm@10 run type-check