Soften the tone of the docs and comments written today

docs/adr/0002-argocd-gitops.md

@@ -2,7 +2,27 @@
 
 ## Status
 
-Accepted
+**Accepted — still the target, not yet implemented.** Not superseded by the
+current production setup.
+
+Since 2026-08-10 the project has a *different*, interim deployment: a single
+EC2 box running `infra/docker/docker-compose.prod.yml` behind Caddy, deployed
+by `.github/workflows/deploy.yml` over SSH. That was built to get a working
+demo online, not to replace this decision. Migrating to the team's Kubernetes
++ ArgoCD remains planned work, and the expensive prerequisite — containerising
+both apps — is already done, so the Dockerfiles and compose services port over.
+
+Two things must still happen and neither has been started:
+
+1. **Repository move to the team's self-hosted Gitea** (company domain), which
+   is where the GitOps repo is meant to live. The project stays on private
+   GitHub until that move is deliberately made. Note the hard boundary already
+   in force: the team's existing `git.vinmec.tech/ai-team/gitops` repository is
+   **reference-only** — never push this project into it.
+2. **Filling in the scaffolds this ADR assumes exist.** `infra/helm/medical-chatbot/templates/`
+   and `infra/k8s/**` are empty (`.gitkeep` only), the chart is version `0.0.0`,
+   and every `infra/argocd/applications/*/app.yaml` still carries unresolved
+   TODOs for project, repo URL and destination cluster.
 
 ## Context