Summary

• Mark original file with xattr after copying to the -optimised path, preventing iCloud sync FSEvents from re-triggering optimisation on the original
• Add configurable protection window (optimisedFileProtectionMs) defaulting to 3s — users on iCloud Drive can increase to 30s/60s to handle longer sync times
• Fix memory leak where newPath was inserted into alreadyOptimisedFiles but never cleaned up
• Add UI picker in General > Optimisation settings for the protection window
• Include setting in SETTINGS_TO_SYNC so it syncs across Macs via iCloud

Root Cause

When OptimisedFileBehaviour is sameFolder (or specificFolder), process() copies the original to a new -optimised path and optimises the copy. The original file was never marked with an xattr, so when iCloud Drive's bird daemon syncs the new file and generates fresh FSEvents (.itemModified/.itemRenamed) on the original, it passes all checks again and gets re-optimised — creating duplicate -optimised 2.png files from iCloud conflict renames.

Changed Files

Test plan

• Build the project in Xcode
• Set image behaviour to "Same folder" with default template %f-optimised
• Save a screenshot to an iCloud-synced Desktop
• Verify exactly ONE -optimised file is created, no " 2" duplicates
• Wait 60s, verify no re-optimisation occurs
• Check xattr on original: xattr -l <original> should show clop.optimisation.status
• Verify the new picker appears in General > Optimisation settings
• Change protection window to 30s, verify setting persists across restart

🤖 Generated with Claude Code