Consistency of /etc configurations after Btrfs snapshot rollbacks

Fedora utilizes Btrfs as the default filesystem, allowing for snapshots that facilitate system recovery after a failed package upgrade. While dnf rollback can revert package versions based on transaction history, there is ambiguity regarding the state of manual configuration files during a filesystem‑level revert.

When a user reverts to a previous Btrfs snapshot via the GRUB menu to undo a failed upgrade, the entire root returns to that point in time. However, manual edits made to files in /etc between the snapshot creation and the upgrade failure may conflict with the expected state of older package versions being re‑introduced.

How does the system handle conflicts when local configuration changes are overwritten or de‑synced during a Btrfs subvolume rollback? Is there a mechanism to ensure that manual /etc edits are synchronized with the reverted package state to prevent service instability?