Add Sentry.io error monitoring to main map and 19hz map

[Copilot]

Adds Sentry Browser SDK to both maps as a single project, using Sentry environment to differentiate between the two endpoints rather than separate projects/DSNs.

Changes

• index.html / 19hz/index.html — load @sentry/browser@8 from jsDelivr CDN; initialize with __SENTRY_DSN__ placeholder and environment: 'funcheapsf' / environment: '19hz' respectively
• deploy.yml — adds SENTRY_DSN to the env block and a sed injection step alongside the existing token replacements
• preview.yml — adds SENTRY_DSN to the env block and a sed injection step so PR preview deployments also have Sentry active
• .env.example — documents the new SENTRY_DSN variable

<script src="https://cdn.jsdelivr.net/npm/@sentry/browser@8/build/bundle.min.js" crossorigin="anonymous"></script>
<script>
  Sentry.init({ dsn: '__SENTRY_DSN__', environment: 'funcheapsf' })
</script>

Set the SENTRY_DSN repo secret (Settings → Secrets → Actions) to the DSN from your Sentry project's Client Keys page. Environments (funcheapsf, 19hz) are created automatically on first error ingestion.

[ProLoser]

@copilot use <script src="https://js.sentry-cdn.com/b1a545ff725524609a522423481f37ad.min.js" crossorigin="anonymous"></script> and update preview.yml

[Copilot]

@copilot use <script src="https://js.sentry-cdn.com/b1a545ff725524609a522423481f37ad.min.js" crossorigin="anonymous"></script> and update preview.yml

preview.yml updated in 6b29765 — it now injects SENTRY_DSN into both HTML files on PR previews, matching deploy.yml.

Your comment appears to have had a URL/reference between "use" and "and update preview.yml" that got stripped — could you clarify what you'd like me to switch to? (e.g. a specific CDN, the Sentry Loader Script, etc.)

[github-actions]

PR Preview Action v1.8.1
Preview removed because the pull request was closed.
2026-04-19 20:46 UTC