BUG-001: MCP tool call missing progressToken injection causing timeout on long reviews (-32001) #14499

Bug Description

OpenCode experiences -32001 timeout errors during long-running code reviews (10~20 minutes) when calling MCP tools (like review-mcp), even though:

• The MCP server has implemented progress notifications with 12-second heartbeat
• OpenCode client has resetTimeoutOnProgress: true set

The timeout errors still occur, indicating a broken link between "server heartbeat exists" and "client timeout renewal works".

Root Cause Analysis

The issue is NOT whether the server sends heartbeat, but whether the client establishes a complete timeout renewal chain: progressToken + progress handler + resetTimeoutOnProgress.

Current Data Flow (Broken Link)

Break point: Step 3 -> 4 (OpenCode doesn't provide onprogress, so SDK doesn't inject progressToken)

Consequence: Server can't see token, heartbeat degrades to no-op; client timer never resets, long request hits -32001.

Proposed Solution

Add onprogress callback in OpenCode's MCP call options at packages/opencode/src/mcp/index.ts:142:

return client.callTool(
  {
    name: mcpTool.name,
    arguments: (args || {}) as Record<string, unknown>,
  },
  CallToolResultSchema,
  {
    onprogress: (event) => {
      log.debug("mcp progress", {
        tool: mcpTool.name,
        progress: event.progress,
        total: event.total,
      })
    },
    resetTimeoutOnProgress: true,
    timeout,
  },
)

This allows the SDK to:

1. Inject progressToken in request _meta
2. Trigger _resetTimeout() on progress notifications

Acceptance Criteria

• Both design and implementation review types no longer experience -32001 timeout
• Works reliably without relying on "fixed long timeout" as primary strategy
• Unit tests verify onprogress callback is included in call options
• Integration tests verify progress notifications renew timeout
• E2E tests pass for long-running tool scenarios

Constraints

• Must maintain existing MCP tool protocol compatibility
• Should work with any MCP server that supports progress notifications
• Progress callback should be lightweight (debug logging only for now)

Related

• MCP SDK: https://github.com/modelcontextprotocol/typescript-sdk