Sync state lives in a .ccr-dir-sync folder beside your repo so restarts resume quickly.
What's wrong with this entry?
The syncer saves what it has already agreed with the laptop into a JSON file under a .ccr-dir-sync directory next to the repository root, named after the remote session id, so a restarted worker resumes instead of re-scanning everything.
- Written with restrictive permissions: file mode 0600, directory mode 0700.
- Refuses to write if the state exceeds 64 MiB or if the file lists exceed what the reader will accept, logging "sync base too large to store".
- Permanently gives up persisting after permission or read-only filesystem errors (EACCES, EPERM, EROFS), logging
dir_sync_worker_persist_failed; syncing continues without a saved state.
.ccr-dir-sync
Strings lifted out of the shipped bundle, so the claim above can be checked against them.