GeezerVison

Summary

• Fixes [BUG] http_request / webhook_request report a successful HTTP 200 as failed when the JSON body has top-level status and data keys #9838: http_request and webhook_request reported a 200 as failed when the JSON body had top-level status and data keys (JSend-style {"status":"success","data":{...}})
• Root cause: transformResponse in both tools still sniffed the body for the envelope the old /api/proxy route returned ({success,status,data,headers}). That route was removed in improvement(files): update execution for passing base64 strings #2906, so the branch only ever matched third-party bodies, returning success: undefined, the body's status string instead of the HTTP code, and empty headers
• Removed the branch from both tools; every response now goes through the normal path (success: response.ok, real status and headers). Non-2xx is still rejected earlier in executeTool
• Behavior change: a 200 body shaped {success: true, status, data} was previously unwrapped (<api.data> was the inner data). It now returns the full body like every other response, so such references move to <api.data.data>

Type of Change

• Bug fix

Testing

• Added a regression test in tools/index.test.ts that runs both real tools through executeTool (the file's mocked registry stubs http_request, which is why existing tests missed this). Red on the pre-fix code, green after
• bunx vitest run tools/index.test.ts tools/http executor/handlers/api (278 passed), biome, check:test-patterns, check:comment-hygiene; full gate in CI

Checklist

• Code follows project style guidelines
• Self-reviewed my changes
• Tests added/updated and passing (new tests pass the test-audit authoring gate)
• No new warnings introduced
• I confirm that I have read and agree to the terms outlined in the Contributor License Agreement (CLA)