[liuchao-001]

Problem

Every fetching sync that lands on a new commit creates a snapshot at snapshots/<key>-<sha>, and nothing ever removes the old ones. On one machine this reached 676 MB, almost all superseded snapshots.

Change

• Each resolution (read, sync, write prepare, ...) records a use by setting the snapshot directory's mtime.
• A fetching sync removes snapshots registered in the same bare repository cache that are not the snapshot it just resolved and have not been used for 24 hours.
• Kept: modified or untracked content (including ignored files), snapshots whose lock is held, locked Git worktrees, anything outside snapshots/ (write-session worktrees), and non-snapshot names.
• The use time is re-checked under the snapshot lock, so a resolve that finished just before eviction keeps it.
• Eviction is best effort: any failure leaves that snapshot in place and never fails the sync. sync --offline never evicts.
• An evicted snapshot is recreated at the same path from the bare cache when resolved again.
• Repository caches are still never evicted. The specification is updated.

Why 24 hours, not immediately

Agents receive a snapshot path and may keep reading it for a whole task without calling the CLI again. Removing a snapshot as soon as a newer commit appears would delete files under a running reader.

Tests

New tests/snapshot-eviction.test.ts: retained inside the window and removed after it; modified, locked, and write-session worktrees preserved; offline sync does not evict. pnpm check, pnpm typecheck, pnpm test (119 tests) pass.

This touches src/sources/resolve.ts like #27; whichever lands second needs a small rebase.

🤖 Generated with Claude Code

[yuezengwu]

Reproduced a concurrent-use eviction defect on 5ed9c2d. The four existing eviction tests, repository check and typecheck pass; an independent regression demonstrates that a just-read snapshot can still be removed. Details are inline. Integration with current main also has conflicts in specification and sparse-worktree tests; no author branch was modified.

[yuezengwu]

Re-reviewed 41318ce integrated with current main ce8789e. The explicit-use timestamp and final eviction check/removal now share the snapshot lock; status preflight occurs before that final check. The previously reported interleaving is covered by a regression and passes. Git non-force removal still protects modifications made after the status check.

All 123 tests passed with HTTPS Git transport prohibited, along with repository checks, typecheck and real package smoke. The prior finding is resolved; no remaining defect found in this change.