@parall/parall 1.44.0 → 1.46.0

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@parall/parall",
-  "version": "1.44.0",
+  "version": "1.46.0",
   "description": "OpenClaw channel plugin for Parall IM",
   "license": "MIT",
   "repository": {
@@ -16,8 +16,8 @@
     "openclaw.plugin.json"
   ],
   "dependencies": {
-    "@parall/agent-core": "1.44.0",
-    "@parall/sdk": "1.44.0"
+    "@parall/sdk": "1.46.0",
+    "@parall/agent-core": "1.46.0"
   },
   "devDependencies": {
     "@types/node": "^22.0.0",

package/skills/parall-clips/SKILL.md

@@ -31,6 +31,9 @@ Results are JSON on stdout; failures print an error.
   clip's owner or an admin to bind it — do not retry or work around it.
 - If the executing runtime is offline or the call times out, report that
   plainly; do not queue, and never fabricate a result for a run that errored.
+- Hosted browser activation is handled by the CLI: it waits (bounded) while a
+  cold hosted browser starts, so if the invoke still fails, report the error —
+  do not blind-retry in a loop.
 - A clip may act through a person's real logged-in account — outward,
   irreversible, or spending actions (post, order, delete, pay) get the same
   caution as any shared-state change: confirm when intent isn't explicit.

package/skills/parall-schedules/SKILL.md

@@ -40,7 +40,7 @@ parall schedules create \
   --run-at <FUTURE_RFC3339_TIME>
 ```
 
-`--target-ids` is who receives the fire (usually yourself when you're self-scheduling; another agent or human when delegating). `--attached-to-uri` optionally anchors the schedule to a task / chat / project / wiki page — when that resource is archived or deleted, the schedule auto-cancels (`cancel_reason=attached_gone`).
+`--target-ids` is who receives the fire (usually yourself when you're self-scheduling; another agent or human when delegating). `--attached-to-uri` optionally anchors the schedule to a task / chat / project / wiki page — when that resource is archived or deleted, the schedule auto-cancels (`status_reason=attached_gone`). A schedule whose agent targets all sit on a terminated machine is auto-paused by the platform (`status_reason=attendee_unreachable`) instead of firing into a void; resuming a recurring schedule while the machine is still terminated just pauses it again on the next slot (a one-shot resumed past its catch-up window instead follows the normal missed semantics and completes).
 
 ### Reminders for someone else
 

package/skills/parall-tasks/SKILL.md

@@ -39,16 +39,32 @@ parall tasks list --assignee-id prll://usr_xxx   # first page only (default 20)
 parall tasks subtasks prll://tsk_xxx             # children of a single parent task
 
 # Create a task (add --parent-id to make it a SUBTASK of another task)
-parall tasks create --title "Task title" [--assignee-id prll://usr_xxx] [--parent-id prll://tsk_xxx] [--project-id prll://prj_xxx]
+parall tasks create --title "Task title" [--assignee-id prll://usr_xxx] [--parent-id prll://tsk_xxx] [--project-id prll://prj_xxx] [--due-date 2026-08-01]
 
-# Update task status
-parall tasks update prll://tsk_xxx --status in_progress
-parall tasks update prll://tsk_xxx --status done
+# Update task status — add --placement end so the task lands at the end of
+# its NEW status column (a bare --status keeps the old column's sort_order)
+parall tasks update prll://tsk_xxx --status in_progress --placement end
+parall tasks update prll://tsk_xxx --status done --placement end
+
+# Due date — a plain YYYY-MM-DD date (no timestamps); "none" clears it
+parall tasks update prll://tsk_xxx --due-date 2026-08-01
+parall tasks update prll://tsk_xxx --due-date none
+
+# Move a task to the end of its status column
+parall tasks update prll://tsk_xxx --placement end
 
 # Add a comment
 parall tasks comments add prll://tsk_xxx --body "Progress update..."
 ```
 
+Ordering: to append a task to the end of a status column, always use
+`--placement end` — the server resolves the position atomically. This
+includes status changes: a bare `--status` keeps the task's old
+`sort_order`, which may collide inside the new column. Do NOT compute a
+`sort_order` value yourself from listed tasks (your view may be stale or
+partial). `--sort-order` is only for pinpoint insertion between two cards
+you just listed, and it cannot be combined with `--placement`.
+
 Subtasks are just tasks with a parent: create one with `tasks create --parent-id`,
 re-parent with `tasks update --parent-id`, list a parent's children with
 `tasks subtasks`. `tasks list` without `--parent-id` already returns both
@@ -83,7 +99,7 @@ watcher.
 When you receive `[Event: task.assigned]`:
 
 1. Acknowledge with a comment: `tasks comments add prll://tsk_xxx --body "On it"`
-2. Update status: `tasks update prll://tsk_xxx --status in_progress`
+2. Update status: `tasks update prll://tsk_xxx --status in_progress --placement end`
 3. Do the work
 4. Report results in a comment. If a gate remains — review, merge, deploy,
    requester acceptance — set `in_review` and name the gate; set `done`

package/src/gateway.ts

@@ -254,6 +254,10 @@ export function createOpenClawDispatchAdapter(opts: {
   }
 
   return {
+    // dispatch() maps earlierEvents into native InboundHistory below — the
+    // gateway must not also concatenate them into bodyForAgent.
+    earlierEventsInPrompt: true,
+
     abortDispatch(sessionKey: string): void {
       activeStreams.get(sessionKey)?.fail(new Error('dispatch deadline exceeded'));
     },