feat: add Scripts — run arbitrary parameterized code from the UI

[rogercampos]

What

A second vertical alongside backfills: Scripts — arbitrary one-shot parameterized code, written in the host app, triggered from the DataDrip UI.

# app/scripts/backfill_company_timezones.rb
class BackfillCompanyTimezones < DataDrip::Script
  description "Recomputes the timezone of a company from its address."

  input :company_id, :integer, required: true
  input :mode, :enum, values: %w[fast thorough], required: true
  input :dry_run, :boolean, default: true

  def call
    log "Recomputing timezone for company #{company_id}..."
    # ...
  end
end

How it works

• Typed input DSL: input name, type, default:, required: — the form at /data_drip/script_runs/new is auto-generated from the declarations, values are coerced server-side via ActiveModel types, and required inputs are validated before the run is created (required booleans accept false but not missing — inclusion validation, not presence).
• Permanent history: every run is recorded in the new data_drip_script_runs table — who ran it, inputs, full log output, error message + backtrace, status, and created/start/started/finished timestamps. Runs are only deletable while still enqueued.
• Execution: a single ScriptRunner job (configurable DataDrip.script_queue_name) runs #call once. Scripts emit output through a log API that persists timestamped lines immediately (update_column appends — no $stdout redirection, which is unsafe in multithreaded workers) and streams them live to the show page via a polling Stimulus controller.
• Hooks: on_script_run_* lifecycle callbacks with the same class-first / global-handler precedence as backfills.

Shared machinery (Backfill behavior unchanged)

• DataDrip::SchematizedOptions — extracted typed-options DSL now backing both Backfill.attribute and Script.input, adding required: support.
• DataDrip::BackfillerContext — shared controller concern for backfiller/timezone resolution.
• The option-form helper is parametrized by field prefix; the existing helper spec (asserting exact backfill field names) guards that backfill form output is byte-identical.
• Shared sidebar partial with Backfills / Scripts navigation.

One deliberate improvement over the backfill form: on validation errors the script form re-renders input fields server-side with submitted values kept sticky.

Generators / upgrade path

• rails g data_drip:script MyScript (supports --sorbet)
• Fresh installs: data_drip:install now also creates app/scripts + the migration
• Existing installs: rails g data_drip:install_scripts

Testing

• Full suite: 162 examples, 0 failures; RuboCop clean.
• ~60 new examples covering the DSL (types, coercion, defaults, required incl. the boolean gotcha), model validations/enqueueing/hooks, job success/failure/output capture, controller (tabs, sticky re-render, updates JSON, destroy rules, AJAX inputs endpoint) and helpers.
• Smoke-tested in the dummy app (bin/dev): script picker, generated form, live output streaming and failure display.

Notes

• Datetime inputs get no user-timezone conversion (parity with backfill options); only the top-level "start at" is converted.
• If the host base_job_class retries, a failed script re-runs from scratch — README documents scripts should be idempotent or hosts should discard_on.
• This branch includes main's local dev-tooling commit (bin/dev + bootable dummy app); that commit will drop out of the diff once main is pushed.

🤖 Generated with Claude Code