Description

NVB 6157307 (GitHub Issue #3233) asked for three commands.mdx flag-documentation gaps to be filled: nemoclaw onboard --fresh, nemoclaw onboard --yes / -y, and nemoclaw <name> connect --probe-only. Two of three were addressed in the v0.0.53 docs — --yes / -y and --probe-only now have synopsis entries plus dedicated explanation paragraphs. --fresh is still synopsis-only, with no explanation block under the ### nemoclaw onboard section. NVB 6157307 is closed-verified for the two fixed flags; this bug tracks the remaining --fresh documentation gap.

Environment

Device:        MacBook Pro (Apple M4)
OS:            macOS 26.x (Darwin 25.1.0, arm64)
Architecture:  arm64
Node.js:       v23.10.0
npm:           11.3.0
Docker:        29.2.1 (Colima)
OpenShell CLI: 0.0.44
NemoClaw:      v0.0.53
OpenClaw:      2026.5.22
Doc file:      docs/reference/commands.mdx (extension migrated .md to .mdx since the original report)

Steps to Reproduce

1. Open docs/reference/commands.mdx.

2. grep for --fresh and observe only three hits, all synopsis-style:

   $ grep -n "\-\-fresh" docs/reference/commands.mdx
   66:   $ nemoclaw onboard [--non-interactive] [--resume | --fresh] ...
   1098: ... `--non-interactive`, `--resume`, `--fresh`, ... (`nemoclaw setup` compat-alias flag list)
   1111: ... `--non-interactive`, `--resume`, `--fresh`, ... (`nemoclaw setup-spark` compat-alias flag list)

3. Confirm there is no explanatory sentence under the ### nemoclaw onboard section describing what --fresh does or how it contrasts with --resume.

4. Confirm that nemoclaw onboard --help has the description, so the gap is purely on the doc side.

Expected Result

commands.mdx ### nemoclaw onboard section should explain --fresh semantics. Suggested wording (one or two lines, similar to how --probe-only is explained at line 341):

--fresh ignores any saved onboarding session and restarts the wizard from scratch. Use this when a prior nemoclaw onboard aborted partway through and you want to discard the saved state rather than resume. Contrast with --resume, which continues an interrupted session.

Actual Result

--fresh appears only in the synopsis line and the two compat-alias flag enumerations. No standalone explanation paragraph. A user reading commands.mdx still cannot determine from the page alone what --fresh does.

Logs

Doc grep evidence on macOS v0.0.53 (2026-05-28):

$ grep -nE "\-\-fresh" /Users/lynnh/.nemoclaw/source/docs/reference/commands.mdx
66:$ nemoclaw onboard [--non-interactive] [--resume | --fresh] [--recreate-sandbox] ...
1098:This command remains as a compatibility alias to `nemoclaw onboard` ... `--non-interactive`, `--resume`, `--fresh`, ...
1111:This command remains as a compatibility alias to `nemoclaw onboard` ... `--non-interactive`, `--resume`, `--fresh`, ...

$ nemoclaw onboard --help | grep -A1 "\-\-fresh"
  --fresh                                  Ignore any saved onboarding session

Related

Follow-up of NVB 6157307 ([All Platforms][Docs][GitHub Issue #3233] commands.md missing documentation for nemoclaw onboard --fresh, --yes, and <name> connect --probe-only).

Original bug had 3 sub-issues; --yes / -y and --probe-only are documented in v0.0.53; --fresh (this bug) remains.

NVB#6235154