fix(cli): stop error tracking user cancels at interactive prompts

[posthog-eu]

Summary

Problem

• Pressing Ctrl+C or Escape at an interactive prompt (for example the Enter your API key: prompt of capgo login) threw a plain Error.
• The top-level handler routed it through shouldCapturePosthogException() and shipped it to error tracking as an $exception, opening a bogus issue that recurs across many CLI users.
• The person who cancelled also saw a misleading Error: … cancelled line for doing exactly what they intended.

Changes

• Throw CliUserError on every isCancel() path — shouldCapturePosthogException() already skips that class, so cancels no longer reach error tracking.
• Downgrade the site message from log.error to log.warn: a user-initiated abort is not an error.
• index.ts no longer prints the redundant, alarming Error: … line for a CliUserError (the call site already printed a clear message).
• New shared uploadCancel() helper for the three cancel paths in bundle/upload.ts.

Swept isCancel() sites

File	Prompt cancelled
login.ts	API key
app/debug.ts	debug command
app/delete.ts	delete app
bundle/cleanup.ts	remove versions
bundle/upload.ts	version bump / builder CTA
build/request.ts	build platform
organization/add.ts, set.ts, delete.ts	org name / email / 2FA / password policy
utils.ts	org selection / Capacitor sync

Scope notes

• probe.ts and run/device.ts cancel with exit(1) (never throw), so they produce no $exception and are left unchanged.
• Kept the fix as a per-site sweep to match the sibling cleanups (fix(cli): stop error tracking the --fail-on-incompatible abort #2939, fix(cli): stop error-tracking noise from duplicate-version uploads #2934, fix(cli): stop error tracking minting a new issue per "not logged in" #2932); a cross-file shared cancel helper was considered but would thread a logger through 8 modules with differing log objects, widening the change.

Test plan

• bun run test:posthog-exception — extended to assert a cancel-shaped CliUserError is not captured.
• bun run typecheck, bun run lint, bun run test:build-platform-selection, bun run test:upload, bun run test:fail-on-incompatible all pass.
• Manual: run npx @capgo/cli login, press Ctrl+C at the prompt — a single Login cancelled warn line, clean exit, no $exception.

Screenshots

No UI change — CLI terminal output only (a warn line instead of an Error: line on cancel).

Checklist

• My code follows the code style of this project and passes bun run lint:backend && bun run lint.
• My change requires a change to the documentation.
• I have updated the documentation accordingly.
• My change has adequate E2E test coverage.
• I have tested my code manually, and I have provided steps how to reproduce my tests.

---

Created with PostHog Desktop from this inbox report.

---

^{Need help on this PR? Tag @codesmith-bot with what you need. Autofix is disabled.}

[codspeed-hq]

Merging this PR will not alter performance

✅ 43 untouched benchmarks
⏩ 2 skipped benchmarks¹

---

_{Comparing posthog-self-driving/fixcli-stop-error-tracking-ctrlc-at-the-fa045d (c1be61b) with main (e82dd01)}

Footnotes

1. 2 benchmarks were skipped, so the baseline results were used instead. If they were deleted from the codebase, click here and archive them to remove them from the performance reports. ↩

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud