artifact-consolidation

To prune session artifacts, you run a dry-run safety check to inventory and categorize plans, handoffs, and tasks by age and status, then execute deletions only after explicit approval using git safety commits for auditability.

The best way to clean up artifact bloat is phase-driven pruning, which classifies plans, archived handoffs, and feature task directories based on age, references, and completion status before removing them.

Dry-run pruning works by generating a report that inventories and categorizes artifacts in plans, archive/handoffs, and tasks directories without deleting anything, ensuring safe review before any action is taken.

Yes, you can revert artifact deletions because the process uses git-based safety commits to capture checkpoints and deletions, enabling full auditability and revertibility for any removed plans or handoffs.

Artifact consolidation requires git to manage workspace cleanup, as it relies on git-based safety commits to capture deletion checkpoints and ensure the process is audit-ready and reversible.

You should not use automated pruning without explicit approval, as the workflow requires a manual review of the dry-run report to verify references and status before executing any git-based deletions.