test: Verify Sentry SDK compatibility (JS + Python real-world validation)

[ajianaz]

What

Verify Sentry SDK compatibility claims by testing real Sentry SDKs (JavaScript + Python minimum) against TrapFall's ingest endpoint.

Why

BMAD CMO finding: TrapFall claims "drop-in DSN swap" but this has never been validated against real Sentry SDKs. If edge cases break (release health envelope, certain event types, breadcrumbs), trust dies on first use. This is the #1 adoption lever — it must work flawlessly.

Changes

1. Integration test suite:
   • JavaScript Sentry SDK (@sentry/node): capture exception, capture message, release health, performance transaction
   • Python Sentry SDK (sentry-sdk): capture exception, capture message, breadcrumbs
   • (Optional) Go Sentry SDK: basic capture
2. Test scenarios:
   • Simple exception capture → verify event appears in TrapFall
   • Message capture → verify
   • Release health envelope → verify release tracking
   • Performance transaction (spans) → verify tracing data
   • Attachments → verify attachment storage
   • Breadcrumbs → verify breadcrumb rendering
3. Document findings: What works, what doesn't, what needs fixing
4. Fix any incompatibilities found (create follow-up issues if major)
5. Create migration guide based on validated flow

Testing

This IS the testing task. Success = all core Sentry SDK features work without code changes beyond DSN URL swap.