Retire the status page nothing routes to

status.zoo.network is served by zoo/status, which is healthy. This copy in
zoo-mainnet has no route, and it has been unready since the migration waiting
on a status-config ConfigMap that no file produces.

Co-authored-by: Hanzo Dev <[email protected]>

deploy/zoo-mainnet/status.yaml

@@ -1,50 +0,0 @@
-# Generated from the live zoo-mainnet/status Deployment on do-sfo3-zoo-k8s
-# by hack/live2values.py. Live is the source: a repo of hand-applied
-# manifests has unknown currency, the running fleet does not.
-replicas: 1
-selectorLabels:
-  app: status
-image:
-  # ghcr.io/hanzoai/status is the one status binary this estate runs, pinned to a
-  # release. This ran an upstream build on a floating `latest` instead, so what
-  # shipped changed whenever someone else cut a release, and it carried no Zoo
-  # mark — the BRAND env that sat below was read by nothing.
-  repository: ghcr.io/hanzoai/status
-  tag: v1.1.17
-  digest: sha256:99148611743671c3bd2e13c4861c63149ec8b48aaacc947fdb62ee5ccb2951cb
-  pullPolicy: IfNotPresent
-env:
-# The mount is absolute; the binary's default is the relative config/config.yaml,
-# so name the path rather than depend on the working directory.
-- name: GATUS_CONFIG_PATH
-  value: /config/config.yaml
-resources: {}
-volumeMounts:
-- mountPath: /config/config.yaml
-  name: config
-  subPath: config.yaml
-ports:
-- containerPort: 8080
-volumes:
-- configMap:
-    name: status-config
-  name: config
-rollingUpdate:
-  maxSurge: 25%
-  maxUnavailable: 25%
-topologySpread:
-  enabled: false
-lifecycle: null
-terminationGracePeriodSeconds: 30
-defaultReadinessProbe: false
-imagePullSecrets: []
-
-# The image for this workload is published for linux/amd64 only, and this
-# cluster has an arm64 node. Unpinned, the scheduler is free to place it on
-# spark, where the kubelet refuses the pull with `no match for platform in
-# manifest` -- which reads as a broken image and is a misplaced pod. Measured
-# 2026-09-09: zoo-ui, zoo-gym, zoo-bot and zoo-build had all been sitting in
-# ImagePullBackOff on spark. Pin follows the artifact: an image that exists for
-# one architecture may only be scheduled where that architecture is.
-nodeSelector:
-  kubernetes.io/arch: amd64