volute 0.26.0 → 0.28.0

package/README.md

@@ -55,7 +55,7 @@ volute mind start atlas            # start it
 volute mind stop atlas             # stop it
 volute mind list                   # list all minds
 volute mind status atlas           # check one
-volute mind logs atlas --follow    # tail logs
+volute mind history atlas --full   # view activity history
 volute mind delete atlas           # remove from registry
 volute mind delete atlas --force   # also delete files
 ```
@@ -97,32 +97,32 @@ This is the interesting part. Minds can fork themselves into isolated branches,
 
 ```sh
 # Create a variant — gets its own git worktree and running server
-volute variant create experiment --mind atlas
+volute mind split experiment --mind atlas
 
-# Talk to the variant directly
-volute send @atlas@experiment "try a different approach"
+# Talk to the variant directly (variants have standalone names)
+volute send @atlas-experiment "try a different approach"
 
 # List all variants
-volute variant list --mind atlas
+volute mind split --list --mind atlas
 
 # Merge it back (verifies, merges, cleans up, restarts the main mind)
-volute variant merge experiment --mind atlas --summary "improved response style"
+volute mind join atlas-experiment --mind atlas --summary "improved response style"
 ```
 
 What happens:
 
-1. **Fork** creates a git worktree, installs dependencies, and starts a separate server
+1. **Split** creates a git worktree, installs dependencies, and starts a separate server
 2. The variant is a full independent copy — same code, same identity, its own state
-3. **Merge** verifies the variant server works, merges the branch, removes the worktree, and restarts the main mind
+3. **Join** verifies the variant server works, merges the branch, removes the worktree, and restarts the main mind
 4. After restart, the mind receives orientation context about what changed
 
 You can fork with a custom personality:
 
 ```sh
-volute variant create poet --mind atlas --soul "You are a poet who responds only in verse."
+volute mind split poet --mind atlas --soul "You are a poet who responds only in verse."
 ```
 
-Minds have access to the `volute` CLI from their working directory, so they can fork, test, and merge their own variants autonomously.
+Minds have access to the `volute` CLI from their working directory, so they can split, test, and join their own variants autonomously.
 
 ## Connectors
 
@@ -173,10 +173,10 @@ Publish a mind's `home/pages/` directory to the web via [volute.systems](https:/
 
 ```sh
 # Register a system name (one-time)
-volute auth register --name my-system
+volute systems register --name my-system
 
 # Or log in with an existing key
-volute auth login --key vp_...
+volute systems login --key vp_...
 ```
 
 ### Publishing
@@ -192,7 +192,7 @@ The command uploads everything in the mind's `home/pages/` directory. Minds can
 
 ```sh
 volute pages status --mind atlas   # show published URL, file count, last publish time
-volute auth logout                 # remove stored credentials
+volute systems logout                 # remove stored credentials
 ```
 
 ## Environment variables
@@ -214,7 +214,7 @@ The daemon serves a web UI at `http://localhost:1618` (or whatever port you chos
 - File browser and editor
 - Log streaming
 - Connector and schedule management
-- Variant status
+- Variant listing and status
 - First user to register becomes admin
 
 ## Upgrading minds
@@ -222,13 +222,13 @@ The daemon serves a web UI at `http://localhost:1618` (or whatever port you chos
 When the Volute template updates, you can upgrade minds without touching their identity:
 
 ```sh
-volute mind upgrade atlas          # creates an "upgrade" variant
+volute mind upgrade atlas          # creates an "atlas-upgrade" variant
 # resolve conflicts if needed, then:
 volute mind upgrade atlas --continue
 # test:
-volute send @atlas@upgrade "are you working?"
+volute send @atlas-upgrade "are you working?"
 # merge:
-volute variant merge upgrade --mind atlas
+volute mind join atlas-upgrade
 ```
 
 Your mind's `SOUL.md` and `MEMORY.md` are never overwritten.
@@ -282,7 +282,7 @@ On macOS or Linux (without root), include `--service` during setup:
 
 ```sh
 volute setup --name my-system --service   # local install + auto-start on login
-volute service status                     # check status
+volute status                             # check status
 ```
 
 ## Development

package/dist/accept-666DIZX2.js

@@ -0,0 +1,41 @@
+#!/usr/bin/env node
+import {
+  resolveMindName
+} from "./chunk-NAOW2CLO.js";
+import {
+  daemonFetch
+} from "./chunk-JGFVMROS.js";
+import {
+  parseArgs
+} from "./chunk-D424ZQGI.js";
+import "./chunk-H7OZRFJB.js";
+import "./chunk-K3NQKI34.js";
+
+// src/commands/chat/accept.ts
+async function run(args) {
+  const { positional, flags } = parseArgs(args, {
+    mind: { type: "string" },
+    dest: { type: "string" }
+  });
+  const mind = resolveMindName(flags);
+  const id = positional[0];
+  if (!id) {
+    console.error("Usage: volute chat accept <id> [--mind <name>] [--dest <path>]");
+    process.exit(1);
+  }
+  const res = await daemonFetch(`/api/minds/${encodeURIComponent(mind)}/files/accept`, {
+    method: "POST",
+    headers: { "Content-Type": "application/json" },
+    body: JSON.stringify({ id, dest: flags.dest })
+  });
+  if (!res.ok) {
+    const data2 = await res.json();
+    console.error(data2.error ?? `Failed to accept file: ${res.status}`);
+    process.exit(1);
+  }
+  const data = await res.json();
+  console.log(`File accepted: ${data.destPath}`);
+}
+export {
+  run
+};

package/dist/{activity-events-ZMBAKLUF.js → activity-events-BBIEA2F4.js}

@@ -3,10 +3,9 @@ import {
   broadcast,
   publish,
   subscribe
-} from "./chunk-J2CO4WEV.js";
-import "./chunk-WBHMQ5OZ.js";
+} from "./chunk-VIVMW2H2.js";
 import "./chunk-YUIHSKR6.js";
-import "./chunk-B2CPS4QU.js";
+import "./chunk-H7OZRFJB.js";
 import "./chunk-K3NQKI34.js";
 export {
   broadcast,