@realtimex/sdk 2.0.9 → 2.0.10

package/package.json

@@ -1,6 +1,6 @@
 {
     "name": "@realtimex/sdk",
-    "version": "2.0.9",
+    "version": "2.0.10",
     "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.9
+   npm install -g @realtimex/pp-cli@2.0.10
    ```
 2. Verify the exact version:
    ```bash
    realtimex-pp-cli --version
    ```
-   The output must be `realtimex-pp-cli 2.0.9`.
+   The output must be `realtimex-pp-cli 2.0.10`.
 
-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.9`, 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.10`, reinstall with the pinned npm command above. Do not proceed with skill commands until exact-version verification succeeds.
 
 * Always run first:
 
@@ -114,6 +114,10 @@ If `--version` reports "command not found" after install, the npm global bin dir
 
 - `realtimex-pp-cli list-plugins` — List installed plugins with enabled state and runtime load status.
 
+**list-terminal-sessions** — Manage list terminal sessions
+
+- `realtimex-pp-cli list-terminal-sessions` — List terminal runtime sessions known to the desktop app. Optionally filter by workspaceSlug and threadSlug.
+
 **list-threads** — Manage list threads
 
 - `realtimex-pp-cli list-threads <workspaceSlug>` — List threads for one exact workspace slug.
@@ -146,6 +150,14 @@ If `--version` reports "command not found" after install, the npm global bin dir
 
 - `realtimex-pp-cli rename-workspace <workspaceSlug>` — Rename one workspace by exact workspace slug. Only the name is changed.
 
+**resume-latest-terminal-session** — Manage resume latest terminal session
+
+- `realtimex-pp-cli resume-latest-terminal-session` — Resume the latest terminal runtime session for one exact thread.
+
+**resume-terminal-session** — Manage resume terminal session
+
+- `realtimex-pp-cli resume-terminal-session <sessionId>` — Resume a terminal runtime session by attaching a CLI controller.
+
 **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.
@@ -194,6 +206,10 @@ If `--version` reports "command not found" after install, the npm global bin dir
 
 - `realtimex-pp-cli stop-channel <channelId>` — Stop one chat channel by exact channel id.
 
+**terminate-terminal-session** — Manage terminate terminal session
+
+- `realtimex-pp-cli terminate-terminal-session <sessionId>` — Terminate a terminal runtime session by detaching any controller and closing the underlying PTY session.
+
 **update-channel** — Manage update channel
 
 - `realtimex-pp-cli update-channel <channelId>` — Update one chat channel by exact channel id. Only channel writable fields are changed.
@@ -324,9 +340,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.9`, reinstall the pinned version:
+   If the command is missing or the output is not exactly `realtimex-pp-cli 2.0.10`, reinstall the pinned version:
    ```bash
-   npm install -g @realtimex/pp-cli@2.0.9
+   npm install -g @realtimex/pp-cli@2.0.10
    ```
    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.
@@ -344,6 +360,15 @@ This skill intentionally exposes a small action-first command set. Prefer these
 * Never call the RealTimeX API directly with `curl`, `fetch`, raw HTTP clients, or custom scripts.
 * If the current CLI cannot do the requested task, say the feature is not available and will be added soon.
 * Use `--agent` on every command.
+* Treat `$RTX_WORKSPACE_SLUG` as the current workspace slug when it is set, and `$RTX_THREAD_SLUG` as the current thread slug when it is set.
+* For requests that refer to "current workspace", "this workspace", "current thread", or "this thread", use those environment values directly when they are available.
+* When you need the resolved current workspace/thread objects or related context, call:
+
+  ```bash
+  realtimex-pp-cli prepare --workspace-slug "$RTX_WORKSPACE_SLUG" --thread-slug "$RTX_THREAD_SLUG" --agent
+  ```
+
+* If `$RTX_WORKSPACE_SLUG` or `$RTX_THREAD_SLUG` is missing for a current-context request that requires it, ask for the missing workspace or thread before running the command.
 * Always run first:
 
   ```bash