v0.3.6: Reliable Async Recall and Web Workflows

v0.3.6 completes the asynchronous subagent Recall lifecycle fix and consolidates the Web navigation, CLI discovery, theme, Runtime Memory and managed embedding improvements merged since v0.3.5. The published DSH baseline remains 0.1.1-rc.2, with the same package verified against the source-only 0.1.2-alpha.1 preview.

#What changed

• Stable asynchronous Recall. A child retains the View and runtime authority captured when it is created, independently of parent completion, later parent turns, View collection and settings swaps. Each executing turn owns its Recall, Related and Documents budgets and caches; parallel calls within a turn share limits, while siblings and cold-resumed activations do not reuse another task's evidence or budget. Requested Memory Space subsets remain enforced during cache replay. This completes the partial fix from #116 in #130.
• Plugin-owned Runtime Memory snapshots. Mnemon supplies changed runtime snapshots in its own message, attributed to the plugin, instead of the Host's shared runtime-context projection. A memory change no longer forces other plugins' stable context sections to be emitted again. #107
• Reliable Memory System navigation and CLI checks. Panel snapshot methods preserve their store receiver on newer DSH clients. Switching between Memory System and other panels follows the visible host state, and configured CLI command names are resolved through PATH so status and version checks agree. #113, #127
• Consistent default themes and dialogs. The Memory System canvas respects the host's official light/dark backgrounds. Shared dialogs use the host's layer-2 surface with a canvas backing, and transparent footers avoid double-compositing translucent themes. #126, #129
• Managed embedding credentials and protocol selection. Native embedding settings accept an optional API key and auto, ollama or openai protocol override, including OpenAI-compatible endpoints without a /v1 suffix. Disabled overrides leave the existing Host environment unchanged. #117
• Reproducible verification. The alpha job preserves its intentional source links through pnpm pre-run checks; real DSH Agent-loop and JSONL cold-resume tests now cover the asynchronous lifecycle. Package-size guards account for the added managed embedding and delegated-turn implementation without publishing test fixtures. #121, #130

#Safety and upgrade

No Runtime, Documents, Memory Space or Provider-data migration is required. Existing embedding settings remain valid; API keys and protocol overrides are optional. Saved keys belong in the DSH settings location and must not be copied into release logs, screenshots or memory content. Model Recall without a valid executing-turn pin is rejected rather than inheriting the parent's latest View.

An already-running child retains its original runtime until that activation is disposed. Wait for or cancel such tasks before retiring their old data location. Update dsh-mnemon, restart each DSH profile using it, and reopen Memory System. Registry installations should continue using DSH 0.1.1-rc.2; alpha is a source-verification target, not an npm installation target.

Rolling back to 0.3.5 does not require data conversion, but restores the earlier Recall and Web behavior and removes this release's managed embedding key/protocol controls. Retain a settings backup before relying on those new overrides.

#Verification

• The complete local Node.js 24 verification chain passes 574 tests, with one Windows-only test skipped on macOS. The async fix adds 29 regression cases, including real DSH Agent-loop, tool-pipeline and JSONL cold-resume coverage.
• Linux Node.js 22.19 and 24, Windows Node.js 24, and the exact source-linked dsh-v0.1.2-alpha.1 tag are checked by CI. The merged implementation passed all four jobs before release preparation.
• Deterministic double builds verify 107 generated files; an isolated real Headless profile exposes 35 tools including five representative Mnemon tools. Package-content validation, all 10 Node-compatible public-entry imports, publint strict and the attw ESM profile pass.
• The existing real npm WebUI before/after records are preserved in navigation and CLI regressions and dialog surface evidence. Those records identify the exact pre-release patch builds and are not relabeled as release screenshots.
• Release changes pass git diff --check; generated lib/ files and test-owned data are not committed.

See the v0.3.5 release notes for the preceding dual-Host compatibility release.