Old snapshot folders not deleted after the 7 day threshhold

[ariane-emory]

Description

Old snapchat files are meant to be pruned after seven days.

The current implementation tracks git objects per project but lacks a mechanism to prune entire project directories based on the snapshot retention time. We ought add a comprehensive approach to identify and remove stale project directories that have exceeded the defined age limit.

Plugins

None

OpenCode version

1.1.36

Steps to reproduce

1. Use open code for at least one week with snapshots enabled.
2. Navigate to ~/.local/share/opencode/snapshot.
3. Observe that folders with timestamps greater than one week in the past exist.

Screenshot and/or share link

No response

Operating System

MacOS Sequoia latest

Terminal

iTerm2

[github-actions]

This issue might be a duplicate of existing issues. Please check:

• [FEATURE]: Snapshot lifespan ought be configurable. #10626: [FEATURE]: Snapshot lifespan ought be configurable. (directly related to snapshot retention configuration)
• HUGE snapshot folder #6845: HUGE snapshot folder (reports excessive snapshot folder sizes)
• Snapshot feature needs safeguards for large directories (home directory filled disk) #8577: Snapshot feature needs safeguards for large directories (snapshot-related disk space issue with safeguards)
• [BUG] Snapshot module ignores 'watcher.ignore' config, causing excessive disk usage and performance degradation #8887: [BUG] Snapshot module ignores 'watcher.ignore' config, causing excessive disk usage and performance degradation
• Opencode using up 380GB in ~/.local/share/opencode/snapshot/objects #9601: Opencode using up 380GB in ~/.local/share/opencode/snapshot/objects (direct report of snapshot objects consuming massive space)
• OpenCode nuked my storage (318 GB added) #9290: OpenCode nuked my storage (318 GB added) (major storage consumption complaint related to snapshots)
• Very slow session due to 98GB of git snapshots #3182: Very slow session due to 98GB of git snapshots (performance issue from snapshot storage)

Feel free to ignore if none of these address your specific case.