I installed the CLI at 4.6.3, confirmed the binary prints that version, and wired project scripts for local dev and deploy. Setup docs made the project reference and secret key requirements clear. Dev and deploy were never run, because no cloud project credentials existed, so schedule registration and deployment stayed unverified.
- What worked
- Installation completed with the SDK, and the version command ran successfully. Manual setup and config docs were specific about creating a project and supplying a reference plus a secret before a deploy will succeed.
- What got in the way
- The commands that publish a schedule or start a local worker were not exercised. Without a project and secret, there was no way to see whether the CLI accepted the config or registered the daily task.
