Erase the close history with the workspace
What It Does
Workspace erasure removes close evidence and execution records before the calendar rows they reference. The participant declares its dependency on configuration and deletes its own records in bounded batches.
The Flow
When Something Fails
A failed delete batch rolls back that batch. Completed earlier batches stay deleted, and the next callback can continue. Foreign keys reject removal of a run while its snapshots or jobs remain. Platform owns participant ordering and retry delivery; only the declared dependency and module callback are verified here.
Open Design Questions
The participant implementation establishes the local deletion order and workspace isolation. Platform evidence is still needed to verify orchestration and retries across participants.