refactor: simplify error handling and reporting

[angeloashmore]

Resolves:

Description

Reworks how the CLI turns a failure into what the user sees, what we track, and what we report. Previously the entrypoint caught every error in one long chain of instanceof branches that each repeated the same tracking boilerplate and only differed in the message printed. That kept message wording far from the code that raised the error and blurred the line between telemetry and crash reporting.

The intent behind the changes:

• Messages live on the errors. Each known error owns its user-facing message, so the top-level handler just prints it. A single lookup decides whether an error is known or unexpected.
• Reporting is split by purpose. Telemetry records the failure of every command, including its message. Crash reporting is limited to unexpected errors plus the few known API and Type Builder failures we still want eyes on. Each failure reports once.
• Observability is opt-in by flag. Telemetry and crash reporting sit behind explicit environment flags instead of implicit production checks, so their behavior is predictable everywhere.
• Crash reporting drops the Sentry SDK. We only used a small slice of it, so it now builds and sends the envelope directly and the dependency is gone.
• Clearer failure copy. Not-found messages name the missing resource, config errors point at prismic init, Type Builder errors link to the repository's settings, and secret token values are no longer echoed back. The sync watch loop surfaces the same contextual messages as one-off commands.

Command routing also moves out of the entrypoint into its own module, leaving the entrypoint focused on setup and failure handling.

No change to which commands succeed or fail; only to what users see and what we report when they do.

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

Medium Risk
Touches all command exit paths, Sentry reporting, and telemetry gating; behavior changes for which errors are reported and what users see, though success/failure semantics are intended to stay the same.

Overview
Centralizes CLI failure handling by moving the command router to src/commands/index.ts and replacing the entrypoint’s long instanceof chain with getErrorMessage, a KNOWN_ERRORS list, and user-facing copy on the error types themselves.

Splits observability: Segment telemetry is controlled via PRISMIC_TELEMETRY_ENABLED (and exported isTelemetryEnabled); Sentry only initializes when PRISMIC_SENTRY_ENABLED is set or telemetry is on in production. Crash reports go to Sentry for unexpected bugs and a small set of known API/Type Builder failures; command end events still record failures with the resolved message.

Replaces @sentry/node-core with a minimal Sentry envelope fetch in lib/sentry.ts, removing OpenTelemetry-related lockfile entries.

Improves messages across API clients (resource IDs in not-found text, operation-specific unknownErrorMessage), config/Type Builder (prismic init hints, settings URL), model errors, InvalidEnvironmentError, and the sync watch loop (same auth/API context as other commands). Invalid CLI args from parseArgs surface as CommandError.

^{Reviewed by Cursor Bugbot for commit f1d6e19. 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 using high effort and found 2 potential issues.

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

^{Reviewed by Cursor Bugbot for commit 6c5a504. Configure here.}

[lihbr]

*chef kiss* LGTM