---
digest: >
  v0.32.1 is the published CV22 release. v0.32.0 was tagged, and its
  publication was refused by the project's own retired-surface tripwire:
  one sentence in Getting Started named the retired Python invocation by
  its literal form, which only the history and release notes may do. The
  sentence is rephrased; nothing else changed. Everything v0.32.0's note
  says is true of this version: install with `npm install -g mirror-mind`,
  or upgrade a clone with the five lines, which include `npm link` and
  `mirror runtime migrate`.
---

# v0.32.1 — The Release That Shipped

**Date:** 2026-10-11

## Highlights

- **This is the CV22 release.** Read [v0.32.0 — One Language, One Install](v0.32.0.md)
  for what it is; this note only says why the number ends in 1.
- **One sentence changed**, in `docs/getting-started.md`: the paragraph telling a clone user
  what the previous updater does no longer spells out the retired interpreter invocation.
- **No code, no behavior, no schema** differs from `v0.32.0`.

## Where We Started

`v0.32.0` was tagged at `78dd5836` and `stable` moved there. The publish workflow, which
stages the package from CI for a maintainer to approve, runs the retired-surface
tripwire first, and it refused: `docs/getting-started.md:385 mentions \`uv run python\`,
retired by CV22.DS10.TS5`. The sentence had been added after the upgrade rehearsal,
committed as a docs-only change, and tagged without re-running the guard; the tests
workflow skips docs-only pushes, so nothing ran it before the tag.

## What Changed

The project's rule is that a tag never moves and the doctor refuses a tag that is not at
`HEAD`, so the fix is a patch: the sentence now reads "the old interpreter form of the
command now fails with `No module named memory.__main__`", which says the same thing to
the person it is for without naming the form the guard forbids. The guard was right: a
Getting Started page is not the place to teach the retired invocation, even in the past
tense.

`v0.32.0` remains a tag in the repository and was never published to npm.

## Conscious Exclusions

- Moving the `v0.32.0` tag to the fix. It would have given a cleaner version list at the
  cost of breaking, by hand, the rule the release tooling encodes, on the first release
  made under it.

## What We Learned

A docs-only commit between the last green check and the tag is still a commit. The
retired-surface guard belongs in the Docs workflow too, so a docs-only push cannot pass
CI while carrying what the publish gate refuses; that is a Change Request, not this patch.

## Next Horizon

Publication through the staged route, then CV22 closes.
