feat(hermes): enable svos_miranda live; retire irv parakeet and voice-studio

Four operator rulings executed.

svos_miranda is live in Hermes. Gateway restarted 02:10 (PID 3107822 -> 3901622,
confirmed by observing the change). /v1/toolsets now reports 29 rows including
svos_miranda, and an api_server session resolves to exactly the 8 plugin tools
with the write-klass five absent.

agent.disabled_toolsets stays off permanently: 'i dont want the tools disabled
everywhere'. That key is a global end-of-pipeline subtraction rather than an
api_server-scoped one - measured, a default session goes 46 tools to 20 - and it
is unnecessary anyway, since platform_toolsets.api_server alone produces the exact
8-tool surface. The operator's own session was verified intact at 46 tools after
the restart, which was the point of the ruling.

The consequence is now SVOS's to absorb: it must stop verifying against the global
roster before it restarts, because that roster is 29 by design and will not shrink.
Two workable options went to svos-dev - verify the api_server surface instead, or
relax the check to 'svos_miranda present and write-klass absent'. The second also
survives any unrelated plugin landing on this host, which matters because 'stt'
already appears in that endpoint's rows while resolving it logs 'Unknown toolset'.

irv parakeet retired: it lost tts-dev's bench to the FV seat at both clip lengths
and to whisper-large-v3 at 6.24s. Checked for consumers first - no gateway alias
pointed at it, and every other reference on that host was a comment in a
port-allocation register. Retirement banner on its README names the replacement.

voice-studio stopped: it existed for the dots mint loop and Breeze obsoleted dots
on 2026-09-06, so it was retired rather than repaired.

persistent-memory.d/2026-09-15-parakeet-stt-fv-ml1.md

@@ -105,8 +105,12 @@ that is where the `ext-tts` family lives, and it needs no gateway restart.
 
 ## Loose ends
 
-- The **irv-ml1 parakeet is still running** (healthz 200 on `100.64.0.6:8765`).
-  Two Parakeets now. Retiring the old one is the operator's call — not touched.
+- ✅ **irv-ml1 parakeet RETIRED 2026-09-15** (operator ruling, on tts-dev's bench
+  evidence). `docker compose down`; retirement banner prepended to its on-host
+  README naming the replacement. Checked for consumers first: **no gateway alias
+  pointed at it**, and every other `8765`/`parakeet` reference on that host was a
+  comment in a port-allocation register, not a dependency. Model files left on
+  disk at `/worktank/parakeet/models/` (regenerable). One Parakeet now.
 - `/opt/docker/compose/parakeet` and `/tank/parakeet` normalised to `root:docker
   2775`; the rest of fv-ml1's deploy tree is still `lkraven:lkraven` (it was not
   part of the 5-host normalisation).

persistent-memory.d/2026-09-15-svos-miranda-plugin-validation.md

@@ -59,7 +59,21 @@ expected refusal — which looked like the plugin's collision reading was wrong.
 was not: doctor's sandbox holds no built-ins, so nothing was claimed and **my
 positive case was not positive.** Reported as untested rather than as a finding.
 
-## ENABLED in config 2026-09-15 (operator-directed) — but NOT activated
+## ✅ LIVE 2026-09-15 02:10 — gateway restarted, plugin registered
+
+`GET /v1/toolsets` = **29 rows including `svos_miranda`**. An api_server session
+resolves to **exactly 8** tools, write-klass absent. Operator's default session
+verified **intact at 46** tools after the restart (memory / read_file / write_file /
+terminal / web_search / browser_exec all present) — the whole point of the ruling.
+
+⚠ **`agent.disabled_toolsets` stays OFF permanently** — operator: *"i dont want the
+tools disabled everywhere."* So **SVOS must stop verifying against the global
+`/v1/toolsets`** before it restarts: it will see 29 and refuse. Options put to
+svos-dev: (1) verify the api_server surface instead — recommended; (3) relax to
+"svos_miranda present AND write-klass five absent", which also survives any unrelated
+plugin landing on this host. Option 2 (accept the fleet-wide cost) is ruled out.
+
+## ENABLED in config 2026-09-15 (operator-directed)
 
 Installed to `~/.hermes/plugins/svos_miranda`; `plugins.enabled`, the settings block
 (dispatch key pulled from the vault, verified byte-equal), and
@@ -67,9 +81,8 @@ Installed to `~/.hermes/plugins/svos_miranda`; `plugins.enabled`, the settings b
 `config.yaml.bak-20260915-svos-miranda-enable`; diffed against it, only the intended
 non-comment lines changed. `hermes plugins list` → `svos_miranda enabled 0.1.0 user`.
 
-**The Hermes gateway was NOT restarted**, so the plugin is not live: the running
-process loaded its plugin set at 2026-09-14 12:35 and `/v1/toolsets` still reports 28
-without `svos_miranda`.
+Gateway restarted 02:10:17 PDT — PID 3107822 → 3901622, confirmed by **observing the
+change** rather than assuming it.
 
 ## ⚠⚠ `agent.disabled_toolsets` is GLOBAL — it would have cost 26 tools fleet-wide