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.

.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,13 @@
+# Canonical CI for hanzoai/prettier — a vendored upstream fork.
+#
+# No `images:` and no `deploy:`: we do not ship this, we carry it. What CI owes
+# a fork is proof that the checkout still builds, so a bad merge from upstream —
+# or a dependency that moved under us — goes red here instead of in whatever
+# consumes it. The build is the real bundler run, so a broken source fails it.
+test:
+  - name: build
+    run: |
+      set -e
+      corepack enable
+      yarn install --immutable
+      yarn build