Does Drupal 10 core config sync resolve field storage schema drift?

Maintaining a repeatable development environment in Drupal 10 relies on synchronizing configuration via YAML files. While core configuration synchronization handles most settings, differences in field storage schemas between environments can lead to synchronization conflicts.

The current challenge involves scenarios where entity field definitions diverge across environments. Because the core system does not automatically merge these changes, schema drift can occur, potentially causing failures during the import process.

Which mechanisms are available to resolve field storage conflicts without manual database intervention? Does the interaction between core sync and the Config Split module provide a reliable way to manage these discrepancies across environments?