fix: only send unknown or intentionally tracked errors to Segment

[angeloashmore]

Resolves: #131

Description

Previously, all errors were sent to Segment before being classified. Known/expected errors (user input mistakes, auth failures, missing config) added noise to analytics. Now only unknown errors and NoSupportedFrameworkError are tracked.

Checklist

• A comprehensive Linear ticket, providing sufficient context and details to facilitate the review of the PR, is linked to the PR.
• If my changes require tests, I added them.
• If my changes affect backward compatibility, it has been discussed.
• If my changes require an update to the CONTRIBUTING.md guide, I updated it.

Preview

How to QA ¹

---

Note

Low Risk
Small change to telemetry/error-reporting behavior in the CLI; main risk is reduced visibility or altered analytics for some known error cases.

Overview
Adjusts CLI error handling in src/index.ts so Segment telemetry only includes error details for unexpected failures (and NoSupportedFrameworkError), while other known/expected errors end the event without an error payload.

This reorders the catch branches to classify CommandError earlier and avoids attaching error metadata for common user-facing failures (e.g., missing/invalid config, not-found), while still reporting unknown errors to both Segment and Sentry.

^{Reviewed by Cursor Bugbot for commit 5b214b3. Bugbot is set up for automated code reviews on this repo. Configure here.}

Footnotes

1. Please use these labels when submitting a review:
   ❓ #ask: Ask a question.
   💡 #idea: Suggest an idea.
   ⚠️ #issue: Strongly suggest a change.
   🎉 #nice: Share a compliment. ↩

[cursor]

Cursor Bugbot has reviewed your changes and found 1 potential issue.

^{❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, enable autofix in the Cursor dashboard.}

^{Reviewed by Cursor Bugbot for commit 5b214b3. Configure here.}