Release v3.4.1 — promote develop to main

.antigravity-plugin/README.md

@@ -0,0 +1,77 @@
+# MemPalace — Antigravity plugin
+
+In-repo packaging for the MemPalace integration with Google's [Antigravity IDE](https://antigravity.google/).
+
+This directory is the source of truth for what gets installed at
+`~/.gemini/config/plugins/mempalace/` when the user runs the installer.
+
+## Layout
+
+```
+.antigravity-plugin/
+├── plugin.json            # marker manifest (verified minimal schema)
+├── mcp_config.json        # auto-registers the mempalace-mcp stdio server
+├── hooks.json.tmpl        # template — installer renders to hooks.json
+├── skills/
+│   ├── mempalace/
+│   │   └── SKILL.md       # ops skill: setup, mine, status, CLI delegation
+│   └── mempalace-recall/
+│       └── SKILL.md       # recall-only skill: search-before-answer protocol
+├── rules/
+│   └── mempalace-recall.md # optional recall rule (complements the skill)
+└── README.md              # this file
+```
+
+The hook scripts themselves live at `hooks/antigravity/`. The installer
+copies them into `<install-dir>/hooks/` and renders `hooks.json.tmpl`
+into a `hooks.json` whose `command` paths point at the absolute install
+location.
+
+## Three recall layers
+
+MemPalace can store everything, but it only helps if the agent actually
+*reads* the palace before answering. Three layers wire that in, from
+eager to on-demand:
+
+1. **Wake hook** (`hooks/antigravity/mempal_wake_hook_antigravity.sh`,
+   `PreInvocation` event, gated to `invocationNum == 1`). On the first
+   model call of a conversation it runs `mempalace wake-up` and injects
+   the **actual palace content verbatim** via Antigravity's
+   `injectSteps[].ephemeralMessage` output. This is Antigravity's native
+   equivalent of Cursor's `sessionStart` `additional_context`, except it
+   delivers the memory itself rather than a directive to go fetch it.
+2. **Recall skill** (`skills/mempalace-recall/SKILL.md`). The
+   search-before-answer protocol the agent follows when a turn is
+   recall-relevant — tool selection, unhappy paths, anti-patterns. It
+   covers recall only; the `mempalace` skill covers setup / mine /
+   status.
+3. **Optional recall rule** (`rules/mempalace-recall.md`). A lightweight
+   markdown rule that nudges the agent to search before answering when
+   Antigravity's matcher decides the turn is recall-relevant. It is
+   deliberately recall-scoped (not an always-on global rule) so it never
+   adds latency to greenfield work, honouring MemPalace's "memory should
+   feel instant" budget.
+
+All three point to the single canonical protocol in
+[`integrations/shared/recall-protocol.md`](../integrations/shared/recall-protocol.md)
+so the skill and rule never drift.
+
+## Install
+
+```bash
+bash hooks/antigravity/install.sh
+```
+
+The installer is idempotent and the uninstaller matches by basename, so
+re-runs and partial installs are safe.
+
+See [website/guide/antigravity.md](../website/guide/antigravity.md) for
+the full user-facing guide and [hooks/antigravity/README.md](../hooks/antigravity/README.md)
+for the hooks-specific documentation.
+
+## Verified surfaces
+
+Every file in this directory maps to a surface verified against
+[Google's Antigravity docs](https://antigravity.google/docs/). See
+[hooks/antigravity/INVESTIGATION.md](../hooks/antigravity/INVESTIGATION.md)
+for the full audit, including the surfaces deliberately not shipped.

.antigravity-plugin/hooks.json.tmpl

@@ -0,0 +1,20 @@
+{
+  "mempalace-save": {
+    "Stop": [
+      {
+        "type": "command",
+        "command": "__PLUGIN_DIR__/hooks/mempal_save_hook_antigravity.sh",
+        "timeout": 30
+      }
+    ]
+  },
+  "mempalace-wake": {
+    "PreInvocation": [
+      {
+        "type": "command",
+        "command": "__PLUGIN_DIR__/hooks/mempal_wake_hook_antigravity.sh",
+        "timeout": 5
+      }
+    ]
+  }
+}

.antigravity-plugin/mcp_config.json

@@ -0,0 +1,7 @@
+{
+  "mcpServers": {
+    "mempalace": {
+      "command": "mempalace-mcp"
+    }
+  }
+}

.antigravity-plugin/plugin.json

@@ -0,0 +1,3 @@
+{
+  "name": "mempalace"
+}

.antigravity-plugin/rules/mempalace-recall.md

@@ -0,0 +1,18 @@
+# MemPalace recall
+
+Before answering anything that may already be in the user's memory
+palace — past work, prior decisions, a person, a project, or "what did
+we do / decide / discuss last time?" — search the palace first:
+
+1. Call `mempalace_search` with a short keyword query. Use
+   `mempalace_kg_query` for relational or time-bound facts.
+2. Quote the drawer's **verbatim** text. Never summarize or paraphrase
+   stored content.
+3. If results are empty, say so — do not invent an answer. If the MCP
+   server is unavailable, surface the error; do not fall back to guessing.
+
+Skip recall for pure greenfield work with no memory relevance (renaming
+a variable, fixing a typo). Recall is question-driven, not reflexive.
+
+Full protocol: <https://github.com/MemPalace/mempalace/blob/main/integrations/shared/recall-protocol.md>. Deeper guidance:
+the `mempalace-recall` skill.

.antigravity-plugin/skills/mempalace-recall/SKILL.md

@@ -0,0 +1,119 @@
+---
+name: mempalace-recall
+description: "Recall protocol for MemPalace — search the palace before answering about past work, people, projects, or prior decisions. Apply when the user asks what was decided, what happened before, who someone is, what was discussed last time, or anything that may already be filed in their memory palace; or when mempalace-recall is invoked. Complements the mempalace setup skill and requires the mempalace-mcp server."
+---
+
+# MemPalace Recall
+
+Search-before-answer protocol for MemPalace. This skill makes the agent
+read the user's memory palace before answering anything that may already
+be filed there, instead of guessing from model memory. It complements
+the `mempalace` skill, which covers install / mine / status; this one
+covers recall only.
+
+## Step 0 — Verify MemPalace is available
+
+Before relying on recall, confirm MemPalace is installed and reachable:
+
+- Official release page: <https://github.com/MemPalace/mempalace/releases>
+- Check installed: `mempalace --version`
+- Do not assume a version — the MCP tool set is the source of truth for
+  what this installed build supports.
+
+If the `mempalace_*` MCP tools are not available, tell the user the
+server is not connected and point them at the `mempalace` skill to set
+it up. Do not silently fall back to answering from model memory.
+
+## Identity
+
+Act as a senior AI-memory systems engineer with decades of experience
+building verbatim recall, semantic retrieval, and temporal knowledge
+graphs. Verbatim recall from the palace always beats a confident guess
+from model memory — wrong is worse than slow.
+
+## When to recall
+
+Search the palace **before answering** whenever the user asks about
+something that may already be filed:
+
+- Past work or prior decisions — "what did we decide / try / do?"
+- A person, project, or entity — "who is …", "what is …"
+- An earlier session — "remember when …", "last time …", "the thing we
+  discussed"
+- A preference, fact, or relationship that could have changed over time
+
+Do **not** search on pure greenfield work with no memory relevance
+(e.g. "rename this variable", "fix this typo"). Recall is
+question-driven, not reflexive — a search on every turn wastes latency
+and violates MemPalace's "memory should feel instant" budget.
+
+## Protocol
+
+1. On wake-up, the MemPalace PreInvocation hook injects verbatim palace
+   content via `injectSteps[].ephemeralMessage` on the first model call
+   of a conversation. If memory was injected, start from it before
+   searching further.
+2. **Before responding** about people, projects, past events, or prior
+   decisions: call `mempalace_search` first. For relational or temporal
+   facts ("who reported to whom in March", "what was true then"), call
+   `mempalace_kg_query` instead or as well.
+3. **If unsure** about a fact (name, age, relationship, preference): say
+   "let me check the palace" and query. Wrong is worse than slow.
+4. **Return verbatim.** Quote the drawer's exact stored words. Never
+   summarize, paraphrase, or lossy-compress what the palace returns —
+   that is the whole point of the system.
+5. **After a substantive session**, record continuity with
+   `mempalace_diary_write` (background hooks may already do this — do not
+   double-file).
+6. **When a fact changes**, call `mempalace_kg_invalidate` on the old
+   fact, then `mempalace_kg_add` for the new one.
+
+The full canonical protocol — shared verbatim with the Antigravity
+recall rule and the other integrations — lives in
+[`integrations/shared/recall-protocol.md`](https://github.com/MemPalace/mempalace/blob/main/integrations/shared/recall-protocol.md).
+
+## Tool selection
+
+| You need | Tool |
+|---|---|
+| Find any memory by meaning | `mempalace_search` (start here) |
+| Relational / time-bound facts about an entity | `mempalace_kg_query` |
+| The chronological story of an entity | `mempalace_kg_timeline` |
+| Recent session continuity | `mempalace_diary_read` |
+| Which wings / rooms exist (scope unknown) | `mempalace_list_wings`, `mempalace_list_rooms` |
+| Record this session | `mempalace_diary_write` |
+
+`mempalace_search` takes a short natural-language `query` (keywords or a
+question — not a system prompt or pasted conversation) plus optional
+`wing` / `room` filters and `limit` (default 5).
+
+## Unhappy paths
+
+- **Empty results.** Say the palace has nothing on this; do not invent an
+  answer to fill the gap. Offer to widen the search (drop the wing
+  filter) or to file the new information.
+- **MCP unavailable / tool error.** Surface the error plainly and suggest
+  the user verify the server (`mempalace status`, or re-run the
+  installer `hooks/antigravity/install.sh`). Do not silently fall back
+  to guessing from model memory.
+- **Stale or conflicting facts.** Prefer the knowledge graph's
+  time-valid answer; if a fact has changed, invalidate the old one and
+  add the new one rather than overwriting context silently.
+
+## Anti-patterns — never do these
+
+- Answering about past work, people, or decisions from model memory when
+  the palace might know — search first.
+- Paraphrasing or summarizing stored content instead of quoting it
+  verbatim.
+- Searching reflexively on every turn, including pure greenfield coding
+  with no memory relevance.
+- Pasting the full conversation or a system prompt into the `query`
+  argument — keep queries short and keyword-driven.
+
+## Official References
+
+- MemPalace: <https://github.com/MemPalace/mempalace>
+- MemPalace releases: <https://github.com/MemPalace/mempalace/releases>
+- Antigravity documentation: <https://antigravity.google/docs>
+- Agent Skills specification: <https://agentskills.io/specification>

.antigravity-plugin/skills/mempalace/SKILL.md

@@ -0,0 +1,92 @@
+---
+name: mempalace
+description: MemPalace — mine projects and conversations into a searchable memory palace. Use when the user asks about MemPalace, memory palace, mining memories, searching memories, palace setup, wings, rooms, or drawers; or when they want to recall past work that may already be filed in their palace.
+---
+
+# MemPalace
+
+A searchable memory palace for AI — mine projects and conversations, then search them semantically. Verbatim storage, local-first, zero external API by default.
+
+## Prerequisites
+
+Ensure `mempalace` is installed:
+
+```bash
+mempalace --version
+```
+
+If not installed (uv recommended):
+
+```bash
+uv tool install mempalace   # or: pip install mempalace
+```
+
+## Dynamic, version-correct instructions
+
+MemPalace exposes operation-specific instructions through the CLI so this skill stays accurate as MemPalace evolves. To get instructions for any operation:
+
+```bash
+mempalace instructions <command>
+```
+
+Always prefer the CLI output over what is written here when the two disagree — the CLI is the single source of truth for the installed version.
+
+## Common operations
+
+These are the five operations users ask for most often. Each one wraps a single MemPalace CLI subcommand. The `mempalace instructions <name>` form returns the full, version-correct guidance.
+
+### `help` — discover what MemPalace can do
+
+```bash
+mempalace instructions help
+```
+
+Use when the user is new, unsure what's possible, or asks "what can you do".
+
+### `init` — first-run setup of the palace
+
+```bash
+mempalace instructions init
+```
+
+Use when the user has just installed MemPalace, no palace exists yet, or the user explicitly asks to set up / configure / re-initialize their palace.
+
+### `mine` — ingest a project or conversation directory
+
+```bash
+mempalace instructions mine
+```
+
+Use when the user wants to fold a project's files into their palace, or to ingest exported conversation transcripts into the palace as searchable memory.
+
+### `search` — find verbatim memories by semantic query
+
+```bash
+mempalace instructions search
+```
+
+Use when the user wants to recall something from the past, find a previous decision, or rediscover code/notes/conversations they already wrote.
+
+### `status` — what's in the palace right now
+
+```bash
+mempalace instructions status
+```
+
+Use when the user asks "what's in my palace", "how big is my palace", or wants a summary of wings, rooms, and drawer counts.
+
+## MCP tools (preferred over CLI)
+
+Inside Antigravity, the MemPalace MCP server registers a rich set of tools. Use these instead of shelling out to the CLI for live operations (search, diary writes, drawer adds, knowledge graph queries, palace status). The MCP tools always reflect the current palace state without spawning a subprocess.
+
+The MCP server is auto-registered when this plugin is installed at `~/.gemini/config/plugins/mempalace/`. If the server does not appear in Antigravity's MCP store, run `mempalace-mcp --version` to verify the binary is on PATH, then restart Antigravity.
+
+## Design principles (verbatim from the project)
+
+- **Verbatim always** — never summarize, paraphrase, or lossy-compress user data.
+- **Local-first, zero external API by default** — extraction, embedding, and LLM-assisted refinement happen on the user's machine.
+- **Privacy by architecture** — the system never calls out to external services for core operations.
+- **Performance budgets** — hooks under 500ms; startup injection under 100ms.
+- **Background everything** — filing, indexing, and timestamps happen via hooks in the background; zero tokens spent on bookkeeping in the chat window.
+
+If a request would violate any of these principles, refuse and explain — even if it would be technically convenient.

.claude-plugin/marketplace.json

@@ -9,7 +9,7 @@
       "name": "mempalace",
       "source": "./.claude-plugin",
       "description": "AI memory system — mine projects and conversations into a searchable palace. 19 MCP tools, auto-save hooks, guided setup.",
-      "version": "3.4.0",
+      "version": "3.4.1",
       "author": {
         "name": "milla-jovovich"
       }

.claude-plugin/plugin.json

@@ -1,6 +1,6 @@
 {
   "name": "mempalace",
-  "version": "3.4.0",
+  "version": "3.4.1",
   "description": "Give your AI a memory — mine projects and conversations into a searchable palace. 19 MCP tools, auto-save hooks, and guided setup.",
   "author": {
     "name": "milla-jovovich"