Make the release build traceable: profileable, with composable names

System Tracing on the phone only records an app's own trace sections when
the app is debuggable or profileable, and the phone runs a build that is
neither once release builds exist. profileable shell="true" admits shell
profilers and nothing else. runtime-tracing names composables inside those
sections and is inert until a trace is recording.

Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>

app/gradle/libs.versions.toml

@@ -68,6 +68,11 @@ androidx-exifinterface = { module = "androidx.exifinterface:exifinterface", vers
 # Declared directly rather than through the plugin's `compose.*` accessors,
 # which are deprecated as of CMP 1.11.
 compose-runtime = { module = "org.jetbrains.compose.runtime:runtime", version.ref = "compose-multiplatform" }
+# Names composables in a system trace, which is how a per-frame cost on the
+# phone gets attributed to a composable rather than to "Compose". Inert until
+# a trace is being recorded. Its own release train: 1.12.0 was the newest
+# stable on Google Maven on 2026-09-02.
+compose-runtime-tracing = { module = "androidx.compose.runtime:runtime-tracing", version = "1.12.0" }
 compose-foundation = { module = "org.jetbrains.compose.foundation:foundation", version.ref = "compose-multiplatform" }
 compose-material3 = { module = "org.jetbrains.compose.material3:material3", version.ref = "compose-material3" }
 compose-ui = { module = "org.jetbrains.compose.ui:ui", version.ref = "compose-multiplatform" }