benchmark_upload

Register a local harbor-format benchmark with the dashboard.

Each data/benchmark/\<name>/ directory becomes a row in the dashboard's benchmark table so experiments can reference it by id. Re-uploading the same content is a no-op (we hash tasks.jsonl); re-uploading changed content registers a new version.

CLI entry point: evsys benchmark upload data/benchmark/\<name>. Programmatic: upload_benchmark(store, path).

The harbor upload body lives in _harbor_upload.upload_harbor (reusable for other harbor-format entities) - this module only wires the benchmark store methods and keeps the historical UploadResult shape.