Starting and finishing a move failed every time. The action referred to a field that does not exist in the database, so the request was rejected before anything was recorded. This was the core movement workflow, and it is fixed.
Two related improvements went with it.
Ticking a check is now settled properly when two people do it at once. A check carries a revision counter that only the database can set. If two devices change the same check, the second is held and shown beside what the server holds, for a person to settle — rather than one silently overwriting the other.
Registers refresh after you change something. Creating, editing or deleting a record left the list in front of you showing the previous version until you navigated away and back. The change was saved correctly; the screen simply did not catch up. Fixed across every module.