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,18 @@
+# Canonical CI/CD config for hanzoai/uuid — read by the hanzoai/ci reusable
+# workflow (.hanzo/workflows/cicd.yml) and by platform.hanzo.ai.
+#
+# LIBRARY: RFC 9562 UUID generation and parsing. No image, no deploy — it ships
+# from a tag.
+#
+# `npm test` runs `pretest` first, so the one command is build-then-test: the
+# four builds (ESM browser, ESM node, CJS, types) are produced by
+# scripts/build.sh and then `node --test dist-node/test/*.js` runs the suite
+# against the BUILT output rather than against src/. That ordering is the point
+# — this package's historical breakages have been in what the build emitted
+# (export maps, dual-package hazards), not in the source it emitted it from.
+#
+# The suite itself covers the v1/v3/v4/v5/v6/v7 generators against the RFC test
+# vectors plus parse/stringify/validate round trips.
+test:
+  - name: build-and-test
+    run: npm ci && npm test