Internal: JOB_RUNNER is not a secret, so it follows the rule for such settings: the live site decides it in config/production.php, and turning the job runner on or off is a commit and a push. The line is empty, so nothing changes until it is set to on.
While the committed line is empty, a JOB_RUNNER=on line in the server's .env still turns the job runner on, so the manual step "Turn on the job runner" still works as written.