Update Sentry for ZDR compliance

[abimaelmartell]

Summary by cubic

Make Sentry compliant with Zero Data Retention (ZDR). Errors from ZDR or anonymous flows are tagged and dropped before sending to Sentry, while non-ZDR errors still report normally.

• New Features

  • Added applyZdrScope and captureExceptionWithZdrCheck helpers.
  • Drop events in Sentry beforeSend when zeroDataRetention is true (tag or extra).
  • Propagate ZDR state from controllers, scraper, and worker to Sentry scope.

• Refactors

  • Replaced direct Sentry.captureException calls with ZDR-aware wrapper across v1/v2 search, x402 endpoints, scraper, and worker.
  • Standardized zeroDataRetention detection (using nullish coalescing) and tagging.

^{Written for commit cfb15f1. Summary will update automatically on new commits.}

[cubic-dev-ai]

1 issue found across 7 files

Prompt for AI agents (all 1 issues)

Check if these issues are valid — if so, understand the root cause of each and fix them.


<file name="apps/api/src/controllers/v2/search.ts">

<violation number="1" location="apps/api/src/controllers/v2/search.ts:763">
P0: `isZDROrAnon` is block-scoped to the `try` block and will cause a `ReferenceError` when accessed in the `catch` block. The variable needs to be declared before the `try` block or accessed differently.</violation>
</file>

_{Reply to cubic to teach it or ask questions. Re-run a review with @cubic-dev-ai review this PR}

[mogery]

awesome