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,16 @@
+# Hanzo eSign — a turborepo whose deployable artifact is the remix app.
+#
+# Gate only. The image is already built and pushed by the native builder in this
+# repo (.hanzo/workflows/deploy.yml → ghcr.io/hanzoai/sign:<tag>), so declaring
+# `images:` here would publish a second copy of the same commit.
+#
+# The gate is the real build of the app the cluster runs: npm ci against the
+# committed lockfile (postinstall generates the Prisma client), then turbo's
+# build of @hanzo/esign-remix, which type-checks every workspace package it
+# depends on. A type error anywhere under packages/ fails here.
+test:
+  - name: build
+    run: |
+      set -euo pipefail
+      npm ci --no-audit --no-fund
+      npx turbo run build --filter=@hanzo/esign-remix