docs(zonos-gateway): vh/zonos-gateway stood up in gitea (resolve not-in-gitea flag)

Created private vh/zonos-gateway on gitea, imported the previously-unversioned
~/zonos-gateway working tree (source + dials-first spec + voices). Updated the
stack README, spec §8, and the sister-repos table to point at the repo. Remaining
follow-up: CI + deploy key to wire the irv-ml1 deploy tree to the repo.

stacks/zonos-gateway/README.md

@@ -9,11 +9,14 @@ engine's** correct native `POST /tts/generate` path — while adding the
 - **Server:** irv-ml1 (Irvine, WireGuard-only), 3090.
 - **Deploy:** `/opt/docker/compose/zonos-gateway/compose.yaml` (fleet convention).
 - **Image:** `zonos-gateway:0.2.0`, `build: .` from the source tree.
-- **⚠️ Source:** lives at `~/zonos-gateway` on irv-ml1 (`src/zonos_gateway/`,
-  its own `pyproject.toml` + `ROADMAP.md` + `persistent-memory.md`) and is **NOT
-  yet in gitea** — a real version-control/backup gap. This eshpfi dir mirrors
-  the *stack* (compose + env + docs), not the source; the source needs its own
-  gitea repo (follow-up).
+- **Source (versioned 2026-07-17):** [`vh/zonos-gateway`](http://10.250.50.70:3000/vh/zonos-gateway)
+  on gitea (private; internal SSH `ssh://git@10.250.50.70:222/vh/zonos-gateway.git`).
+  The dials-first emotion spec lives there at `docs/EMOTION-DIALS-SPEC.md`. This
+  eshpfi dir mirrors the *stack* (compose + env + docs). **Note:** the deployed
+  working tree on irv-ml1 (`~/zonos-gateway`) was imported as the initial commit
+  but is not yet git-connected/CI-wired — future edits go through the repo, then
+  deploy to irv-ml1 (CI + deploy key is the open follow-up, like the other
+  sister services).
 
 ## Why it exists