---
digest: >
  v0.16.1 publishes the runtime update preflight resilience fix validated during
  CV9.E2 stabilization. The updater now distinguishes full runtime readiness
  from a narrow update-safe preflight state, so old code no longer blocks a
  stable update only because the database already contains a core migration
  introduced by the target version. Runtime status also recovers SQLite WAL
  sidecar absence during read inspection. The normal safety path remains intact:
  clean git state, backup, backup verification, fast-forward, migrations, and
  post-update status are still enforced.
---

# v0.16.1 — Runtime Update Preflight Resilience

**Date:** 2026-05-27

## Highlights

- Published the CV9.E2.S3 updater hardening fix as a patch release.
- Allows `runtime update` to pass a narrow pre-update gate when the only blocker is core migration drift that the target release may resolve.
- Keeps dirty git trees, missing databases, extension health issues, checksum drift, and unreadable migration ledgers blocked.
- Recovers SQLite WAL sidecar absence during runtime status inspection without creating a missing database.
- Preserves the normal backup, backup verification, fast-forward, migration, and post-update status gates.

## Where We Started

Production Mirror was on `0.15.0` while stable had advanced to `0.16.0`. The welcome correctly detected the new version, but the update command stopped at the status gate before fetching or fast-forwarding.

The root problem was not the specific migration. It was the updater's shape. The old checkout used its own strict `runtime status` as a hard pre-update gate. When the database already contained a migration row introduced by the newer target release, the old code called that row unknown and blocked the very update that would make it known.

A second fragility appeared in the same diagnosis: strict SQLite read-only inspection can report `unable to open database file` for a WAL database when sidecar files are absent or need refresh.

## What Changed

`runtime status` remains strict. It still reports attention when installed code sees pending or unknown core migrations.

`runtime update` now has a narrower preflight interpretation. If mirror home resolution, git state, database existence, and extension health are safe, and the only remaining blocker is readable core migration drift, the updater may proceed into the normal update path. It still fetches the configured channel, accepts only no-op or fast-forward plans, creates and verifies a database backup before migrations, applies migrations through `MemoryClient`, and requires post-update status to be ready.

The SQLite status reader still tries strict read-only mode first. If that fails with `unable to open database file`, it retries against the existing database in bounded read-write mode so SQLite can recreate WAL sidecars. It does not create a missing database file or mutate semantic Mirror data.

## Conscious Exclusions

This release does not add broad automatic repair. Dirty worktrees, diverged branches, missing databases, invalid extension manifests, extension migration drift, checksum drift, and unreadable migration ledgers still require explicit diagnosis and repair.

This release also does not deliberately reproduce future migration drift in production by editing migration ledgers. That remains unsafe for a user's real memory database. The production recovery evidence and focused regression tests cover the failure class without corrupting the ledger.

## What We Learned

A self-updater cannot treat current-code status and update-preflight status as the same question. Runtime readiness asks whether the installed checkout and database are coherent now. Update readiness asks whether it is safe to move to code that may restore that coherence.

The boundary is narrow, but important. Safety is not the same as refusing to move. Sometimes the safest operation is the controlled update path.

## Next Horizon

The next validation step is to update production from `0.16.0` to `0.16.1` through the normal user-facing flow. If we want to validate the newly installed updater executing another update, a later minimal stub such as `v0.16.2` can exercise that path without development-branch bridging.
