.gitSource-control history
Repositories and their history are distinct from specific generated folders inside a project.
Your work is not clutter
The repository, the conversation and the credentials behind a project are not interchangeable with generated output.

The boundary
.gitRepositories and their history are distinct from specific generated folders inside a project.
SessionsKnown Codex, Claude Code and editor working locations are protected. A new or unfamiliar location still needs care.
CredentialsKeychains, SSH keys, credential stores and recovery data belong outside routine cleanup.
Personal dataMail, Messages, Photos, iCloud and system paths have protection boundaries. Some reviews send you to the owning app instead.
Before an action
Path
Normal cleanup checks the supplied path and its resolved location, including protected folders and symbolic-link boundaries.
Identity
The normal cleanup executor rechecks an item before moving it and verifies the recorded Trash destination. Changed or uncertain items must not be treated as the scanned candidate.
Outcome
Actions and failures are recorded. An uncertain result calls for inspection, not an automatic repeat of a destructive operation.
What this does not mean
Rules are based on known locations and evidence available to the scanner. Cairn cannot know the value of every file on your Mac. A folder called build is not enough on its own to establish that its contents are disposable.
Incomplete results may mean access was denied, a time limit was reached or a scan was stopped. Review the coverage before choosing an action.
Direct deletion cannot be undone through Cairn. Put Back depends on a matching recorded item still being in Trash. Keep independent backups of important work.
Get recovery guidanceFor the work ahead
Understand the workflow before deciding what goes.