/voice shows 'No speech detected' on Linux x86_64 (v2.18.0) - voice subcommand missing from kiro-cli-chat binary. The TUI frontend spawns 'kiro-cli voice --ptt' but the Rust binary does not have the voice subcommand compiled in for the Linux .deb build. Mi

### 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 7.0.0-29-generic - Ubuntu 26.04 LTS

### Expected behaviour

The kiro-cli / kiro-cli-chat binary on Linux should include the voice subcommand (whisper-rs/cpal compiled in), so that /voice and Space push-to-talk work the same as on macOS. When a working microphone is detected and the user speaks,
the transcription should return text instead of silently returning empty.

### Actual behaviour

/voice always returns "No speech detected" regardless of microphone input. The TUI spawns kiro-cli voice --ptt but the binary exits immediately with empty stdout because the voice subcommand is not recognized (error: unrecognized
subcommand 'voice'). The TUI interprets empty text as no speech. Microphone is functional (verified via arecord with RMS/peak analysis showing valid audio capture).

### Steps to reproduce

**1. Install kiro-cli v2.18.0 on Linux x86_64 (.deb package, Ubuntu 26.04)

2. Ensure KIRO_ENABLED_FEATURES includes "voice"
3. Start kiro-cli chat
4. Type /voice and speak into a working microphone
5. Observe "No speech detected" every time
6. Verify with kiro-cli-chat voice --help → shows "unrecognized subcommand 'voice'"**

### Environment

```yaml

[q-details]
version = "2.18.0"
hash = "9f8f25f3acae5def920c2dd06e192d5cf941426c"
date = "2026-08-11T23:50:55.274384Z (2d ago)"
variant = "full"

[system-info]
chip = "11th Gen Intel(R) Core(TM) i5-1145G7 @ 2.60GHz"
total-cores = 4
memory = "22.12 GB"

[system-info.os.linux]
kernel_version = "7.0.0-29-generic"
id = "ubuntu"
name = "Ubuntu"
pretty_name = "Ubuntu 26.04 LTS"
version_id = "26.04"
version = "26.04 LTS (Resolute Raccoon)"

[environment]
cwd = "/home/USER"
cli-path = "/home/USER"
os = "Linux"
shell-path = "/usr/bin/bash"
install-method = "unknown"

[env-vars]
DISPLAY = ":0"
GTK_IM_MODULE = "ibus"
PATH = "/home/USER/.local/go/bin:/home/USER/.atuin/bin:/home/USER/.cargo/bin:/home/USER/.bun/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/usr/local/games:/snap/bin:/snap/bin:/home/USER/.local/bin:/bin:/home/USER/.npm-global/bin"
QT_IM_MODULE = "ibus"
Q_SET_PARENT_CHECK = "1"
SHELL = "/bin/bash"
TERM = "xterm-256color"
XDG_CURRENT_DESKTOP = "ubuntu:GNOME"
XDG_SESSION_DESKTOP = "ubuntu"
XDG_SESSION_TYPE = "wayland"
XMODIFIERS = "@im=ibus"
```

Start with the Rust kiro-cli-chat/kiro-cli voice entry point and the Linux .deb build configuration; verify whether the voice feature is compiled when KIRO_ENABLED_FEATURES includes voice. Run kiro-cli-chat voice --help and reproduce /voice with a working microphone; done means the voice subcommand is recognized and speech produces transcription text instead of "No speech detected".

Written by the indexing model from the issue text.