What per‑event acknowledgment does the Sentry SDK provide for batch transmissions?

When the Sentry SDK sends a batch of error events over HTTP, it retries failed transmissions using exponential backoff and relies on the server‑side event ID for deduplication. However, the SDK does not expose per‑event acknowledgments, so developers cannot determine which individual events were accepted on the first attempt and which must be retried. This lack of granular feedback makes it difficult to reason about duplicate writes or to implement custom fallback logic.

What information does the Sentry SDK return to the client about the success or failure of each event in a batch transmission, and how can developers infer which events may have been duplicated when a retry occurs?