mirror-mind 0.38.0 → 0.39.0

package/bin/loader.js

@@ -24,34 +24,52 @@
 // stands on; `scripts/smoke_npm_package.sh` runs both bins from a real global
 // install on CI's Node 24.
 //
-// The warning filter below is the shim's own copy, because the hook emits its
+// The warning filter is the shim's own copy, because the hook emits its
 // ExperimentalWarning before the core's filter can be imported through it.
+// `boot` installs it; `registerTypeStripping` alone does not (CV24.DS1).
 
 import { readFileSync } from "node:fs";
 import { registerHooks, stripTypeScriptTypes } from "node:module";
 import { fileURLToPath } from "node:url";
 
-process.removeAllListeners("warning");
-process.on("warning", (warning) => {
-  if (warning.name === "ExperimentalWarning") return;
-  process.stderr.write(`${warning.name}: ${warning.message}\n`);
-});
-
 const packageRoot = new URL("../", import.meta.url).href;
+const REGISTERED = Symbol.for("mirror-mind.typeStripping");
 
-registerHooks({
-  load(url, context, nextLoad) {
-    if (url.startsWith(packageRoot) && url.endsWith(".ts")) {
-      const source = readFileSync(fileURLToPath(url), "utf8");
-      return {
-        format: "module",
-        source: stripTypeScriptTypes(source, { mode: "strip" }),
-        shortCircuit: true,
-      };
-    }
-    return nextLoad(url, context);
-  },
-});
+/**
+ * Register the load hook that strips types for `.ts` files under this package
+ * root. Idempotent per package root, so the bins and the library entry
+ * (`lib/desktop.js`, CV24.DS1) can both call it in one process.
+ *
+ * It does nothing to the process's warnings: a library entry runs inside a
+ * host that owns them. Only `boot`, which owns its process, filters them.
+ */
+export function registerTypeStripping() {
+  if (!globalThis[REGISTERED]) globalThis[REGISTERED] = new Set();
+  const roots = globalThis[REGISTERED];
+  if (roots.has(packageRoot)) return;
+  roots.add(packageRoot);
+  registerHooks({
+    load(url, context, nextLoad) {
+      if (url.startsWith(packageRoot) && url.endsWith(".ts")) {
+        const source = readFileSync(fileURLToPath(url), "utf8");
+        return {
+          format: "module",
+          source: stripTypeScriptTypes(source, { mode: "strip" }),
+          shortCircuit: true,
+        };
+      }
+      return nextLoad(url, context);
+    },
+  });
+}
+
+function filterExperimentalWarnings() {
+  process.removeAllListeners("warning");
+  process.on("warning", (warning) => {
+    if (warning.name === "ExperimentalWarning") return;
+    process.stderr.write(`${warning.name}: ${warning.message}\n`);
+  });
+}
 
 /**
  * Import the entry at `entryPath` (relative to the package root) and run its
@@ -62,6 +80,9 @@ registerHooks({
  * @returns {Promise<number>}
  */
 export async function boot(entryPath) {
+  // The filter first: registering the hook emits its own ExperimentalWarning.
+  filterExperimentalWarnings();
+  registerTypeStripping();
   const { runAsEntry } = await import(new URL(entryPath, packageRoot).href);
   return runAsEntry();
 }

package/docs/releases/index.md

@@ -12,6 +12,8 @@ Future release notes should use the structure defined in [Release Notes](../proc
 
 ## Releases
 
+- [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.

package/docs/releases/v0.33.3.md

@@ -111,7 +111,8 @@ hand:
 
 ```bash
 # a clone: in the checkout
-git pull --ff-only
+git fetch origin
+git merge --ff-only origin/stable   # origin/main if the clone follows main
 # a package
 npm install -g mirror-mind@latest
 ```
@@ -124,6 +125,13 @@ mirror runtime update          # or: npm install -g mirror-mind
 
 There is no database migration and no runtime wiring change.
 
+*Corrected on 2026-10-29:* the clone line first read `git pull --ff-only`. A clone follows
+`stable` unless you chose `main`. On `main`, that command pulls past the release, so the
+next `runtime update` refused with `plan: local commits present` (CR186). If that happened
+to you, your checkout is fine. Every later release contains the commits it pulled, so
+`runtime update` works again from the next release on. `mirror runtime channel main`
+follows `main` instead.
+
 ## Conscious Exclusions
 
 - **A Windows product.** REFERENCE.md's platform envelope stands: POSIX. The Windows

package/docs/releases/v0.38.1.md

@@ -0,0 +1,152 @@
+---
+digest: >
+  v0.38.1 is a patch release of three Change Requests, CR185, CR186, and CR187, two of
+  them from Leandro Garcia's report on PR #42. Where Mirror refused to go on, it now
+  says what to do next. 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 the key
+  goes in, said before anything is touched. A `stable` clone that took `main`'s commits
+  early is told that `stable` is behind it, not to push or reset. No migration.
+---
+
+# v0.38.1 — The Refusal Names the Way Out
+
+**Date:** 2026-10-30
+
+## Highlights
+
+- **A package with no home configured says where it looks and what to run**
+  ([CR185](../project/refinement/rs010-cv22-oracle-and-port-hygiene/cr185-a-package-with-no-home-configured-does-not-say-where-it-looks.md)).
+  The error names the homes it finds under `~/.mirror-minds`, the `mirror init <name>`
+  that selects one, and the file that command writes. `mirror init <name>` now adopts a
+  home that already exists, changing nothing in it, so moving from a clone to the
+  package is one command. The bare `mirror` names the home too.
+- **A missing OpenRouter key stops the command before it touches anything**
+  ([CR187](../project/refinement/rs010-cv22-oracle-and-port-hygiene/cr187-a-missing-openrouter-key-crashes-three-commands-with-a-stack-trace-that-names-no-file.md)).
+  The six commands that cannot work without it (`consult`, `journal`, `week plan`,
+  `descriptor generate`, `consolidate scan`, and `shadow scan`) refuse in one line that
+  says what was not done and where the key goes, and exit 2. `journal` says the entry
+  was not saved, instead of crashing after it had copied the database into a snapshot.
+  A key that OpenRouter refuses is one line too. `runtime status`, `runtime diagnose`,
+  and a degraded search say when the key is missing.
+- **A `stable` clone ahead only by `main`'s commits is told that `stable` is behind it**
+  ([CR186](../project/refinement/rs010-cv22-oracle-and-port-hygiene/cr186-runtime-update-reads-main-s-commits-as-local-work.md)).
+  The ways out are `runtime channel main` or the next release, in the words a package
+  install already used. It is no longer told to push commits the remote already has, or
+  to reset its code below a database that may be newer than `stable`'s. Real local work
+  keeps the push-or-reset refusal.
+- No migration, and no model or prompt change.
+
+## Where We Started
+
+v0.33.3 fixed installs under a non-ASCII path, which Leandro Garcia reproduced on PR #42.
+On 2026-10-17 he came back with two bumps he met while following the update
+instructions:
+
+- Moving to the package, `runtime update` stopped with "Mirror home is not configured"
+  and did not say where the package looks.
+- On a clone, the release notes' manual step, `git pull --ff-only`, pulled `main` past
+  the release. The next `runtime update` refused with `local commits present` and
+  "push or reset", for commits that were not his.
+
+The answer came on 2026-10-29, twelve days late. The v0.33.3 notes were corrected to
+`git fetch origin` and `git merge --ff-only origin/stable`. CR185's review turned up a
+third refusal of the same kind: with no `OPENROUTER_API_KEY`, `consult`, `journal`, and
+`week plan` crashed with a stack trace that named no file, and `journal` lost the entry.
+
+## What Changed
+
+**A home the error can name (CR185).** One module now owns the homes root,
+`~/.mirror-minds`, and decides what counts as a home there: a directory with a non-empty
+`identity/` or a `memory*.db` file. The not-configured error is one line everywhere it
+appears. It ends with the command that finishes the job:
+
+```text
+Mirror home is not configured. To use the home at <root>/<name>, run: mirror init <name> (it writes MIRROR_USER=<name> to <config>).
+```
+
+There are forms for several homes, for a home whose name `init` would refuse, and for
+none. `init <name>` on an existing home copies nothing and changes nothing in it. It
+writes `MIRROR_USER` to an owner-only config file when no home is selected, and prints
+only what is left to do: the key, `mirror seed` when there is no database, and the
+runtime wiring. Selecting the only home automatically was considered and refused. A
+silent fallback once caused the wrong-session export incident, so one explicit command,
+whose effect is kept in a file, is the honest minimum.
+
+**A key checked before anything is touched (CR187).** The key used to be read at the
+first model call, so a failing command could already have done work. A keyless
+`journal` copied the whole database into its pre-write snapshot, then crashed. Now the
+six commands that cannot work without the key check it before the database opens. Any
+other command that meets a missing key is answered by the front door's handler: one
+line, no stack trace. All the sentences come from one place and name the file the
+install reads its configuration from. When that file does not exist yet, the line says
+to create it readable only by its owner. A key that OpenRouter refuses (HTTP 401 or 403)
+gets its own line, whether a chat call or an embedding call met it. `consolidate apply`
+is not checked up front, because only a merge proposal embeds.
+
+**The channel behind the clone (CR186).** The plan stage of `runtime update` counted
+every commit in `origin/stable..HEAD` as the person's own. Releases only fast-forward
+`stable` to `main`, so one more local count tells the two cases apart. When every commit
+past `stable` is already on `origin/main`, the clone's channel is behind it. The update
+then refuses the way the package lane refuses a channel behind the installed version,
+and in its words: "A downgrade is refused: migrations do not run backwards.", then
+`runtime channel main`, or staying until the next release. The captured Change Request
+also offered a reset to `origin/stable`; it was dropped. `main`'s code can migrate the
+database when it opens it, and `stable`'s core refuses a database newer than itself. One
+function now reads where a clone stands, for both the update plan and the welcome card,
+which had counted two different ways. A count that cannot run reads as local work, so
+real work is never mistaken for published work.
+
+**Reviewed before code, validated by hand.** Each plan was reviewed through persona
+lenses before any code was written: five for CR185, four each for CR186 and CR187. The
+Navigator validated each change on a natural route: CR185 and CR187 as a package user,
+the lane Leandro was on, and CR186 in a scratch clone ahead of `stable`. CR186's reviews
+turned its plan around. It had proposed reporting the clone as up to date, until the
+engineer found the package lane already refusing the same state.
+
+## Upgrading
+
+```bash
+mirror runtime update          # or: npm install -g mirror-mind@latest
+```
+
+No migration, and nothing to configure. Moving from a clone to the package with a home
+that already exists: `mirror init <your-name>` now selects it without changing anything
+in it, and says what is left, such as the key. No skill, plugin, or extension changed in
+this release, so a reinstall line the updater prints for Codex, Antigravity, or Grok
+Build only moves the version number.
+
+## Conscious Exclusions
+
+- Transport failures other than a refused key (a timeout, an outage, a rate limit, a
+  server error) still crash the commands that call a model with a stack trace, and
+  `journal` still loses the entry
+  ([CR188](../project/refinement/rs010-cv22-oracle-and-port-hygiene/cr188-a-provider-outage-crashes-the-commands-that-call-a-model-with-a-stack-trace.md)).
+- Extraction at session end with no key is unchanged, and a configuration error still
+  counts as an attempt, which can quarantine a conversation
+  ([CR178](../project/refinement/rs010-cv22-oracle-and-port-hygiene/cr178-a-configuration-error-counts-as-an-extraction-attempt-and-nothing-releases-a-quarantine.md)).
+- With a wrong key, `descriptor generate` still prints "skipped (empty response)" for each
+  persona. That line is golden-graded.
+- `runtime update --check` still reports `local_ahead` for a clone ahead of `stable` by
+  `main`'s commits, where a package reports `channel_behind`.
+- A `main`-channel clone ahead by commits on another pushed branch keeps the
+  push-or-reset refusal.
+
+## What We Learned
+
+A validation route is code too, and it has to be run before it is handed over. CR186's
+route, run first by the agent, never reached the plan: a `node_modules` symlink made the
+scratch tree dirty, because `.gitignore`'s `node_modules/` matches only a directory.
+CR187's first route could not prove that no snapshot was taken, because `ls -l` shows
+minutes. Both were caught before the Navigator ran them.
+
+CI runs the suite under `MEMORY_ENV=test`. CR185's first push failed a test that had
+assumed `memory.db`. The suite is now run that way before every push.
+
+The same state deserves the same words. CR186's answer was already written, in the
+package lane's refusal of a channel behind the installed version.
+
+## Next Horizon
+
+CR188, the transport failures, is the next refusal of this kind. CV9, Mirror Mind 1.0,
+continues, and when its done condition is met the release is `v1.0.0`.

package/docs/releases/v0.39.0.md

@@ -0,0 +1,110 @@
+---
+digest: >
+  v0.39.0 is a minor release that ships CV24's first eight Delivery Stories: a library
+  entry, `mirror-mind/desktop`, through which a host such as Mirror Desktop 0.3 embeds
+  this core in its own Node process instead of spawning a CLI. Twenty-five calls and refusal
+  classes, beside `DESKTOP_API_VERSION`, cover a
+  home's migration state, Conversations, sidebar reads, home creation, migration on
+  request, Mirror's context for a turn, learning from open Conversations, and Journey
+  administration, each taking an explicit path and reading no environment. The package
+  gains an `exports` field, which closes every deep import other than the new entry. The
+  terminal, the bins and the hooks behave as before. No migration, and no model or prompt
+  change.
+---
+
+# v0.39.0 — The Core as a Library
+
+**Date:** 2026-10-31
+
+## Highlights
+
+- **`mirror-mind/desktop`, a library entry for a host**
+  ([CV24](../project/roadmap/cv24-embeddable-core-for-mirror-desktop/index.md)). Imported by
+  package name from a host's `node_modules`, with no flags: the entry registers the bins'
+  type-stripping hook itself. Everything a host may call is re-exported there by name, with
+  `DESKTOP_API_VERSION = 1`; a name not in that file is not part of the contract.
+- **Eight stories, one rule.** Every call takes an explicit database or home path, never reads
+  `MIRROR_HOME`, `MIRROR_USER`, `DB_PATH` or a key from the environment, never migrates as a side
+  effect, and refuses a database that is not `current` before opening it for writing.
+- **Custody chosen per write, with a decision for each.** Conversation writes go through a
+  narrowed handle instead of a per-write snapshot; a home is created beside its target and renamed
+  into place; a home migrates only behind a uniquely named, verified backup the core never deletes.
+- **Breaking for deep imports only.** The package now declares `exports` with `./desktop` and
+  `./package.json`. Any other `import "mirror-mind/…"` path that resolved before no longer does.
+  The `mirror` and `mirror-hook` bins are unaffected.
+- No migration, and no model or prompt change, so the model-behavior release gate does not apply.
+
+## Where We Started
+
+Decision CV22.DS10.TS1 left Mirror Desktop outside the TypeScript migration: it kept calling the
+Python core through the retired Journey administration and a catalog script. On 2026-10-28 Mirror
+Desktop decided to follow this core instead. It froze its 0.2 line on Python and opened a 0.3 line
+that hosts the core in its own Node process, on its own home.
+
+That host could not use the CLI's way in. It runs from `node_modules`, where Node refuses to strip
+TypeScript types. A shell that starts it may export another home's `MIRROR_HOME`. It writes on every
+turn of a Conversation that never ends. And it has to ask the person before a home is migrated,
+while every open through the front door migrates first.
+
+## What Changed
+
+The contract grew one story at a time on `desktop/library-seam-1a`, each with its spec first, and
+merged as PR #52.
+
+- **DS1, inspect a home without migrating.** `inspectMigrationState` reports `missing`,
+  `not_mirror`, `current`, `pending` or `ahead`, with the pending list. It shares its three
+  ledger readers with `ensureMigratedOnOpen`, so what it calls pending is exactly what an open
+  would apply. The loader became `boot` plus an idempotent `registerTypeStripping`; only `boot`,
+  which owns its process, filters warnings.
+- **DS2, Conversations as calls.** `ensureConversation`, `appendConversationMessages` (the
+  `conversations append` contract, byte for byte), `renameConversation` and
+  `rebindConversationJourney`, written through `openDatabaseForConversationWrites`. That handle
+  prepares only a single SELECT, INSERT … VALUES into three tables, and an UPDATE of four
+  `conversations` columns by id. The per-write `VACUUM INTO` measured about 0.9 s on a 108 MB
+  home, too much for every turn.
+- **DS3, Journey reads.** `readJourneyTree` (a new contract in the stored sibling order, not a
+  revival of the retired registry dump), `listJourneyConversations` and `inspectConversation`,
+  read-only.
+- **DS4, create a home.** `createHome` copies the templates with the person's name, bootstraps,
+  and seeds in a staging directory, renaming it into place only when the home reads `current`.
+  It never writes `~/.config/mirror/env`.
+- **DS5, migrate on request.** `migrateHome` applies exactly the pending list the person was
+  shown, under the bootstrap lock, behind a backup that is quick-checked, hashed, and read back as
+  the same pre-image.
+- **DS6, Mirror's context as a call.** `deliverMirrorContext` is the doorman for a host's turn,
+  with the key as an argument and Mirror Mode from the first turn; each provider call is tried
+  once within its own bound. Its write is `mirror doorman`'s, behind the front door's snapshot.
+- **DS7, learning from an open Conversation.** `learnFromConversations` extracts the stretch an
+  idle, unended Conversation gained since its `learned_through` watermark, in bounded pieces,
+  with the terminal's prompts, and never ends it.
+- **DS8, Journey administration as calls.** `addJourney`, `setJourneyProjectPath`, `moveJourney`
+  and `deleteJourney` port Python 0.31.14's administration, so the requests Desktop 0.2 sent keep
+  their meaning. `updateJourney` is new: it edits a Journey's name, description and status, and
+  refuses `journey_changed` when the row changed since the host read it.
+
+Existing code changed only where the entry needed it: the loader, three exported readers, two
+`export` keywords in `extraction.ts`, the tarball guard (`lib/` allowed, `lib/desktop.js`
+required), and `package.json`. No existing test changed. The npm smoke installs the package and
+imports the entry from a host project for DS1 to DS5.
+
+## Conscious Exclusions
+
+- **Renaming a Journey's slug.** The slug keys Conversations, memories and tasks; renaming it is a
+  migration, not a call.
+- **A Journey's icon and color, and a receipt ledger for Journey calls.**
+- **The front door's own migration custody.** `ensureMigratedOnOpen` still overwrites one fixed
+  backup; giving it DS5's custody is a separate decision.
+- **Installed-package smoke for DS6 to DS8.** DS6 and DS7 need a provider key. DS8 is exercised
+  end to end by Mirror Desktop's real-host test; a keyless smoke probe is a cheap follow-up.
+
+## What We Learned
+
+A library entry is a stricter consumer than a CLI. Every assumption the bins could make about
+their own process — environment, warnings, migrate-on-open, a snapshot per write — had to become
+an explicit argument or a decision. The retired-surfaces sweep also caught the port twice naming a
+retired verb in comments, which says the sweep is doing its job on new files.
+
+## Next Horizon
+
+Mirror Desktop moves its pin from a branch tarball to this release, then its first 0.3 alpha. CV24
+stays open for the pieces that alpha's use asks for.

package/lib/desktop.js

@@ -0,0 +1,72 @@
+// `mirror-mind/desktop` — the core's library entry for Mirror Desktop. CV24.DS1.
+//
+// Mirror Desktop hosts this core in its own Node process and imports it from
+// `node_modules`, where Node refuses to strip TypeScript types. So this entry
+// registers the same type-stripping hook the bins use, and only then imports
+// the TypeScript modules -- dynamically, because a static `export ... from
+// "./x.ts"` would be loaded before the hook exists.
+//
+// Everything Desktop may call is re-exported here BY NAME. A name missing from
+// this file is not part of the contract, whatever the TypeScript tree holds.
+// `DESKTOP_API_VERSION` changes when a name is removed or changes meaning.
+
+import { registerTypeStripping } from "../bin/loader.js";
+
+registerTypeStripping();
+
+const migrationReport = await import("../ts/src/db/migrationReport.ts");
+const conversations = await import("../ts/src/conversation/hostCalls.ts");
+const reads = await import("../ts/src/conversation/hostReads.ts");
+const homes = await import("../ts/src/init/createHome.ts");
+const migration = await import("../ts/src/db/migrateHome.ts");
+const context = await import("../ts/src/mirror/deliverContext.ts");
+const learning = await import("../ts/src/conversation/learnFromConversations.ts");
+const journeys = await import("../ts/src/journey/journeyCalls.ts");
+
+export const DESKTOP_API_VERSION = 1;
+export const inspectMigrationState = migrationReport.inspectMigrationState;
+
+// CV24.DS2: Conversations as calls. Each opens only a `current` database,
+// never migrates, and writes through the narrowed Conversation handle.
+export const ensureConversation = conversations.ensureConversation;
+export const appendConversationMessages = conversations.appendConversationMessages;
+export const renameConversation = conversations.renameConversation;
+export const rebindConversationJourney = conversations.rebindConversationJourney;
+export const DatabaseNotCurrentError = conversations.DatabaseNotCurrentError;
+export const ConversationCallRejectedError = conversations.ConversationCallRejectedError;
+
+// CV24.DS3: the reads a sidebar is built from. Read-only, `current` homes only.
+export const readJourneyTree = reads.readJourneyTree;
+export const listJourneyConversations = reads.listJourneyConversations;
+export const inspectConversation = reads.inspectConversation;
+
+// CV24.DS4: create a complete, seeded home at an explicit path, all or nothing.
+// Writes nothing outside it, never the machine-wide ~/.config/mirror/env.
+export const createHome = homes.createHome;
+export const CreateHomeRejectedError = homes.CreateHomeRejectedError;
+
+// CV24.DS5: migrate a home on request, applying exactly the pending list the
+// person was shown, behind a uniquely named, verified, retained backup.
+export const migrateHome = migration.migrateHome;
+export const MigrateHomeRejectedError = migration.MigrateHomeRejectedError;
+
+// CV24.DS6: Mirror's context for a host's turn -- the doorman as a call. The
+// key is an argument; nothing is read from the environment. A Conversation is
+// in Mirror Mode from its first turn.
+export const deliverMirrorContext = context.deliverMirrorContext;
+export const forgetMirrorContext = context.forgetMirrorContext;
+export const MirrorContextRejectedError = context.MirrorContextRejectedError;
+
+// CV24.DS7: learn from a host's idle Conversations without ending them -- the
+// stretch each gained since it was last learned from. The key is an argument.
+export const learnFromConversations = learning.learnFromConversations;
+export const LearningRejectedError = learning.LearningRejectedError;
+
+// CV24.DS8: Journeys as calls -- create, edit, move, set a project path,
+// delete -- each answering with the tree `readJourneyTree` reads.
+export const addJourney = journeys.addJourney;
+export const updateJourney = journeys.updateJourney;
+export const setJourneyProjectPath = journeys.setJourneyProjectPath;
+export const moveJourney = journeys.moveJourney;
+export const deleteJourney = journeys.deleteJourney;
+export const JourneyCallRejectedError = journeys.JourneyCallRejectedError;

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "mirror-mind",
-  "version": "0.38.0",
+  "version": "0.39.0",
   "description": "Mirror Mind: a local-first memory and identity framework for agentic AI runtimes (Pi, Claude Code, Codex, Antigravity)",
   "license": "MIT",
   "repository": {
@@ -27,8 +27,13 @@
     "mirror": "bin/mirror.js",
     "mirror-hook": "bin/mirror-hook.js"
   },
+  "exports": {
+    "./desktop": "./lib/desktop.js",
+    "./package.json": "./package.json"
+  },
   "files": [
     "bin",
+    "lib",
     "ts/src",
     "templates",
     "docs/releases",

package/plugins/mirror-mind/.claude-plugin/plugin.json

@@ -1,6 +1,6 @@
 {
   "name": "mirror-mind",
-  "version": "0.38.0",
+  "version": "0.39.0",
   "description": "Mirror Mind — local-first memory and identity for agentic runtimes.",
   "author": {
     "name": "Mirror Mind"

package/plugins/mirror-mind/plugin.json

@@ -1,7 +1,7 @@
 {
   "name": "mirror-mind",
   "description": "Mirror Mind — local-first memory and identity for agentic runtimes.",
-  "version": "0.38.0",
+  "version": "0.39.0",
   "mcpServers": {
     "mirror-mind": {
       "command": "/bin/sh",

package/ts/src/conversation/extraction.ts

@@ -179,7 +179,7 @@ export async function runConversationExtraction(
   return { memoryIds, taskIds, extracted: memoryIds.length };
 }
 
-async function persistExtractedTasks(
+export async function persistExtractedTasks(
   db: WritableDatabase,
   llm: LlmProvider,
   messages: readonly ExtractionMessage[],
@@ -295,7 +295,7 @@ function logEmbeddingAttempt(
   return embeddingLedgerHook(db, { conversationId, now });
 }
 
-function insertMemory(
+export function insertMemory(
   db: WritableDatabase,
   id: string,
   conversationId: string,