stop declaring an image this copy does not own

Its 3 unique commits are carried into `hanzoai/bootnode` first — merged onto the default branch or pushed there as `carry/*` refs — so nothing here is lost. This copy has no push mirror, so those commits had reached nothing.

hanzoai/bootnode keeps ghcr.io/hanzoai/bootnode.

hanzo.yml

@@ -1,49 +0,0 @@
-# Hanzo CI/CD — one declarative build + test config.
-#
-# Read by platform.hanzo.ai, the sole orchestrator for this repo. On every
-# push / PR the platform GitHub App delivers the event to platform, which reads
-# THIS file and builds each image on the shared in-cluster `hanzo-build-*`
-# arcbuild pool (bootnode has no self-hosted runners of its own — the reason the
-# old GitHub-Actions `.github/workflows/cicd.yml` dead-ended and was removed).
-# Registry credentials live in the cluster (kaniko-ghcr), never in GitHub.
-#
-# Images publish to ghcr.io/bootnode/bootnode as `<sha>-amd64-<tag-suffix>`.
-# Rollout is GitOps, not platform: luxfi/universe pins the freshly-built tag and
-# Argo applies it. The `deploy:` block below is therefore advisory (platform
-# treats the Deployment-style `services:` form as build-only).
-
-images:
-  - name: api
-    context: ./api
-    dockerfile: ./api/Dockerfile
-    repo: ghcr.io/bootnode/bootnode
-    tag-suffix: api
-  - name: web
-    context: ./console
-    dockerfile: ./console/Dockerfile
-    repo: ghcr.io/bootnode/bootnode
-    tag-suffix: web
-  # The Lux fleet API: pure Go, built from the repo-root module. Hanzo repos
-  # publish to ghcr.io/hanzoai — the two entries above are the legacy refs the
-  # running bootnode Deployments still pull.
-  - name: fleet
-    context: .
-    dockerfile: ./Dockerfile.fleet
-    repo: ghcr.io/hanzoai/bootnode
-    tag-suffix: fleet
-
-# Commands run on the arc runner after the image builds. Non-zero fails the run.
-test:
-  - name: api
-    run: >-
-      docker compose -f compose.yml up -d postgres redis >/dev/null 2>&1;
-      cd api &&
-      DATABASE_URL=postgresql+asyncpg://bootnode:bootnode@localhost:5432/bootnode
-      JWT_SECRET=ci API_KEY_SALT=ci
-      uv run pytest -q --tb=short
-
-# KMS source for /deploy secrets (GHCR_TOKEN, KUBECONFIG). workspace + endpoint
-# are supplied as repo vars so this file carries no secrets.
-kms:
-  path: /deploy
-  environment: prod