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.

persistent-memory.md

@@ -33,6 +33,7 @@ Sister repos (separate gitea repos, deployed by playbooks here):
 | `vh/Worldtree` | Conversation API (corviduo-dev demo :8080 / personal :8081 / pinned :8082) — Heimdall auth, Bifrost integration. **gitea-runner builds on ana-docker**; claude-bot ADMIN collaborator (2026-06-20). Now v1.0.0b19. | push-to-main → CI build-and-deploy (runner on ana-docker) |
 | `vh/yt-voice-clipper` | YouTube → diarized voice-clip dataset builder + audition console (irv-ml1 :8000) | push-to-main → **gitea-webhook auto-deploy** to irv-ml1 (2026-06-03) — see `docs/runbooks/ytvc-autodeploy.md` |
 | `vh/arbo` | Catalog-driven ComfyUI engine (irv-ml1 :8201, comfy-dev owns engine/catalog/image) | push-to-main → gitea Actions CI (deploy-engine.sh, build-local, health-gated) now LIVE; catalog via :9009 webhook |
+| `vh/zonos-gateway` | OpenAI-compatible TTS gateway over stock ZONOS2 (`:8890` irv-ml1); emotion **dials-first** + voice mapping; reached via LiteLLM `ext-tts` alias | **stood up 2026-07-17** (private; internal SSH); NOT yet CI-wired — deployed `~/zonos-gateway` tree on irv-ml1 imported as the initial commit; CI + deploy key = open follow-up. Dials-first emotion spec at `docs/EMOTION-DIALS-SPEC.md` |
 | `model-training-forge` (mtf-dev) | Fine-tuning recipe forge; **T1 = E-RP writing LoRA, retargeted qwopus-122B→AEON-27B (2026-07-06)** (SFT→DPO, LitBench-RM reward) | training runs, not a deployed sidecar |
 
 (`vh/volva` + Heid were re-architected from systemd daemons to Claude Code

stacks/zonos-gateway/EMOTION-DIALS-SPEC.md

@@ -134,7 +134,8 @@ degrade, worse under emotion steering. Register a reusable voice via
   §3 (carry the "deaf by 1.5" warning; no clamp added — no cap by ruling). Trim
   the in-code `PRESETS` to a couple of examples (or drop) once current `preset:`
   usage in asset-engine / gateway-chat is confirmed.
-- **Version control:** the gateway source lives only on irv-ml1 (`~/zonos-gateway`,
+- **Version control:** DONE (2026-07-17) — `vh/zonos-gateway` stood up on gitea
-  not in gitea) — stand up `vh/zonos-gateway` so this spec + the code are tracked
+  (private); this spec's canonical home is now `docs/EMOTION-DIALS-SPEC.md` in
-  together. This spec currently lives in the eshpfi mirror as the version-controlled
+  that repo (the eshpfi copy is a mirror). Remaining: git-connect / CI-wire the
-  home until then.
+  deployed irv-ml1 working tree (build + deploy on push, like the other sister
+  services) with a deploy key.

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/`,
+- **Source (versioned 2026-07-17):** [`vh/zonos-gateway`](http://10.250.50.70:3000/vh/zonos-gateway)
-  its own `pyproject.toml` + `ROADMAP.md` + `persistent-memory.md`) and is **NOT
+  on gitea (private; internal SSH `ssh://git@10.250.50.70:222/vh/zonos-gateway.git`).
-  yet in gitea** — a real version-control/backup gap. This eshpfi dir mirrors
+  The dials-first emotion spec lives there at `docs/EMOTION-DIALS-SPEC.md`. This
-  the *stack* (compose + env + docs), not the source; the source needs its own
+  eshpfi dir mirrors the *stack* (compose + env + docs). **Note:** the deployed
-  gitea repo (follow-up).
+  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