---
digest: >
  Mirror Mind v0.10.4 fixes the remaining Pi startup lifecycle issue after
  v0.10.3. Startup maintenance now runs as a fully detached fire-and-forget
  process, so the extension does not keep Node child-process handles open while
  Pi is trying to finish startup.
---

# v0.10.4 — Pi Startup Lifecycle

**Date:** 2026-05-25

## Highlights

- Pi startup maintenance is now launched as a detached background process.
- The extension no longer keeps stdout/stderr pipes or child-process close
  handlers alive for maintenance.
- Maintenance still appends its output to `mirror-logger.log` for diagnostics.

## Why This Patch Exists

v0.10.3 moved expensive conversation maintenance out of the blocking startup
path. Production validation confirmed Mirror opened quickly again, but Pi's
startup counter still did not stop.

That narrowed the problem: the issue was no longer Python maintenance cost. It
was extension lifecycle cleanup. The background process was still owned by the
extension through active child-process handles and pipes.

## What Changed

The Pi extension now starts maintenance through a detached shell process with
ignored stdio and immediately calls `unref()` on the child process. The command
redirects its output into `mirror-logger.log`, preserving diagnostic evidence
without keeping the extension's event loop attached to maintenance.

## Next Horizon

Production validation should confirm that Pi opens quickly and that the startup
counter stops normally. If it still does not stop, the remaining cause is likely
inside Pi's own lifecycle/working-indicator state rather than Mirror's child
process handling.
