smart-notes: handle response-stream error on body-limit destroy

request.destroy(err) destroys the response stream with the same error;
the request-level 'error' handler rejects the promise but the response
side had no listener, so every body-limit / timeout / abort destroy also
surfaced as an uncaught stream error on stderr.

Co-authored-by: Alfonso [Magic Context] <288211368+alfonso-magic-context@users.noreply.github.com>

Author: ualtinok

packages/plugin/src/features/magic-context/smart-notes/ssrf-guard.ts

@@ -238,6 +238,13 @@ function requestValidatedAddress(
                     }
                     chunks.push(buf);
                 });
+                // request.destroy(err) (body limit, timeout, abort) also destroys
+                // this response stream with the same error. Without a listener,
+                // that becomes an UNCAUGHT stream 'error' dumped to stderr — the
+                // request-level handler alone does not cover the response side.
+                response.on("error", (error) => {
+                    reject(toNetworkError(error, "response failed"));
+                });
                 response.on("end", () => {
                     const status = response.statusCode ?? 0;
                     if (status >= 500) {