diff --git a/k8s/discover/kustomization.yaml b/k8s/discover/kustomization.yaml
index 776773a..89485bb 100644
--- a/k8s/discover/kustomization.yaml
+++ b/k8s/discover/kustomization.yaml
@@ -64,13 +64,21 @@ configMapGenerator:
 
 # The base image `tidaldb:deploy` is the LOCAL kind-loaded tag and would
 # ImagePullBackOff on a real cluster. Pinned to the current published amd64
-# PLATFORM-manifest digest (tag m12-poisonfix-20260831), the same image the live
+# PLATFORM-manifest digest (tag m12-agesort-20260901), the same image the live
 # cluster set runs (k8s/cluster/statefulset.yaml:103). One image serves every
 # subcommand; the StatefulSet's `standalone` args select the mode.
+#
+# Bumped from m12-poisonfix-20260831 (sha256:93a2929d) because THIS profile is
+# the reason the age-aware ranking work exists: on that older image `score_hot`
+# read no `created_at` at all and `Sort::New` scored by raw entity id, so
+# deploying discover against it would reproduce exactly the limitation the
+# `NO sort:` block in schema.yaml documents. Necessary but NOT sufficient —
+# cold-start still ties, because hot's `log10(max(views,1))` numerator is
+# exactly 0.0 at 0 or 1 views. See that block's STATUS: PENDING RE-MEASUREMENT.
 images:
   - name: tidaldb
     newName: registry.threesix.ai/tidal/server
-    digest: sha256:93a2929d2473c753ed2322aac547dcc5a2d8598fd00aada5104553d7b8632078
+    digest: sha256:9234aacb197a275a67d1c1c8fbadb108e626aa48a779d4c653ad6109cda3df5a
 
 labels:
   # Mirrors the label k8s/kustomization.yaml applies to the base set.