fix: use execFileSync in execSyncVarlock to handle paths with spaces (#543)

* Initial plan

* fix: use execFileSync to handle paths with spaces in execSyncVarlock

Agent-Logs-Url: https://github.com/dmno-dev/varlock/sessions/dc30e1d2-49c8-4bcf-8dd2-303af699f9ce

Co-authored-by: theoephraim <1158956+theoephraim@users.noreply.github.com>

---------

Co-authored-by: copilot-swe-agent[bot] <198982749+Copilot@users.noreply.github.com>
Co-authored-by: theoephraim <1158956+theoephraim@users.noreply.github.com>

Author: Copilot

.changeset/fix-spaces-in-path.md

@@ -0,0 +1,7 @@
+---
+"varlock": patch
+---
+
+Fix execSyncVarlock breaking when project path contains spaces
+
+Use `execFileSync` instead of `execSync` for the fallback varlock path resolution to avoid shell interpretation of spaces in directory paths.

packages/varlock/src/lib/exec-sync-varlock.ts

@@ -1,7 +1,7 @@
 import path from 'node:path';
 import fs from 'node:fs';
 import os from 'node:os';
-import { execSync } from 'node:child_process';
+import { execFileSync, execSync } from 'node:child_process';
 
 // weird tsup issue using `typeof execSync` from node:child_process
 // see https://github.com/egoist/tsup/issues/1367
@@ -49,7 +49,7 @@ export function execSyncVarlock(
       if (fs.existsSync(possibleBinPath)) {
         const possibleVarlockPath = path.join(possibleBinPath, 'varlock');
         if (fs.existsSync(possibleVarlockPath)) {
-          const result = execSync(`${possibleVarlockPath} ${command}`, {
+          const result = execFileSync(possibleVarlockPath, command.split(' '), {
             ...opts,
             stdio: 'pipe',
           });