[macOS/Ubuntu 24.04][CLI&UX] Hermes TUI parity check exits before the response is rendered

## Description

The automated Hermes TUI-versus-CLI parity check can report missing TUI output even when the interactive client has not finished rendering the requested answer. The completion gate matches persistent status text and interrupts the session before the response is available.

Platform scope: Platform-specific: fails on macOS and Ubuntu 24.04; verified working on DGX Spark.

Regression: Unknown — earlier versions not tested.

## Environment

```text
Platform 1
Device: Apple Silicon Mac
OS: macOS 26.5 (Darwin 25.5.0)
Architecture: arm64
Node.js: v22.23.1
npm: 10.9.8
Docker Engine: 29.4.1
OpenShell: 0.0.85
NemoClaw: v0.0.102
Agent: NemoHermes

Platform 2
Device: Linux workstation
OS: Ubuntu 24.04, kernel 6.8.0-106-generic
Architecture: x86_64
Node.js: v22.22.3
npm: 10.9.8
Docker Engine: 29.4.0
OpenShell: 0.0.85
NemoClaw: v0.0.102
Agent: NemoHermes
```

## Steps to Reproduce

1. Install NemoClaw v0.0.102 and onboard a NemoHermes sandbox.
2. Run the non-interactive Hermes command with this prompt: `List 10 REST API endpoints for a blog service, one per line, using GET / POST / PUT / DELETE verbs.`
3. Confirm that the non-interactive command returns 10 endpoint lines.
4. Launch Hermes interactively and submit the same prompt.
5. In the automated session, wait 3 seconds, treat `connected`, `idle`, `ready`, or any HTTP verb as completion, and send Ctrl-C.
6. Compare the captured interactive output with the non-interactive output.

## Expected Result

The parity check waits for prompt-specific response content and captures the completed TUI answer before interrupting the session. The TUI and non-interactive CLI should both contain the requested endpoint lines.

## Actual Result

The completion condition matches persistent TUI status text before the answer is rendered, then the test sends Ctrl-C. On Ubuntu 24.04 the capture contains only a short progress message; on macOS it contains startup/status content. Both captures contain 0 endpoint verbs while the non-interactive CLI returns all 10 requested endpoints.

This is an automation false negative. The current evidence does not prove that NemoClaw truncates TUI responses.

## Logs

```text
step[2] sending the endpoint-list prompt
step[3] waiting 3000 ms
step[4] matched: connected|idle|ready|GET|POST|PUT|DELETE
step[5] sending Ctrl-C

Ubuntu 24.04 captured TUI text:
Confirming the gateway stays responsive (~25s)...

Ubuntu 24.04: TUI endpoint mentions: 0; CLI endpoint mentions: 10
macOS: TUI endpoint mentions: 0; CLI endpoint mentions: 10
```

---
[NVB#6563614](https://nvbugspro.nvidia.com/bug/6563614)