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,17 @@
+# Canonical CI/CD config for hanzoai/cookie — read by the hanzoai/ci reusable
+# workflow (.hanzo/workflows/cicd.yml) and by platform.hanzo.ai.
+#
+# LIBRARY: HTTP cookie serialize/parse. No image, no deploy — it ships from a tag.
+#
+# `npm ci && npm test` is exactly what this repo's own CI runs, and `test` here
+# is two things, both of which belong in a merge gate:
+#   - `ts-scripts test` — the vitest suite: RFC 6265 parsing edge cases, the
+#     attribute serializer, and the encode/decode round trip. A cookie parser
+#     fails by accepting one byte too many, which only a test can see.
+#   - `npm run size` — size-limit against dist/index.js, capped at 1.4 KB.
+#     That is a real gate for a library this small: it is a dependency of
+#     effectively every Node HTTP stack, so a transitive dependency sneaking
+#     in shows up as bytes before it shows up as anything else.
+test:
+  - name: test
+    run: npm ci && npm test