0.1.42

Vaults can be named

A hex id tells you nothing about which vault holds your notes, and an account can easily end up with several. You can now give each one a name in Settings.

The name is encrypted with your vault key. A vault name is text you wrote — "Health journal", "Work — Acme" — so storing it readable would hand the server exactly the kind of thing this design exists to keep from it. It's encrypted on your device; the server stores bytes it cannot read, the same as your notes.

One honest consequence: only a device holding the vault key can display a name. A vault this device has no access to still shows as its id, because it genuinely knows nothing about it.

Names show up where you actually choose

The settings row now reads Personal notes · 412 files · 36 MB instead of a truncated id.

More importantly, so does the "This device already has access to" list — the screen where you pick a vault to attach to. Each row now shows its name and file count rather than two near-identical hex ids. That screen is where a device ended up attached to a one-file vault while 877 changes sat in another one.

Also

Fixed --local being ignored by the migration scripts. .env loaded first, so DATABASE_URL overrode the one flag whose entire purpose is to say "not that database".