[2026 DevOps] Tag Sentry releases, upload source maps and add an error-budget view

[Nanle-code]

Objective

Make production errors readable and link them to releases.

Target area

Sentry setup, vite.config.js, release workflow

Context

@sentry/react is installed, but minified stack traces are useless without uploaded source maps and release tagging, and there's no agreed error budget.

Acceptance criteria

• The release workflow creates a Sentry release, uploads hidden source maps, and does not serve maps publicly.
• Events carry release, environment and network tags, and are scrubbed with the [2026 Security] Redact secrets and signed XDR from diagnostics #774 redaction rules.
• Document an error-budget SLO (e.g. crash-free sessions) with a dashboard link.
• Telemetry respects the consent flow ([2026 Security] Add privacy-preserving telemetry consent renewal prompts #834).
• Automated tests cover the primary flow, at least one boundary case, and at least one failure case.
• User-facing documentation or developer guidance is updated, including compatibility, security, or migration notes where applicable.

Pull request requirements

• All continuous integration checks must pass before a pull request may be merged.
• The branch must be free of merge conflicts with the target branch at the time of merge.
• Do not request merge with failing workflows, skipped required checks, or unresolved conflicts.

[drips-wave]

@Nanle-code This issue could not be added to the Stellar Wave Program because the per-repo points budget would be exceeded (25000 / 25000 points already used). The label has been automatically removed.

The budget resets at the end of each Wave. You can review the remaining budget for your repos on the Orgs & Repos page.

ℹ️ Learn more about points budgets