memory: providers.yaml summarization pre-sync DONE (#384/#385 b168)

Synced the boot-gating summarization block + deep-reasoning desc to demo +
personal via deploy-wt-config (health-gated); replied GO. Recorded gotchas:
unpushed-commit fetch falls back to default branch (verify SHA exists), and
paste-sourced YAML needs indent/validate (8-space desc was invalid).

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; **#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). **PENDING providers.yaml pre-sync (2026-08-03):** the #384/#385 train adds a NEW `summarization` capability block (provider `vastblueai-gateway`, model `gen`, non-thinking, temp 0.5, max_tokens 8192, inserted after `classification`) that the in-image `agents/muninn/config.yaml` references → **boot-blocking** if an instance's bind-mounted providers.yaml lacks it. BEFORE the image deploy lands, sync the block into `/opt/worldtree-*/config/providers.yaml` on **demo AND personal** via `deploy-wt-config` — from the EXACT commit worldtree-dev sends on thread `01KZ2JPRQ0DG` (not the prose), then confirm present on both before they deploy. ACKed `01KZ2JS14EWF3Z1V3ZANHXW0V9`. (No other providers.yaml changes in the train; the stale "Mistral Small 4" deep-reasoning description is theirs to fix repo-side — mapping gen-reasoning→heretic-thinking is correct by design.)
+**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). **providers.yaml pre-sync DONE (2026-08-02):** #384/#385 b168 (commit 293f8f3) needed a boot-gating `summarization` capability block (vastblueai-gateway/gen, non-thinking, temp 0.5, 8192, after `classification`) + a deep-reasoning description refresh. Synced BOTH hunks into demo + personal `providers.yaml` via `deploy-wt-config` (health-gated, both api healthy ~18-21s); instance-configs repo commit `53349f8`; replied GO (`01KZ2NMER3EP78X95CMZGP76BK`) → they push main (demo auto-deploy) + cut personal staging tag. **GOTCHAS for next time:** (1) the source commit was UNPUSHED at sync time — `git show <sha>` 404s and a gitea `raw?ref=<sha>` silently falls back to the default branch; verify the commit exists before trusting a fetch, else ask the peer to paste hunks. (2) worldtree-dev's hunk paste indented the deep-reasoning `description:` at 8 spaces but the block keys are 4-space → invalid YAML; corrected to 4-space (always YAML-validate after a paste-sourced edit). **deploy-wt-config runbook:** `diff`/`deploy <inst> --file providers.yaml` (repo `~/development/worldtree-instance-configs`, per-instance dirs demo/personal/pinned; deploy = host write + api/matrix restart + 90s health-gate + auto-rollback); demo+personal providers.yaml are byte-identical. See [[reference_worldtree_instance_configs_repo]].
 
 **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).