You get warned when a cloud peer stops confirming file sync, and told when it resumes.
What's wrong with this entry?
When a session shares files with a cloud peer and the peer goes two turns without confirming sync, you get a warning that your changes may not be reaching the other side, followed by a notice when confirmations resume.
- Adds two outcomes to the directory-sync pull telemetry (
ccr_dir_sync_pull): "peer_stopped" and "peer_resumed". - No separate switch beyond directory sync being active for the session.
The cloud session has confirmed file sync again
Strings lifted out of the shipped bundle, so the claim above can be checked against them.