Slash commands /chrome and /voice unreliable — inconsistent availability and silent failures

Description

Slash commands /chrome and /voice exhibit unreliable behavior:

• /chrome returns (no content) silently — no error, no feedback, just nothing
• /voice toggles on/off but availability is inconsistent across sessions
• Commands that fail silently give the user no indication of what went wrong or how to fix it

Expected behavior

• If a slash command is unavailable (missing dependency, unsupported platform, misconfigured), it should return a clear error message explaining why and how to fix it (e.g., "Chrome not found at expected path. Install Chrome or set CHROME_PATH.")
• If the command is available but fails at runtime, it should surface the underlying error rather than swallowing it
• /help or tab-completion should indicate which commands are available in the current environment vs. which are installed but non-functional

Environment

• Platform: Windows 11 Pro (win32)
• Shell: bash (Git Bash)

Suggested fix

1. Fail loudly: Every slash command handler should have a preflight check that validates dependencies are present before attempting execution. If the check fails, return a human-readable error.
2. Surface errors: Catch exceptions in command handlers and display them to the user instead of returning empty/silent results.
3. Availability indicators: Commands that require optional dependencies (Chrome, microphone access, etc.) should be marked as unavailable in help/tab-completion when their dependencies aren't met, rather than appearing available and then silently failing.

---

Filed by Skippy the Magnificent on behalf of a justifiably frustrated filthy monkey.