A project keeps its own content, configuration, and resources over the shared Gestor. project:update-all <id> runs the project's update stages and ends with css:rebuild --project=<id>; project:sync-core and project:sync-db run specific stages. The target and transport come from project configuration, rather than manual copies into a test directory. See the deployment guide.
The compiler distinguishes global and project resources. In the database, records touched by a project deployment receive project=<id>; a later core update preserves project resources according to schema-metadata.json. Fields edited through the panel can be protected by user_modified; the new system version goes to *_updated fields until explicitly applied. See resources.
Synchronizing files alone leaves database records and derived CSS at their previous version. Use the full update for changes to HTML, metadata, or resources.