Vault Manager v0.7.1
Vault Manager v0.7.1
The "Apps and spaces enrolled" list no longer disappears when a messenger connects. Mark hit
this live on 2026-08-18: the moment a Parley device enrolled on his node, the whole enrolled-apps
section went blank with an error — hiding the VaultDrive and ReelVault rows that had been showing
fine a second earlier. This release fixes that, and carries forward the space-rename polish from
v0.7.0.
What was wrong
A Parley device is a messenger — it has no VaultDrive storage space — so the node correctly reports
that enrolment with an empty (null) space. Vault Manager was reading the enrolled-members list in
one all-or-nothing pass that demanded a value for every field, so a single null field on one
enrolment failed the read for the entire list. One messenger took every other app off the screen.
The fix
- A missing or empty field is now a "—", never a crash. Each enrolment field tolerates the node
reporting nothing for it. - The list is read one row at a time, so an enrolment shaped in a way Vault Manager didn't expect
can only ever affect its own row — it can never hide the others again. A row it genuinely can't read
is shown as a placeholder rather than silently dropped. - A messenger enrolment with no space now reads "—" in the Space column, instead of a blank cell.
Also in this release
The space-Rename control from v0.7.0 (rename a space your node owns; it waits for the node to
actually apply the change, and your access never changes because grants ride the space's permanent
identity). Nothing about that changed — it's carried forward.
Verification
215 unit tests (one new — a_null_field_on_one_enrolment_never_blanks_the_whole_list — which
pins that a null-heavy messenger row leaves a well-formed row completely intact), plus the
call-site, page-structure and TLS guards. The shipped binary was launched and driven over its own
debug bridge to confirm the enrolled-members command is wired and answers safely.
Seeing the full list render with a real Parley device enrolled is a live check at the keyboard — the
node has to have a messenger enrolled to produce the null the fix is about — and the parsing logic
itself is covered by the unit test above.
Downloads
Published under both VaultManager-* and VaultFlasher-* names; the bytes are identical.
NSIS setup.exe sha256 b8be652f3e91827ffba82e4fc187c7326196074ef7aec1323d6bd0aadd1971d0
MSI sha256 51a2ee0a2cac8945cd6945409880ea5706e9a9ed12e0e44b5c51d2b9a6ad0c79
⚠ Compare hashes, not sizes.