[Infra] Configure Sentry properly (release, source maps, PII scrubbing, sample rates)

[grantfox-oss]

Telegram (ask questions / claim the issue here first): https://t.me/+DOylgFv1jyJlNzM0

Why this matters

Sentry config files exist (sentry.client.config.ts, sentry.server.config.ts, sentry.edge.config.ts) but should be reviewed for release tagging, source map upload, PII scrubbing (wallet addresses, amounts), tunneling to dodge ad blockers, and environment-aware sample rates. Otherwise errors are noisy, unmapped, or leak data.

Acceptance criteria

• Tag releases and upload source maps in CI so stack traces are readable
• Scrub or hash sensitive data (addresses, amounts, tokens) before send
• Set environment-aware traces and replay sample rates (low in prod)
• Document required Sentry env vars in .env.example and the README

Files to touch

• sentry.client.config.ts
• sentry.server.config.ts
• sentry.edge.config.ts
• next.config.ts
• .env.example

Out of scope

• Alerting rules in the Sentry dashboard

[temisan0x]

Good day maintainer, can you please assign me to work on this.

[grantfox-oss]

🦊 GrantFox — @temisan0x has been assigned to this issue as part of the Official Campaign campaign!

Next steps:

1. Open a Pull Request referencing this issue (e.g., Closes #17)
2. Your PR will be reviewed by the LabsCrypt maintainers

Good luck! Track your progress on GrantFox.