Does DataSpell’s Local History preserve Jupyter kernel state after notebook restoration?

Goal

To understand whether DataSpell’s Local History feature can reliably restore a Jupyter notebook to a runnable state, including re‑establishing the kernel connection and any associated environment settings.

Current Behavior

Local History records changes to notebook files (.ipynb) and allows a user to revert to any prior snapshot via the IDE’s context menu. After restoring a notebook, the kernel connection is lost; the user must manually reconnect and re‑execute cells to return to a runnable state. Database connection configurations are not backed up, and there is no public API to trigger a revert programmatically.

Unresolved Questions

• Is there a built‑in or future‑planned mechanism that automatically reconnects the Jupyter kernel or restores the execution environment when a notebook is reverted from Local History?
• Can the snapshot retention policy be configured to keep all historical versions regardless of the configured size limit, ensuring critical changes are never purged?
• Does DataSpell expose any API or command‑line option to programmatically trigger a Local History revert, enabling automated backup verification workflows?