[< Releases](index.md)

# v0.12.0 — Multi-Mirror and Preferences

## Digest

This release closes CV13.E2, the Multi-Mirror and Preferences slice of the Mirror Web Experience. The local web app can now discover local Mirrors, switch safely among discovered Mirror databases, and persist user-facing web preferences per Mirror: display name, avatar symbol, and light/dark/system theme.

## Highlights

- The header Mirror selector discovers local Mirrors with `memory.db` and filters out non-Mirror directories such as backups.
- Mirror switching is constrained to server-discovered local Mirror names; the browser never submits arbitrary filesystem paths.
- Workspace, Identity, memory, and search surfaces reload against the selected Mirror database for the running web session.
- A Preferences page shows the active Mirror context and the local preferences file path.
- Display name and avatar symbol are stored per Mirror under `<mirror-home>/web/preferences.json`.
- Theme preference supports `system`, `light`, and `dark`, applies immediately, and persists per Mirror.
- The Mirror selector shows each Mirror's display name and avatar while keeping the technical directory name as detail.

## Narrative context

`v0.11.0` made the read-only web surface feel like a product. `v0.12.0` makes that product local-user aware. Mirror Web can now answer: which Mirror am I looking at, can I switch to another local Mirror safely, and how do I want this interface to identify and present this Mirror?

The boundary remains intentionally local-first. This release does not add remote access, arbitrary database paths, identity mutation, configuration editing, authentication, or background operations. Preferences are web preferences, not changes to the Mirror identity graph.

## What changed

- Added a read-only Mirror registry for local web discovery.
- Added `/api/mirrors` and safe `/api/mirrors/select` web endpoints.
- Extended `/api/shell` with active Mirror path, discovered Mirrors, profile, theme, and preferences path.
- Added server-side validation so Mirror selection only accepts discovered local Mirrors with `memory.db`.
- Added a Preferences perspective to the web shell.
- Added profile preference persistence for display name and avatar symbol.
- Added theme preference persistence for `system`, `light`, and `dark`.
- Applied selected theme through the document root while keeping `system` delegated to OS color preference.
- Added final coherence coverage for cross-Mirror preference isolation.
- Updated CV13.E2 roadmap and worklog records through S1–S5.

## Conscious exclusions

- No arbitrary path input.
- No remote Mirror selection.
- No authentication system.
- No Mirror creation, deletion, migration, backup, or repair flows.
- No identity graph/profile mutation.
- No `.env` or runtime configuration editing.
- No journey metadata editing.
- No conversation retitle operation.
- No LLM calls during page load or switching.
- No web operation runner.

## Validation

Focused validation passed during the story cycle:

```bash
uv run pytest tests/unit/memory/web/test_preferences.py tests/unit/memory/web/test_mirrors.py tests/unit/memory/web/test_server.py
uv run ruff check src/memory/web tests/unit/memory/web/test_preferences.py tests/unit/memory/web/test_mirrors.py tests/unit/memory/web/test_server.py
uv run ruff format --check src/memory/web tests/unit/memory/web/test_preferences.py tests/unit/memory/web/test_mirrors.py tests/unit/memory/web/test_server.py
node --check src/memory/web/static/app.js
git diff --check
```

Navigator browser validation accepted S1–S5, including final cross-Mirror preference isolation and the Mirror selector's display-name/avatar presentation.

## Next horizon

The next CV13 epic is Configuration Console: inspect Mirror configuration and journey metadata through guarded web surfaces without weakening service boundaries.
