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,19 @@
+# Canonical CI/CD config for hanzoai/bufferutil — read by the hanzoai/ci
+# reusable workflow (.hanzo/workflows/cicd.yml) and by platform.hanzo.ai.
+#
+# LIBRARY: the WebSocket mask/unmask primitive — a C++ N-API addon with a pure-JS
+# fallback. No image, no deploy — it ships from a tag.
+#
+# `npm install` is load-bearing here and is not just "fetch the deps": the
+# package's own `install` script is node-gyp-build, so this compiles src/
+# against the runner's Node headers. That is the gate for the half of this
+# library that a JS test cannot reach — if the addon does not build, this goes
+# red before mocha ever starts.
+#
+# Then mocha runs test/, which checks that the masked output is byte-identical
+# across the native and fallback paths. Both halves, in one command, which is
+# the only way to test a package whose whole job is that two implementations
+# agree.
+test:
+  - name: build-and-test
+    run: npm install && npm test