[Ubuntu 26.04][CLI&UX] status --json exits nonzero instead of reporting route drift fields

## Description

When the live shared inference route drifts from the route recorded for a sandbox, the JSON status command exits nonzero instead of returning the documented route drift fields. This prevents automation from reading `recordedRoute`, `liveRoute`, and `routeDrift` from `status --json`.

Platform scope: Reproduced on Ubuntu 26.04 GPU validation only; other platforms were not proven for this failure.

## Environment

```text
Device: Ubuntu 26.04 GPU validation runner
OS: Ubuntu 26.04
Architecture: x86_64
Docker: Available in sandbox-capable test job
NemoClaw: Product build under test from current NemoClaw validation pipeline
```

## Steps to Reproduce

1. Create or use a NemoClaw sandbox with an initially recorded shared inference route.
2. Change the live shared inference route externally so it no longer matches the sandbox-recorded route.
3. Run the sandbox status command with JSON output enabled.
4. Parse the command exit code and JSON payload.

## Expected Result

The command exits successfully and returns JSON containing `recordedRoute`, `liveRoute`, and `routeDrift` so automation can detect and report the mismatch.

## Actual Result

The status command exits nonzero after the shared route is changed, so the expected JSON route drift fields are not available to the caller.

```text
AssertionError: expected command exit code 1 to be +0
Context: status --json after external shared route change
```

## Logs

Not captured beyond the assertion excerpt above.