Report committed comparison cleanup failures

docs/operations.md

@@ -149,6 +149,13 @@ use the per-report statuses and retain successful output files. For a comparison
 failure, inspect the published manifest when its path is present: individual
 profile failures retain their safe result and successful Markdown files, while
 cancellation and pre-publication errors leave the prior destination unchanged.
+
+If a replacement commits but cleanup of its prior sibling backup fails, the new
+bundle remains valid and its artifact paths appear in the failed command
+summary. Preserve the retained backup path reported by the command error until
+it has been inspected and cleaned up manually; do not remove the new bundle to
+retry that cleanup.
+
 Enable explicit debug capture only when content-rich Promptkit diagnostics are
 necessary.