[Jetson][CLI&UX] channels status times out while Slack remains healthy

## Description

On NemoClaw v0.0.126 on Jetson AGX Thor, the documented awaitable Slack readiness command times out even though Slack Socket Mode is connected and the underlying OpenClaw channel status remains healthy throughout the wait.

Platform scope: Reproduced on Jetson AGX Thor only; other platforms were not tested for this exact healthy-but-timeout mismatch.

Regression: Unknown — #7383 introduced this readiness contract, but an earlier released version was not independently retested for this exact symptom.

OpenShell issue: No — the failing surface is the NemoClaw channel-readiness command, while the gateway and direct channel probe remain responsive.

## Environment

```text
Device: Jetson AGX Thor
OS: Linux 6.8.12-1021-tegra
Architecture: aarch64
Node.js: v22.23.2
npm: 10.9.8
Docker: Docker Engine 29.6.2
OpenShell CLI: 0.0.116
NemoClaw: v0.0.126
OpenClaw: 2026.7.1
```

## Steps to Reproduce

1. Install NemoClaw v0.0.126 on a Jetson AGX Thor.
2. Onboard an OpenClaw sandbox with valid Slack bot and app credentials.
3. Confirm the Slack preset is applied and start the channel.
4. Run:

```bash
nemoclaw {sandbox} channels status --channel slack --wait --timeout 180 --json
```

5. In parallel, observe the OpenClaw gateway channel status and Slack connection logs.

## Expected Result

The command reports the Slack channel as operational and exits successfully once registration, policy, runtime, Socket Mode, and account checks are healthy.

## Actual Result

The command polls 19 times for about 180 seconds, reports the runtime process as unreachable, and exits with a timeout:

```text
Runtime process: OpenClaw channel status is not reachable
readiness.state: timeout
last observed reason: status_probe_unreachable
```

During the same interval, Slack Socket Mode is connected, Slack auth probes succeed, and direct channel diagnostics report `connected=true` and `healthState=healthy`. Gateway logs show successful `channels.status` responses roughly every ten seconds.

## Logs

```text
[slack] socket mode connected
[ws] response succeeded: channels.status
account connected=true
account healthState=healthy

Awaitable command result:
state=timeout
attempts=19
reason=status_probe_unreachable
```

## Related

- #7383 defined the awaitable messaging-readiness contract.
- #8566 implemented that contract. The current released behavior does not satisfy it for this scenario.

Start with the `nemoclaw ... channels status --wait ...` entry point and trace the readiness contract described in #7383 and implemented in #8566. Compare its status probe with the gateway's successful `channels.status` responses and the direct Slack diagnostics. Done means a healthy Slack channel exits successfully instead of timing out on Jetson.

Written by the indexing model from the issue text.