Windows: aborted bash tool call can leave a dangling tool_use without tool_result and corrupt the session #21489

{
  "type": "tool",
  "tool": "bash",
  "callID": "toolu_bdrk_01BWmoT2NYtjBp4BSo72YRN3",
  "state": {
    "status": "error",
    "input": {},
    "raw": "",
    "error": "Tool execution aborted"
  }
}

### Plugins

None / no third-party plugins involved. Reproduced with built-in tools.

### OpenCode version

1.4.0

### Steps to reproduce

1. Start an OpenCode session on Windows Desktop with an Anthropic Claude model.
2. Ask the assistant to run a long inline shell command through the bash tool, especially a long `python -c "..."` or `powershell.exe -Command` command with embedded script text.
3. Let the assistant continue in the same session after the tool attempt fails or gets interrupted.
4. Observe that one tool record may become `Tool execution aborted` with empty `input` and empty `raw`.
5. Continue the same conversation.
6. Eventually the session can become invalid and fail with an error like: `tool_use ids were found without tool_result blocks immediately after`.

Note: I do not have a minimal deterministic repro yet, but this has happened multiple times in real sessions on Windows when the model emits long inline bash commands.

### Screenshot and/or share link

<img width="1131" height="1092" alt="Image" src="https://github.com/user-attachments/assets/c0caca8d-e51b-4f84-a510-b78529e04ab8" />

### Operating System

Windows11

### Terminal

Windows  Desktop