The cloud/local file-sync protocol has a new lightweight 'standing' status distinct from a full sync report
What
The git-based cloud/local file-sync protocol gained a new, lightweight journal message kind called standing, decoded by a new function separate from the full worker note/report. When a standing message is present, the client updates its local record from it and returns a new outcome code, peer_standing, instead of the usual outcomes like nothing_new or applied. This new peer_standing value was also added to the retry-outcome switch and related status enum, alongside existing states such as no_journal, yielded, upload_only, and refused.
Why
This gives the sync protocol a cheap way to report a peer's status without sending a full sync report, which should make routine status checks lighter weight.