🤖 tests: sendModeDropdown 'send after step' waits only 1 s for the stream to start #5807

tests/ui/chat/sendModeDropdown.test.ts › "send after step waits for every tool call emitted in the current step" failed in CI with "Expected the source turn to be streaming before queueing".

• Seen once: PR 🤖 fix: an edit keeps its text in memory, so the unsent draft survives a reload and stays out of other windows #5801 head 76c52aa, run 37537817431, job 112523650492 ("Test / Integration (1/3)"). The message appears twice in that job because jest prints its failure summary twice.
• The same test passed in CI on the next head (a0ca200), and the whole file passed 10 of 10 local runs on that head.
• A scan of the last 40 failed PR workflow runs found the message only in that job.

Likely cause (not proven): the waitFor for canInterrupt at sendModeDropdown.test.ts:207 sets no timeout, so it uses the testing-library default of 1000 ms. A sibling test waits for the same condition with { timeout: 30_000 } (around line 240). On a loaded runner the stream can take more than 1 s to start.

Fix idea: give that wait an explicit load-tolerant timeout, as the sibling test does.

The PR #5801 readiness check found that its changes cannot reach this path: the failing wait runs before any composer edit code, and the only send before it is a normal send.

Generated with xum • Model: anthropic:claude-opus-5-5 • Thinking: high • Cost: $33.65