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,24 @@
+# Canonical CI/CD config for hanzoai/cc (tweakcc) — read by the hanzoai/ci
+# reusable workflow (.hanzo/workflows/cicd.yml) and by platform.hanzo.ai.
+#
+# LIBRARY: a CLI published to npm. No image, no deploy — it ships from a tag.
+#
+# The gate is the repo's own two commands, in the order its own CI runs them:
+#   lint  = `tsc --noEmit && eslint src`   (types first, then rules)
+#   test  = `vitest run`
+# Both are needed. This tool rewrites another program's bundled source by
+# pattern-matching it, so the type-check catches the refactor break and the
+# vitest suite catches the patterns quietly ceasing to match — a failure the
+# compiler cannot see, because a regex that matches nothing is well-typed.
+#
+# pnpm is installed explicitly instead of via corepack: package.json declares
+# no `packageManager` field, so the corepack shim has no version to activate
+# and resolves to whatever it feels like. The lockfile is v9, which pnpm 10
+# reads and writes natively.
+test:
+  - name: lint-and-test
+    run: |
+      npm install -g pnpm@10
+      pnpm install --frozen-lockfile
+      pnpm lint
+      pnpm test