---
digest: >
  v0.33.4 is a maintenance release of three first-run corrections, two from a
  contributor's PR #43 and one Change Request, CR141, that its review opened.
  `mirror init --help` created a home named `--help`; `init ../escaped` created
  one outside `.mirror-minds`; `init "My User"` put a space into `MIRROR_USER`
  for every wiring command. 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. And `identity edit` on Windows opens Notepad when no editor
  is named, instead of failing to start nano. Existing homes are untouched; no
  migration.
---

# v0.33.4 — A Name Is a Key

**Date:** 2026-10-17

## Highlights

- **`init` takes a kebab-case key for a user name, and nothing else** (CR141, from the
  review of PR #43). `init ../escaped` created `~/escaped`, outside the directory the
  product owns; `init "My User"` put a space into `MIRROR_USER`, which every wiring
  command `init` prints then carried; `init a/b` nested. Each is refused before anything
  is created, with the sentence `identity set` already uses: the consequence, the rule,
  and a key that would work.
- **`init --help` no longer creates a home named `--help`** (PR #43 by
  @rodrigoimmaginario). The command has no flags; a word that starts with `-` gets the
  usage line and exit 2.
- **`identity edit` opens Notepad on Windows when no editor is named** (PR #43). The
  order is unchanged, `EDITOR`, then `VISUAL`, then the platform's default: `notepad` on
  Windows, where nano exists only inside Git Bash, `nano` elsewhere.
- **Existing homes are untouched.** `init` only creates; a home with another kind of name
  keeps it.

## Where We Started

A contributor's first run on Windows met two small things and sent a PR for each:
`init --help` created a home, and `identity edit` with no `EDITOR` set failed to start
nano. The first was not a Windows bug at all; it reproduced on macOS in a second.

Its review asked what else `init` accepted. The answer was anything. The name becomes
`~/.mirror-minds/<user>` and the value of `MIRROR_USER`, and the repository had already
decided, in CR104, that a key which goes into paths and shell commands must be one plain
word a shell cannot split, substitute, or read as an option. Journey slugs and persona
ids had met that rule since `v0.32.0`. The user name was the last key of its kind that
did not.

## What Changed

**One sentence for every key.** `newUserNameProblem` joins `newIdentityKeyProblem` in
`ts/src/identity/identityKey.ts`, both over one builder, so `init`, `identity set`,
`identity edit`, and `seed` refuse a non-key the same way. The key is printed escaped: a
name with a newline or a `;` in it cannot forge output or a command. `runInit` asks before
`initUserHome`, so a refusal leaves `$HOME` as it was: no home, no identity directory, no
config file.

**The test is the PR's, widened.** `../escaped`, `My User`, `a/b`, and an accented name go
through the real front door; each asserts the exit, the sentence with its suggestion, and
an empty home afterwards. PR #43's own `init --help` test stands beside it.

**Notepad, with its evidence still owed.** The platform is a dependency of
`resolveEditor`, so both defaults are tested on every OS. The PR verified the Windows
round trip on an unchanged buffer, which prints `No changes detected.` whether Notepad
blocked or returned at once; early Windows 11 Notepad did return at once. A round trip
that changes the buffer is asked for on the PR, and the default ships as the better of
the two available answers: nano could not start at all.

### What you will notice

- A first `mirror init` with a name that is not a plain lowercase word is refused with
  a name that would work. `mirror init your-name`, as Getting Started has always said,
  is unchanged.
- On Windows, `mirror identity edit …` opens Notepad instead of failing.
- Nothing else.

## Upgrading

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

There is no database migration and no runtime wiring change. If `v0.33.3`'s note applied
to you, a Mirror under a path with a space or an accent, and you have not yet taken its
one manual update, take it first; from `v0.33.3` on, `runtime update` works.

## Conscious Exclusions

- **Selecting an existing home by name.** `MIRROR_USER` pointing at a home created
  before this rule, under whatever name, still selects it. Only creation is constrained.
- **`init`'s wiring lines on Windows.** They print `ln -s`, which Windows has no answer
  to; that waits for the runtimes to be verified there, as the contributor's PR says.
- **Counting verdicts as front-door errors** (CR139), unchanged since `v0.33.2`.

## What We Learned

A fix for an instance invites the question "what else?", and the cheapest moment to ask
it is the review. The `-` check was right; the class was one line away, and the rule
already existed with its sentence, its escaping, and its tests. When a repository has
decided something once, the second instance should cost a reference, not a decision.

## Next Horizon

CR139, the verdict loop, is the visible next step in RS010. The contributor's Windows
series, if it comes, begins with the suite on `windows-latest`.
