parallelSplashInit

When true, the TemplateApplication.onCreate prewarm path constructs the CoreApi on a background IO coroutine instead of waiting for the first Activity lazy-init. This overlaps the JNI loadLibrary + DB open + MetadataRepository construction with whatever the splash/login screen is doing on the main thread.

Default false — third-party SDK consumers see no behavior change. Demo / kiosk shells flip true in their Application.onCreate BEFORE calling super.onCreate() so the gate is set when com.mapsted.app_template.TemplateApplication reads it. Set after super.onCreate() runs, the prewarm has already finished its gate check and the flag has no effect.

Race-safe: MapstedBaseApplication.setCoreApi destroys the loser of a foreground/prewarm collision (releasing native resources) so even if the activity races ahead and calls getCoreApi() before the prewarm finishes, exactly one CoreApi survives.