mirror-mind 0.35.0 → 0.36.1

package/AGENTS.md

@@ -18,8 +18,8 @@ Applies to all sessions, regardless of project.
 The mirror operates in four modes, chosen automatically based on context:
 Mirror, Builder, Explorer, and Soul.
 
-Each skill below is named three ways: `/mm-<skill>` in Pi, `$mm-<skill>` in
-Codex, `/mm:<skill>` in Claude Code. A **plugin** install prefixes the plugin's
+Each skill below is named three ways: `/mm-<skill>` in Pi and Grok Build,
+`$mm-<skill>` in Codex, `/mm:<skill>` in Claude Code. A **plugin** install prefixes the plugin's
 name — `/mirror-mind:mm:<skill>` in Claude Code's menu and in Antigravity,
 `$mirror-mind:mm:<skill>` in Codex, `mirror-mind:mm-<skill>` as the skill's own
 name — and the forms below refer to the same skill.

package/README.md

@@ -60,8 +60,8 @@ This is not a chatbot with memory. This is a mirror — and yours.
 
 ## How It Works
 
-Local-first. SQLite. Four supported runtimes: Pi, Claude Code, Codex,
-Antigravity. One TypeScript core, run by Node.js. Jungian architecture: Self, Ego,
+Local-first. SQLite. Five supported runtimes: Pi, Claude Code, Codex,
+Antigravity, Grok Build. One TypeScript core, run by Node.js. Jungian architecture: Self, Ego,
 Personas, Shadow.
 Context-activated modes — Mirror, Builder, Explorer, and Soul. The identity lives
 in your machine, not a server.
@@ -110,7 +110,7 @@ this repository, turning a personal experiment into a reusable framework:
 
 - **English** — full migration from Portuguese across code, CLI, schema, identity, and docs
 - **Framework/user separation** — user identity and memory live privately under `~/.mirror/<user>/`, outside the repository
-- **Multi-runtime** — from Claude Code only to Pi, Claude Code, Codex, and Antigravity
+- **Multi-runtime** — from Claude Code only to Pi, Claude Code, Codex, Antigravity, and Grok Build
 - **Multi-user** — independent mirrors for multiple users on the same machine
 - **Multi-session** — concurrent sessions tracked safely in a database-backed session registry
 - **Intelligence depth** — hybrid semantic and lexical search, honest reinforcement, two-pass extraction, memory consolidation, and shadow cultivation

package/docs/releases/index.md

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

package/docs/releases/v0.36.0.md

@@ -0,0 +1,222 @@
+---
+digest: >
+  v0.36.0 is a minor release closing CV21.DS10: Grok Build is Mirror Mind's
+  fifth runtime, at its honest L3 through the canonical plugin, in two steps
+  `mirror init` prints and `runtime diagnose` understands. With it ships
+  CV21.DS5.US2: a home's installed extensions reach Claude Code, Codex,
+  Antigravity, and Grok Build as one generated plugin per home, the shape
+  DS5.TS1 chose by measurement on all four. Three Change Requests ride along,
+  each found by using the product: an extension's installation settings get a
+  file Mirror reads for them (`extensions/<id>.env`), a closed pipe ends a
+  command quietly instead of with a stack trace, and `bind` refuses what it
+  cannot bind instead of writing a row that does nothing. No migration.
+---
+
+# v0.36.0 — Five Runtimes, and a Home's Extensions on Every One
+
+**Date:** 2026-10-20
+
+## Highlights
+
+- **Grok Build is the fifth runtime** (CV21.DS10). Two printed steps — a
+  trusted plugin install and a home rule for the Operating Instructions — and
+  Grok has Mirror's skills, its hooks, and its MCP server. Measured live on
+  grok 1.0.62: the rule reaches the model, `/mm-mirror` answers signed by a
+  persona, every turn is logged as `grok_build`, the close fits Grok's 1.5 s
+  bound. Honest ceiling, written where a user reads it: Grok adds nothing to
+  the model's context per turn, so Mirror Mode lasts as long as the skill's
+  own instructions do.
+- **A home's extensions reach every plugin runtime** (CV21.DS5.US2).
+  `mirror extensions install` and `uninstall` regenerate one small plugin per
+  Mirror home, `runtime/plugin/mirror-ext-<user>/`, and print the one wiring
+  step a runtime on the `PATH` still needs. Chosen over two other shapes by a
+  measured table on claude 2.1.296, codex 0.163.0, agy 1.4.2, and grok 1.0.62
+  ([decision](../project/decisions.md#user-extensions-reach-every-runtime-as-a-per-home-plugin)).
+  `runtime diagnose` names a stale copy and the command that brings it level.
+- **An extension's installation settings have a home**
+  ([CR145](../project/refinement/rs011-extension-contract-completeness/cr145-an-extension-s-installation-settings-have-nowhere-to-live-but-the-login-shell.md)).
+  `~/.mirror-minds/<user>/extensions/<id>.env`, merged *under* the environment
+  for the one process Mirror spawns — subcommand or context provider — and
+  nothing else. The reason it had to be Mirror: Node reads
+  `NODE_EXTRA_CA_CERTS` before any extension code runs, so only the spawner can
+  set it, and the alternative was the login shell, where it broke every other
+  Postgres client on the machine.
+- **Two front-door manners** ([CR148](../project/refinement/rs010-cv22-oracle-and-port-hygiene/cr148-the-front-door-dies-with-a-stack-trace-when-its-stdout-closes-early.md),
+  [CR149](../project/refinement/rs010-cv22-oracle-and-port-hygiene/cr149-bind-accepts-a-persona-or-journey-that-does-not-exist.md)).
+  `mirror … | head -1` exits 0 in silence instead of dying of `EPIPE` with a
+  stack trace — on the hook entry too, where exit 1 was the one code it
+  promised never to return. And `mirror ext <id> bind` checks the extension,
+  the capability, and the persona or journey before writing a row, refusing
+  with the fix in the line: `no persona 'engine' (mirror list personas shows
+  this home's)`.
+
+## Where We Started
+
+v0.35.0 closed CV21's runtime set at four — Pi, Claude Code, Codex,
+Antigravity — with Grok Build and user extensions named as what remained.
+Grok had been reading Mirror's skills by accident since DS12, through its
+Claude compatibility, with no hooks and no logging, and DS12.TS4 had left the
+MCP attachment as a contradiction: the server ready with its seven tools in
+Grok's own view, every session created with `mcp_server_count: 0`. User
+extensions reached Claude Code through `expose-claude` and Pi through its
+catalog, and nothing else; DS12.TS5 had measured that and left the exposure
+as a choice among three shapes, deciding none.
+
+Then the product was used. An extension built for a private journey needed a
+TLS mode and a certificate that belonged to the machine, and the only place
+the contract left for them was `~/.zshrc`. A mistyped `tail -` produced a
+Node stack trace from the front door. A mistyped persona was bound without a
+word. Three Change Requests, two days.
+
+## What Changed
+
+**Grok Build, in four stories on one day** (2026-10-18, grok 1.0.62).
+CV21.DS10.US1 measured five install shapes and chose two printed steps:
+`grok plugin install "<pkg>/plugins/mirror-mind" --trust`, and the Operating
+Instructions linked as a rule at `~/.grok/rules/mirror-mind.md` — Grok shows a
+session-start hook's context on screen only, so the rule is how the
+instructions reach the model. US1 also found that the root `plugin.json`
+marker DS7 had added was hiding the plugin's version and MCP server from
+Grok; it now carries both, one server on all four plugin runtimes. TS2
+closed DS12's contradiction: the server attaches, its tools sit behind Grok's
+`search_tool` and `use_tool` meta-tools (as `mirror-mind__list_journeys`), and
+the zero count was a snapshot taken while the server was `pending`. US3
+measured L3 with an ablation — remove the rule and the model loses the
+instructions; the hook canaries never reached it — and the deferred close
+tail finished at the next start, DS4.TS2's design on Grok's bound. TS4 wrote
+it: the contract's Grok reference implementation, README, Getting Started,
+REFERENCE, and the Operating Instructions name Grok Build as the fifth
+runtime with its two steps and its ceiling. Paid on the way, CR143: the
+inject hook returns at once on Grok instead of spending 2–3 s per load on a
+context Grok discards.
+
+**User extensions, chosen then built** (2026-10-19). CV21.DS5.TS1 measured
+the three shapes DS12.TS5 had left — user-level skill roots, a per-home
+generated plugin, MCP prompts — in scratch homes on all four runtimes, each
+cell read by the runtime's own listing and then by one headless turn asking
+for a canary, with every tool call classified so a find reached by searching
+the disk did not count. Only the per-home plugin qualified on all four: the
+skill roots are three roots that no runtime set reads in common, and MCP
+prompts attached everywhere and reached no model. US2 built it.
+`mirror extensions install`, `uninstall`, and `sync` regenerate
+`runtime/plugin/mirror-ext-<user>/` in the canonical plugin's format,
+version `0.1.<generation>`, carrying each extension's `claude` skill as its
+manifest already declares it — no manifest rewritten. The install prints what
+a runtime on the `PATH` still needs: a link for Claude Code, two commands for
+Codex, one for Antigravity, one with `--trust` for Grok (and the line that
+there is nothing for `--trust` to activate). After a change, the three
+runtimes that copy a plugin hold a stale copy until one command each, which
+the verbs print and `runtime diagnose` raises as five `ext_plugin_*` findings,
+each with its repair. Two homes wire beside each other. `runtime status`
+gained `Extensions plugin: mirror-ext-<user> <version> (<n> skills)`.
+
+**The settings file** (CR145). `mirror-cli-v1` handed a subcommand the five
+`MIRROR_*` variables and whatever environment `mirror` had; `mirror-context-v1`
+handed a provider the environment untouched. Now both read
+`extensions/<id>.env` — dotenv, the parser behind Mirror's own `.env` — and
+merge it *under* the process environment: an explicit export still wins, the
+five `MIRROR_*` names can never come from the file, and the result reaches
+that one process. The file sits beside the installed directory, not inside
+it: `install` rewrites the directory, and in a development home the directory
+is a symlink into the extension's own repository. `mirror ext <id>` ends its
+listing with the file's absolute path and one of four states — the variable
+*names* it carries, `no variables`, `not present` with what to do, or
+`unreadable` with the reason — and says when other users can read it. A file
+that exists and cannot be read refuses the subcommand (one line, exit 1,
+nothing spawned) and skips the provider with a `settings_unreadable`
+diagnostic. A full `uninstall` keeps the file and says so. The contract
+reference has the rules in full.
+
+**A closed pipe** (CR148). One listener at each entry — `mirror` and
+`mirror-hook` — on `EPIPE`: exit 0, write nothing. `npm`, `cargo`, and
+`kubectl`'s choice over git's 141, because under `set -o pipefail` 141 fails a
+pipeline a person wrote on purpose. Anything that is not `EPIPE` is rethrown.
+The hook leaves one line in `hooks.log` first, `stdout closed early`, because
+its try/catch could never see a stream's `error` event, and a runtime that
+gives up on a hook closes its pipe. Stop means stop: work after the reader
+closes is abandoned, as `SIGPIPE` abandons git's.
+
+**`bind` checks what it binds** (CR149). Four checks before the one insert,
+outside in: the id against the manifest's grammar, the extension installed,
+the capability declared (the validator first, then the context reader for the
+list), the persona or journey present in the identity rows a load is later
+matched against. Each refusal is one line on stdout at exit 1 and writes no
+row. `unbind` and `bindings` are untouched: removing a row that points at
+nothing is the repair. A deliberate divergence from the Python oracle; the
+bindings golden kept every byte, with its world given what the checks need.
+
+## Upgrading
+
+```bash
+npm install -g mirror-mind@latest    # or: mirror runtime update
+```
+
+No migration. Existing homes, sessions, memories, and bindings are untouched.
+
+**Grok Build:** `mirror init` prints the two steps when it finds `grok` on
+your `PATH`; Getting Started's Grok Build section has them with what they
+cost. If you had wired Claude Code, Grok already read the skills from that
+link; after the plugin install each skill appears twice in Grok's menu, and
+the hooks run once.
+
+**If you have extensions installed:** the per-home plugin is generated by the
+next `extensions` verb, not by the update. Re-install any one extension —
+`mirror extensions install <id> --extensions-root <root>` from its source, or
+from the home's own `~/.mirror-minds/<user>/extensions` — and the report
+prints the one wiring step each runtime on your `PATH` still needs. Pi needs
+nothing; its catalog path is unchanged.
+
+**If an extension of yours reads machine settings from your shell profile:**
+move them to `~/.mirror-minds/<user>/extensions/<id>.env`, `chmod 600` it,
+and `mirror ext <id>` will show the keys it carries. Then delete the exports
+— they reached every other program you run.
+
+## Conscious Exclusions
+
+- **DS5 is not closed.** US3 — `review-copy` invoked live on each runtime
+  from the shipped package, with version, binary, and date — and TS4 — the
+  contract, extension docs, Getting Started, and REFERENCE saying how an
+  extension reaches each runtime — remain. Until TS4, the install's printed
+  steps and the contract's per-home plugin section are the documentation.
+- **DS11**, the contract and docs refresh that folds all five runtimes into
+  one parity matrix, is not this release's.
+- **An extension cannot yet declare the settings it expects** (CR146), so the
+  settings file is written from the extension's README, not from a
+  checklist Mirror prints. **`install` shows `suggested_personas` the home does
+  not have as if it did** (CR150). **Three copies of the extension-id grammar
+  remain, two of them disagreeing** (CR147); CR145 and CR149 used the
+  manifest's. All three captured, none done.
+- **Still open from earlier:** the plugin smoke's negative probe on a machine
+  with a global `mirror-hook` (CR142); the DS7 routes removing agy's credential
+  where 1.3.x kept it (CR144).
+- **141** as the exit on a closed pipe, and `EPIPE` handling inside extension
+  subcommands: not chosen, recorded in CR148.
+
+## What We Learned
+
+Twice in one day a validation route had to be shown failing before it could
+be trusted passing. CR145's first run validated nothing: the `mirror` on the
+Navigator's `PATH` was the published 0.35.0, and the shell wrapped it in the
+very function the CR retires — the workaround, measured where it lived. CR148's
+planned control, `| head -1`, could not fail: a 2 KB listing lands whole in
+the pipe buffer before `head` quits, so there was never an `EPIPE` to handle;
+the reproduction is a reader that closes without reading. A route that names
+the binary by path and a control that has been seen red are now part of what
+a Change Request's validation means.
+
+The three CRs came from using the product, not from reading it: a private
+journey's extension, a typo, another typo. The review that preceded each —
+five lenses on CR145, three on CR148, four on CR149 — changed each plan
+before a line was written, and the things it added (a result type instead of
+a throw, a diagnostic kind instead of a generic failure, a check zero on the
+id grammar) are the parts a future reader will be glad of.
+
+## Next Horizon
+
+DS5.US3 is the recommended pull: the live proof of `review-copy` on all four
+plugin runtimes from the shipped package, through the steps this release
+prints. TS4 writes what US3 measures. DS11 then folds five runtimes into one
+contract and one matrix, and CV21 closes. RS011 — extension contract
+completeness — holds the gaps the contract has, found one extension at a time;
+CR146, a manifest that declares the settings it expects, is its next natural
+candidate.

package/docs/releases/v0.36.1.md

@@ -0,0 +1,137 @@
+---
+digest: >
+  v0.36.1 is a patch release of one Change Request, CR153. Session
+  maintenance used to read Pi's session directory and import every session a
+  home did not already track, so on a machine with more than one Mirror home
+  each home copied the other's Pi conversations and titled them again through
+  the provider. Maintenance now imports no Pi session: a home's Pi
+  conversations are the ones the Pi extension logged into it, as they
+  happened, and `PI_SESSIONS_DIR` is no longer read. Conversations an earlier
+  version imported stay where they are, and this note shows how to list them.
+  Update every install that has a home. No migration.
+---
+
+# v0.36.1 — A Home Keeps Only Its Own Pi Sessions
+
+**Date:** 2026-10-21
+
+## Highlights
+
+- **Session maintenance imports no Pi session**
+  ([CR153](../project/refinement/rs010-cv22-oracle-and-port-hygiene/cr153-a-home-s-pi-backfill-imports-another-home-s-sessions.md)).
+  It used to read every file in Pi's session directory and import each one the home
+  did not track, every session another Mirror home on the same machine had logged
+  among them. A home's Pi conversations are now exactly the ones the Pi extension
+  logged into it, as they happened.
+- **Nothing in Mirror reads Pi's session files.** Not your history from before Mirror,
+  not sessions you run without it, and not another home's. `PI_SESSIONS_DIR` is inert:
+  a `.env` that sets it keeps working, and it changes nothing.
+- **What was already imported stays.** This release removes the cause, not the copies;
+  [Upgrading](#upgrading) shows how to list them.
+- **Update every install that has a home.** A home is safe from a neighbour's
+  maintenance only once the install that neighbour runs carries this release.
+
+## Where We Started
+
+The import is older than the idea of two homes on one machine. It existed to fill a
+gap: a Pi session the extension never logged reached the home anyway, at the next
+maintenance. v0.32.0 narrowed it to sessions newer than the home, so a new home would
+not swallow a lifetime of Pi history. Nothing scoped it to the home.
+
+CV21.DS5.US3's live route exposed it. A Claude Code cell ran on the real `HOME` against
+a scratch home born that evening, and two seconds into its first session, maintenance
+imported four of the person's Pi sessions from that day, from both of their real homes,
+and titled them through the provider. The route closed its own hole the same evening;
+the product's was CR153.
+
+Measured before planning, read-only, on the maintainer's two homes, one a copy of the
+other since July: each had taken the other's Pi conversations all along, 543 between
+them, and both were still doing it. Titling them took 411 provider calls. No memory
+came from any of them, because extraction needs a journey and an import carries none,
+but every one listed as the newest conversation, since an import's start is the moment
+it was imported. The gap the import existed to fill came up once in three months.
+
+## What Changed
+
+**The decision.** Three ways out were weighed: a claim recorded at session start, so a
+home imports only sessions it saw begin; a mark written into each Pi session file, so a
+home imports only files carrying its name; or no import at all. The claim would have
+kept the one recovery in three months for a table, a migration, and a claim lifecycle.
+The mark would have left every home reading every other home's files at every start.
+Retiring the import is the only option in which no home reads Pi's files at all, and
+it gives up almost nothing
+([decision](../project/decisions.md#session-maintenance-imports-no-pi-session-a-home-holds-the-pi-conversations-it-logged-live)).
+
+**The change.** The Pi backfill, the import seam only it still used, and v0.32.0's
+birth floor are deleted, and a retired-surface guard keeps them deleted. The tests came
+first: three cases — a session in Pi's default directory, one under `PI_SESSIONS_DIR`,
+and the full `session-start` the SessionStart hooks run — failed on the old code, each
+importing a session another home had logged, and pass now. The Navigator then ran the
+published 0.36.0 beside the change on the same session: the old version took it and
+the new one did not. On the real Pi history the new one took nothing, and a live Pi
+session against a scratch home was logged as before.
+
+### What you will notice
+
+- The maintenance report has four lines: `Closed stale conversations`, `Retitled pending
+  conversations`, `Extracted pending conversations`, and `Finished deferred close tails`.
+- If you have run more than one home on this machine, each may hold Pi conversations
+  the other logged. They are not removed.
+- A Pi session you run without Mirror's extension never appears in Mirror. Run Pi with
+  the Mirror package, and its sessions are logged as they happen.
+
+## Upgrading
+
+```bash
+mirror runtime update          # or: npm install -g mirror-mind
+```
+
+Update every install that has a home: the package, and each clone. There is no
+database migration, and no runtime wiring changes.
+
+To list the Pi conversations an earlier version imported into a home, read-only:
+
+```bash
+sqlite3 ~/.mirror-minds/<user>/memory.db \
+  "SELECT id, title, started_at FROM conversations
+    WHERE interface = 'pi' AND julianday(started_at) >= julianday(ended_at)
+    ORDER BY started_at"
+```
+
+An import gives itself away: it started when it was imported, after its last message.
+The home's dated backups and its pre-write backup hold the same rows.
+
+## Conscious Exclusions
+
+- **Removing what was imported.** A command that lists and removes those conversations
+  is [CR154](../project/refinement/rs010-cv22-oracle-and-port-hygiene/cr154-a-home-cannot-list-or-remove-the-pi-conversations-it-imported.md).
+- **A session whose logging never reached the core** is now simply missing from the
+  home, with an error line in `mirror-logger.log` and nowhere else. `runtime diagnose`
+  reading those lines is
+  [CR155](../project/refinement/rs010-cv22-oracle-and-port-hygiene/cr155-runtime-diagnose-does-not-read-the-pi-extension-s-error-lines.md).
+- **A home made by copying another's database** is the same home twice — the same ids,
+  the same history. The docs saying so is
+  [CR156](../project/refinement/rs010-cv22-oracle-and-port-hygiene/cr156-a-home-made-by-copying-another-s-database-is-the-same-home-twice.md).
+- **Importing a Pi session on request.** If it is wanted, it is a feature with its own
+  story, not something maintenance does in the background.
+- **The transcript backfill** matches a session's replies by time window — the same
+  shape, inside one home. That is
+  [CR151](../project/refinement/rs010-cv22-oracle-and-port-hygiene/cr151-the-transcript-backfill-writes-a-session-s-replies-into-other-sessions-conversations.md),
+  its own change.
+
+## What We Learned
+
+The import decided ownership from an absence: a session the home did not track was the
+home's to take. That was true while a machine had one home, and it stopped being true
+on the day a second home appeared, with nothing to mark the day.
+
+The leak was also invisible to the check that should have caught it. The first look at
+the real homes asked by journey, and an import has no journey. Measured by construction
+instead — an import starts after its own last message — the same homes held 543. A
+measurement taken before planning turned "consider pulling it first" into a fact about
+the maintainer's own data.
+
+## Next Horizon
+
+CR154: a home lists, and on request removes, the Pi conversations an earlier version
+imported. Then CV21.DS5.TS4 and DS11, and CV21's own release.

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "mirror-mind",
-  "version": "0.35.0",
+  "version": "0.36.1",
   "description": "Mirror Mind: a local-first memory and identity framework for agentic AI runtimes (Pi, Claude Code, Codex, Antigravity)",
   "license": "MIT",
   "repository": {

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

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

package/plugins/mirror-mind/plugin.json

@@ -1,4 +1,14 @@
 {
   "name": "mirror-mind",
-  "description": "Mirror Mind — local-first memory and identity for agentic runtimes."
+  "description": "Mirror Mind — local-first memory and identity for agentic runtimes.",
+  "version": "0.36.1",
+  "mcpServers": {
+    "mirror-mind": {
+      "command": "/bin/sh",
+      "args": [
+        "-c",
+        "mmbin=\"\"; [ -n \"$MIRROR_BIN\" ] && [ -x \"$MIRROR_BIN/mirror\" ] && mmbin=\"$MIRROR_BIN/mirror\"; [ -n \"$mmbin\" ] || mmbin=\"$(command -v mirror 2>/dev/null)\"; for mmdir in \"$HOME/.nvm/current/bin\" /opt/homebrew/bin /usr/local/bin; do [ -n \"$mmbin\" ] && break; [ -x \"$mmdir/mirror\" ] && mmbin=\"$mmdir/mirror\"; done; [ -n \"$mmbin\" ] || { echo \"mirror-mind: mirror not found on PATH; the MCP server cannot start. Install mirror-mind (npm install -g mirror-mind) or set MIRROR_BIN to its bin directory.\" >&2; exit 1; }; mmnode=\"$MIRROR_NODE\"; [ -n \"$mmnode\" ] && [ -x \"$mmnode\" ] || mmnode=\"$(command -v node 2>/dev/null)\"; for mmdir in \"$(dirname \"$mmbin\")\" \"$HOME/.nvm/current/bin\" /opt/homebrew/bin /usr/local/bin; do [ -n \"$mmnode\" ] && break; [ -x \"$mmdir/node\" ] && mmnode=\"$mmdir/node\"; done; [ -n \"$mmnode\" ] || { echo \"mirror-mind: node not found on PATH; the MCP server cannot start. Set MIRROR_NODE.\" >&2; exit 1; }; exec \"$mmnode\" \"$mmbin\" mcp"
+      ]
+    }
+  }
 }

package/plugins/mirror-mind/rules/AGENTS.md

@@ -18,8 +18,8 @@ Applies to all sessions, regardless of project.
 The mirror operates in four modes, chosen automatically based on context:
 Mirror, Builder, Explorer, and Soul.
 
-Each skill below is named three ways: `/mm-<skill>` in Pi, `$mm-<skill>` in
-Codex, `/mm:<skill>` in Claude Code. A **plugin** install prefixes the plugin's
+Each skill below is named three ways: `/mm-<skill>` in Pi and Grok Build,
+`$mm-<skill>` in Codex, `/mm:<skill>` in Claude Code. A **plugin** install prefixes the plugin's
 name — `/mirror-mind:mm:<skill>` in Claude Code's menu and in Antigravity,
 `$mirror-mind:mm:<skill>` in Codex, `mirror-mind:mm-<skill>` as the skill's own
 name — and the forms below refer to the same skill.

package/ts/src/conversation/loggerRuntime.ts

@@ -2,10 +2,10 @@
 //
 // Everything the `conversation-logger` subcommands need beyond the database
 // is assembled here, once per invocation, from an EXPLICIT environment: the
-// clock and id generator, the transcript/session resolution inputs, the Pi
-// sessions directory, the pre-write backup, and -- only for the subcommands
-// that cross the LLM close tail -- the replay providers and the maintenance
-// dependencies built on them.
+// clock and id generator, the transcript/session resolution inputs, the
+// pre-write backup, and -- only for the subcommands that cross the LLM close
+// tail -- the replay providers and the maintenance dependencies built on them.
+// (No Pi sessions directory: maintenance reads no Pi session file, CR153.)
 //
 // The providers are loaded lazily. `diagnose-journeys`
 // or `session-start --fast` must never fail because a replay fixture is not
@@ -17,7 +17,6 @@
 // Nothing here reads `process.env` or `os.homedir()`; the front door passes
 // them in, which is what keeps every test of this module hermetic.
 
-import { backfillPiSessions, homeBornAt, resolvePiSessionsDir } from "#conversation/backfill.ts";
 import { createCloseHooks, maybeGenerateTitle } from "#conversation/closeTail.ts";
 import { runConversationExtraction } from "#conversation/extraction.ts";
 import { runExtractionWithAccounting } from "#conversation/extractionRun.ts";
@@ -47,7 +46,6 @@ import {
 export type LoggerRuntimeEnv = {
   MIRROR_SESSION_ID?: string;
   CLAUDE_PROJECT_DIR?: string;
-  PI_SESSIONS_DIR?: string;
   MIRROR_TS_CONVERSATION_LLM_REPLAY?: string;
   MIRROR_TS_CONVERSATION_EMBEDDING_REPLAY?: string;
   /** Read by the live providers when the close tail runs against a real model. */
@@ -100,12 +98,11 @@ export interface LoggerRuntime {
   readonly homeDir: string;
   readonly claudeProjectDir: string | null;
   readonly environmentSessionId: string | null;
-  readonly piSessionsDir: string;
   /** Which transport answers the close tail here: replay, incomplete replay, or live. */
   readonly transportMode: ProviderTransportMode;
   /** The close hooks (extraction + finalization) behind the replay transport. */
   closeHooks(): Promise<CloseHooks>;
-  /** The full maintenance wiring, including the real Pi backfill. */
+  /** The full maintenance wiring. */
   maintenanceDeps(): Promise<MaintenanceDeps>;
   /** The dated zip backup for the mutating journey repair; see `LoggerRuntimeOptions.backup`. */
   readonly backup: ((stdout: (line: string) => void) => string | null) | null;
@@ -135,7 +132,6 @@ function liveTailOverrides(
 
 export function createLoggerRuntime(options: LoggerRuntimeOptions): LoggerRuntime {
   const { db, env, deps } = options;
-  const piSessionsDir = resolvePiSessionsDir(null, env, options.homeDir);
 
   // One precedence, shared with the router so the two cannot disagree about
   // which transport is live: replay -> incomplete -> live. The pair rule that
@@ -225,7 +221,6 @@ export function createLoggerRuntime(options: LoggerRuntimeOptions): LoggerRuntim
     homeDir: options.homeDir,
     claudeProjectDir: env.CLAUDE_PROJECT_DIR || null,
     environmentSessionId: env.MIRROR_SESSION_ID?.trim() || null,
-    piSessionsDir,
     transportMode: transport.mode,
     backup: options.backup ?? null,
     closeHooks,
@@ -246,14 +241,6 @@ export function createLoggerRuntime(options: LoggerRuntimeOptions): LoggerRuntim
         // CV21.DS4.TS2: the finalization a bounded runtime's SessionEnd deferred.
         finalizeCloseTail: (database, conversationId) =>
           hooks.finalizeMetadata(database, conversationId),
-        // CR121: only the sessions newer than this home; its birth is read from
-        // the ledger once per maintenance run, and an unknown birth is an error.
-        backfillPiSessions: (database) =>
-          backfillPiSessions(
-            database,
-            { sessionsDir: piSessionsDir, notBefore: homeBornAt(database) },
-            deps,
-          ),
         extractionLimit: resolveMaintenanceMaxExtractions({ env }),
         staleOrphanMinutes: resolveStaleOrphanMinutes({ env }),
         monotonic: options.monotonic,

package/ts/src/conversation/runtimePolicy.ts

@@ -1,6 +1,7 @@
 // What a runtime's session lifecycle lets Mirror do at its edges, by the label
 // US8 stamps on the session row (`claude_code`, `codex`, `grok_build`). One home
-// for the two policies the close path reads (CV21.DS4.TS2, US4).
+// for the policies the hooks read: the two the close path reads (CV21.DS4.TS2,
+// US4) and the one the inject hook reads (CV21.DS10.TS4, CR143).
 
 /**
  * Whether a runtime's SessionEnd hook has the time to run the LLM tail at exit
@@ -11,8 +12,10 @@
  *   codex        synchronous ("running async SessionEnd hook synchronously",
  *                DS12.TS2 L2), 1 s for a handler with no `timeout` (DS2's live
  *                `/hooks` table, 2026-10-13, Codex 0.162.1).
- *   grok_build   1.5 s for a handler with no `timeout` (DS12.TS4, Grok 1.0.52).
- *                DS10 re-measures it and may flip this entry.
+ *   grok_build   1.5 s for a handler with no `timeout` (DS12.TS4, Grok 1.0.52);
+ *                re-measured on 1.0.62 (CV21.DS10.US3): the guide says a
+ *                plugin's SessionEnd hook gets at most that default whatever
+ *                its own `timeout`, and the close landed 213–259 ms after it.
  *
  * Any other label, and no label, keeps today's behavior: the tail runs.
  */
@@ -57,3 +60,23 @@ export function sessionEndRunsLlmTail(interfaceName: string | null | undefined):
 export function sessionOutlivesTui(interfaceName: string | null | undefined): boolean {
   return interfaceName === "codex" || interfaceName === "antigravity";
 }
+
+/**
+ * Whether a runtime gives the model what a `UserPromptSubmit` hook returns as
+ * `additionalContext` — the channel the inject hook uses (CV21.DS10.TS4, CR143).
+ *
+ *   grok_build   no. Grok shows a SessionStart hook's `systemMessage` on
+ *                screen and discards both events' `additionalContext`
+ *                (DS12.TS4 L2/L3 on 1.0.52; CV21.DS10.US3 on 1.0.62, with a
+ *                random canary the probe hook emitted on every turn and the
+ *                model never quoted). The loads the hook made there held a
+ *                turn 2.3–2.6 s for a context nobody read; the hook returns
+ *                before any of them when this is false.
+ *
+ * Any other label, and no label, reads it: an unlabelled payload is a Claude
+ * Code payload by detection's own rule (`detectHookRuntime`), and a predicate
+ * that failed closed would silence injection on the runtime that needs it.
+ */
+export function runtimeReadsPromptContext(interfaceName: string | null | undefined): boolean {
+  return interfaceName !== "grok_build";
+}

package/ts/src/conversation/sessionComposites.ts

@@ -48,12 +48,6 @@ export interface MaintenanceDeps {
    * only for callers written before the step existed; the front door wires it.
    */
   finalizeCloseTail?: (db: WritableDatabase, conversationId: string) => Promise<void> | void;
-  /**
-   * `backfillPiSessions` (slice E) bound to its resolved sessions directory.
-   * Injected rather than resolved here so the composite never reads the
-   * environment itself; the front door owns that resolution.
-   */
-  backfillPiSessions: (db: WritableDatabase) => Promise<number> | number;
   /** Python's `MEMORY_MAINTENANCE_MAX_EXTRACTIONS` (AI-05); defaults to the released budget. */
   extractionLimit?: number;
   /** `MIRROR_STALE_ORPHAN_MINUTES` (CV21.DS4.US4); defaults to the 30-minute threshold. */
@@ -231,6 +225,11 @@ function formatElapsed(elapsed: number): string {
  * warning tails. The step order is behavior, not presentation — closing stale
  * orphans first is what makes their conversations eligible for the extraction
  * step in the same run.
+ *
+ * CR153: there is no Pi backfill step. Python's walked Pi's session directory
+ * and imported every file this home did not track, which on a machine with two
+ * homes meant each other's sessions; a home's Pi conversations are the ones the
+ * Pi extension logged into it, and maintenance reads no Pi session file.
  */
 export async function sessionMaintenance(
   db: WritableDatabase,
@@ -246,7 +245,6 @@ export async function sessionMaintenance(
         thresholdMinutes: deps.staleOrphanMinutes ?? STALE_ORPHAN_THRESHOLD_MINUTES,
       }),
     ),
-    await timedStep("Backfilled Pi sessions", monotonic, () => deps.backfillPiSessions(db)),
     await timedStep("Retitled pending conversations", monotonic, () =>
       retitlePendingConversations(db, { retitleConversation: deps.retitleConversation }),
     ),

package/ts/src/conversation/transcriptBackfill.ts

@@ -23,7 +23,11 @@ function isRecord(value: unknown): value is Record<string, unknown> {
   return typeof value === "object" && value !== null && !Array.isArray(value);
 }
 
-/** Python `dict.get` on something that must be a dict; see `backfill.ts`. */
+/**
+ * Python `dict.get(key, default)` on a value that MUST be a dict: anything else
+ * raises, as Python's AttributeError does. The default applies only when the
+ * key is ABSENT -- a present `null` comes back as null, as Python returns None.
+ */
 function getOr(container: unknown, key: string, fallback: unknown): unknown {
   if (!isRecord(container)) throw new TypeError(`expected an object with '${key}'`);
   return key in container ? container[key] : fallback;

package/ts/src/db/migrations.ts

@@ -548,13 +548,10 @@ export const MIGRATIONS: readonly (readonly [string, MigrationApply])[] = [
  * contract.
  */
 export function runMigrations(db: WritableDatabase): void {
-  // The ledger has a second reader: `homeBornAt` (conversation/backfill.ts,
-  // CR121) takes MIN(applied_at) as the instant this home was born, and
-  // session maintenance imports only the Pi sessions newer than it. Never
-  // rewrite history here -- no re-stamping, no squash that deletes rows and
-  // re-inserts them with a later date. Retiring a migration id moves the
-  // minimum forward at worst, which imports less; re-stamping could move it
-  // and would be a lie about the home's age.
+  // The ledger records which migrations ran, and when -- nothing more. Do not
+  // infer a home's birth from its first `applied_at`: a database copied to
+  // make a second home carries its source's ledger, so two homes would share
+  // one birth (CR153 retired the reader that did, CR156 records the copy).
   db.exec(`
     CREATE TABLE IF NOT EXISTS _migrations (
         id TEXT PRIMARY KEY,