Environment variable behavior after Collection Runner completion in Postman 10.12

Determine whether Postman offers a built‑in way to automatically revert environment variables to their original values after a Collection Runner run completes, so that successive runs start with a clean state without manual intervention.

The version 10.12 changelog highlights the Collection Runner cache cleanup that fixed the memory leak, but it does not mention any change to environment variable handling. Official docs state that variable modifications are retained intentionally to enable state sharing across runs, leaving teams that require isolation to implement their own reset scripts. This raises uncertainty about whether a configuration option or future update will provide automatic rollback.

• Is there a setting or flag that can be enabled to revert environment variables after each Collection Runner iteration?
• Does Postman plan to introduce an automatic reset‑on‑completion feature in a forthcoming release?
• How can teams reliably isolate state between runs without resorting to external scripts?