Keep Android screen state and events separate.
Guides Android ViewModel implementation so screen state stays immutable to consumers and one-off events remain separate.
When to use it
Use when implementing Android ViewModels and managing UI state and one-off events.
It changes how the agent implements Android ViewModels, assigning UI state and business logic to ViewModels and exposing immutable APIs.
What you provide
The preferred explicit backing-field pattern uses Kotlin 2.3 with -Xexplicit-backing-fields or Kotlin 2.4+, where it is stable and recommended.
No additional actions listed.