Contents

v0.2.14: Readable Sidebar Surfaces

View source on GitHub

v0.2.14 is a focused Web UI patch that keeps the Mnemon Sidebar workspace readable when a DSH skin makes the base background transparent.

Fixed

  • The mounted Mnemon workspace, shared view surface, and Sidebar-specific chrome now prefer --dsw-alias-bg-overlay and fall back to --dsw-alias-bg-base when the overlay token is unavailable.
  • The fallback is applied consistently to the Sidebar shell, headers, navigation, page surfaces, dialogs, footers, canvas, and update banner, preventing the conversation and full-screen skin artwork from showing through the workspace.
  • Default-theme behavior is preserved because themes without the overlay token continue to use the existing base surface.

Safety and compatibility

  • This release changes Client CSS only. Host behavior, Runtime Memory, Project Documents, Memory Spaces, Providers, configuration, RPC permissions, storage formats, credentials, and existing data are unchanged.
  • Skins such as maid-atelier can retain their transparent conversation canvas while providing Mnemon with their high-opacity overlay color. No skin-specific selector or dependency is introduced.
  • Update dsh-mnemon and restart the affected DSH profile. A normal downgrade to v0.2.13 restores the previous surface selection and requires no data rollback.

Verification

  • Two real isolated DSH 0.1.0-rc.8 Web profiles load v0.2.13 and this release with maid-atelier pinned at d0419da; same-viewport captures confirm that the workspace changes from fully transparent to a high-opacity surface and remains readable in both light and dark modes.
  • The complete local verification passes with 371 tests; one Windows-only smoke test is skipped only on the non-Windows local run.
  • Focused CSS coverage verifies the overlay-to-base fallback in source and compiled output and prevents direct base-only Sidebar surfaces from returning.
  • Type checking, deterministic builds, Headless activation, package validation, publint, attw, and CI on Ubuntu and Windows pass.
  • The fix resolves issue #56.

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