harvest-run

The last step of a run: graduate what is durable out of the run directory, then delete it. Deleting without harvesting loses the why; harvesting without deleting leaves a directory that conceals its own follow-ups.

Preconditions

The work landed, the user read the handoff, and they answered its keep-or-change questions — "keep every §3 default as logged" or the specific §3 and §4 rows they change. Without those answers, ask; they are the one input this close cannot derive. A run under review stays live and keeps its directory.

An abandoned run, or a standalone handoff doc, closes the same way — point at the file and it plays the directory's part, deletion included. With no handoff, reconstruct the three lists below from the notes and plan, put the keep-or-change questions from that reconstruction, and say so.