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

.openclaw-sync/source.json

@@ -1,5 +1,5 @@
 {
   "repository": "openclaw/openclaw",
-  "sha": "a102f4dede6af52523473ac29575c7e442493d15",
-  "syncedAt": "2026-05-01T00:36:55.572Z"
+  "sha": "b277ae3f4c402596402cb8be5be4dca2106483f4",
+  "syncedAt": "2026-05-01T01:15:16.131Z"
 }

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

@@ -1,2 +1,2 @@
-851a39b442a4a15e78d27d8a3e1ee66ff61a061356d412051e205f6c07f54c34  plugin-sdk-api-baseline.json
-d3106b731a3a13f7dddaa0b1916f223c1757fa8d1df3476914f70502c9532c2f  plugin-sdk-api-baseline.jsonl
+e75701dd791461feb4893e7106362dbbb41668bc4341e8b42becc346001e9f0e  plugin-sdk-api-baseline.json
+077e30997781d3a064f00491d55f7ac78465868b02fdcfb70e07e03555bb2afe  plugin-sdk-api-baseline.jsonl

docs/concepts/commitments.md

@@ -60,11 +60,15 @@ When it finds a high-confidence candidate, OpenClaw stores a commitment with:
 - the original channel and delivery target
 - a due window
 - a short suggested check-in
-- enough source context for heartbeat to decide whether to send it
+- non-instructional metadata for heartbeat to decide whether to send it
 
 Delivery happens through heartbeat. When a commitment becomes due, heartbeat
 adds the commitment to the heartbeat turn for the same agent and channel scope.
 The model can send one natural check-in or reply `HEARTBEAT_OK` to dismiss it.
+If heartbeat is configured with `target: "none"`, due commitments remain
+internal and do not send external check-ins. Commitment delivery prompts do not
+replay the original conversation text, and due commitment heartbeat turns run
+without OpenClaw tools.
 
 OpenClaw never delivers an inferred commitment immediately after writing it.
 The due time is clamped to at least one heartbeat interval after the commitment