fix: Correct workflow name for run_unit_evals

The run_unit_evals.yml workflow was incorrectly named 'run_agent_evals'
due to both workflows being generated from the same module. This caused
duplicate workflow names in GitHub Actions.

Changes:
- Updated run_agent_evals.rs to explicitly set the workflow name for
  run_unit_evals to 'run_unit_evals'
- Regenerated workflows using 'cargo xtask workflows'
- The workflow file now correctly identifies itself as 'run_unit_evals'

This fixes potential CI/CD issues where GitHub Actions would be confused
by duplicate workflow names.

Author: Huggyturd

.github/workflows/run_unit_evals.yml

@@ -1,6 +1,6 @@
-# Generated from xtask::workflows::run_agent_evals
+# Generated from xtask::workflows::run_unit_evals
 # Rebuild with `cargo xtask workflows`.
-name: run_agent_evals
+name: run_unit_evals
 env:
   CARGO_TERM_COLOR: always
   CARGO_INCREMENTAL: '0'

tooling/xtask/src/tasks/workflows/run_agent_evals.rs

@@ -57,7 +57,8 @@ fn agent_evals() -> NamedJob {
 pub(crate) fn run_unit_evals() -> Workflow {
     let unit_evals = unit_evals();
 
-    named::workflow()
+    Workflow::default()
+        .name("run_unit_evals".to_string())
         .on(Event::default()
             .schedule([
                 // GitHub might drop jobs at busy times, so we choose a random time in the middle of the night.