[< Releases](index.md)

# v0.13.0 — Configuration Console

## Digest

This release closes CV13.E3, the Configuration Console slice of the Mirror Web Experience. The local web app can now inspect non-sensitive Mirror/runtime configuration, understand selected environment boundaries with secrets masked, and manage selected journey metadata from the Workspace context where journeys already live.

## Highlights

- Added a read-only Configuration page for active Mirror paths and runtime defaults.
- Organized Configuration into internal tabs to reduce visual clutter.
- Added an Environment boundary section with selected allowlisted settings and secret masking.
- Kept global Configuration scoped to Mirror/runtime settings instead of duplicating journeys.
- Added a Workspace Settings tab for the selected journey.
- Added safe journey metadata editing for project path, sync file, icon, and color.
- Added final coherence coverage for secret masking, configuration boundaries, and journey metadata persistence.

## Narrative context

`v0.12.0` made Mirror Web local-user aware through Mirror switching and per-Mirror preferences. `v0.13.0` makes the local configuration boundary visible and safer to operate. The release separates concerns clearly: Configuration explains Mirror/runtime settings, Workspace owns journey settings, and Preferences owns user-facing web preferences.

The release deliberately avoids raw configuration editors. It does not expose complete environment dumps, raw `.env` editing, YAML editing, database editing, or journey content editing. Where writes exist, they pass through a bounded service method and are limited to selected journey metadata fields.

## What changed

- Added `GET /api/configuration/overview` for non-sensitive configuration overview.
- Added a Configuration tab to the web shell.
- Shows Mirror home, database, preferences file, backups, exports, transcript exports, extensions, runtime environment, memory search model, memory extraction model, LLM audit logging, and conversation routing.
- Added Environment boundary visibility for selected runtime variables.
- Masks sensitive environment-derived values such as API keys.
- Added a Workspace Settings section for the selected journey.
- Added `POST /api/journeys/metadata` for safe metadata updates.
- Added `JourneyService.update_metadata_fields()` for selected field updates.
- Added tests for configuration serialization, masking, Workspace placement, safe write behavior, and final coherence.

## Conscious exclusions

- No raw `.env` editing.
- No complete `os.environ` dump.
- No secret disclosure.
- No raw JSON/YAML/database editor.
- No journey content or briefing editor.
- No remote configuration management.
- No operation runner.
- No conversation retitle.

## Validation

Focused validation passed during the story cycle:

```bash
uv run pytest tests/unit/memory/surfaces/test_workspace.py tests/unit/memory/web/test_configuration.py tests/unit/memory/web/test_server.py
uv run ruff check src/memory/services src/memory/surfaces src/memory/web tests/unit/memory/surfaces/test_workspace.py tests/unit/memory/web/test_configuration.py tests/unit/memory/web/test_server.py
uv run ruff format --check src/memory/services src/memory/surfaces src/memory/web tests/unit/memory/surfaces/test_workspace.py tests/unit/memory/web/test_configuration.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 Configuration/Workspace boundary coherence, environment masking, and safe journey metadata edit persistence.

## Next horizon

The next CV13 epic is Conversation Intelligence: readable transcripts, useful conversation titles, and safe retitle operations for individual and legacy conversations.
