sentry-debug-bundle

# Sentry Debug Bundle ## Overview Collect SDK versions, configuration state, network connectivity, and event delivery status into a single diagnostic report. Attach the output to Sentry support tickets or use it to systematically isolate why events are not reaching the dashboard. ## Current State !`node --version 2>/dev/null || echo 'Node.js not found'` !`python3 --version 2>/dev/null || echo 'Python3 not found'` !`npm list @sentry/node @sentry/browser @sentry/react @sentry/cli 2>/dev/null | grep sentry || pip show sentry-sdk 2>/dev/null | grep -E '^(Name|Version)' || echo 'No Sentry SDK found'` !`sentry-cli --version 2>/dev/null || echo 'sentry-cli not installed'` !`sentry-cli info 2>/dev/null || echo 'sentry-cli not authenticated'` ## Prerequisites - At least one Sentry SDK installed (`@sentry/node`, `@sentry/browser`, `@sentry/react`, or `sentry-sdk` for Python) - `SENTRY_DSN` environment variable set (or DSN configured in application code) - For API checks: `SENTRY_AUTH_TOKEN` with `project:read` scope ([generate token](https://sentry.io/settings/auth-tokens/)) - Optional: `sentry-cli` installed for source map diagnostics and `send-event` tests ## Instructions ### Step 1 — Gather SDK Version, Configuration, and Init Hooks Identify the installed SDK, verify all `@sentry/*` packages share the same version (mismatches cause silent failures), and extract the runtime configuration. **Check installed packages:** ```bash # Node.js — list all Sentry packages and flag v...