hanzo.yml: drop the deploy: block, which no longer does anything

hanzoai/ci no longer has a deploy step. It cloned a universe repo that 404s,
wrote to a CR directory that universe deleted, and fell back to a kubectl patch
the cluster rejects — so this block has been declaring a rollout that never
happened.

What runs is declared in hanzo/universe, which cd.hanzo.ai reads and applies
within one poll. The build still publishes the image.

hanzo.yml

@@ -42,20 +42,6 @@ test:
       JWT_SECRET=ci API_KEY_SALT=ci
       uv run pytest -q --tb=short
 
-# Roll the freshly-built images onto the cluster. Only on the listed branches /
-# on v* tags. The operator (or kubectl, via the KMS kubeconfig) patches each
-# Service to the new image. Omit this block for build-only repos.
-deploy:
-  cluster: bootnode-k8s
-  namespace: bootnode
-  on:
-    - main
-  services:
-    - name: web3-platform-api
-      image: api
-    - name: web3-platform-web-bootnode
-      image: web
-
 # KMS source for /deploy secrets (GHCR_TOKEN, KUBECONFIG). workspace + endpoint
 # are supplied as repo vars so this file carries no secrets.
 kms: