Vagrant VM fails to boot after box upgrade (VirtualBox)

Goal: Safely return a Vagrant environment to a working state when a box upgrade leaves the associated VM unable to start, while preserving existing provider‑specific disks and avoiding unnecessary cleanup of orphaned artifacts.

Constraints: The recovery must not rely on automatic fallback (Vagrant does not revert box versions), must work across providers (focus on VirtualBox), and should allow the Vagrantfile to continue referencing a known‑good box version. Uncertainty remains about whether a provider‑agnostic procedure exists to detach the VM from the broken box and re‑attach it to a prior version without manual intervention in the provider UI, and what steps are required to remove any leftover state that could cause repeated failures.

Questions: Is there a Vagrant‑only method to revert a running VM to the previously used box version? If not, what is the recommended sequence of commands to point the VM at a known‑good box while keeping its disks intact? Are there provider‑agnostic cleanup actions to eliminate orphaned artifacts after such a failure?