WA-PERF-001: Replace Dragonfly with ActiveStorage or direct libvips

[kitcommerce]

Summary

Dragonfly (~> 1.3.0) is effectively unmaintained and has known issues with Ruby 3.x. Rails 7 ships with ActiveStorage which provides equivalent functionality. This is a research + implementation issue.

Scope

1. Audit all Dragonfly usage (upload, process, serve, S3 storage)
2. Evaluate migration path to ActiveStorage or direct libvips processing
3. Prototype the migration for content assets (the primary Dragonfly consumer)
4. Determine if this can be backward-compatible or requires a migration

Objective

Plan and begin replacing Dragonfly with a maintained alternative.

Client impact

High — clients with custom Dragonfly processors will need migration. This needs a deprecation period.

Acceptance Criteria

• Migration plan documented
• Prototype demonstrates equivalent functionality
• Backward compatibility strategy defined

Verification Plan

1. Document current Dragonfly usage surface
2. Prototype working image upload/process/serve cycle with new approach
3. Benchmark performance comparison