Follow up nemoclaw debug for first-class macOS support #546

Summary

Follow up nemoclaw debug for first-class macOS support.

Motivation

The current nemoclaw debug implementation is Linux-first. It does run on macOS, but several collectors either:

• are missing and get skipped
• exist but behave differently from GNU/Linux
• produce noisy or low-value failures

That makes the command usable-but-rough on macOS rather than clearly supported.

Compatibility Snapshot

Based on the current nemoclaw debug implementation reviewed in PR #502:

Works well on macOS

• date
• uname -a
• uptime
• df -h
• docker ps -a
• docker stats --no-stream
• docker info
• docker system df
• lsof -i -P -n
• curl / nslookup

Partially works or is noisy on macOS

• ps -eo ... --sort=... | head -30
• top -b -n 1 | head -50
• dmesg | tail -100
• /etc/resolv.conf
• OpenShell diagnostics, depending on local install state

Missing or Linux-specific on macOS

• free -m
• ss -ltnp
• ip addr
• ip route
• vmstat 1 5 is different enough to deserve explicit handling
• iostat -xz 1 5 uses Linux flags that do not match macOS
• sandbox-internal commands that assume Linux userland inside the target environment

Requirements

Platform detection

• Detect macOS explicitly
• Prefer macOS-native collectors when Linux-specific commands are unavailable or incompatible

Collector substitutions

• Replace free -m with a macOS-appropriate memory summary
• Replace ss/ip addr/ip route with macOS-native network inspection
• Replace Linux-only top/iostat flags with macOS-compatible equivalents
• Handle dmesg restrictions gracefully on modern macOS without treating them as surprising failures

Output quality

• Reduce noisy failures for expected macOS limitations
• Keep the final report obviously useful rather than looking partially broken

Additional work

• Add a macOS validation path to tests or release validation
• Run the updated command on a real macOS host and confirm the output is mostly green/useful

Participants

• @cv
• @kjw3