Explicit --checkout/--no-checkout beats OPENFN_NO_CHECKOUT_AFTER_DEPLOY

[midigofrank]

Short Description

An explicit --checkout or --no-checkout on project deploy now overrides OPENFN_NO_CHECKOUT_AFTER_DEPLOY. The env var only sets the default.

Fixes OFN-4763

Implementation Details

• Root cause: checkout had a yargs default: true, so ensure() couldn't tell an explicit --checkout from the default and set checkout = false whenever the env var was 'true'.
• Removed the yargs default; ensure() resolves the value from the env var only when the flag wasn't passed.

QA Notes

• New deploy-options.test.ts (5 cases, parsing the real command through yargs): env=true + --checkout failed before the fix; the rest lock in existing behaviour.
• --help no longer shows [default: true] for --checkout; the description still says checkout is the default.

AI Usage

• I have used Claude Code
• I have used another model
• I have not used AI