---
digest: >
  Mirror Mind v0.9.1 adds the missing opening awareness around the v0.9.0
  self-update path. The runtime can now surface stable release availability in
  the welcome through a network-tolerant check and a small cache, while Pi gets
  a compact status-bar signal that shows the active user and whether attention
  is needed. This patch does not change the update executor; it makes the
  existing stable update capability visible at the moment the user opens the
  Mirror.
---

# v0.9.1 — Welcome Release Awareness

**Date:** 2026-05-23

## Highlights

- Welcome can detect a newer stable release through a lightweight remote check
  when its update cache is missing or stale.
- Update awareness is cached under `<mirror-home>/runtime/update-check.json`.
- Remote welcome checks fail softly and can be disabled with
  `MIRROR_WELCOME_REMOTE_UPDATE_CHECK=off`.
- `python -m memory welcome --status-line` renders a compact status signal for
  runtime status bars.
- Pi now uses the compact status signal instead of showing only conversation
  logging status.

## Where We Started

After publishing `v0.9.0`, the self-update mechanism worked, but the opening
experience did not yet reveal it. A user could run `runtime update --check` and
see the new release, but simply opening Mirror showed version and channel only.
The system was operationally capable but experientially quiet.

That gap mattered because the desired user experience is natural: open Mirror,
see that a release is available, ask what changed, and ask Mirror to update.

## What Changed

The welcome card now has network-tolerant release awareness. It can refresh a
small update cache with a lightweight `git ls-remote` check when the cache is
absent or older than six hours. It does not fetch, mutate refs, update files,
run backups, run migrations, or block startup. If the remote is unavailable, the
welcome still opens normally.

When a stable update is known, the welcome can show:

```text
Update available: v0.9.1 — Welcome Release Awareness
Ask: "what changed?" or "update my Mirror"
```

The compact status-line command gives runtimes a small signal:

```text
◇ alisson-vale · ✓
◇ alisson-vale · ⬆ v0.9.1
```

Pi's `mirror-logger` extension now uses that status-line command for its footer
status.

## Conscious Exclusions

- This patch does not auto-update the runtime.
- The status bar reads cached state only; welcome owns remote refresh.
- The release title is available when local release notes exist. Otherwise the
  notice degrades to version-only or commit-level availability.
- This patch does not add a full health dashboard.

## What We Learned

Mirror Mind should be local-first in state and network-tolerant in operation.
The welcome should not depend on the network, but it can use the network as an
antenna. The status bar should remain a signal; the welcome is where explanation
and next action belong.

## Next Horizon

The next release-awareness improvements should come from dogfooding: whether the
status signal is clear enough, whether the cache TTL feels right, and whether
natural-language update requests should get a dedicated intent path beyond the
existing runtime commands.
