mirror-mind 0.34.0 → 0.36.0

package/.pi/skills/mm-build/SKILL.md

@@ -10,7 +10,7 @@ Activates Builder Mode for a specific journey. Loads identity context and projec
 
 ## Usage
 
-Pi and Gemini CLI:
+Pi:
 
 ```
 /mm-build <journey-slug>

package/.pi/skills/mm-explore/SKILL.md

@@ -14,7 +14,7 @@ attractors, experiment proposals, and Builder handoff.
 
 ## Usage
 
-Pi and Gemini CLI:
+Pi:
 
 ```text
 /mm-explore <journey-slug>

package/.pi/skills/mm-help/SKILL.md

@@ -1,12 +1,12 @@
 ---
 name: "mm-help"
-description: Shows available Mirror Mind commands on Pi and Gemini CLI
+description: Shows available Mirror Mind commands on Pi
 user-invocable: true
 ---
 
 # Help
 
-Show the user the available commands (same on Pi and Gemini CLI):
+Show the user the available commands:
 
 ## Operating Modes
 

package/.pi/skills/mm-soul/SKILL.md

@@ -13,7 +13,7 @@ surface and the question: "how is your day going today?"
 
 ## Usage
 
-Pi and Gemini CLI:
+Pi:
 
 ```text
 /mm-soul [journey-slug]

package/AGENTS.md

@@ -1,9 +1,10 @@
 # Mirror Mind — Operating Instructions
 
 <!-- This file ships in the mirror-mind package and is read by every runtime:
-     Pi and Codex read it from the project root natively, Claude Code and
-     Gemini CLI through the @AGENTS.md import in CLAUDE.md, and an installed
-     package's Pi session receives it from the extension (CV22.DS10.US3, D13).
+     Pi and Codex read it from the project root natively, Claude Code through
+     the @AGENTS.md import in CLAUDE.md, Antigravity as the plugin's rules, and
+     an installed package's Pi session receives it from the extension
+     (CV22.DS10.US3, D13).
      It holds nothing about this repository; that is CLAUDE.md's part. -->
 
 ---
@@ -17,9 +18,9 @@ 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 and Gemini CLI,
-`$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,
+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, Gemini CLI, Codex, Claude
-Code. 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.
@@ -79,9 +79,8 @@ in your machine, not a server.
 - [OpenRouter](https://openrouter.ai) account with at least $5 in credits —
   embeddings, memory extraction, and multi-LLM
 - An AI runtime subscription:
-  [Codex Plus](https://openai.com/codex/) (recommended),
-  [Claude Code Pro](https://code.claude.com/docs), or
-  [Gemini AI Pro](https://geminicli.com/)
+  [Codex Plus](https://openai.com/codex/) (recommended) or
+  [Claude Code Pro](https://code.claude.com/docs)
 - [Pi](https://github.com/earendil-works/pi/tree/main/packages/coding-agent)
   — recommended harness (multi-model, not locked to one provider)
 
@@ -111,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 four runtimes: Pi, Gemini CLI, Codex, and Claude Code
+- **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.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.
 - [v0.33.3 — Mirror Finds Itself Under Any Path](v0.33.3.md) — patch release of one Change Request, CR140, carried by a contributor's PR #42: Mirror read its own install path from `URL.pathname`, so a checkout or package under a path with a space or a non-ASCII character read as `Install: unknown`, the welcome card showed no update, and `runtime update` refused. The path is now a filesystem path, a guard keeps the idiom out, and an `unknown` install names the path it looked up from. On Windows, npm's global layout is recognized and npm runs with no shell, verified on Windows in CI for the two files they touch; there is still no Windows product. Affected installs update once by hand. No migration.

package/docs/releases/v0.35.0.md

@@ -0,0 +1,199 @@
+---
+digest: >
+  v0.35.0 is a minor release closing CV21.DS8: the Gemini CLI integration no
+  longer ships, and Antigravity stands in its place. Mirror Mind supports four
+  runtimes — Pi, Claude Code, Codex, Antigravity — and every document says so.
+  The removal waited for its gate: DS7 measured Antigravity at L4 on agy 1.4.2,
+  all five bar items, so a Gemini CLI user who moves loses nothing and gains
+  MCP. The cutoff is recorded here in full — what no longer exists, why, what
+  to do instead, what still works, and what a user who does nothing will see —
+  with the four hook entries to delete named, and v0.34.0 named as the last
+  release that carries the integration. A retired-surface guard keeps the
+  removal removed. No migration: homes, memories, journeys, and the
+  conversations logged as gemini_cli are untouched.
+---
+
+# v0.35.0 — Four Runtimes, One Successor
+
+**Date:** 2026-10-18
+
+## Highlights
+
+- **Gemini CLI is no longer a Mirror runtime; Antigravity is its successor**
+  ([decision](../project/decisions.md#gemini-cli-is-retired-and-antigravity-is-its-successor)).
+  The four `.gemini/hooks` wrappers, the `gemini:*` hook family, the two
+  Gemini CLI steps `mirror init` printed, and the Gemini smoke no longer ship
+  (CV21.DS8.US1). The package's description and keywords, and every
+  runtime-facing document, name Pi, Claude Code, Codex, and Antigravity
+  (CV21.DS8.US2).
+- **The gate was met first.** v0.33.0 gave notice that the integration would
+  be removed "only once Antigravity gives a Gemini CLI user what they have
+  now". CV21.DS7.US4 measured that on agy 1.4.2, live: all of Mirror's
+  skills, the Operating Instructions at session start, Mirror Mode context
+  injected once per user turn, every turn logged and the conversation closed,
+  setup in one step against Gemini CLI's two — and MCP reachable, which the
+  Gemini CLI wiring never had.
+- **The cutoff is written where a user reads it before it happens to them**:
+  the section below, the Antigravity section of
+  [Getting Started](../getting-started.md#antigravity), and a
+  [troubleshooting entry](../process/troubleshooting.md#gemini-cli-runs-a-mirror-hook-that-no-longer-exists)
+  for the symptom a Gemini CLI user would meet.
+- **A retired-surface guard keeps the removal removed.** `.gemini/` can never
+  ship again from this package: the row is enforced on every push and by the
+  release tripwire. That matters because `mirror init` once told users to
+  write absolute paths into that directory into their settings — a standing
+  instruction to execute whatever a later release might put there.
+
+## Where We Started
+
+v0.32.1 shipped Gemini CLI as one of four supported runtimes, at L4 parity,
+wired by two documented steps. On 2026-09-25 the Navigator retired it —
+Google had set a deprecation date for the Gemini Code Assist backend for
+individuals, and Antigravity, which imports Claude-format plugins, was the
+successor — but the call lived in one story's notes while the release kept
+advertising the runtime. The decision was recorded on 2026-10-13, with a
+condition: the integration goes only behind a documented cutoff, and only
+once Antigravity meets the bar a Gemini CLI user already had. DS7 built the
+agy-native layer and measured the bar. DS8 is the cutoff.
+
+## What Changed
+
+**The integration is gone from the package.** No `.gemini/hooks`, no `gemini`
+entry in the wiring `mirror init` prints, no `gemini:*` hook names — an
+unknown name is noted in `hooks.log` and the turn proceeds, as any unknown
+name does. The Gemini smoke and the npm smoke's Gemini section retired with
+it; the hook payload reader dropped the one field only Gemini CLI supplied.
+
+**The docs say what ships.** Twenty files: README, Getting Started,
+REFERENCE, the Operating Instructions and their plugin copy, the
+runtime-interface spec, the welcome spec, the architecture, and the skills
+that said "Pi and Gemini CLI". Where a runtime list, a wiring step, or a
+parity table had Gemini CLI, it has Antigravity. Where a lesson says what
+Gemini CLI taught — the payload-shape bug its smoke caught, the one-JSON-
+object rule its hook entries kept — the lesson stays, in the past tense.
+Getting Started's subscription table no longer carries a Gemini AI Pro row
+and invents no Antigravity row: what Antigravity requires is Google's to
+say, and Mirror needs only the `agy` command on your PATH.
+
+**Antigravity's own documentation is unchanged** beyond taking Gemini CLI's
+place: DS7 wrote it and measured it.
+
+## The Cutoff: Gemini CLI
+
+**What you keep.** Everything that is yours. Your `~/.mirror-minds/<user>`
+home, your identity, your memories, your journeys, and every conversation
+you logged — including the ones labelled `gemini_cli`, which stay readable
+in `mm-conversations` and `mm-recall` and are never migrated or relabelled.
+Only the runtime that reads them changes.
+
+**Removed.** The four `.gemini/hooks` wrappers (`session-start.sh`,
+`log-user.sh`, `log-assistant.sh`, `session-end.sh`) and the `gemini:*` hook
+family behind them; the two Gemini CLI steps `mirror init` printed (the
+skills link, the four hooks merged into `~/.gemini/settings.json`); the
+Gemini smoke; the runtime from the package's description and keywords and
+from every runtime-facing document.
+
+**Why.** Google deprecated the Gemini Code Assist backend for individuals
+(2026-06-18). Antigravity is its successor and imports Claude-format
+plugins — the one plugin Mirror already ships. The removal waited for
+DS7.US4's measurement on agy 1.4.2: all five items of the bar DS12.TS3 set
+PASS, with per-turn injection — the cost the decision feared losing —
+carried by agy's `PreInvocation` hook. The one difference that did
+materialize: agy has no session-end signal, so a conversation closes when
+your next session starts rather than at exit (as Codex's does); logging
+parity holds, and memories extract after the close.
+
+**What to do instead.** Install Antigravity, then the one step `mirror init`
+prints when it finds `agy` on your PATH:
+
+```bash
+agy plugin install "<pkg>/plugins/mirror-mind"    # <pkg> = $(npm root -g)/mirror-mind
+```
+
+Your home carries over unchanged — nothing to export, nothing to re-seed.
+Same home, same memory, different door. The skills carry the plugin's name:
+`/mirror-mind:mm:mirror`, `/mirror-mind:mm:journeys`, and so on.
+
+**What still works.** Gemini *models*. Memory extraction runs on
+`google/gemini-2.5-flash-lite` through OpenRouter, and `consult` reaches the
+`gemini` family as before. Those are model choices, not the runtime.
+
+**If you do nothing.** After the update, the four `mirror-*` hook commands in
+your `~/.gemini/settings.json` point at files that no longer exist, while the
+links in `~/.gemini/skills/` still resolve — `.pi/skills` keeps shipping. So
+Gemini CLI keeps Mirror's skills and loses logging and Mirror Mode injection.
+Said plainly: your Gemini CLI sessions stop being logged and Mirror Mode
+stops being injected, and nothing on screen says so. Measured on Gemini CLI
+0.61.0 in headless mode (`gemini -p`), 2026-10-18: a registered hook whose
+command is missing is skipped silently; the session proceeds. The entries to
+delete, in `~/.gemini/settings.json`: `mirror-session-start` (under
+`SessionStart`), `mirror-log-user` (`BeforeAgent`), `mirror-log-assistant`
+(`AfterAgent`), `mirror-session-end` (`SessionEnd`); and the `mm-*` links in
+`~/.gemini/skills/`. Mirror never wrote those files and does not edit them.
+Whether Antigravity also reads `~/.gemini/skills/` — which would show a
+migrated user the stale links as duplicate skills — was not measured;
+remove the links either way.
+
+**To stay on Gemini CLI a while longer.** `npm install -g mirror-mind@0.34.0`
+is the last release that carries the integration. The welcome card and
+`runtime update` will keep offering the newer version every session; the pin
+is a choice to make knowingly, not a quiet state.
+
+## Upgrading
+
+```bash
+npm install -g mirror-mind@latest    # or: mirror runtime update
+```
+
+**If you used Gemini CLI:** read the cutoff above; the steps are in Getting
+Started's Antigravity section. **Every other runtime:** nothing to do. No
+migration. Existing homes, sessions, and memories are untouched.
+
+## Also In This Release
+
+- **Typecheck is green on `main` again.** DS7.TS3 left one early return in
+  `hooks/agy.ts` without the field it had just added; `tsc --noEmit`, a CI
+  gate, refused since. Found by DS8.US1's validation, paid in its own commit.
+- **The docs link check is green again.** The plugin's byte copy of the
+  Operating Instructions carries a root-relative link that cannot resolve
+  under `rules/`; the checker reported it on every `.md` push since DS7.US1.
+  The copy's links now resolve where the source lives — not skipped: a link
+  the source cannot resolve still fails through the copy.
+- **The P1 redaction invariant outlives the runtime it was written against.**
+  "A failed hook never writes the prompt or the reply to `hooks.log`" was
+  tested through the Gemini CLI hooks; it now runs through the Claude-family
+  hooks every plugin runtime shares.
+
+## Conscious Exclusions
+
+- **No second cutoff document.** CV22 needed `pending-cutoffs.md` for eleven
+  cutoffs in one release; DS8 has one, and this note is its record.
+- **Mirror does not edit `~/.gemini/settings.json` or `~/.gemini/skills/`.**
+  It never wrote them. The note and the guidance name what to remove.
+- **The Claude plugin smoke's negative probe** still cannot run on a machine
+  with a globally installed `mirror-hook` (CR142, D-031): pre-existing,
+  local-only, carried.
+- **DS5, DS10, DS11** — user extensions on every runtime, Grok through the
+  plugin, the contract and docs refresh — are CV21's remaining stories, not
+  this release's.
+
+## What We Learned
+
+A retirement that lives in a decision while the release advertises the
+runtime has not happened; it happened here in three stories, in order:
+remove, then make the tree say so, then tell the user — and the guard that
+proves each step split by story, so nothing went red between them. The
+sweep found what the inventory missed (a spec line, a history link), which
+is what a guard is for. And the one fact this note most needed — what a
+user who does nothing will see — turned out to be *nothing*: Gemini CLI
+skips a missing hook in silence. That is the strongest reason the cutoff is
+written where the user looks, not only here.
+
+## Next Horizon
+
+DS8 closes with this release, and with it the runtime set CV21 set out to
+reach: the canonical plugin on Claude Code, Codex, and Antigravity, Pi
+through its extension. What remains in CV21 is pulled deliberately from the
+CV21 index: user extensions on every runtime (DS5), Grok through the plugin
+(DS10), and the contract and docs refresh that folds all of it into one
+account (DS11).

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/package.json

@@ -1,7 +1,7 @@
 {
   "name": "mirror-mind",
-  "version": "0.34.0",
-  "description": "Mirror Mind: a local-first memory and identity framework for agentic AI runtimes (Pi, Claude Code, Gemini CLI, Codex)",
+  "version": "0.36.0",
+  "description": "Mirror Mind: a local-first memory and identity framework for agentic AI runtimes (Pi, Claude Code, Codex, Antigravity)",
   "license": "MIT",
   "repository": {
     "type": "git",
@@ -15,7 +15,6 @@
     "agent",
     "pi-package",
     "claude-code",
-    "gemini-cli",
     "codex",
     "sqlite",
     "local-first"
@@ -36,7 +35,6 @@
     ".pi/extensions",
     ".pi/skills",
     ".claude/hooks",
-    ".gemini/hooks",
     "plugins/mirror-mind",
     ".agents/plugins",
     "AGENTS.md",

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

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