Persist retryable post-publish cleanup obligations

docs/internal/workspace.md

@@ -54,13 +54,17 @@ lock only while their context remains active, and report a release failure.
 
 Automatic post-publish cleanup:
 
-- only runs when publish actually executed and succeeded;
+- is created only after a successful publish commit with complete publish
+  metadata, then is persisted before any deletion;
 - requires `uploaded=true`, a remote commit key, and a current commit-pointer
   key in publish metadata;
 - consumes the resolved cleanup policy described in
   [Configuration](../config.md);
 - refuses unsafe deletes (root delete, out-of-root delete, and symlinked
-  ancestors or entries).
+  ancestors or entries);
+- retries any recorded incomplete target on later invocations even when no
+  publish work is selected. Missing targets are a successful, idempotent
+  cleanup result only after the completion evidence is saved.
 
 Manual cleanup uses the same root-confined deletion mechanism. Invocation
 syntax and exact deletion scope belong in [CLI](../cli.md#clean) and