update-gaia

To update a framework without overwriting custom files, use a three-way merge strategy based on manifest-defined file ownership. This approach compares your current code, the baseline, and the latest release to preserve adopter-owned customizations.

The best way to sync local project files with the latest GAIA release is through an automated three-way merge. This process respects manifest-defined file classes to protect your customizations while managing version transitions and complex directory structures.

Yes, you need git, gh CLI, jq, and curl installed. These dependencies are required for version resolution, state detection, and manifest processing during the automated three-way merge synchronization process.

Manifest-driven file ownership handles conflict patching by categorizing files into owned, shared, and wiki-owned classes. This ensures the merge respects your customizations and automatically generates conflict patches for manual review.

Framework updates fail to preserve local modifications when not using a manifest-driven three-way merge. Properly defining file ownership in your manifest ensures customizations are safely preserved across complex directory structures during version transitions.

Yes, you can automatically create backups when syncing with the GAIA framework. The update process features automated safety measures that generate backups and conflict patches for manual review to ensure you never lose work.