add-error-tracking

# Add Error Tracking Integrate Temps error tracking (Sentry-compatible) into an application. The Temps DSN is a drop-in replacement for a Sentry DSN — use the official Sentry SDK for the user's platform and point it at the Temps DSN via an environment variable. ## Prefer Sentry's official per-framework skills when available Temps is Sentry wire-compatible, so every skill Sentry publishes for their SDKs works against a Temps DSN. If the user's CLI already has one of these installed, route them to it and only substitute the DSN: | User's platform | Sentry skill | Source | |---|---|---| | Next.js | `/sentry-nextjs-sdk` | `getsentry/sentry-for-ai` | | React (Vite, Remix, etc.) | `/sentry-react-sdk` | `getsentry/sentry-for-ai` | | Vanilla browser JS | `/sentry-browser-sdk` | `getsentry/sentry-for-ai` | | Node.js | `/sentry-node-sdk` | `getsentry/sentry-for-ai` | | React Native | `/sentry-react-native-sdk` | `getsentry/sentry-for-ai` | | Generic (language-agnostic) | `/sentry-sdk-setup` | `getsentry/sentry-for-ai` | For platforms Sentry has no dedicated skill for (Vue, Svelte, Angular, Python, Go, Rust, Ruby, Java, PHP, .NET, Flutter, etc.), follow the setup in this file directly. **Always set the DSN from an environment variable — never hardcode it.** The user will point the env var at their Temps DSN instead of a Sentry DSN. ## Detect the platform Infer the platform from the codebase: - `package.json` with `"next"` → **Next.js** → `@sentry/nextjs` - `package.json` with `...