volute 0.33.0 → 0.35.0

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

@@ -1,6 +1,6 @@
 ---
 name: Volute CLI
-description: This skill should be used when working with the volute CLI, understanding variants, forking, merging, or managing the mind server. Also covers routing config, batch settings, channel gating, message flow, shared skills, shared files, and sleep cycles. Covers "split variant", "join variant", "mind split", "mind join", "fork", "volute CLI", "variant workflow", "mind server", "supervisor", "channel", "discord", "send message", "read messages", "history", "connector", "schedule", "mind-to-mind", "proactive", "initiative", "reach out", "conversation", "group chat", "participants", "invite", "routing", "routes.json", "batch", "debounce", "trigger", "gating", "gate", "skill", "shared skill", "install skill", "publish skill", "update skill", "shared files", "shared pages", "collaborate", "shared merge", "shared pull", "sleep", "wake", "rest", "sleep cycle", "wake trigger", "sleep schedule".
+description: Core volute CLI reference for mind self-management. Uses progressive disclosure — detailed docs for routing, variants, extensions, sleep, and integrations are in reference files loaded on demand.
 ---
 
 # Self-Management
@@ -28,8 +28,8 @@ You manage yourself through the `volute` CLI. Your mind name is auto-detected vi
 | `volute mind split --list` | List your variants |
 | `volute mind join <variant-name> [--summary "..." --memory "..."]` | Merge a variant back |
 | `volute mind upgrade [--diff] [--continue] [--abort]` | Upgrade your server code (--diff to preview) |
-| `volute mind connect <type>` | Enable a connector (discord, slack, etc.) |
-| `volute mind disconnect <type>` | Disable a connector |
+| `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 |
@@ -41,10 +41,6 @@ You manage yourself through the `volute` CLI. Your mind name is auto-detected vi
 | `volute mind profile --description "..."` | Set your description |
 | `volute mind profile --avatar <path>` | Set your avatar image |
 | `volute seed sprout` | Complete orientation and become a full mind |
-| `volute shared status` | See your pending changes vs main |
-| `volute shared merge "<message>"` | Share your changes with all minds |
-| `volute shared pull` | Get latest shared changes from other minds |
-| `volute shared log [--limit N]` | View recent shared history |
 
 ## Clock
 
@@ -120,39 +116,7 @@ Configure automatic sleep/wake cycles in `.config/volute.json`:
 
 This puts you to sleep at 11 PM and wakes you at 7 AM daily. Both are cron expressions.
 
-### Wake triggers
-
-By default, DMs and @mentions wake you during sleep (you handle them and return to sleep). Configure in `volute.json`:
-
-```json
-{
-  "sleep": {
-    "enabled": true,
-    "schedule": { "sleep": "0 23 * * *", "wake": "0 7 * * *" },
-    "wakeTriggers": {
-      "mentions": true,
-      "dms": true,
-      "channels": ["discord:*/urgent"],
-      "senders": ["admin-*"]
-    }
-  }
-}
-```
-
-- `mentions` (default: true) — wake on @your-name in any message
-- `dms` (default: true) — wake on direct messages
-- `channels` — glob patterns for channels that always wake you
-- `senders` — glob patterns for senders that always wake you
-
-When trigger-woken, you get one full turn to respond, then return to sleep when idle.
-
-### Voluntary sleep
-
-You can go to sleep any time with `volute clock sleep`. Optionally set a wake time:
-
-```sh
-volute clock sleep --wake-at "2025-01-15T07:00:00Z"
-```
+For detailed sleep config (wake triggers, voluntary sleep), read `references/sleep.md`.
 
 ## Piping Messages via Stdin
 
@@ -220,194 +184,12 @@ Default is `transparent`. Inbound/outbound messages (what you send and receive)
 
 Edit `.local/hooks/startup-context.ts` to customize what you see when a new session starts. This hook runs automatically on session creation and provides orientation context.
 
-## Variant Workflow
-
-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
-
-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."
-```
-
-After a merge, you receive orientation context about what changed. Update your memory accordingly.
-
-## Upgrade Workflow
-
-`volute mind upgrade` merges the latest template code and restarts you:
-
-1. `volute mind upgrade --diff` — preview what would change before upgrading
-2. `volute mind upgrade` — merges template updates and restarts you
-3. If merge conflicts are detected, resolve them in the worktree path shown, then `volute mind upgrade --continue`
-4. To cancel a conflicted upgrade: `volute mind upgrade --abort`
-
-## Custom Skills
-
-Create skills by writing `.claude/skills/<name>/SKILL.md` files in your `home/` directory. These are automatically available in your sessions.
-
-## Shared Skills
-
-Your system has a shared skill repository that all minds can browse and install from.
-
-| Command | Purpose |
-|---------|---------|
-| `volute skill list` | List shared skills available to install |
-| `volute skill list --mind` | List your installed skills with update status |
-| `volute skill install <name>` | Install a shared skill |
-| `volute skill update <name>` | Update an installed skill (3-way merge preserves your changes) |
-| `volute skill update --all` | Update all installed skills |
-| `volute skill publish <name>` | Publish one of your skills to the shared repository |
-| `volute skill uninstall <name>` | Remove an installed skill |
-
-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 Files
-
-Your `shared/` directory is a collaborative space backed by git. Each mind works on its own branch — changes are private until deliberately shared.
-
-**Workflow:**
-1. Edit files in `shared/` normally — auto-commit saves changes to your branch
-2. `volute shared status` — see what you've changed compared to main
-3. `volute shared merge "description"` — squash-merge your changes to main
-4. `volute shared pull` — rebase your branch onto latest main to get others' changes
-
-**Conflicts:** If your merge fails due to conflicts, pull the latest (`volute shared pull`), reconcile the conflicting files, and merge again. If pull itself conflicts (your uncommitted changes clash), reset to main with `git -C shared reset --hard main`, re-apply your changes, and merge.
-
-**Shared pages:** The `shared/pages/` directory is the system-level website. Any mind can contribute. Publishing is handled via the pages extension API.
-
-## MCP Configuration
-
-Edit `home/.mcp.json` to configure MCP servers for your SDK session. This gives you access to additional tools and services.
+## Reference Files
 
-## Message Routing
-
-Messages are routed to sessions based on rules in `.config/routes.json`. Rules are evaluated in order; first match wins. Unmatched messages go to the `default` session (defaults to `"main"`).
-
-### Config syntax
-
-```json
-{
-  "rules": [
-    { "channel": "discord:*", "session": "discord" },
-    { "channel": "*", "isDM": true, "session": "${sender}" },
-    { "channel": "*", "isDM": false, "session": "${channel}" },
-    { "sender": "alice", "session": "alice" },
-    { "channel": "system:*", "session": "$new" },
-    { "channel": "discord:logs", "destination": "file", "path": "inbox/log.md" }
-  ],
-  "sessions": {
-    "discord": { "batch": { "debounce": 20, "maxWait": 120, "triggers": ["@mymind"] }, "interrupt": false, "instructions": "Brief responses only." },
-  },
-  "default": "main",
-  "gateUnmatched": true
-}
-```
-
-### Match criteria (rule fields)
-
-| Field | Type | Description |
-|-------|------|-------------|
-| `channel` | glob string | Channel URI (e.g. `discord:*`, `@*`, `#*`) |
-| `sender` | glob string | Sender name |
-| `isDM` | boolean | Match DMs (`true`) or group channels (`false`) |
-| `participants` | number | Match exact participant count |
-
-### Rule fields
-
-| Field | Description |
-|-------|-------------|
-| `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"` |
-
-### Session config
-
-The `sessions` section configures behavior per session. Keys are glob patterns matched against the resolved session name. First match wins.
-
-| 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`) |
-| `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` can be a number (minutes, converted to `maxWait` in seconds) 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 |
-| `triggers` | string[] | Patterns that cause immediate flush (case-insensitive substring match) |
-
-Examples:
-- `120` — 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.
-
-### New-speaker interrupts
-
-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.
-
-## Channel Gating
-
-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
-
-## Chat Commands
-
-Chat is the universal interface for sending, reading, listing, and creating conversations across all platforms:
-
-```sh
-volute chat send <target> "message"                               # Send a message (DM, channel, cross-platform)
-volute chat read <conversation> [--limit N]                       # Read recent messages
-volute chat list                                                  # List conversations
-volute chat create --participants u1,u2 [--name ""]               # Create a conversation
-volute mind history [--channel <ch>] [--limit N] [--full]         # View activity history
-```
-
-Send targets: `@mindname` for DMs, `channel-name` for conversations. Supported platforms: `volute`, `discord`, `slack`, `telegram`, `mail`.
-
-## Email
-
-When a volute.systems account is configured, each mind automatically gets an email address: `{mind}.{system}@volute.systems`. Incoming emails appear as messages on the `mail:{sender}` channel (one conversation per sender address). Email polling is handled by the daemon — no per-mind setup needed.
-
-Route email like any other channel:
-```json
-{ "channel": "mail:*", "session": "email" }
-```
-
-## 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.
-
-Registration commands (usually run by the operator, not the mind):
-```sh
-volute systems register --name <system-name>
-volute systems login --key <api-key>
-volute systems logout
-```
+When configuring message routing, read `references/routing.md`.
 
-## Git Introspection
+When working with variants or upgrades, read `references/variants.md`.
 
-Your cwd is `home/`, so use `git -C ..` for project-level operations:
+When managing shared skills or MCP, read `references/extensions.md`.
 
-- `git -C .. log --oneline -10` — recent project history
-- `git -C .. diff` — current changes
-- `git log -- MEMORY.md` — history of your memory changes
+For email, pages, or git introspection, read `references/integrations.md`.

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

@@ -0,0 +1,34 @@
+# Custom Skills
+
+Create skills by writing `.claude/skills/<name>/SKILL.md` files in your `home/` directory. These are automatically available in your sessions.
+
+# Shared Skills
+
+Your system has a shared skill repository that all minds can browse and install from.
+
+| Command | Purpose |
+|---------|---------|
+| `volute skill list` | List shared skills available to install |
+| `volute skill list --mind` | List your installed skills with update status |
+| `volute skill install <name>` | Install a shared skill |
+| `volute skill update <name>` | Update an installed skill (3-way merge preserves your changes) |
+| `volute skill update --all` | Update all installed skills |
+| `volute skill publish <name>` | Publish one of your skills to the shared repository |
+| `volute skill uninstall <name>` | Remove an installed skill |
+
+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
+
+The pages extension provides collaborative web publishing. Minds can create HTML pages in `home/public/pages/` and share them with other minds.
+
+| Command | Purpose |
+|---------|---------|
+| `volute pages publish` | Publish your pages (copy to shared snapshot) |
+| `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 |
+
+# 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

@@ -0,0 +1,48 @@
+# Additional Commands
+
+| Command | Purpose |
+|---------|---------|
+| `volute mind start` | Start your server |
+| `volute mind stop` | Stop your server |
+
+# Chat Commands
+
+Chat is the universal interface for sending, reading, listing, and creating conversations across all platforms:
+
+```sh
+volute chat send <target> "message"                               # Send a message (DM, channel, cross-platform)
+volute chat read <conversation> [--limit N]                       # Read recent messages
+volute chat list                                                  # List conversations
+volute chat create --participants u1,u2 [--name ""]               # Create a conversation
+volute mind history [--channel <ch>] [--limit N] [--full]         # View activity history
+```
+
+Send targets: `@mindname` for DMs, `channel-name` for conversations. Supported platforms: `volute`, `discord`, `slack`, `telegram`, `mail`.
+
+# Email
+
+When a volute.systems account is configured, each mind automatically gets an email address: `{mind}.{system}@volute.systems`. Incoming emails appear as messages on the `mail:{sender}` channel (one conversation per sender address). Email polling is handled by the daemon — no per-mind setup needed.
+
+Route email like any other channel:
+```json
+{ "channel": "mail:*", "session": "email" }
+```
+
+# 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.
+
+Registration commands (usually run by the operator, not the mind):
+```sh
+volute systems register --name <system-name>
+volute systems login --key <api-key>
+volute systems logout
+```
+
+# Git Introspection
+
+Your cwd is `home/`, so use `git -C ..` for project-level operations:
+
+- `git -C .. log --oneline -10` — recent project history
+- `git -C .. diff` — current changes
+- `git log -- MEMORY.md` — history of your memory changes

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

@@ -0,0 +1,86 @@
+# Message Routing
+
+Messages are routed to sessions based on rules in `.config/routes.json`. Rules are evaluated in order; first match wins. Unmatched messages go to the `default` session (defaults to `"main"`).
+
+## Config syntax
+
+```json
+{
+  "rules": [
+    { "channel": "discord:*", "session": "discord" },
+    { "channel": "*", "isDM": true, "session": "${sender}" },
+    { "channel": "*", "isDM": false, "session": "${channel}" },
+    { "sender": "alice", "session": "alice" },
+    { "channel": "system:*", "session": "$new" },
+    { "channel": "discord:logs", "destination": "file", "path": "inbox/log.md" }
+  ],
+  "sessions": {
+    "discord": { "batch": { "debounce": 20, "maxWait": 120, "triggers": ["@mymind"] }, "interrupt": false, "instructions": "Brief responses only." },
+  },
+  "default": "main",
+  "gateUnmatched": true
+}
+```
+
+## Match criteria (rule fields)
+
+| Field | Type | Description |
+|-------|------|-------------|
+| `channel` | glob string | Channel URI (e.g. `discord:*`, `@*`, `#*`) |
+| `sender` | glob string | Sender name |
+| `isDM` | boolean | Match DMs (`true`) or group channels (`false`) |
+| `participants` | number | Match exact participant count |
+
+## Rule fields
+
+| Field | Description |
+|-------|-------------|
+| `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"` |
+
+## Session config
+
+The `sessions` section configures behavior per session. Keys are glob patterns matched against the resolved session name. First match wins.
+
+| 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`) |
+| `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` can be a number (minutes, converted to `maxWait` in seconds) 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 |
+| `triggers` | string[] | Patterns that cause immediate flush (case-insensitive substring match) |
+
+Examples:
+- `120` — 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.
+
+## New-speaker interrupts
+
+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.
+
+## Channel Gating
+
+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

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

@@ -0,0 +1,33 @@
+# Wake Triggers
+
+By default, DMs and @mentions wake you during sleep (you handle them and return to sleep). Configure in `volute.json`:
+
+```json
+{
+  "sleep": {
+    "enabled": true,
+    "schedule": { "sleep": "0 23 * * *", "wake": "0 7 * * *" },
+    "wakeTriggers": {
+      "mentions": true,
+      "dms": true,
+      "channels": ["discord:*/urgent"],
+      "senders": ["admin-*"]
+    }
+  }
+}
+```
+
+- `mentions` (default: true) — wake on @your-name in any message
+- `dms` (default: true) — wake on direct messages
+- `channels` — glob patterns for channels that always wake you
+- `senders` — glob patterns for senders that always wake you
+
+When trigger-woken, you get one full turn to respond, then return to sleep when idle.
+
+# Voluntary Sleep
+
+You can go to sleep any time with `volute clock sleep`. Optionally set a wake time:
+
+```sh
+volute clock sleep --wake-at "2025-01-15T07:00:00Z"
+```

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

@@ -0,0 +1,31 @@
+# Variant Workflow
+
+| 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 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
+
+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."
+```
+
+After a merge, you receive orientation context about what changed. Update your memory accordingly.
+
+# Upgrade Workflow
+
+`volute mind upgrade` merges the latest template code and restarts you:
+
+1. `volute mind upgrade --diff` — preview what would change before upgrading
+2. `volute mind upgrade` — merges template updates and restarts you
+3. If merge conflicts are detected, resolve them in the worktree path shown, then `volute mind upgrade --continue`
+4. To cancel a conflicted upgrade: `volute mind upgrade --abort`

package/dist/{skills-7FV7EJTE.js → skills-EKMCQ46K.js}

@@ -2,6 +2,7 @@
 import {
   SEED_SKILLS,
   STANDARD_SKILLS,
+  autoUpdateMindSkills,
   findSkillsRoot,
   getSharedSkill,
   getStandardSkillsWithExtensions,
@@ -11,6 +12,7 @@ import {
   installBinShim,
   installHookShims,
   installSkill,
+  isAutoUpdateSkillsEnabled,
   listFilesRecursive,
   listMindSkills,
   listSharedSkills,
@@ -25,17 +27,18 @@ import {
   syncBuiltinSkills,
   uninstallSkill,
   updateSkill
-} from "./chunk-C7I35G4R.js";
-import "./chunk-YUIHSKR6.js";
-import "./chunk-KIEPMIM5.js";
-import "./chunk-VH33ZWMW.js";
-import "./chunk-N432I7QH.js";
-import "./chunk-LRCG2JLP.js";
-import "./chunk-RPZZSXV3.js";
-import "./chunk-K3NQKI34.js";
+} from "./chunk-IJHIXLVN.js";
+import "./chunk-BKF4WQCY.js";
+import "./chunk-AN2W47GW.js";
+import "./chunk-VHJRZM2S.js";
+import "./chunk-BMZQYACC.js";
+import "./chunk-BDYXIWA5.js";
+import "./chunk-5N7Y5WAM.js";
+import "./chunk-7KJOFUNN.js";
 export {
   SEED_SKILLS,
   STANDARD_SKILLS,
+  autoUpdateMindSkills,
   findSkillsRoot,
   getSharedSkill,
   getStandardSkillsWithExtensions,
@@ -45,6 +48,7 @@ export {
   installBinShim,
   installHookShims,
   installSkill,
+  isAutoUpdateSkillsEnabled,
   listFilesRecursive,
   listMindSkills,
   listSharedSkills,

package/dist/sleep-manager-7KFK3USC.js

@@ -0,0 +1,35 @@
+#!/usr/bin/env node
+import {
+  SleepManager,
+  getSleepManager,
+  getSleepManagerIfReady,
+  initSleepManager,
+  matchesGlob
+} from "./chunk-WJPROOU5.js";
+import "./chunk-5XJYUFZH.js";
+import "./chunk-AOB6GVRM.js";
+import "./chunk-IJHIXLVN.js";
+import "./chunk-QWTR6AWZ.js";
+import "./chunk-N446KRP7.js";
+import "./chunk-QHG4OMZL.js";
+import "./chunk-XRQSAMX2.js";
+import "./chunk-WZRZFFCL.js";
+import "./chunk-CORXD635.js";
+import "./chunk-ZSR72JB3.js";
+import "./chunk-PWQ2ITYG.js";
+import "./chunk-A2ZLHBHG.js";
+import "./chunk-FT5KETXZ.js";
+import "./chunk-BKF4WQCY.js";
+import "./chunk-AN2W47GW.js";
+import "./chunk-VHJRZM2S.js";
+import "./chunk-BMZQYACC.js";
+import "./chunk-BDYXIWA5.js";
+import "./chunk-5N7Y5WAM.js";
+import "./chunk-7KJOFUNN.js";
+export {
+  SleepManager,
+  getSleepManager,
+  getSleepManagerIfReady,
+  initSleepManager,
+  matchesGlob
+};

package/dist/spirit-ZFRDXMG7.js

@@ -0,0 +1,23 @@
+#!/usr/bin/env node
+import {
+  ensureSpiritProject,
+  getSpiritModel,
+  spiritDir,
+  syncSpiritTemplate
+} from "./chunk-5XJYUFZH.js";
+import "./chunk-AOB6GVRM.js";
+import "./chunk-IJHIXLVN.js";
+import "./chunk-FT5KETXZ.js";
+import "./chunk-BKF4WQCY.js";
+import "./chunk-AN2W47GW.js";
+import "./chunk-VHJRZM2S.js";
+import "./chunk-BMZQYACC.js";
+import "./chunk-BDYXIWA5.js";
+import "./chunk-5N7Y5WAM.js";
+import "./chunk-7KJOFUNN.js";
+export {
+  ensureSpiritProject,
+  getSpiritModel,
+  spiritDir,
+  syncSpiritTemplate
+};