Basalt Sync 0.8.6

One fix, from watching my own vault stop syncing for a day.

A server that answers is not a server that works

Basalt's server 0.8.4 had a bug that made it refuse every batch a device sent.
Server 0.8.5
fixes that, and you want it.

This release is about what the client did while that was happening. It
connected, was refused, and came back three seconds later. Twenty two thousand
times in a day. The backoff that exists to prevent exactly this, and which
climbs to five minutes, never got past its first step, because it reset the
moment the handshake finished.

Connecting is not progress. The reset now happens after the device has
reconciled against the server, which is the smallest thing that means the
session was worth having. A connection that drops after that is a network, and
the next attempt is quick, as before. A connection that achieves nothing and
repeats now backs off.

Nothing else about reconnection changes. A refusal your device cannot apply
still stops with an explanation after three identical failures, and an ordinary
dropped connection is still retried promptly.

Upgrading

Update the plugin through Obsidian or replace its three files. CLI users can
run npm install -g basalt-sync@0.8.6. Protocol 7 and the stored data format
are unchanged, so this works against a server on 0.8.4 or 0.8.5 and existing
pairings keep working. Upgrade the server too if you have not.