Tusk's Vault for Foundry 1.0.3

Corrects the package-browser description, which described only one of the module's two modes.

The previous text opened "This is a bridge, not the archivist. It does nothing on its own" — written before Lite existed. Since the package browser is the only place Foundry can tell you anything about a dependency on a non-package, that was the one screen where a prospective Lite user could learn the module answers from their journals with nothing else installed, and it told them the opposite.

The description now leads with what the module does, then names both modes:

• Lite — answers from the journal entries in one folder, cites the entry it used, honours journal permissions. Nothing else installed.
• Bridge — connects to Tusk's Vault, a separate free self-hosted app, so answers come from your whole archive instead of one journal folder.

No functional change to the module itself. The manifest validator now checks for both halves of that statement rather than only the bridge warning, using the text that shipped in 1.0.2 as its negative case.

Tusk's Vault for Foundry 1.0.2

The Foundry half of Tusk's Vault. It needs the Vault app running on the GM's own machine — install that first.

Install in Foundry — Add-on Modules → Install Module → Manifest URL:

https://github.com/KochiTusker/Tusks-Vault-Foundry/releases/latest/download/module.json

In this release

• Diagnostics no longer quote a hand-set Vault address. The dump is written to be pasted into a public issue, and the configuration block already reported a non-loopback address only as a category — the event log printed underneath it did not. Loopback keeps its port, because that number is the whole question when discovery fails and it identifies nobody.
• The Lite default model moves to gemini-3.8-flash.

Compatible with Foundry VTT v13 and v14.