Files
engine/hanzo.yml
wbin90620andClaude Opus 5.5 5d42e6437e fix(ci): make hanzo.yml parse again
The kv-isolation gate's command ended in `tenant::`, and a colon at the end
of a plain YAML scalar starts a mapping, so hanzo.yml stopped parsing and the
first forge run failed reading it before any gate ran. Filter on
`tenant::tests`, which selects the same four tests and needs no quoting.

Co-Authored-By: Claude Opus 5.5 <[email protected]>
2026-11-19 20:41:24 -08:00

44 lines
2.0 KiB
YAML

# Canonical CI/CD config for hanzoai/engine — read by the hanzoai/ci reusable
# (.hanzo/workflows/cicd.yml) and by platform.hanzo.ai.
#
# The Zen inference engine: a 23-crate Rust workspace.
#
# The image is declared at the end of this file and built by the build door;
# it is the Dockerfile's one builder. The GPU/FFI/release lanes sit beside it.
#
# `rustup component add rustfmt` first: the toolchain this workflow provisions
# (dtolnay/rust-toolchain@stable) installs the compiler ALONE, so `cargo fmt`
# dies with "'cargo-fmt' is not installed for the toolchain" before reading a
# line of code — a red run that says nothing about the repo. ci.yml buys this
# with `components:` on the toolchain action; the provision step above is not
# ours to configure, so the gate buys it itself. It is idempotent.
#
# The gates are the repo's own (.hanzo/workflows/ci.yml), cheapest first: fmt
# is seconds and catches what needs no compiler, then a full type-check of every
# member. `cargo check` — not `cargo build` — because nothing here consumes a
# binary; the question this gate asks is whether the workspace still compiles.
test:
# Every first-party path is /v1/...; a quoted "/api/" or a joined `}api/`
# outside Markdown (prose that cites third-party APIs) is a regression.
- name: v1-only
run: |
! git grep -nE -e '["(`]/api/' -e "'/api/" -e '}api/' -- ':!*.md' ':!hanzo.yml'
- name: fmt
run: rustup component add rustfmt && cargo fmt --all -- --check
# Prefix-cache tenant isolation: no request decodes against another tenant's KV or against KV no
# forward wrote. A security boundary, so it runs before the workspace-wide check, which a crate
# it does not build could turn red.
- name: kv-isolation
run: cargo test -p hanzo-engine -p hanzo-server-core --lib -- kv_isolation tenant::tests
- name: check
run: cargo check --workspace
# Built by the build door, one BuildKit Job per platform.
images:
- name: engine
context: .
dockerfile: Dockerfile
repo: ghcr.io/hanzoai/engine
platforms: [linux/amd64]