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,12 @@
+# fsevents — NO GATE EXISTS ON THIS FLEET, and saying so is the honest
+# declaration.
+#
+# This is a darwin-only native module: package.json declares `os: [darwin]`, so
+# npm refuses to install it at all on linux (EBADPLATFORM), and binding.gyp
+# declares its targets under `OS=="mac"` — meaning `npm run build` on linux runs
+# node-gyp over ZERO targets and exits 0 having built nothing. Every test in
+# test/ requires the compiled fsevents.node. A `test:` block here could only be
+# one of those two lies, so there is none: the run instead carries the
+# workflow's own "this build was NOT tested" warning, plus the structural
+# invariants (ignoretracked / modsize / conflictmarkers) that gate every repo.
+# It becomes gateable the day the fleet has a darwin runner.