refactor: rename clawdbot to moltbot with legacy compat

docs/concepts/model-failover.md

@@ -1,5 +1,5 @@
 ---
-summary: "How Clawdbot rotates auth profiles and falls back across models"
+summary: "How Moltbot rotates auth profiles and falls back across models"
 read_when:
   - Diagnosing auth profile rotation, cooldowns, or model fallback behavior
   - Updating failover rules for auth profiles or models
@@ -7,7 +7,7 @@ read_when:
 
 # Model failover
 
-Clawdbot handles failures in two stages:
+Moltbot handles failures in two stages:
 1) **Auth profile rotation** within the current provider.
 2) **Model fallback** to the next model in `agents.defaults.model.fallbacks`.
 
@@ -15,7 +15,7 @@ This doc explains the runtime rules and the data that backs them.
 
 ## Auth storage (keys + OAuth)
 
-Clawdbot uses **auth profiles** for both API keys and OAuth tokens.
+Moltbot uses **auth profiles** for both API keys and OAuth tokens.
 
 - Secrets live in `~/.clawdbot/agents/<agentId>/agent/auth-profiles.json` (legacy: `~/.clawdbot/agent/auth-profiles.json`).
 - Config `auth.profiles` / `auth.order` are **metadata + routing only** (no secrets).
@@ -37,20 +37,20 @@ Profiles live in `~/.clawdbot/agents/<agentId>/agent/auth-profiles.json` under `
 
 ## Rotation order
 
-When a provider has multiple profiles, Clawdbot chooses an order like this:
+When a provider has multiple profiles, Moltbot chooses an order like this:
 
 1) **Explicit config**: `auth.order[provider]` (if set).
 2) **Configured profiles**: `auth.profiles` filtered by provider.
 3) **Stored profiles**: entries in `auth-profiles.json` for the provider.
 
-If no explicit order is configured, Clawdbot uses a round‑robin order:
+If no explicit order is configured, Moltbot uses a round‑robin order:
 - **Primary key:** profile type (**OAuth before API keys**).
 - **Secondary key:** `usageStats.lastUsed` (oldest first, within each type).
 - **Cooldown/disabled profiles** are moved to the end, ordered by soonest expiry.
 
 ### Session stickiness (cache-friendly)
 
-Clawdbot **pins the chosen auth profile per session** to keep provider caches warm.
+Moltbot **pins the chosen auth profile per session** to keep provider caches warm.
 It does **not** rotate on every request. The pinned profile is reused until:
 - the session is reset (`/new` / `/reset`)
 - a compaction completes (compaction count increments)
@@ -60,9 +60,9 @@ Manual selection via `/model …@<profileId>` sets a **user override** for that
 and is not auto‑rotated until a new session starts.
 
 Auto‑pinned profiles (selected by the session router) are treated as a **preference**:
-they are tried first, but Clawdbot may rotate to another profile on rate limits/timeouts.
+they are tried first, but Moltbot may rotate to another profile on rate limits/timeouts.
 User‑pinned profiles stay locked to that profile; if it fails and model fallbacks
-are configured, Clawdbot moves to the next model instead of switching profiles.
+are configured, Moltbot moves to the next model instead of switching profiles.
 
 ### Why OAuth can “look lost”
 
@@ -73,7 +73,7 @@ If you have both an OAuth profile and an API key profile for the same provider,
 ## Cooldowns
 
 When a profile fails due to auth/rate‑limit errors (or a timeout that looks
-like rate limiting), Clawdbot marks it in cooldown and moves to the next profile.
+like rate limiting), Moltbot marks it in cooldown and moves to the next profile.
 Format/invalid‑request errors (for example Cloud Code Assist tool call ID
 validation failures) are treated as failover‑worthy and use the same cooldowns.
 
@@ -99,7 +99,7 @@ State is stored in `auth-profiles.json` under `usageStats`:
 
 ## Billing disables
 
-Billing/credit failures (for example “insufficient credits” / “credit balance too low”) are treated as failover‑worthy, but they’re usually not transient. Instead of a short cooldown, Clawdbot marks the profile as **disabled** (with a longer backoff) and rotates to the next profile/provider.
+Billing/credit failures (for example “insufficient credits” / “credit balance too low”) are treated as failover‑worthy, but they’re usually not transient. Instead of a short cooldown, Moltbot marks the profile as **disabled** (with a longer backoff) and rotates to the next profile/provider.
 
 State is stored in `auth-profiles.json`:
 
@@ -120,7 +120,7 @@ Defaults:
 
 ## Model fallback
 
-If all profiles for a provider fail, Clawdbot moves to the next model in
+If all profiles for a provider fail, Moltbot moves to the next model in
 `agents.defaults.model.fallbacks`. This applies to auth failures, rate limits, and
 timeouts that exhausted profile rotation (other errors do not advance fallback).