fix: guard interactive startup without tty

[TinyTb]

Problem

During initial setup, Hermes could offer to start the setup/chat flow even when it did not have a usable interactive TTY. In that state, the prompt_toolkit CLI could print the welcome/goodbye text and then crash with a traceback like:

KeyError: '0 is not registered'
...
OSError: [Errno 22] Invalid argument

This happens because the interactive CLI tries to attach an asyncio reader to stdin fd 0, but fd 0 is not a selectable terminal in non-interactive contexts. The resulting traceback is confusing for new users and makes setup look broken.

There was also a README post-install example that led with source ~/.bashrc, even though macOS users on the default zsh shell need source ~/.zshrc.

Summary

• fail early with a clear error when interactive hermes/hermes chat is launched without a TTY, while preserving hermes chat -q for non-interactive use
• skip the legacy setup script's "run setup wizard now" prompt when stdin is not interactive, instead telling users to run hermes setup later
• update README post-install instructions to show zsh/macOS and bash shell reload commands separately

Test Plan

• /Users/hermes/.hermes/hermes-agent/venv/bin/python -m pytest tests/hermes_cli/test_setup_noninteractive.py tests/hermes_cli/test_setup_hermes_script.py -q
• /Users/hermes/.hermes/hermes-agent/venv/bin/python -m py_compile hermes_cli/main.py hermes_cli/setup.py
• bash -n setup-hermes.sh

[alt-glitch]

Related to #8641 (root issue) — competing with open PRs #8420 and #8842 which implement the same TTY guard.

[alt-glitch]

Related to #8641 (root issue) — competing with open PRs #8420 and #8842 which implement the same TTY guard.

[teknium1]

Thanks for addressing the no-TTY startup path. A configured classic chat still reaches cli.main() without an early TTY gate on current head (hermes_cli/main.py:2404-2430), while the legacy developer setup script still prompts unconditionally (setup-hermes.sh:455-461).

Problems

• The proposed guard checks only args.query (hermes_cli/main.py:1270 in this PR). That would reject --image with no TTY, although current main treats an image as a non-interactive single-query input (hermes_cli/_parser.py:272; hermes_cli/main.py:12560).
• The first-run setup portion is already covered: current main exits with non-interactive guidance before prompting (hermes_cli/main.py:2327-2331), and commit 256bedb632ece7b9142a20f4e830f5a5fe48ad5f removed post-setup chat relaunching.

Suggested changes

• Salvage the direct guard against current cmd_chat(), exempting both query and image single-query modes, and add a no-TTY image regression test.
• Keep the setup-script and README changes scoped to the legacy contributor path.

Automated hermes-sweeper review.

[teknium1]

--image is also a single-query input: current dispatch uses not query and not image to identify an interactive prompt (hermes_cli/main.py:12560). Please exempt args.image here as well and add a no-TTY image-path regression test; otherwise this guard rejects a supported headless single-query mode.