Pull reads the remote working definition. Push writes it. Neither operation changes the live version by itself.
Pull current state
The project link in .fluidrc identifies the definition. You can select a different definition explicitly:
Use --force only when you intend to overwrite local changes while switching definitions.
Reconcile concurrent changes
Before a remote write:
- Preserve your local changes in version control or a patch.
- Pull the current working definition.
- Reapply the intended local edits.
- Resolve cross-resource slug changes.
- Run local validation and review the diff.
Do not edit .portal-sync/ to suppress drift. It is tool-managed synchronization state.
Push the working definition
Use --yes only to skip the confirmation prompt:
--yes does not approve new widget network access. After package review, use interactive approval or the explicit --allow-network-widgets option.
Recover from a partial push
Push can partially succeed. If a phase fails, earlier successful changes can remain.
Read the command result. Inspect the remote state and the tool-managed synchronization state. Fix the reported local resource and rerun validation and push. Do not assume the operation rolled back.
Do not add --activate to the normal synchronization workflow. First make the working definition correct. Then create and activate a version as separate release steps.
