fix(sep-2243): forward only signal/timeout to the -32001 recovery refresh

The one-refresh-on-HeaderMismatch recovery in callTool() passed the
caller's full CallToolRequestOptions to _refreshAllToolDefinitions(),
which forwards them to every internal listTools() page. Options like
toolDefinition, headers, and onprogress are tools/call-specific and do
not apply to tools/list — only the abort signal and timeout should
propagate.

Author: felixweinberger

packages/client/src/client/client.ts

@@ -1733,7 +1733,7 @@ export class Client extends Protocol<ClientContext> {
             if (!mirroringActive || !isHeaderMismatch || options?.toolDefinition !== undefined) {
                 throw error;
             }
-            await this._refreshAllToolDefinitions(options).catch(() => {});
+            await this._refreshAllToolDefinitions({ signal: options?.signal, timeout: options?.timeout }).catch(() => {});
             result = await this.request({ method: 'tools/call', params }, buildSendOptions());
         }
 
@@ -1823,7 +1823,10 @@ export class Client extends Protocol<ClientContext> {
 
     /**
      * SEP-2243 internal recovery refresh: walk every `tools/list` page so
-     * `_cachedToolDefinitions` is rebuilt completely. The `-32001` retry path
+     * `_cachedToolDefinitions` is rebuilt completely. Only the caller's
+     * `signal`/`timeout` are forwarded to each page request — `tools/call`
+     * options like `toolDefinition`, `headers`, or `onprogress` do not apply
+     * to `tools/list`. The `-32001` retry path
      * in {@linkcode callTool} uses this rather than a bare cursor-less
      * `listTools()`, which would only fetch page 1 and (because page 1 clears
      * the merged cache) drop the page-≥2 scans the application accumulated via