Vault Manager v0.7.7

Vault Manager v0.7.7

You can now name the devices asking to join a space, so you can tell which is which. When two
devices are waiting for you to approve them, the node often labels them identically (or not at all) —
so approving the right one meant comparing raw keys. Now you give each one your own name once, and it
shows under that name every time it appears.

Name a device on the space-join screen

Every device waiting to join a space gets a "Name this device" button (it reads "Rename" once
you've named it). Click it, type something you'll recognise — "Mark's phone" — and Save.

• The name shows in place of whatever the node called the device, with the device's full key still
  underneath for the character-by-character check, and the name the device gave itself kept faintly
  beside yours.
• It follows the device — the same device shows the same name across refreshes and across every
  space it asks to join.
• It is kept on this computer only. Naming a device changes nothing about the device and does not
  grant it any access — the node has no way to set these labels, so this is Vault Manager's own note
  to you. (It deliberately does not follow a re-paste: re-opening an invite makes a brand-new key, and
  Vault Manager never pretends two keys are the same device — the same reason it warns you about
  superseded requests.)

Verification

• 242 unit tests (4 new): the name renders by agent key; it follows one key across spaces but a
  different key (a re-paste) carries no name; an empty key is never named; and the name is trimmed,
  bounded to 60 characters, and cleared by a blank.
• The naming, keying and normalisation live in Rust as the single source of truth; the screen renders
  the result, and the invoke-args guard confirms the page and the command agree.
• Live-driven on the built binary: the release vault-manager.exe was launched and the naming
  command exercised against the real local store — a name is trimmed and persisted under the device's
  key, a blank clears it, a long name is capped at 60, and a keyless request is refused with a reason.
  7/7, against no node.

The one thing still owed is the button-click-through against a real pending join request, which needs
a device actually asking to join one of your spaces — the same live cert as the screen's other actions.
The naming itself is complete and tested.

Downloads

Published under both VaultManager-* and VaultFlasher-* names; the bytes are identical.

NSIS setup.exe  sha256  fd6b8e2d311e208c223c6b61236db9386a84ef1031a269203e6040c6bd61f1e3
MSI             sha256  f18dc2ac80d064126f8e015c9de7948c8fd25fef942e7cdf606e04f0761ea327