The server ETag at the last sync (compare with a vaultChanged event's etag).
true when the last sync couldn't reach the server (or the vault was opened from the offline cache)
Downloads, merges local edits and uploads them (conditional PUT, merge and retry on 412). With
localChanged: false it first asks the server and stops there when nothing changed.
Edits made to vault while the sync runs are kept: the core merges them into the result and uploads
them in up to two more rounds of the same call. Any still landing after that stay as unsynced edits
for the next sync (vault.hasPendingEdits()). The report's outcome is the most any round did.
Sets a field (creating the entry by title with create) and syncs it up.
An open account vault: the core's
Vault(entries, groups, fields, history, attachments) plus string conveniences. Editvault, thensync().