What
Per-file sync now tells you when tracked files under directories like vendor/, build/ or node_modules/ are being left out for the session, and it recognises when the cloud side has stopped: if that container is restarted and loses track of which files were synced, sync halts with a message saying so, and resumes when the peer comes back.
Details
- Two reasons are given for leaving a dependency directory out: it holds more files than a single turn can track, or those files are not checked out on this machine.
- The halted-peer state and the dependency-exclusion reporting are both new; neither exists in v2.1.241.
Evidence
its container was restarted and lost track of your synced files
Strings lifted out of the shipped bundle, so the claim above can be checked against them.