Summary

• Send structured frontend exception reports with source, label, error type, stack, top frame, view, build metadata, and bounded breadcrumbs.
• Capture Go-side panics into a pending crash report and flush them on the next launch when desktop telemetry is enabled.
• Add client-side and Worker-side redaction for home-directory paths, emails, bearer/API keys, JWTs, and long token-like strings before reports are sent or stored.
• Expand the crash-report Worker dashboard with source/severity/version/platform metadata, filters, regression reopening, retained first sample plus latest samples, and structured sample details.
• Generate hidden frontend source maps and move them out of dist into an ignored desktop/frontend/sourcemaps/<commit>/ directory for private symbolication.

Required production deployment order

This PR changes the live D1 schema. A maintainer with access to the Cloudflare account that owns the reasonix-crash D1 database and reasonix-crash-report Worker should run the migration before deploying the matching Worker.

1. Back up or snapshot the production D1 database reasonix-crash.
2. Apply the one-time migration:

cd workers/crash-report
npx wrangler d1 execute reasonix-crash --remote --file=migrate-structured-reports.sql

3. Deploy the Worker after the migration succeeds:

cd workers/crash-report
npm run typecheck
npm run deploy

4. Release the desktop app after the Worker is deployed.

Important: do not run schema.sql against the existing production database as the upgrade path. schema.sql is for fresh databases; existing production needs migrate-structured-reports.sql. Running the new Worker before the migration can make crash report inserts fail because the new columns do not exist yet.

Verification

• go test ./... from desktop
• pnpm typecheck from desktop/frontend
• pnpm test from desktop/frontend
• pnpm build from desktop/frontend
• npm run typecheck from workers/crash-report
• git diff --check
• Confirmed desktop/frontend/dist contains no .map files after build