update

To update NanoClaw without losing local customizations, fetch upstream changes and merge them with local modifications. The process handles conflict resolution using intent files and runs necessary migrations to preserve custom agent behaviors.

Merge conflict resolution during an upstream sync uses intent files to intelligently guide the integration of new upstream code with local customizations. It flags conflicts and helps resolve them to ensure custom modifications remain intact.

Yes, you need git, Node.js with npm, and TypeScript execution to run migrations for a codebase update. These tools are required to fetch upstream changes, execute database migrations, and verify the build.

The best way to verify a codebase after merging upstream changes is to run post-update verification through build and tests. This ensures the updated code compiles successfully and passes all functional tests.

Pre-flight checking matters before fetching upstream code because it validates environment readiness and prevents sync failures. It ensures local state is stable before attempting to merge new changes and run migrations.

You should run database migrations during a codebase sync immediately after successfully merging upstream changes. This updates your data structure to match the new version before executing post-update verification and tests.