1.3.1

Three fixes, all of them things that broke without looking broken.

Dragging in the tree stopped working after the file explorer was rebuilt

Moving the file explorer to the other sidebar, or closing and reopening it, left drag-to-reorder dead until the plugin was reloaded. The listeners were attached once to that view's element, and a rebuilt file explorer has a new one.

Saved orders kept rendering correctly the whole time, because that part is installed differently, so there was nothing to suggest the drag had come loose — checking that the tree looked right could never have found it.

An order could be written to a note the vault had not indexed yet

The companion to the startup bug fixed in 1.3.0, on the writing side. In the same startup window, a write would try to create a note that already existed. Obsidian checks the filesystem before creating and refuses, so the note was never in danger — but the write was lost while the in-memory order still showed the change, so nothing looked wrong until the next restart. It now waits for the vault to catch up.

A missing json block was not always recognised as damage

When the order note is changed from outside — another device syncing, a hand edit — a missing json block is only benign if nothing was ever stored there. That test consulted what was in memory but not the backup in data.json, so it could miss the case where memory was legitimately empty: a vault that had saved no order yet, or one just after "Clear every saved order". It now checks both, exactly as loading does.