Versioned asset rollback versus migration‑script rollback: handling cached Template7 templates after a failed upgrade

When a Framework7 upgrade fails, developers can either redirect the router to a previous version‑specific asset bundle or run a migration script that reverts DOM changes and clears version‑specific storage. Both methods aim to restore the pre‑upgrade state, but the framework’s documentation does not guarantee what happens to the Template7 template cache during such a rollback.

The unresolved behavior is whether cached, compiled Template7 templates are retained and reused after the rollback, potentially mixing old markup with new data, or whether they are invalidated and re‑compiled from the restored bundle. This uncertainty affects UI consistency and could lead to rendering errors if stale templates persist.

Which rollback approach—versioned asset bundle redirection or migration‑script cleanup—provides a deterministic guarantee about Template7 cache handling, and what steps (if any) are required to ensure the cache is cleared or refreshed to match the rolled‑back version?