fix(startup): load libsodium synchronously to prevent race with Compose

LibSodiumInitializer was wrapping initializeWithCallback in a
CoroutineScope(Dispatchers.IO).launch, making native lib loading
fire-and-forget. On slower devices, Compose could attach and call
Box.keypair() before the background coroutine finished, crashing with:

    UninitializedPropertyAccessException: lateinit property sodiumJna
    has not been initialized

Initializer.create() runs on the main thread at app startup, and on
Android initializeWithCallback is synchronous (JNA Native.load +
sodium_init), so calling it directly guarantees sodium is ready
before any downstream caller touches it.

Author: bmc08gt

apps/flipcash/app/src/main/kotlin/com/flipcash/app/internal/startup/LibSodiumInitializer.kt

@@ -5,16 +5,17 @@ import androidx.startup.Initializer
 import com.getcode.utils.TraceType
 import com.getcode.utils.trace
 import com.ionspin.kotlin.crypto.LibsodiumInitializer
-import kotlinx.coroutines.CoroutineScope
-import kotlinx.coroutines.Dispatchers
-import kotlinx.coroutines.launch
 
 class LibSodiumInitializer: Initializer<Unit> {
     override fun create(context: Context) {
-        CoroutineScope(Dispatchers.IO).launch {
-            LibsodiumInitializer.initializeWithCallback {
-                trace("libsodium initialized", type = TraceType.Process)
-            }
+        // Must run synchronously on the main thread: Initializer.create runs at app
+        // startup before any UI is attached, and downstream callers (e.g. Box.keypair)
+        // hit sodiumJna as soon as Compose attaches. Dispatching this to a background
+        // coroutine creates a race where the native lib may not be loaded in time.
+        // On Android, initializeWithCallback is synchronous — it loads the .so via
+        // JNA, calls sodium_init, then invokes the callback on the same thread.
+        LibsodiumInitializer.initializeWithCallback {
+            trace("libsodium initialized", type = TraceType.Process)
         }
     }