pub fn runs_tasks_page(
corpus: &str,
service: &str,
previous: Option<&str>,
current: Option<&str>,
previous_status: Option<&str>,
current_status: Option<&str>,
offset: Option<usize>,
page_size: Option<usize>,
pool: &State<DbPool>,
) -> Result<Template, Status>Expand description
The human task-diff screen: a server-rendered, filterable table of the individual tasks whose
status changed between two snapshots — the 1:1 HTML twin of api_run_task_diffs, sharing
TaskDiffDto. This is the filter-driven heart of run management: pick a
previous_status → current_status transition (and optionally a snapshot pair) and see exactly
which documents regressed or improved. This parses gracefully: 400 on a malformed
date/status, 404 on an unknown corpus/service, and an empty filter just lists every change.
It replaced the legacy diff-history binary route, which .expect()ed the status params and
.unwrap()ed the dates — panicking on the dispatch path (the F-1 gap, now closed).