fix: enhance studio path resolution for pnpm strict isolation

Author: hotlong

packages/cli/src/utils/studio.ts

@@ -9,6 +9,7 @@
 import path from 'path';
 import fs from 'fs';
 import net from 'net';
+import { createRequire } from 'module';
 import { spawn, type ChildProcess } from 'child_process';
 import chalk from 'chalk';
 
@@ -49,14 +50,32 @@ export function resolveStudioPath(): string | null {
   }
 
   // Fallback: resolve from node_modules
-  try {
-    const { createRequire } = require('module');
-    const req = createRequire(import.meta.url);
-    const resolved = req.resolve('@objectstack/studio/package.json');
-    return path.dirname(resolved);
-  } catch {
-    return null;
+  // Try resolving from the consumer's working directory first (important for
+  // pnpm strict isolation where the CLI cannot see the consumer's dependencies),
+  // then fall back to resolving from the CLI's own location.
+  const resolutionBases = [
+    path.join(cwd, '__placeholder__.js'),   // consumer workspace
+    import.meta.url,                          // CLI package itself
+  ];
+
+  for (const base of resolutionBases) {
+    try {
+      const req = createRequire(base);
+      const resolved = req.resolve('@objectstack/studio/package.json');
+      return path.dirname(resolved);
+    } catch (e) {
+      // Not resolvable from this base — try next
+      if (process.env.DEBUG) console.error(`  [studio] resolve from ${base} failed:`, (e as Error).message);
+    }
   }
+
+  // Last resort: direct filesystem check in node_modules
+  const directPath = path.join(cwd, 'node_modules', '@objectstack', 'studio');
+  if (fs.existsSync(path.join(directPath, 'package.json'))) {
+    return directPath;
+  }
+
+  return null;
 }
 
 /**