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: [master]
+    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/cookie-parser — read by the hanzoai/ci
+# reusable workflow (.hanzo/workflows/cicd.yml) and by platform.hanzo.ai.
+#
+# LIBRARY: Express cookie-parsing middleware. No image, no deploy — it ships
+# from a tag.
+#
+# The gate is the mocha suite. The part that has to be tested is the SIGNED
+# cookie path: this middleware decides whether `s:value.signature` verifies
+# against the app's secret, supports secret rotation via an array, and must
+# leave the cookie in `req.cookies` rather than `req.signedCookies` when the
+# signature does not check out. Getting that backwards is silent — the request
+# still works, it is just trusting an attacker-supplied value — and only the
+# suite can tell the two apart.
+#
+# `npm install`, not `npm ci`: this repo ships no package-lock.json.
+test:
+  - name: test
+    run: npm install && npm test