chore(sync): mirror docs from openclaw/openclaw@de0d484236

.openclaw-sync/source.json

@@ -1,5 +1,5 @@
 {
   "repository": "openclaw/openclaw",
-  "sha": "63c9fbcfa3da770a0f8c41c0d1359a8442317cd5",
-  "syncedAt": "2026-05-02T05:22:33.283Z"
+  "sha": "de0d484236fc52cbcb8142386db04824fe934bfc",
+  "syncedAt": "2026-05-02T05:32:08.276Z"
 }

docs/cli/sessions.md

@@ -85,7 +85,7 @@ openclaw sessions cleanup --json
   - In text mode, dry-run prints a per-session action table (`Action`, `Key`, `Age`, `Model`, `Flags`) so you can see what would be kept vs removed.
 - `--enforce`: apply maintenance even when `session.maintenance.mode` is `warn`.
 - `--fix-missing`: remove entries whose transcript files are missing, even if they would not normally age/count out yet.
-- `--active-key <key>`: protect a specific active key from disk-budget eviction.
+- `--active-key <key>`: protect a specific active key from disk-budget eviction. Durable external conversation pointers, such as group sessions and thread-scoped chat sessions, are also kept by age/count/disk-budget maintenance.
 - `--agent <id>`: run cleanup for one configured agent store.
 - `--all-agents`: run cleanup for all configured agent stores.
 - `--store <path>`: run against a specific `sessions.json` file.

docs/concepts/session.md

@@ -127,6 +127,10 @@ to `"enforce"` for automatic cleanup:
 
 For production-sized `maxEntries` limits, Gateway runtime writes use a small high-water buffer and clean back down to the configured cap in batches. Session store reads do not prune or cap entries during Gateway startup. This avoids running full store cleanup on every startup or isolated cron session. `openclaw sessions cleanup --enforce` applies the cap immediately.
 
+Maintenance preserves durable external conversation pointers, including group
+sessions and thread-scoped chat sessions, while still allowing synthetic cron,
+hook, heartbeat, ACP, and sub-agent entries to age out.
+
 Preview with `openclaw sessions cleanup --dry-run`.
 
 ## Inspecting sessions

docs/reference/session-management-compaction.md

@@ -81,6 +81,11 @@ Session persistence has automatic maintenance controls (`session.maintenance`) f
 
 Normal Gateway writes batch `maxEntries` cleanup for production-sized caps, so a store may briefly exceed the configured cap before the next high-water cleanup rewrites it back down. Session store reads do not prune or cap entries during Gateway startup; use writes or `openclaw sessions cleanup --enforce` for cleanup. `openclaw sessions cleanup --enforce` still applies the configured cap immediately.
 
+Maintenance keeps durable external conversation pointers such as group sessions
+and thread-scoped chat sessions, but synthetic runtime entries for cron, hooks,
+heartbeat, ACP, and sub-agents can still be removed when they exceed the
+configured age, count, or disk budget.
+
 OpenClaw no longer creates automatic `sessions.json.bak.*` rotation backups during Gateway writes. The legacy `session.maintenance.rotateBytes` key is ignored and `openclaw doctor --fix` removes it from older configs.
 
 Enforcement order for disk budget cleanup (`mode: "enforce"`):