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,19 @@
+# Canonical CI/CD config for hanzoai/openid-client — read by the hanzoai/ci
+# reusable workflow (.hanzo/workflows/cicd.yml) and by platform.hanzo.ai.
+#
+# LIBRARY: an OAuth 2 / OpenID Connect client. No image, no deploy — it ships
+# from a tag.
+#
+# The gate is the ava suite under test/, which is the right one for a protocol
+# client: every case stands up an undici MockAgent with `disableNetConnect()`
+# and asserts on the exact bytes of the request and the handling of the
+# response — DPoP proofs, PAR, DCR, decryption, issuer checks. It is hermetic
+# (no OP is contacted) and it fails on a semantic change a type-check cannot
+# see, which is the only kind of bug that matters in an auth client.
+#
+# `npm clean-install`, not `npm install`: the lockfile is what the published
+# package is built against, and a gate that silently floats its own
+# dependencies is testing a tree nobody ships.
+test:
+  - name: test
+    run: npm clean-install && npm test