Fix version attribution and align config-path snippets per review

- recall.maxParallel + dreaming schedule controls are 2026.6.11-beta.1, not 2026.6.4 stable
- field-guide memory/meetingNotes snippets now use plugins.entries.* path matching example config

Co-Authored-By: Rob <onerobby@gmail.com>

Author: devin-ai-integration[bot]

AWESOME.md

@@ -70,7 +70,7 @@ See [Part 23 — ClawHub Skills Marketplace](./part23-clawhub-skills-marketplace
 - **[memory-lancedb](https://github.com/openclaw/memory-lancedb)** — LanceDB vector store. 2026.4.15-beta.1 added cloud storage mode.
 - **Active Memory filters** — current builds support per-conversation `allowedChatIds` / `deniedChatIds`, partial recall on timeout, and people-aware wiki provenance views.
 - **Meeting Notes plugin** — 2026.5.22 source-only external plugin for date-sharded meeting transcripts, manual imports, CLI reads, and Discord voice as the first live source. 2026.6.4 adds Google Meet live capture plus `meetingNotes.retentionDays`/redaction. Define retention before enabling.
-- **Recall + dreaming tuning** — 2026.6.4 exposes `memory.recall.maxParallel`, scheduled dreaming (`memory.dreaming.schedule`), and `memory promote --dry-run` so consolidation runs off-hours and promotions are reviewable.
+- **Recall + dreaming tuning** — 2026.6.4 ships `memory promote --dry-run` (review what dreaming would promote before it mutates); 2026.6.11-beta.1 adds `memory.recall.maxParallel` and scheduled dreaming (`memory.dreaming.schedule`) so consolidation runs off-hours.
 - **Generic embedding provider contract** — 2026.5.22 plugin SDK surface (`contracts.embeddingProviders`, `api.registerEmbeddingProvider`) that should make explicit OpenAI-compatible embedding providers cleaner.
 - **[Ollama](https://ollama.com/)** — local embedding runtime. `qwen3-embedding:0.6b` is the right default for most setups.
 - **[LightRAG](https://github.com/HKUDS/LightRAG)** — graph + vector hybrid RAG. The right upgrade once your vault crosses ~500 files. See [Part 18](./part18-lightrag-graph-rag.md).

part26-migration-guide.md

@@ -311,7 +311,7 @@ This is the current stable baseline for this guide. It promotes the 5.24 beta li
 - `openclaw policy check --export attestation.json` produces diffable attestations; drift against the last accepted attestation is now a reviewable change.
 - `models.providers.<id>.health` adds interval probes with bounded automatic lane demotion (`failureThreshold`, `demoteForMs`).
 - Meeting Notes gains Google Meet live capture plus `meetingNotes.retentionDays` and redaction rules.
-- `memory.recall.maxParallel`, scheduled dreaming (`memory.dreaming.schedule`), and `memory promote --dry-run` make memory behavior explicit.
+- `memory promote --dry-run` lets you preview what dreaming would promote into `MEMORY.md` before it mutates anything. (`memory.recall.maxParallel` and additional dreaming schedule controls are 2026.6.11-beta.1, not 2026.6.4 stable — see step 7.)
 - `openclaw doctor` adds secret-rotation reminders (`secrets.rotation.maxAgeDays`) and flags unscoped `mcp.servers.<id>.codex.agents`.
 
 **Steps:**
@@ -322,7 +322,7 @@ This is the current stable baseline for this guide. It promotes the 5.24 beta li
 4. Schedule `openclaw policy check --export` (cron or CI) and store the first attestation as your baseline. Keep `--fix` manual.
 5. If you use Meeting Notes, set `retentionDays` and redaction rules before enabling the Google Meet source.
 6. Resolve any new doctor findings for plaintext/stale secrets and unscoped Codex MCP servers.
-7. Optionally test 2026.6.11-beta.1 on a copied profile for `/context map --diff`, sandbox egress allowlists, and per-channel image-quality overrides.
+7. Optionally test 2026.6.11-beta.1 on a copied profile for `/context map --diff`, `memory.recall.maxParallel`, dreaming schedule controls, sandbox egress allowlists, and per-channel image-quality overrides.
 
 ## Rollback Plan (Every Path)
 

part33-late-april-2026-field-guide.md

@@ -257,16 +257,22 @@ The late-May voice work is not just "talk to the bot":
 - Meeting Notes is now a source-only external plugin with auto-start capture config, manual transcript imports, read-only `openclaw meeting-notes` CLI access, and Discord voice as the first live source.
 - 2026.6.4 adds **Google Meet live capture as a second source** plus explicit `meetingNotes.retentionDays` and redaction-rule config, so transcripts can expire and scrub sensitive fields instead of living forever.
 
-Retention config shape:
+Retention config shape (under the `meeting-notes` plugin config):
 
 ```json5
 {
-  meetingNotes: {
-    retentionDays: 30,
-    redact: ["email", "phone", "api-key"],
-    sources: {
-      discordVoice: { autoStart: false },
-      googleMeet: { autoStart: false }
+  plugins: {
+    entries: {
+      "meeting-notes": {
+        config: {
+          retentionDays: 30,
+          redact: ["email", "phone", "api-key"],
+          sources: {
+            discordVoice: { autoStart: false },
+            googleMeet: { autoStart: false }
+          }
+        }
+      }
     }
   }
 }
@@ -443,17 +449,25 @@ Operator rule: every production agent should have at least two non-Anthropic lan
 
 ## 17. Tune Recall Parallelism And Dreaming Schedules
 
-Two memory levers landed for long-running agents:
+Three memory levers landed for long-running agents:
+
+- `memory promote --dry-run` (**2026.6.4 stable**) shows what the Deep phase *would* promote into `MEMORY.md` before it mutates anything — use it when you suspect dreaming is promoting noise.
+- `memory.recall.maxParallel` (**2026.6.11-beta.1**) bounds how many memory sub-agents run concurrently. Raise it on a fast local embedding tier for snappier recall; lower it on shared hardware to stop recall from starving foreground turns.
+- Dreaming schedule controls (**2026.6.11-beta.1**) refine when consolidation runs (building on the existing `dreaming.schedule` key), so it lands in a predictable off-hours window rather than mid-conversation.
 
-- `memory.recall.maxParallel` bounds how many memory sub-agents run concurrently. Raise it on a fast local embedding tier for snappier recall; lower it on shared hardware to stop recall from starving foreground turns.
-- Dreaming now takes an explicit schedule instead of only firing on idle, so consolidation runs in a predictable window rather than mid-conversation.
-- `memory promote --dry-run` shows what the Deep phase *would* promote into `MEMORY.md` before it mutates anything — use it when you suspect dreaming is promoting noise.
+The recall/schedule keys live under the `memory-core` plugin config, alongside the dreaming block (see [templates/openclaw.example.json](./templates/openclaw.example.json)):
 
 ```json5
 {
-  memory: {
-    recall: { maxParallel: 3 },
-    dreaming: { schedule: "0 3 * * *" }
+  plugins: {
+    entries: {
+      "memory-core": {
+        config: {
+          recall: { maxParallel: 3 },
+          dreaming: { schedule: "0 3 * * *" }
+        }
+      }
+    }
   }
 }
 ```

templates/openclaw.example.json

@@ -64,12 +64,12 @@
         "config": {
           "recall": {
             "maxParallel": 3,
-            "_comment": "2026.6.4+: bound concurrent memory sub-agents. Raise on a fast local embedding tier; lower on shared hardware so recall doesn't starve foreground turns."
+            "_comment": "2026.6.11-beta.1+: bound concurrent memory sub-agents. Raise on a fast local embedding tier; lower on shared hardware so recall doesn't starve foreground turns. Not available on 2026.6.4 stable yet."
           },
           "dreaming": {
             "enabled": true,
             "schedule": "0 3 * * *",
-            "_schedule_comment": "2026.6.4+: explicit off-hours schedule instead of idle-only. Verify promotions with `memory promote --dry-run` before trusting them.",
+            "_schedule_comment": "Off-hours dreaming schedule (cron). 2026.6.11-beta.1 adds finer schedule controls. Verify promotions with `memory promote --dry-run` (2026.6.4+) before trusting them.",
             "storage": {
               "mode": "separate",
               "_comment": "Current default. Phase blocks land in memory/dreaming/{phase}/YYYY-MM-DD.md. Flip to `inline` if you want them in the daily memory file."