Stop mislabeling the Compose box as production in read-only audits

.github/workflows/build-practice-images.yml

@@ -1,9 +1,11 @@
-name: Build and sync k3s practice images
+name: Build and sync k3s images
 
-# Practice-cluster only (readytochat.realvuxbaro.me, ArgoCD-managed on the
-# self-hosted k3s box). Does not touch deploy.yml or the production
-# EC2/Compose stack — production never pulls a GHCR image and isn't
-# ArgoCD-managed at all, so this workflow has no path to affect it.
+# This IS the production deploy path. `medical-chatbot-app` (ArgoCD, k3s) is
+# the same release behind both realvuxbaro.me and readytochat.realvuxbaro.me
+# since the 2026-08-17 cutover — there is no longer a separate "practice"
+# Application this workflow avoids touching. The Compose EC2 is unaffected
+# only because it has no CI/CD path left at all (deploy.yml/rollback.yml were
+# removed); it is a manual DNS fallback, not a deploy target.
 #
 # ArgoCD's Applications already autosync (syncPolicy.automated) — the gap
 # this closes is that the image tag they deploy was a static string