migrate-from-openclaw

# Migrate from OpenClaw Guide the user through migrating their OpenClaw installation into NanoClaw v2. This is a conversation, not a batch job. Read OpenClaw state, discuss it with the user, decide together what to bring over and where it belongs in v2's entity model, and show proposed changes before applying. **Principle:** Never silently copy data. Read it, explain it, place it, then apply. Credentials are masked when displayed (first 4 + `...` + last 4). 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. ## What this skill changes (conformance) This skill drives existing NanoClaw entry points (`setup/index.ts --step register`, `scripts/init-first-agent.ts`, the `onecli` CLI) and copies a few files in (workspace markdown, OpenClaw skills, and its own transform module + test). It makes no code-level reach-in into core. Its integration assumptions about v2 are guarded by `scripts/transform.test.ts`, which is copied into the project's `scripts/` test tree on apply (Phase 8) so vitest runs it against the composed install. `REMOVE.md` reverses every file the skill copies. ## v2 architecture the migration targets OpenClaw and NanoClaw v2 differ structurally. Keep these in mind throughout: - **Entity model.** v2's central DB (`data/v2.db`) holds `users`, `user_roles`, `agent_groups`, `messaging_groups`, and t...