feat(sidekiq): migrate to ActiveJob-first integration

[solnic]

Introduces Sidekiq's JobExtension and shared retry/reporting policies, and makes standalone Sidekiq instrumentation use the core producer/consumer helpers.

Routes ActiveJob jobs through Sentry's ActiveJob integration while preserving Sidekiq trace propagation, retry limits, error reporting, delivery metadata, and scope cleanup. Includes queue conformance, early-failure coverage, and separate processes for isolated specs.

[cursor]

Stale Bugbot comment from a previous run.

[cursor]

Stale Bugbot comment from a previous run.

[cursor]

Cursor Bugbot has reviewed your changes and found 2 potential issues.

^{❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, enable autofix in the Cursor dashboard.}

^{Reviewed by Cursor Bugbot for commit 6014ce1. Configure here.}

[cursor]

Shutdown reported as job failure

Medium Severity

The ActiveJob handoff ensure treats every unfinished exception as a job failure and sends it through ErrorHandler. That includes Sidekiq::Shutdown, which the standalone middleware never rescued (rescue is StandardError only) and which Sidekiq does not pass to error handlers. Stopping a worker can therefore record in-flight ActiveJob runs as errors.

Additional Locations (1)

• sentry-rails/lib/sentry/rails/active_job.rb#L185-L191

 

^{Reviewed by Cursor Bugbot for commit 6014ce1. Configure here.}

[cursor]

Isolated specs share one process

Medium Severity

spec:isolated runs each isolated example file through RSpec::Core::RakeTask in the current Ruby process. Those files are meant to be separate processes, but registrations, Rails boot, and Sidekiq configuration now leak between spec/isolated/active_job_spec.rb, spec/isolated/native_extension_spec.rb, and spec/isolated/rails_spec.rb.

 

^{Reviewed by Cursor Bugbot for commit 6014ce1. Configure here.}