Sync

1. 1.Read your folder: what you changed goes up.
2. 2.Settle what both sides changed.
3. 3.Land the project’s changes: edits from Ro, the web, another computer, and deletes.
4. 4.Read again, so the project holds what landed.

Between passes the folder is read in the background. Nothing is written to it outside a pass.

In the desktop app: when you open a project, when you press Sync, when a turn you watched ends, before a command you run, and every 5 minutes while the app is open. From a terminal:

runlog sync     # one pass
runlog watch    # keeps reading; never writes to the folder

Nothing lands while a repository is mid-merge, rebase, cherry-pick or revert; the pass says so and waits. A nested repository in that state holds back only its own files. A branch switch arrives as one read. Staging, commits and stashes stay yours.