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,15 @@
+# Go ORM library — ships from a tag, builds no image.
+#
+# Gate: the module compiles, and every package whose tests need no live database
+# actually runs them. The root and tests/ suites drive MySQL/Postgres/MSSQL/TiDB
+# and are what `make test-<driver>` exists for — they need a server, so they are
+# not a push gate. `go vet ./...` is red on this tree today (legacy reflect
+# shapes); wiring it in would ship a gate that is red for a reason nobody
+# introduced, so the compile is the assertion here.
+test:
+  - name: build-and-unit
+    run: |
+      set -euo pipefail
+      go build ./...
+      go test ./caches/... ./convert/... ./core/... ./dialects/... \
+              ./internal/... ./log/... ./names/... ./schemas/... ./tags/...