[v2] _resetTimeout never updates startTime, so totalElapsed keeps accumulating from the original

[lowlyocean]

What happened?

The timer isn't reset when a progress notification arrives, so a long-running tool call will timeout even though progress notifications are being sent.

The inspector SDK migration guide suggests that the behavior of MCP_REQUEST_TIMEOUT_RESET_ON_PROGRESS is "always on; no longer configurable", but this bug makes that untrue.

What did you expect?

Each progress notification should cause the MCP tool call request timeout to reset.

Code to reproduce

See originally reported issue here

SDK version

2.0.0

Area

Client