Task Retry: Delete Partial, Fresh Attempt, Then Publish Diagram

Partial Is Deleted

A crash can land mid-write and leave a partial attempt file behind
Retry deletes the partial file before writing a single new byte
Keeping the partial and appending would duplicate or interleave rows

Fresh Attempt IDs

Each attempt writes under its own name: task-2-attempt-1, never reused
The driver commits an attempt only after its checksum verifies
Two attempts of one task never both count as committed

Readers Pin

Publication happens once, after every task has committed
The reader pins one manifest version and reads only its files
All-or-nothing: the whole result or nothing, never a mix