Jetstream stack migration from Livewire to Inertia without downtime

The goal is to move a small Laravel application from the Jetstream Livewire stack to the Inertia stack while keeping the site available. Jetstream treats the frontend stack as an installation-time decision, so the change requires rewriting Blade views as Inertia pages rather than updating a single configuration value. Laravel Fortify continues to own registration, login, verification, and two-factor rules through config/fortify.php, but it is unclear whether those routes can safely render both Livewire and Inertia responses while old and new code are deployed side by side. Additive migrations for sessions, personal access tokens, and two-factor secrets must remain compatible with both UI implementations, and device-session features such as log out of other browsers depend on shared session storage across load-balanced nodes.

What conditions allow Fortify-managed authentication routes to serve Livewire and Inertia views concurrently during a staggered migration? Which Jetstream database changes must stay additive while both stacks are active? How should shared session storage be configured so device-session behavior remains consistent across nodes running different Jetstream frontend stacks?