#15306: fix: explicit exit after onboarding command completes

# Fix explicit exit after onboarding command completes ## Summary Add an explicit process exit after the [onboard](file://src/commands/onboard.ts#12-81) command finishes. This fixes an issue where the CLI process would hang indefinitely after completing the wizard, blocking automated setup scripts (like [docker-setup.sh](file://docker-setup.sh)) which wait for the CLI container to exit before starting the gateway service. ## Underlying Issue The [onboardCommand](file://src/commands/onboard.ts#12-81) logic completes successfully but leaves lingering event loop handles (e.g., active database connections or intervals), preventing the Node.js process from exiting naturally. ## Changes - **src/cli/program/register.onboard.ts**: Added `defaultRuntime.exit(0)` to the end of the [onboard](file://src/commands/onboard.ts#12-81) command handler. - This ensures the process terminates immediately upon successful completion of the wizard. - The exit call is placed in the CLI handler rather than the reusable [onboardCommand](file://src/commands/onboard.ts#12-81) function to avoid side effects when [onboardCommand](file://src/commands/onboard.ts#12-81) is used by other commands (like `openclaw setup`). ## Verification - Verified that [docker-setup.sh](file://docker-setup.sh) now proceeds correctly past the onboarding step and starts the `openclaw-gateway` service without hanging. - Verified that `openclaw setup` continues to work (as [onboardCommand](file://src/commands/onboard.ts#12-81) itself does not exit). <!-- greptile_comment --> <h2>Greptile Overview</h2> <h3>Greptile Summary</h3> Refactored CLI exit logic from command-specific handler to global entry point. Previously, `defaultRuntime.exit(0)` was called directly in the onboard command handler. Now, a `.then(() => { process.exit(0); })` is attached to `program.parseAsync()` in `src/index.ts`, ensuring all CLI commands exit cleanly after completion. This change maintains correct behavior for both short-lived commands (which complete and trigger the global exit) and long-running commands like `gateway run` (which manage their own lifecycle via signal handlers and never resolve parseAsync). <h3>Confidence Score: 5/5</h3> - This PR is safe to merge with minimal risk - The refactoring is a clean architectural improvement that centralizes CLI exit logic. The change correctly handles both short-lived commands (which complete and exit via the global handler) and long-running commands (which manage their own lifecycle). Test modifications confirm the new behavior is properly validated. The commit history shows this is an intentional evolution from a command-specific fix to a global solution. - No files require special attention _{Last reviewed commit: 24a927a} <!-- greptile_other_comments_section --> _{(3/5) Reply to the agent's comments like "Can you suggest a fix for this @greptileai?" or ask follow-up questions!} <!-- /greptile_comment -->