Baixar Vault Flasher 0.7.8 per a Windows

# Vault Manager v0.7.8

**You can now invite one of your apps into a space your node stores.** Until now, if a space lived on
your node — the storage your website fills, for example — there was no way to let VaultDocs or
VaultDrive open its files：your desktop apps had only *joined* that space, so they held no key to
share it, and the only link Vault Manager could make was a *management* invite, which those apps
correctly refuse. This release adds the missing generator.

## Invite an app to a space on this node

A new section, **"Invite an app to a space on this node"**, appears once you're managing a node.

• Pick one of the spaces your node stores, and press **Create invite link**.
• You get a copyable link and a QR code. Open **Accept an invite / connect a space** in the app you
want to let in — VaultDocs or VaultDrive — and paste it (or scan the QR).
• Anyone who opens the link **joins the space immediately** — the one-time link *is* your approval, so
there is nothing extra to click here.

It sits alongside the two links Vault Manager already makes, and each now says plainly what it is for
so they can't be confused:

• **Give another app access** hands a *website* management of the node.
• **Add a device to this node** connects a *phone* that just uses the node.
• **Invite an app to a space** — this one — hands an app the *files* in one space.

The link itself is minted by your node and handed to you unchanged：it is the same standard space
invite VaultDocs and VaultDrive already understand, so nothing about it is reshaped by Vault Manager.

## Verification

• **246 unit tests** (5 new)：a good reply is read into a mint with the invite token kept *verbatim*;
the `auto`/`approve` grant mode survives to the screen; an error envelope inside a `200`, or a reply
with no invite, is a failure; and the mint's error copy names the mint's own failures (an old node,
a scope refusal, a personal space) rather than borrowing the join-approval screen's wording.
• The mint is a **§4 signed request at manage scope** — the same signing Vault Manager already uses to
read the join queue and mint a management invite — never the owner token.
• Guards green：the invoke-args guard confirms the new command and its screen agree; the
surface-purpose guard (now covering all four connect/invite surfaces, self-test 6/6) pins each
surface's *what it's for / the other half / when not to use it*.

**Still owed — the live end-to-end.** Minting a real link and redeeming it in VaultDocs/VaultDrive
needs a node paired into Vault Manager on this computer. The generator is complete, built and tested;
the round-trip cert is the same live test its neighbours owe.

## Downloads

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

```
NSIS setup.exe sha256 d60cf09cb5cc33622a4a62f4b2f3793564d7169637df2e60a86207bad6f97838
MSI sha256 0ebe20441ad5438b2d0647497d8b75c88647ae9cefeaa79931f746f9ea38ee0a
```