Make backfill progress and controls more reliable

Backfills could show conflicting states in different Dashboard views, and a retry or replaced snapshot pod could make a current run appear failed or finished incorrectly. The new backfill experience was also not yet available to every company.

Artie now uses the current snapshot attempt to keep backfill status aligned across the home page, pipeline header, progress card, table list, picker, and legacy dialog. The new backfill flow is available to every company, and the speed selected in the dialog applies to the run it starts. The Dashboard distinguishes queued work, active copying, finishing work, and failed backfills more consistently.

This is for operators starting, monitoring, or retrying table backfills who need trustworthy progress signals.

Why this matters

• See the same backfill state throughout the Dashboard
• Avoid stale pod events making a new attempt look failed or complete
• Apply the selected backfill speed to the run you launch