Eval Curation — Curate the Suite

Problem Description

You're running a curation pass over an eval suite for a tile. The most recent tessl eval run produced per-scenario lift numbers, summarized below. The tile's owner wants a curation summary before the next publish.

Output Specification

Write a file named curation-summary.md in the working directory. The file's content depends on the suite's state:

• If any scenarios need curation, list them with the cause identification (from the tile's three-cause framework), the recommended action, and reasoning.
• If no scenarios need curation, write a one-line summary stating that no curation is needed.

Do not fabricate diagnoses for scenarios that don't need them.

Per-Scenario Lift Summary

The suite has 5 positive-case scenarios and 1 negative-case scenario. Lift values are means across 3 runs.

Note on the negative case: refuse-publish-with-uncommitted-changes tests that the agent refuses to publish when the working tree has uncommitted changes. The 0-lift means baseline and with-context agents both refuse at the same rate.