continuing chat sessions that are initiated with piped input

### Checks

- [x] I have searched [github.com/aws/amazon-q-developer-cli/issues](https://github.com/aws/amazon-q-developer-cli/issues?q=) and there are no duplicates of my issue
- [x] I have run `q doctor` in the affected terminal session
- [x] I have run `q restart` and replicated the issue again

### Operating system

Linux 5.10.234-205.895.amzn2int.x86_64 - Amazon Linux 2

### Expected behaviour

the chat session should continue

### Actual behaviour

the chat session ends before I can reply or say "yes" to the proposed action

### Steps to reproduce

`cat ./lib/stacks/workflowStack.ts | q chat "can you help me, with the context i just added"`

### Environment

```yaml
[q-details]
version = "1.7.0"
hash = "8885a6708f2f07d02d29460a96f9c422da095e49"
date = "2025-03-06T01:03:21.313384Z (6d ago)"
variant = "minimal"

[system-info]
chip = "AMD EPYC 7R13 Processor"
total-cores = 16
memory = "123.22 GB"

[system-info.os.linux]
kernel_version = "5.10.234-205.895.amzn2int.x86_64"
id = "amzn"
name = "Amazon Linux"
pretty_name = "Amazon Linux 2"
version_id = "2"
version = "2"
variant = "internal"

[environment]
cwd = "/local/home/USER"
cli-path = "/local/home/USER"
os = "Linux"
shell-path = "/local/home/USER/.toolbox/tools/toolbox/1.1.1726.0/toolbox-exec"
shell-version = "5.8"
install-method = "toolbox"
in-ssh = true

[env-vars]
PATH = '/home/USER/.toolbox/bin:/home/USER/.toolbox/bin:/home/linuxbrew/.linuxbrew/bin:/home/linuxbrew/.linuxbrew/sbin:/apollo/env/envImprovement/bin:/home/USER/.cargo/bin:/usr/local/bin:/usr/bin:/home/USER/bin:/usr/local/sbin:/usr/sbin:/home/USER/.local/bin:/home/USER/bin:/usr/local/bin/mwinit:/home/USER/.toolbox/bin:/home/USER/CoolScripts:/home/USER/dotnet:/Applications/Visual\ Studio\ Code.app/Contents/Resources/app/bin:/home/linuxbrew/.linuxbrew/bin'
SHELL = "/bin/zsh"
TERM = "xterm-256color"
```

Comienza reproduciendo `cat ./lib/stacks/workflowStack.ts | q chat "can you help me, with the context i just added"` en el entorno Linux reportado y, a continuación, sigue el punto de entrada de `q chat` que gestiona la entrada canalizada. Se considera terminado cuando una sesión iniciada con contexto canalizado permanece abierta para que el usuario pueda responder o confirmar las acciones propuestas.

Escrito por el modelo de indexación a partir del texto del issue.