Auto-merge upstream openclaw/openclaw

Author: friuns2

.agents/skills/openclaw-parallels-smoke/SKILL.md

@@ -50,6 +50,7 @@ Use this skill for Parallels guest workflows and smoke interpretation. Do not lo
 - Because the default upgrade lane no longer needs a host tgz, skip `npm pack` + host HTTP server startup for `--mode upgrade` unless `--target-package-spec` is set. Keep the pack/server path for `fresh` and `both`.
 - If that release-to-dev lane fails with `reason=preflight-no-good-commit` and repeated `sh: pnpm: command not found` tails from `preflight build`, treat it as an updater regression first. The fix belongs in the git/dev updater bootstrap path, not in Parallels retry logic.
 - Until the public stable train includes that updater bootstrap fix, the macOS release-to-dev lane may seed a temporary guest-local `pnpm` shim immediately before `openclaw update --channel dev`. Keep that workaround scoped to the smoke harness and remove it once the latest stable no longer needs it.
+- After the package -> git switch, prefer post-update verification through explicit `node ~/openclaw/openclaw.mjs ...` calls. In Tahoe `prlctl exec --current-user` runs, the shebanged global `openclaw` wrapper can fail with `env: node: No such file or directory` even though the dev switch already succeeded.
 - Default to the snapshot closest to `macOS 26.3.1 latest`.
 - On Peter's Tahoe VM, `fresh-latest-march-2026` can hang in `prlctl snapshot-switch`; if restore times out there, rerun with `--snapshot-hint 'macOS 26.3.1 latest'` before blaming auth or the harness.
 - `parallels-macos-smoke.sh` now retries `snapshot-switch` once after force-stopping a stuck running/suspended guest. If Tahoe still times out after that recovery path, then treat it as a real Parallels/host issue and rerun manually.

CHANGELOG.md

@@ -1030,6 +1030,29 @@
         }
       }
     },
+    "music_generate": {
+      "emoji": "🎵",
+      "title": "Music Generation",
+      "actions": {
+        "generate": {
+          "label": "generate",
+          "detailKeys": [
+            "prompt",
+            "model",
+            "durationSeconds",
+            "format",
+            "instrumental"
+          ]
+        },
+        "list": {
+          "label": "list",
+          "detailKeys": [
+            "provider",
+            "model"
+          ]
+        }
+      }
+    },
     "video_generate": {
       "emoji": "🎬",
       "title": "Video Generation",

apps/shared/OpenClawKit/Sources/OpenClawKit/Resources/tool-display.json

@@ -1,4 +1,4 @@
-57a3b1cc7d573c3788a670d927eac947fb1685384804f5c3c926f702a27fe00b  config-baseline.json
-82163136ff466db3caa61290fd65a8b8dd9487fc61f3871c177f96fcecf9e29b  config-baseline.core.json
-ae67508350baf891b902348d55fada6c17e9c053adf53aaf3a8b92cd364ef3f1  config-baseline.channel.json
-d972a11d0f86080a722bddfe48990dd1b8fa16eb8e157e83f49bd46a5941c512  config-baseline.plugin.json
+fb2c88ef41657f1aa7237dcce655d16313dc849fd03991b221346367c569a482  config-baseline.json
+ff8f64e1866748644776b229bdf334762875e3139b717a3adb8e5c587286ada3  config-baseline.core.json
+ba5f7e89aad95d3eae0bc4e3b590c8dbb87bd921bba0d8f12fe67545af5887c6  config-baseline.channel.json
+dc19ac1c60544d87fe08944d1184e0ade7b469367cdf8d6ce61452f64f9e0a47  config-baseline.plugin.json

docs/.generated/config-baseline.sha256

@@ -1,2 +1,2 @@
-97509287d728c8f5d1736f7ea07521451ada4b9d7ef56555dbe860a89e1b6e08  plugin-sdk-api-baseline.json
-a22b3d427953cc8394b28c87ef7a992d2eb4f2c9f6a76fa58b33079e2306661b  plugin-sdk-api-baseline.jsonl
+4e024092a28987e1a826b0c731e9ee5adb9d28e73b5cac51ca055c46d9067258  plugin-sdk-api-baseline.json
+9e3279a3e78e24b72952ab0f1707dcf465f8c283acf568f043e9b232fd0ae5dd  plugin-sdk-api-baseline.jsonl

docs/.generated/plugin-sdk-api-baseline.sha256

@@ -103,6 +103,7 @@ Password-based setup (token is cached after login):
 
 Matrix stores cached credentials in `~/.openclaw/credentials/matrix/`.
 The default account uses `credentials.json`; named accounts use `credentials-<account>.json`.
+When cached credentials exist there, OpenClaw treats Matrix as configured for setup, doctor, and channel-status discovery even if current auth is not set directly in config.
 
 Environment variable equivalents (used when the config key is not set):
 
@@ -280,7 +281,7 @@ OpenClaw marks finalized text-only preview edits with:
 
 ```bash
 curl -sS -X PUT \
-  "https://matrix.example.org/_matrix/client/v3/pushrules/global/override/openclaw-finalized-preview" \
+  "https://matrix.example.org/_matrix/client/v3/pushrules/global/override/openclaw-finalized-preview-botname" \
   -H "Authorization: Bearer $USER_ACCESS_TOKEN" \
   -H "Content-Type: application/json" \
   --data '{
@@ -310,8 +311,15 @@ Replace these values before you run the command:
 
 - `https://matrix.example.org`: your homeserver base URL
 - `$USER_ACCESS_TOKEN`: the receiving user's access token
+- `openclaw-finalized-preview-botname`: a rule ID unique to this bot for this receiving user
 - `@bot:example.org`: your OpenClaw Matrix bot MXID, not the receiving user's MXID
 
+Important for multi-bot setups:
+
+- Push rules are keyed by `ruleId`. Re-running `PUT` against the same rule ID updates that one rule.
+- If one receiving user should notify for multiple OpenClaw Matrix bot accounts, create one rule per bot with a unique rule ID for each sender match.
+- A simple pattern is `openclaw-finalized-preview-<botname>`, such as `openclaw-finalized-preview-ops` or `openclaw-finalized-preview-support`.
+
 The rule is evaluated against the event sender:
 
 - authenticate with the receiving user's token
@@ -322,12 +330,20 @@ The rule is evaluated against the event sender:
 ```bash
 curl -sS \
   -H "Authorization: Bearer $USER_ACCESS_TOKEN" \
-  "https://matrix.example.org/_matrix/client/v3/pushrules/global/override/openclaw-finalized-preview"
+  "https://matrix.example.org/_matrix/client/v3/pushrules/global/override/openclaw-finalized-preview-botname"
 ```
 
 7. Test a streamed reply. In quiet mode, the room should show a quiet draft preview and the final
    in-place edit should notify once the block or turn finishes.
 
+If you need to remove the rule later, delete that same rule ID with the receiving user's token:
+
+```bash
+curl -sS -X DELETE \
+  -H "Authorization: Bearer $USER_ACCESS_TOKEN" \
+  "https://matrix.example.org/_matrix/client/v3/pushrules/global/override/openclaw-finalized-preview-botname"
+```
+
 Notes:
 
 - Create the rule with the receiving user's access token, not the bot's.

docs/channels/matrix.md

@@ -34,8 +34,6 @@ openclaw memory status --deep --index
 openclaw memory status --deep --index --verbose
 openclaw memory status --agent main
 openclaw memory index --agent main --verbose
-openclaw memory promote-explain "router vlan"
-openclaw memory rem-harness --json
 ```
 
 ## Options
@@ -80,9 +78,9 @@ openclaw memory promote [--apply] [--limit <n>] [--include-promoted]
 
 Full options:
 
-- Ranks short-term candidates from `memory/YYYY-MM-DD.md` using weighted recall signals (`frequency`, `relevance`, `query diversity`, `recency`).
-- Uses recall events captured when `memory_search` returns daily-memory hits.
-- When dreaming is enabled, `memory-core` auto-manages a cron job for the deep phase that triggers promotion in the background (no manual `openclaw cron add` required).
+- Ranks short-term candidates from `memory/YYYY-MM-DD.md` using weighted promotion signals (`frequency`, `relevance`, `query diversity`, `recency`, `consolidation`, `conceptual richness`).
+- Uses short-term signals from both memory recalls and daily-ingestion passes, plus light/REM phase reinforcement signals.
+- When dreaming is enabled, `memory-core` auto-manages one cron job that runs a full sweep (`light -> REM -> deep`) in the background (no manual `openclaw cron add` required).
 - `--agent <id>`: scope to a single agent (default: the default agent).
 - `--limit <n>`: max candidates to return/apply.
 - `--min-score <n>`: minimum weighted promotion score.
@@ -92,54 +90,26 @@ Full options:
 - `--include-promoted`: include already promoted candidates in output.
 - `--json`: print JSON output.
 
-`memory promote-explain`:
-
-Explain why a specific candidate would or would not promote, with a full score breakdown.
-
-```bash
-openclaw memory promote-explain "<selector>"
-```
-
-- `<selector>`: candidate key, path fragment, or snippet fragment to match.
-- `--agent <id>`: scope to a single agent (default: the default agent).
-- `--include-promoted`: include already promoted candidates.
-- `--json`: print JSON output.
-
-`memory rem-harness`:
-
-Preview REM reflections, candidate truths, and deep promotion output without writing anything. Useful for staging and debugging the REM phase before it runs for real.
-
-```bash
-openclaw memory rem-harness [--json] [--agent <id>] [--include-promoted]
-```
-
-- `--agent <id>`: scope to a single agent (default: the default agent).
-- `--include-promoted`: include already promoted deep candidates.
-- `--json`: print JSON output.
-
-See [Dreaming](/concepts/dreaming) for the full phase model and how REM fits in.
-
 ## Dreaming (experimental)
 
 Dreaming is the background memory consolidation system with three cooperative
-phases: **light** (organize into `DREAMS.md` in inline mode), **deep**
-(promote into `MEMORY.md`), and **REM** (reflect and find patterns in
-`DREAMS.md` in inline mode).
+phases: **light** (sort/stage short-term material), **deep** (promote durable
+facts into `MEMORY.md`), and **REM** (reflect and surface themes).
 
 - Enable with `plugins.entries.memory-core.config.dreaming.enabled: true`.
-- Toggle from chat with `/dreaming on|off` or `/dreaming enable|disable light|deep|rem`.
-- Each phase runs on its own cron schedule, managed automatically by `memory-core`.
-- Only the deep phase writes durable memory to `MEMORY.md`. With default inline storage, Light and REM write to `DREAMS.md`.
+- Toggle from chat with `/dreaming on|off` (or inspect with `/dreaming status`).
+- Dreaming runs on one managed sweep schedule (`dreaming.frequency`) and executes phases in order: light, REM, deep.
+- Only the deep phase writes durable memory to `MEMORY.md`.
+- Human-readable phase output and diary entries are written to `DREAMS.md` (or existing `dreams.md`), with optional per-phase reports in `memory/dreaming/<phase>/YYYY-MM-DD.md`.
 - Ranking uses weighted signals: recall frequency, retrieval relevance, query diversity, temporal recency, cross-day consolidation, and derived concept richness.
 - Promotion re-reads the live daily note before writing to `MEMORY.md`, so edited or deleted short-term snippets do not get promoted from stale recall-store snapshots.
 - Scheduled and manual `memory promote` runs share the same deep phase defaults unless you pass CLI threshold overrides.
 - Automatic runs fan out across configured memory workspaces.
 
-Default phase schedules:
+Default scheduling:
 
-- **Light**: every 6 hours (`0 */6 * * *`), `lookbackDays=2`, `limit=100`
-- **Deep**: daily at 3 AM (`0 3 * * *`), `limit=10`, `minScore=0.8`, `minRecallCount=3`, `minUniqueQueries=3`, `recencyHalfLifeDays=14`
-- **REM**: weekly, Sunday 5 AM (`0 5 * * 0`), `lookbackDays=7`, `limit=10`
+- **Sweep cadence**: `dreaming.frequency = 0 3 * * *`
+- **Deep thresholds**: `minScore=0.8`, `minRecallCount=3`, `minUniqueQueries=3`, `recencyHalfLifeDays=14`, `maxAgeDays=30`
 
 Example:
 
@@ -165,6 +135,5 @@ Notes:
 - `memory status` includes any extra paths configured via `memorySearch.extraPaths`.
 - If effectively active memory remote API key fields are configured as SecretRefs, the command resolves those values from the active gateway snapshot. If gateway is unavailable, the command fails fast.
 - Gateway version skew note: this command path requires a gateway that supports `secrets.resolve`; older gateways return an unknown-method error.
-- Override each phase schedule with `phases.<phase>.cron` and fine-tune deep promotion with `phases.deep.minScore`, `phases.deep.minRecallCount`, `phases.deep.minUniqueQueries`, `phases.deep.recencyHalfLifeDays`, and `phases.deep.maxAgeDays`.
-- Set `plugins.entries.memory-core.config.dreaming.verboseLogging` to `true` to emit per-run candidate and apply details into the normal gateway logs while tuning the feature.
+- Tune scheduled sweep cadence with `dreaming.frequency`. Deep promotion policy is otherwise internal; use CLI flags on `memory promote` when you need one-off manual overrides.
 - See [Dreaming](/concepts/dreaming) for full phase descriptions and configuration reference.

docs/cli/memory.md

@@ -96,11 +96,13 @@ High-level:
 3. Fetches upstream (dev only).
 4. Dev only: preflight lint + TypeScript build in a temp worktree; if the tip fails, walks back up to 10 commits to find the newest clean build.
 5. Rebases onto the selected commit (dev only).
-6. Installs deps (pnpm preferred; npm fallback; bun remains available as a secondary compatibility fallback).
+6. Installs deps with the repo package manager. For pnpm checkouts, the updater bootstraps `pnpm` on demand (via `corepack` first, then a temporary `npm install pnpm@10` fallback) instead of running `npm run build` inside a pnpm workspace.
 7. Builds + builds the Control UI.
 8. Runs `openclaw doctor` as the final “safe update” check.
 9. Syncs plugins to the active channel (dev uses bundled extensions; stable/beta uses npm) and updates npm-installed plugins.
 
+If pnpm bootstrap still fails, the updater now stops early with a package-manager-specific error instead of trying `npm run build` inside the checkout.
+
 ## `--update` shorthand
 
 `openclaw --update` rewrites to `openclaw update` (useful for shells and launcher scripts).