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 @@
+# node-dtrace-provider — the tap suite needs a working dtrace(1), which linux
+# does not have, so it cannot be the gate here. What linux consumers actually
+# exercise is the other half of this package: the stub provider it falls back to
+# (bunyan loads it on every non-dtrace host). The gate installs — which runs the
+# real node-gyp build and its documented fallback — and then drives the whole
+# provider API through it. Red on a broken build path, a broken fallback, or a
+# changed API.
+test:
+  - name: provider-smoke
+    run: |
+      npm i --no-audit --no-fund
+      node -e 'const d=require("./dtrace-provider.js"); const p=d.createDTraceProvider("hanzoci"); p.addProbe("gate","int"); p.enable(); p.fire("gate", function(){ return [1]; }); p.disable();'