[< Docs](../index.md)

# Releases

Narrative release notes for Mirror Mind live here from the adoption of CV9.E5 onward.

Release notes are prospective. Historical versions through `v0.7.0` remain valid project history, recorded in Git tags and the [worklog](../process/worklog.md), but they are not retroactively reinterpreted by the new [versioning rule](../process/versioning.md).

Future release notes should use the structure defined in [Release Notes](../process/release-notes.md): digest, highlights, narrative context, what changed, conscious exclusions, lessons, and next horizon.

---

## Releases

- [v0.44.2 — A Journey's Content, Read Whole](v0.44.2.md) — patch release of CR217: `readJourney` answers one Journey's content whole, the text the runtime delivers to a turn, where the tree carries only a collapsed description; read-only, additive, `DESKTOP_API_VERSION` stays 1.
- [v0.44.1 — A Help Flag That Only Helps, and a Journey the Host Keeps](v0.44.1.md) — patch release gathering what merged since v0.44.0: CR216, a Mirror load never moves a host's Conversation to another journey (`ensureConversation` marks it, the session guess skips it, the bind never nulls); CR215 with PR #60, `-h` or `--help` after any command answers its usage and runs nothing, where `tasks delete <id> --help` deleted the task; CR211 and CR213, the operating instructions bound a task's size and describe the persona routing the Core has. `build ... --help` now exits 0. No migration.
- [v0.44.0 — A Persona the Host Can Create and Delete](v0.44.0.md) — minor release of CR207: `createPersona` writes a persona the router can choose from the next turn by its description; `previewPersonaDeletion` and `deletePersona` delete one behind the preview's digest and a named, verified backup, keeping its history, removing its descriptor, integrations and bindings, and clearing a Journey's default and the sticky default that name it; an heir refuses. No migration.
- [v0.43.0 — A Persona Edit That Reaches the Open Conversation](v0.43.0.md) — minor release of CR206: the doorman remembers, per delivered persona, a fingerprint of its prompt, and a turn routed to a persona whose prompt changed since delivers it again under a `revised` header; a name or description change delivers nothing; the full load records its fingerprint and a compaction starts over; a session written by an earlier Core is adopted without re-delivery. No migration.
- [v0.42.0 — A Persona the Host Can Read and Edit](v0.42.0.md) — minor release of CR205: `mirror-mind/desktop` gains `listPersonas`, `readPersona` and `updatePersona`; the update writes only the fields it is given (name, prompt, description, routing keywords), keeps every other metadata key, refuses a stale edit with `persona_changed`, writes nothing when nothing changes and goes behind the front door's verified snapshot; `defaultModel` and `inheritsFrom` are read only; an edited prompt reaches an open conversation only with CR206. Desktop API version 1. No migration.
- [v0.41.0 — A Persona When the Subject Asks for One](v0.41.0.md) — minor release of CR203 and CR204: a Mirror Mode turn's persona is routed by its subject, by a Decisions model through OpenRouter taken only above a threshold, else the Journey's `default_persona`, else none; a turn never inherits the session's persona, and a turn with none tells the model not to sign; every routing failure is none; one content-free `llm_calls` row per call; `mirror-mind/desktop` returns `personaName` beside the persona's id. No migration.
- [v0.40.1 — The Bins You Named, or Why Not](v0.40.1.md) — patch release of CR197: the plugin's hook wrappers and MCP entry use `MIRROR_BIN` only as an absolute path to a directory holding the bin they need, the rule `MIRROR_NODE` follows since v0.39.5; a relative value is never used, so a project's own `bin/mirror-hook` cannot run, and a refused value is named with its reason, once a day in `hooks.log` and on the MCP entry's stderr; the forward-slash `C:/…` form Windows machines set counts as absolute, in CI under Git Bash. Also carries CV9's re-baseline (documents only). No migration.
- [v0.40.0 — A Reply Stays in Its Own Conversation, and a Journey Can Go](v0.40.0.md) — minor release closing the first release train: CR151, a session's transcript fills only the conversation that session is bound to, each reply stamped with its transcript time, where it used to fill every open reply-less conversation in the transcript's window, another session's included; a transcript no session owns backfills nothing; and CR200, previewed as v0.40.0-next.1, `mirror-mind/desktop` deletes a Journey with every record that belongs to it, by digest, behind a verified backup. Update every install that has a home. No migration.
- [v0.40.0-next.1 — A Journey Can Go, Showing What Goes With It](v0.40.0-next.1.md) — preview under npm's `next`, read by no updater, for Nautilus for Mirror (the release train): CR200, `mirror-mind/desktop` gains `previewJourneyDeletion` and `deleteJourneyWithRecords`, deleting a Journey with every record that belongs to it after a preview that counts it, by digest, behind a verified backup; child Journeys refuse. Terminal users receive it with v0.40.0. No migration.
- [v0.39.5 — The Node You Named, or Why Not](v0.39.5.md) — patch release of CR192, from PR #47's thread (@rodrigoimmaginario): the hook wrappers, the plugin's MCP entry, and `runtime diagnose` use `MIRROR_NODE` only as an absolute path to an executable file, as the Pi extension does; a relative value is never run, and a refused one is named with its reason, once a day in `hooks.log` and on the MCP entry's stderr; the Windows installer's drive-letter path counts as absolute, in CI under Git Bash and on the installer. No migration.
- [v0.39.4 — The Reply Finds Its Prompt](v0.39.4.md) — patch release of PR #51 (@alannascimento1), CR166 and CR196: on Claude Code, a prompt typed while a turn runs and a journey entered in plain words no longer lose the reply; `nothing_waiting` in `hooks.log` means a lost reply again. No schema change, no migration.
- [v0.39.3 — Windows Gets Its Hooks](v0.39.3.md) — patch release of PR #53, PR #50, and PR #54 (@rodrigoimmaginario): the plugin's hook wrappers and MCP locator run the package's own bin when npm's global entry is a shell shim, so Claude Code hooks and the MCP server work on a Windows package install; `runtime diagnose` no longer counts its own verdict as a front-door error (CR139); the docs point a Windows reader to the installer in its own repository. No migration.
- [v0.39.2 — Input, Read the Platform's Way](v0.39.2.md) — patch release of PR #49 and PR #48 (@rodrigoimmaginario), CR194, and CR193: `runtime diagnose` stops warning every Windows install about Node; a PowerShell byte-order mark is not stored; stdin is decoded by its mark, UTF-8 or UTF-16, and `identity set` and `journey update` gain `--file`, the route around PowerShell 5.1's ASCII pipe; `package-lock.json` names the package at its version, and the release doctor checks it. No migration.
- [v0.39.1 — Pi Finds Its Node, or Says So](v0.39.1.md) — patch release of PR #47 (@rodrigoimmaginario) and CR191: a Pi opened where `node` is not on the PATH no longer exits; the Pi extension resolves Node where the hook wrappers look, so a global install needs nothing configured; when no Node resolves, one warning names the fix and `runtime diagnose` reports the `hooks.log` line. No migration.
- [v0.39.0 — The Core as a Library](v0.39.0.md) — minor release of CV24's first eight Delivery Stories: `mirror-mind/desktop`, a library entry through which a host such as Mirror Desktop 0.3 embeds this core; calls for a home's migration state, Conversations, sidebar reads, home creation, migration on request, Mirror's context, learning from open Conversations, and Journey administration, each with an explicit path and no environment. The new `exports` field closes every other deep import. No migration.
- [v0.38.1 — The Refusal Names the Way Out](v0.38.1.md) — patch release of three Change Requests, CR185, CR186, and CR187: a package with no home configured names the homes it finds and the `mirror init <name>` that selects one, and `init` adopts a home that already exists; a missing or refused OpenRouter key is one line that names the file, before anything is touched; a `stable` clone ahead only by `main`'s commits is told that `stable` is behind it, not to push or reset. No migration.
- [v0.38.0 — The Model Behind the Memories, Chosen by Measurement](v0.38.0.md) — minor release closing CV9.DS9: the model behind memories, tasks, titles, summaries, tags, reception, journal, shadow, and consolidation is Claude Haiku 5.5 at reasoning off, chosen on the eval suite with reasoning on and off and on 24 of the owner's own conversations ranked blind, where it came first on 16 of 26 surfaces. Every extraction-pin call can carry a reasoning effort, and a pin carries its own default. With CR180, summaries open with their subject, every lifecycle prompt sees the owner's name, and a framed opening is written once more. Release gate 70 of 70 probes. Rollback is one env line. No migration.
- [v0.37.0 — The Mirror Stays in the Conversation](v0.37.0.md) — minor release closing CV9.DS8 and, with CV21.DS11, CV21: on Pi, Claude Code, Codex, and Antigravity one doorman in the core puts Mirror's context before the model on every turn of Mirror Mode, all of it on the turn Mirror Mode starts and then the persona and memories each question calls for; an explicit turn loads once; one signature, `◇ persona-name`; Pi reaches L4, measured live. One parity matrix in the runtime interface contract, sourced and held by a test. Codex, Antigravity, and Grok Build need their plugin copy brought level. Migration 018, applied on its own.
- [v0.36.3 — A Skill You Invoke Is Not Something You Said](v0.36.3.md) — patch release of one Change Request, CR160, with CR159's docs: on Pi, a skill picked from the menu or typed is no longer stored as the person's words, and neither is its reply; a question asked with `/mm-mirror` is stored as the question. Pi's turns go through the rule the other runtimes have. `mirror conversations skill-turns` repairs what earlier versions stored, only on `--apply` and after a verified backup. No migration.
- [v0.36.2 — Clearing Out What Another Home Copied](v0.36.2.md) — patch release of one Change Request, CR154, finishing what v0.36.1 began: `mirror conversations imported` lists the Pi conversations an earlier version imported, by the folder each session came from and beside how many sessions the home logged live there, and `remove` deletes the ones you name, only on `--apply` and after a verified backup. `discard-current` no longer fails on a conversation a Soul Mode integration names. No migration.
- [v0.36.1 — A Home Keeps Only Its Own Pi Sessions](v0.36.1.md) — patch release of one Change Request, CR153: session maintenance imports no Pi session, so the Mirror homes on one machine no longer copy each other's Pi conversations; a home's Pi conversations are the ones the Pi extension logged into it. `PI_SESSIONS_DIR` is inert. Conversations an earlier version imported stay, and the note shows how to list them. Update every install that has a home. No migration.
- [v0.36.0 — Five Runtimes, and a Home's Extensions on Every One](v0.36.0.md) — minor release closing CV21.DS10: Grok Build is the fifth runtime, at its honest L3 through the canonical plugin in two printed steps, measured live on grok 1.0.62. With it, CV21.DS5.US2: a home's installed extensions reach Claude Code, Codex, Antigravity, and Grok Build as one generated plugin per home, chosen by measurement on all four. Three Change Requests found by use: an extension's settings file (`extensions/<id>.env`, merged under the environment for the one spawned process), a quiet exit on a closed pipe, and a `bind` that refuses what it cannot bind. No migration.
- [v0.35.0 — Four Runtimes, One Successor](v0.35.0.md) — minor release closing CV21.DS8: the Gemini CLI integration no longer ships and Antigravity stands in its place, the gate met by DS7's live L4 on agy 1.4.2. Four runtimes — Pi, Claude Code, Codex, Antigravity — named everywhere; the cutoff recorded in full, with the four hook entries a Gemini CLI user deletes and v0.34.0 as the last release that carries the integration; a retired-surface guard keeps it removed. No migration.
- [v0.34.0 — Codex Through the Canonical Plugin](v0.34.0.md) — minor release closing CV21.DS4: Codex runs Mirror through the canonical plugin, installed in two commands from a marketplace the package ships, measured live at L4 on Codex 0.163.0. The v0.32.1 wrapper wiring no longer ships; `runtime diagnose` and `runtime update` say when Codex's cached plugin copy is behind and name the re-add that brings it level. No migration.
- [v0.33.4 — A Name Is a Key](v0.33.4.md) — patch release of three first-run corrections: two from a contributor's PR #43 and CR141, which its review opened. `init --help` created a home named `--help`, `init ../escaped` created one outside `.mirror-minds`, and `init "My User"` put a space into `MIRROR_USER`; a user name is now a kebab-case key like a journey slug or a persona id, refused otherwise with a name that would work and nothing created. `identity edit` on Windows opens Notepad when no editor is named. Existing homes untouched. No migration.
- [v0.33.3 — Mirror Finds Itself Under Any Path](v0.33.3.md) — patch release of one Change Request, CR140, carried by a contributor's PR #42: Mirror read its own install path from `URL.pathname`, so a checkout or package under a path with a space or a non-ASCII character read as `Install: unknown`, the welcome card showed no update, and `runtime update` refused. The path is now a filesystem path, a guard keeps the idiom out, and an `unknown` install names the path it looked up from. On Windows, npm's global layout is recognized and npm runs with no shell, verified on Windows in CI for the two files they touch; there is still no Windows product. Affected installs update once by hand. No migration.
- [v0.33.2 — Git Runs Where Mirror Lives](v0.33.2.md) — patch release of one Change Request, CR138: on a clone install, `runtime status`, `version`, and `diagnose` describe the install from any directory, and `diagnose` grades Mirror's own tree. Git now runs only in the install's own checkout, so a checkout someone else made can no longer run a `core.fsmonitor` command through these commands; `version --start PATH` is the one explicit exception. Package installs were never exposed. No migration.
- [v0.33.1 — The Install Answers For Itself](v0.33.1.md) — patch release of six RS010 Change Requests: the welcome card, the status line, and both `release-notes` readers answer for the install that is running, never for the cwd or the repository around the install. A package asks its own tree and the npm registry, a clone its own checkout and remote; `pending` says `unknown` when it cannot tell, and a `--ref` value can no longer run a command through git. No migration.
- [v0.33.0 — One Plugin, Three Runtimes](v0.33.0.md) — minor release closing CV21.DS2: the one plugin works as it is on Claude Code, Codex, and Grok. Its MCP server starts on all three, the explicit Mirror form is recognized in every runtime's spelling, and each session is logged under its runtime with every reply beside its prompt. Also: a faster Pi session start, and notice that Gemini CLI is retired in favor of Antigravity.
- [v0.32.1 — The Release That Shipped](v0.32.1.md) — patch release that is the published CV22 release: `v0.32.0` was tagged and its publication refused by the retired-surface tripwire over one sentence in Getting Started, now rephrased. No code, behavior, or schema differs from `v0.32.0`; read that note for the release itself.
- [v0.32.0 — One Language, One Install](v0.32.0.md) — minor release that closes CV22, the TypeScript Core Port. Mirror Mind is one TypeScript package run by Node.js 24, installed with `npm install -g mirror-mind` and wired to Pi, Claude Code, Gemini CLI, or Codex by one documented step each; no Python remains in the repository or the shipped artifact; every command answers as it did. Eleven surfaces are retired with cutoffs, recorded in [Pending Cutoffs](pending-cutoffs.md), which this note carries. A new home imports only the Pi sessions newer than itself.
- [v0.31.14 — Change Request Resume](v0.31.14.md) — patch release that adds the public Ariad Workbench `change-request resume` verb so a non-terminal advanced Change Request that lost the active pointer can continue without direct SQLite edits or artificial status regression. Resume preserves the CR record, restores only the Refinement cursor, allows `implemented` to proceed to `validate` and `validated` to proceed to `done`, and keeps terminal CRs closed.
- [v0.31.13 — Explicit Append and Lifecycle Recovery](v0.31.13.md) — patch release that adds the public `conversations append` JSON boundary with atomic exact-Journey persistence, caller-owned idempotency, bounded receipts, and no runtime-session routing or late-append semantic refresh; it also restores Ariad Coherence reentry after evidence correction and pays D-016's lazy SQLite WAL recovery defect without changing model pins or prompts.
- [v0.31.12 — Bounded Authority and Journey Integrity](v0.31.12.md) — patch release that makes Builder delegation exact and durable: natural and cadence-declared story Plan authority remains generation-bound, single-use, and stopped at Navigator Validation; Driver-authored Plans survive approval; release intent grants no publication authority; transactional model-free Journey administration protects hierarchy and history; and Delivery Story Done refuses false coherence while authored roadmap status is stale.
- [v0.31.11 — Confined Operational Relative Links](v0.31.11.md) — security-preserving hotfix that resolves authored Markdown links from their containing document and accepts parent-relative traversal only when the canonical target remains inside the registered Journey root. Canonical escapes, absolute/URI/backslash targets, symlink escapes, and missing-target publication failures remain bounded; the last valid projection pair is preserved.
- [v0.31.10 — Journey Projection Contract](v0.31.10.md) — patch release that implements `mirror.journey-projections@1.0` in the Python Core with registered-root confinement, per-Journey cross-process linearizability, immutable receipts, deterministic Ariad Operational compilation, post-commit lifecycle refresh, and Extension API `1.1`. The unchanged consumer-owned probe passes against isolated synthetic state; installed-runtime acceptance remains explicit through the consumer return record.
- [v0.31.9 — Recursive Journey Hierarchy](v0.31.9.md) — patch release that removes the artificial two-level journey limit while preserving organizational-only parentage. Textual and web surfaces render arbitrary depth and full lineage; cycles are rejected; moves preserve ids, paths, and filesystem content; removal refuses parents and associated leaves without cascade. The TypeScript strangler now tracks an explicit moving Python product command by command instead of freezing user-facing evolution for the duration of the migration.
- [v0.31.8 — Windows Desktop Frame](v0.31.8.md) — patch release that makes the native Windows Frame the primary installed experience while preserving the terminal recovery path. Guided onboarding, tabbed Pi/ConPTY sessions, exact Pi `0.83.0` convergence, all-PTY update gating, fail-closed packaging, packaged Electron smoke, and real non-ASCII profile validation establish the first releasable desktop boundary; installer `0.31.0` remains unsigned and Mirror-core updates still arrive through a complete new installer.
- [v0.31.7 — Collaborative Refinement Work](v0.31.7.md) — patch release that makes the document-first Workbench usable across contributors and their Mirrors. File-first inspection now renders a standard read-only view; active CRs can record a human Driver and branch/PR Delivery reference; and a project-owned protocol defines capture, selection, planning, assignment, validation, terminal closure, return handoff, and ordinary Git conflict handling without adding a parser, shared database, lock, watcher, synchronizer, or custom Git protocol.
- [v0.31.6 — Document-First Refinement Authority](v0.31.6.md) — patch release that replaces journey-local SQLite as the shared source of Refinement truth whenever a project declares `docs/project/refinement/index.md`. The canonical Markdown index now owns RS/CR focus, order, and status; linked files own narrative and evidence; Git owns collaboration and recovery. Builder surfaces and Pi/Gemini/Codex guidance follow the project files without inspecting stale Workbench rows, while projects without the index retain the legacy SQLite path. The release preserves migrations `015`/`016`, performs no implicit migration or dual-write, and records the abandoned projection/recovery/handoff architecture as an archived experiment rather than production machinery.
- [v0.31.5 — One Code, One Package](v0.31.5.md) — maintenance patch that closes the roadmap-resolution class v0.31.4 only partially fixed. One shared resolver (`memory.builder.story_paths`) now backs both Ariad Expand and the CLI's Plan/checkpoint lookup, superseding v0.31.4's narrower, same-day `_resolve_existing_item_directory` fix (discovered independently on `kia-desktop`) while this release's own investigation traced a second occurrence of the CR048 defect (CV22.DS7). Two packages sharing a code, or a resolved package whose candidate table can't be parsed, now render a first-class `EXPAND_BLOCKED` refusal instead of resolving silently or fabricating a generic story; a new CI check makes "one code, one package" a build-time guarantee. Closes D-012 (candidate-table code-cell path sanitization) as a direct consequence of touching the functions its revisit trigger named. Reconciled with v0.31.4 by rebase, keeping its regression test as additional coverage.
- [v0.31.4 — Roadmap-Aligned Story Expansion](v0.31.4.md) — maintenance patch that stops Ariad's Builder from materializing a phantom, parallel story-package tree when expanding a Delivery Story. `_artifact_directory` derived roadmap folders from code plus title, but hand-authored roadmaps use CV/DS slugs (`cv3-build-de-producao`) no title derivation can reproduce, so expanding CV3.DS22 wrote a boilerplate `cv3-manage-100-funcional/cv3-ds22/` tree instead of the real `cv3-build-de-producao/cv3-ds22-manage-100-funcional/` node. Expand now resolves the existing folder by matching each `index.md`'s `# CODE — Title` heading to the item code (the same scan the pull inspector uses) and only falls back to title derivation for genuinely new items. Pinned by a nested-folder regression test and validated against the live kia-desktop roadmap.
- [v0.31.3 — Ariad DS-Plan Artifact Integrity](v0.31.3.md) — maintenance patch that makes the Ariad Delivery Story plan lifecycle's artifacts trustworthy. Fixes phantom `ARTIFACTS_MATERIALIZED` rows for a never-written `test-guide.md` and a falsely "updated" `index.md` (AF-002, AF-006) by driving the surface from the writer's real manifest and materializing the full package without clobbering authored content. Scaffolds every `plan_contract` section in `plan.md` (AF-003), then — after a six-lens technical review chose pure-preserve over a surgical status patcher — removes mutable status from the document so `approve-delivery-story-plan` preserves the authored plan instead of regenerating it, and flags any section left unfilled. Records the warn-not-block choice and the D-012 code-segment sanitization gap as conscious exclusions.
- [v0.31.2 — Filesystem-Safe Slug Consolidation](v0.31.2.md) — maintenance patch that fixes an `OSError [Errno 63]` (File name too long) crash in `build pull-item` when a Delivery Story candidate title is paragraph-length, by consolidating four drifted kebab `_slugify` copies into one accent-stripping, length-capped `memory.utils.kebab_slug`. Closes the same latent `mkdir` crash in the Explorer handoff writer, makes the roadmap package writer and locator derive the same path by construction, and adds an empty-slug guard. Reviewed through five personas before implementation; records D-012 (code-cell path-separator sanitization) and D-013 (the `transcript_export` slug sibling) as conscious debt.
- [v0.31.1 — Change Request Terminal Verbs](v0.31.1.md) — patch release that adds `change-request park/reject/promote` (and `refinement-story park`) to the Ariad Refinement Workbench, closing the gap that forced an off-contract production storage write for CR023. Planned through a six-persona review before implementation; fixes a latent `_flow_event` bug, a surface-marker injection path, and a progress-surface trust bug found during that review. CR023 is Navigator-confirmed reconciled; an open roadmap-parser investigation is closed in documentation; TD-002 is registered.
- [v0.31.0 — Stabilization & Robustness](v0.31.0.md) — minor release that delivers the bulk of the CV9.E2 Stabilization & Robustness epic: extraction failure isolation/quarantine and idempotency, lexical-only search degradation, explicit call timeouts, content-mediated injection fencing across all five model surfaces, an identity-write allowlist, metadata-default cost observability, and an `eval --all` release gate — plus the AI Engineering Audit P0 tier and most P1/P2 findings. CV9.E2.S2 is deferred; the model-behavior gate is satisfied by a recorded D-005 waiver.
- [v0.30.2 — Network-Appropriate Git Timeouts](v0.30.2.md) — patch release that gives runtime git push/fetch operations a 120-second network timeout instead of sharing the 2-second local-inspection timeout, fixing a false-failure report from `release-promote --push` during the v0.30.1 promotion.
- [v0.30.1 — Runtime State Home Containment](v0.30.1.md) — patch release that contains all user-scoped runtime state inside the resolved mirror home for every environment, makes unconfigured resolution fail loudly instead of writing to the homes root, unifies core and extension database resolution, contains the Pi logger's log, and teaches `runtime diagnose` to report legacy root artifacts.
- [v0.30.0 — Windows Installer Distribution](v0.30.0.md) — first public Windows installer distribution release, turning the native installer into a release-backed `.exe` asset path while keeping generated binaries out of the repository and preserving runtime self-update for existing installs.
- [v0.29.3 — Pi External-Skill Discovery Fix](v0.29.3.md) — maintenance patch that fixes Pi external-skill discovery on the `~/.mirror-minds` home layout by resolving the mirror home like the core, records the resulting cross-language resolution duplication as TD-001, and hardens the Gemini smoke test's production-DB guard.
- [v0.29.2 — Ariad Builder Flow Refinement](v0.29.2.md) — patch release that refines Ariad Builder surfaces, RS/CR display codes, Project Position orientation, artifact materialization reporting, and Delivery Done handoffs after dogfooding.
- [v0.29.1 — Windows Compatibility Hardening](v0.29.1.md) — patch release that preserves Windows-safe Claude/plugin skill paths, UTF-8 console output, explicit mojibake repair, and cross-platform path rendering.
- [v0.29.0 — Ariad Refinement Workbench](v0.29.0.md) — minor release that makes Refinement a first-class Builder Mode work field with Workbench storage, Refinement Stories, Change Requests, CR cycles, and RS review/coherence/close.
- [v0.28.0 — Ariad Delivery Story Lifecycle](v0.28.0.md) — minor release that makes Delivery Story flow a first-class Ariad Builder path with aggregate DS Plan/Validation/Review/Coherence/Done, canonical checkpoint artifacts, and visual surfaces.
- [v0.27.0 — Ariad Builder Lifecycle Runtime](v0.27.0.md) — minor release that adds the full Ariad Builder lifecycle from Pull through Done, deterministic surfaces, hard gates, story packages, validation acceptance, Debt Review, Coherence, Done, and conservative higher-autonomy cadence.
- [v0.26.2 — Web Conversation Bulk Actions](v0.26.2.md) — emergency patch release that adds selected bulk assignment and deletion to the main web Conversations view.
- [v0.26.1 — Soul Mode English Integration Copy](v0.26.1.md) — patch release that normalizes hard-coded Soul Mode integration prompts and additive identity section headings to the English baseline.
- [v0.26.0 — Soul Mode Integration](v0.26.0.md) — minor release that adds Closing Rite, multi-layer Integration Proposal, explicit confirmation-only identity integration, additive identity updates, and atomic integration records.
- [v0.25.0 — Soul Mode More Voices](v0.25.0.md) — minor release that adds active Wisdom Voice and Beauty Voice listening lenses, full voice-card utterances, source/aesthetic bridge guidance, and non-mutating Soul Mode voice boundaries.
- [v0.24.0 — Soul Mode First Ritual](v0.24.0.md) — minor release that adds the first complete Soul Mode ritual: entry, Possible Listenings, Self and Shadow listening lenses, Fruit In Maturation, Harvested Fruit, journal persistence, and pre-release web/journal refinements.
- [v0.23.0 — Durable Explorer Mode](v0.23.0.md) — minor release that completes the first Explorer Mode release with durable stories, source-evidence handoff artifacts, required surface rendering, Builder boundary routing, and session-scoped Pi mode status.
- [v0.22.1 — Mode Orientation CI Formatting](v0.22.1.md) — validation patch that preserves v0.22.0 behavior and restores green CI formatting.
- [v0.22.0 — Mode Orientation and Test Hygiene](v0.22.0.md) — minor release that adds explicit mode lifecycle, status-line orientation, transition surfaces, experimental Explorer activation, and `/mm-discard` for test-session cleanup.
- [v0.21.1 — Mirror Mode Conversation Continuity](v0.21.1.md) — patch release that prevents repeated Mirror Mode context loads from splitting one active runtime session into many conversations.
- [v0.21.0 — Scene Workspace Home](v0.21.0.md) — minor release that adds Current Scene, persisted grounded Scene Orientation, narrative global Workspace surfaces, compact all-conversations navigation, and focused orientation tabs.
- [v0.20.0 — Hierarchical Journey Organization](v0.20.0.md) — minor release that adds one-level parent journeys, hierarchical web/text rendering, journey settings title/status/parent editing, and display-only hierarchy semantics.
- [v0.19.1 — Web Console Maintenance CI Formatting](v0.19.1.md) — validation patch that preserves v0.19.0 behavior and restores green CI formatting.
- [v0.19.0 — Web Console Conversation and Journey Maintenance](v0.19.0.md) — minor release that adds web journey creation, explicit conversation deletion, bulk selected deletion, and broader selected-journey conversation visibility.
- [v0.18.2 — Conversation Journey Assignment](v0.18.2.md) — patch release that adds unassigned conversation visibility, manual/bulk journey assignment, and conservative journey backfill.
- [v0.18.1 — Empty Conversation Cleanup](v0.18.1.md) — patch release that expands cleanup to empty conversation records while preserving dry-run, approval, and backup boundaries.
- [v0.18.0 — Conversation Metadata Lifecycle](v0.18.0.md) — minor release that finalizes conversation metadata at close time and adds web metadata maintenance, historical backfill, resume scopes, and orphan cleanup.
- [v0.17.3 — Builder Guard Non-Mirror Projects](v0.17.3.md) — patch release that restricts the Builder production-clone guard to Mirror Mind checkouts so ordinary journey projects load normally.
- [v0.17.2 — Builder Guard CI Formatting](v0.17.2.md) — validation patch that keeps the Builder project-path guard behavior and restores green CI formatting.
- [v0.17.1 — Builder Project-Path Guard](v0.17.1.md) — patch release that scopes Builder Mode's production-clone guard to the selected journey project path.
- [v0.17.0 — Conversation Title Hardening](v0.17.0.md) — minor release that hardens conversation titles across runtime close, startup maintenance, Pi backfill, and bounded web batch retitle operations.
- [v0.16.2 — Runtime Update Validation Stub](v0.16.2.md) — minimal stable release used to validate the corrected v0.16.1 updater executing a normal production update.
- [v0.16.1 — Runtime Update Preflight Resilience](v0.16.1.md) — patch release that publishes the updater hardening fix for core migration drift and SQLite WAL sidecar status recovery.
- [v0.16.0 — Async Operations and Agentic Web Console](v0.16.0.md) — minor release that closes CV13 with asynchronous operation runs, durable event timelines, controlled command execution, cancellation, approval checkpoints, and a bounded agent-run prototype with a polished run console.
- [v0.15.0 — Web Operations Runner](v0.15.0.md) — minor release that closes CV13.E5 with allowlisted synchronous web operations, runtime health, database backup, conversation repair, local audit evidence, and the first visible Operations surface.
- [v0.14.0 — Conversation Intelligence](v0.14.0.md) — minor release that closes CV13.E4 with readable transcripts, explicit title improvement, configuration references, and read-only journey attachments.
- [v0.13.0 — Configuration Console](v0.13.0.md) — minor release that closes CV13.E3 with read-only Mirror/runtime configuration, masked environment boundaries, and safe journey metadata editing from Workspace.
- [v0.12.0 — Multi-Mirror and Preferences](v0.12.0.md) — minor release that closes CV13.E2 with safe local Mirror switching and per-Mirror profile/theme preferences.
- [v0.11.0 — Read-only Web Refinement](v0.11.0.md) — minor release that closes CV13.E1 with Workspace-first navigation, Identity memory drilldowns, read-only search, and refined conversation cards.
- [v0.10.17 — Update Notice Tone](v0.10.17.md) — patch release that makes update notices informational and prefixes them with ✨.
- [v0.10.16 — Update Action Routing Validation Stub](v0.10.16.md) — minimal stable release used to validate v0.10.15 update-action routing.
- [v0.10.15 — Update Action Routing](v0.10.15.md) — patch release that routes `update my Mirror` to the safe runtime updater.
- [v0.10.14 — Update Prompt Wording](v0.10.14.md) — patch release that changes the welcome update prompt to "what's new in this update?".
- [v0.10.13 — Pending Notes Ref Refresh Validation Stub](v0.10.13.md) — minimal stable release used to validate v0.10.12 pending-notes ref refresh.
- [v0.10.12 — Pending Release Notes Ref Refresh](v0.10.12.md) — patch release that safely fetches stable refs before rendering cumulative pending release notes.
- [v0.10.11 — Pending Notes Prompt Validation Stub](v0.10.11.md) — minimal stable release used to validate v0.10.10 welcome pending-notes prompt routing.
- [v0.10.10 — Pending Release Notes Prompt](v0.10.10.md) — patch release that routes welcome update prompts to cumulative pending release notes.
- [v0.10.9 — Release Awareness Validation Stub](v0.10.9.md) — minimal stable release used to validate v0.10.8 welcome update detection.
- [v0.10.8 — Welcome Release Awareness](v0.10.8.md) — patch release that refreshes stable-channel welcome awareness after cached up-to-date checks.
- [v0.10.7 — Runtime Operations Documentation](v0.10.7.md) — patch release that reconciles updater and release-management docs/help with the current command surface.
- [v0.10.6 — Update Status Recovery](v0.10.6.md) — patch release that retries update status after safely bootstrapping an unavailable production database.
- [v0.10.5 — Cumulative Release Notes](v0.10.5.md) — patch release that lists every pending release note for users more than one version behind.
- [v0.10.4 — Pi Startup Lifecycle](v0.10.4.md) — patch release that fully detaches Pi startup maintenance so the startup counter can complete.
- [v0.10.3 — Pi Startup Maintenance](v0.10.3.md) — patch release that moves expensive Pi conversation maintenance out of the blocking startup path.
- [v0.10.2 — Fresh Release Awareness](v0.10.2.md) — patch release that refreshes visible welcome update notices when stable advances again inside the cache window.
- [v0.10.1 — Welcome Startup Clarity](v0.10.1.md) — patch release that clarifies Pi startup status and gives new-version availability stronger welcome emphasis.
- [v0.10.0 — Web Visibility](v0.10.0.md) — closes CV9.E6 with read-only Identity and Workspace perspectives, object detail with Source Context, and a Pi Builder journey-association repair path.
- [v0.9.1 — Welcome Release Awareness](v0.9.1.md) — patch release that makes stable release availability visible in the welcome and Pi status bar through network-tolerant update awareness.
- [v0.9.0 — Self-Update Done](v0.9.0.md) — closes the release-aware self-update arc with stable update notices, release-note skill parity, release promotion doctor, controlled promotion, and fresh-user stable smoke evidence.
- [v0.8.0 — Stable Self-Update Foundation](v0.8.0.md) — first prospective stable-channel release; establishes safe runtime self-update, updater self-recovery, stable/main channels, welcome version visibility, and runtime release-note access.

---

## Historical Boundary

- Pre-adoption versions: `v0.2.0` through `v0.7.0`, recorded by Git tags and worklog entries.
- Process adoption: CV9.E5.
- First prospective major boundary: CV9 completion may become `v1.0.0`, because CV9 is the public-release readiness boundary for Mirror Mind 1.0.

Retroactive release notes may be added later as archival work, but they are not required for the process to operate from here forward.
