---
digest: >
  Mirror Mind v0.10.7 reconciles runtime updater and release-management
  documentation with the current command surface. The command reference,
  troubleshooting guide, repair policy, release-note process, docs index, and
  top-level help now describe cumulative release notes, updater repair, release
  promotion options, and database-unavailable update recovery coherently.
---

# v0.10.7 — Runtime Operations Documentation

**Date:** 2026-05-25

## Highlights

- Documented `runtime release-notes pending [--from] [--ref]` for cumulative
  release-note visibility.
- Documented `release-doctor --stable` and `release-promote --stable --remote
  --dry-run --push`.
- Documented the `v0.10.6` database-unavailable update recovery behavior.
- Updated top-level `python -m memory --help` runtime usage with the current
  arguments.
- Clarified that final users should not need to kill web/runtime processes for
  the common database-unavailable update case.

## Why This Patch Exists

The release train from `v0.10.0` through `v0.10.6` added several operational
surfaces quickly: stable promotion, cumulative release notes, updater repair, and
status-gate recovery. The code was ahead of the docs.

Because these commands are safety boundaries, stale documentation is not just a
cosmetic issue. It can push users toward manual repair paths when the runtime now
has a safer command path.

## What Changed

The command reference now lists the current runtime command arguments and
explains when to use pending release notes, updater repair, release doctor, and
release promotion flags.

The troubleshooting guide now has a dedicated entry for `unable to open database
file` during update, pointing users to the repaired updater path for older clones
and explaining that current versions recover automatically.

The runtime repair policy now treats temporarily unavailable production
databases as a bounded recovery scenario, not as a normal manual process-killing
workflow.

## Next Horizon

Future operator-facing commands should update `REFERENCE.md`, the top-level help,
and troubleshooting/repair docs in the same patch that introduces the behavior.
