@realtimex/sdk 2.0.14 → 2.0.16

package/package.json

@@ -1,6 +1,6 @@
 {
     "name": "@realtimex/sdk",
-    "version": "2.0.14",
+    "version": "2.0.16",
     "description": "SDK for building Local Apps that integrate with RealtimeX",
     "main": "dist/index.js",
     "module": "dist/index.mjs",

package/skills/realtimex-moderator-sdk/SKILL.md

@@ -20,15 +20,15 @@ This skill drives the `realtimex-pp-cli` binary. Verify the CLI is installed and
 
 1. Install or reinstall the pinned version via npm:
    ```bash
-   npm install -g @realtimex/pp-cli@2.0.14
+   npm install -g @realtimex/pp-cli@2.0.16
    ```
 2. Verify the exact version:
    ```bash
    realtimex-pp-cli --version
    ```
-   The output must be `realtimex-pp-cli 2.0.14`.
+   The output must be `realtimex-pp-cli 2.0.16`.
 
-If `--version` reports "command not found" after install, the npm global bin directory is not on `$PATH`. If it reports any version other than `2.0.14`, reinstall with the pinned npm command above. Do not proceed with skill commands until exact-version verification succeeds.
+If `--version` reports "command not found" after install, the npm global bin directory is not on `$PATH`. If it reports any version other than `2.0.16`, reinstall with the pinned npm command above. Do not proceed with skill commands until exact-version verification succeeds.
 
 * Always run first:
 
@@ -166,6 +166,14 @@ If `--version` reports "command not found" after install, the npm global bin dir
 
 - `realtimex-pp-cli resume-terminal-session <sessionId>` — Resume a terminal runtime session by attaching a CLI controller.
 
+**run-automation-workflow** — Manage run automation workflow
+
+- `realtimex-pp-cli run-automation-workflow` — Run any app automation flow or scenario exposed via flowMetadata.cli.enabled=true by passing workflowName.
+
+**send-channel-file** — Manage send channel file
+
+- `realtimex-pp-cli send-channel-file` — Send one local CLI file back to an external channel using an explicit channel delivery context id.
+
 **send-message** — Manage send message
 
 - `realtimex-pp-cli send-message <workspaceSlug> <threadSlug>` — Send one message to an exact thread using the same routing as channel replies.
@@ -238,10 +246,6 @@ If `--version` reports "command not found" after install, the npm global bin dir
 
 - `realtimex-pp-cli update-channel <channelId>` — Update one chat channel by exact channel id. Only channel writable fields are changed.
 
-**workspace-message** — Manage workspace message
-
-- `realtimex-pp-cli workspace-message` — Send a message in a workspace/thread through the desktop UI.
-
 
 ### Finding the right command
 
@@ -368,9 +372,9 @@ Verify: `claude mcp list`
    ```bash
    realtimex-pp-cli --version
    ```
-   If the command is missing or the output is not exactly `realtimex-pp-cli 2.0.14`, reinstall the pinned version:
+   If the command is missing or the output is not exactly `realtimex-pp-cli 2.0.16`, reinstall the pinned version:
    ```bash
-   npm install -g @realtimex/pp-cli@2.0.14
+   npm install -g @realtimex/pp-cli@2.0.16
    ```
    Then run `realtimex-pp-cli --version` again and proceed only after exact-version verification succeeds.
 2. Match the user query to the best command from the Unique Capabilities and Command Reference above.
@@ -421,6 +425,16 @@ For `send-message`:
 * If any of those values are missing or ambiguous, ask for the missing values before running the command.
 * Do not provide LLM provider/model arguments to `send-message`; the server routes the message based on the thread/workspace configuration.
 
+
+For `send-channel-file`:
+
+* Use this command only from a channel-linked terminal session that has `REALTIMEX_CHANNEL_DELIVERY_CONTEXT_ID` in its environment, or when the user explicitly provides a `chdel_*` context id.
+* Always pass the context explicitly. In channel-linked sessions use `--context "$REALTIMEX_CHANNEL_DELIVERY_CONTEXT_ID"`; use a literal `chdel_*` only when intentionally overriding for debugging.
+* Do not infer a destination from workspace, thread, recent activity, or channel metadata.
+* Send one file per command call. Repeat the command for multiple files.
+* In desktop/local runtime, the CLI should send the absolute local `filePath` to the server. The server validates the path against allowed storage/temp roots before sending through the channel. Base64 upload is fallback transport, not the preferred path.
+* The server validates the delivery context, active channel session, plugin state, runtime binding when supplied, and file size/type handling before delivery.
+
 For workspace default-agent setup:
 
 * Use `prepare.agents` only.
@@ -451,3 +465,7 @@ For personality and heartbeat setup:
 * Use `setup-heartbeat-tasks` to get the target `HEARTBEAT.md` path.
 * Start from `templates/HEARTBEAT.template.md` when creating `HEARTBEAT.md`.
 * Keep heartbeat instructions separate from personality files.
+
+For `setup-working-dir` and `run-automation-workflow*`:
+
+* Never auto retry on error code 500 or timeout, just inform error to user