session 2026-08-24 addendum 2: trial IS running on multilingual-e5-small — prior addendum corrected

The plugin's progress panel confirms 'Using Xenova/multilingual-e5-small for embeddings'
(336/48233, 1729 tok/sec). Addendum 1 reported the opposite from smart_env.json, which
still read bge-micro-v2 in a file written 14s earlier — a persistence artifact with a
debounce, read as live state. Trial clock starts 2026-08-24, grade 2026-10-05.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01JQKeKY9T9d95KpvHwwok8T

claude/memory/session-2026-08-24-the-heap-got-a-dynamo.md

@@ -173,14 +173,16 @@ same move, and if they are not, the container is still missing.
 
 **Actionable resumption point (as of wrap — re-judge against what changed):**
 
-1. ⚠ **SUPERSEDED 12:23, AND THE NEWS IS BAD.** The steward restarted Obsidian and set
-   `Xenova/multilingual-e5-small` at the pane — but `.smart-env/smart_env.json`, **written 14
-   seconds before the check**, still records `TaylorAI/bge-micro-v2`, and the vault had already
-   embedded at 12:16 (110 MB). **The change did not take, and the vault holds English-only vectors.**
-   Possible cause: the config keeps `smart_sources.embed_model` separate from
-   `smart_chat_threads.chat_model` (the latter on `ollama`), so the wrong control is easy to set.
-   **FIRST MOVE: confirm the EMBEDDING model, verify that JSON line changed, confirm a re-embed.
-   The six weeks run from the first confirmed multilingual day, not from installation.**
+1. ✅ **RESOLVED 12:24 — the trial is running on the right model.** The steward deleted the previous
+   110 MB and re-set the model; the plugin's progress panel confirms *"Using
+   Xenova/multilingual-e5-small for embeddings"*, 336/48233. **Six weeks run from 2026-08-24; grade
+   2026-10-05.** ⚠ I had reported the opposite minutes before, from `smart_env.json` still reading
+   `bge-micro-v2` in a file written 14 seconds earlier. **A config file is a persistence artifact
+   with a debounce; it answers *what was last written*, never *what is running.*** The banked rule
+   that would have caught it — *verify the running binary's provenance, not source HEAD* — is the
+   same principle in another domain and I did not reach for it. What held: I stated both
+   possibilities instead of picking one, so only one direction needed correcting.
+
 2. **Watch `thread-query.py` run at the next wake** — it fires automatically now. Record honestly
    whether it surfaced anything wanted. Null results are the trial's data.
 3. **Then the real question:** does a *work-shaped container* need building, or is thread-keyed