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 @@
+# Canonical CI/CD config for hanzoai/sql-meta — read by the hanzoai/ci reusable
+# (.hanzo/workflows/cicd.yml) and by platform.hanzo.ai.
+#
+# PostgreSQL metadata/management API. The repo is a pinned re-tag of the
+# upstream image with our provenance labels — there is no source in it, so the
+# Dockerfile IS the gate and a `test:` block would have nothing to compile.
+# It can still go red, which is the point: the pin is an exact upstream tag,
+# and this build fails the moment that tag stops resolving.
+#
+# No `deploy:` — no operator Service CR names this image yet.
+
+images:
+  - name: sql-meta
+    context: .
+    dockerfile: Dockerfile
+    repo: ghcr.io/hanzoai/sql-meta