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,12 @@
+# This fork has had no build gate at all — .github/workflows holds only
+# triage.yml. `npm ci && npm run compile` is the repo's real build (gulp over
+# the whole workbench plus every bundled extension), so it is what runs.
+#
+# The apt line is not scaffolding: on Linux the postinstall step compiles
+# native-keymap, node-pty and keytar, which need the X11/kerberos/libsecret
+# headers. Without them `npm ci` dies in node-gyp before any TypeScript is read.
+# Chained with && so a failure early cannot be masked by a later success — the
+# reusable runs gates under `bash -c`, with no set -e of its own.
+test:
+  - name: build
+    run: sudo apt-get update && sudo apt-get install -y --no-install-recommends build-essential g++ python3 libx11-dev libxkbfile-dev libsecret-1-dev libkrb5-dev && npm ci && npm run compile