fix(cli): use shell-neutral env-var removal guidance

[mangeshraut712]

Summary

login status and the post-login warning printed POSIX unset OPENAI_API_KEY ..., which is invalid in PowerShell. Windows users following that hint cannot drop the environment API keys that shadow a ChatGPT sign-in.

Fixes #33.

Changes

• Added formatEnvironmentVariableRemovalGuidance() so the CLI prints shell-neutral wording (remove OPENAI_API_KEY and CODEX_API_KEY from the environment) instead of a POSIX command.
• Used that helper for the login status path and the post-login / access-token warning that lists whichever shadowing keys are actually set.

Testing

• bun test --timeout 30000 ./tests-ts/api-environment.test.ts ./tests-ts/cli-authentication.test.ts — 29 pass, 0 fail
• pnpm run lint (tsc --noEmit) — exit 0

Risk and rollout

Documentation-only user-facing strings. No auth, scan, or credential-handling behavior change. Existing CLI authentication tests now assert the shell-neutral text and that unset no longer appears.

Public disclosure review

• No customer, partner, prospect, or user identities, data, or identifying details are included.
• No credentials, personal data, private source, scan findings, or nonpublic links or tickets are included.
• I reviewed the branch name, title, description, commits, changes, comments, logs, screenshots, attachments, and links for public disclosure.

[chatgpt-codex-connector]

Note

You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard.