From 57f05128cba9c3cf2e8b0cb52a54ae7daa7a8608 Mon Sep 17 00:00:00 2001 From: Peter Steinberger Date: Sun, 26 Apr 2026 01:49:06 +0100 Subject: [PATCH] docs: clarify Crestodian rescue audit metadata --- docs/cli/crestodian.md | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/docs/cli/crestodian.md b/docs/cli/crestodian.md index 350b0f018b7..f0a2692614a 100644 --- a/docs/cli/crestodian.md +++ b/docs/cli/crestodian.md @@ -239,13 +239,13 @@ Security contract for remote rescue: operation, where the runtime already has unsandboxed local authority. - Require an explicit owner identity. Rescue must not accept wildcard sender rules, open group policy, unauthenticated webhooks, or anonymous channels. -- Owner DMs only by default. Group/channel rescue requires explicit opt-in and - should still route approval prompts to the owner DM. +- Owner DMs only by default. Group/channel rescue requires explicit opt-in. - Remote rescue cannot open the local TUI or switch into an interactive agent session. Use local `openclaw` for agent handoff. - Persistent writes still require approval, even in rescue mode. -- Audit every applied rescue operation, including channel, account, sender, - session key, operation, config hash before, and config hash after. +- Audit every applied rescue operation. Message-channel rescue records channel, + account, sender, and source-address metadata. Config-mutating operations also + record config hashes before and after. - Never echo secrets. SecretRef inspection should report availability, not values. - If the Gateway is alive, prefer Gateway typed operations. If the Gateway is