The Lux and Hanzo explorers run v2.8.5-lux

v2.8.5-lux lists only chains that have an explorer: the SPC and Pars cards
linked names that do not resolve, and every page load asked api.pars.network
for validators and got 502. The Hanzo explorer was still on v1.1.30; it runs
the same image as Lux and Zoo now, from ghcr.io/hanzoai. The Lux testnet
explorer (explore-fe-lux-testnet, not declared here) runs the same image.

Co-Authored-By: Claude Opus 5.5 (1M context) <[email protected]>

deploy/lux-mainnet/explore-fe-hanzo.yaml

@@ -14,8 +14,8 @@ selectorLabels:
 containerName: explore
 image:
   repository: ghcr.io/hanzoai/explore
-  tag: v1.1.31
-  digest: sha256:1f8e1afd9dbe521c894df399df961e94279ef2eed198a543856e9497f006ee38
+  tag: v2.8.5-lux
+  digest: sha256:4f9d6435eb819262375a4e0903903127ddb6becd435e73b25b7d97277e9b868c
   pullPolicy: IfNotPresent
 labels:
   brand: hanzo

deploy/lux-mainnet/explore-fe-lux.yaml

@@ -14,7 +14,7 @@ selectorLabels:
 containerName: explore
 image:
   repository: ghcr.io/luxfi/explore
-  # v2.8.1-lux. This is the deployment that SERVES explore.lux.network — the
+  # v2.8.5-lux. This is the deployment that SERVES explore.lux.network — the
   # ingress points at explorer:80, and the Go explorer proxies the brand host
   # here. The `explore` sidecar inside the explorer pod is NOT the one on the
   # page; bumping it changed nothing visible, which is how this was found.
@@ -24,8 +24,8 @@ image:
   # every pin at v1.1.30. The hazard this file warns about is a pin BELOW what is
   # running, which applies itself as a rollback; this is the opposite, forward to
   # an image proven pullable in-cluster.
-  tag: v2.8.1-lux
-  digest: sha256:c4a75d036d7d7f93b870f7c1d3b9876b3b1c3e34063c11b90f68189554706193
+  tag: v2.8.5-lux
+  digest: sha256:4f9d6435eb819262375a4e0903903127ddb6becd435e73b25b7d97277e9b868c
   pullPolicy: IfNotPresent
 labels:
   brand: lux