jds-finish

To clean up temporary session artifacts after completing a workflow, you run a final verification and cleanup process. This confirms prior verification succeeded and deletes residual session data, ensuring no unintended working state remains.

The best way to verify workflow completion before deleting artifacts is to run a final verification step that checks prior verification succeeded. This prevents cleanup from occurring on incomplete sessions and removes residual temporary data safely.

Artifact cleanup does not automatically commit changes, push, or create pull requests. It acts as a safety boundary by only deleting temporary session data, leaving all version control actions to the developer or caller.

You need to run final artifact cleanup in a software engineering workflow when all plan tasks are completed and initial verification has executed. This timing ensures no residual artifacts remain and prevents unintended commits during session teardown.

Residual session data remains after workflow tasks are finished because temporary artifacts are generated during execution and require a dedicated cleanup step to delete. This final step verifies prior checks succeeded and removes all residual artifacts.