maintenance

Automated cleanup of Plans.md and session-log.md moves completed tasks to an archive section and splits oversized logs into monthly archives. This keeps workspaces lean, readable, and SSOT-aligned while preserving project history.

Archiving old logs and trimming state files safely requires a selective cleanup process with dry-run options and SSOT synchronization checks. These safeguards prevent removing in-progress items and verify state alignment before executing destructive actions.

Yes, you can delete stale log files while protecting active research workflows by enforcing safeguards that check for in-progress items. Per-target subcommands and SSOT sync requirements ensure only obsolete files are removed during maintenance.

SSOT synchronization checks verify that your single source of truth is fully aligned before any destructive cleanup occurs. This mechanism prevents data loss by blocking the removal of state files or logs that have not been properly synced.

You should not use automated file cleanup when your project has unsynchronized state files or active in-progress items in Plans.md. Bypassing SSOT checks or dry-run options risks permanent data loss during the maintenance process.