Kiro is tracking messages typed in my linux shell, not chat

### 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 6.17.0-12-generic - Ubuntu 25.10

### Expected behaviour

No terminal commands logged

### Actual behaviour

I open a terminal and type any command, echo, ls, cd, etc. I find them in the `history` table of `~/.local/share/kiro-cli/data.sqlite3`

### Steps to reproduce

_No response_

### Environment

```yaml
my bash_profile is:
# Kiro CLI pre block. Keep at the top of this file.
[[ -f "${HOME}/.local/share/kiro-cli/shell/bash_profile.pre.bash" ]] && builtin source "${HOME}/.local/share/kiro-cli/shell/bash_profile.pre.bash"

# Kiro CLI post block. Keep at the bottom of this file.
[[ -f "${HOME}/.local/share/kiro-cli/shell/bash_profile.post.bash" ]] && builtin source "${HOME}/.local/share/kiro-cli/shell/bash_profile.post.bash"
```

Beginne damit, die im Bericht referenzierten Dateien bash_profile.pre.bash und bash_profile.post.bash zu untersuchen. Prüfe anschließend, wie Terminaleingaben ~/.local/share/kiro-cli/data.sqlite3 und dessen history-Tabelle erreichen. Reproduziere das Problem mit Befehlen wie echo, ls und cd und überprüfe, dass Shell-Befehle dort nicht mehr aufgezeichnet werden, während Chatnachrichten weiterhin funktionieren.

Vom Indexierungsmodell aus dem Issue-Text verfasst.