xml-to-compose-migration-prolisted

Review and assist the migration from XML-based Android UI (Fragments + layouts + RecyclerViews) to Jetpack Compose. Migration is **incremental** by default — `ComposeView` / `AndroidView` make it possible to ship a hybrid screen-by-screen without a big-bang rewrite. Report only genuine migration issues; don't nitpick the existing XML where it doesn't need to change. Review process: 1. Frame the migration scope using `references/interop-strategy.md` — incremental vs all-at-once, where to put interop boundaries. 2. Translate layouts using `references/layout-migration.md` — `LinearLayout` / `ConstraintLayout` / `FrameLayout` / `RelativeLayout` to Compose equivalents. 3. Translate RecyclerViews using `references/recyclerview-to-lazy.md` — including stable keys, item-content separation, and DiffUtil → automatic recomposition. 4. Translate Fragments using `references/fragment-to-composable.md` — lifecycle ownership, ViewBinding → parameters, animations. 5. Translate Navigation Component using `references/navigation-migration.md` — `NavGraph` XML → `NavHost` Kotlin DSL. 6. Bridge ViewModels using `references/viewmodel-bridge.md` — existing ViewModels stay; only the View layer changes. 7. Translate themes using `references/themes-styles.md` — `styles.xml` → `MaterialTheme(colorScheme, typography, shapes)`. If doing a partial review, load only the relevant reference files. ## Core Instructions - **Migrate incrementally.** A full XML-to-Compose rewrite of a non-trivial app is mont