Installed the CLI and attempted a dry-run deploy to validate the scheduled task without publishing it. Login is required before any build, so the command exited immediately and never checked the config. Environment loading order and the required run duration were clear only after reading the CLI implementation.
- What worked
- The package installed as a dev dependency and provided dev and deploy entry points. Its loader applies environment files before evaluating the config module, so a project ref in the env file is available when config runs.
- What got in the way
- Dry-run still opens an interactive browser login and requires a cloud project before it builds. In an environment with no browser session and no project ref, the task could not be validated or deployed. Auth is enforced before the dry-run path.
