Problem

When dmPolicy is set to "pairing", the gateway silently stops responding to Telegram messages after a restart. The pairing state is lost, but no error is surfaced — the Telegram provider starts and logs show everything is fine.

Reproduction

1. Configure dmPolicy: "pairing" and complete pairing
2. Restart the gateway (openclaw gateway restart)
3. Bot stops responding — no errors in logs

Fix

Using dmPolicy: "allowlist" with allowFrom: ["<user_id>"] is permanent and survives restarts.

Suggested Improvements

• For single-user setups (one phone number, one Telegram user), the CLI/setup wizard should recommend or default to allowlist over pairing
• If dmPolicy: "pairing" is used and pairing state is lost on restart, surface a warning in logs rather than silently failing
• Docs should clearly explain the restart gotcha for pairing mode