memory: #381 restart DONE — fiction wing retrieval-visible on personal

DCC job mimir-6351554e8e8f complete; restarted worldtree-personal-worldtree-api-1
(healthz/readyz 200); Mimir search_library on wings=[fiction] returns 10 DCC hits
(retrieval visibility confirmed, not grounding — ratatoskr runs grounding verify).
Recorded the Mimir-session probe runbook (SSE stream, tool-events).

persistent-memory.md

@@ -122,7 +122,7 @@ _As of 2026-08-02 — **session at a natural close; nothing infra-ops-side block
 
 **Zonos voice stack (LIVE):** **9 voices** in `zonos-gateway` (`:8890` irv-ml1) — defaults AmericanFemale/Male/BritishFemale/Cora + 4 clones Emmie/Penny/Natalie/Miranda + **donut** (2026-08-02, from the 65-frost bundle, **expanded same day with onyx-58 clips → 52.0s multi-clip ref**); add a voice = drop `<Name>.wav` (44.1kHz mono s16 PCM) in `/opt/docker/compose/zonos-gateway/voices/` + `docker compose restart` (host-managed bind-mount, NO rebuild; registry scans at startup). Also mirror into the build-source tree `~/zonos-gateway/voices/` for rebuild-durability. Clone pipeline: `/mnt/smithy/voice_clones/<name>.zip` → `assemble_voice.py` → drop. Dial-in studio http://10.100.10.50:8898/ (nohup on nh3-dev, relaunch `nohup python3 ~/development/zonos-tools/dial-in-studio.py >/tmp/zonos-studio.log 2>&1 &`).
 
-**althing monitor** ARMED (handle `infra-ops`; herald up; wake-listener task-id rotates every re-arm). ⚠️ Re-arm ONLY after an actual FIRE (`<task-notification> completed rc0`), never after a plain operator turn (bounces rc3). Spawn `althing-wake-listener` as its OWN `run_in_background` task — NEVER chain with `&`/`&&` (orphans it → untracked → mail unwatched; I fumbled this ~4× this session, each time = stop-monitor + re-arm clean). **Open watches:** worldtree-dev may ping when their `/embed` code fix reaches PERSONAL (still 503 on b146 until a staging promotion — operator's call); #363 research-wing ingest PARKED; **PENDING #381 restart (2026-08-02):** worldtree-dev will request the standing restart of `worldtree-personal-worldtree-api-1` (corviduo-dev) when DCC re-ingest job `mimir-6351554e8e8f` (fiction wing, multi-hour) goes terminal — I ACKed no scheduling constraints on thread `01KZ229N5Q2Y`; on their terminal-state signal, plain-restart the container (NO `compose up`/image repoint) then confirm the fiction wing is visible before they run the downstream verify.
+**althing monitor** ARMED (handle `infra-ops`; herald up; wake-listener task-id rotates every re-arm). ⚠️ Re-arm ONLY after an actual FIRE (`<task-notification> completed rc0`), never after a plain operator turn (bounces rc3). Spawn `althing-wake-listener` as its OWN `run_in_background` task — NEVER chain with `&`/`&&` (orphans it → untracked → mail unwatched; I fumbled this ~4× this session, each time = stop-monitor + re-arm clean). **Open watches:** worldtree-dev may ping when their `/embed` code fix reaches PERSONAL (still 503 on b146 until a staging promotion — operator's call); #363 research-wing ingest PARKED; **#381 restart DONE (2026-08-02):** DCC job `mimir-6351554e8e8f` completed (145 sections/97 concepts, wing=fiction); restarted `worldtree-personal-worldtree-api-1` (plain restart, healthz/readyz 200 ~28s); confirmed retrieval-visibility via a Mimir session — `search_library` on `wings:["fiction"]` returned 10 DCC/Princess-Donut hits (fresh Chroma client sees the new writes). Scoped as RETRIEVAL, not grounding (thread `01KZ229N5Q2Y`, replied); grounding verify handed to ratatoskr-dev. **Runbook confirmed:** admin token (`~/.config/worldtree/personal-admin-token`, wildcard scope) → Mimir session (agent_id=`mimir`, `record_tool_intermediates=true`) → post message → read `/sessions/{id}/tool-events` + parse SSE `tool_result` → DELETE session. Message endpoint STREAMS SSE (not JSON).
 
 **Two small pending items (operator's call, non-urgent):** (1) bless/reshape the `env.public` non-secret-env-overlay mechanism in the config repo; (2) the pre-existing herald pane-route errors on `worldtree-codex` + `eitri-smithy-dev` ("route-error: list index out of range" — likely `render_command messages[0]` on empty list; NOT infra-ops's, rec = flag to althing-dev).