Fix test isolation: use sendAndWait in blob/attachment tests

The blob and file attachment tests used session.send() (fire-and-forget)
then immediately disconnected. The pending CAPI request leaked into
subsequent tests via the shared CLI process, causing the vision test's
proxy to receive mismatched requests. Use sendAndWait to ensure the
CLI finishes processing before the test completes.

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>

Author: SteveSandersonMS

nodejs/test/e2e/session_config.test.ts

@@ -46,7 +46,7 @@ describe("Session Configuration", async () => {
     it("should accept blob attachments", async () => {
         const session = await client.createSession({ onPermissionRequest: approveAll });
 
-        await session.send({
+        await session.sendAndWait({
             prompt: "Describe this image",
             attachments: [
                 {
@@ -58,7 +58,6 @@ describe("Session Configuration", async () => {
             ],
         });
 
-        // Just verify send doesn't throw — blob attachment support varies by runtime
         await session.disconnect();
     });
 
@@ -67,12 +66,11 @@ describe("Session Configuration", async () => {
 
         const session = await client.createSession({ onPermissionRequest: approveAll });
 
-        await session.send({
+        await session.sendAndWait({
             prompt: "Summarize the attached file",
             attachments: [{ type: "file", path: join(workDir, "attached.txt") }],
         });
 
-        // Just verify send doesn't throw — attachment support varies by runtime
         await session.disconnect();
     });
 

test/snapshots/session_config/should_accept_blob_attachments.yaml

@@ -5,4 +5,100 @@ conversations:
       - role: system
         content: ${system}
       - role: user
-        content: Describe this image
+        content: |-
+          Describe this image
+          test-pixel.png
+          [image]
+      - role: assistant
+        content: I'll view the image for you.
+      - role: assistant
+        tool_calls:
+          - id: toolcall_0
+            type: function
+            function:
+              name: report_intent
+              arguments: '{"intent":"Viewing image file"}'
+      - role: assistant
+        tool_calls:
+          - id: toolcall_1
+            type: function
+            function:
+              name: view
+              arguments: '{"path":"${workdir}/test-pixel.png"}'
+  - messages:
+      - role: system
+        content: ${system}
+      - role: user
+        content: |-
+          Describe this image
+          test-pixel.png
+          [image]
+      - role: assistant
+        content: I'll view the image for you.
+        tool_calls:
+          - id: toolcall_0
+            type: function
+            function:
+              name: report_intent
+              arguments: '{"intent":"Viewing image file"}'
+          - id: toolcall_1
+            type: function
+            function:
+              name: view
+              arguments: '{"path":"${workdir}/test-pixel.png"}'
+      - role: tool
+        tool_call_id: toolcall_0
+        content: Intent logged
+      - role: tool
+        tool_call_id: toolcall_1
+        content: Path ${workdir}/test-pixel.png does not exist. Please provide a valid path.
+      - role: assistant
+        content: Let me check the current directory to locate the image file.
+      - role: assistant
+        tool_calls:
+          - id: toolcall_2
+            type: function
+            function:
+              name: ${shell}
+              arguments: '{"command":"Get-ChildItem -Recurse -Filter \"test-pixel.png\"","description":"Find test-pixel.png file"}'
+  - messages:
+      - role: system
+        content: ${system}
+      - role: user
+        content: |-
+          Describe this image
+          test-pixel.png
+          [image]
+      - role: assistant
+        content: I'll view the image for you.
+        tool_calls:
+          - id: toolcall_0
+            type: function
+            function:
+              name: report_intent
+              arguments: '{"intent":"Viewing image file"}'
+          - id: toolcall_1
+            type: function
+            function:
+              name: view
+              arguments: '{"path":"${workdir}/test-pixel.png"}'
+      - role: tool
+        tool_call_id: toolcall_0
+        content: Intent logged
+      - role: tool
+        tool_call_id: toolcall_1
+        content: Path ${workdir}/test-pixel.png does not exist. Please provide a valid path.
+      - role: assistant
+        content: Let me check the current directory to locate the image file.
+        tool_calls:
+          - id: toolcall_2
+            type: function
+            function:
+              name: ${shell}
+              arguments: '{"command":"Get-ChildItem -Recurse -Filter \"test-pixel.png\"","description":"Find test-pixel.png file"}'
+      - role: tool
+        tool_call_id: toolcall_2
+        content: <exited with exit code 0>
+      - role: assistant
+        content: The file doesn't appear to be in the working directory. Could you please upload or provide the image file
+          again? I'll be happy to describe it once I can access it.

test/snapshots/session_config/should_accept_message_attachments.yaml

@@ -13,3 +13,53 @@ conversations:
           <tagged_files>
           * ${workdir}/attached.txt (1 lines)
           </tagged_files>
+      - role: assistant
+        content: I'll read the attached file and summarize it for you.
+      - role: assistant
+        tool_calls:
+          - id: toolcall_0
+            type: function
+            function:
+              name: report_intent
+              arguments: '{"intent":"Reading attached file"}'
+      - role: assistant
+        tool_calls:
+          - id: toolcall_1
+            type: function
+            function:
+              name: view
+              arguments: '{"path":"${workdir}/attached.txt"}'
+  - messages:
+      - role: system
+        content: ${system}
+      - role: user
+        content: |-
+          Summarize the attached file
+
+
+
+          <tagged_files>
+          * ${workdir}/attached.txt (1 lines)
+          </tagged_files>
+      - role: assistant
+        content: I'll read the attached file and summarize it for you.
+        tool_calls:
+          - id: toolcall_0
+            type: function
+            function:
+              name: report_intent
+              arguments: '{"intent":"Reading attached file"}'
+          - id: toolcall_1
+            type: function
+            function:
+              name: view
+              arguments: '{"path":"${workdir}/attached.txt"}'
+      - role: tool
+        tool_call_id: toolcall_0
+        content: Intent logged
+      - role: tool
+        tool_call_id: toolcall_1
+        content: 1. This file is attached
+      - role: assistant
+        content: The attached file contains a single line of text that simply states "This file is attached" - it's a minimal
+          test file confirming its attachment status.