Report committed comparison cleanup failures

docs/internal/app-orchestration.md

@@ -36,6 +36,11 @@ internals](prepared-report.md), [comparison execution
 internals](comparison-execution.md), and [comparison publication
 internals](comparison-publication.md).
 
+When publication has committed its new bundle, application results contain the
+absolute manifest, data-package, and successful report paths even if removal of
+the previous sibling backup then fails. That cleanup failure is still returned
+as an operational error rather than treating the new bundle as unpublished.
+
 ## Boundaries And Verification
 
 The package does not parse flags, load YAML, implement transport, construct provider SDKs, or define report-period policy. Prompt, profile, weather, and Distributor implementations remain behind project-owned contracts.

docs/internal/comparison-publication.md

@@ -11,8 +11,14 @@ is neither the filesystem root nor the working directory, rejects unsafe
 symlinks and non-directories, accepts a missing or empty directory, and permits
 replacement only for a recognized current bundle. Publication rechecks that
 plan, writes a private sibling staging directory, and installs it atomically.
-Replacement temporarily moves the recognized prior bundle aside and restores it
-if installation fails.
+Replacement temporarily moves the recognized prior bundle aside, reauthorizes
+that moved entry, and restores it if installation fails.
+
+Publication reports whether the new bundle committed. Once the new bundle is
+installed, a failure to remove the prior sibling backup does not roll it back.
+The result retains the absolute backup path and returns an inspectable cleanup
+error that unwraps the filesystem cause so an operator can recover the prior
+bundle if needed.
 
 The application preflights before prompt inspection and collection, then
 preflights again before publication. A cancellation or any failure before the