chore(sync): mirror docs from openclaw/openclaw@04e774eeac

.openclaw-sync/source.json

@@ -1,5 +1,5 @@
 {
   "repository": "openclaw/openclaw",
-  "sha": "47b6d3a334a12d1759200186e4ade7f984f2e319",
-  "syncedAt": "2026-04-28T07:44:22.103Z"
+  "sha": "04e774eeacb36350564f9838e4b5f5d15bb3f1a1",
+  "syncedAt": "2026-04-28T07:56:15.644Z"
 }

docs/platforms/android.md

@@ -107,6 +107,17 @@ After the first successful pairing, Android auto-reconnects on launch:
 - Manual endpoint (if enabled), otherwise
 - The last discovered gateway (best-effort).
 
+### Presence alive beacons
+
+After the authenticated node session connects, and when the app moves to the background while the
+foreground service is still connected, Android calls `node.event` with
+`event: "node.presence.alive"`. The gateway records this as `lastSeenAtMs`/`lastSeenReason` on the
+paired node/device metadata only after the authenticated node device identity is known.
+
+The app counts the beacon as successfully recorded only when the gateway response includes
+`handled: true`. Older gateways may acknowledge `node.event` with `{ "ok": true }`; that response is
+compatible but does not count as a durable last-seen update.
+
 ### 4) Approve pairing (CLI)
 
 On the gateway machine: