rename: homelab-gateway → telegram-gateway

Aligns the project name with the public URL (tg.arcodange.fr) and the
Arcodange organization conventions. The 'homelab-gateway' name was too
generic.

Touches: chart name + helpers, image registry path, Go module path,
secret/configmap names, deployment mountPath, all docs.

README.md

@@ -1,4 +1,4 @@
-# homelab-gateway
+# telegram-gateway
 
 Telegram **webhook gateway** for the Arcodange home lab. Replaces polling-based
 bots (e.g. those scheduled in Cowork) with direct webhook delivery from
@@ -13,7 +13,7 @@ See the design doc at `~/.claude/plans/pour-les-notifications-on-inherited-seal.
 ## Architecture (current)
 
 ```
-Telegram → Cloudflare Tunnel (tg.arcodange.fr) → Service homelab-gateway:8080
+Telegram → Cloudflare Tunnel (tg.arcodange.fr) → Service telegram-gateway:8080
         → /bot/<slug> → secret_token check → handler dispatch → Bot API sendMessage
 ```
 
@@ -55,19 +55,19 @@ make deletewebhook SLUG=factory
 ## Configuration
 
 - **Routing** (non-secret): YAML at `$CONFIG_PATH` (default
-  `/etc/homelab-gateway/bots.yaml`, mounted from a ConfigMap in cluster).
+  `/etc/telegram-gateway/bots.yaml`, mounted from a ConfigMap in cluster).
 - **Secrets**: per-bot env vars `BOT_<UPPER_SLUG>_TOKEN`,
   `BOT_<UPPER_SLUG>_SECRET`. Sourced from Vault path
-  `kvv2/homelab-gateway/config` via Vault Secrets Operator.
+  `kvv2/telegram-gateway/config` via Vault Secrets Operator.
 
 ## Cluster deploy
 
-- Image: `gitea.arcodange.lab/arcodange/homelab-gateway:<tag>`
+- Image: `gitea.arcodange.lab/arcodange/telegram-gateway:<tag>`
 - Helm chart: `chart/`
-- ArgoCD app: `homelab-gateway` (in `factory/argocd/values.yaml`)
+- ArgoCD app: `telegram-gateway` (in `factory/argocd/values.yaml`)
 - Public URL: `https://tg.arcodange.fr` (Cloudflare déjà configuré pour
   router `*.arcodange.fr` vers le home lab → Traefik route par Host)
-- Secrets Phase 1 : `kubectl create secret generic homelab-gateway-bots …`
+- Secrets Phase 1 : `kubectl create secret generic telegram-gateway-bots …`
   (sans Vault). Migration vers Vault Secrets Operator en Phase 2+ via
   `vault.enabled: true` dans `chart/values.yaml`.