Eric Traut b7fec54354 Queue follow-up input during user shell commands (#18820) ...

Fixes #17954.

## Why
When a manual shell command like `!sleep 10` is running, submitting
plain text such as `hi` currently sends that text as a steer for the
active shell turn. User shell turns are not steerable like model turns,
so the TUI can remain stuck in `Working` after the shell command
finishes.

## What Changed
- Detect when the only active work is one or more
`ExecCommandSource::UserShell` commands.
- Queue plain submitted input in that state so it drains after the shell
command and shell turn complete.
- Preserve `!cmd` submissions during running work so explicit shell
commands keep their existing behavior.
- Add regression coverage for the `!sleep 10` plus `hi` flow in
`chatwidget::tests::exec_flow::user_message_during_user_shell_command_is_queued_not_steered`.

## Verification
- Manually confirmed hang before the fix and no hang after the fix

2026-04-21 10:13:13 -07:00

..

frames

Rename tui_app_server to tui (#16104)

2026-03-28 11:23:07 -06:00

src

Queue follow-up input during user shell commands (#18820)

2026-04-21 10:13:13 -07:00

tests

Stabilize Bazel tests (timeout tweaks and flake fixes) (#17791)

2026-04-16 07:57:51 -07:00

BUILD.bazel

bazel: use native rust test sharding (#18082)

2026-04-17 23:14:11 +00:00

Cargo.toml

Remove simple TUI legacy_core reexports (#18631)

2026-04-20 10:48:27 -07:00

prompt_for_init_command.md

Rename tui_app_server to tui (#16104)

2026-03-28 11:23:07 -06:00

styles.md

Rename tui_app_server to tui (#16104)

2026-03-28 11:23:07 -06:00

tooltips.txt

Add /side conversations (#18190)

2026-04-19 11:59:41 -07:00