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,11 @@
+# The Firebase JS SDK — a lerna/yarn monorepo of ~40 published packages.
+# The gate is the project's own build: every @firebase/* package plus the
+# `firebase` umbrella, each compiled with its own tsc/rollup config. A type
+# error or a broken export map in any package fails it.
+#
+# The suites are not here: they run against browsers and against live emulator
+# instances (firestore, database, auth), which is a fixture this runner has not
+# got and which would make the gate report on the emulator, not the SDK.
+test:
+  - name: build
+    run: yarn install --frozen-lockfile && yarn build