Document completed spell catalog baseline

docs/integrations/dnd-spell-artifacts.md

@@ -51,7 +51,10 @@ Each spell cast contains exactly these required fields:
   IDs and evidence unit ranges. It must contain at least one entry.
 
 All four string fields must be non-empty. `caster` is the in-world caster, not
-the transcript speaker. Unknown fields are rejected.
+the transcript speaker. The `spell` value must resolve through the effective
+SRD-plus-overlay catalog as either a canonical name or alias. Catalog
+validation accepts aliases but does not rewrite them; unknown fields are
+rejected.
 
 ## Source References
 
@@ -81,10 +84,18 @@ manifest metadata:
       "response_schema_id": "notarius.dnd.spells",
       "response_schema_name": "notarius_dnd_spells_v1",
       "response_schema_version": "v1",
-      "response_schema_sha256": "sha256:..."
+      "response_schema_sha256": "sha256:...",
+      "catalog_base_id": "dnd-5e-2014-srd-spells",
+      "catalog_digest": "sha256:...",
+      "catalog_overlay_ids": ["campaign.example"]
     }
   }
 }
 ```
 
-Raw prompt and schema content are not included in manifest metadata.
+`catalog_digest` identifies the effective semantic catalog, while
+`catalog_overlay_ids` is sorted and empty for a base-only configuration. Raw
+prompt, schema, catalog, alias, and local overlay-file content are not
+included in manifest metadata. Overlay origin, media type, byte size, and raw
+digest are recorded separately in the manifest's reference provenance; see
+the [JSON output contract](json-output.md#manifestjson).