garbage-collector

Safe local file cleanup requires a preview-first workflow that scans target directories, generates a readable report of proposed actions, and executes deletion only after explicit user approval. This approach uses deterministic scripts and maintains undo-ready logs to support reversing actions.

A preview-first cleanup workflow explains scan findings and proposes actions before making any changes. It enforces safety boundaries on scan targets and requires explicit user consent, ensuring destructive local file actions are handled carefully to prevent unintended harm.

Yes, local cleanup actions can be undone because the workflow logs all steps for traceability and uses reversible actions like moving files to a quarantine area. This undo-ready design ensures you can recover items if a deletion was premature.

You can automate local file organization by loading custom cleanup rules from a CSV rule store. The system applies these rules during the directory scan to generate a deterministic cleanup plan tailored to your specific workspace requirements.

The cleanup script supports both reversible quarantine and permanent deletion. It applies actions with an optional permanent-delete flag, allowing you to choose between moving files to a quarantine area for undo purposes or executing irreversible destruction.

Automated workspace cleanup scripts have safety boundaries that limit scan targets to common areas like Downloads and Trash. They are constrained by explicit handling of destructive actions, meaning they cannot operate outside approved targets without clear user confirmation.