---
digest: >
  Mirror Mind v0.10.6 makes runtime update more resilient when the production
  database is temporarily unavailable during the status gate. The updater now
  attempts a safe MemoryClient bootstrap and retries status before failing,
  avoiding a manual repair step for the common running-surface scenario.
---

# v0.10.6 — Update Status Recovery

**Date:** 2026-05-25

## Highlights

- Runtime update now detects database-unavailable status-gate failures.
- The updater attempts a safe database bootstrap through `MemoryClient` and
  retries the status check before blocking the update.
- Post-update status performs the same recovery attempt before reporting failure.
- Recovery guidance now uses `uv run python -m memory ...` so production users do
  not accidentally call a Python environment without the `memory` package.

## Why This Patch Exists

Production update validation showed a repeated failure mode: when a local Mirror
surface has recently used the production database, `runtime status` can report
`unable to open database file`. The update command then refuses to continue at
the status gate.

This is too likely for final users. They should not need to discover processes,
kill a web server, or run a one-off Python command just to let the updater open
the database again.

## What Changed

Before failing a status gate because the database is unavailable, runtime update
now tries the same safe open path that previously fixed the issue manually:
constructing a production `MemoryClient`, opening the configured database, and
closing it. If that succeeds, the updater rebuilds status and continues.

The same recovery is applied after fast-forward/migrations if post-update status
sees the database as unavailable.

## Next Horizon

If users still hit database-unavailable update failures, the next step is to add
explicit local surface lifecycle coordination so the updater can gracefully ask
Mirror web surfaces to stop before update and restart after update.
