Vagrant snapshot or migration‑script rollback: choosing a method that also reverts host‑synced folder changes

The goal is to roll back a database schema change in a Vagrant‑managed development environment while also restoring any side‑effects that were written to host‑mounted synced folders during the change.

A constraint is that a Vagrant snapshot restores the VM’s disk and memory state but leaves the contents of host‑synced folders untouched, so folder artifacts persist after a snapshot rollback.

An uncertainty remains whether using versioned migration scripts with down migrations can reliably revert both the database schema and the host‑folder changes without requiring additional manual cleanup or provider‑specific steps.

Which approach guarantees that host‑folder artifacts are reverted alongside the database schema? What are the trade‑offs in storage usage and VM state consistency between snapshot‑based and script‑based rollbacks?