post-deploy-cleanup

Post-deploy cleanup automation safely removes temporary artifacts like output/ and Flow/ draft files after deployment. It uses preflight checks, user confirmation workflows, and safe deletion reconciliation to prevent unintended data loss and protect other agents.

You should clean up output and Flow temporary files once deployment completes and all agent work is finished. Preflight checks confirm repository status and deployment completion, ensuring obsolete artifacts are only removed when no longer needed by other agents.

The safest way to delete post-deploy artifacts is using a workflow with preflight checks, mandatory user confirmation, and deletion reconciliation. This targeted approach removes only output/{agent_name}/ and optional Flow drafts, ensuring no impact on other active agents.

Yes, you can selectively clean up Flow drafts while keeping output files. The cleanup workflow supports targeted deletion of output/{agent_name}/ separately from the optional cleanup of Flow/{year_month}/{date}/{agent_name}/ drafts, giving you precise control over what is removed.

Yes, post-deploy artifact cleanup requires user confirmation before deleting files. The workflow implements a mandatory confirmation step and QC checks alongside preflight validation to prevent accidental data loss during the removal of temporary deployment artifacts.