Vault Flasher: versionet e vjetra dhe historiku

# Vault Manager v1.0.0

Vault Manager 1.0 is the first full release. It sets up, claims and manages your own Vault node, on a spare PC, a mini PC or a Synology NAS, and it lets you share what that node stores with your apps and your family.

## Set up a Synology NAS as a node

A new guided **Set up a server or NAS → Synology** flow.

• **Set it up for me:** enter your NAS address and DSM login, and Vault Manager does every DSM step itself. It creates the folder, uploads and checks the node image, creates and starts the Container Manager project, and reads the claim code. Your DSM password is used for that one setup and never stored. Two-factor sign-in is supported.
• **I'll do it myself:** a click-by-click guide for DSM 7.2 and 7.4, with every field and value spelled out. If your NAS has no `docker` shared folder, the guide covers that too.
• The offered node image always follows the current release, and it's checked against its published SHA-256 before use.

Tested from a clean DSM 7.2 and 7.4.1 install, with and without an existing `docker` share, end to end：node running, claimed and serving.

## Manage your node from anywhere

• Manage a node from off your home network. Vault Manager falls back to your node's secure tunnel when it can't reach it directly.
• Your owner credentials are sealed at rest in the Windows keychain (AES-256-GCM), including backups.
• The node list shows friendly app names, clear "recovering" states while a node restarts, and no more endless "checking…".
• Storage：mirror a data disk onto a spare twin, see mirror status and last-checked times, and use one clear reconfigure button.
• New **Shutdown** control, alongside Reboot.

## Spaces, invites and recovery

• Invite someone to a space as an **Editor** or a **Viewer**.
• Invite one of your apps, such as VaultDocs or VaultDrive, into a space your node stores.
• Invite links come with a QR code that is drawn locally and sized to scan reliably on a phone, even for long invites.
• **Self-service space recovery:** recover a space whose key was lost, straight from Vault Manager.
• **Rebuild in VaultDrive:** hand a damaged space off for a fast rebuild.
• Removing an app from a node, or revoking a device, can require a second owner device to confirm.

## Add-ons

Vault Manager can install signed add-ons, which run in a sandboxed frame with only the access they declare. The first is **Leaderboard Admin**, for moderating game leaderboards hosted on your node.

## Upgrading

Install over any earlier version. Your nodes, claims and settings carry over. The download names `VaultManager-x64-setup.exe` and `VaultManager-x64.msi` are unchanged, and `VaultFlasher-*` copies are included for older links.

## Checksums (SHA-256)

• `VaultManager-x64-setup.exe`：`0844dc2e7d5bee544d8da6098234878885d1faab1f393ec6334c15b74abe9fb9`
• `VaultManager-x64.msi`：`0297f5b123784063ed2ff11a73b5681553340d5cabd7b708977cc1c8f5f81cbd`

# 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
```