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, master]
+    tags: ['v*']
+  pull_request:
+  workflow_dispatch:
+jobs:
+  cicd:
+    uses: hanzoai/ci/.hanzo/workflows/build.yml@v1
+    secrets: inherit

hanzo.yml

@@ -0,0 +1,16 @@
+# hanzoai/dashscope-go-sdk — Go client for the DashScope/Qwen APIs. A library:
+# ships from a tag as a Go module, builds no image, deploys nowhere.
+#
+# Compile everything, then run the suite. The suite is honest without a
+# credential: the tests that need a live key call t.Skip when DASHSCOPE_API_KEY
+# is empty, and the gomock-backed tests (request shaping, response decoding,
+# the SSE stream splitter) run offline and are the ones that actually pin this
+# client's behaviour. So this gate goes red on a real break and never on a
+# missing secret.
+test:
+  - name: build-and-test
+    run: |
+      set -e
+      go build ./...
+      go vet ./...
+      go test -count=1 ./...