fix(tools): surface HTTP status on error ToolResponse output

executeTool's catch handled Error instances in its first branch and only
extracted status/statusText/data for non-Error object throws — so HTTP errors
(thrown as Error instances carrying .status) lost their status on the returned
output. Surface it for Error instances too, so callers can branch on the
status (e.g. the enrichment cascade treating a provider 404 as a no-match).

Author: TheodoreSpeaks

apps/sim/tools/index.ts

@@ -1156,6 +1156,18 @@ export async function executeTool(
 
     if (error instanceof Error) {
       errorMessage = error.message || `Error executing tool ${toolId}`
+      // HTTP errors are thrown as Error instances carrying `status`/`statusText`/
+      // `data` (see createTransformedErrorFromErrorInfo). Surface them on the
+      // output so callers can branch on the status (e.g. treat 404 as a clean
+      // no-match) — the object branch below only ran for non-Error throws.
+      const httpStatus = (error as { status?: unknown }).status
+      if (typeof httpStatus === 'number') {
+        errorDetails = {
+          status: httpStatus,
+          statusText: (error as { statusText?: string }).statusText,
+          data: (error as { data?: unknown }).data,
+        }
+      }
     } else if (typeof error === 'string') {
       errorMessage = error
     } else if (error && typeof error === 'object') {