git.hanzo.ai is the forge and act_runner is what executes here; .hanzo/workflows
is where it looks. A workflow under .github/ on this forge does not fail — it
queues, indefinitely, while reading as configured CI, which is the failure mode
worth avoiding. The runners were already right (runs-on: lux-build-amd64); only
the path was not.
.hanzo/actions/kms-action goes with them: it is CI machinery, and the three
workflows that named it by its old path were the kubectl ones.
.github/hero.svg stays. It is the README's banner and a forge profile asset, not
a workflow.
Co-authored-by: Hanzo Dev <[email protected]>
zeekayandHanzo Dev
3007b77670