migrate-nanoclaw

To migrate customizations without merge conflicts, extract user modifications from a fork into a replayable migration guide, then reapply those customizations onto a clean upstream base using intent-based migration rather than merge-based upgrades.

Intent-based migration replaces merge-based upgrades by extracting customizations into a guide that captures implementation details, then reapplying those changes on a clean base. This avoids merge conflicts by replaying intent rather than merging divergent branches.

Safely upgrade a forked repository by backing up customizations, validating the applied changes within a git worktree, and applying customizations in controlled stages. This process provides a safe rollback strategy if the upstream upgrade fails.

Yes, you can validate repository upgrades using a git worktree. The migration process validates changes in a worktree to ensure the reapplication of customizations on a clean upstream base is safe and correct before finalizing.

No, fork migration does not affect runtime state or data. The extraction, guide-generation, and upgrade steps replace merge-based upgrades with intent-based migration across the repository without touching data or runtime state.

Use intent-based migration over a standard git merge when you need to upgrade a heavily customized fork to upstream. It avoids complex merge conflicts by extracting intent and reapplying customizations on a clean base, ensuring safe, controlled staging.