Session visibility limits after restoring a backup of Jetstream's sessions table

After restoring a database backup that includes the sessions table, the goal is to confirm that Jetstream’s session management page lists the restored sessions as active and that session expiration follows the lifetime defined in config/session.php.

It is uncertain whether the Livewire component queries the sessions table in real time or relies on cached data, and whether restored sessions will be treated as active, cause duplicate entries, or trigger premature expiration based on the configured lifetime. Additionally, it is unclear if any cleanup is required to avoid stale session records after a backup restore.

Does the Livewire session component display sessions restored from a backup as active? Will restored sessions expire according to the Laravel lifetime setting, or are they ignored until garbage collection runs? Is any manual cleanup needed to prevent stale entries after restoring the sessions table?