docs: v0.29.0 + dashboard v0.8.1 release notes

Co-authored-by: Alfonso [Magic Context] <288211368+alfonso-magic-context@users.noreply.github.com>

Author: ualtinok

.alfonso/release-notes/dashboard-v0.8.1.md

@@ -4,10 +4,12 @@ A focused fix release: the embedding **Test Connection** button now works for th
 
 ## Fixes
 
-- **Test Connection now works with `{file:...}` / `{env:...}` keys.** If your `embedding.api_key` used a `{file:~/...key}` or `{env:VAR}` reference (the recommended way to keep secrets out of the config file), Test Connection refused it with a confusing message about an environment variable not being set, even for file references. It now resolves these tokens exactly like the plugin does at runtime, so the test uses your real key. Unresolved references (a missing file, or an env var the desktop app didn't inherit) are reported with accurate, kind-specific guidance, and a `{file:...}` that points into a credential directory (`~/.ssh`, `~/.aws`, `~/.gnupg`, `~/.config/gh`) is refused on purpose.
+- **Test Connection (user config) now works with `{file:...}` / `{env:...}` keys.** If your user-level `embedding.api_key` used a `{file:~/...key}` or `{env:VAR}` reference (the recommended way to keep secrets out of the config file), Test Connection refused it with a confusing message about an environment variable not being set, even for file references. It now resolves these tokens exactly like the plugin does at runtime, so the test uses your real key. Unresolved references (a missing file, or an env var the desktop app didn't inherit) are reported with accurate, kind-specific guidance, and a `{file:...}` that points into a credential directory (`~/.ssh`, `~/.aws`, `~/.gnupg`, `~/.config/gh`) is refused on purpose, including via `..` traversal or symlinks.
 
 - **Test Connection now accepts `http://` and local endpoints.** A self-hosted embedding server at `http://127.0.0.1:1234/v1` (LM Studio, Ollama, llama.cpp, and similar) was rejected with "Endpoint must start with http:// or https://" even though it clearly did, because the check was HTTPS-only. Both `http://` and `https://` are now accepted, and loopback / private-LAN addresses are allowed so local servers can be tested. Cloud instance-metadata addresses stay blocked.
 
+- **Test Connection is limited to user config.** The embedding section (provider, endpoint, API key, and the Test button) is now hidden when editing a *project* config. Project configs are shared repository files, and the plugin already ignores an embedding endpoint set there, so testing one was both pointless and a way for a shared repo to direct a key at an arbitrary endpoint. Embedding setup stays in your user config; project configs keep their own settings (like the per-project memory toggles).
+
 - **Model discovery no longer spins up unrelated daemons.** The config page's model dropdowns run `opencode --pure models`, so opening the page no longer boots other OpenCode plugins (and the background processes some of them spawn).
 
 ## Config editor

.alfonso/release-notes/v0.29.0.md

@@ -16,7 +16,11 @@ Adds **smart drops** (opt-in): content-aware reclaim that frees more context on
 
 - **Commit detection unified across its three call sites.** The historian's commit-cluster trigger, the note-nudge "a commit just happened" boundary, and the Pi note detector each carried their own hash + keyword patterns that had quietly drifted apart (different hash lengths, different keyword sets). They now share one definition, so a commit is recognized consistently everywhere.
 
-- **With `memory.enabled: false`, the `ctx_memory` tool and its guidance are no longer presented.** Previously, even with memory off, the agent was still given the `ctx_memory` tool and told to "save to memory proactively" — but with memory off the `<project-memory>` block is never injected, so anything it wrote could never resurface, making those writes silent busywork. The tool and all its guidance are now omitted when memory is off. `ctx_search` stays available (it still searches your conversation history and indexed git commits, just not memories).
+- **With `memory.enabled: false`, the `ctx_memory` tool and its guidance are no longer presented.** Previously, even with memory off, the agent was still given the `ctx_memory` tool and told to "save to memory proactively", but with memory off the `<project-memory>` block is never injected, so anything it wrote could never resurface, making those writes silent busywork. The tool and all its guidance are now omitted when memory is off. `ctx_search` stays available (it still searches your conversation history and indexed git commits, just not memories).
+
+- **Fixed a crash in the WASM sandbox that runs compiled smart-note checks.** When two projects' nightly smart-note sweeps overlapped (common at multi-project startup), the shared sandbox could throw `QuickJSUseAfterFree: Lifetime not alive` and fail the check. Sandbox runs are now serialized, so a check that pauses for a file read or network request can no longer corrupt a concurrent one.
+
+- **Pi: the `ctx_memory` tool now stays consistent when you switch projects.** In a single Pi session that moves between projects (one with memory enabled, one without), the tool could end up registered for the wrong project's setting. It is now always registered and gates per-project at call time, matching what the prompt advertises for the current project.
 
 ## Docs