docs(crons): Add rufus-scheduler setup for Ruby

platform-includes/crons/setup/ruby.mdx

@@ -56,6 +56,43 @@ sentry_monitor_check_ins monitor_config: Sentry::Cron::MonitorConfig.from_interv
 sentry_monitor_check_ins monitor_config: Sentry::Cron::MonitorConfig.from_crontab('5 * * * *')
 ```
 
+### rufus-scheduler
+
+<Alert>
+
+The rufus-scheduler integration ships in the next release of `sentry-ruby`.
+
+</Alert>
+
+If you're using `rufus-scheduler`, enable the `:rufus_scheduler` patch to capture check-ins for `cron`, `every`, and `interval` jobs:
+
+```rb
+Sentry.init do |config|
+  config.enabled_patches += [:rufus_scheduler]
+end
+```
+
+```rb
+scheduler = Rufus::Scheduler.new
+
+scheduler.cron '0 9 * * 1-5', name: 'daily-report' do
+  # do stuff
+end
+
+scheduler.every '10m', name: 'sync-accounts' do
+  # do stuff
+end
+
+# skip a job
+scheduler.every '1m', sentry_monitor: false do
+  # do stuff
+end
+```
+
+The monitor slug comes from the job's `name` option, or from the handler's class or method name when you pass one instead of a block. Blocks without a `name` aren't monitored, so set `name` on every block you want to monitor.
+
+Sentry creates the monitor from `cron` jobs and from `every` jobs whose frequency is a whole number of minutes, hours, or days. `interval` jobs wait a fixed time after each run ends, so they don't have a fixed schedule. For those, and for cron lines Sentry can't read the same way (for example `L`, `#`, or sub-minute seconds), the SDK sends check-ins without a monitor config, and you need to create the monitor in Sentry with the same slug. The same applies when the job's time zone is an offset like `+05:30` rather than an IANA name like `Europe/Vienna`. One-off `in` and `at` jobs are not monitored, and jobs scheduled by `sidekiq-scheduler` are left to the `:sidekiq_scheduler` patch.
+
 ## Manual Setup
 
 If you're using `Clockwork` or `Whenever`, you'll need to instrument your jobs