claude: Make command-utils import dynamic to fix build cycle

Changed execute/engine.ts to use dynamic import for initializeProjectContextAndEngines
from command/command-utils.ts. This breaks a circular dependency that was causing
the build to fail.

The cycle was:
  execute/engine.ts → command/command-utils.ts → ... → execute/engine.ts

The import is only used in the engine command action handler, so making it dynamic
has no performance impact on normal operations while fixing the build.

🤖 Generated with [Claude Code](https://claude.com/claude-code)

Co-Authored-By: Claude <[email protected]>

Author: gordonwoodhull

src/execute/engine.ts

@@ -40,7 +40,8 @@ import { Command } from "cliffy/command/mod.ts";
 import { quartoAPI } from "../core/api/index.ts";
 import { satisfies } from "semver/mod.ts";
 import { quartoConfig } from "../core/quarto.ts";
-import { initializeProjectContextAndEngines } from "../command/command-utils.ts";
+// Dynamic import to break circular dependency
+// import { initializeProjectContextAndEngines } from "../command/command-utils.ts";
 
 const kEngines: Map<string, ExecutionEngineDiscovery> = new Map();
 
@@ -386,6 +387,9 @@ export const engineCommand = new Command()
   .arguments("<engine-name:string> [args...:string]")
   .action(async (options, engineName: string, ...args: string[]) => {
     // Initialize project context and register external engines
+    const { initializeProjectContextAndEngines } = await import(
+      "../command/command-utils.ts"
+    );
     await initializeProjectContextAndEngines();
 
     // Get the engine (now includes external ones)