migrate-nanoclaw

Replayable migration guides capture intent and implementation details of customizations, enabling an intent-based upgrade by reapplying documented changes to a clean upstream base instead of resolving messy merge conflicts.

Intent-based migration replaces merge-based upgrades by extracting user customizations into a replayable guide, then reapplying those documented changes onto a clean upstream checkout to avoid merge conflicts entirely.

Extract customizations from a fork by running an extraction phase that documents changes, creates backup points, and generates a replayable migration guide containing explicit instructions, code snippets, and configurations.

Yes, the upgrade phase uses a clean worktree to apply the migration guide to upstream changes, preventing merge conflicts by reapplying customizations directly onto a fresh upstream base.

Handling non-standard customizations during an upstream code upgrade requires detailed documentation with explicit instructions, code snippets, and configurations to adapt them correctly when applying the migration guide.

Yes, a structured plan to merge skills and customizations provides rollback points and safety checks, ensuring you can safely revert if applying the migration guide to upstream changes fails.