chore(augaman): remove the fv-ml1 instance (Prime)

Prime removed the second instance after the v0.1.3 bench. esh-ml1 handles a face
in ~48 ms, sits in the house next to the cameras, and holds the verified
backup. fv-ml1's gallery was empty (0 identities). The container, gallery volume,
image, compose dir (with its .env), backup dir and build sources are removed from
fv-ml1. GPU_ID / CARD_SUFFIX stay in the compose for any future second host.

servers/fv-ml1/README.md

@@ -180,14 +180,9 @@ embed/rerank/reward trio. GPUs are pinned per container via
 **GPU 1 — light / eval / retrieval + char-RP GGUF (~91/98 GB, on-demand):**
 
 > ⚠ **This table is stale (checked 2026-09-27).** Live GPU 1 residents were `scriberr`,
-> `vllm-coder`, `vllm-erp-seat`, `vllm-meromero-rp` and now **`augaman`** (below). Read the
-> host (`docker inspect … DeviceRequests`), not this table.
->
-> **`augaman` :8040 (since 2026-09-27, Prime):** the second instance of the face-recognition service
-> (`stacks/augaman`, `GPU_ID=1`), ~1.3 GB. **Fixtures-only: it has no gallery backup wired.**
-> The primary instance, which holds the gallery and its backup, is on esh-ml1. Note that this host's restic copies
-> `/var/lib/docker/volumes` raw, and that includes `augaman_gallery`: a live SQLite file, so the copy is
-> not guaranteed consistent. That is acceptable for fixtures and not for real faces.
+> `vllm-coder`, `vllm-erp-seat` and `vllm-meromero-rp`. Read the host
+> (`docker inspect … DeviceRequests`), not this table. (A fixtures-only `augaman` instance ran
+> here for about an hour on 2026-09-27 for a speed bench, and was then removed on Prime's call.)
 
 | Container | Port | Served model | Quant | Ctx |
 |-----------|------|--------------|-------|-----|