v0.5.45

Highlights

Experiments are now editable collections of runs.

• Add and remove runs after launch. On an experiment page, + Add runs opens a dialog that searches the workspace's runs (by name, #id, scenario set or target). Remove selected takes runs out. A run page has Add to experiment. Runs and their frozen inputs never change; only which experiments they belong to does.
• A run can belong to several experiments. Adding a run to another experiment keeps it in the first one. Run pages and the runs dashboard show every experiment a run is in.
• Factors follow the runs. The compared inputs ("compares target × max turns") are worked out from the runs currently in the experiment, so they update when runs are added or removed.
• Delete an experiment. Only the grouping is removed. Runs, results and monitors are kept; monitors simply stop being tied to it.
• Permissions: workspace admins and auditors can edit or delete a private experiment. A public experiment needs an admin and an explicit confirmation, because adding a run publishes it (transcripts included). A run is publicly visible when any experiment it belongs to is public.

Timeline: no duplicate flag when there is no captured input, and a retrieval comes first when it starts at the same time as another step.

Upgrade note: includes the migration audits.0010, which copies existing experiment links into the new table. Restart the worker together with the web process.