Description

Description:
After curl|bash install completes onboarding and creates a new sandbox, the "Next:" completion message always shows the old default sandbox name from sandboxes.json instead of the sandbox name that was just created in the current session.

[Environment]
Device: macOS Apple Silicon (Apple M4, 24576 MB unified memory)
Node.js: v23.10.0
npm: 11.3.0
Docker: Colima 27.4.0
OpenShell CLI: 0.0.25
NemoClaw: v0.0.7 / v0.0.7.2 / v0.0.14 (reproduced on all three)
OpenClaw: 2026.4.2 (d74a122)

[Steps to Reproduce]

1. Have an existing NemoClaw installation with a default sandbox (e.g. lynn-abc)
2. Run: curl -fsSL https://www.nvidia.com/nemoclaw.sh | bash
3. Complete onboard wizard, create a new sandbox (e.g. abc-abc)
4. Observe the "Next:" section in the completion output

[Expected Result]
Next:
$ source /Users/lynnh/.zshrc
$ nemoclaw abc-abc connect <-- should show the sandbox created in this session
sandbox@abc-abc$ openclaw tui

[Actual Result] [INFO] === Installation complete ===

Next:
$ source /Users/lynnh/.zshrc
$ nemoclaw lynn-abc connect        <-- wrong: shows old default, not the sandbox just created
sandbox@lynn-abc$ openclaw tui

Running nemoclaw lynn-abc connect fails:
Sandbox 'lynn-abc' is not present in the live OpenShell gateway.
Removed stale local registry entry.
Root Cause:
The installer completion message reads the default sandbox name from the local registry (~/.nemoclaw/sandboxes.json) rather than using the sandbox name that was just created during the current onboard session. When the gateway has been rebuilt (e.g. after colima delete or version switch), the old default sandbox entry becomes stale but is still referenced in the completion message.

Bug Details

[NVB# 6072655]

[NVB#6072655]