fix(engine): correct parameter order in runVerificationCommand after merge

Reorder backend/timeoutMsOverride params so timeoutMsOverride remains at
position 10 (matching callers in executor.ts, merger.ts from main).
Update mission-verification.ts call sites to pass undefined for
timeoutMsOverride before the isolating backend argument.

packages/engine/src/mission-verification.ts

@@ -501,6 +501,7 @@ export class TestExecutionVerificationCapability implements VerificationCapabili
         verifyLog,
         "reviewer",
         scrubbedEnv,
+        undefined,
         isolating,
       );
 
@@ -531,6 +532,7 @@ export class TestExecutionVerificationCapability implements VerificationCapabili
           verifyLog,
           "reviewer",
           scrubbedEnv,
+          undefined,
           isolating,
         );
 

packages/engine/src/verification-utils.ts

@@ -324,14 +324,14 @@ export async function runVerificationCommand(
   agentLabel?: string,
   /** Optional extra environment variables to inject into the child process (merged over process.env). */
   extraEnv?: NodeJS.ProcessEnv,
+  /** Optional project-level per-command timeout override in milliseconds. Values <= 0 preserve the legacy default. */
+  timeoutMsOverride?: number,
   /**
    * Optional explicit sandbox backend. When omitted, the process-global backend
    * is resolved. Pass this to pin an isolating backend without mutating global
    * state (required for safe concurrent verification — see mission-verification).
    */
   backend?: SandboxBackend,
-  /** Optional project-level per-command timeout override in milliseconds. Values <= 0 preserve the legacy default. */
-  timeoutMsOverride?: number,
 ): Promise<VerificationCommandResult> {
   const logger = log ?? { log: console.log, error: console.error, warn: console.warn };
   const label = (agentLabel ?? "merger") as AgentRole;