evidence-prune-source

To safely prune local agent-out usage records already stored in an archive, use a dry-run mode to preview matched records before requiring explicit user confirmation to apply any deletions to the local source tree.

Synchronizing local agent-out records with an evidence archive catalog involves reading both the local tree and the archive catalog, then pruning local sources that are already represented in the archive to keep states aligned.

Yes, you can preview which archived agent-out records will be pruned by running the dry-run mode, which identifies matching records for deletion without modifying the local source tree until explicitly confirmed.

Yes, you need to manually confirm before the tool deletes local source files during archive pruning, as an explicit apply step is required to enforce safety and prevent accidental data loss from the agent-out tree.

Local agent-out usage records become out of sync with the evidence archive when source files are retained locally after being archived, requiring a pruning workflow to reconcile the local state with the archive catalog.