fix: preserve transform_js and rate_limit on http_client tools (#563)

* fix: handle SIGUSR2 reloads in runner mode

* fix: preserve transform_js and rate_limit on http_client tools from ai_mcp_servers

When http_client tools were extracted from ai_mcp_servers config, the
CustomToolDefinition was constructed with only a subset of fields, dropping
transform_js and rate_limit. This meant the MCP server's transform_js
application code never fired because tool.transform_js was always undefined.

This caused disqualified candidates to appear in Workable API list responses
despite the workable-api tool having a transform_js filter configured.

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>

---------

Co-authored-by: Claude Opus 4.6 <noreply@anthropic.com>

Author: buger

src/providers/ai-check-provider.ts

@@ -1507,6 +1507,13 @@ export class AICheckProvider extends CheckProvider {
             auth: entry.config.auth as CustomToolDefinition['auth'],
             headers: entry.config.headers as Record<string, string>,
             timeout: (entry.config.timeout as number) || 30000,
+            // Preserve transform_js and rate_limit from the original tool config
+            ...(entry.config.transform_js
+              ? { transform_js: entry.config.transform_js as string }
+              : {}),
+            ...(entry.config.rate_limit
+              ? { rate_limit: entry.config.rate_limit as CustomToolDefinition['rate_limit'] }
+              : {}),
             inputSchema: {
               type: 'object',
               properties: {