[Ubuntu 22.04][Agent&Skills] OpenClaw TUI waits 120 seconds with no valid reply after successful onboard and Ready sandbox

> [!WARNING]
> **Regression** — GitHub issue #6194 covered the same "openclaw tui interactions timeout after connected idle" symptom on the same platforms and was verified fixed after v0.0.72. This report is the identical symptom recurring on v0.0.116; the exact version where it broke again has not been bisected.

## Description

CI-run OpenClaw TUI sends a prompt but receives no valid reply after waiting 120 seconds, even though install and sandbox-Ready both complete successfully in the same run.

**Platform scope:** Reproduced on Ubuntu 22.04; the identical symptom was also observed on Ubuntu 26.04 GPU in the same CI campaign (separate test run), so this is not isolated to one platform. Other platforms not tested.

## Environment

```text
Device: Not captured (CI automation runner)
OS: Ubuntu 22.04
Architecture: Not captured
Node.js: Not captured
npm: Not captured
Docker: Not captured
OpenShell CLI: Not captured
NemoClaw: v0.0.116
OpenClaw: Not captured
```

## Steps to Reproduce

1. Run automated NemoClaw v0.0.116 install and onboard on Ubuntu 22.04.
2. Confirm the sandbox reaches Ready phase.
3. Connect to the sandbox and launch OpenClaw TUI.
4. Send a prompt to the agent.

## Expected Result

The TUI returns a valid response within the configured timeout.

## Actual Result

The TUI waits 120 seconds with no valid reply. Install and sandbox-Ready both completed successfully in this run; the failure is isolated to the agent reply step (test run result: 6 passed, 1 failed, no hook failure).

## Logs

```text
Not captured
```

## Related

#6194 previously covered the same class of symptom (TUI hangs/no reply after reaching "connected idle") as a cross-platform systemic regression across all CI runners of the time, including the same Ubuntu 22.04 and Ubuntu 26.04 GPU platform pair, and was verified fixed after v0.0.72. This report is that same symptom recurring on v0.0.116.

Start by comparing this v0.0.116 failure with the previously fixed issue #6194, which reported the same OpenClaw TUI no-reply symptom. Reproduce the listed Ubuntu 22.04 install, onboard, Ready, connect, and prompt steps; the issue does not identify relevant files, tests, or captured logs. Done means determining why the agent reply times out and verifying a valid reply within the configured timeout.

Written by the indexing model from the issue text.