fix(benchmark): scenario status in run view and some additional tweaks

[ross-rl]

Description

Summary of Pending Changes (3 files modified)

1. src/components/StatusBadge.tsx (Minor change)

• Changed "COMPLETED" to "COMPLETE" for consistency
• Updated label from "Completed" to "Complete"

2. src/screens/BenchmarkJobDetailScreen.tsx (+59 lines)

Main feature: Fetch actual benchmark run names instead of showing IDs

• Added import for getBenchmarkRun service
• Added runNames state to cache fetched run names
• Added React effect that:
  • Collects all run IDs from outcomes and in-progress runs
  • Fetches full run details in parallel using getBenchmarkRun()
  • Extracts names (falls back to ID if name is null)
  • Stores in a Map for fast lookup
• Updated run display logic to use fetched names instead of:
  • Old: agent names or "Unknown Agent"
  • New: actual benchmark run names from API

3. src/screens/BenchmarkRunDetailScreen.tsx (+263 lines, -53 lines)

Major feature: Display scenario runs within benchmark run details

Added features:

• Scenario runs state and loading
• Overall status section that calculates aggregate status from scenario runs
  • Shows "Failed", "Complete", "In Progress", or "Not Started"
  • Displays scenario count
• Scenario runs table with columns:
  • ID
  • Name
  • Status (with colors)
  • Score
• Auto-refresh scenario runs every 5 seconds when run is active
• Polling integration to refresh scenario runs alongside run details

Removed:

• Environment Variables section (removed from both detail view and polling display)

Note: PR titles should follow Conventional Commits format (e.g., feat(devbox): add support for custom env vars or fix(snapshot): resolve pagination issue) as they are used for automatic release notes generation.

Type of Change

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• Documentation update
• Code refactoring
• Performance improvement
• Test updates

Related Issues

Closes #

Changes Made

Testing

• I have tested locally
• I have added/updated tests
• All existing tests pass

Checklist

• My code follows the code style of this project
• I have performed a self-review of my own code
• I have commented my code, particularly in hard-to-understand areas
• I have updated the documentation accordingly
• My changes generate no new warnings
• I have added tests that prove my fix is effective or that my feature works
• New and existing unit tests pass locally with my changes
• Any dependent changes have been merged and published

Screenshots (if applicable)

Additional Notes