Publish a benchmark (TaskSet)

Fleet calls the published benchmark a TaskSet. Authoring YAML is an editable source; importing compiles it into canonical immutable content.

flt pull "file://$PWD/taskset.yaml" benchmark
flt inspect benchmark

Inspect before publishing. Confirm the Task count, Task keys, Environment bindings, and root digest.

flt push benchmark \
  registry-alpha.fleetai.me/acme/evals:v1 --dry-run

flt push benchmark \
  registry-alpha.fleetai.me/acme/evals:v1

A versioned push publishes the complete immutable closure, then separately attempts to advance latest by default. If that second step is refused or fails, the version remains published and retrying is safe. Add --no-latest-retag to skip the attempt to move latest.

flt pull \
  flt://registry-alpha.fleetai.me/acme/evals:v1 \
  benchmark-release
flt inspect benchmark-release

Open Tasksets → project → repository → version in Registry to browse the same root. Importing or pushing authored local YAML remains a CLI workflow; the UI can compose and publish from existing Registry roots, then verify and operate them.