Video-only Session Rewind versus state restoration after a schema change

Teams using BrowserStack Automate want rollback-safe debugging after a server-side schema change and are evaluating Session Rewind as a way to inspect a prior point in a test session.

Session Rewind is documented as a capability to jump to a specific timestamp within a test session's video recording for visual debugging. The UI description covers video playback, while the REST API reference does not expose explicit semantics for restoring browser storage, cookies, localStorage, sessionStorage, DOM or JavaScript state to the rewind point.

The unresolved behavior is whether rewinding affects the live browser context at all, or is limited to video playback. When tests depend on schema-dependent responses, a mismatch between the video timestamp and the current client state can create ambiguity about what is being inspected.

Does Session Rewind restore browser storage and DOM to the selected timestamp, or is playback video-only? If state is not restored, what is the documented contract for state consistency between the video timestamp and the live browser context? Is there a documented approach to guarantee a clean browser context after a schema change when reusing a session?