---
digest: >
  v0.36.2 is a patch release of one Change Request, CR154, which finishes what
  v0.36.1 began. v0.36.1 stopped Mirror importing Pi sessions, but the
  conversations an earlier version had imported stayed, and the only way to
  see them was a SQL query. `mirror conversations imported` now lists them by
  the folder each session came from, beside how many Pi sessions the home
  logged live there, and `remove` deletes the ones you name, only on
  `--apply` and only after a verified backup. With it, `discard-current` no
  longer fails on a conversation a Soul Mode integration names. No migration.
---

# v0.36.2 — Clearing Out What Another Home Copied

**Date:** 2026-10-21

## Highlights

- **`mirror conversations imported` shows what an earlier version imported**
  ([CR154](../project/refinement/rs010-cv22-oracle-and-port-hygiene/cr154-a-home-cannot-list-or-remove-the-pi-conversations-it-imported.md)):
  one line per folder the session came from, with how many conversations were imported
  from it and how many Pi sessions this home logged live there. A folder where the home
  logged nothing live is most likely another home's work. `--project <text>` lists a
  folder's conversations.
- **`remove` deletes what you name, and nothing else.** Ids, or every import of one
  folder, written exactly as the listing prints it. It is a dry run until `--apply`;
  `--apply` takes a dated backup, verifies it, and removes in one transaction. Memories
  and provider-call records that named a removed conversation are kept, unlinked, and
  the report names the backups that still hold copies.
- **A typo cannot widen a removal.** Every option is declared, and one the command does
  not know is refused before the database opens.
- **`discard-current` works on a Soul Mode conversation.** It failed with `FOREIGN KEY
  constraint failed` on any conversation a Soul Mode integration named. Deleting a
  conversation now decides every table that references one, and a test reads the
  schema so the next such table cannot be missed.

## Where We Started

v0.36.1 stopped session maintenance from importing Pi sessions, the defect that let the
Mirror homes on one machine copy each other's conversations. It removed the cause and
said so: the copies stayed, and the note gave a SQL query to list them. Deleting them
was the person's decision, and no command could carry it out — `discard-current`
removes only the current conversation.

## What Changed

**One command, folders first.** A home can hold hundreds of imports, and the decision a
person makes is about where they came from, so the listing leads with folders. The
folder is the directory the Pi session file lived in, read from the path the home
stored; Mirror reads no Pi file to learn it. Beside each folder, the number of Pi
sessions the home logged live from it. On the maintainer's production home, 96 imports
came from one development worktree and 76 from the development checkout, where it had
logged none live, and 3 from its own workspace, where it had logged 714. In a home made
by copying another, the copied rows count as its own, which blurs the number.

**Removal is careful by construction.** A dry run first, with the exact command that
applies it to the same home. On `--apply`, the set is decided read-only; a refusal or
an empty set stops there, with no backup. Then the dated archive, verified; then one
transaction that decides the set again and refuses if it moved. An id must name exactly
one imported conversation, by its full id or by a prefix of at least eight characters:
a live conversation, an unknown id, or an ambiguous prefix refuses the whole command.

**A review before any code.** Five personas reviewed the plan. The database architect
found that the deletion `discard-current` used, the one this command meant to reuse,
missed one of the six tables that reference a conversation, so with foreign keys on, a
conversation a Soul Mode integration named could not be deleted at all — measured on a
scratch home, then fixed for both commands. The security engineer found that under the
listing's lenient parser, a typo such as `--projet` would drop the folder filter and
remove every import in the home; the command parses strictly, with the parser `backup`
and `repair-encoding` already used.

**Validated on a copy of the real thing.** On a scratch home made from a fresh backup of
the maintainer's development home, the command listed 515 imports from 22 folders
and 5 of unknown origin, refused the typo, and removed the 418 from the production workspace's folder with their
21,901 messages. Live conversations, memories, and provider-call records kept their
counts.

### What you will notice

- A new command, `mirror conversations imported`, and its `remove`.
- `discard-current` deletes a conversation that a Soul Mode integration names.

## Upgrading

```bash
mirror runtime update          # or: npm install -g mirror-mind
```

There is no database migration, and no runtime wiring changes. Then, if you ran more
than one home:

```bash
mirror conversations imported
mirror conversations imported --project <text>
mirror conversations imported remove --all --project <folder>
mirror conversations imported remove --all --project <folder> --apply
```

Start with the folders where "logged live here" is 0, and look at a folder's
conversations before removing them. The dated backups made since the import, and the
pre-write backup, keep copies until you delete them or they age out (30 days for an
archive).

## Conscious Exclusions

- **Telling another home's copy from a gap this home filled for itself.** That takes
  both homes' databases, and no home reads another's. The folders and the logged-live
  counts are the evidence a person decides on.
- **Removing anything from backups.**
- **Options before the subcommand.** `mirror conversations --db-path X imported` shows
  the plain listing and removes nothing; that is
  [CR096](../project/refinement/rs009-cv22-front-door-routing-correctness/cr096-conversations-lists-instead-of-appending-when-options-come-first.md)'s
  class.
- **A tool for models.** No MCP tool and no skill runs this command: a person does.

## What We Learned

Reusing a routine is a claim about it. The deletion `discard-current` used was correct
for the tables it knew, and wrong the day another table began to reference a
conversation. The question that found it — which tables reference a conversation? — is
now a test that asks the schema, not a person's memory.

A lenient parser is harmless in a listing and dangerous in a deletion: the same ignored
token is a no-op in one and a wider removal in the other.

## Next Horizon

CV21.DS5.TS4, then DS11 and CV21's own release. Captured and open: CR155, `runtime
diagnose` reading the Pi extension's error lines; CR156, what copying a home makes;
CR157, three settings `REFERENCE.md` lists that nothing reads.
