---
digest: >
  v0.18.0 completes the Conversation Metadata Lifecycle release arc. Mirror now
  finalizes non-manual title, summary, and tags when conversations close;
  exposes contextual metadata maintenance in the web conversation detail; and
  gives Operations a production-ready historical metadata backfill with dry-run,
  safe/force modes, all-conversation batches, resume scopes, approval, backups,
  per-conversation progress, no-change evidence, and orphan conversation cleanup.
  Manual metadata remains preserved by default.
---

# v0.18.0 — Conversation Metadata Lifecycle

**Date:** 2026-06-01

## Highlights

- Finalizes non-manual conversation metadata at close time.
- Adds web conversation-detail maintenance for title, summary, and tags.
- Adds historical metadata backfill through Operations with dry-run, approval, backups, progress, and final result evidence.
- Supports `safe` and `force` backfill profiles while preserving manual metadata by default.
- Adds all-conversation and resume/review scopes for production-scale backfill.
- Adds approval-gated orphan conversation cleanup with backup and deletion progress.

## Where We Started

Mirror already had first-message/provisional titles and batch retitling, but
conversation metadata still behaved too narrowly. Old conversations could have
thin titles, missing summaries, missing tags, or stale metadata provenance. The
runtime also had no close-time finalization step, and users had to use CLI tools
for broad historical repair.

That was especially painful in the web console: Operations could run long tasks,
but metadata lifecycle maintenance was not yet visible enough for a real user to
trust a broad production backfill.

## What Changed

Conversation metadata now has explicit lifecycle policy and execution profiles.
`safe` mode applies clear repairs conservatively, `force` regenerates selected
non-manual metadata, and close-time finalization refreshes non-manual metadata
when a conversation ends. Manual title, summary, and tag edits remain protected.

The web conversation detail now exposes contextual maintenance: check whether
metadata needs updating, review user-facing reasons, suggest/save title and
summary, edit tags, and apply a report-driven metadata update.

Operations now includes **Historical metadata backfill**. It can preview or
apply batches, choose safe/force from a dropdown, filter by journey, process all
matching conversations, or scope to `not_backfilled` and `no_change_latest_run`
for recovery/review. Apply requires approval, creates a backup, emits progress
per conversation, and renders final result details including changed and
no-change evidence.

A companion **Orphan conversation cleanup** operation handles the cleanup found
during real production backfill: short orphan conversations that produced no
metadata changes. It supports dry-run, candidate review, approval, backup,
reference cleanup, per-conversation deletion progress, and final deleted counts.

## Production Validation

This release was validated against the user's real Mirror database. The broad
force backfill processed 579 conversations, changed 482, and identified 97
no-change results. A follow-up orphan cleanup preview found short orphan
conversations; the cleanup path was hardened after production revealed foreign-key
and database-lock failure modes.

The final operation path now handles referenced orphan conversations, commits
before emitting progress, and marks unexpected thread failures as failed instead
of leaving runs stuck as running.

## Conscious Exclusions

- No automatic unbounded background backfill is enabled.
- `force` still preserves manual metadata by default.
- Orphan cleanup does not infer journeys or recover content; it deletes only the selected previewed candidates after approval.
- Operations still uses polling rather than true streaming/SSE.
- Active per-turn metadata refresh remains future work beyond close-time and explicit maintenance/backfill operations.

## Next Horizon

The remaining CV9 stabilization work can now focus on boundary hardening,
release readiness, and any polish discovered after production uses v0.18.0 as
the baseline metadata lifecycle release.
