Rename back to catalogue-agent; stop owning the shared namespace

catalog-agent was one rename too aggressive: 'catalogue' is accepted, and the
Keycloak client, its audience scope and the Vault key that names it were never
renamed to match — leaving an inconsistency between what Kubernetes and
Keycloak call the same agent. Keycloak carries more weight to move, so this
side moves back.

k8s/namespace.yaml is out of this Kustomization's inventory. It was in
2026-08-31 when renaming the Kustomization pruned the old one — which owned
the namespace three agents share — and took all three down. A namespace shared
across repos should not be owned by any one of them.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>

k8s/configmap.yaml

@@ -1,10 +1,10 @@
 # Everything here is an endpoint or a public identifier. The one secret the
-# agent holds arrives through catalog-agent-secrets; nothing in this file is
+# agent holds arrives through catalogue-agent-secrets; nothing in this file is
 # sensitive, which is the point of keeping the split visible.
 apiVersion: v1
 kind: ConfigMap
 metadata:
-  name: catalog-agent-config
+  name: catalogue-agent-config
   namespace: agents
 data:
   CATALOGUE_KEYCLOAK_REALM_URL: https://keycloak.sttlab.local/realms/classic-models
@@ -23,7 +23,7 @@ data:
   # What other agents dial, so it is the Service DNS name and not the bind
   # address. It is advertised in the Agent Card; get it wrong and A2A callers
   # are pointed at nothing.
-  CATALOGUE_PUBLIC_URL: http://catalog-agent.agents.svc.cluster.local:8080/
+  CATALOGUE_PUBLIC_URL: http://catalogue-agent.agents.svc.cluster.local:8080/
   # The peer's Service name, overriding the default in config.py — set here so
   # the rename took effect without rebuilding an image.
   CATALOGUE_SUPPLY_URL: http://supply-agent.agents.svc.cluster.local:8080/