---
digest: >
  v0.44.2 is a patch release that adds one read for a host that embeds the Core. `readJourney`
  answers one Journey's content whole, the text the runtime delivers to every turn, where the
  Journey tree carries only a collapsed `## Description` (CR217). It is read-only, additive, and
  leaves `readJourneyTree` and `DESKTOP_API_VERSION` as they were. No schema change, no
  migration, and no model or prompt change.
---

# v0.44.2 — A Journey's Content, Read Whole

**Date:** 2026-11-21

## Highlights

- **`readJourney(dbPath, { journeyId })`**
  ([CR217](../project/refinement/rs010-cv22-oracle-and-port-hygiene/cr217-a-host-cannot-read-a-journeys-content-whole.md),
  PR #82). It answers `{ id, name, content, updatedAt }`, where `content` is the identity row
  exactly as stored, with its sections, lists and paragraph breaks, or an empty string when the
  Journey has none. An unknown Journey is refused `unknown_journey`, a malformed request
  `invalid_request`.
- **The tree is unchanged.** `readJourneyTree` and its collapsed `description` behave as before,
  so sidebars and listings keep working. The name rule (`display_name`, then the first heading,
  then the key) is now one function shared by both reads.
- **Read-only, like every CV24.DS3 read.** It refuses a home that is not `current`, never
  migrates, writes nothing and never reads `MIRROR_HOME`.
- No schema change, no migration. `DESKTOP_API_VERSION` stays 1: the name is new, none is
  removed or changes meaning.

## Where We Started

A host's Journey Briefing panel showed a Journey's briefing from the tree's `description`: one
section, cut at the next `## `, collapsed into a single line. A Journey whose content carries a
field, its trails and a current focus showed one flattened paragraph, although the runtime
delivers the whole content to the agent on every turn. No call answered with it.

## What Changed

`readJourney` sits in `ts/src/conversation/hostReads.ts`, beside the tree, and `mirror-mind/desktop`
re-exports it. It is a separate read, not a field on each tree node, because the tree is read on a
host's turn path, on every sidebar reload and on deletion, and a host writes it to its cache each
time. In the Navigator's home the 67 Journeys' contents add up to about 160 KB (2.4 KB on average,
26 KB at most), which only one panel needs.

## Conscious Exclusions

- **Cutting or rendering the content.** Which lines a host shows is the host's decision; the Core
  answers the text the runtime delivers.
- **A CLI verb.** `mirror identity get journey <id>` already prints the content.

## Upgrading

```bash
mirror runtime update
```

Nothing changes for the terminal. A host that embeds the Core moves its pin to 0.44.2 to use the
new read.

## Next Horizon

CR208, the doorman delivering a matching attachment whole on every turn; CR209, a journey for one
session; CR212 and CR214; and the rest of the way to 1.0 in the
[CV9 index](../project/roadmap/cv9-mirror-1-0/index.md).
