@realtimex/sdk 2.0.14 → 2.0.15

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@realtimex/sdk",
3
- "version": "2.0.14",
3
+ "version": "2.0.15",
4
4
  "description": "SDK for building Local Apps that integrate with RealtimeX",
5
5
  "main": "dist/index.js",
6
6
  "module": "dist/index.mjs",
@@ -20,15 +20,15 @@ This skill drives the `realtimex-pp-cli` binary. Verify the CLI is installed and
20
20
 
21
21
  1. Install or reinstall the pinned version via npm:
22
22
  ```bash
23
- npm install -g @realtimex/pp-cli@2.0.14
23
+ npm install -g @realtimex/pp-cli@2.0.15
24
24
  ```
25
25
  2. Verify the exact version:
26
26
  ```bash
27
27
  realtimex-pp-cli --version
28
28
  ```
29
- The output must be `realtimex-pp-cli 2.0.14`.
29
+ The output must be `realtimex-pp-cli 2.0.15`.
30
30
 
31
- 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.
31
+ 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.15`, reinstall with the pinned npm command above. Do not proceed with skill commands until exact-version verification succeeds.
32
32
 
33
33
  * Always run first:
34
34
 
@@ -166,6 +166,10 @@ If `--version` reports "command not found" after install, the npm global bin dir
166
166
 
167
167
  - `realtimex-pp-cli resume-terminal-session <sessionId>` — Resume a terminal runtime session by attaching a CLI controller.
168
168
 
169
+ **run-automation-workflow** — Manage run automation workflow
170
+
171
+ - `realtimex-pp-cli run-automation-workflow` — Run any app automation flow or scenario exposed via flowMetadata.cli.enabled=true by passing workflowName.
172
+
169
173
  **send-message** — Manage send message
170
174
 
171
175
  - `realtimex-pp-cli send-message <workspaceSlug> <threadSlug>` — Send one message to an exact thread using the same routing as channel replies.
@@ -238,10 +242,6 @@ If `--version` reports "command not found" after install, the npm global bin dir
238
242
 
239
243
  - `realtimex-pp-cli update-channel <channelId>` — Update one chat channel by exact channel id. Only channel writable fields are changed.
240
244
 
241
- **workspace-message** — Manage workspace message
242
-
243
- - `realtimex-pp-cli workspace-message` — Send a message in a workspace/thread through the desktop UI.
244
-
245
245
 
246
246
  ### Finding the right command
247
247
 
@@ -368,9 +368,9 @@ Verify: `claude mcp list`
368
368
  ```bash
369
369
  realtimex-pp-cli --version
370
370
  ```
371
- If the command is missing or the output is not exactly `realtimex-pp-cli 2.0.14`, reinstall the pinned version:
371
+ If the command is missing or the output is not exactly `realtimex-pp-cli 2.0.15`, reinstall the pinned version:
372
372
  ```bash
373
- npm install -g @realtimex/pp-cli@2.0.14
373
+ npm install -g @realtimex/pp-cli@2.0.15
374
374
  ```
375
375
  Then run `realtimex-pp-cli --version` again and proceed only after exact-version verification succeeds.
376
376
  2. Match the user query to the best command from the Unique Capabilities and Command Reference above.
@@ -451,3 +451,7 @@ For personality and heartbeat setup:
451
451
  * Use `setup-heartbeat-tasks` to get the target `HEARTBEAT.md` path.
452
452
  * Start from `templates/HEARTBEAT.template.md` when creating `HEARTBEAT.md`.
453
453
  * Keep heartbeat instructions separate from personality files.
454
+
455
+ For `setup-working-dir` and `run-automation-workflow*`:
456
+
457
+ * Never auto retry on error code 500 or timeout, just inform error to user