Does Vite need an automated upgrade command with rollback snapshots for plugin compatibility?

Vite currently lacks a built-in mechanism to automate recovery when a major version upgrade breaks plugin compatibility or leaves stale caches. The manual process—reverting package.json, restoring the lockfile, and clearing node_modules/.vite—does not address global or plugin-specific caches that may persist across reinstalls. An unresolved design question is whether Vite should ship a vite upgrade command that snapshots the pre-upgrade state, updates dependencies, and offers a one-step rollback if the build or dev server fails.

Which cache layers beyond node_modules/.vite must a rollback snapshot capture to guarantee a clean revert? Can a single command reliably detect plugin API incompatibilities before committing the upgrade? What verification steps should an automated upgrade command require before marking the migration successful?