v0.1.3 — fix the relationship schema that blocked manifest install

Installing by manifest URL failed on a remote server:

  [Module.vanity-delve] validation errors: relationships: systems:
  ArrayField 0: type: requires is not a valid choice

The relationship entry used type: "requires". In Foundry's schema `type` is the
PACKAGE type — module, system or world — and the relationship kind is expressed
by which array the entry sits in. So the correct value is "system".

The entry now also carries VANITY's manifest URL, so Foundry can offer to
install the system rather than just refusing.

This was never caught because the module had only ever been installed by copying
files into Data/modules by hand. The validator that rejected it only runs on the
manifest-install path, so every local test passed while the published artifact
could not be installed at all — the same shape as the scene-control hook bug,
where testing the layer below the interface hid a failure in the interface.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>

foundry-module/module.json

@@ -2,7 +2,7 @@
   "id": "vanity-delve",
   "title": "DELVE — a dungeon layer for VANITY",
   "description": "Generates a coherent delve and sequences VANITY's Forge to stage it, one area at a time.",
-  "version": "0.1.2",
+  "version": "0.1.3",
   "compatibility": {
     "minimum": "13",
     "verified": "14.365"
@@ -11,7 +11,8 @@
     "systems": [
       {
         "id": "vanity",
-        "type": "requires",
+        "type": "system",
+        "manifest": "https://raw.githubusercontent.com/slaguru666/Vanity/main/system.json",
         "compatibility": {
           "minimum": "0.10.0"
         }