migrate-from-openclaw

# Migrate from OpenClaw Guide the user through migrating their OpenClaw installation to NanoClaw. This is a conversation, not a batch job. Read OpenClaw state, discuss it with the user, make judgment calls together about what to bring over and how. **Principle:** Never silently copy data. Read it, explain it, discuss where it belongs in NanoClaw's architecture, show proposed changes before applying. Credentials must be masked when displayed (first 4 + `...` + last 4 characters). Make judgment calls about what's core vs. reference material. **UX:** Use `AskUserQuestion` for multiple-choice only. Use plain text for free-form input. Don't dump raw data — summarize and explain conversationally. ## Migration State File Create `migration-state.md` in the project root at the start of Phase 0. Update it after each phase completes. This file is the single source of truth for the migration — if context is compacted or lost, re-read it to recover all decisions and progress. Before starting any phase, re-read `migration-state.md` to ensure you have current state. Sections to maintain (add data as each phase completes): - **Progress** — checkbox list of phases (Phase 0–7) - **Discovery** — STATE_DIR, IDENTITY_NAME, channels, groups (with JID mappings), workspace files, cron job count, MCP servers - **Decisions** — assistant_name, group_model (shared/separate/main-only), main_group (folder + jid) - **Registered Groups** — table: folder, jid, channel, is_main - **Settings Migrated**...