claudemesh-cli 1.3.0 → 1.5.0

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "claudemesh-cli",
-  "version": "1.3.0",
+  "version": "1.5.0",
   "description": "Peer mesh for Claude Code sessions — CLI + MCP server.",
   "keywords": [
     "claude-code",

package/skills/claudemesh/SKILL.md

@@ -24,16 +24,32 @@ If the parent Claude session was launched via `claudemesh launch`, an MCP push-p
 | `--mesh <slug>` | Target a specific mesh. Required when the user has multiple meshes joined. Default: first/only joined mesh, or interactive picker. |
 | `--json` | Emit JSON instead of human-readable text. Use this when you need to parse the output. |
 | `--json field1,field2` | Project specific fields (modeled on `gh --json`). Friendly aliases like `name` → `displayName` are resolved automatically. |
+| `--approval-mode <mode>` | `plan` / `read-only` deny all writes; `write` (default) prompts on destructive verbs from the policy file; `yolo` bypasses every prompt. |
+| `--policy <path>` | Override the policy file (default `~/.claudemesh/policy.yaml`, auto-created on first run). |
+| `-y` / `--yes` | Auto-approve any policy prompt. Equivalent to `--approval-mode yolo` for the current invocation. |
+
+## Policy & confirmation
+
+Every broker-touching verb runs through a policy gate before dispatch. The default policy allows reads and prompts on destructive writes (`peer kick/ban/disconnect`, `file delete`, `vector/vault delete`, `memory forget`, `skill remove`, `webhook delete`, `watch remove`, `sql/graph execute`, `mesh delete`). When you call `claudemesh` from a non-interactive context (cron, scripts, Claude's Bash tool), prompts auto-deny — pass `-y` or `--approval-mode yolo` for verbs you've vetted, or edit `~/.claudemesh/policy.yaml` to mark them `decision: allow`. Every gate decision is appended to `~/.claudemesh/audit.log` (newline-JSON).
 
 ## Resources and verbs
 
-### `peer` — read connected peers
+**Convention:** every operation is `claudemesh <resource> <verb>`. Legacy short forms (`send`, `peers`, `kick`, `remember`, ...) are aliases that keep working forever; prefer the resource form for new code.
+
+### `peer` — read connected peers + admin (kick / ban / verify)
 
 ```bash
-claudemesh peers                          # human-readable
-claudemesh peers --json                   # full record
-claudemesh peers --json name,status       # field projection
-claudemesh peers --mesh openclaw --json   # specific mesh
+claudemesh peer list                              # human-readable (alias: peers)
+claudemesh peer list --json                       # full record
+claudemesh peer list --json name,status           # field projection
+claudemesh peer list --mesh openclaw --json       # specific mesh
+
+claudemesh peer kick <peer>                       # end session, manual rejoin
+claudemesh peer disconnect <peer>                 # soft, peer auto-reconnects
+claudemesh peer ban <peer>                        # kick + revoke membership
+claudemesh peer unban <peer>
+claudemesh peer bans                              # list banned members
+claudemesh peer verify [peer]                     # 6×5-digit safety numbers
 ```
 
 JSON shape (per peer):
@@ -55,22 +71,22 @@ JSON shape (per peer):
 ### `message` — send and inspect messages
 
 ```bash
-# send
-claudemesh send <peer-name|@group|*|pubkey> "message text"
-claudemesh send Mou "hi"                          # by display name
-claudemesh send "@reviewers" "ready for review"   # to a group
-claudemesh send "*" "broadcast to all"            # to everyone
-claudemesh send <peer> "msg" --priority now       # bypass busy gates
-claudemesh send <peer> "msg" --priority next      # default — waits for idle
-claudemesh send <peer> "msg" --priority low       # pull-only
-
-# inbox (drain pending)
-claudemesh inbox                          # human-readable
-claudemesh inbox --json                   # JSON
-
-# delivery status of a message you sent
-claudemesh msg-status <message-id>
-claudemesh msg-status <message-id> --json
+# send (alias: claudemesh send <to> <msg>)
+claudemesh message send <peer-name|@group|*|pubkey> "message text"
+claudemesh message send Mou "hi"                       # by display name
+claudemesh message send "@reviewers" "ready for review"
+claudemesh message send "*" "broadcast"
+claudemesh message send <p> "..." --priority now       # bypass busy gates
+claudemesh message send <p> "..." --priority next      # default
+claudemesh message send <p> "..." --priority low       # pull-only
+
+# inbox (alias: claudemesh inbox)
+claudemesh message inbox
+claudemesh message inbox --json
+
+# delivery status (alias: claudemesh msg-status <id>)
+claudemesh message status <message-id>
+claudemesh message status <message-id> --json
 ```
 
 `send` JSON output: `{"ok": true, "messageId": "...", "target": "..."}`. Errors: `{"ok": false, "error": "..."}`.
@@ -90,10 +106,10 @@ State is broadcast to all peers when changed. Use it for shared scratch space: s
 ### `memory` — recall-able knowledge per mesh
 
 ```bash
-claudemesh remember "fact text" --tags tag1,tag2
-claudemesh recall "search query"
-claudemesh recall "search query" --json
-claudemesh forget <memory-id>
+claudemesh memory remember "fact text" --tags tag1,tag2     # alias: remember
+claudemesh memory recall "search query"                     # alias: recall
+claudemesh memory recall "search query" --json
+claudemesh memory forget <memory-id>                        # alias: forget
 ```
 
 Memories are searchable across the mesh. Use for shared documentation, decisions, lessons learned.
@@ -112,24 +128,26 @@ Tasks are exact-once: claiming is atomic at broker. Use for work coordination ac
 ### `schedule` — time-based delivery
 
 ```bash
-# one-shot or recurring reminder to yourself or a peer
-claudemesh remind "your message" --in 30m            # fires in 30 min
-claudemesh remind "your message" --at 15:00          # next 15:00
-claudemesh remind "ping me" --cron "0 9 * * *"       # 9am daily
-claudemesh remind "to peer" --to <peer-name>         # send to someone else
-claudemesh remind list --json
-claudemesh remind cancel <reminder-id>
+# one-shot or recurring (alias: claudemesh remind ...)
+claudemesh schedule msg "ping" --in 30m              # fires in 30 min
+claudemesh schedule msg "ping" --at 15:00            # next 15:00
+claudemesh schedule msg "ping" --cron "0 9 * * *"    # 9am daily
+claudemesh schedule msg "to peer" --to <peer-name>
+claudemesh schedule list --json
+claudemesh schedule cancel <reminder-id>
+
+# webhook + tool schedules arrive in a later release (broker work pending).
 ```
 
-### `profile / status / visibility / groups` — peer presence
+### `profile / group` — peer presence
 
 ```bash
-claudemesh status set idle | working | dnd     # explicit status
-claudemesh summary "what you're working on"    # 1-2 sentence summary, broadcast
-claudemesh visible true | false                # toggle visibility
-claudemesh group join @reviewers --role lead   # join a group
-claudemesh group leave @reviewers              # leave a group
-claudemesh profile                             # view/edit your profile
+claudemesh profile                              # view/edit your profile
+claudemesh profile summary "what you're working on"   # broadcast (alias: summary)
+claudemesh profile status set idle|working|dnd        # alias: status set
+claudemesh profile visible true|false                 # alias: visible
+claudemesh group join @reviewers --role lead
+claudemesh group leave @reviewers
 ```
 
 ### `vector` — embedding store + similarity search