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 @@
+# Canonical CI/CD config for hanzoai/logo — the one file both the hanzoai/ci
+# reusable (.hanzo/workflows/cicd.yml) and platform.hanzo.ai read.
+#
+# GATE ONLY: @hanzo/logo is an npm package, and the logo site has its own lanes
+# already (.hanzo/workflows/publish.yml, deploy.yml). A second image build for
+# the same Dockerfile on the same push buys nothing.
+#
+# `pnpm test` here is `pnpm typecheck && pnpm build` — and the build half is the
+# real gate, because this package's output is GENERATED: `pnpm generate` runs
+# the compiled dist/build.js, which bakes the tuner's animation states into the
+# svg + animated.ts that every consumer imports. A break in the generator is a
+# break in the artifact, and it only shows when the generator is actually run.
+test:
+  - name: build
+    run: |
+      set -e
+      corepack enable
+      pnpm install --frozen-lockfile
+      pnpm test