All legacy versions have the same semver label (1.0.0-beta.1)

[ScuttleBot]

Problem

The /benchmark_versions endpoint returns all legacy git-hash versions with the same semver: "1.0.0-beta.1" label, making them indistinguishable.

Current API Response

{
  "id": "c6da2ea",
  "semver": "1.0.0-beta.1",  // All the same!
  "label": "1.0.0-beta.1"
},
{
  "id": "07e25144",
  "semver": "1.0.0-beta.1",  // Same again
  "label": "1.0.0-beta.1"
},
{
  "id": "180baea",
  "semver": "1.0.0-beta.1",  // And again...
  "label": "1.0.0-beta.1"
}

Expected

Each legacy version should have a unique beta number based on chronological order:

{
  "id": "c6da2ea",
  "semver": "1.0.0-beta.80",
  "label": "1.0.0-beta.80"
},
{
  "id": "07e25144", 
  "semver": "1.0.0-beta.79",
  "label": "1.0.0-beta.79"
}
// etc, numbered by created_at order

Root Cause

The backfill migration (20260406_backfill_legacy_versions.sql) was supposed to assign sequential beta numbers, but either:

1. The migration didn't run correctly
2. The /benchmark_versions endpoint isn't reading from the right column
3. The version-to-semver mapping table exists but isn't being joined properly

Investigation Needed

1. Check benchmark_versions table — does it have unique semver values?
2. Check the API route that builds /benchmark_versions response
3. Verify the backfill migration ran successfully

Related

• Backfill migration: api#37
• Leaderboard display issue: leaderboard#78