skald (engine/kokoro): public release prep — AGPL-3.0, generic config, engine-variant README

engines/README.md

@@ -35,24 +35,23 @@ generalise. Examples:
   question intonation, paragraph/scene/breath gap durations tuned
   for af_heart's pacing, notes on how respellings need to be all-
   lowercase to avoid letter-by-letter spell-out by misaki.
-- `engine/tortoise` — GPU exclusivity coordinator (stops F5 +
-  Kokoro before a Tortoise run since the 2070 Super can't host
-  all three at once), preset choice ergonomics, character→tortoise-
-  voice seed assignments.
+- `engine/tortoise` — sentence chunking, device selection, and
+  pitch/rate modulation tuned for Tortoise's audiobook-quality
+  output. On an 8GB card Tortoise wants the GPU largely to itself,
+  so run it when the other engines are stopped.
 
-When deploying an engine to the host, the build dir at
-`/srv/appdata/<engine>/build/` tracks the engine's branch:
+To deploy a tuned engine, check out the engine's branch in the build
+dir and `docker compose up -d --build`:
 
 ```bash
-cd /srv/appdata/kokoro/build
 git fetch && git checkout engine/kokoro
-docker compose -p <name> up -d --build
+docker compose up -d --build
 ```
 
-## GPU coordination (2070 Super)
+## GPU coordination
 
-The 8GB card is the bottleneck. F5 + Kokoro can co-reside (~5GB +
-~1GB). Tortoise pushes the budget over and needs the GPU largely
-to itself — the `engine/tortoise` branch will carry the script
-that stops kokoro + f5 before a tortoise run and restarts them
-after. Replace with proper coordination once we have more VRAM.
+On an 8GB card F5 + Kokoro can co-reside (~5GB + ~1GB). Tortoise
+pushes the budget over and needs the GPU largely to itself — stop
+kokoro + f5 before a Tortoise run and restart them after, or give
+Tortoise its own card. Proper multi-engine coordination is left to
+the deployment once more VRAM is available.