Testing: Agent input request is not surface while session remains "Working"

Testing #335485

## Summary

An Agent Host session running in a Dev Container requested user input after encountering a terminal sandbox failure (see https://github.com/microsoft/vscode/issues/335755), but the Agents Window did not display the question.

Instead, the session remained visibly stuck in a **Working** state for several minutes.

## Environment

- VS Code: 1.138.0-insider
- OS: Bluefin 44, Linux
- Docker Engine: 29.7.2
- Repository: https://github.com/microsoft/vscode-remote-try-node
- Dev Container image: `mcr.microsoft.com/devcontainers/javascript-node:1-18-bullseye`

## Steps to Reproduce

1. Start a new Agent Host session for the Node.js Dev Container sample using **Dev Container**.
2. Ask the agent to modify files, run the application, verify it with `curl`, and commit the changes.
3. Allow a tool failure that causes the agent to call `ask_user`.
4. Observe the session in the Agents Window.

## Actual Behavior

At `2026-09-11T14:56:14.052Z`, the remote Agent Host emitted both:

- `chat/inputRequested`
- `session/inputNeededSet`

The requested question was:

> The sandbox's shell tool is completely non-functional here (missing Bubblewrap/bwrap runtime), so I can't run `node`, `curl`, or `git` commands at all — this blocks running the server, verifying with curl, and committing. I've already made the code and README changes. How would you like to proceed?

The Agents Window did not display this question. It continued showing **Working**, with its in-progress animation, for several minutes.

After cancelling the turn and running **Developer: Reload Window**, the previously hidden question appeared in the completed turn as a skipped question.

## Expected Behavior

When the remote Agent Host emits `chat/inputRequested` and `session/inputNeededSet`:

- The question should immediately appear in the Agents Window.
- The session should visibly transition to an input-needed state.
- The UI should not continue presenting the turn as actively working.

## Additional Information

The connection remained healthy throughout this period. The Dev Container was running, the in-container Agent Host process was alive, and protocol pings continued succeeding.

This was not a disconnected or crashed Agent Host—the UI failed to reflect the authoritative input-needed state.

## Screenshots

### Session stuck on Working

### State after reloading the window