fix(ci+android): restore the full harness suite; non-blocking legacy VMI getter

- expo57-example/jest.config.js scoped its roots to ../example/src,
  which silently dropped ~20 on-device suites (all of example/__tests__,
  including this PR's e2e guards) from every harness job. Widen the
  root to ../example so the full shared suite runs against the Expo
  app, per the config's own stated intent.

- Replace the legacy Android getViewModelInstance main-hop
  (runBlocking(Dispatchers.Main.immediate), added earlier on this
  branch) with a main-thread-maintained @volatile snapshot: off-main
  callers get the last snapshot and schedule a refresh — eventually
  consistent, which suits the polling consumers (the async hook's ref
  path, harness waitFor loops). runBlocking JS→main can deadlock if the
  main thread ever waits on JS under the legacy bridge, and is the
  prime suspect in the android-legacy harness job timing out on all
  three attempts; the hazard is real regardless of that verdict.

Author: mfazekas

android/src/legacy/java/com/margelo/nitro/rive/HybridRiveView.kt

@@ -12,7 +12,6 @@ import app.rive.runtime.kotlin.core.Alignment as RiveAlignment
 import app.rive.runtime.kotlin.core.errors.*
 import android.util.Log
 import kotlinx.coroutines.Dispatchers
-import kotlinx.coroutines.runBlocking
 import kotlinx.coroutines.withContext
 
 fun Variant_HybridViewModelInstanceSpec_DataBindMode_DataBindByName?.toBindData(): BindData {
@@ -116,13 +115,9 @@ class HybridRiveView(val context: ThemedReactContext) : HybridRiveViewSpec() {
     }
 
   override fun getViewModelInstance(): HybridViewModelInstanceSpec? {
-    // Read on the main thread: the controller's state-machine list is mutated
-    // there during startup and the legacy runtime has no internal
-    // synchronization (issue #297 race class). Mirrors iOS's MainThread.run;
-    // `immediate` avoids a deadlock when already called on main.
-    val viewModelInstance =
-      runBlocking(Dispatchers.Main.immediate) { view.getViewModelInstance() }
-        ?: return null
+    // Thread-safety lives in RiveReactNativeView.getViewModelInstance(): it
+    // returns a main-thread-maintained snapshot without blocking this thread.
+    val viewModelInstance = view.getViewModelInstance() ?: return null
     return HybridViewModelInstance(viewModelInstance)
   }
 

android/src/legacy/java/com/rive/RiveReactNativeView.kt

@@ -167,7 +167,17 @@ class RiveReactNativeView(context: ThemedReactContext) : FrameLayout(context) {
     }
   }
 
-  fun getViewModelInstance(): ViewModelInstance? {
+  // Cache maintained on the main thread: the controller's state-machine list
+  // is mutated there and the legacy runtime has no internal synchronization
+  // (issue #297 race class), so other threads must not traverse it. Off-main
+  // reads return the last main-thread snapshot and schedule a refresh —
+  // eventually consistent, which suits the polling callers (the async hook's
+  // ref path, harness waitFor loops). Blocking on the main thread instead
+  // would risk a JS↔main deadlock under the legacy bridge.
+  @Volatile
+  private var lastKnownViewModelInstance: ViewModelInstance? = null
+
+  private fun readViewModelInstanceOnMain(): ViewModelInstance? {
     val stateMachines = riveAnimationView?.controller?.stateMachines
     return if (!stateMachines.isNullOrEmpty()) {
       stateMachines.first().viewModelInstance
@@ -176,6 +186,17 @@ class RiveReactNativeView(context: ThemedReactContext) : FrameLayout(context) {
     }
   }
 
+  fun getViewModelInstance(): ViewModelInstance? {
+    if (android.os.Looper.myLooper() == android.os.Looper.getMainLooper()) {
+      lastKnownViewModelInstance = readViewModelInstanceOnMain()
+      return lastKnownViewModelInstance
+    }
+    android.os.Handler(android.os.Looper.getMainLooper()).post {
+      lastKnownViewModelInstance = readViewModelInstanceOnMain()
+    }
+    return lastKnownViewModelInstance
+  }
+
   fun applyDataBinding(bindData: BindData) {
     bindToStateMachine(bindData)
   }

expo57-example/jest.config.js

@@ -1,6 +1,8 @@
 module.exports = {
   preset: 'react-native-harness',
-  // Run the bare example's harness suite against this Expo app; the shared
-  // metro config redirects those files' imports into this workspace.
-  roots: ['<rootDir>', '<rootDir>/../example/src'],
+  // Run the bare example's FULL harness suite against this Expo app (both
+  // example/__tests__ and example/src/__tests__); the shared metro config
+  // redirects those files' imports and assets into this workspace. Scoping
+  // this to example/src silently dropped ~20 on-device suites from CI.
+  roots: ['<rootDir>', '<rootDir>/../example'],
 };