@realtimex/sdk 2.0.11 → 2.0.13

package/package.json

@@ -1,6 +1,6 @@
 {
     "name": "@realtimex/sdk",
-    "version": "2.0.11",
+    "version": "2.0.13",
     "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.11
+   npm install -g @realtimex/pp-cli@2.0.13
    ```
 2. Verify the exact version:
    ```bash
    realtimex-pp-cli --version
    ```
-   The output must be `realtimex-pp-cli 2.0.11`.
+   The output must be `realtimex-pp-cli 2.0.13`.
 
-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.11`, 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.13`, reinstall with the pinned npm command above. Do not proceed with skill commands until exact-version verification succeeds.
 
 * Always run first:
 
@@ -180,7 +180,7 @@ If `--version` reports "command not found" after install, the npm global bin dir
 
 **set-heartbeat-default-agent** — Manage set heartbeat default agent
 
-- `realtimex-pp-cli set-heartbeat-default-agent` — Set workspace or global ambient-agent main executor default terminal agent and optional model.
+- `realtimex-pp-cli set-heartbeat-default-agent` — Set workspace or global ambient-agent default terminal agent and optional model for heartbeat defaults and legacy
 
 **set-heartbeat-enabled** — Manage set heartbeat enabled
 
@@ -188,7 +188,7 @@ If `--version` reports "command not found" after install, the npm global bin dir
 
 **set-heartbeat-interval** — Manage set heartbeat interval
 
-- `realtimex-pp-cli set-heartbeat-interval` — Set workspace or global ambient-agent main executor interval.
+- `realtimex-pp-cli set-heartbeat-interval` — Set workspace or global ambient-agent scheduler check interval.
 
 **set-heartbeat-timezone** — Manage set heartbeat timezone
 
@@ -218,6 +218,14 @@ If `--version` reports "command not found" after install, the npm global bin dir
 
 - `realtimex-pp-cli terminate-terminal-session <sessionId>` — Terminate a terminal runtime session by detaching any controller and closing the underlying PTY session.
 
+**trigger-workspace-heartbeat** — Manage trigger workspace heartbeat
+
+- `realtimex-pp-cli trigger-workspace-heartbeat <workspaceSlug>` — Trigger the default HEARTBEAT.md task for a workspace immediately.
+
+**trigger-workspace-heartbeat-tasks** — Manage trigger workspace heartbeat tasks
+
+- `realtimex-pp-cli trigger-workspace-heartbeat-tasks <workspaceSlug>` — Trigger specified HEARTBEAT.md task names for a workspace immediately.
+
 **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.
@@ -348,9 +356,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.11`, reinstall the pinned version:
+   If the command is missing or the output is not exactly `realtimex-pp-cli 2.0.13`, reinstall the pinned version:
    ```bash
-   npm install -g @realtimex/pp-cli@2.0.11
+   npm install -g @realtimex/pp-cli@2.0.13
    ```
    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.

package/skills/realtimex-moderator-sdk/templates/HEARTBEAT.template.md

@@ -4,31 +4,69 @@
 
 Describe the ambient agent's standing responsibility.
 
-## Scheduled tasks (optional)
+## Tasks
 
-Remove this section if you don't need recurring tasks.
-When present, the scheduler runs only tasks that are due on each tick.
-Tasks without an interval inherit the main check interval.
+The scheduler evaluates this `tasks:` block on every heartbeat tick and runs only tasks that are due.
+The first task is treated as the default task unless another task has `default: true`.
+Use `default: true` on exactly one task to make it the default manual heartbeat target.
+Use `default: false` on the first task if you do not want any task to be auto-selected as default.
 Use `interval` for simple timing. Supported units are `m`, `h`, and `d`, for example `3m`, `1h`, or `1d`.
+Omit `interval` and `cron` to run on every scheduler check interval.
+Use `interval: disabled` to keep a task in the file but skip it during scheduled heartbeat checks. Manual triggers can still run the task.
 Use `cron` for complex schedules, for example `0 9 * * *`.
-Use `agent` to run a task with a specific terminal agent, for example `@codex-terminal`.
-Use `model` to run a task with a specific model, for example `gpt-5.5-medium`.
-Use `skills` to prefer skills for the task, for example `agent-browser, realtimex-moderator-sdk`.
-`agent`, `model`, `skills`, `interval`, and `cron` are optional. If omitted, the task inherits from the main heartbeat executor.
+Agent tasks require `agent`, for example `@codex-terminal`.
+Use `model` to run an agent task with a specific model, for example `gpt-5.5-medium`.
+Use `skills` to prefer skills for an agent task, for example `agent-browser, realtimex-moderator-sdk`.
+Use `executor: shell` and `command` to run a shell command instead of an agent. Shell tasks do not use `prompt`.
+When a shell command prints valid JSON, it can trigger additional tasks. Use one of these forms:
+
+```json
+["task-name-1", "task-name-2"]
+```
+
+```json
+{
+  "tasks": ["task-name-1", "task-name-2"],
+  "reason": "metrics changed"
+}
+```
+
+To trigger tasks in another workspace, include `workspace`:
+
+```json
+{
+  "workspace": "other-workspace-slug",
+  "tasks": ["task-name-1"],
+  "reason": "shared dependency changed"
+}
+```
+
+Only valid JSON triggers task dispatch. If the shell output is not valid JSON, no extra tasks are run.
 
 tasks:
 
-- name: example-task
+- name: default-review
+  default: true
   interval: 30m
   agent: @codex-terminal
   model: gpt-5.5-medium
   skills: agent-browser, realtimex-moderator-sdk
-  prompt: Describe what the agent should do for this task
+  prompt: Review the workspace context and respond HEARTBEAT_OK when no action is needed
 - name: weekday-morning-task
   cron: 0 9 * * 1-5
+  agent: @codex-terminal
   prompt: Describe what should run on a cron schedule
+- name: sync-metrics
+  interval: 30m
+  executor: shell
+  command: bash ./scripts/sync-metrics.sh
+- name: paused-task
+  interval: disabled
+  agent: @codex-terminal
+  prompt: This task is skipped by scheduled heartbeat checks until re-enabled
 - name: another-task
-  prompt: Tasks without interval run at the main check interval
+  agent: @codex-terminal
+  prompt: Tasks without interval or cron run on every scheduler check interval
 
 ## Check for