fix(tools): pass time parameter to page.evaluate in waitForTimeout

[SebTardif]

waitForTimeout(time) has two branches:

• Blocked path (dialog active): correctly uses the time parameter
• Normal path: hardcodes 1000ms, ignoring time

Both callers in utils.ts pass 500, so every waitForCompletion cycle (click, fill, navigate, and other interactive tools) waits 1000ms instead of the intended 500ms. This adds an unnecessary 500ms to each tool call.

The fix passes the time parameter through to page.evaluate, making the normal path consistent with the blocked path.

Before:

await this.page.evaluate(() => new Promise(f => setTimeout(f, 1000))).catch(() => {});

After:

await this.page.evaluate(ms => new Promise(f => setTimeout(f, ms)), time).catch(() => {});

This was introduced in #37286 when MCP tools were moved into the monorepo.

[github-actions]

Test results for "MCP"

1 failed
❌ [chrome] › mcp/cli-killall.spec.ts:42 › kill-all kills filtered dashboard pid @mcp-windows-latest-chrome

7206 passed, 1113 skipped

---

Merge workflow run.