Changed

• If the "command" entry of the JSON job provided is empty, the runner now considers this a no-op job and exits early (before attempting to install dependencies or run pre/post scripts), with the message "Command is empty; nothing to run" and a success status. (Previously, it would emit the help message and exit with an error status; the change allows sending an empty job if there are no jobs to run, bypassing any setup.)