style: apply ruff format across backend + scripts (line-length 100)

Mechanical, whole-tree `ruff format` pass — no behaviour change. Recorded in
.git-blame-ignore-revs (next commit) so git blame skips it.

backend/tests/test_downloads_finalize.py

@@ -6,6 +6,7 @@ file-delete-under-live-holder class (done/error hold the asset, canceled does no
 atomic `UPDATE ... WHERE status='running'`, so these tests assert it fires exactly when the job is
 still running and is a no-op otherwise. Uses the real-Postgres `db` fixture; skipped without a DB.
 """
+
 from sqlalchemy import text
 
 from app.downloads import service
@@ -53,9 +54,7 @@ def test_finalize_is_a_noop_on_a_canceled_job(db):
     # finishing child then tries to write `done`. The guard must NOT resurrect it, or a later delete
     # would double-release the asset.
     job = _running_job(db)
-    db.execute(
-        text("UPDATE download_jobs SET status = 'canceled' WHERE id = :id"), {"id": job.id}
-    )
+    db.execute(text("UPDATE download_jobs SET status = 'canceled' WHERE id = :id"), {"id": job.id})
     db.commit()
     won = service.finalize_if_running(db, job.id, status=JobStatus.DONE, progress=100)
     db.commit()
@@ -65,9 +64,7 @@ def test_finalize_is_a_noop_on_a_canceled_job(db):
 
 def test_finalize_is_a_noop_on_a_paused_job(db):
     job = _running_job(db)
-    db.execute(
-        text("UPDATE download_jobs SET status = 'paused' WHERE id = :id"), {"id": job.id}
-    )
+    db.execute(text("UPDATE download_jobs SET status = 'paused' WHERE id = :id"), {"id": job.id})
     db.commit()
     won = service.finalize_if_running(db, job.id, status=JobStatus.ERROR, error="boom", phase=None)
     db.commit()