fix: Run example tests from their own directories with local Jest configs

Example tests now execute from their respective example directories using
their own jest.config.js files instead of the root configuration. This
resolves path resolution issues and mock conflicts that occurred when
running example tests from the repository root.

Author: celicoo

run-tests.js

@@ -2,6 +2,7 @@
 
 const path = require('path')
 const _glob = require('glob')
+const fs = require('fs')
 const { existsSync } = require('fs')
 const fsp = require('fs/promises')
 const nodeFetch = require('node-fetch')
@@ -546,8 +547,37 @@ ${ENDGROUP}`)
         return resolve(new Date().getTime() - start)
       }
 
-      const child = spawn(jestPath, args, {
+      // For example tests, run Jest from the example directory with its own config
+      const isExampleTest = test.file.startsWith('examples/')
+      let cwd = process.cwd()
+      let actualJestPath = jestPath
+      let actualArgs = args
+
+      if (isExampleTest) {
+        // Extract example directory (e.g., 'examples/with-jest' from 'examples/with-jest/__tests__/index.test.tsx')
+        const exampleDir = test.file.split('/').slice(0, 2).join('/')
+        cwd = path.join(process.cwd(), exampleDir)
+
+        // Use relative path from example directory
+        const relativePath = test.file.replace(exampleDir + '/', '')
+        actualArgs = [...args]
+        actualArgs[actualArgs.indexOf(test.file)] = relativePath
+
+        // Try to use the example's own Jest if it exists, otherwise use root Jest
+        const localJestPath = path.join(
+          cwd,
+          'node_modules',
+          '.bin',
+          `jest${process.platform === 'win32' ? '.CMD' : ''}`
+        )
+        if (fs.existsSync(localJestPath)) {
+          actualJestPath = localJestPath
+        }
+      }
+
+      const child = spawn(actualJestPath, actualArgs, {
         stdio: ['ignore', 'pipe', 'pipe'],
+        cwd,
         env: {
           ...process.env,
           ...env,