refactor: rename clawdbot to moltbot with legacy compat

docs/automation/cron-vs-heartbeat.md

@@ -95,7 +95,7 @@ Cron jobs run at **exact times** and can run in isolated sessions without affect
 ### Cron example: Daily morning briefing
 
 ```bash
-clawdbot cron add \
+moltbot cron add \
   --name "Morning briefing" \
   --cron "0 7 * * *" \
   --tz "America/New_York" \
@@ -112,7 +112,7 @@ This runs at exactly 7:00 AM New York time, uses Opus for quality, and delivers
 ### Cron example: One-shot reminder
 
 ```bash
-clawdbot cron add \
+moltbot cron add \
   --name "Meeting reminder" \
   --at "20m" \
   --session main \
@@ -168,13 +168,13 @@ The most efficient setup uses **both**:
 **Cron jobs** (precise timing):
 ```bash
 # Daily morning briefing at 7am
-clawdbot cron add --name "Morning brief" --cron "0 7 * * *" --session isolated --message "..." --deliver
+moltbot cron add --name "Morning brief" --cron "0 7 * * *" --session isolated --message "..." --deliver
 
 # Weekly project review on Mondays at 9am
-clawdbot cron add --name "Weekly review" --cron "0 9 * * 1" --session isolated --message "..." --model opus
+moltbot cron add --name "Weekly review" --cron "0 9 * * 1" --session isolated --message "..." --model opus
 
 # One-shot reminder
-clawdbot cron add --name "Call back" --at "2h" --session main --system-event "Call back the client" --wake now
+moltbot cron add --name "Call back" --at "2h" --session main --system-event "Call back the client" --wake now
 ```
 
 
@@ -226,7 +226,7 @@ Use `--session main` with `--system-event` when you want:
 - No separate isolated run
 
 ```bash
-clawdbot cron add \
+moltbot cron add \
   --name "Check project" \
   --every "4h" \
   --session main \
@@ -243,7 +243,7 @@ Use `--session isolated` when you want:
 - History that doesn't clutter main session
 
 ```bash
-clawdbot cron add \
+moltbot cron add \
   --name "Deep analysis" \
   --cron "0 6 * * 0" \
   --session isolated \