Vault Manager v0.7.0

Vault Manager v0.7.0

You can rename a space your node owns. Until now there was no way to do it from anywhere — Vault
Manager didn't offer it, and VaultDrive is deliberately read-only about someone else's space — so a
space kept whatever name it was first given. This release adds a Rename control to each space on
the node's Spaces panel.

Rename a space your node owns

On the Spaces panel, every space your node authored now has a Rename button. Click it, type
the new name, press Save (or Enter). That's it.

Two things make it trustworthy rather than a name that silently doesn't stick:

• It waits for your node to actually apply the change before it settles. The node accepts a
  rename and then applies it — the new name shows up on the node's own space list within about a
  minute, and on your other devices once it syncs to them. Vault Manager watches the node's own list
  and only reports "renamed" once the node itself shows the new name, never on the strength of the
  request being accepted. If a minute passes without the name changing, it says exactly that and
  keeps your typed text in place, rather than looking like it worked when it didn't.
• Your access doesn't change. Renaming touches only the name. Everything that grants access — the
  people and devices you've shared the space with, its storage pin, its enrolment — is keyed to the
  space's permanent identity, which a rename never moves. So a rename can't quietly lock anyone out.

This needs a current node (Vault Node v0.2.4-rc.3 or newer, where the node learned to rename a
space it owns). On an older node the Rename control is shown disabled, with the reason — never
hidden — and it lights up on its own once the node updates itself; there's nothing to install in
Vault Manager.

What it touches

Only the space's name, and only for a space your node authored (a member device still can't edit
someone else's space — that's correct, and unchanged). It changes none of your files and none of
your grants.

Verification

214 unit tests (four new), plus the call-site, page-structure and TLS guards. The rename control
is pinned by a structural guard that requires it to confirm the applied name from the node's own
space list rather than trusting the node's acceptance reply (the same rule the self-hosting toggle
keeps). The Rust side is unit-tested: it reads the node's acceptance versus a refusal-inside-a-2xx,
names each refusal cause honestly (an older node, no conductor, the wrong scope), and gates the
control on the release that added renaming.

The rename endpoint is live on the current Vault Node release, so the control reaches a real route
on an up-to-date node. Driving the full round-trip end to end — rename in Vault Manager, watch the new
name appear in VaultDrive and VaultDocs — is a live check at the keyboard; the code path is the same
signed request the node's own route test covers.

Downloads

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

NSIS setup.exe  sha256  36f7e3f514f3278ec2a4590e8f057edd4b8b84e58dcf1a60c0f9ec67342cf19a
MSI             sha256  fce5e8effff170ca83fb07b28fcb4c87c80c1340d4936529e71bfd7d799ad0d4

⚠ Compare hashes, not sizes.