sync is for when you want the archive current immediately, before
asking your agent about something you just did, for example.
For an invited project, run sync once from your local clone after accepting
the invite. That first run registers the clone with the daemon; subsequent
syncs happen automatically.
What it covers
Only the current project. The daemon covers every project in the registry;sync is scoped to the directory you are standing in.
The command finds the nearest .resumecontext.json by walking upward from your
current directory. The daemon does the same on every tick. If a registered
directory no longer resolves to the expected project marker, that project is
skipped until the marker is fixed; other projects keep syncing.
Sharing the daemon’s lock
sync takes the same exclusive lock the daemon uses, so a manual run cannot
race a background tick and double-push or corrupt the sync cursor. If the daemon
is mid-tick, sync waits for it.
Turns are deduplicated on content, so pushing the same history twice, or from
two machines that share it, stores it once.