Stop the slugifier from deleting the letter D-stroke

infra/helm/medical-chatbot/values-production.yaml

@@ -53,19 +53,21 @@ aiService:
     answerModelId: qwen.qwen3-next-80b-a3b
     rerankEnabled: true
 
-# Auth rollout (2026-08-18): stays OFF here for now. Flipping these on
-# without secret.jwtSecret already present inline on the live Application
-# breaks ArgoCD's render for the WHOLE Application (not just these two
-# services) — it did, on the first attempt, and blocked the routine
-# ai-service/web image sync along with it. Add secret.jwtSecret inline on
-# the Application first (same way secret.grafanaAdminPassword already
-# works — see infra/argocd/applications/medical-chatbot-app.yaml), confirm
-# ArgoCD picks it up, THEN flip these to true in a follow-up commit.
+# Auth is live in production (2026-08-19). These stayed false here for a day
+# while the live Application carried `enabled: true` inline, so Git and the
+# cluster disagreed and the cluster silently won — recreating the Application
+# from Git would have turned auth off without a word. They now match.
+#
+# secret.jwtSecret is deliberately still absent: it is a real credential and
+# lives inline on the Application, the same way secret.grafanaAdminPassword
+# does. The chart fails closed via `required` if it is ever missing while
+# either service below is on — which is exactly what took the whole render
+# down on the first attempt (2026-08-18). Set the secret first, always.
 authService:
-  enabled: false
+  enabled: true
 
 apiGateway:
-  enabled: false
+  enabled: true
 
 observability:
   grafana: