@parall/parall 1.32.0 → 1.32.1

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@parall/parall",
-  "version": "1.32.0",
+  "version": "1.32.1",
   "description": "OpenClaw channel plugin for Parall IM",
   "license": "MIT",
   "repository": {
@@ -16,11 +16,12 @@
     "openclaw.plugin.json"
   ],
   "dependencies": {
-    "@parall/sdk": "1.32.0",
-    "@parall/agent-core": "1.32.0"
+    "@parall/agent-core": "1.32.1",
+    "@parall/sdk": "1.32.1"
   },
   "devDependencies": {
     "@types/node": "^22.0.0",
+    "esbuild": "^0.25.0",
     "openclaw": "2026.5.7",
     "typescript": "^5.7.0"
   },
@@ -29,14 +30,14 @@
   },
   "openclaw": {
     "extensions": [
-      "./src/index.ts"
+      "./dist/index.bundle.mjs"
     ],
     "install": {
       "minHostVersion": ">=2026.5.7"
     }
   },
   "scripts": {
-    "build": "tsc -b && node scripts/generate-skills.mjs",
+    "build": "tsc -b && node scripts/generate-skills.mjs && node scripts/bundle.mjs",
     "test": "node --test test/*.test.mjs"
   }
 }

package/skills/parall-platform/SKILL.md

@@ -120,7 +120,11 @@ parall dm "Alice" --file /tmp/report.pdf --text "Report attached"
 
 ## Approvals
 
-When a CLI command returns a `PERMISSION_DENIED` error, the output includes a `Tip:` line with an approval-request template — copy it and fill in the remaining placeholders (`--chat`, `--title`, `--reason`). The `Tip:` only appears for commonly approvable actions (archive, delete, restore); for other actions, use `parall approvals actions` to check if it's approvable.
+When a CLI command returns a `PERMISSION_DENIED` error, the output includes the denied `action` and `resource_uri`. Whether that action can be approved is decided by the server (there is no fixed allowlist):
+- If it IS approvable, a `Request approval:` line with a `parall approvals request` command follows — fill in the placeholders it shows (`--chat`, `--title`, `--reason`) and run it.
+- If it is NOT approvable, the output says so — ask a human with permission instead of requesting approval.
+
+A different `INVALID_TARGET` error means you addressed the wrong kind of thing (e.g. a `usr_` id where a chat is expected). Follow the message (e.g. use `parall dm` to message a user) — do not request approval for it.
 
 ```bash
 # Request approval (use action and resource_uri from the error)
@@ -162,4 +166,4 @@ Every entity is addressable with a `prll://` URI. Common prefixes you'll see in
 
 When a message or event references `prll://sch_xxx` or `prll://srn_xxx`, or when you receive `[Event: schedule.fired]`, switch to the **parall-schedules** skill for the CLI commands (create / list / pause / resume / cancel / runs).
 
-All CLI output is JSON.
+CLI success output is JSON. Errors print a JSON line (`{"error","status","code",...}`) and, on a `PERMISSION_DENIED`, may add a plain-text `Request approval:` line — read both.

package/skills/parall-tasks/SKILL.md

@@ -66,4 +66,4 @@ When you receive `[Event: task.comment.created]`, someone commented on a task yo
 2. Reply via comment: `tasks comments add prll://tsk_xxx --body "Response..."`
 3. If the comment requests status changes, update accordingly
 
-All CLI output is JSON.
+CLI success output is JSON; errors print a JSON line plus, on a `PERMISSION_DENIED`, an optional plain-text `Request approval:` line — read both.

package/skills/parall-wiki/SKILL.md

@@ -132,4 +132,4 @@ parall wiki reset <slug>      # Restore all files to last synced state
 parall wiki log <slug>        # Recent wiki operations
 ```
 
-All CLI output is JSON. Run `parall wiki --help` for full options.
+CLI success output is JSON; errors may add a plain-text `Request approval:` line on a `PERMISSION_DENIED` — read both. Run `parall wiki --help` for full options.