Contents

v0.2.6: Remote-Safe UI Reliability

View source on GitHub

v0.2.6 makes Memory System reads and asynchronous UI transitions reliable across trusted remote deployments, slow Providers, and rapid workspace or page changes.

Fixed

  • Refreshing an individual Memory Space card now uses the trusted read RPC. Remote read-only deployments no longer report Failed to fetch while full synchronization succeeds.
  • HTTP-based Providers now honor signals that were already aborted before request setup. OpenViking fallback delays also reject with a proper error.
  • Provider settings, Document readers, related-memory traversal, and entity views ignore responses from older scopes or interactions instead of overwriting the newest UI state.
  • Related-memory scrolling safely degrades when scrollIntoView is unavailable.

Deployment Boundary

  • Browser code remains transport-neutral: it delegates RPC and deployment URLs to the DSH host connection and does not construct root-relative API, plugin, or asset URLs.
  • Full /prefix/ hosting still requires DSH to expose one coherent base URL for its shell, assets, plugin bundles, RPC/API, and WebSocket endpoints. The host-level compatibility work is tracked in the Roadmap.

Roadmap

  • Added Cordis / DSH contract coverage for service injection, hot reload and disposal, late-registered structured-output tools, and toolFilter isolation.
  • Added explicit host capability declarations and a real URL-subpath deployment matrix as future work; this release does not weaken subagent tool isolation.

Verification

  • The complete suite passes with 330 tests; the Windows-only smoke test is skipped only on non-Windows local runs.
  • Deterministic builds, Headless activation, package checks, and CI on Ubuntu and Windows pass.
  • Real WebUI testing covered the Memory System status page, Memory Space overview and card refresh, rapid page changes, and rapid entity selection without browser errors or warnings.

Upgrading

Update dsh-mnemon and restart the affected DSH profile. Storage layouts, schemas, Provider configuration, and tool contracts are unchanged; no data migration is required.

See the v0.2.5 release notes for the previous patch release.