refactor(explorer): drop the trajectory-manifest download, which only the hosted hub serves

[polakamtejas]

The runs table on a task's page had a Downloads column holding one button, Trajectory Manifest. It called GET /api/v1/tasks/{id}/runs/{run_group_id}/trajectory-manifest, which only Scale's hosted AgentEnvHub serves: it returns a JSON of presigned S3 URLs for a run group's trajectories. The explorer UI was forked from the hosted hub's frontend, and the explorer backend has no such route, so the button always failed.

This removes the button, the column, and the Download icon import. The column's 10% width goes to Model (+3), Status (+4) and Score (+3). The two full-width rows (batch progress, expanded instance) now span 9 columns instead of 10.

Testing

• npm run typecheck, npm run test:smoke (11 passed; the 2 skips need trajectory fixtures) and npm run build:static pass.
• Checked in the browser against agent-env up: the runs table, an expanded run group (batch progress spans the table) and an expanded instance all align.

Follow-ups, separate PRs: the UI's other calls to hosted-hub-only routes. POST /api/v1/tasks sits in the task runner's embedded (iframe) mode, which is dead in OSS. GET …/instances/{id}/triggers feeds the Triggers tab and is worth porting.

🤖 Generated with Claude Code

Confidence Score: 5/5

The PR appears safe to merge.

Summary

The task runs table drops the Trajectory Manifest download, which relies on a route served only by the hosted hub. It gives the freed space to other columns and updates expanded rows to span the narrower table.

• Removes the manifest download button and its column.
• Widens the Model, Status, and Score columns.
• Changes expanded instance and batch-progress rows to span nine columns.

_{Reviews (1) · Last reviewed commit: "refactor(explorer): drop the trajectory-..."}