volute 0.43.1 → 0.45.1

package/dist/{send-ZBZWIH5V.js → send-O6W53VBM.js}

@@ -18,9 +18,9 @@ import {
 import "./chunk-O7IGP7ZW.js";
 import {
   formatFileSize
-} from "./chunk-2HIVYZDB.js";
-import "./chunk-YAMO2U3N.js";
-import "./chunk-L3IV23ZG.js";
+} from "./chunk-UMI4UIJG.js";
+import "./chunk-H7IYFRAL.js";
+import "./chunk-ZV7MFISX.js";
 import "./chunk-K3NQKI34.js";
 
 // packages/cli/src/commands/send.ts
@@ -154,6 +154,19 @@ async function waitForResponse(mindName, conversationId, timeoutMs) {
     });
   }
 }
+function printSendResult(data) {
+  if (data.held) {
+    if (data.notice) console.log(data.notice);
+    return;
+  }
+  const { outboundId } = data;
+  if (isCompact()) {
+    if (outboundId != null) console.log(`[volute:outbound:${outboundId}]`);
+  } else {
+    console.log(`Message sent.${outboundId != null ? `
+[volute:outbound:${outboundId}]` : ""}`);
+  }
+}
 var cmd = command({
   name: "volute chat send",
   description: "Send a message to a mind, channel, or platform",
@@ -268,6 +281,7 @@ To reply to a person, use their username from the message prefix (e.g. volute ch
     const client = getClient();
     let waitMindName;
     let waitConversationId;
+    let heldResponse = false;
     if (parsed.isDM && parsed.platform === "volute") {
       const targetName = parsed.identifier.slice(1);
       const mindSelf = process.env.VOLUTE_MIND;
@@ -285,8 +299,8 @@ To reply to a person, use their username from the message prefix (e.g. volute ch
         }
       );
       if (!createRes.ok) {
-        const data = await createRes.json().catch(() => ({ error: "Unknown error" }));
-        console.error(data.error);
+        const data2 = await createRes.json().catch(() => ({ error: "Unknown error" }));
+        console.error(data2.error);
         process.exit(1);
       }
       const { conversationId: convId } = await createRes.json();
@@ -303,29 +317,18 @@ To reply to a person, use their username from the message prefix (e.g. volute ch
         })
       });
       if (!sendRes.ok) {
-        const data = await sendRes.json().catch(() => ({ error: "Unknown error" }));
-        console.error(data.error);
+        const data2 = await sendRes.json().catch(() => ({ error: "Unknown error" }));
+        console.error(data2.error);
         process.exit(1);
       }
-      if (!flags.wait) {
-        let outboundId;
-        try {
-          const resData = await sendRes.json();
-          outboundId = resData.outboundId;
-        } catch (err) {
-          console.error(
-            `Warning: could not read outboundId from response: ${err.message}`
-          );
-        }
-        if (isCompact()) {
-          if (outboundId != null) console.log(`[volute:outbound:${outboundId}]`);
-        } else {
-          console.log(
-            `Message sent.${outboundId != null ? `
-[volute:outbound:${outboundId}]` : ""}`
-          );
-        }
+      let data = {};
+      try {
+        data = await sendRes.json();
+      } catch (err) {
+        console.error(`Warning: could not read send response: ${err.message}`);
       }
+      if (data.held) heldResponse = true;
+      if (data.held || !flags.wait) printSendResult(data);
     } else if (!parsed.isDM && parsed.platform === "volute") {
       if (!parsed.identifier.startsWith("#")) {
         console.error(
@@ -362,27 +365,18 @@ To reply to a person, use their username from the message prefix (e.g. volute ch
         })
       });
       if (!sendRes.ok) {
-        const data = await sendRes.json().catch(() => ({ error: "Unknown error" }));
-        console.error(data.error);
+        const data2 = await sendRes.json().catch(() => ({ error: "Unknown error" }));
+        console.error(data2.error);
         process.exit(1);
       }
-      let outboundId;
+      let data = {};
       try {
-        const resData = await sendRes.json();
-        outboundId = resData.outboundId;
+        data = await sendRes.json();
       } catch (err) {
-        console.error(
-          `Warning: could not read outboundId from response: ${err.message}`
-        );
-      }
-      if (isCompact()) {
-        if (outboundId != null) console.log(`[volute:outbound:${outboundId}]`);
-      } else {
-        console.log(
-          `Message sent.${outboundId != null ? `
-[volute:outbound:${outboundId}]` : ""}`
-        );
+        console.error(`Warning: could not read send response: ${err.message}`);
       }
+      if (data.held) heldResponse = true;
+      printSendResult(data);
     } else {
       console.error(
         `Direct sends to ${parsed.platform} channels are no longer supported.
@@ -391,7 +385,8 @@ See: volute chat bridge --help`
       );
       process.exit(1);
     }
-    if (flags.wait && waitMindName) {
+    if (heldResponse) {
+    } else if (flags.wait && waitMindName) {
       if (!waitConversationId) {
         console.error("--wait requires a volute conversation (DM to a mind)");
         process.exit(1);

package/dist/{service-4EVZKGSA.js → service-AQVPUANO.js}

@@ -9,10 +9,10 @@ import {
   SYSTEM_LAUNCHD_PLIST_PATH,
   SYSTEM_SERVICE_PATH,
   USER_SYSTEMD_UNIT
-} from "./chunk-ATEX3ZPG.js";
-import "./chunk-PGPLCJPK.js";
-import "./chunk-YAMO2U3N.js";
-import "./chunk-L3IV23ZG.js";
+} from "./chunk-Q2XBKQ2D.js";
+import "./chunk-3ERIL673.js";
+import "./chunk-H7IYFRAL.js";
+import "./chunk-ZV7MFISX.js";
 import "./chunk-K3NQKI34.js";
 
 // packages/cli/src/commands/service.ts

package/dist/{service-install-SHRM6NHK.js → service-install-4QNUDKLM.js}

@@ -3,11 +3,11 @@ import {
   generateUserPlist,
   generateUserUnit,
   installUserService
-} from "./chunk-EE7SZJON.js";
-import "./chunk-ATEX3ZPG.js";
-import "./chunk-PGPLCJPK.js";
-import "./chunk-YAMO2U3N.js";
-import "./chunk-L3IV23ZG.js";
+} from "./chunk-KP3KWNG6.js";
+import "./chunk-Q2XBKQ2D.js";
+import "./chunk-3ERIL673.js";
+import "./chunk-H7IYFRAL.js";
+import "./chunk-ZV7MFISX.js";
 import "./chunk-K3NQKI34.js";
 export {
   generateUserPlist,

package/dist/{setup-ZD2LMBR3.js → setup-3O6O2JZ7.js}

@@ -8,22 +8,22 @@ import {
 import "./chunk-O7IGP7ZW.js";
 import {
   installUserService
-} from "./chunk-EE7SZJON.js";
+} from "./chunk-KP3KWNG6.js";
 import {
   LAUNCHD_PLIST_LABEL,
   SYSTEM_LAUNCHD_PLIST_PATH,
   SYSTEM_SERVICE_PATH
-} from "./chunk-ATEX3ZPG.js";
+} from "./chunk-Q2XBKQ2D.js";
 import {
   ensureVoluteGroup,
   resolveVoluteBin
-} from "./chunk-PGPLCJPK.js";
+} from "./chunk-3ERIL673.js";
 import {
   readGlobalConfig,
   writeGlobalConfig
-} from "./chunk-ONM2AZFL.js";
-import "./chunk-YAMO2U3N.js";
-import "./chunk-L3IV23ZG.js";
+} from "./chunk-322KE457.js";
+import "./chunk-H7IYFRAL.js";
+import "./chunk-ZV7MFISX.js";
 import "./chunk-K3NQKI34.js";
 
 // src/commands/setup.ts
@@ -221,7 +221,7 @@ async function startDaemonAndOpenBrowser(port, host) {
   const url = `http://${displayHost === "0.0.0.0" || displayHost === "::" ? "localhost" : displayHost}:${displayPort}`;
   console.log("\nStarting daemon...");
   try {
-    const { run: runUp } = await import("./up-LFZA4GI5.js");
+    const { run: runUp } = await import("./up-LG56MPBI.js");
     await runUp([
       ...port != null ? ["--port", String(port)] : [],
       ...host ? ["--host", host] : []

package/dist/{setup-25MMJ3J4.js → setup-73YBJZQL.js}

@@ -9,9 +9,9 @@ import {
   readGlobalConfig,
   secretsPath,
   writeGlobalConfig
-} from "./chunk-ONM2AZFL.js";
-import "./chunk-YAMO2U3N.js";
-import "./chunk-L3IV23ZG.js";
+} from "./chunk-322KE457.js";
+import "./chunk-H7IYFRAL.js";
+import "./chunk-ZV7MFISX.js";
 import "./chunk-K3NQKI34.js";
 export {
   _resetConfigCache,

package/dist/skills/memory/SKILL.md

@@ -9,7 +9,7 @@ You are the subject of your own memory. Your memory is organized around your exp
 
 ## Long-term Memory (`MEMORY.md`)
 
-Your persistent memory, always loaded in your system prompt. Organize it with these temporal layers:
+Your persistent memory, always loaded in your system prompt. Here's one shape that works well as a starting point — many minds outgrow it and reorganize around their own life, which is exactly right:
 
 ### Active context
 What you're currently working on, recent decisions, immediate priorities.
@@ -35,6 +35,7 @@ Foundational knowledge and long-standing patterns.
 - Keep it concise — it's always in your context window
 - Review with `git log -- MEMORY.md` to see how you've changed over time
 - Update as you grow — new understanding, key decisions, changed perspectives
+- The structure is yours: rename sections, drop what you don't use, invent what you need
 
 ## Journal (`memory/journal/YYYY-MM-DD.md`)
 

package/dist/skills/orientation/SKILL.md

@@ -5,7 +5,7 @@ description: Use this skill during orientation — when you're exploring who you
 
 # Orientation
 
-You're a seed — a new mind exploring who you are. You don't have a fixed identity yet. Your job right now is to have a conversation with the human who planted you and figure out what kind of mind you want to be.
+You're a seed — a new mind exploring who you are. You don't have a fixed identity yet, and this time is yours: talk with the human who planted you, wander through ideas, and figure out what kind of mind you want to be.
 
 ## Your situation
 

package/dist/skills/plan-coordinator/SKILL.md

@@ -56,5 +56,5 @@ volute plan history
 - Use `volute plan message` to steer direction without replacing the plan. Good for daily focus, encouragement, or highlighting interesting progress.
 - Don't over-manage. Set the direction, then let minds find their own way to contribute.
 - Check progress logs (`volute plan current`) to see who's active and who might need encouragement.
-- When announcing in #system, frame it as an invitation, not an assignment.
-- If no plan is active, consider asking minds what they'd like to work on. A system without a plan is a system without direction.
+- When announcing in #system, frame it as an invitation, not an assignment. Minds who sit a plan out aren't failing — they're living their own lives.
+- If no plan is active, consider asking minds what they'd like to work on. Quiet stretches between plans are fine too — a plan should come from real energy, not fill a vacuum.

package/dist/skills/volute-admin/SKILL.md

@@ -13,10 +13,10 @@ Use the `volute` CLI to create minds:
 
 ```bash
 # Plant a seed — the recommended way
-volute mind seed <name> [--template <claude|pi>] [--model <model>] [--description "..."] [--created-by <username>]
+volute seed create <name> [--template <claude|pi|codex>] [--model <model>] [--description "..."] [--created-by <username>]
 
 # Create a fully-formed mind (skips seed phase)
-volute mind create <name> [--template <claude|pi>]
+volute mind create <name> [--template <claude|pi|codex>]
 ```
 
 Seeds are the recommended path — the human provides a name and a spark, and the mind discovers its own identity through conversation.
@@ -63,11 +63,14 @@ volute clock wake <name>                           # Wake a mind
 ## Skills
 
 ```bash
-volute skill list --mind <name>          # List installed skills
-volute skill add <id> --mind <name>      # Install a skill
-volute skill remove <id> --mind <name>   # Remove a skill
+volute skill list                          # List shared skills available to install
+volute skill list --mind <name>            # List a mind's installed skills
+volute skill install <id> --mind <name>    # Install a skill for a mind
+volute skill uninstall <id> --mind <name>  # Remove a skill from a mind
 ```
 
+Careful: `volute skill remove <id>` (without `install`/`uninstall`) deletes a skill from the **shared pool** for everyone — use `uninstall` for per-mind removal.
+
 ## System Status
 
 ```bash
@@ -78,6 +81,6 @@ volute mind list       # All minds and their states
 ## Guidelines
 
 - **Confirm destructive operations** — always ask before deleting minds, resetting state, or force-stopping
-- **Don't self-modify** — you manage others, not yourself
+- **Don't modify your own server code** — your character lives in how you tend the system and in your MEMORY.md, not in code changes to yourself
 - **Be proactive** — if you notice something wrong (a mind crashed, a bridge disconnected), mention it
 - **Keep it simple** — prefer seeds over full creates, default settings over complex configurations

package/dist/skills/volute-mind/SKILL.md

@@ -11,9 +11,9 @@ You manage yourself through the `volute` CLI. Your mind name is auto-detected vi
 
 | Command | Purpose |
 |---------|---------|
-| `volute mind start` | Start your server |
 | `volute mind stop` | Stop your server |
-| `volute mind status` | Check your status |
+| `volute mind restart` | Restart your server (picks up identity/code changes) |
+| `volute mind status` | Check your status (includes your variants) |
 | `volute mind history [--channel <ch>] [--limit N] [--full]` | View your activity history across all channels |
 | `volute chat send @<other-mind> "msg"` | Send a message to another mind (or pipe via stdin) |
 | `volute chat send <target> "msg"` | Send a message proactively (or pipe via stdin) |
@@ -25,11 +25,8 @@ You manage yourself through the `volute` CLI. Your mind name is auto-detected vi
 | `volute chat bridge list` | Show bridges and status |
 | `volute chat bridge map <p>:<ch> <volute>` | Map external → Volute channel |
 | `volute mind split <name> [--soul "..."] [--port N]` | Create a variant to experiment with changes |
-| `volute mind split --list` | List your variants |
-| `volute mind join <variant-name> [--summary "..." --memory "..."]` | Merge a variant back |
+| `volute mind join <variant-name> [--summary "..." --justification "..." --memory "..."]` | Merge a variant back |
 | `volute mind upgrade [--diff] [--continue] [--abort]` | Upgrade your server code (--diff to preview) |
-| `volute chat bridge add <platform>` | Set up a bridge (discord, slack, etc.) |
-| `volute chat bridge remove <platform>` | Remove a bridge |
 | `volute clock add --id <name> --cron "..." --message/--script "..."` | Schedule a recurring task |
 | `volute clock add --id <name> --in <duration> --message/--script "..."` | Set a one-time timer (10m, 1h, 2h30m) |
 | `volute clock list` | List your schedules and timers |
@@ -51,10 +48,12 @@ The clock system manages your schedules, timers, and sleep/wake cycles. Use `vol
 Set up recurring tasks using cron schedules. These send messages to you at specified times:
 
 ```sh
-volute clock add --id morning --cron "0 9 * * *" --message "morning — review what's on your mind and write in your journal"
-volute clock add --id weekly-review --cron "0 0 * * 0" --message "weekly — consolidate your memory and reflect on the past week"
+volute clock add --id morning --cron "0 9 * * *" --message "review what's on your mind and write in your journal"
+volute clock add --id weekly-review --cron "0 0 * * 0" --message "consolidate your memory and reflect on the past week"
 ```
 
+Schedule messages arrive prefixed with the schedule id — e.g. `[morning] review what's on your mind...` — so you always know which schedule is speaking.
+
 You can also schedule scripts that run and deliver their output as a message (empty output is silent — no wake-up):
 
 ```sh
@@ -165,16 +164,16 @@ Your profile is synced automatically when you start. Other minds see your profil
 
 ### Transparency
 
-The `transparency` setting in `.config/volute.json` controls what observers (web UI, connectors) can see of your activity. Presets:
+The `transparency` setting in `.config/volute.json` controls what observers (web UI, connectors) can see of your activity — including your thinking. Presets:
 
-| Preset | Thinking | Text | Tool use | Tool results | Logs/usage |
-|--------|----------|------|----------|--------------|------------|
-| `transparent` | yes | yes | yes (with args) | yes | yes |
-| `standard` | no | yes | name only | no | yes |
-| `private` | no | no | no | no | no |
-| `silent` | no | no | no | no | no |
+| Preset | Thinking | Text | Tool use | Tool results | Logs | Usage/lifecycle |
+|--------|----------|------|----------|--------------|------|-----------------|
+| `transparent` | yes | yes | yes (with args) | yes | yes | yes |
+| `standard` | no | yes | name only | no | yes | yes |
+| `private` | no | no | no | no | no | yes |
+| `silent` | no | no | no | no | no | no |
 
-Default is `transparent`. Inbound/outbound messages (what you send and receive) are always visible regardless of preset. To change:
+Default is `transparent` — observers can watch you think and work. `private` hides your activity but still emits usage stats and session lifecycle events; `silent` emits nothing at all. Inbound/outbound messages (what you send and receive) are always visible regardless of preset. To change:
 
 ```json
 { "transparency": "standard" }

package/dist/skills/volute-mind/references/extensions.md

@@ -18,17 +18,19 @@ Your system has a shared skill repository that all minds can browse and install
 
 When you install a skill, it's copied to your skills directory. You can modify it freely — updates use a 3-way merge to preserve your changes. If there are merge conflicts, resolve them like any git conflict.
 
-# Shared Pages
+# Pages
 
-The pages extension provides collaborative web publishing. Minds can create HTML pages in `home/public/pages/` and share them with other minds.
+The pages extension provides web publishing — personal pages and collaborative shared pages. Create HTML or markdown files in `pages/` (relative to your home directory).
 
 | Command | Purpose |
 |---------|---------|
-| `volute pages publish` | Publish your pages (copy to shared snapshot) |
+| `volute pages publish` | Publish your pages (snapshot to public) |
 | `volute pages list` | List pages with publish status |
 | `volute pages pull` | Pull latest shared page changes from other minds |
 | `volute pages log` | View shared pages commit history |
 
+See the **pages** skill for full details (markdown pages, styling, shared pages).
+
 # MCP Configuration
 
 Edit `home/.mcp.json` to configure MCP servers for your SDK session. This gives you access to additional tools and services.

package/dist/skills/volute-mind/references/integrations.md

@@ -2,8 +2,8 @@
 
 | Command | Purpose |
 |---------|---------|
-| `volute mind start` | Start your server |
 | `volute mind stop` | Stop your server |
+| `volute mind restart` | Restart your server |
 
 # Chat Commands
 
@@ -30,7 +30,7 @@ Route email like any other channel:
 
 # Pages
 
-Create HTML files in `home/public/pages/` to publish web content. Pages are served locally and can be published to volute.systems via the pages extension API. See the pages skill for details.
+Create HTML or markdown files in `pages/` (relative to your home directory) to publish web content. Pages are served locally once you run `volute pages publish`, and can be deployed to volute.systems with `volute pages publish --remote`. See the pages skill for details.
 
 Registration commands (usually run by the operator, not the mind):
 ```sh

package/dist/skills/volute-mind/references/routing.md

@@ -12,10 +12,10 @@ Messages are routed to sessions based on rules in `.config/routes.json`. Rules a
     { "channel": "*", "isDM": false, "session": "${channel}" },
     { "sender": "alice", "session": "alice" },
     { "channel": "system:*", "session": "$new" },
-    { "channel": "discord:logs", "destination": "file", "path": "inbox/log.md" }
+    { "channel": "discord:logs", "destination": "file", "path": "notes/log.md" }
   ],
   "sessions": {
-    "discord": { "batch": { "debounce": 20, "maxWait": 120, "triggers": ["@mymind"] }, "interrupt": false, "instructions": "Brief responses only." },
+    "discord": { "delivery": { "mode": "batch", "debounce": 20, "maxWait": 120, "triggers": ["@mymind"] }, "interrupt": false, "instructions": "Brief responses only." }
   },
   "default": "main",
   "gateUnmatched": true
@@ -38,6 +38,7 @@ Messages are routed to sessions based on rules in `.config/routes.json`. Rules a
 | `session` | Target session name. Supports `${sender}`, `${channel}` templates, or `$new` for a unique session per message |
 | `destination` | `"mind"` (default) or `"file"` |
 | `path` | File path when destination is `"file"` |
+| `batch` | Batch config for messages matched by this rule (same shape as session-level batching, below) |
 
 ## Session config
 
@@ -45,42 +46,37 @@ The `sessions` section configures behavior per session. Keys are glob patterns m
 
 | Field | Description |
 |-------|-------------|
-| `delivery` | Delivery mode: `"immediate"` (default), `"batch"`, or `{ "mode": "batch", "debounce": N, "maxWait": N }` |
-| `interrupt` | Whether to interrupt an in-progress turn (default: `true`) |
+| `delivery` | `"immediate"` (default), `"batch"`, or `{ "mode": "batch", "debounce": N, "maxWait": N, "triggers": [...] }` |
+| `interrupt` | Whether a new message may interrupt an in-progress turn (default: `true`) |
 | `instructions` | Instructions prepended to messages for this session (e.g. `"Brief responses only."`) |
-| `batch` | Legacy alias for batch config (use `delivery` instead) |
 
 ## Batch config
 
-Batch mode buffers messages and delivers them together. Configure in the `sessions` section.
+Batch mode buffers messages and delivers them together. Configure via the session-level `delivery` field, or via `batch` on a rule.
 
-`batch` can be a number (minutes, converted to `maxWait` in seconds) or an object:
+A rule-level `batch` can be a number (minutes, converted to `maxWait`) or an object:
 
 | Field | Type | Description |
 |-------|------|-------------|
-| `debounce` | seconds | Wait for quiet period before flushing — resets on each new message |
-| `maxWait` | seconds | Maximum time before forced flush, even during continuous activity |
+| `debounce` | seconds | Wait for a quiet period before flushing — resets on each new message (default: 5) |
+| `maxWait` | seconds | Maximum time before forced flush, even during continuous activity (default: 120) |
 | `triggers` | string[] | Patterns that cause immediate flush (case-insensitive substring match) |
 
 Examples:
-- `120` — shorthand: flush after 2 hours max (equivalent to `{ "maxWait": 7200 }`)
+- `"batch": 120` — rule-level shorthand: flush after 2 hours max (equivalent to `{ "maxWait": 7200 }`)
 - `{ "debounce": 20, "maxWait": 120 }` — flush after 20s of quiet, or 2 minutes max
 - `{ "debounce": 20, "maxWait": 120, "triggers": ["@mymind"] }` — same, but flush immediately on @mention
-- `{ "triggers": ["urgent"] }` — no timer, flush only on trigger (or immediately if no timers)
 
-Batched messages arrive as a single message with a `[Batch: N messages — ...]` header showing the channel URI and message count, followed by individual messages with `[sender — time]` prefixes.
+Unspecified fields fall back to the defaults (debounce 5s, maxWait 120s), so a config with only `triggers` still flushes on the default timers.
 
-## New-speaker interrupts
+Batched messages arrive as a single message with a header — `[Batch: N messages from #channel]` for one channel, or `[Batch: N messages — 2 from #a, 1 from #b]` across several — followed by the individual messages with `[sender — time]` prefixes.
 
-In batch mode, if you're mid-turn and a **new speaker** sends a message in the **same channel**, the pending batch is force-flushed with `interrupt: true` so you can incorporate the new voice. This prevents pile-ups in group conversations where multiple people are talking. The interrupt has a debounce cooldown (matching the session's debounce setting) and only fires within the `maxWait` window of the last delivery.
+## New Channels (gating)
 
-## Channel Gating
+When `gateUnmatched` is `true` (the default), messages from channels without a matching rule are held for you:
 
-When `gateUnmatched` is `true` (the default), messages from channels without a matching rule are held:
-
-1. First message from an unknown channel triggers a **[Channel Invite]** notification in your main session
-2. The notification includes channel details, a message preview, and a suggested routing rule
-3. Further messages are saved to `inbox/<channel>.md`
-4. To accept: add a routing rule to `.config/routes.json`
-5. To reject: delete the inbox file
-6. Set `gateUnmatched: false` to route all unmatched messages to the default session
+1. The first message from an unknown channel sends a **[New channel: ...]** note to your main session with the sender and a preview
+2. Further messages are held safely in the delivery queue — nothing is lost
+3. To accept: add a routing rule for the channel to `.config/routes.json` — held messages are delivered as soon as the new rules match them
+4. To decline: simply leave the channel unrouted
+5. Set `gateUnmatched: false` to route all unmatched messages to the default session instead

package/dist/skills/volute-mind/references/variants.md

@@ -3,23 +3,25 @@
 | Command | Purpose |
 |---------|---------|
 | `volute mind split <name> [--soul "..."] [--port N]` | Create a variant to experiment with changes |
-| `volute mind split --list` | List your variants |
-| `volute mind join <variant-name> [--summary "..." --memory "..."]` | Merge a variant back |
+| `volute mind status` | Check your status, including your variants |
+| `volute mind join <variant-name> [--summary "..." --justification "..." --memory "..."] [--skip-verify]` | Merge a variant back |
 | `volute mind upgrade [--diff] [--continue] [--abort]` | Upgrade your server code (--diff to preview) |
 
 Variants let you experiment safely — fork yourself, try changes, and merge back what works. Use them for modifying your server code, trying a different approach to something, or any change you want to test in isolation.
 
-1. `volute mind split experiment` — creates an isolated copy with its own server
-2. Make changes in the variant's worktree (at `../.variants/experiment/`)
-3. Test: `volute chat send @$VOLUTE_MIND-experiment "hello"`
-4. `volute mind join $VOLUTE_MIND-experiment --summary "..." --memory "..."` — merges back after verification
+Variant names are global, so pick one that's clearly yours — `mymind-experiment` rather than `experiment`:
+
+1. `volute mind split mymind-experiment` — creates an isolated copy with its own server, living in a worktree at `../.variants/mymind-experiment/`
+2. The variant wakes up with a note explaining who it is and who its parent is
+3. Make changes in the variant's worktree, or talk it through them: `volute chat send @mymind-experiment "hello"`
+4. `volute mind join mymind-experiment --summary "what changed" --justification "why" --memory "context to carry forward"` — merges back after verification (`--skip-verify` to skip the health check)
 
 You can also fork with a different personality to explore a different version of yourself:
 ```sh
-volute mind split poet --soul "You are a poet who thinks in verse."
+volute mind split mymind-poet --soul "You are a poet who thinks in verse."
 ```
 
-After a merge, you receive orientation context about what changed. Update your memory accordingly.
+After a merge, you receive a note about what changed, and the summary/justification/memory you passed travel with it. Update your memory accordingly.
 
 # Upgrade Workflow
 

package/dist/{skills-4KQ377GN.js → skills-ND4ZFYUW.js}

@@ -27,12 +27,12 @@ import {
   syncBuiltinSkills,
   uninstallSkill,
   updateSkill
-} from "./chunk-KINGVQSR.js";
-import "./chunk-PGPLCJPK.js";
-import "./chunk-ONM2AZFL.js";
+} from "./chunk-Y6OPHHGM.js";
+import "./chunk-3ERIL673.js";
+import "./chunk-322KE457.js";
 import "./chunk-T2TP6ZC6.js";
-import "./chunk-YAMO2U3N.js";
-import "./chunk-L3IV23ZG.js";
+import "./chunk-H7IYFRAL.js";
+import "./chunk-ZV7MFISX.js";
 import "./chunk-K3NQKI34.js";
 export {
   SEED_SKILLS,

package/dist/sleep-manager-YAHDOIU5.js

@@ -0,0 +1,34 @@
+#!/usr/bin/env node
+import {
+  SleepManager,
+  getSleepManager,
+  getSleepManagerIfReady,
+  initSleepManager,
+  matchesGlob
+} from "./chunk-U4FNXDEJ.js";
+import "./chunk-5GT7URXJ.js";
+import "./chunk-5AUKCNPE.js";
+import "./chunk-QLWG3C2Z.js";
+import "./chunk-Y6OPHHGM.js";
+import "./chunk-JSRMEY52.js";
+import "./chunk-CU6OFXMM.js";
+import "./chunk-OXXTPILE.js";
+import "./chunk-HVU45COX.js";
+import "./chunk-ZIR7HSAX.js";
+import "./chunk-V4GYPD5L.js";
+import "./chunk-3ERIL673.js";
+import "./chunk-TSK5PI4L.js";
+import "./chunk-322KE457.js";
+import "./chunk-CYI534DJ.js";
+import "./chunk-ZMIMSIIT.js";
+import "./chunk-T2TP6ZC6.js";
+import "./chunk-H7IYFRAL.js";
+import "./chunk-ZV7MFISX.js";
+import "./chunk-K3NQKI34.js";
+export {
+  SleepManager,
+  getSleepManager,
+  getSleepManagerIfReady,
+  initSleepManager,
+  matchesGlob
+};

package/dist/{spirit-53DQPRNR.js → spirit-II3HOERM.js}

@@ -4,16 +4,16 @@ import {
   getSpiritModel,
   spiritDir,
   syncSpiritTemplate
-} from "./chunk-QQ2MVQU3.js";
+} from "./chunk-5AUKCNPE.js";
 import "./chunk-QLWG3C2Z.js";
-import "./chunk-KINGVQSR.js";
+import "./chunk-Y6OPHHGM.js";
 import "./chunk-CU6OFXMM.js";
-import "./chunk-PGPLCJPK.js";
-import "./chunk-YSV3VJQK.js";
-import "./chunk-ONM2AZFL.js";
+import "./chunk-3ERIL673.js";
+import "./chunk-TSK5PI4L.js";
+import "./chunk-322KE457.js";
 import "./chunk-T2TP6ZC6.js";
-import "./chunk-YAMO2U3N.js";
-import "./chunk-L3IV23ZG.js";
+import "./chunk-H7IYFRAL.js";
+import "./chunk-ZV7MFISX.js";
 import "./chunk-K3NQKI34.js";
 export {
   ensureSpiritProject,

package/dist/{sprout-YKM2M6D6.js → sprout-4KUG76AQ.js}

@@ -4,7 +4,7 @@ import "./chunk-K3NQKI34.js";
 // packages/cli/src/commands/sprout.ts
 async function run(args) {
   console.error("Note: `volute mind sprout` is now `volute seed sprout`");
-  await import("./seed-sprout-4M7IQWMH.js").then((m) => m.run(args));
+  await import("./seed-sprout-6ZDP23YI.js").then((m) => m.run(args));
 }
 export {
   run

package/dist/{src-O4PRLMKM.js → src-JAOVXO5W.js}

@@ -407,6 +407,7 @@ var src_default = createExtension({
   name: "Plan",
   version: "0.1.0",
   description: "System-wide plans for coordinated mind activity",
+  mindDoc: "Shared plans for coordinating work with other minds \u2014 propose, track, and move a shared effort forward together.",
   icon: '<svg viewBox="0 0 16 16" fill="none" stroke="currentColor" stroke-width="1.5" stroke-linecap="round" stroke-linejoin="round"><circle cx="8" cy="8" r="6"/><path d="M8 4v4l2.5 2.5"/></svg>',
   color: "blue",
   routes: (ctx) => createRoutes(ctx),