docs: add Bugsnag configuration and documentation

Add environment variables for Bugsnag configuration and document
how to enable error reporting in README.

Author: morgan-wowk

.env.example

@@ -34,3 +34,22 @@ VITE_DEFAULT_REMOTE_COMPONENT_LIBRARY_BETA=<boolean>
 
 # Dev Tools
 VITE_ENABLE_DEBUG_MODE=<boolean>
+
+# =============================================================================
+# BUGSNAG ERROR REPORTING (OPTIONAL)
+# =============================================================================
+# Bugsnag error reporting is disabled by default. To enable, set your API key
+# below.
+
+# Required: Your Bugsnag API key
+# Get this from your Bugsnag project settings
+# VITE_BUGSNAG_API_KEY=
+
+# Optional: Custom endpoints (defaults to Bugsnag)
+# VITE_BUGSNAG_NOTIFY_ENDPOINT=https://notify.bugsnag.com
+# VITE_BUGSNAG_SESSIONS_ENDPOINT=https://sessions.bugsnag.com
+
+# Optional: Custom grouping key for metadata
+# If set, the normalized error message will also be added to metadata.custom[key]
+# Useful for integration with platforms that use custom grouping keys
+# VITE_BUGSNAG_CUSTOM_GROUPING_KEY=

README.md

@@ -54,6 +54,14 @@ If you find you are blocked by CORS, you will, for now, need to use the manual s
 
 If you complete these steps the app will launch on `127.0.0.1:8000` with the latest build you've created on the frontend.
 
+### Reporting errors to Bugsnag (Optional)
+
+To enable error reporting, add your API key to your `.env` file:
+
+```bash
+VITE_BUGSNAG_API_KEY=your-api-key
+```
+
 ## App features:
 
 - Build and edit pipelines using drag and drop visual editor