v0.2.1

A run clears its work directory before collecting, instead of being told to remove it afterwards.

The cleanup was an instruction in prose, and the first unattended run skipped it — leaving eighteen files behind, including message parts from an earlier, longer split. Those are the exact artefacts whose survival had already caused a bug: a sender walking msg-01, msg-02, … in order would have delivered two current messages followed by two from the previous run.

Clearing at the start rather than the end is the better half of the change. A run that dies partway leaves its files to be read, and the next run removes them, so the debugging value survives while a previous run's output can no longer be mistaken for this one's. --keep-work opts out.

The guard on that deletion now checks the root still holds a .newsrc.toml. Checking the work directory against the root, as first written, proves nothing: the two are derived from each other and stay consistent for any root at all, / included — which a test caught by trying to create a directory there. What is worth asserting before deleting a tree is that the evidence which justified operating on this corpus is still on disk.

No configuration change. Upgrading from 0.2.0 is a straight replacement.