Schema rollback scope in Insomnia Designer after OpenAPI changes

Insomnia Designer provides a schema validation mode for OpenAPI and GraphQL documents and a documented undo schema change action that restores a temporary workspace snapshot without losing other workspace data. The rollback relies on internal version history stored in the workspace file and is described for Designer 2023.5.0 and later.

The documented limits include session-bound undo history that is cleared on restart, a requirement that the workspace be saved to disk for rollback to be available, and no automatic change to environment variables or request collections that reference the schema.

An unresolved behavior concerns consistency of dependent artifacts. Does rolling back a schema change also revert test scripts or generated client code that were updated based on the new schema, or do those artifacts remain modified and become out of sync with the reverted schema? What is the supported scope of the rollback with respect to workspace artifacts beyond the schema node?