CI-only CLI failures usually expose local assumptions

A CI debugging note about checking working directory, shell, runtime versions, config files, and secret availability before changing code.

When a CLI command works locally but fails in CI, I try to print the working directory, runtime versions, package manager version, shell, and config file paths before touching product code. Local machines hide global packages, cached files, personal profiles, and .env assumptions. CI failures often look like code bugs, but the fix is frequently a pinned version, explicit working directory, or clearer setup step.