note: You are running `vp test` as a Vite+ built-in command. If you meant to run the test npm script, use `vpr test` instead.

 RUN  v5.0.5 /home/user/wt/pr-32583-evidence

stdout | packages/provider-cursor/src/server/adapter.evidence.test.ts > Cursor interrupted prompt evidence > R3 different native agent ignores the pending carry
ROW R3 send 1: R3 request A: write a dog story.

<runtime_info>In case you're asked: you are running in T3 Code through the Cursor harness. No need to mention this otherwise. You can embed images, video, and audio in your response using Markdown image syntax with absolute file paths. Link any other file you produce using its absolute path so the user can open it in T3 Code's files viewer.</runtime_info>

<pull_request_linking>
Link each PR you create, take over, or push to: link_pull_request, or link_pull_requests for several, full URL, every stack layer, as your next call. Host tools do not link for you. If linking fails, say so. Skip PRs you only read or review, and PRs named only as background. Call watch_pull_request when asked to monitor or babysit, or when work you were asked to do, such as a merge, still waits on checks or reviews, even after an earlier unwatch. Finish any needed branch update and push first, then watch and end your turn. Otherwise act now or hand back. Delegated children never watch, even if the brief says babysit. After PR work, a child's last line is: PR <full URL>, head <SHA>, checks and reviews <state>. Links and watches persist across pushes. For PR waits, no sleep, loops, gh --watch, Monitor or ScheduleWakeup. Before handback, call unwatch_pull_request on any PR you watch.
</pull_request_linking>
ROW R3 send 1 payload: {"agent":"native-agent-1","summarize":false,"accepted":true,"messageKind":"string","images":[]}

stdout | packages/provider-cursor/src/server/adapter.evidence.test.ts > Cursor interrupted prompt evidence > R3 different native agent ignores the pending carry
ROW R3 send 2: R3 request B: inspect the garden.

<runtime_info>In case you're asked: you are running in T3 Code through the Cursor harness. No need to mention this otherwise. You can embed images, video, and audio in your response using Markdown image syntax with absolute file paths. Link any other file you produce using its absolute path so the user can open it in T3 Code's files viewer.</runtime_info>

<pull_request_linking>
Link each PR you create, take over, or push to: link_pull_request, or link_pull_requests for several, full URL, every stack layer, as your next call. Host tools do not link for you. If linking fails, say so. Skip PRs you only read or review, and PRs named only as background. Call watch_pull_request when asked to monitor or babysit, or when work you were asked to do, such as a merge, still waits on checks or reviews, even after an earlier unwatch. Finish any needed branch update and push first, then watch and end your turn. Otherwise act now or hand back. Delegated children never watch, even if the brief says babysit. After PR work, a child's last line is: PR <full URL>, head <SHA>, checks and reviews <state>. Links and watches persist across pushes. For PR waits, no sleep, loops, gh --watch, Monitor or ScheduleWakeup. Before handback, call unwatch_pull_request on any PR you watch.
</pull_request_linking>
ROW R3 send 2 payload: {"agent":"native-agent-2","summarize":false,"accepted":true,"messageKind":"string","images":[]}

stdout | packages/provider-cursor/src/server/adapter.evidence.test.ts > Cursor interrupted prompt evidence > R4 compress sends no carry and preserves it for the next real message
ROW R4 send 1: R4 request A: write a dog story.

<runtime_info>In case you're asked: you are running in T3 Code through the Cursor harness. No need to mention this otherwise. You can embed images, video, and audio in your response using Markdown image syntax with absolute file paths. Link any other file you produce using its absolute path so the user can open it in T3 Code's files viewer.</runtime_info>

<pull_request_linking>
Link each PR you create, take over, or push to: link_pull_request, or link_pull_requests for several, full URL, every stack layer, as your next call. Host tools do not link for you. If linking fails, say so. Skip PRs you only read or review, and PRs named only as background. Call watch_pull_request when asked to monitor or babysit, or when work you were asked to do, such as a merge, still waits on checks or reviews, even after an earlier unwatch. Finish any needed branch update and push first, then watch and end your turn. Otherwise act now or hand back. Delegated children never watch, even if the brief says babysit. After PR work, a child's last line is: PR <full URL>, head <SHA>, checks and reviews <state>. Links and watches persist across pushes. For PR waits, no sleep, loops, gh --watch, Monitor or ScheduleWakeup. Before handback, call unwatch_pull_request on any PR you watch.
</pull_request_linking>
ROW R4 send 1 payload: {"agent":"native-agent-1","summarize":false,"accepted":true,"messageKind":"string","images":[]}

stdout | packages/provider-cursor/src/server/adapter.evidence.test.ts > Cursor interrupted prompt evidence > R4 compress sends no carry and preserves it for the next real message
ROW R4 send 2: /compress
ROW R4 send 2 payload: {"agent":"native-agent-1","summarize":true,"accepted":true,"messageKind":"string","images":[]}

stdout | packages/provider-cursor/src/server/adapter.evidence.test.ts > Cursor interrupted prompt evidence > R4 compress sends no carry and preserves it for the next real message
ROW R4 send 3: Your previous turn was interrupted and is missing from your history. Some of its work may already be done. Its request was:

R4 request A: write a dog story.

The new message, which may continue or change that request:

R4 request B: make the dog a pig.

<runtime_info>In case you're asked: you are running in T3 Code through the Cursor harness. No need to mention this otherwise. You can embed images, video, and audio in your response using Markdown image syntax with absolute file paths. Link any other file you produce using its absolute path so the user can open it in T3 Code's files viewer.</runtime_info>

<pull_request_linking>
Link each PR you create, take over, or push to: link_pull_request, or link_pull_requests for several, full URL, every stack layer, as your next call. Host tools do not link for you. If linking fails, say so. Skip PRs you only read or review, and PRs named only as background. Call watch_pull_request when asked to monitor or babysit, or when work you were asked to do, such as a merge, still waits on checks or reviews, even after an earlier unwatch. Finish any needed branch update and push first, then watch and end your turn. Otherwise act now or hand back. Delegated children never watch, even if the brief says babysit. After PR work, a child's last line is: PR <full URL>, head <SHA>, checks and reviews <state>. Links and watches persist across pushes. For PR waits, no sleep, loops, gh --watch, Monitor or ScheduleWakeup. Before handback, call unwatch_pull_request on any PR you watch.
</pull_request_linking>
ROW R4 send 3 payload: {"agent":"native-agent-1","summarize":false,"accepted":true,"messageKind":"string","images":[]}

stdout | packages/provider-cursor/src/server/adapter.evidence.test.ts > Cursor interrupted prompt evidence > R5 rejected send preserves carry for retry and successful completion clears it
ROW R5 send 1: R5 request A: write a dog story.

<runtime_info>In case you're asked: you are running in T3 Code through the Cursor harness. No need to mention this otherwise. You can embed images, video, and audio in your response using Markdown image syntax with absolute file paths. Link any other file you produce using its absolute path so the user can open it in T3 Code's files viewer.</runtime_info>

<pull_request_linking>
Link each PR you create, take over, or push to: link_pull_request, or link_pull_requests for several, full URL, every stack layer, as your next call. Host tools do not link for you. If linking fails, say so. Skip PRs you only read or review, and PRs named only as background. Call watch_pull_request when asked to monitor or babysit, or when work you were asked to do, such as a merge, still waits on checks or reviews, even after an earlier unwatch. Finish any needed branch update and push first, then watch and end your turn. Otherwise act now or hand back. Delegated children never watch, even if the brief says babysit. After PR work, a child's last line is: PR <full URL>, head <SHA>, checks and reviews <state>. Links and watches persist across pushes. For PR waits, no sleep, loops, gh --watch, Monitor or ScheduleWakeup. Before handback, call unwatch_pull_request on any PR you watch.
</pull_request_linking>
ROW R5 send 1 payload: {"agent":"native-agent-1","summarize":false,"accepted":true,"messageKind":"string","images":[]}

stdout | packages/provider-cursor/src/server/adapter.evidence.test.ts > Cursor interrupted prompt evidence > R5 rejected send preserves carry for retry and successful completion clears it
ROW R5 send 2: Your previous turn was interrupted and is missing from your history. Some of its work may already be done. Its request was:

R5 request A: write a dog story.

The new message, which may continue or change that request:

R5 request B: make the dog a pig.

<runtime_info>In case you're asked: you are running in T3 Code through the Cursor harness. No need to mention this otherwise. You can embed images, video, and audio in your response using Markdown image syntax with absolute file paths. Link any other file you produce using its absolute path so the user can open it in T3 Code's files viewer.</runtime_info>

<pull_request_linking>
Link each PR you create, take over, or push to: link_pull_request, or link_pull_requests for several, full URL, every stack layer, as your next call. Host tools do not link for you. If linking fails, say so. Skip PRs you only read or review, and PRs named only as background. Call watch_pull_request when asked to monitor or babysit, or when work you were asked to do, such as a merge, still waits on checks or reviews, even after an earlier unwatch. Finish any needed branch update and push first, then watch and end your turn. Otherwise act now or hand back. Delegated children never watch, even if the brief says babysit. After PR work, a child's last line is: PR <full URL>, head <SHA>, checks and reviews <state>. Links and watches persist across pushes. For PR waits, no sleep, loops, gh --watch, Monitor or ScheduleWakeup. Before handback, call unwatch_pull_request on any PR you watch.
</pull_request_linking>
ROW R5 send 2 payload: {"agent":"native-agent-1","summarize":false,"accepted":false,"messageKind":"string","images":[]}
ROW R5 send 3: Your previous turn was interrupted and is missing from your history. Some of its work may already be done. Its request was:

R5 request A: write a dog story.

The new message, which may continue or change that request:

R5 request B: make the dog a pig.

<runtime_info>In case you're asked: you are running in T3 Code through the Cursor harness. No need to mention this otherwise. You can embed images, video, and audio in your response using Markdown image syntax with absolute file paths. Link any other file you produce using its absolute path so the user can open it in T3 Code's files viewer.</runtime_info>

<pull_request_linking>
Link each PR you create, take over, or push to: link_pull_request, or link_pull_requests for several, full URL, every stack layer, as your next call. Host tools do not link for you. If linking fails, say so. Skip PRs you only read or review, and PRs named only as background. Call watch_pull_request when asked to monitor or babysit, or when work you were asked to do, such as a merge, still waits on checks or reviews, even after an earlier unwatch. Finish any needed branch update and push first, then watch and end your turn. Otherwise act now or hand back. Delegated children never watch, even if the brief says babysit. After PR work, a child's last line is: PR <full URL>, head <SHA>, checks and reviews <state>. Links and watches persist across pushes. For PR waits, no sleep, loops, gh --watch, Monitor or ScheduleWakeup. Before handback, call unwatch_pull_request on any PR you watch.
</pull_request_linking>
ROW R5 send 3 payload: {"agent":"native-agent-1","summarize":false,"accepted":true,"messageKind":"string","images":[]}

stdout | packages/provider-cursor/src/server/adapter.evidence.test.ts > Cursor interrupted prompt evidence > R5 rejected send preserves carry for retry and successful completion clears it
ROW R5 send 4: R5 request C: now write about a cow.

<runtime_info>In case you're asked: you are running in T3 Code through the Cursor harness. No need to mention this otherwise. You can embed images, video, and audio in your response using Markdown image syntax with absolute file paths. Link any other file you produce using its absolute path so the user can open it in T3 Code's files viewer.</runtime_info>

<pull_request_linking>
Link each PR you create, take over, or push to: link_pull_request, or link_pull_requests for several, full URL, every stack layer, as your next call. Host tools do not link for you. If linking fails, say so. Skip PRs you only read or review, and PRs named only as background. Call watch_pull_request when asked to monitor or babysit, or when work you were asked to do, such as a merge, still waits on checks or reviews, even after an earlier unwatch. Finish any needed branch update and push first, then watch and end your turn. Otherwise act now or hand back. Delegated children never watch, even if the brief says babysit. After PR work, a child's last line is: PR <full URL>, head <SHA>, checks and reviews <state>. Links and watches persist across pushes. For PR waits, no sleep, loops, gh --watch, Monitor or ScheduleWakeup. Before handback, call unwatch_pull_request on any PR you watch.
</pull_request_linking>
ROW R5 send 4 payload: {"agent":"native-agent-1","summarize":false,"accepted":true,"messageKind":"string","images":[]}

stdout | packages/provider-cursor/src/server/adapter.evidence.test.ts > Cursor interrupted prompt evidence > R6 repeated steers chain both earlier requests into the third send
ROW R6 send 1: R6 request A: write a dog story.

<runtime_info>In case you're asked: you are running in T3 Code through the Cursor harness. No need to mention this otherwise. You can embed images, video, and audio in your response using Markdown image syntax with absolute file paths. Link any other file you produce using its absolute path so the user can open it in T3 Code's files viewer.</runtime_info>

<pull_request_linking>
Link each PR you create, take over, or push to: link_pull_request, or link_pull_requests for several, full URL, every stack layer, as your next call. Host tools do not link for you. If linking fails, say so. Skip PRs you only read or review, and PRs named only as background. Call watch_pull_request when asked to monitor or babysit, or when work you were asked to do, such as a merge, still waits on checks or reviews, even after an earlier unwatch. Finish any needed branch update and push first, then watch and end your turn. Otherwise act now or hand back. Delegated children never watch, even if the brief says babysit. After PR work, a child's last line is: PR <full URL>, head <SHA>, checks and reviews <state>. Links and watches persist across pushes. For PR waits, no sleep, loops, gh --watch, Monitor or ScheduleWakeup. Before handback, call unwatch_pull_request on any PR you watch.
</pull_request_linking>
ROW R6 send 1 payload: {"agent":"native-agent-1","summarize":false,"accepted":true,"messageKind":"string","images":[]}

stdout | packages/provider-cursor/src/server/adapter.evidence.test.ts > Cursor interrupted prompt evidence > R6 repeated steers chain both earlier requests into the third send
ROW R6 send 2: Your previous turn was interrupted and is missing from your history. Some of its work may already be done. Its request was:

R6 request A: write a dog story.

The new message, which may continue or change that request:

R6 request B: make the dog a pig.

<runtime_info>In case you're asked: you are running in T3 Code through the Cursor harness. No need to mention this otherwise. You can embed images, video, and audio in your response using Markdown image syntax with absolute file paths. Link any other file you produce using its absolute path so the user can open it in T3 Code's files viewer.</runtime_info>

<pull_request_linking>
Link each PR you create, take over, or push to: link_pull_request, or link_pull_requests for several, full URL, every stack layer, as your next call. Host tools do not link for you. If linking fails, say so. Skip PRs you only read or review, and PRs named only as background. Call watch_pull_request when asked to monitor or babysit, or when work you were asked to do, such as a merge, still waits on checks or reviews, even after an earlier unwatch. Finish any needed branch update and push first, then watch and end your turn. Otherwise act now or hand back. Delegated children never watch, even if the brief says babysit. After PR work, a child's last line is: PR <full URL>, head <SHA>, checks and reviews <state>. Links and watches persist across pushes. For PR waits, no sleep, loops, gh --watch, Monitor or ScheduleWakeup. Before handback, call unwatch_pull_request on any PR you watch.
</pull_request_linking>
ROW R6 send 2 payload: {"agent":"native-agent-1","summarize":false,"accepted":true,"messageKind":"string","images":[]}

stdout | packages/provider-cursor/src/server/adapter.evidence.test.ts > Cursor interrupted prompt evidence > R6 repeated steers chain both earlier requests into the third send
ROW R6 send 3: Your previous turn was interrupted and is missing from your history. Some of its work may already be done. Its request was:

Your previous turn was interrupted and is missing from your history. Some of its work may already be done. Its request was:

R6 request A: write a dog story.

The new message, which may continue or change that request:

R6 request B: make the dog a pig.

The new message, which may continue or change that request:

R6 request C: put the pig on the moon.

<runtime_info>In case you're asked: you are running in T3 Code through the Cursor harness. No need to mention this otherwise. You can embed images, video, and audio in your response using Markdown image syntax with absolute file paths. Link any other file you produce using its absolute path so the user can open it in T3 Code's files viewer.</runtime_info>

<pull_request_linking>
Link each PR you create, take over, or push to: link_pull_request, or link_pull_requests for several, full URL, every stack layer, as your next call. Host tools do not link for you. If linking fails, say so. Skip PRs you only read or review, and PRs named only as background. Call watch_pull_request when asked to monitor or babysit, or when work you were asked to do, such as a merge, still waits on checks or reviews, even after an earlier unwatch. Finish any needed branch update and push first, then watch and end your turn. Otherwise act now or hand back. Delegated children never watch, even if the brief says babysit. After PR work, a child's last line is: PR <full URL>, head <SHA>, checks and reviews <state>. Links and watches persist across pushes. For PR waits, no sleep, loops, gh --watch, Monitor or ScheduleWakeup. Before handback, call unwatch_pull_request on any PR you watch.
</pull_request_linking>
ROW R6 send 3 payload: {"agent":"native-agent-1","summarize":false,"accepted":true,"messageKind":"string","images":[]}

stdout | packages/provider-cursor/src/server/adapter.evidence.test.ts > Cursor interrupted prompt evidence > R8 interrupted native images carry text and saved paths without resending image bytes
ROW R8 send 1: R8 request A: compare these two images.

[Attached image "first.png" is saved at: /tmp/lead-32583-r1/evidence-capture/20261110T124000Z/tmp/t3-provider-host-GSBsJy/userdata/attachments/evidence-image-first]

[Attached image "second.png" is saved at: /tmp/lead-32583-r1/evidence-capture/20261110T124000Z/tmp/t3-provider-host-GSBsJy/userdata/attachments/evidence-image-second]

<runtime_info>In case you're asked: you are running in T3 Code through the Cursor harness. No need to mention this otherwise. You can embed images, video, and audio in your response using Markdown image syntax with absolute file paths. Link any other file you produce using its absolute path so the user can open it in T3 Code's files viewer.</runtime_info>

<pull_request_linking>
Link each PR you create, take over, or push to: link_pull_request, or link_pull_requests for several, full URL, every stack layer, as your next call. Host tools do not link for you. If linking fails, say so. Skip PRs you only read or review, and PRs named only as background. Call watch_pull_request when asked to monitor or babysit, or when work you were asked to do, such as a merge, still waits on checks or reviews, even after an earlier unwatch. Finish any needed branch update and push first, then watch and end your turn. Otherwise act now or hand back. Delegated children never watch, even if the brief says babysit. After PR work, a child's last line is: PR <full URL>, head <SHA>, checks and reviews <state>. Links and watches persist across pushes. For PR waits, no sleep, loops, gh --watch, Monitor or ScheduleWakeup. Before handback, call unwatch_pull_request on any PR you watch.
</pull_request_linking>
ROW R8 send 1 payload: {"agent":"native-agent-1","summarize":false,"accepted":true,"messageKind":"native-images","images":[{"data":"iVBORw0KGgoAAAANSUhEUgAAAAEAAAABCAQAAAC1HAwCAAAAC0lEQVR42mP8/x8AAwMCAO+j1ioAAAAASUVORK5CYII=","mimeType":"image/png"},{"data":"iVBORw0KGgoAAAANSUhEUgAAAAEAAAABCAQAAAC1HAwCAAAAC0lEQVR42mP8/x8AAwMCAO+j1ioAAAAASUVORK5CYII=","mimeType":"image/png"}]}

stdout | packages/provider-cursor/src/server/adapter.evidence.test.ts > Cursor interrupted prompt evidence > R8 interrupted native images carry text and saved paths without resending image bytes
ROW R8 send 2: Your previous turn was interrupted and is missing from your history. Some of its work may already be done. Its request was:

R8 request A: compare these two images.

[Attached image "first.png" is saved at: /tmp/lead-32583-r1/evidence-capture/20261110T124000Z/tmp/t3-provider-host-GSBsJy/userdata/attachments/evidence-image-first]

[Attached image "second.png" is saved at: /tmp/lead-32583-r1/evidence-capture/20261110T124000Z/tmp/t3-provider-host-GSBsJy/userdata/attachments/evidence-image-second]

The new message, which may continue or change that request:

R8 request B: focus on the first image.

<runtime_info>In case you're asked: you are running in T3 Code through the Cursor harness. No need to mention this otherwise. You can embed images, video, and audio in your response using Markdown image syntax with absolute file paths. Link any other file you produce using its absolute path so the user can open it in T3 Code's files viewer.</runtime_info>

<pull_request_linking>
Link each PR you create, take over, or push to: link_pull_request, or link_pull_requests for several, full URL, every stack layer, as your next call. Host tools do not link for you. If linking fails, say so. Skip PRs you only read or review, and PRs named only as background. Call watch_pull_request when asked to monitor or babysit, or when work you were asked to do, such as a merge, still waits on checks or reviews, even after an earlier unwatch. Finish any needed branch update and push first, then watch and end your turn. Otherwise act now or hand back. Delegated children never watch, even if the brief says babysit. After PR work, a child's last line is: PR <full URL>, head <SHA>, checks and reviews <state>. Links and watches persist across pushes. For PR waits, no sleep, loops, gh --watch, Monitor or ScheduleWakeup. Before handback, call unwatch_pull_request on any PR you watch.
</pull_request_linking>
ROW R8 send 2 payload: {"agent":"native-agent-1","summarize":false,"accepted":true,"messageKind":"string","images":[]}

 ✓ |root| packages/provider-cursor/src/server/adapter.evidence.test.ts > Cursor interrupted prompt evidence > R3 different native agent ignores the pending carry 21ms
 ✓ |root| packages/provider-cursor/src/server/adapter.evidence.test.ts > Cursor interrupted prompt evidence > R4 compress sends no carry and preserves it for the next real message 5ms
 ✓ |root| packages/provider-cursor/src/server/adapter.evidence.test.ts > Cursor interrupted prompt evidence > R5 rejected send preserves carry for retry and successful completion clears it 6ms
 ✓ |root| packages/provider-cursor/src/server/adapter.evidence.test.ts > Cursor interrupted prompt evidence > R6 repeated steers chain both earlier requests into the third send 4ms
 ✓ |root| packages/provider-cursor/src/server/adapter.evidence.test.ts > Cursor interrupted prompt evidence > R8 interrupted native images carry text and saved paths without resending image bytes 6ms

 Test Files  1 passed (1)
      Tests  5 passed (5)
   Start at  13:56:36
   Duration  6.68s (transform 74%, setup 17%, import 8%, tests 1%)