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,10 @@
+# The canonical Node base image. There is no source to test here — the
+# Dockerfile IS the gate: it round-trips an in-memory DB through node:sqlite AND
+# compiles better-sqlite3 from source against the baked-in toolchain, and the
+# image fails to build if either stops working. No `test:` block, because a
+# second command run outside the image would be testing something else.
+images:
+  - name: nodejs
+    context: .
+    dockerfile: Dockerfile
+    repo: ghcr.io/hanzoai/nodejs