compose-state-authoring

Jetpack Compose UI state resets during recomposition when local variables are not backed by `remember` and `mutableStateOf`. You must wrap state initialization in `remember { mutableStateOf(...) }` to ensure values survive recomposition cycles.

To properly observe list mutations in Jetpack Compose state, use `mutableStateListOf` or `mutableStateMapOf` instead of `remember { mutableStateOf(mutableListOf(...)) }`. Standard mutable collections bypass snapshot observation, causing UI updates to fail when items are added.

You can safely apply the `@ReadOnlyComposable` annotation only when a composable function strictly reads composition state without allocating UI nodes, calling `remember`, or invoking non-read-only composables to prevent invalid runtime optimizations.

To write recomposition-safe local state in a @Composable function, ensure every local `var` is backed by `remember` plus `mutableStateOf`, `mutableStateListOf`, or `mutableStateMapOf` to trigger correct snapshot mutation observation and UI updates.

The best way to prevent Jetpack Compose snapshot observation bugs is to avoid wrapping standard mutable collections in `mutableStateOf`. Replace value references or use `mutableStateListOf` to ensure mutations are tracked by the snapshot system correctly.

Using `remember` with `mutableStateOf` does not fix all Compose state update issues. If you store a mutable collection like `mutableListOf` inside `mutableStateOf`, calling `.add()` bypasses snapshot observation, so you must use `mutableStateListOf` instead.