Update dataset (part 2)

README.md

@@ -247,7 +247,7 @@ Harbor on your own machine.
 
 Every task runs on HUD, including the nine that have no Harbor package. The tasks are
 published there as the taskset [`ec-swe`](https://www.hud.ai/shared/tasksets/979e6e02-d726-46f6-a066-914afc5c9f44),
-which anyone can view; it is still being filled as its environments are built.
+which anyone can view; it holds all 24.
 
 To run a task in a HUD workspace of your own: each folder under `harbor/sources/` is the build
 source of one task's HUD environment. With a HUD account, on Linux, macOS or WSL:
@@ -265,9 +265,9 @@ hud eval my-ec-swe claude --full      # runs it on the platform with an agent
 Results appear as jobs and traces on hud.ai (`hud jobs`). On HUD the agent and the grader
 share one container, kept apart by file permissions, and the four tasks with a criterion
 judged by a model get that judge from HUD's gateway. The commands follow HUD's
-documentation. We rehearsed `hud deploy` and `hud sync tasks` for every folder in their
-dry-run mode and ran them in full for the terser folder; we have not run an agent with
-`hud eval` from this folder.
+documentation. We deployed eighteen of the folders this way ourselves and synced the task of
+every folder into the taskset above; we have not run an agent with `hud eval` from this
+folder.
 
 ### With Harbor