feat(sentry): error tracking, performance monitoring, and session replay

[Just-Insane]

Adds comprehensive Sentry error tracking, performance monitoring, and session replay to Sable.

Commits

1. feat(sentry): initialize Sentry SDK with environment-based sampling
Adds @sentry/react and wires instrument.ts into the app entry point. Environment-based sampling rates (production 10%, preview/dev 100%), full session replay with privacy masking, performance tracing, and data scrubbing for Matrix tokens and user IDs.

2. feat(sentry): developer settings panel and debug log attachment
Adds a SentrySettings panel under Developer Tools for manually capturing events, using the feedback widget, and controlling session replay. The debugLogger now attaches its buffered log buffer to Sentry events via breadcrumbs, extra data, and a file attachment for full diagnostic context on crash reports.

3. feat(sentry): crash page and bug report Sentry integration
DefaultErrorPage shows the Sentry event ID and offers one-click feedback submission. BugReportModal prefers the Sentry feedback dialog over GitHub issues when Sentry is configured. App.tsx wraps the router in a Sentry ErrorBoundary for automatic capture of unhandled React render errors.

4. feat(sentry): performance instrumentation across sync and messaging
Sentry spans and custom metrics across the critical paths: ClientRoot (user context via hashed MXID), ClientNonUIFeatures (push notifications), DirectDMsList (DM sync), RoomTimeline (jump-load and pagination latency with sable.timeline.jump_load_ms metric), RoomInput (message send with threading context), EncryptedContent (per-event decryption latency), matrix.ts/room.ts (Matrix API calls), slidingSync.ts (sync cycle spans).

5. docs(sentry): privacy information, integration guide, and CI environment configuration
Comprehensive docs/SENTRY_INTEGRATION.md covering setup, environment variables, sampling rates, privacy configuration, and self-hosting. CI workflows pass VITE_SENTRY_DSN and VITE_SENTRY_ENVIRONMENT to Cloudflare deploy and OpenTofu actions.

Setup

Sentry is opt-in: the integration is a no-op unless VITE_SENTRY_DSN is set at build time. Self-hosters who do not set this variable are unaffected.

Environment variable reference:

Variable	Required	Notes
VITE_SENTRY_DSN	Yes	Sentry project DSN
VITE_SENTRY_ENVIRONMENT	No	production (10% sampling) or preview (100%)

See docs/SENTRY_INTEGRATION.md for full details.

[github-actions]

OpenTofu plan for production

Plan: 2 to add, 0 to change, 2 to destroy.

OpenTofu used the selected providers to generate the following execution
plan. Resource actions are indicated with the following symbols:
-/+ destroy and then create replacement

OpenTofu will perform the following actions:

  # cloudflare_worker_version.site must be replaced
-/+ resource "cloudflare_worker_version" "site" {
!~      annotations         = {
+           workers_message      = (known after apply)
+           workers_tag          = (known after apply)
!~          workers_triggered_by = "create_version_api" -> (known after apply)
        } -> (known after apply)
!~      assets              = { # forces replacement
!~          asset_manifest_sha256 = "b44bbf6a507cd60278d078f529f5e4b4bfe36580139ecb1ff4fc842de520526f" -> "dabe9263bcfbd3acf488419df0f30df7f446fd96b3307ddca33789bb563681ce" # forces replacement
!~          directory             = "/home/runner/work/Sable/Sable/dist" -> "/github/workspace/dist"
#            (1 unchanged attribute hidden)
        }
+       compatibility_flags = (known after apply)
!~      created_on          = "2026-03-14T23:24:54Z" -> (known after apply)
!~      id                  = "************************************" -> (known after apply)
+       limits              = (known after apply)
+       main_script_base64  = (known after apply)
!~      number              = 112 -> (known after apply)
!~      source              = "terraform" -> (known after apply)
+       startup_time_ms     = (known after apply)
#        (4 unchanged attributes hidden)
    }

  # cloudflare_workers_deployment.site must be replaced
-/+ resource "cloudflare_workers_deployment" "site" {
!~      annotations  = { # forces replacement
!~          workers_message      = "b90555a27c7dac104a96bf0e2e5b66c2c815da2f" -> "feat(sentry): error tracking, performance monitoring, and session replay"
!~          workers_triggered_by = "deployment" -> (known after apply)
        }
!~      author_email = "cloudflare@sl.sable.moe" -> (known after apply)
!~      created_on   = "2026-03-14T23:24:55Z" -> (known after apply)
!~      id           = "************************************" -> (known after apply)
!~      source       = "terraform" -> (known after apply)
!~      versions     = [ # forces replacement
!~          {
!~              version_id = "************************************" -> (known after apply)
#                (1 unchanged attribute hidden)
            },
        ]
#        (3 unchanged attributes hidden)
    }

Plan: 2 to add, 0 to change, 2 to destroy.

Warning: Attribute Deprecated

  with cloudflare_workers_custom_domain.site,
  on main.tf line 41, in resource "cloudflare_workers_custom_domain" "site":
  41:   environment = "production"

This attribute is deprecated.

(and one more similar warning elsewhere)

📝 Plan generated in Cloudflare Infra #53

[github-actions]

Deploying with    Cloudflare Workers

Status	Preview URL	Commit	Alias	Updated (UTC)
✅ Deployment successful!	https://pr-280-sable.raspy-dream-bb1d.workers.dev	99ff314	pr-280	Sun, 15 Mar 2026 20:29:02 GMT