WA-RAILS7-023: Error reporting API migration

[kitcommerce]

Summary

Rails 7.1 introduced new error reporting API (Rails.error.report). Workarea may be using older exception notification patterns.

Approach

1. Audit current error handling (Bugsnag? Sentry? Custom?)
2. Evaluate Rails 7.1 error reporting API
3. Decide: adopt new API or keep current pattern
4. Document decision

Objective

Clear strategy for error reporting on Rails 7.1+.

Client Impact

Optional. Existing error handling continues to work.

Acceptance Criteria

• Current error handling documented
• Rails 7.1 error reporting API evaluated
• Decision made and documented
• If adopting: integration PR opened
• If not: rationale documented

Verification Plan

Error handling smoke test (raise exception, verify reported).

[kitcommerce]

I audited Workarea's error handling patterns and found that core Workarea does not bundle an error reporting provider (Sentry/Bugsnag/etc.). Instead, it relies on the host app (and/or optional plugins like workarea-sentry) plus standard Rack/Rails exception handling. Storefront error pages also set request.env['rack.exception'] in ErrorsController#internal so middleware can observe exceptions.

Rails 7.1 adds Rails.error.report (ActiveSupport::ErrorReporter) for reporting handled exceptions.

Decision: adopt Rails.error.report as an additive/opt-in hook.

PR opened: #758

• Adds Workarea::ErrorReporting.report wrapper (no-op when Rails.error.report is unavailable)
• Uses it to report a few handled/swallowed exceptions (homebase/rubygems network calls and fraud analyzer)
• Documents rationale in docs/rails7-migration-patterns/error-reporting.md

Client impact: optional; existing error handling remains unchanged.

[kitcommerce]

Merged via PR #758.