wp-migratelisted

# WP Migrate End-to-end migration workflow. Owns dryrun, apply, backup, restore, clone. The HARDEST safety surface in the toolkit — every step is destructive at production scale. Walks a plan → backup → apply → verify → rollback ladder. ## Iron Rule <EXTREMELY-IMPORTANT> 1. NEVER apply a migration without running `migrate_dryrun` first AND surfacing the plan to the user for explicit OK — apply is irreversible at scale. 2. NEVER apply without `backup_create` on the destination first — the only reliable rollback is the destination backup, taken IMMEDIATELY before apply, archived locally. 3. NEVER set destination to production-matched siteurl without `confirm_production: true` AND the user typing back the destination hostname verbatim — most production data loss starts with a fast "yes, go" reply. </EXTREMELY-IMPORTANT> ## When to use - "Move dev to staging" - "Sync the latest plugin set from dev to prod" - "Clone walnut.local to a new sandbox site" - "Back this up before I install a risky plugin" - "Roll back last week's migration" Skip when: - The change is content-only (a few posts) → `wp-content` REST CRUD. - The change is a single plugin's config → `wp-edit-plugin`. ## Boundary Owns: - `rolepod_wp_migrate_dryrun` — compute the plan without applying. - `rolepod_wp_migrate_data` — apply the plan. - `rolepod_wp_backup_create` — pre-apply backup of destination. - `rolepod_wp_backup_restore` — rollback path. - `rolepod_wp_clone` — full-site copy (db + wp-content + URL re