# Runs: multi-select delete and size sort Client side of the `delete_runs` contract (server built in parallel): - Request `delete_runs` `{run_ids: [int]}`; reply `runs_deleted` `{deleted: [int], refused: [{run_id, reason}], freed_bytes: int}`. - Broadcast `runs_removed` `{run_ids: [int]}` removes rows and closes an open detail (route returns to the list). - Run summaries may carry `size_bytes`; absent means unknown (nothing shown, sorted last under Largest first). UI: bar action Select (or long-press a row) enters select mode; day headings get Select all / Deselect all for that day's finished runs; active runs have a disabled checkbox whose semantics give the reason. The bar shows `N selected`, the selection size, Delete and Done. The run row and detail menus offer Delete run for finished runs. The sort choice persists (`pipelines.next.runsSort.v1`). Code: `lib/features/runs/domain/run_deletion.dart`, `ui/runs_selection.dart`, `ui/runs_selection_bar.dart`, `actions/delete_runs_{action,dialog}.dart`, `data/runs_sort_store.dart`. Tests: `test/features/runs/domain/run_deletion_test.dart`, `test/features/runs/ui/runs_delete_test.dart`. Browser evidence: `node tool/runs_delete_probe.mjs build/web