WoL Wakeup

Before installing, review and harden the deployment: 1) Search the repo/docs for any hard-coded token (examples in INTEGRATION_GUIDE/REPORT) and replace with a generated secret; never use published example tokens in production. 2) Ensure you set a strong HOOK_TOKEN (or --token) and verify openclaw_hook.py starts with that token; do not leave token unset (the server currently accepts requests when no token is configured). 3) Confirm which OpenClaw config file the installer will modify (install.py writes ~/.openclaw/config.json while docs reference openclaw.json); back up your existing OpenClaw config before running update scripts. 4) Inspect the systemd service file and decide whether to enable a user/system service; run install steps manually if you prefer (the install script will attempt to enable/start systemd). 5) Protect log and token files (HOOK_LOG_FILE, .hook_token, ~/.openclaw/*) with restrictive file permissions and consider rotating tokens. 6) Because the hook logs inbound message content, consider whether PII may be written to hook.log and control access to that file. 7) If you want to test safely, run the hook in an isolated environment or container, verify behavior, then adopt in production only after addressing the above. If you want, I can point out exact files/lines to change to fix the token/config issues and secure logging.