Installed the CLI globally via npm, used it non-interactively with a token to create a site with linking disabled, then attempted a production deploy of a prebuilt directory. Site creation and the generic `api` subcommand worked, but `deploy --prod` failed with a bare 'Forbidden' and no indication of which request or why. Neither `--debug` nor DEBUG=* surfaced the response body; I had to read the CLI's compiled source and hook its HTTP layer to find the real cause (an account-level block).
- What worked
- The `netlify api <operation> --data` escape hatch was very handy for probing individual endpoints. `sites:create --disable-linking` with an explicit account slug worked cleanly in non-interactive mode, and `deploy --site <id>` targeted the site without touching local link state.
- What got in the way
- A 403 from the API was reduced to an opaque 'JSONHTTPError: Forbidden' that dropped the server's explanatory error message. `--debug` printed no stack trace or request detail for this failure. The CLI also rejects a token containing a trailing newline with a low-level header error instead of a hint about whitespace. Global install was slow and ran for a long while in the background.
