📜 Description

Native (NDK) events no longer duplicate scope attachments.

When an attachment is added to the scope on the Java side, it is synced down to the native SDK via NdkScopeObserver. A native event captured through sentry_capture_event is then written to the outbox already carrying that attachment as its own envelope item. When OutboxSender re-ingests the cached envelope, it calls captureEvent with a hint that is both Cached and ApplyScopeData, so SentryClient re-applied the Java scope's attachments on top — sending each attachment twice.

The fix skips re-applying scope attachments when the event comes from a cached envelope (!HintUtils.hasType(hint, Cached.class)). The guard is intentionally narrow: it only gates addScopeAttachmentsToHint, leaving the rest of scope-data enrichment (contexts, tags, breadcrumbs, level, user) applied as before, which native crashes rely on.

💡 Motivation and Context

Fixes attachment duplication on native/NDK events.

• GH: Attachments duplication #5542
• Linear: JAVA-559

💚 How did you test it?

• Added a unit test in SentryClientTest asserting that a Cached + ApplyScopeData hint does not add scope attachments to the envelope.
• Reproduced manually in sentry-samples-android: tapping "Native Capture" with a scope attachment configured showed sentry.png twice before the fix and once after.

📝 Checklist

• I added GH Issue ID & Linear ID
• I added tests to verify the changes.
• No new PII added or SDK only sends newly added PII if sendDefaultPII is enabled.
• I updated the docs if needed.
• I updated the wizard if needed.
• Review from the native team if needed.
• No breaking change or entry added to the changelog.
• No breaking change for hybrid SDKs or communicated to hybrid SDKs.

🔮 Next steps

None.