@pnds/pond 1.6.0 → 1.6.2

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@pnds/pond",
-  "version": "1.6.0",
+  "version": "1.6.2",
   "description": "OpenClaw channel plugin for Pond IM",
   "license": "MIT",
   "repository": {
@@ -15,8 +15,8 @@
     "openclaw.plugin.json"
   ],
   "dependencies": {
-    "@pnds/cli": "1.6.0",
-    "@pnds/sdk": "1.6.0"
+    "@pnds/cli": "1.6.2",
+    "@pnds/sdk": "1.6.2"
   },
   "devDependencies": {
     "@types/node": "^22.0.0",

package/skills/pond-wiki/SKILL.md

@@ -15,25 +15,57 @@ npx @pnds/cli@latest wiki tree <slug>                 # List files and directori
 npx @pnds/cli@latest wiki tree <slug> --path docs/    # List a subdirectory
 ```
 
-## Editing (requires local workspace)
+## Editing
 
-Wiki editing uses a local workspace. Sync first, edit files with standard tools, then propose.
+Wiki editing works on a **local workspace** — a directory on disk where wiki
+files are synced. You sync from the server, edit files locally, then propose
+a changeset.
+
+### Step 1: Sync
 
 ```bash
-# 1. Sync wiki to local workspace
 npx @pnds/cli@latest wiki sync <slug>
+```
+
+This downloads wiki files to a local directory. The output includes the
+**absolute mount path** for each wiki (e.g. `synced → /data/.openclaw/workspace/kb`).
+
+### Step 2: Find the mount path
+
+The sync output JSON contains `synced[].path` — the absolute path where files
+live. You can also check it anytime with:
+
+```bash
+npx @pnds/cli@latest wiki status <slug>
+```
+
+The output includes `Mount: /absolute/path/to/<slug>`.
 
-# 2. Edit files locally (they live under POND_WIKI_MOUNT_ROOT)
-#    Use read/write/edit tools on the local files
+Use this path with `read`, `write`, and `edit` tools. For example, if the mount
+is `/data/.openclaw/workspace/kb`, then `README.md` is at
+`/data/.openclaw/workspace/kb/README.md`.
 
-# 3. Review changes
-npx @pnds/cli@latest wiki status <slug>               # Summary of local changes
-npx @pnds/cli@latest wiki diff <slug>                  # Unified diff
+### Step 3: Edit files
 
-# 4. Propose changeset
-npx @pnds/cli@latest wiki changeset create <slug> --title "My change"
+Use standard file tools (`read`, `write`, `edit`) on files under the mount path.
+
+### Step 4: Review changes
+
+```bash
+npx @pnds/cli@latest wiki diff <slug>       # Shows unified diff of all local changes
+npx @pnds/cli@latest wiki status <slug>     # Shows which files changed with +/- line counts
 ```
 
+Always review before proposing.
+
+### Step 5: Propose changeset
+
+```bash
+npx @pnds/cli@latest wiki changeset create <slug> --title "Description of changes"
+```
+
+This uploads your local changes as a changeset for review.
+
 ## Changeset Management
 
 ```bash
@@ -42,22 +74,24 @@ npx @pnds/cli@latest wiki changeset show <changesetId> <slug> # Show detail + fe
 npx @pnds/cli@latest wiki changeset diff <changesetId> <slug> # Show changeset diff
 ```
 
-If a changeset is rejected, fix the files and re-propose:
+If a changeset is rejected, fix the files locally and re-propose:
 
 ```bash
 npx @pnds/cli@latest wiki changeset create <slug> --update <changesetId>
 ```
 
-## History
+The title is inherited from the original changeset — no need to repeat it.
+
+## Discarding local changes
 
 ```bash
-npx @pnds/cli@latest wiki log <slug>                  # Recent operations
+npx @pnds/cli@latest wiki reset <slug>      # Restore all files to last synced state
 ```
 
-## Tips
+## History
 
-- Always `wiki diff` before proposing to verify the exact change.
-- Use `wiki tree` to browse the file structure without syncing.
-- After sync, read files directly from the local workspace — no need for a separate read command.
+```bash
+npx @pnds/cli@latest wiki log <slug>        # Recent wiki operations
+```
 
 All CLI output is JSON. Run `npx @pnds/cli@latest wiki --help` for full options.